Skip to navigation

Confirm Intent

Deprecated
View as Markdown

[DEPRECATED — removed] Confirm a payment intent.

This endpoint is retired and always returns HTTP 410. It was never wired to a real charge path: it marked the intent succeeded without contacting a processor, producing card-independent phantom successes. There is no correct standalone “charge a PaymentIntent” flow — a PaymentIntent is settled as part of paying its invoice.

To collect a payment, pay the invoice instead (e.g. the invoice pay-with-intents / collection flow), which charges through the customer-present checkout path and reconciles the invoice.

Authentication

AuthorizationBearer

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

Path parameters

external_idstringRequired
account_idstringRequired

Headers

Idempotency-Keystring or nullOptional>=8 characters
A unique key for this request. A retry with the same key returns the first response instead of running again, for 24 hours. Keys are per caller.

Request

This endpoint expects an object.
payment_method_idstring or nullOptional
metadatamap from strings to any or nullOptional

Errors

410
Gone Error
422
Unprocessable Entity Error