Payments and transaction statuses

Understand the payment lifecycle

A payment can pass through authorization, pending processing, completion, decline, cancellation, reversal, or refund-related events. The visible status is a snapshot; the event history provides the fuller story.

Use the transaction ID, created time, amount, status, payment-method summary, and internal order reference together when identifying a record.

Read common statuses

• Successful or completed: the recorded processing outcome is final in the platform context. Reconcile related events before fulfillment.
• Pending: processing is not final. Check the most recent event and avoid an immediate duplicate attempt.
• Declined: the attempt was not approved. Verify non-sensitive input and allow the customer to contact their issuer.
• Canceled or voided: an available action stopped an operation before normal completion.
• Reversed: a prior authorization or movement was released or undone through the processing lifecycle.

Handle a declined payment

1. Confirm the final transaction status and preserve the safe transaction ID.
2. Review customer-facing error information without collecting full card details.
3. Ask the customer to verify their information or speak with their issuer.
4. Offer another valid method only if the customer chooses it.
5. If the result appears technical, collect timestamps and the exact safe error message for support.

Investigate a pending transaction

1. Open the record and compare its created and last-updated times.
2. Check for later success, decline, cancellation, or reversal events.
3. Confirm time-zone and banking-day context.
4. Avoid processing an identical attempt while the first remains unresolved.
5. Escalate with the timeline when the state remains inconsistent with the available payment-method context.

Search, confirm, and reconcile

Search by transaction ID first when available. If you need broader filters, combine a limited date range, amount, status, and safe customer or order reference. For duplicate-looking activity, compare unique IDs and lifecycle events before taking any adjustment action.

Receipts should be matched to the exact transaction outcome. Never request or record a full card number, CVV, password, or authentication code while investigating.