Hosted checkout
Use this if you want no payment UI to build. You redirect the customer to Pesepay’s page, and they come back when they have paid.
Taking payments on your own web page? Use Embedded checkout. It takes every payment method, cards with 3-D Secure included, and card details never reach your servers.
The three paths differ in where the customer pays. Hosted checkout is the fastest to launch, and the Direct API is for places with no browser at all.
Use this if you want no payment UI to build. You redirect the customer to Pesepay’s page, and they come back when they have paid.
Use this if you have a web page or app and want the checkout to stay on it. You mount Pesepay Elements, and the customer pays in them.
Use this if there is no browser: USSD, WhatsApp bots, POS terminals, kiosks or charges your server starts. You build the UI yourself.
| Hosted checkout | Embedded checkout | Direct API | |
|---|---|---|---|
| Where the customer pays | Pesepay’s page | Your page, in Pesepay Elements | Your own UI and fields |
| Server work | Create the payment | Create the payment | Create and charge in one encrypted call |
| Browser work | Redirect | Mount an element | Everything: form, validation, waiting |
| Payment methods | All | All | EcoCash, InnBucks, O’mari, PayGo |
| Cards and 3-D Secure | Yes | Yes, in a Pesepay-hosted frame | No |
| Mobile money approval wait | Handled | Handled in the element | You poll or wait for the callback |
| Frameworks | Any | Script tag, JavaScript, React, Vue, Angular | Any server language |
| Best for | Fastest launch, no front end | Web shops and apps with their own checkout | USSD, bots, POS, kiosks, server-started charges |
Already on the Direct API and want cards or more methods? See Migrate from the Direct API.
Only the middle step differs. Your keys, creating the payment, the
referenceNumber, transaction statuses, the result callback and testing work
the same way on all three paths, so you learn them once. See
How payments work.