Reefpay connects your application to payment processors. You send one API request; we route it to the right processor, normalize the response, and handle settlement.
Nineteen operations cover the whole API. Most integrations use fewer than ten.
Quickstart
Send your first card sale and read the response.
Authentication
The two headers every request needs, and the third resellers use.
Environments and test data
Where to send requests while you build, and which cards to use.
| Take card payments | A sale in one call, or authorize now and capture when you ship |
| Take bank payments | ACH debits through VeriCheck, and payouts back out |
| Store payment methods | A token issued with the transaction, so card numbers never reach your systems |
| Bill on a schedule | Recurring payments with the stored-credential fields card networks require |
| Reverse a payment | Void before settlement, refund after |
| Reconcile | Transaction and batch reporting |
| Board merchants | Clients and processor integrations, for platforms and resellers |
- Amounts are integers in cents.
10000is 100.00 USD. USD is the only currency. - A decline returns
200. Branch onresult, not on the status code. See Handle declines. - There are no webhooks. Anything that arrives after the response — settlement, an ACH return — is found by polling.
- There is no idempotency key. Reconcile before retrying a payment.
Known limitations has the full list.