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/Integrations/Persona KYC

Integrations

Persona verification integration

FurlPay contains a Persona webhook integration for processing verification outcomes. Provider credentials and an approved Persona configuration are required; this technical integration page is not an offer of identity verification in every account or region.

Availability is account and provider dependent

Users should start verification only from a flow shown inside their signed-in FurlPay account. Do not create a separate Persona inquiry or send documents based on a code sample on this page.

Webhook handling

MethodPathDescription
POST/api/webhooks/personaVerifies Persona's signature over the raw request body and processes a bound inquiry outcome

The handler verifies the persona-signature header before parsing JSON. It requires PERSONA_WEBHOOK_SECRET, rejects an invalid or missing signature, de-duplicates deliveries and checks the inquiry's server-side user binding before changing a verification status. Missing configuration fails closed.

Deployment requirements

  • Configure the Persona account and server-side credentials through the deployment's approved secret-management process.
  • Register the exact production webhook URL with Persona and use the matching webhook secret.
  • Exercise inquiry binding, duplicate delivery, failure and out-of-order events in a non-production environment first.
  • Do not treat a webhook acknowledgement as proof that a user passed verification; inspect the account's recorded status.

User-facing guidance

The supported verification provider, required documents and current status should be displayed by the authenticated product. See the identity verification help page for safe user guidance.

Did this page help?
Edit this page on GitHub

← Previous

Stripe Crypto

Next →

Regulatory status