Payment Lifecycle
Trace each transaction’s journey — from initiation to settlement — across every payment flow.
The payment lifecycle defines how a transaction progresses from initiation to settlement, including possible paths such as authorization, capture, refund, or void.
Each stage is determined by the transaction type (paymentType) and the status transitions returned by the system.
Core Payment Statuses
Every transaction, regardless of type, moves through a predictable set of statuses:
| Status | Description |
|---|---|
InProgress | The payment is being processed—awaiting input, authorization, or issuer response. |
Approved | The payment has been successfully authorized or captured. |
Declined | The payment was rejected by the issuer or gateway. |
Settled | The transaction has been batched and funds moved for settlement. |
Voided | The transaction was canceled before settlement—no funds captured. |
Reversal | System-initiated cancellation (timeout, duplicate, or communication failure). |
Adjustment | A manual correction made before settlement. |
Once settled, a transaction is considered final but can still appear in dispute or chargeback reports if later challenged.
Payment Types and Flows
Each transaction type follows its own lifecycle, but all share the same core statuses.
Sale Flow
A Sale represents an authorization and immediate capture of funds.
Lifecycle:
InProgress → Approved → Settled → [End]
↓
Voided / Reversal / Adjustment| Status | Description |
|---|---|
InProgress | Payment initiated and awaiting issuer authorization. |
Approved | Authorization and capture succeeded. |
Voided | Merchant voided before settlement. |
Reversal | System canceled due to timeout or communication issue. |
Settled | Funds deposited post batch close. |
Adjustment | Manual correction before settlement. |
Authorization and Capture (AuthOnly & SaleCompletion)
Used when you want to authorize funds first and capture them later.
Step 1: Authorization
- Initiate with
authOnly: true. - Response includes a
paymentTokenused for later capture. paymentType = Authorization
| Status | Description |
|---|---|
InProgress | Awaiting issuer response. |
Approved | Hold placed on funds (not yet captured). |
Declined | Issuer declined authorization. |
Voided | Hold released if not captured within the allowed period (typically 7 days). |
Adjustment | Manual correction before capture. |
Step 2: Capture (SaleCompletion)
- Make a new payment request using the same
paymentToken. - Set
paymentType = SaleCompletion.
| Status | Description |
|---|---|
InProgress | Capture requested and awaiting confirmation. |
Approved | Capture successful — funds are now collected. |
Voided / Reversal | Merchant or system cancellation. |
Settled | Funds batched for deposit. |
Confirmation of capture:
paymentType = SaleCompletionauthOnly = falsestatus = Approved
There’s no explicit “Captured” status — once captured, the transaction remains Approved until Settled in the batch.
Refund Flow
Used to return funds for a completed transaction.
InProgress → Approved → Settled → [End]
↓
Voided / Reversal| Status | Description |
|---|---|
InProgress | Refund initiated, awaiting gateway or issuer response. |
Approved | Refund accepted. |
Declined | Issuer rejected refund. |
Voided / Reversal | Merchant or system canceled refund before settlement. |
Settled | Refund completed and reflected in batch. |
Void & Reversal
| Type | Description |
|---|---|
| Void | Merchant-initiated cancellation before settlement. No funds move. |
| Reversal | System-initiated cancel due to timeout, duplicate transaction, or comms failure. Equivalent to Void. |
Both result in no fund movement and are considered final states.
Adjustment
| Status | Description |
|---|---|
Created | Manual ledger entry applied to a Sale, Authorization, or CashAdvance before settlement. |
Settled | Adjustment processed in batch. |
[End] | Lifecycle complete. |
Cash Advance
Used for cash disbursement via card or terminal.
InProgress → Approved → Settled → [End]
↓
Voided / Reversal / Adjustment| Status | Description |
|---|---|
InProgress | Awaiting terminal confirmation. |
Approved | Cash advance confirmed. |
Voided / Reversal | Canceled or system failed. |
Adjustment | Manual correction before settlement. |
Settled | Funds processed. |
Prepaid & Withdrawal Transactions
| Type | Description | Typical Flow |
|---|---|---|
| Prepaid | Instant approval — skips Authorization stage. | InProgress → Approved → Settled |
| Withdrawal | Cash withdrawal or merchant payout. | InProgress → Approved → Settled |
Balance Inquiry
Represents a non-monetary check (e.g., account balance).
| Status | Description |
|---|---|
[End] | Informational only; no fund movement. |
Lifecycle Diagram (Summary)
Here’s a simplified overview of how major payment types flow:
Authorization (AuthOnly)
├── Approved → SaleCompletion → Settled
└── Declined / Voided
Sale
├── Approved → Settled
├── Voided / Reversal
└── Adjustment
Refund
├── Approved → Settled
└── Voided / Reversal
Void / Reversal
└── [End]Key Notes
- Settled indicates the transaction has been successfully batched and submitted for funding.
- Voided or Reversed means no funds were captured or released.
- Approved status can apply to both Authorization and Capture stages.
- Chargebacks are separate post-settlement events, appearing in dispute reports.
API help ticket https://prioritycommerce.atlassian.net/jira/servicedesk/projects/APIHELP/queues/issue/APIHELP-10373
All Possible Payment Statuses
Approved (Authorized) Declined Settled Voided Chargedback TicketOnly (Offline) AuthOnly (Hold) InProgress
Updated 18 days ago