Seamless (direct) flow

In the seamless flow, your own UI collects the payment method and any fields it requires (like a phone number for EcoCash), and you submit everything directly — no redirect to a Pesepay-hosted page.

Customer

Your server

Pesepay

Wallet provider

1 Submits checkout method + phone number

2 Make payment POST /v2/payments/make-payment

3 Requests the debit

4 PIN prompt on the phone

5 referenceNumber + pollUrl status not yet final

6 Enters PIN

7 Result callback POST resultUrl

8 Confirm the status GET /payments/check-payment

1. Customer → Your server Submits checkout method + phone number
2. Your server → Pesepay Make payment POST /v2/payments/make-payment
3. Pesepay → Wallet provider Requests the debit
4. Wallet provider → Customer PIN prompt on the phone
5. Pesepay → Your server referenceNumber + pollUrl status not yet final
6. Customer → Wallet provider Enters PIN
7. Pesepay → Your server Result callback POST resultUrl
8. Your server → Pesepay Confirm the status GET /payments/check-payment

Seamless flow — an EcoCash payment approved on the customer's phone

The gap between step 5 and step 7 is the part that catches people out: your API call has already returned while the customer is still holding their phone. Show a waiting state, and drive it from the callback or pollUrl.

Building it

1. Pick a payment method and check its required fields — e.g. EcoCash needs customerPhoneNumber, InnBucks needs no extra fields at all.
2. Build the request — amount, currency, paymentMethodCode, the method’s required fields, plus resultUrl and returnUrl.
3. Encrypt and send it to Make Payment.
4. Decrypt the response and store the referenceNumber. The customer still has to approve the payment on their side, so the status you get back is usually not final.
5. Get the result via the result callback or by checking status with the referenceNumber.

Note

Card methods — Visa, Mastercard and Zimswitch — are not available in the seamless flow. Card entry happens on the Pesepay-hosted page, so use the redirect flow for those.

Caution

A 200 from Make Payment does not mean you were paid. Only a terminal transactionStatus of SUCCESS means that, and it arrives via the callback or a status check — never fulfil an order on the Make Payment response alone.

Full request/response fields, headers, and code samples in five languages: Make Payment reference →