Console
Docs/Get started

Overview

What PayGate is, what it is not, and the two environments your integration lives in.

#What PayGate does

  • Accepts payments: mobile money (the buyer approves a prompt on their phone) and cards (the buyer finishes on a hosted page, so card numbers never reach your server).
  • Reports one status per payment, decided after asking the provider. A redirect or deep link is never treated as proof of payment.
  • Pays recipients out: you onboard recipients, release a payment when work is delivered, then settle or let the recipient withdraw.
  • Sends events to your server and retries when it is down.

Amounts: the REST API uses integer minor units (250000 is KES 2,500). The SDKs accept major units (1500 is KES 1,500) and convert for you. Never send a float.

#Environments

Every app has two credentials from day one:

  • sandbox: runs on the simulator. No real money moves, and in production a sandbox collection is recorded as simulated without touching the tenant's books.
  • live: real providers.

Reads are scoped: a live credential cannot read a sandbox payment and vice versa. Use sandbox for development and CI, live for production. They are different credentials, not a header.

Reference

Every route, parameter and response is generated from the OpenAPI 3.1 document.

Open the API reference