Transaction amounts are stored in the token’s smallest unit (e.g., 6 decimals for USDC). The
amount_usd field provides the USD equivalent at the time of the transaction.The Transaction object
Unique identifier for the transaction (e.g.,
tx_abc123).Current status of the transaction. One of:
pending, confirming, completed, failed.Transaction amount in the token’s smallest unit.
USD equivalent of the transaction amount at the time of payment.
Contract address of the received token.
Chain ID where the payment was received.
On-chain transaction hash. Null while
pending.Wallet address of the payer.
Wallet address that received the payment.
Associated customer ID, if the payer is a known customer.
Payment link that originated this transaction.
Checkout session that originated this transaction.
If the payer paid from a different chain, this is the chain they paid from.
If the payer paid with a different token, this is the token they paid with.
The amount the payer sent (before swap/bridge), in the source token’s smallest unit.
Platform fee amount in the received token’s smallest unit.
Custom form data submitted by the customer during checkout.
Shipping address provided by the customer.
Selected shipping option.
Metadata from the checkout session.
ISO 8601 timestamp when the transaction was initiated.
ISO 8601 timestamp when the transaction reached
confirming status.ISO 8601 timestamp when the transaction reached
completed status.Transaction statuses
| Status | Description |
|---|---|
pending | Transaction initiated, waiting for on-chain submission. |
confirming | Transaction submitted on-chain, waiting for block confirmations. |
completed | Transaction confirmed and payment received by the recipient. |
failed | Transaction failed due to revert, timeout, or insufficient funds. |
List transactions
Retrieve a paginated list of transactions with optional filters.Filter by status:
pending, confirming, completed, failed.Filter by customer ID.
Filter by payment link ID.
Filter transactions created on or after this ISO 8601 date (e.g.,
2026-01-01).Filter transactions created on or before this ISO 8601 date (e.g.,
2026-02-28).Page number for pagination.
Number of results per page (max 100).
- Response
Retrieve a transaction
The transaction ID (e.g.,
tx_abc123).- Response
Returns the full Transaction object.
Get transaction stats
Retrieve aggregate statistics across all your transactions.- Response
Export transactions
Export transaction data in CSV or JSON format. The response is streamed as a file download.Export format. One of:
csv, json.Filter by status:
pending, confirming, completed, failed.Filter transactions created on or after this ISO 8601 date.
Filter transactions created on or before this ISO 8601 date.
Exports are limited to 50,000 records. For larger datasets, use date range filters to break exports into smaller chunks.
- CSV Response
- JSON Response
HypeDuel