Charges a customer without them being present, using a card they saved on an earlier payment (a merchant-initiated transaction, or MIT). The same endpoint also completes Apple Pay and Google Pay payments.

Charging a saved card

1. Create a payment link with save_card set to required, optional or required_without_checkbox (Create payment link). Sending save_card to this endpoint does nothing.
2. When the customer pays, store the payment ID from the redirect, Fetch payment info, or the webhook. The payment details include the ID of the saved card.
3. Call this endpoint with that card_id and the amount to charge.

See Card on file for the full flow, including what to show the customer when they save a card.

Wallet payments (Apple Pay / Google Pay)

Send payment_link_id with an apple_pay_token or google_pay_token from Create Apple Pay token or Create Google Pay token. In this mode only payment_link_id, the token and payment_ip are read; every other field is ignored. The amount, currency and customer details come from the payment link, so the link needs a fixed amount at or above the minimum, or the call returns 422. Split payments (payouts_share) and holds (hold_and_charge_later) aren't applied to wallet charges.

Wallet payments take the customer from the link, so create the link with the customer's top-level email (plus first_name / last_name). Without an email this call returns 422 email is missing.