Authorization header.
GET /api/x402/seller/balance
Retrieve your current USDC earnings split across two buckets: your Gateway balance (payments collected but not yet withdrawn) and your on-chain wallet balance (funds already withdrawn to your EOA or SCA).GET https://flarehq.xyz/api/x402/seller/balance
Query Parameters
string
The seller wallet address to inspect. Defaults to the address linked to your merchant account if omitted.
Response
object
Your on-chain USDC wallet state, read directly from the Arc testnet USDC contract (
0x3600000000000000000000000000000000000000).object
Your Circle Gateway balance — x402 payments collected but not yet withdrawn.
Example
Response
POST /api/x402/seller/balance/withdraw
Withdraw your accumulated Gateway earnings to a wallet address. Supports same-chain Arc testnet withdrawals (instant) and cross-chain withdrawals to supported destination chains via Circle’s bridging infrastructure.POST https://flarehq.xyz/api/x402/seller/balance/withdraw
Body Parameters
string
required
Amount of USDC to withdraw, as a decimal string (e.g.
"10.5"). The value must not exceed your gateway.withdrawable balance.string
Target chain for the withdrawal. Defaults to
"arcTestnet" for a same-chain transfer. Pass another supported Circle chain identifier for cross-chain bridging.string
Recipient wallet address on the destination chain. Defaults to the seller address tied to your API key if omitted.
Response
boolean
true when the withdrawal transaction was confirmed on-chain.string
Arc testnet transaction hash for the withdrawal.
string
Human-readable USDC amount that was withdrawn (e.g.
"10.500000").string
The chain from which funds were withdrawn (always
arcTestnet for the Gateway).string
The chain where funds were sent.
string
The address that received the withdrawal.
string
Confirmation state. Returns
"confirmed" on success.string
Direct link to the transaction on ArcScan (e.g.
https://testnet.arcscan.app/tx/0x...).Example
Response
POST /api/x402/verify
Verify a buyer’s payment proof server-side without executing the upstream proxy call. Use this when you want to gate access to your own infrastructure and handle the upstream request yourself, rather than letting FlareHQ proxy it.POST https://flarehq.xyz/api/x402/verify
Body Parameters
string
required
The
X-402-Payment-Proof value sent by the buyer. This is the same Circle Nanopayment authorization proof used in /api/x402/pay.Response
boolean
true when the proof was successfully validated.boolean
true if the payment settled successfully on Arc testnet. false if the proof is expired, malformed, or references an insufficient amount.string
The USDC amount covered by this proof, as a decimal string.
string
On-chain address of the buyer who generated the proof.
number
Unix timestamp (seconds) when the proof was issued. Proofs are time-bounded — reject any proof where
timestamp is more than 60 seconds in the past.Example
Response (valid proof)
Response (invalid proof)
Use
/api/x402/verify when you self-host your upstream API and want to check payment before responding — without routing traffic through FlareHQ. Use /api/x402/pay when you want FlareHQ to both verify and proxy the upstream call in one step.
