The Transactions page is the authoritative record of every financial movement that has passed through your OwnPay gateway. Whether a customer completed a payment via bKash, Nagad, Stripe, or a manual gateway link, every attempt — successful or not — is recorded here with its full lifecycle history. Administrators use this page to monitor revenue, investigate payment failures, verify customer payment proofs, and cross-reference the double-entry ledger.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/own-pay/OwnPay-Documentation/llms.txt
Use this file to discover all available pages before exploring further.
Accessing the Transactions Page
- Log in to the OwnPay admin panel.
- In the left sidebar under the PAYMENTS section, click Transactions.
Page Layout
The transactions interface is divided into two main views: the List View with its filter toolbar, and the Transaction Detail page.Filter Toolbar
At the top of the content area, a set of filter controls narrows down the transaction table:| Control | Description |
|---|---|
| Status Tab Filters | Quick-access tabs: All, Completed, Pending, Failed, Refunded, Cancelled. Click a tab to instantly filter the list. |
| Search Input | Match transactions by TRX ID or payment amount. Partial matches are supported. |
| Gateway Filter | Dropdown to restrict results to a specific payment processor (e.g. Stripe, bKash, Nagad, or manual gateway links). |
| From Date / To Date | Date range pickers to constrain results to a specific period. |
| Filter Button | Executes the combined search and date range query on the table. |
Transactions Table
The main table lists all matching transactions with the following columns:| Column | Description |
|---|---|
| TRX ID | Unique system-generated transaction code (e.g. TXN-20260501-0042). |
| Customer | Customer email or phone number associated with the payment. |
| Amount | Transaction value and currency. |
| Gateway | The payment processor that handled the transaction. |
| Status | Color-coded badge: green (completed), yellow (pending), red (cancelled / failed). |
| Date | Creation timestamp of the transaction. |
| Actions | View button to open the full Transaction Detail page. |
Transaction Statuses
Understanding each status is essential for managing your payment pipeline correctly.- Completed
- Pending
- Failed
- Refunded
- Cancelled
completed — The payment was successfully processed and confirmed by the payment gateway. Funds have been registered in the ledger. This is the terminal success state.A corresponding credit (CR) ledger entry is posted to the brand’s MERCHANT_PAYABLE account when a transaction reaches this state.Filtering Transactions
Select a status tab
Click the desired status tab at the top of the table — for example, Completed — to immediately filter to only successful payments.
Enter a search term
Type a full or partial TRX ID or an exact payment amount in the search field to narrow results further.
Apply gateway and date filters (optional)
Use the Gateway Filter dropdown to restrict results to a single processor. Set From Date and To Date to a specific date range. Leave these blank to search across all gateways and dates.
Viewing Transaction Details
Review the Details Block
The detail page shows the complete financial breakdown:
| Field | Description |
|---|---|
| Status | Current lifecycle state of the transaction. |
| Amount | Total amount paid by the customer. |
| Fee | Processing fee charged by the payment gateway (e.g. bKash’s percentage fee). |
| Net Amount | Amount credited to your ledger after deducting the gateway fee (Amount − Fee). |
| Gateway TRX ID | The transaction reference ID returned by the external payment processor. Use this to verify against your gateway portal or bank statement. |
| Created At / Updated At | Timestamps for when the transaction was initiated and last updated. |
Review the Customer Block
Below the financial details, the Customer Block shows the customer’s name, email, phone number, and IP address at the time of payment. This information assists in fraud investigation and customer dispute resolution.
Cross-reference the Ledger
If Ledger Entries are displayed at the bottom of the detail page, they show the corresponding double-entry journal movements (debit/credit pairs). Alternatively, navigate to Ledger and search by the TRX ID to trace the full accounting record.
Transaction Detail Fields Reference
Financial Fields
| Field | Description |
|---|---|
| trx_id | Internal unique transaction identifier generated by OwnPay. |
| gateway_trx_id | Transaction ID returned by the external gateway (e.g. bKash transaction ID). |
| amount | Gross amount paid by the customer in the transaction currency. |
| fee | Gateway processing fee deducted from the gross amount. |
| net_amount | Net funds credited to your merchant ledger (amount − fee). |
| status | Current state: completed, pending, failed, refunded, or cancelled. |
Customer Fields
| Field | Description |
|---|---|
| name | Customer’s registered display name. |
| Customer’s email address. | |
| phone | Customer’s phone number (critical for mobile wallet gateways like bKash/Nagad). |
| ip_address | Customer’s IP address at the time of checkout. |
Best Practices
Verify Gateway TRX IDs
Before releasing high-value goods or services, cross-check the
gateway_trx_id against your physical bKash, Nagad, or Stripe merchant portal statements. Do not rely solely on OwnPay status badges for large transactions.Monitor Failed Transactions
Regularly review the Failed tab. A sudden spike in failures on a specific gateway indicates a configuration error, gateway downtime, or a credentials issue that needs immediate attention.
Cross-Reference the Ledger
For every completed transaction you wish to audit financially, locate the corresponding debit/credit pair in the Ledger. This confirms the correct net amount was posted to your merchant payable account.
Handle Refunds Carefully
Before marking a transaction as refunded, verify that the reversing ledger debit will not create a negative balance in your merchant account. Always confirm with the Ledger’s Current Balance first.
Troubleshooting
| Symptom | Likely Cause | Fix |
|---|---|---|
| No transactions appear in the list | Wrong brand context selected, or no transactions exist for the current filter combination. | Verify the Brand Context in the top header, clear all filters, and click Filter again. |
A transaction remains pending after the customer claims payment | Gateway webhook (IPN) failed to fire, or the SMS parsing device is offline. | Check Developer → Webhook Logs and the Paired Devices screen for pending SMS matches or failed callback events. |
net_amount appears lower than expected | Gateway fee is higher than anticipated for the selected processor. | Review the gateway fee structure in Payment Gateways settings. |
Related Pages
Dashboard
Real-time overview of transaction volumes, revenue KPIs, and recent activity.
Ledger
The double-entry bookkeeping journal underlying every financial transaction.
Invoices
Create structured invoices and track the resulting payment transactions.
Payment Links
Inspect transactions generated from shareable payment link checkouts.