arc_ref_... reference and a hosted checkout URL you can redirect your customer to or share as a payment link. The session stays open for 120 minutes before expiring. Both merchant API keys and consumer session tokens are accepted, and if you are wiring up an autonomous agent you can pass its on-chain scaAddress to associate the payment with a registered ERC-8004 identity.
Endpoint
Request
Headers
Body Parameters
string
required
Payment amount denominated in USDC, expressed as a decimal string (e.g.
"25.00", "0.500000"). USDC supports up to 6 decimal places of precision. Do not pass raw atomic units — pass the human-readable value.string
default:"USDC"
Currency code for the payment. Defaults to
"USDC". This field is recorded on the ledger and surfaced in receipts and dashboard exports; it does not alter the on-chain token.string
Display name shown to the payer on the hosted checkout page (e.g.
"Acme Corp"). For merchant-type API keys this value is ignored — FlareHQ always resolves the business name server-side from your verified merchant record to prevent spoofing. For consumer and internal callers the value you supply here is used as-is.string
Payer email address used for sending a payment receipt. Optional — if omitted no receipt email is sent. For agent-initiated payments this field defaults to
autonomous-agent@arc.network unless you provide a value.string
HTTPS URL that FlareHQ will
POST to when the payment status changes (e.g. payment.completed, payment.failed). The webhook body mirrors the response from GET /api/payments/verify/. Must be publicly reachable.string
default:"send"
Flow direction for consumer-originated payments. Accepted values:
"send"— the authenticated consumer is the payer sending USDC to a recipient."request"— the authenticated consumer is requesting USDC from someone else; the payer is determined at checkout.
string
The on-chain Smart Contract Account (SCA) address of the autonomous agent initiating the payment. When provided, FlareHQ verifies that the agent is registered. If no matching agent is found the request is rejected with
HTTP 404. On success the agent object in the response will be populated with the agent’s identity metadata.The agent must be deployed and registered before use. Deploy a new agent via
POST /api/agent/deploy.string
Recipient wallet address for consumer
"send" flows. Must be a valid EVM 0x... address. Ignored for merchant API key callers (the payout address is resolved from your verified merchant wallet record) and for "request" direction flows.Response
boolean
true on a successful initialization.string
Human-readable confirmation —
"Payment initialized successfully.".string
Unique payment reference identifier with the prefix
arc_ref_. Store this value — you will use it to verify the payment status and correlate webhook events.Example: "arc_ref_k7x2m9lp4d8f1q2z"string
Fully-qualified URL to the FlareHQ hosted checkout page for this session. Redirect your customer here or embed it in a payment link.Example:
"https://flarehq.xyz/checkout/arc_ref_k7x2m9lp4d8f1q2z"object
Summary of the initialized payment session.
object | null
Populated when
agentSCA was provided and the agent was found in the registry. null for all non-agent payments.Examples
Success Response
Agent Payment Success Response
Error Responses
Notes
Payment sessions expire 120 minutes after creation. After expiry the session transitions to
EXPIRED status and the checkout URL becomes inactive. Initialize a fresh session if you need to retry.
