FurlPay Docs
Open App
  • Services & Availability
  • Quickstart
  • For AI Agents
  • Monorepo
  • API Routes
  • Authenticationupdated
  • Webhook Eventsupdated
  • Error Codesupdated
  • Rate Limitsnew
  • Configuration & Setupnew
  • Merchant Paymentsnew
  • Payroll & Payoutsnew
  • Agentic Payments (x402)updated
  • Agent Trust & Mandates (TAP)updated
  • CCTP Cross-Chainupdated
  • LI.FI Swapsupdated
  • FurlPay Travels (Travel MCP)updated
  • Solana Actions & Blinks
  • Settlement Workspacenew
  • FURL Tokennew
  • Claude Connectorupdated
  • AI Assistants
  • Circlenew
  • Ramp Providersnew
  • Telegram Mini Appnew
  • Stripe Crypto
  • Persona KYC
  • Regulatory status
  • Screening & Casesnew
  • Security Postureupdated
  • Signing & WebAuthnupdated
  • Help Center
  • Getting Started
  • KYC Verification
  • Passkeys & Biometrics
  • Privacy & Data Protection
  • Transaction Statuses
  • Gasless Transfers
  • Deposits & Withdrawals
  • Managing Virtual Cards
  • Freezing & Unfreezing Cards
  • Declined Transactions
  • SDK & API Support
  • x402 Monetization Basics
  • Booking Travel
  • Travel Refunds & Cancellations

Resources

  • Changelog
  • System Status
  • OpenAPI Spec
  • Community
  • GitHub
Docs/Help Center/x402 Monetization Basics

Help Center

x402 monetization basics

x402 is a protocol for requesting payment per HTTP request. FurlPay's endpoint returned503 controls_unavailable with reason plan_limit on 11 October 2026. Production settlement is also in development.

FurlPay x402 is currently unavailable

The endpoint is not currently issuing challenges, and the default facilitator is not enabled for production settlement. You can develop an integration or connect a facilitator you operate or have separately contracted. Check /api/rails and the x402 endpoint before offering a paid resource; if either reports an error, treat the rail as unavailable.

How the protocol works

An unpaid request can receive 402 Payment Required with payment requirements. The caller signs a compatible payment authorization and retries with it attached. A configured facilitator verifies and settles the payment before the endpoint releases the paid response. A challenge by itself does not authorize access to paid data.

Protocol versions

x402 clients and services may use different header and payload formats. FurlPay's integration guide documents the supported request formats and its separate production settlement status. Check the protocol guide before choosing a client or facilitator.

Self-hosted gateway package

The open-source @furlpay/gateway package can protect an API you operate. Configure the resource price, destination wallet and quote secret, then choose an available facilitator. The package can also be used with a facilitator you operate or contract separately; FurlPay's default facilitator is not currently enabled for production settlement.

See the current package documentation on npm for installation and framework-specific examples.

What a production integration must verify

  • Bind the payment requirements to the exact resource, method, amount, asset and network.
  • Reject expired authorizations, replayed nonces, underpayment and a wrong recipient.
  • Release paid content only after the configured facilitator confirms settlement.
  • Use shared replay protection when deploying multiple gateway instances.

Confirm the settlement recipient

After the selected facilitator confirms settlement, funds go to the wallet configured aspayTo. Verify the recipient, network, asset and settlement transaction before releasing the protected resource.

For FurlPay's request and settlement status, read Agentic Payments (x402) and the service availability overview.

Did this page help?
Edit this page on GitHub

← Previous

SDK & API Support

Next →

Booking Travel