Transactions List
The Transactions List component (transactions-list) provides a full transaction querying and management interface. It allows users to search, filter, inspect, and take actions on payment transactions processed through the OnAccess platform.
Loaded via: Orchestrator Oc (requires CreditRisk approved + Adyen KYC active)
How It Works
The Orchestrator Oc handles authentication, authorization, and compliance verification before rendering this component. Once loaded, the Transactions List receives a signed JWT (authToken) and evoOrganisationId and uses these to query the Pay Querier API for transaction data scoped to the merchant's organisation.
Orchestrator Oc
|
| Passes authToken + evoOrganisationId
v
Transactions List OC
|
| Queries Pay Querier API with JWT auth
v
Pay Querier API
|
| Returns paginated transaction/operation data
v
Transactions List renders data grid
Parameters
All parameters are injected by the Orchestrator Oc. The host application does not pass these directly.
| Parameter | Type | Description |
|---|---|---|
evoOrganisationId | string | Tenant organisation ID, scopes all queries to this merchant |
authToken | string | Signed JWT (60-minute expiry) issued by the orchestrator API |
lang | string | UI language code (e.g. en) |
cultureCode | string | Locale for date/number formatting (e.g. en-GB) |
Views
The component provides two tabs:
Transactions Tab (default)
Displays individual payment transactions in a data grid with the following columns:
| Column | Description |
|---|---|
| Provider | Payment provider (e.g. Adyen) |
| Transaction State | Current lifecycle state (Authorised, Paid, Adjusted, Refunded, Canceled) |
| Date/Time | When the transaction was created |
| Client Order Reference | Merchant's own reference for the transaction |
| Provider Reference | Provider-assigned transaction ID |
| Cardholder Name | Name on the card |
| Card Type | Visa, Mastercard, Amex, etc. |
| Expiry Date | Card expiry |
| Card Number | Last 4 digits only (PCI compliant) |
| Transaction Type | eCommerce, MOTO, or Chip & PIN |
| Status | Success or Failed |
| Initial Amount | Original transaction amount |
| Current Amount | Amount after any adjustments/refunds |
| Currency | Transaction currency |
Operations Tab
Displays transaction operations (individual actions within a transaction lifecycle) as separate records:
| Column | Description |
|---|---|
| Transaction ID | Parent transaction identifier |
| Reference | Operation reference |
| Operation Name | Authorization, Capture, Refund, Adjustment, Cancellation |
| Operation ID | Unique operation identifier |
| Timestamp | When the operation was executed |
| Operation Status | Success or Failed |
Filters
Both views support filtering. Available filters:
| Filter | Type | Details |
|---|---|---|
| Date Range | Date picker | Presets: last hour, today, yesterday, this week, last week. Custom range supported. |
| Card Type | Multi-select | Visa, Mastercard, Amex, debit variants, Maestro, etc. |
| Transaction State | Multi-select | Authorised, Paid, Adjusted, Refunded, Canceled |
| Flow Type | Multi-select | eCommerce, MOTO, Chip & PIN |
| Client IDs | Multi-select | Filter by specific client/site identifiers |
| Client Order Reference | Text search | Search by merchant order reference |
Sorting is server-side. Pagination uses continuation tokens (not offset-based).
Transaction Detail Modal
Clicking a row opens a detail modal with full transaction information:
| Section | Contents |
|---|---|
| Payment Lifecycle | Parent transaction ID, flow state, success status |
| Card Details | Cardholder name, card type, expiry, last 4 digits |
| Billing Address | Full billing address (if provided) |
| Processing Details | Provider, provider reference, fraud score, funding source |
| Fee Breakdown | Fee reference, amount, type, description |
| 3D Secure | Version, authenticated status, ECI value |
| Metadata | Provider-specific data and custom metadata |
| Operations | List of all operations for this transaction |
| Available Actions | Context-sensitive action buttons (see below) |
Actions
From the transaction detail modal, users can perform the following actions depending on the transaction's current state:
| Action | Description | When Available |
|---|---|---|
| Cancel | Cancel an authorised transaction before capture | Transaction state = Authorised |
| Refund | Refund a captured transaction (supports partial refund with custom amount) | Transaction state = Paid |
| Complete / Capture | Capture a pre-authorised amount | Transaction state = Authorised |
| Top-up / Adjustment | Adjust the transaction amount | Transaction state = Paid |
Export
The current transaction or operations list can be exported to CSV. The export respects the currently applied filters and includes all matching records.
All API calls are authenticated using the JWT passed by the Orchestrator Oc.