Skip to content

How payments work

Every Pesepay payment — regardless of method — follows the same shape:

  1. Your server → Pesepay Create the transaction encrypted payload
  2. Pesepay → Your server referenceNumber store it now
  3. Customer → Pesepay Customer pays hosted page, elements, or your UI
  4. Pesepay → Payment provider Processes the payment
  5. Payment provider → Pesepay Outcome
  6. Pesepay → Your server Result callback
  7. Your server → Pesepay Confirm the status
  8. Pesepay Settles to your account
The lifecycle of a Pesepay transaction
  1. Your server creates a transaction with an amount, currency, and reason for payment, encrypts it, and sends it to Pesepay.
  2. The customer pays in one of three places: on a Pesepay-hosted page (Hosted checkout), in Pesepay Elements on your own page (Embedded checkout), or in your own UI, which submits their details to the Direct API.
  3. Pesepay processes the payment with the relevant provider (EcoCash, a card network, a bank, etc).
  4. Your server finds out the result — either pushed to you via the result callback, or pulled by checking status with the referenceNumber.
  5. Funds settle to your payout account roughly T+2 days after the transaction completes.

Every transaction gets a referenceNumber the moment it’s created. Store it against your order/invoice immediately — it’s what ties together the initiation request, the result callback, and any status checks you make later. See the transaction result fields.

Hosted checkoutEmbedded checkoutDirect API
Where the customer enters payment detailsPesepay’s hosted pagePesepay Elements on your pageYour own UI
Payment methodsAll, cards includedAll, cards includedEcoCash, InnBucks, O’mari, PayGo
PCI/compliance surface on your serversMinimalMinimal: card fields run on a Pesepay originLarger — you handle method-specific fields
Best forFastest to shipYour own checkout on the webNo browser: USSD, bots, POS

Hosted checkout → · Embedded checkout → · Direct API →

For the full comparison, see Choose your integration.

Any of the three can settle part of each payment to a second merchant automatically — see Split payments.