Skip to main content
Every error response follows the same envelope:
status is failed, statusCode is a string, and message is safe to log but not to show to a customer verbatim.

​
Common errors

The header is missing entirely. It is api-key — not apikey, API-Key, or Authorization.
The key is unrecognised, belongs to the other environment, or you sent a secret key to an endpoint that expects the public one. See Authentication.
Returned by the secret-key endpoints — verify, refunds, chargebacks, tokenized charge — when the key is unrecognised or is a public key.
The data field could not be decrypted. Most often the wrong padding (it must be PKCS#1 v1.5, not OAEP), or an encryption key from the other environment. See Encryption.
The reference doesn’t match an order. Check you’re reusing the reference from the create-order call rather than generating a new one.
A payment for this order is already in flight. Poll Get order status rather than retrying the pay call.
A network failure or gateway error on a pay-order request does not mean the payment failed — the response may simply have been lost after Reeple processed it. Check the order’s status before retrying, or you risk double-charging the customer. Retrying a pay call for an order that already has one in flight returns 13 — Order payment is currently pending.