Financial infrastructure

The financial infrastructure for apps, agents, and the internet economy.

Move money, issue cards, open global accounts, accept stablecoins, and let AI agents pay — all through one API.

TypeScriptPythonGoRustREST APIWebhooks

Apps

The same rails, in your pocket.

Mobile, desktop and web share one account, one balance and one set of spending controls — the same API surface your integration talks to.

Get it onGoogle Play Download on theApp Store

Desktop:Windows .msi macOS .dmg Linux .deb

FurlPay Wallet

AUGUST / 2026

@yourname

IDENTITYACCOUNT & AGENT

ONE OF ONEyourname.furlpay.com

Get your card today

Reserve a handle your account and its agents present when they pay. Free to reserve.

Integrated rails, stablecoins & networks

StripeWiseAlpacaMarqetaPersonaSardineSafeTurnkeyUSDCEURCBaseSolanaArbitrum

What can you build

Build the financial layer of your product.

One integration covers payment acceptance, account balances, card issuing and settlement. What you assemble from those is up to you.

AI agents

Give an autonomous agent its own wallet, a spending policy it cannot exceed, and the ability to pay per API call over x402 — with human approval required before money moves.

Agent infrastructure

Global fintech

Accounts, balances, cards and FX behind one API.

Fintech stack

Travel

Stays and flights paid in stablecoins, settled on-chain.

Travel payments

Marketplaces

Take payment, split it, and pay sellers out in USDC.

Marketplace payouts

Creator platforms

Programmable payouts and rewards, without card rails.

Creator payouts

Financial infrastructure

Four primitives. Everything else is composition.

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

Stablecoin paymentsUSDC over x402 and direct transfer
TransfersGasless EIP-3009, fees quoted in USDC
PayoutsPay many recipients from one balance
FXMid-market quotes, priced per call

Explore move money

Issue financial products

Cards with controls in the rail

Virtual cardsIssued programmatically
Physical cardsSame controls, same ledger
Spending controlsPer-purchase and daily caps
Policy engineRules evaluated before authorization

Explore issue financial products

Build accounts

Balances your users actually own

Global accountsOne handle, many chains
WalletsNon-custodial, 2-of-2 MPC
BalancesMulti-asset, multi-chain
Lot ledgerCost basis and corporate actions

Explore build accounts

Automate finance

Money under program control

AI agentsOwned keys with enforced policies
x402HTTP 402 pay-per-call settlement
Programmable paymentsConditions before funds move
WebhooksSigned, replay-protected delivery

Explore automate finance

AI agents

Give AI agents the ability to transact.

Give autonomous software access to programmable financial infrastructure — with permissions, limits and policies built in.

Agent walletsSpending limitsHuman approvalProgrammable paymentsx402

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.

Agent infrastructure Read the x402 guide

AI agent
01
Your model, framework or workflow
Agent wallet
02
Its own key — never the account's
Policy engine
03
Per-agent caps, allowlists, velocity
Human approval
04
Passkey confirmation before funds move
USDC payment
05
EIP-3009 authorization, settled on-chain
Merchant or API
06
Paid per call over HTTP 402
Settlement
07
Receipt, ledger entry, audit record

Policy and approval are evaluated before settlement, never after.

API

Read it once, integrate it once.

Read the docs →

Five surfaces, one client. The Agents tab runs a real, unauthenticated request against this deployment — the rest show documented response shapes.

payment.ts

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'
});

example responseOpen in docs

{
  "id": "pay_3f81c2",
  "status": "settled",
  "amount": "100.00",
  "currency": "USDC",
  "chain": "arbitrum",
  "recipient": "merchant@example.com",
  "settlementTx": "0x9c4a…d21f"
}

Production

Built for 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.ts

Auth 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.mjs

Replay-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.ts

Probes 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/health

Rail status

GET /api/rails

Read live from this deployment when the page loaded. A rail without production credentials reports “not configured” rather than a green light.

Full status board

Security

Built for money. Designed for 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.ts

Transaction 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.ts

Spending 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.ts

Key custody

2-of-2 MPC with an HSM policy co-signer: no single key that can move funds ever exists in one place.

lib/custody.ts

Audit 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.ts

Trust & security centre

Threat model, disclosure policy, and what is and is not covered today.

Read the detail

Provenance

What is actually running

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.

Live

Agent spend control plane
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.ts
x402 settlement
HTTP 402 payment-required flow with EIP-3009 authorization, facilitator verify/settle, and policy evaluation before funds move.
/api/x402/facilitator/settle · lib/x402Settler.ts
MCP server for autonomous agents
Model Context Protocol server exposing tools, resources and prompts over JSON-RPC, with OAuth 2.1 and DPoP-bound tokens.
/api/mcp · lib/mcp/oauth.ts · lib/mcp/dpop.ts
Hong Kong bank directory
Live 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.ts
Corporate actions ledger
Splits, 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.ts
Rail registry
One 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.ts
Passkey-first security
WebAuthn 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.json

Built, not yet exercised

Written and typechecked, but not yet run against a live counterparty. Listed separately rather than blended into the section above.

Travel Rule messaging
Route and provider integration are written. Pending: a provisioned VASP account and a verified live message exchange.
/api/compliance/travel-rule
Bank API connectors
Provider 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)
Production settlement
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.md

Proof

Built by developers. Built for production.

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.

TypeScript@furlpay/furlpay-node
Pythonfurlpay
Gogithub.com/furlpay/furlpay-go
Rustfurlpay

Agent framework adapters

Drop-in tools so an agent can pay from inside the framework you already use.

LangChain
LlamaIndex
CrewAI
PydanticAI
OpenAI Agents
Vercel AI SDK
Mastra
MCP

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.

GitHub repository What shipped recently →

Why FurlPay

One API where you would otherwise need three.

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 comparison between FurlPay, traditional financial APIs and crypto-only APIs
Capability	FurlPay	Traditional financial APIs	Crypto-only APIs
Stablecoin payments	Yes	Partial	Yes
Global accounts	Yes	Yes	No
Cards	Yes	Yes	Partial
AI agent payments	Yes	No	Partial
Crypto checkout	Yes	No	Yes
Programmable payments	Yes	Partial	Yes
One API for all of it	Yes	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.

Pricing

Start free. Pay when you move money.

Every line in every tier names something that exists today.

Developer Core

$0/mo

For startups & AI agent sandbox testing

Full REST & MCP server API access
OAuth 2.1 with DPoP sender-constrained tokens
x402 pay-per-call settlement for AI agents
Passkey (WebAuthn) authentication
Community support

Start Building

Growth Orchestrator

POPULAR

$299/mo

For platforms, neobanks & travel OTAs

Agent spend control plane with enforced per-agent policies
Human passkey approval on every money-moving tool call
Rail registry: protocol, chains, fees and per-transaction caps
Corporate-actions ledger — splits, dividends, mergers, spin-offs
Hong Kong bank directory: 20 licensed banks, HKMA open data

Start Building

Enterprise & BaaS

Custom

For high-volume merchants & platforms

Custom settlement rates below the standard 0.5%
Settlement and uptime SLA
Per-transaction audit trails with reconciliation exports
Auth posture of every endpoint enforced in CI
Dedicated account manager

Contact Enterprise

Resources

Everything you need to ship.

Documentation

Concepts, guides, quickstarts

API reference

Every route and payload

SDKs

TypeScript, Python, Go, Rust

GitHub

Source, issues, releases

Changelog

What shipped, when

Status

System status board

Examples

Apps built on FurlPay

Webhooks

Signed event delivery

Build the financial layer of your product.

Payments, accounts, cards, stablecoins and AI agent infrastructure — all through one API.

Get your API key Talk to engineering

TypeScriptPythonGoRustREST APIWebhooks

Updates worth reading, from a team that ships.

Product launches, engineering deep-dives, and a weekly digest you can actually skim. Unsubscribe anytime.

Want to pick specific topics? Manage preferences

Give AI agents the ability to transact.

Give autonomous software access to programmable financial infrastructure — with permissions, limits and policies built in.

Agent walletsSpending limitsHuman approvalProgrammable paymentsx402

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' });

Built for 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.ts

Auth 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.mjs

Replay-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.ts

Probes 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/health

What is actually running

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.

Live

Agent spend control plane

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.ts

x402 settlement

HTTP 402 payment-required flow with EIP-3009 authorization, facilitator verify/settle, and policy evaluation before funds move.

/api/x402/facilitator/settle · lib/x402Settler.ts

MCP server for autonomous agents

Model Context Protocol server exposing tools, resources and prompts over JSON-RPC, with OAuth 2.1 and DPoP-bound tokens.

/api/mcp · lib/mcp/oauth.ts · lib/mcp/dpop.ts

Hong Kong bank directory

Live 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.ts

Corporate actions ledger

Splits, 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.ts

Rail registry

One 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.ts

Passkey-first security

WebAuthn 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.json

Built, not yet exercised

Written and typechecked, but not yet run against a live counterparty. Listed separately rather than blended into the section above.

Travel Rule messaging

Route and provider integration are written. Pending: a provisioned VASP account and a verified live message exchange.

/api/compliance/travel-rule

Bank API connectors

Provider 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)

Production settlement

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.md

Capability

FurlPay

Traditional financial APIs

Crypto-only APIs

Stablecoin payments

Global accounts

Cards

AI agent payments

Crypto checkout

Programmable payments

One API for all of it