Skip to main content
An order is the unit of work in the Checkout API. You create one, the customer pays it, and you poll it until it settles.

​
Authentication

All order endpoints authenticate with your public key in the api-key header, and all of them take an RSA-encrypted body:
Track an event is the exception to the envelope shape — its key is capitalised: {"Data": "..."}.

​
Endpoints

​
The order of operations

1

Optionally, quote the fee

Get order fee tells you what the customer will actually be charged, before you create anything.
2

Create

Create an order with your own unique reference. The response tells you which payment methods are available for that currency.
3

Pay

Pay an order with the method-specific payload. Returns a redirect or account details for the customer.
4

Poll

Get order status until isFinalStatus is true.
5

Verify

Verify an order from your backend with your secret key before fulfilling.

​
Your reference

You choose the order reference at create time. It must be unique across your account, and it is the key for every subsequent call about that order — payment, status, verification, refunds.
Generate the reference before you create the order and store it immediately. If a create call times out you have no other way to find out whether the order exists.
Reeple also returns its own identifiers, which you can log for support but should not use as your primary key:

​
Currency support

The currency is fixed at creation and determines which payment methods are offered. See Supported currencies.