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/Architecture/Monorepo

Architecture

Monorepo

FurlPay uses an npm-workspace Turborepo. The repository contains the web app and API, developer SDKs, agent integrations, shared packages and client application source. Code in the repository does not by itself indicate a released or production-enabled service.

Repository presence is not product availability

Some packages and route handlers are prototypes, test integrations or gated capabilities. Use the service availability overview and the current rail status before relying on a feature in production.

Main workspaces

apps/webNext.js 15

Web product, documentation portal and App Router API handlers.

sdks/node@furlpay/furlpay-node

Node.js / TypeScript server SDK and webhook-signature helper.

packages/cli@furlpay/cli

Command-line developer tooling. Commands that call payment, travel, card or brokerage routes inherit those routes' availability limits.

packages/gateway@furlpay/gateway

Self-hosted x402 gateway package. Its default FurlPay facilitator requires production settlement to be enabled.

mcp@furlpay/mcp-server

MCP integration for compatible agent clients; available tools and payment execution are separate concerns.

packages/Shared modules

Shared code for schemas, ledger, signing, compliance, settlement and UI components.

Dependency direction

Apps and SDKs can depend on shared packages. Shared packages should not depend on a product surface. This keeps reusable schemas and domain logic separate from Next.js route handlers and client applications.

  • API and product routes live in apps/web/src/app.
  • Shared payment, security and provider code lives under apps/web/src/lib and packages/.
  • Server SDK sources live under sdks/; the CLI and x402 gateway are separate packages.
  • Application and package release status is maintained separately from source code.

Build and deployable artifacts

Workspace build scripts are orchestrated through Turborepo and npm. Deployment targets, external credentials, release signing and store publication are configured separately. A successful local build does not prove that a provider is configured or that an artifact is published.

Source and documentation

The public packages and repositories are linked from the FurlPay GitHub organization. Use each package's own README and release metadata for installation details. This portal is the source for current FurlPay API and service availability guidance.

Did this page help?
Edit this page on GitHub

← Previous

For AI Agents

Next →

API Routes