The charge has been created and the payment flow has started
After the customer appears on Checkout page
No action needed — wait for the next status
The customer has been redirected to an external page (3DS or a provider page)
When redirecting to 3DS / the provider’s page
No action needed — wait for the customer/provider to complete the step
The system is waiting for confirmation (provider notification) of the authorization result
After successful 3DS verification (for cards) or in flows where authorization confirmation is required
No action needed — it usually moves quickly to authorized, declined, or failed
A “deferred” payment was created for an alternative payment method (e.g., an invoice); payment will happen later
After the customer is sent to an external APM page/invoice
Wait for payment. If it isn’t completed in time, expect declined
Funds are authorized/held on the card but not captured yet
After successful authorization
If you use the Auth/Capture model, the next step is captured
The charge is confirmed by the system and/or sent to the provider; final collection is pending
Often in sale (one-step capture) flows, or before captured in a capture flow
Wait for the final status
Funds have been captured after a capture operation (following a successful authorized)
In Auth/Capture flows after a successful capture
Fulfil the order/service and record the payment as successful
Funds have been collected (an immediate sale payment)
In Sale flows (2DS/3DS), or for some APMs after successful payment
Fulfil the order/service and record the payment as successful
The payment was declined (business/payment reason)
Fraud/antifraud rejection, provider/bank decline, failed 3DS, unsuccessful auth/capture, APM expiry, etc.
Ask the customer to try again or use another payment method. If it happens frequently, contact support
The payment failed due to a technical error
System/integration issues (e.g., server-side error)
Recommend trying again later. If it repeats, contact support with the order details