Create an Offloader Wallet to give a customer a dedicated on-chain address tied to a specific bank account. Any stablecoin sent to that address is automatically converted to the linked fiat currency and forwarded — no per-transfer API call required. Each customer should have their own wallet; sharing an address across customers makes deposit attribution unreliable.Documentation Index
Fetch the complete documentation index at: https://docs.spherepay.co/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Authentication
All requests must include a Bearer token in theAuthorization header.
Request parameters
The ID of the customer who owns the destination bank account.
The stablecoin the wallet accepts for deposits.Accepted values:
"usdc" | "usdt" | "eurc"The blockchain network the wallet is deployed on.Accepted values:
"sol" | "ethereum" | "arbitrum" | "polygon" | "base" | "avalanche" | "tron"The bank account destination where converted funds are sent. The shape of this object depends on the payout rail.
Your integrator fee in basis points. Accepted range: 0–1000.
On-chain address to return funds to if a transfer fails. Must be valid for the selected
network.Response fields
Unique identifier for the offloader wallet.
The ID of the customer who owns this wallet.
The on-chain wallet address where the customer sends stablecoins.
The stablecoin this wallet accepts (e.g.,
"usdc").The blockchain network this wallet is deployed on (e.g.,
"ethereum").The bank account destination configuration, including
bankAccountId, currency, network, and any rail-specific reference field.The on-chain address used for returning funds on failed transactions.
ISO 8601 timestamp of when the wallet was created.
ISO 8601 timestamp of the last update to the wallet.

