Payment Transactions
The Payment Transactions page allows administrators to search, review, and inspect payment transaction records. It provides a transaction list, grouped order totals, filtering options, and a detailed transaction timeline.
Use this page when you need to verify payment status, review captured or failed transactions, inspect order-related payment activity, or check provider response details.
Overview
The Payment Transactions screen is divided into two main views: the transaction list page and the transaction detail page.
| View | Description |
|---|---|
| Transaction List | Displays payment transactions with filters, grouped order totals, and quick access to each transaction detail. |
| Transaction Detail | Displays the selected transaction's core information, failure details, and processing timeline. |
Transaction List
The transaction list shows payment records within the selected search conditions. At the top of the page, you can see the total number of rows and the total transaction amount.
Summary Area
| Item | Description |
|---|---|
| Rows | The number of transaction records returned by the current search. |
| Total | The total amount of the returned transactions. |
| Reset | Clears the current search conditions and reloads the default transaction list. |
Search Filters
Use the search area to narrow down transaction records by configuration, status, order ID, date range, and record limit.
| Filter | Description |
|---|---|
| ConfigId | Filters transactions by payment configuration ID. Example: 12. |
| Status | Filters transactions by payment status such as approved, failed, captured, or token-created status. |
| OrderId | Searches transactions connected to a specific order ID. |
| From | The start date of the transaction search range. |
| To | The end date of the transaction search range. |
| Take | Limits the number of records returned by the search. |
| Search | Runs the transaction search using the selected filters. |
Transaction Table
The transaction table displays payment records and groups them by order ID. Each group shows the order ID, transaction count, and group total amount.
| Column | Description |
|---|---|
| ID | The internal transaction ID. |
| TransactionId | The transaction identifier returned or stored by the payment process. If no value exists, a dash may be displayed. |
| Amount | The transaction amount. |
| Status | The current transaction status. |
| Risk | The risk score or risk information if provided by the payment provider. |
| Created | The date and time when the transaction record was created. |
| Action | Provides the View button to open the transaction detail page. |
Grouped Order Information
Transactions are grouped by OrderId. Each group displays:
- OrderId: The order connected to the transactions.
- Count: The number of transaction records in the group.
- Group Total: The total amount for that order group.
A single order may have multiple transaction records. For example, one order may include a token-created transaction, a captured transaction, a failed transaction, or another provider response record.
Common Transaction Statuses
| Status | Meaning |
|---|---|
| CAPTURED | The payment was successfully captured. |
| HOSTED_TOKEN_CREATED | A hosted payment token was created. This usually means the payment form/token process was started or completed. |
| ORDER_NOT_FOUND | The system could not find the related order for the transaction. |
| APPROVED | The transaction was approved by the payment provider. |
| FAILED | The transaction failed or was rejected. |
| REFUNDED | The transaction was refunded. |
Transaction Detail
Click the View button from the transaction list to open the transaction detail page. The detail page provides full information about a single payment transaction.
Header Summary
The top area displays key transaction values in compact labels.
- TXID: Internal transaction ID.
- ConfigId: Payment configuration ID.
- OrderId: Related order ID.
- Amount: Transaction amount.
- Status: Current transaction status.
- Risk: Risk information if available.
Core Information
The Core section shows basic transaction information. This is the main area used to inspect the transaction record.
| Field | Description |
|---|---|
| TXID | The internal transaction ID. |
| ConfigId | The payment configuration used for this transaction. |
| OrderId | The order ID connected to this transaction. |
| CustomerId | The customer ID if the transaction is connected to a customer record. |
| Amount | The payment amount. |
| Status | The current payment status. |
| ProviderTxId | The transaction ID returned by the payment provider. |
| ProviderChargeId | The provider charge ID if available. |
| RiskScore | The risk score returned by the payment provider, if supported. |
| Failure | Indicates whether the transaction failed. |
Timeline
The Timeline section shows important processing timestamps for the transaction.
| Timeline Item | Description |
|---|---|
| Created | The date and time when the transaction record was created. |
| Authorized | The date and time when the transaction was authorized, if available. |
| Captured | The date and time when the payment was captured. |
| Refunded | The date and time when the transaction was refunded, if applicable. |
| Updated | The latest date and time when the transaction record was updated. |
Failure Detail
If the transaction failed or has an error status, the Failure Detail section shows the failure code and message.
| Field | Description |
|---|---|
| FailureCode | The failure code returned by the system or payment provider. |
| FailureMessage | The failure message explaining why the transaction failed. |
Recommended Workflow
- Open Admin > Payment > Transactions.
- Set the date range using From and To.
- Enter an OrderId, ConfigId, or Status if needed.
- Click Search.
- Review grouped transaction records by order.
- Click View to inspect a specific transaction.
- Check the Core section, Timeline, and Failure Detail.
- Click Back to list or Back to return to the transaction list.
Common Use Cases
| Use Case | Recommended Action |
|---|---|
| Check whether an order was paid | Search by OrderId and review the transaction statuses. |
| Find failed transactions | Search by failed status or inspect transactions with failure messages. |
| Review captured payments | Search for captured transactions and verify the amount and captured timestamp. |
| Investigate missing orders | Open transactions with ORDER_NOT_FOUND and check the failure message. |
| Review payment provider data | Check ProviderTxId, ProviderChargeId, status, and timeline values. |
Troubleshooting
| Problem | Possible Cause | Solution |
|---|---|---|
| No transactions are displayed | The date range may not include any records, or the filters may be too restrictive. | Reset the filters or expand the date range. |
| Order is not found | The transaction may reference an order ID that does not exist in the order table. | Check the OrderId and verify that the order exists. |
| Amount is $0.00 | The transaction may be a token, failed, test, or non-payment record. | Open the detail page and review the status and provider information. |
| Provider transaction ID is empty | The provider may not have returned a transaction ID, or the process failed before provider confirmation. | Review the status, failure message, and payment provider logs. |
| Timeline value is missing | The transaction may not have reached that processing stage. | Check the transaction status and provider response. |
Best Practices
- Use the date range filter first before searching large transaction history.
- Search by OrderId when investigating a specific customer payment issue.
- Review grouped totals to understand all payment activity connected to one order.
- Open the detail page when the status is failed, missing, or unclear.
- Do not rely only on the list page; use the detail page to confirm provider IDs, status, and timeline data.
- Keep payment provider logs available when investigating serious payment issues.
Payment transaction records are important financial records. Review them carefully before making changes to related orders, refunds, customer billing records, or provider settings.