How pending transactions work

What this guide covers

Pending transactions are incomplete processing events; this guide helps you decide when to wait and when to investigate. Work through each step in order, preserve safe reference details, and stop before repeating an action if the original result is still unclear.

Step-by-step

1. Open the transaction and capture its ID, created time, last-updated time, amount, and current status.
2. Check whether the history contains a later success, decline, reversal, or cancellation event.
3. Avoid submitting an identical payment while the first record remains unresolved unless your documented workflow explicitly allows it.
4. Account for weekends, banking days, and payment-method processing differences when reviewing elapsed time.
5. Escalate with the full timeline when the status remains unchanged beyond the expected context for that payment method.

Troubleshooting

• Refresh the transaction detail rather than relying on an older list view.
• Check whether local time-zone differences make the record appear older than it is.
• For customer inquiries, communicate that the outcome is not final and avoid promising a completion time.

If the result changes after a check, record what changed and the exact time. That detail is often more useful than repeating every step.

Before contacting support

Prepare the smallest set of information needed to explain the issue. Redact passwords, one-time codes, API keys, authorization headers, CVVs, full card numbers, and full bank account details.

• Transaction and customer reference IDs
• Timestamps with time zone
• Payment method category and amount

State the expected outcome, observed outcome, current impact, and whether the issue is ongoing or intermittent.