Financial infrastructure
Accept stablecoins, move money, and build on production payment APIs — all through one interface. Agent payments, card issuing and global accounts are in development.
View docsApps
The web app is live today. Mobile and desktop clients are built and in final testing — when they ship they will share one account, one balance and one set of spending controls, on the same API surface your integration talks to.
Mobile apps — coming soon
Integrated rails, stablecoins & networks
What can you build
One integration covers payment construction, balances and agent access today, with acceptance, card issuing and settlement in development. What you assemble is up to you.
Financial infrastructure
Move money, issue products, hold balances, automate the whole thing. Each one is a documented API surface, not a bundle you have to take whole.
Move money
Payments that settle in seconds
Issue financial products
Cards with controls in the rail
Build accounts
Balances your users actually own
Automate finance
Money under program control
AI agents
Give autonomous software access to programmable financial infrastructure — with permissions, limits and policies built in.
An agent key is not an account key. It carries its own policy — per-transaction and daily caps, allowed counterparties, velocity limits — evaluated before anything moves. Money-moving tool calls return an approval URL instead of a result: the model proposes, a human with a passkey disposes.
AI agent
01Your model, framework or workflow
Agent wallet
02Its own key — never the account's
Policy engine
03Per-agent caps, allowlists, velocity
Human approval
04Passkey confirmation before funds move
USDC payment
05EIP-3009 authorization, settled on-chain
Merchant or API
06Paid per call over HTTP 402
Settlement
07Receipt, ledger entry, audit record
Policy and approval are evaluated before settlement, never after.
API
Five surfaces, one client. The Agents tab runs a real, unauthenticated request against this deployment — the rest show documented response shapes.
import { Furlpay } from '@furlpay/furlpay-node';
const furlpay = new Furlpay(process.env.FURLPAY_API_KEY);
const payment = await furlpay.payments.create({
amount: '100.00',
currency: 'USDC',
chain: 'arbitrum',
recipient: 'merchant@example.com'
});{
"id": "pay_3f81c2",
"status": "settled",
"amount": "100.00",
"currency": "USDC",
"chain": "arbitrum",
"recipient": "merchant@example.com",
"settlementTx": "0x9c4a…d21f"
}Production
The interesting question about payment infrastructure is not what it does when everything works. These are the behaviours under failure, and where to check them.
Fails closed, loudly
An upstream error returns an error. The bank directory answers 502 rather than an empty list; the durable store refuses its in-memory fallback in production instead of silently forgetting writes.
lib/hkma.ts · lib/kv.tsAuth posture enforced in CI
Every route's authentication class is declared in a manifest and checked on every build, so a handler cannot quietly become public.
security/route-manifest.json · scripts/check-route-security.mjsReplay-protected webhooks
Signatures are verified over the raw body with a constant-time compare, and stale timestamps are rejected. Delivery is idempotent by key.
/docs/architecture/webhooks · lib/idempotency.tsProbes with hard timeouts
Dependency health is a real round-trip per component with a bounded timeout and a 30-second cache — never a status constant someone forgot to update.
/api/ops/healthRail status
GET /api/railsRead live from this deployment when the page loaded. A rail without production credentials reports “not configured” rather than a green light.
Security
Five controls that are implemented, each naming the module that implements it. No certification badges appear on this page, because none have been attested.
Authentication
WebAuthn passkeys, with a step-up challenge required before money moves. Phishing-resistant by construction — there is no password to hand over.
lib/webauthn.tsTransaction controls
Per-transaction caps live in the rail registry, not in a caller's request. A payload cannot ask to exceed its own limit.
lib/rails/registry.ts · lib/moneyLimits.tsSpending limits for agents
Every agent key carries its own policy — amount, counterparty and velocity — evaluated before settlement, with human approval on money-moving calls.
lib/agentPolicy.tsKey custody
Three independent policy gates — client, server, and enclave — must each approve before anything is signed.
lib/custody.tsAudit logs
Money movement writes an audit record, and a failed or dropped write is surfaced as degraded rather than counted silently — a hole in the trail is still a hole.
lib/audit.ts · lib/auditDb.tsProvenance
Each capability below names the route or module that implements it, so any claim on this page can be checked rather than taken on trust.
Owned agent keys with enforced per-agent policies. Money-moving tools return an approval URL requiring human passkey confirmation — the model proposes, the human disposes.
/api/agents/keys · lib/agentPolicy.ts · lib/mcp/tools.tsModel Context Protocol server exposing tools, resources and prompts over JSON-RPC, with OAuth 2.1 and DPoP-bound tokens. This is the transport and authorization layer; it is live and callable. Paying for a resource over it is x402, which is not — see below.
/api/mcp · lib/mcp/oauth.ts · lib/mcp/dpop.tsLive branch and ATM data covering 20 licensed banks, published by the Hong Kong Monetary Authority. Fails closed: an upstream error returns 502, never an empty list.
/api/banking/directory · lib/hkma.tsSplits, dividends with withholding and DRIP, mergers, spin-offs and delistings. Projection is pure and cannot credit cash; settlement is a separate, idempotent step.
lib/corporateActions/ · lib/ledger.tsOne descriptor per payment rail — protocol, chains, asset, fee model, per-transaction cap — merged with live operational status. Execution paths stay independent by design.
/api/rails · lib/rails/registry.tsWebAuthn authentication with step-up challenges on money movement, and a route manifest enforcing the auth posture of every endpoint in CI.
lib/webauthn.ts · security/route-manifest.jsonWritten and typechecked, but not yet run against a live counterparty. Listed separately rather than blended into the section above.
Route and provider integration are written. Pending: a provisioned VASP account and a verified live message exchange.
/api/compliance/travel-ruleProvider comparison data is in place. Pending: production credentials and a signed agreement per institution. The previous HSBC sandbox client was deleted on 23 Jul 2026 — its endpoints returned API Gateway's unmatched-route error, so it described connections that did not exist.
components/banking/BankingHub.tsx (comparison data only)Settlement is proven end-to-end in a local environment with real on-chain transfers. Pending: production fee-payer and RPC configuration.
docs/GO-LIVE-MONEY.mdHTTP 402 payment-required flow with EIP-3009 authorization, facilitator verify/settle, and policy evaluation before funds move. Pending: production facilitator configuration — /api/rails currently reports these rails as not configured, so agents cannot pay through them yet.
/api/x402/facilitator/settle · lib/x402Settler.ts · /api/railsEIP-3009 transferWithAuthorization with a relayer that submits and pays gas on the sender's behalf. Pending: a funded production fee payer — /api/rails reports this rail as not configured.
/api/transfers/gasless · /api/railsProof
No testimonials on this page — there are none to quote yet. Instead, the things you can clone, install and read.
First-party SDKs
One client per language, generated against the same REST surface.
@furlpay/furlpay-nodefurlpaygithub.com/furlpay/furlpay-gofurlpayAgent framework adapters
Drop-in tools so an agent can pay from inside the framework you already use.
Eight framework adapters, each a published package rather than a logo on a page.
Read the source
The claims on this page name the file that backs them. The repository is public, so you can check any of them without asking us.
Why FurlPay
Traditional financial APIs do accounts and cards. Crypto APIs do stablecoins. Building a product that needs both usually means integrating both, and then reconciling them.
| Capability | FurlPay | Traditional financial APIs | Crypto-only APIs |
|---|---|---|---|
| Stablecoin payment APIs | Yes | Partial | Yes |
| Passkey-first security | Yes | Partial | No |
| Programmable payments | Yes | Partial | Yes |
| AI agent payments | In development | No | Partial |
| Crypto checkout | In development | No | Yes |
| Global accounts | In development | Yes | No |
| Cards | In development | Yes | Partial |
| One API for all of it | In development | No | No |
Compares product categories, not named vendors — individual products vary, and several are adding capabilities. “Partial” means the category is mixed rather than absent. “Soon” in the FurlPay column means built but not yet available in production — see what is actually running.
Pricing
Every line in every tier names something that exists today.
$0/mo
For startups & AI agent sandbox testing
Free to start. No payment required.
Create your account and start building.
$299/mo
$299 billed monthly
For platforms, neobanks & travel OTAs
Payment methods are currently unavailable. You can review the plan at checkout; no payment will be taken.
Custom
For high-volume merchants & platforms
A plan built around your business.
Talk with our team about pricing and your integration.
Resources
Stablecoin payment APIs, a passkey wallet and AI agent infrastructure — all through one API. Accounts, cards and agent settlement are in development.
TypeScriptPythonGoRustREST APIWebhooks
Product launches, engineering deep-dives, and a weekly digest you can actually skim. Unsubscribe anytime.
Want to pick specific topics? Manage preferences