Get secure payment calldata by token
Retrieves executable payment calldata for a secure payment token. When chain and token are provided, the backend prepares a crosschain payment for the selected source asset; otherwise it returns the existing same-chain or batch payment calldata.
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)
"0x6923831ACf5c327260D7ac7C9DfF5b1c3cB3C7D7"
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 calldata retrieved successfully
- Option 1
- Option 2
- Option 3
single Flat ordered list of calls the smart account must execute atomically. Main-payment transactions come first; fee-payment transactions follow.
Fee bundle summary for this payment. Null when no fee plan applies.