Skip to main content
GET
Get secure payment calldata by token

Headers

x-client-id
string
required

Client ID for frontend authentication

Origin
string
required

Origin header (automatically set by browser)

Path Parameters

token
string
required

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

token
enum<string>

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.

Available options:
USDC,
USDT,
EURC,
USDT0
wallet
string

The wallet address of the payer (optional, used to check existing approvals)

Example:

"0x6923831ACf5c327260D7ac7C9DfF5b1c3cB3C7D7"

chain
enum<string>

The source chain of the crosschain payment

Available options:
BASE,
OPTIMISM,
ARBITRUM,
ETHEREUM,
POLYGON,
BNB
eoaWallet
string

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).

isSafe
enum<string>

When true, prepares calldata for a Gnosis Safe multisig payer (wallet must be the Safe address). Mutually exclusive with eoaWallet.

Available options:
true,
false

Response

Secure payment calldata retrieved successfully

paymentType
enum<string>
required
Available options:
single
transactions
any[]
required

Flat ordered list of calls the smart account must execute atomically. Main-payment transactions come first; fee-payment transactions follow.

feeBundle
object | null
required

Fee bundle summary for this payment. Null when no fee plan applies.

metadata
object
required
eoaApprovalTransactions
any[]