Charge card

Charges a saved card token. Use this for server-to-server charges when you already hold a card token — for example, for recurring or merchant-initiated transactions.

Billing fields are optional. Any field you omit falls back to the customer record on file. Fields you provide take precedence and are saved to the resulting charge record.

Headers

Request Body

Request Examples

{
"payment_intent_id": "pi_429f578b-...",
"card_token": "tokn_80aebb6ea2594a74bc215a64",
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@example.com",
"billing_address1": "123 Market St",
"billing_city": "San Francisco",
"billing_state": "CA",
"billing_zip": "94105",
"billing_country": "US"
}

Responses

200 response

One of the following variants:

{
"payment_intent_id": "pi_429f578b-...",
"transaction_id": "txn_a1b2c3d4-...",
"status": "succeeded",
"requires_action": false
}

{
"payment_intent_id": "pi_429f578b-...",
"status": "failed",
"requires_action": false,
"failure_code": "card_declined",
"failure_message": "Your card was declined"
}

400 response

Authorization

• ApiKeyAuth