Get secure payment data by token
Retrieves secure payment display data and resolved destination info. The token must be valid, not expired, and the payment must be in ‘pending’ status.
Headers
Client ID for frontend authentication
Origin header (automatically set by browser)
Path Parameters
Secure payment token (ULID) returned by POST /v2/secure-payments, POST /v2/secure-payments/payouts, or POST /v2/secure-payments/multicall-payouts. Distinct from the token query parameter, which selects the crosschain source currency.
Query Parameters
The source token of the crosschain payment. Pair with chain; both must be sent together. Not the secure payment token — that is the {token} path parameter.
USDC, USDT, EURC, USDT0 The wallet address of the payer (optional, used to check existing approvals)
The source chain of the crosschain payment
BASE, OPTIMISM, ARBITRUM, ETHEREUM, POLYGON, BNB The EOA wallet address that holds the funds. When provided, balance checks and LiFi quotes use this address while the wallet param is used for calldata building (smart account flow).
When true, prepares calldata for a Gnosis Safe multisig payer (wallet must be the Safe address). Mutually exclusive with eoaWallet.
true, false Response
Secure payment data retrieved successfully
- Option 1
- Option 2
- Option 3
- Option 4
Type of payment: single or batch
single pending, completed, expired, invalidated, compliance_failed Optional redirect URL configured at creation time. Null when no redirect was set.
Optional label describing the redirect destination. Null when no label was provided.
Request Network request IDs represented by this payment
Payee wallet address
Blockchain network
Payment amount
Payment currency ID
Whether the payment currency is the native currency (e.g., ETH)
Resolved destination for this payment, or null when the payment is not linked to a stored destination (e.g., payouts created from raw recipient details).
Merchant reference for the payment
Fee plan snapshot captured at creation time. Null when fees don't apply (non-stablecoin currency, payment created before fee plan rollout, etc.).
Orchestrator ID associated with the secure payment, if any
Vendor-neutral analytics metadata that SPP maps into Mixpanel shared properties. Amount values are decimal USD strings to avoid frontend precision loss.
Whether payee-address fields are intentionally masked until access is approved