Transactions
The Transactions page shows all payments processed through your providers.
Payment Lifecycle
Every payment goes through these statuses:
| Status | Description |
|---|---|
PENDING | Payment created, waiting for customer to complete payment form |
PROCESSING | Customer completed payment, provider confirmed success, awaiting settlement |
COMPLETED | Settlement sent successfully |
FAILED | Payment failed (card declined, expired, etc.) |
CANCELED | Payment canceled (timed out or manually canceled) |
CRASH | System error during processing (rare) |
REFUNDED | Payment was refunded through the provider |
DISPUTED | Payment is under dispute |
Transaction Details
Each transaction shows:
- Amount — Gross payment amount in cents (e.g., 10000 = $100.00)
- Currency — Payment currency (e.g.,
usd) - Net — Your earnings after fee deduction
- Status — Current payment status
- Card — Last 4 digits of the card used
- Brand — Card brand (visa, mastercard, amex, etc.)
- Cardholder — Name on the card
- Country — Card issuing country
- Provider — Which of your providers processed it
- Created — When the payment was initiated
- Updated — Last status change timestamp
Expanded Details
Clicking a transaction reveals:
- Provider Payment ID — The provider's
pi_xxxidentifier - External ID — Client's order reference (hidden from Relays for privacy)
- IP Address — Customer's IP (encrypted at rest)
- Fee Breakdown — Static fee + percentage breakdown
- Send Amount — Amount to be settled to Client
- Raw Log — Full provider API response (encrypted at rest, decrypted for display)
- Wallet Addresses — Relay and Client Solana wallet addresses
- Transaction Hash — Solana transaction signature for settlement
Filtering
Filter transactions by:
- Status — COMPLETED, FAILED, CRASH, or all
- Payment ID — Search by internal UUID or provider
pi_xxxID - Card — Last 4 digits
- Country — ISO country code
- Cardholder — Name search
- Amount range — Min and max amount
- Date range — Start and end date
- Provider — Specific provider
- Client ID — Filter by client
Encrypted fields (card number, cardholder, country) are decrypted server-side for filtering. Searches on these fields may fetch more records internally to ensure accurate results.