Skip to main content
Create an order returns otherPaymentOptions — the methods available for that order’s currency. Render those as the customer’s choices, then send the matching payload to Pay an order.

​
Available options

Do not hard-code this list. Availability depends on the order’s currency and on what is enabled for your account — always read otherPaymentOptions from the create-order response. An NGN order typically offers card and bank transfer; a USD order typically offers card only.
The code values returned in otherPaymentOptions are uppercase (BANK-TRANSFER), while the paymentoption field in a pay-order payload is matched case-insensitively — both bank-transfer and BANK-TRANSFER are accepted. Card is C in both places.

​
Choosing a flow

​
Card

You collect the card details, encrypt them, and send them. The response carries a redirectUrl; send the customer there to authenticate. Cards can be saved for later one-click charges — see Save a card and Tokenized charge.

​
Bank transfer

You send a bank code from List banks. The response carries a recipientAccount — a temporary account number the customer transfers to. Display it, then poll for status; the order settles when the bank notifies Reeple.

​
USSD

The customer dials a string on their phone to authorise the payment.
USSD is listed as a supported method but the provider has not published a pay-order payload for it, and GET /charge/banks?paymentmethod=ussd currently returns an empty list on sandbox. Confirm availability with Reeple before building against it. See Pay with USSD.

​
What every payload has in common

Whatever the method, the encrypted pay-order payload always carries these three fields: Everything else is method-specific.