Getting Started
FurlPay services and developer docs
Build stablecoin payment and agent workflows with FurlPay's APIs, SDKs and wallet security tools. This page separates production services from integrations that are still being prepared.
Check availability before handling money
GET /api/rails before building a live flow. If that endpoint cannot return a current status, treat the rail as unavailable until its status can be verified. A quote, challenge or payment intent is not proof that funds moved.Services and current availability
Status labels come from FurlPay's production capability registry. Live means observed working in production; In development means the flow is implemented but a production gate remains; Planned means the production service is not implemented. Most configuration observations were recorded on 21 September 2026. On 11 October 2026,/api/rails returned 503 controls_unavailable with reason plan_limit, and /api/x402/fx also returned 503. Treat all payment rail status as unknown until the registry responds successfully; these labels are not a current availability guarantee.
Developer APIs, SDKs and documentation
LiveREST APIs, SDKs, OpenAPI docs and MCP connectivity; each money-moving route still depends on rail availability.
Start here →Passkey authentication
LiveWebAuthn sign-in and step-up authentication for protected account actions.
Authentication guide →Stablecoin payment APIs
LiveFee estimates and non-custodial payment or bridge data for a user's wallet to review and sign. This does not mean FurlPay has settled the payment.
API routes →FurlPay-operated settlement
In developmentBroadcasting a signed payment through a FurlPay-operated production signer.
Current gate: No production signer, fee payer or Arbitrum RPC endpoint is configured, and rail controls must be readable.
Check rail status →Merchant payment links, invoices and hosted checkout
In developmentUSDC collection from a payer's own wallet, marked paid only after on-chain verification. Needs provisioned destinations and the payment migration.
Current gate: Deploy the merchant payment release, apply migrations 0040 to 0047, and register collection addresses through a custody provider; none is integrated.
Merchant payments guide →Contractor payroll
In developmentA contractor roster and wallet-signed USDC pay runs. FurlPay prepares and verifies; the employer's wallet pays.
Current gate: A reviewed and deployed router per network, and migrations 0042, 0044 and 0048.
Payroll guide →Settlement workspace and business onboarding
In developmentA business console with onboarding, document review and screening. Records saved in the workspace are drafts and do not move money.
Current gate: Record an authenticated production check of the workspace and onboarding storage, with an identity provider configured and a compliance officer granted.
Workspace guide →Circle user-controlled wallets
In developmentWallets the user controls with a PIN or biometric in Circle's SDK. FurlPay holds no key share.
Current gate: Circle Wallets production credentials and an observed completed wallet-creation challenge.
Circle integration →Telegram Mini App
In developmentSign in to an existing account from Telegram and view balances and activity. It cannot send a payment.
Current gate: Restore key-value store availability, then confirm sign-in end to end with migration 0050 applied.
Telegram guide →Buying and selling crypto
PlannedProvider adapters exist, but FurlPay does not operate an on-ramp or off-ramp and no provider is live.
Ramp provider status →x402 payment challenges
In developmentThe endpoint currently returns 503 because operational controls are unavailable. Challenge service and settlement must both be checked separately.
Current gate: Restore operational-control availability; the x402 endpoint must return a current challenge before it is advertised as available.
x402 guide →x402 and MPP settlement
In developmentThe agent payment protocols have separate settlement gates; do not treat an issued challenge as a completed payment.
Current gate: A production facilitator signer, Arbitrum RPC endpoint and readable operational controls are required.
x402 and MPP guide →AI agent access and payment execution
In developmentMCP connectivity, scoped access and spend policies are available; FurlPay agent payment settlement is pending production rail configuration.
Current gate: Blocked on x402 settlement.
Agent guide →Gasless USDC transfers
In developmentA relayed EIP-3009 transfer flow; production sponsorship is not enabled until its rail is configured.
Current gate: The relayer fee payer is not configured or funded in production.
Transfer status →Market data
LiveMarket quotes, charts and related read-only data. Brokerage execution is a separate service.
Open markets →Hotel discovery
LiveHotel search and map discovery. Finding a property does not mean a booking or payment can be completed.
Explore hotels →Travel booking
In developmentProduction booking inventory and payment are not currently available.
Current gate: The production flight and stay inventory provider is on a test credential, which the code refuses to use in production.
Travel integration status →Stock and ETF orders
In developmentOrder submission is not currently routed to a live brokerage.
Current gate: The brokerage flag is off pending a live brokerage agreement; enabling it also requires the AI_TRADING_LIVE review.
Investing product status →Card issuing
PlannedNo production card program is available.
Card availability →Local bank accounts and banking rails
PlannedFurlPay does not currently provide local account issuance or bank payouts.
Funding availability →FurlPay mobile apps
In developmentMobile clients are not currently distributed through the app stores.
Current gate: Store review and, for Android, the Play App Signing fingerprint.
Passkey and device guidance →FurlPay desktop app
In developmentA signed desktop release is not currently available to users.
Current gate: Code signing and a published release channel.
Repository layout →Tokenized equities
PlannedA verified production token registry and trading path are not available.
Investing product status →Payment rails
The API includes non-custodial transaction-building and payment protocol integrations. The payer signs with their own wallet where a route is client-signed. FurlPay-operated relaying is a separate capability and is currently in development. Individual rails can be paused, unconfigured or unavailable; read their current status and the linked route guide before sending a transaction.
- USDC payment APIs: fee estimates, payment intents and signing data for supported flows.
- Agent protocols: x402 and MPP challenge flows; the x402 endpoint is currently unavailable and settlement readiness is separate.
- Cross-chain tools: Circle CCTP and LI.FI route construction, subject to rail status.
- Solana Actions: transaction construction for supported checkout assets.
Agent and developer services
FurlPay also provides an MCP endpoint, agent key and spend-policy management, passkey authentication, developer documentation and typed SDKs. Connector tools may read data or prepare an action; financial settlement remains subject to the user's authorization and the live status of the selected rail.
- For AI agents — MCP, agent access and spend controls.
- Claude connector — scoped access and human approval for financial actions.
- Authentication — sessions, WebAuthn and API access patterns.
- OpenAPI specification — machine-readable route contracts.
- Configuration and setup — credentials, flags, migrations and scheduled jobs.
- Screening and cases — address screening, monitoring rules and case management.
Services not available as live products
FurlPay does not currently offer production card issuing, local bank account issuance, fiat on-ramp or off-ramp payouts, or live stock and ETF order execution. Travel booking is also not available with production inventory. Related pages describe integration designs or development work; they are not offers to provide those services today.
FurlPay is a software and payment-infrastructure provider, not a bank, card issuer, brokerage or investment adviser. Availability, supported assets, networks and limits are deployment-specific.
Next: verify a rail and request a quote