Skip to main content
The Reeple Checkout API lets you collect payments in multiple currencies through whichever method your customer prefers — card, bank transfer, USSD, or pay-with-bank-account. You build the payment experience; Reeple handles authorisation, settlement, and status. All requests go to a single base URL:
Request bodies are encrypted with RSA before they are sent. This is not optional — every order endpoint expects an encrypted envelope. Read Encryption before writing any integration code.

​
The three operations

A completed payment is always the same three steps.
1

Create the order

Send the customer details, the amount, the currency and your own unique reference. Reeple returns the order — including its status and the payment options available for that currency. See Create an order.
2

Pay the order

The customer picks a method. You send the method-specific details (card, bank code, and so on) for the order reference. See Pay an order.
3

Verify the payment status

A success response from step 2 does not mean the money has moved — most methods route the customer through an authentication or confirmation step first. Poll Get order status until isFinalStatus is true.
Never treat the response to Pay an order as proof of payment. Card payments go through 3-D Secure; bank transfers wait on a bank notification. Only a final status from step 3 — or a server-side Verify an order call with your secret key — is authoritative.

​
Two keys, two audiences

Both travel in the same api-key header — the endpoint determines which one is expected. See Authentication.

​
Next steps

Quickstart

A complete create, pay and verify cycle you can run against sandbox right now.

Encryption

RSA payload encryption, with working code in four languages.

Order lifecycle

Every status an order moves through, and when to stop polling.

API reference

Every endpoint, request body and response shape.