Skip to main content
POST
Charge a saved card

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
checkout_session_id
string
required
instrument_id
string
required

Required, never defaulted. The caller verbally agreed to a SPECIFIC card, so an implicit default is how a misheard "use my other one" charges the wrong one.

Response

Success.

amount_cents
number
charge_id
string
checkout_session_id
string
currency
string
merchant_id
string
order_id
string | null

Also the confirmation number the agent reads back: it is the MERCHANT's, not ours.

platform_call_id
string | null
processor_payment_id
string | null
replay
boolean

True when this exact charge already happened and you are seeing the original.

status
enum<string>

Where a charge stands.

pending means the charge is not settled: the processor has not confirmed an outcome, and it may or may not have taken the payment. Do NOT start another payment for the same order. We resolve it for you and the result arrives on the webhook.

completed and failed are settled and final.

Available options:
pending,
succeeded,
failed
wallet
enum<string>

Which wallet paid, when the payment came from the pay page's Apple Pay or Google Pay button. Absent on card charges. Wallet payments never create a saved card (the processor does not allow a wallet to become a card on file), so a wallet charge references no saved instrument.

Available options:
apple_pay,
google_pay