PaymentIntent lifecycle and statuses

A PaymentIntent tracks a payment from creation through customer action, authorization, and capture. Read its pi_status value to decide the next merchant action.

PaymentIntent statuses#

Use the exact pi_status value returned by XPay. The documented manual-capture status is requires_capture.

Typical automatic-capture path#

requires_payment_method
        ↓
requires_action, when authentication is required
        ↓
succeeded

A failed attempt can return the PaymentIntent to requires_payment_method, allowing the customer to provide another supported method.

Manual-capture path#

requires_payment_method
        ↓
requires_action, when authentication is required
        ↓
requires_capture
        ↓
succeeded

Use Capture a payment later after a manual-capture PaymentIntent reaches requires_capture.

Reconcile the state#

The SDK result helps the frontend respond to the current attempt. The merchant backend should also process verified webhook updates and store the PaymentIntent ID and current status against its order record.

Use the Retrieve Payment Intent API for the complete retrieved object and statuses returned by that operation.