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/Gasless Transfers

Help Center

Gasless transfer availability

FurlPay has implemented an EIP-3009 gas-sponsored USDC transfer flow, but the production relayer is not configured. Gasless sending is not currently available as a live service.

Do not promise a zero-gas transfer

A payment authorization or fee quote does not mean FurlPay will submit it. Check /api/rails before offering a sponsored transfer. If the rail is unconfigured or its status cannot be read, stop the flow.

How the development flow works

EIP-3009 lets a USDC holder sign an authorization that binds the sender, recipient, amount and expiry. A configured relayer can submit it and pay network gas. The signature alone is not a transfer, and the relayer cannot change its signed fields.

Network fees

When a user submits a transaction directly from their wallet, the wallet needs the network's gas token and the transaction may incur network fees. A FurlPay sponsor may pay those fees only when a production rail is enabled and its current conditions are shown to the user.

Developer status

The implementation and route contract are documented for integration planning. Do not enable customer-facing gasless transfers based only on code presence. See agent payment protocols and the service availability overview.

Did this page help?
Edit this page on GitHub

← Previous

Transaction Statuses

Next →

Deposits & Withdrawals