Payment Transactions
Navigate to yStore → Payment → Transactions to view a full log of every payment transaction processed through your store.
Transaction list
The list view shows all transactions in reverse chronological order. You can search and filter by order reference, gateway, or status.
Each row in the list shows:
| Column | Description |
|---|---|
| Transaction ID | Unique identifier for this transaction record |
| Order | Linked order reference number — click to open the order |
| Gateway | Payment method / gateway used (e.g., Stripe, Bank Transfer) |
| Amount | Amount due and amount paid |
| Status | Current transaction state (see below) |
| Created | Timestamp of when the transaction was recorded |
Transaction detail
Click any transaction to open the detail view. This shows:
- Payment method code and gateway name
- Total due and total paid (useful for spotting partial payments or mismatches)
- Related order link — navigate directly to the order
- Transaction ID — the internal yStore transaction reference
- Payment request ID — the identifier sent to or returned by the gateway
- Status and last updated timestamp
- Gateway response payload — the raw response data from the gateway, used for deep debugging
Transaction states
| State | Meaning |
|---|---|
| Pending | Transaction initiated but not yet confirmed by the gateway |
| Authorized | Payment has been authorized (reserved) but not yet captured |
| Captured | Payment has been successfully captured — funds are being transferred |
| Refunded | A full or partial refund has been processed |
| Failed | The transaction was declined or encountered an error |
| Voided | An authorized transaction that was cancelled before capture |
Some gateways separate authorization from capture. Authorization reserves funds on the customer's card. Capture is when the funds are actually collected. If your gateway supports this two-step flow, you can manually capture or void authorized transactions from the transaction detail view.
Manual capture and void
If your payment gateway supports it, the transaction detail view shows action buttons for:
- Capture — collect funds on an authorized transaction
- Void — cancel an authorized transaction without charging the customer
These actions are only available when the gateway plugin supports them and the transaction is in Authorized state.
Debugging payment issues
The transactions log is the first place to check when investigating payment problems.
Customer says they paid but the order is not confirmed
- Go to
yStore → Payment → Transactions. - Search for the customer's order reference or email.
- Open the transaction and check the Status.
- If Pending: the gateway callback may not have been received. Check your gateway webhook configuration.
- If Failed: the payment was declined. Check the gateway response payload for the decline reason or error code.
- If Captured: payment succeeded. Check the order status separately — there may be a post-payment workflow issue.
- Use the Payment request ID to cross-reference with your payment provider's dashboard for the authoritative record.
Mismatched amounts
Compare Total Due and Total Paid in the transaction detail. A mismatch may indicate a partial payment, a currency conversion issue, or a fee applied by the gateway.
When escalating a payment issue to your gateway provider, share the Payment request ID from the transaction detail. This is the identifier the provider uses in their own system.