Transaction details
A payment's detail page combines the current state, amounts, connector, customer context, attempts and event history.
How it works
A payment's detail page combines the current state, amounts, connector, customer context, attempts and event history. Use its references to investigate an order.
Implementation
Review the routing decision and provider errors before attempting another charge. Capture or release a held authorization only when its state allows it. Sync from the provider when events are missing; sending a webhook creates another delivery, not another payment. External-change recording and deletion are administrative operations that require careful reconciliation. Buyer-context and replay access follows your permissions and retention settings.
In this area
- Actions
- Capture or release a held payment
- Sync from provider
- Send webhook
- Record an external change
- Delete payment
- Why a payment failed
- Tabs
- Routing decision
- Processor payout
- Buyer context and replay
Controls and values
| Control | Values and related labels |
|---|---|
| Refund | Succeeded, Partially captured, Refunds, Read & Write |
| Capture / Release authorization | Awaiting capture, Partially authorized, Partially captured & capturable, Transactions, Read & Write |
| Open in processor dashboard | Provider Dashboard Access |
| Send webhook | Fire Webhooks Manually |
| Record an external change | Merchant Admin, Shop Admin |
| Create invoice (Invoice card) | Invoices & Credit Notes, Read & Write |
| Delete payment | Transactions, Read & Write |
| Overview | Invoice, Status timeline |
Related guides
Fragen zu deiner Integration? SpicePay kontaktieren ↗