Skip to main content
POST
Confirm payment intent
Confirm consumes the session token’s one-time jti. Send an idempotency key and retain it across transport retries.

Body

Response

The response is the full partner-facing payment intent. A successful confirm normally returns authorized: the wallet side is captured or under recovery, and local merchant delivery is queued or processing. Poll GET /v1/payment_intents/{intent_id} or consume webhooks until a terminal status.
The delivery rail is not called inside this HTTP transaction. After an ambiguous response, read the intent before attempting any further action. The server’s durable single-flight guard prevents a second debit or delivery for the same intent. See Get payment intent for lifecycle states and OpenAPI for response and error schemas.