Payment states and lifecycle

Understanding how payments transition through different states in Orchestration

Payment state machine

A payment in Orchestration transitions through various states from creation to completion. The exact path depends on factors like capture method, authentication requirements, and payment outcome.

State reference

requires_payment_method

Payment created but no payment method attached yet

Possible actions: Attach payment method via SDK or API

requires_confirmation

Payment method attached, awaiting confirmation

Possible actions: Confirm payment via SDK or API • Cancel payment

requires_action

Additional customer action needed (for example, 3DS authentication)

Possible actions: Customer completes authentication • Payment times out

requires_capture

Payment authorised, awaiting capture (manual capture mode)

Possible actions: Capture full amount • Capture partial amount • Void authorisation

processing

Payment is being processed by the payment processor

Possible actions: Wait for processor response

succeeded

Payment completed successfully

Possible actions: Refund (if needed)

failed

Payment failed due to decline or error

Possible actions: Retry with different payment method • Create new payment

cancelled

Payment was cancelled by merchant or system

Possible actions: Create new payment if needed

partially_captured

Only part of the authorised amount has been captured

Possible actions: Capture remaining amount • Void remaining authorisation