Retrieve payment status
Retrieves how far a payment has got and what the buyer must do next, if anything. A payment is collected in the background, so poll this rather than reading the create response. Accepts either a secret key or the payment’s own client_secret, so the surface collecting the payment can poll it directly.
Authorizations
An Account API key, account-scoped JWT, App API key, or user OAuth token. Prepend the key or token with Bearer, for example Bearer ***************************.
Path Parameters
The unique identifier of the payment.
Response
Payment status retrieved
The payment this status describes, prefixed pay_.
Details of the most recent failed attempt, or null when the payment has not failed.
What the buyer must do next while status is requires_action, otherwise null.
Always payment_status.
Present while status is processing on a settlement rail, otherwise null.
Where to send the buyer once the payment reaches a resting state, or null to leave them where they are. Editable until they return — see the return_url operation.
How far the payment has got. requires_confirmation — nothing attempted yet, or the last attempt failed and can be retried. requires_action — the buyer has a step outstanding; see next_action. confirming — the buyer has done their part and the processor is deciding. processing — the money is moving; see processing_details. succeeded — collected. canceled — voided or written off.
requires_confirmation, requires_action, confirming, processing, succeeded, canceled "requires_confirmation"

