Why a lifecycle exists
A payment is not always one request that immediately succeeds or fails. It can require creation, confirmation, provider processing, outcome verification, financial recording, and settlement. A lifecycle prevents the interface from interpreting a missing response as confirmed failure.
Main stages
- Creation: define amount, currency, merchant, and reference without executing the same effect twice.
- Confirmation: the authorized person or customer approves the final details.
- Processing: submit through the approved financial path.
- Outcome: success, failure, cancellation, or additional verification.
- Recording: preserve financial effect, reference, and state history.
- Settlement: include eligible activity in a settlement cycle.
- Reconciliation: match transaction, settlement, and report.
Duplicate protection
If connectivity ends after confirmation, it does not prove the payment did not execute. Financial systems use a stable key for the logical attempt so the client can retrieve the outcome instead of creating a new payment.
What the user should see
The interface should present an understandable state and next step: wait, refresh status, correct data, or contact support. Internal provider details should not become an obscure customer message.
Continue with Payment states and The settlement cycle.