Skip to main content
Saves the card used on a completed order, so the customer can pay with one tap next time. Saved cards come back in the savedCards array of Create an order and are charged by savedCardId — see Pay with a card.
This is the after the fact route. You can also save a card at charge time by setting "saveCard": true in the card object — see Pay with a card. Use this endpoint when the customer decides to save the card only after seeing the payment succeed.

​
Endpoint

Authenticate with your public key. See Authentication.
This is the only PATCH endpoint in the API. Sending POST returns a method error.

​
Request body

​
Payload (before encryption)

​
Request example

​
Response

Returns the standard envelope.
The provider has not published a full response body for this endpoint. Confirm the exact shape against your sandbox account before relying on any field beyond status / statusCode.

​
Rules

  • The order must have been paid with a card and reached a successful final status.
  • The card is saved against the customer identified on that order — matched by the email you supplied at order creation.
  • Saving the same card twice is a no-op rather than a duplicate.
Only save a card with the customer’s explicit consent, and tell them what they are agreeing to. You never receive or store the card number — Reeple returns a savedCardId reference instead.

​
Charging it later

Pay with a saved card

In-session, with the public key and a savedCardId.

Tokenized charge

Server-side with your secret key and a card token — for recurring billing.