Skip to main content
Creates and charges an order in one call using a stored card token. This is the off-session path — for subscriptions, retries and repeat billing where there is no customer at a checkout page to complete an authentication step. Unlike every other payment route, there is no separate create-then-pay: one request does both.

​
Endpoint

​
Authentication

Authenticate with your secret key in the api-key header.
This endpoint moves money with no customer interaction. Keep the secret key server-side and charge only with a mandate the customer has actually agreed to.

​
Request body

Plain JSON — this endpoint is not encrypted.

​
Customer object

​
Order object

​
Payment object

​
Authorization object

​
Request example

​
Response

Returns the same shape as Pay an order: a paymentDetail and an orderPayment.
A successful response still isn’t proof of payment. Poll Verify an order with the reference you supplied, exactly as you would for an interactive payment.
If the issuer requires authentication despite the token, paymentDetail.redirectUrl comes back populated. Off-session, there is no one to send there — treat that as “this charge needs the customer” and fall back to an interactive payment rather than dropping the redirect.

​
Where the token comes from

cardToken is issued when a card is stored:

Save a card

Store the card after a successful order.

Save at charge time

Set saveCard: true on the original charge.
cardToken here is a different identifier from the savedCardId used by Pay with a card. savedCardId is an in-session convenience with your public key; cardToken is the off-session credential used with your secret key. Confirm with Reeple how the token is surfaced for your account.

​
Common errors

Use a fresh, idempotent reference for every billing period. Reusing one returns an error rather than charging twice — which is the safe outcome, but it means a genuine retry needs a reference you can recognise as the same attempt.