Confirm and capture a Payment Intent

These merchant actions apply to Payment Intents using customer_balance. They require a merchant secret key; a restricted or browser credential cannot authorize a customer debit.

Confirm

POST /api/v1/payment_intents/:id/confirm

Confirmation checks the exact customer, chain, asset and available balance. With capture_method: "automatic", confirmation atomically debits the customer and credits the merchant. With capture_method: "manual", it reserves funds and moves the intent to requires_capture.

curl https://api-prod.paybytoken.io/api/v1/payment_intents/pay_123/confirm \
  -X POST \
  -H "Authorization: Bearer $PAYBYTOKEN_SECRET_KEY"

Capture

POST /api/v1/payment_intents/:id/capture

Capture is valid only for a manually authorized intent in requires_capture. It atomically moves the reserved customer funds to the merchant and returns the updated Payment Intent.

curl https://api-prod.paybytoken.io/api/v1/payment_intents/pay_123/capture \
  -X POST \
  -H "Authorization: Bearer $PAYBYTOKEN_SECRET_KEY"

Both actions are state-checked and idempotent at the resource transition. Fulfill only after the verified payment_intent.succeeded event. Cancel an uncaptured authorization to release the reserved funds.