FurlPay Docs
Open App
  • Introduction
  • Quickstart
  • For AI Agents
  • Monorepo
  • API Routes
  • Authenticationnew
  • Webhook Eventsnew
  • Error Codesnew
  • Rate Limitsnew
  • Agentic Payments (x402)
  • Agent Trust & Mandates (TAP)
  • CCTP Cross-Chainnew
  • LI.FI Swapsnew
  • FurlPay Travels (Travel MCP)
  • Solana Actions & Blinks
  • Claude Connectornew
  • AI Assistants
  • Stripe Crypto
  • Persona KYC
  • MiCA Roadmap
  • Security Posturenew
  • MPC & WebAuthn
  • Help Centernew
  • 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/Managing Virtual Cards

Help Center

Activating and Managing Your Virtual Cards

Every control on a FurlPay card applies in real time — a limit you set now applies to the very next authorization.

The controls

  • Label — name cards by purpose ("Subscriptions", "Travel") so statements stay readable.
  • Per-purchase limit — the ceiling for any single authorization.
  • Daily limit — total spend per day; the card declines past it and resets at midnight UTC.
  • Channels — enable or disable online, in-person, and ATM use independently. A subscriptions card with only "online" enabled cannot be skimmed at a terminal.
  • Settlement currency — which currency the card settles in (USD, EUR, GBP, INR).
  • Asset priority — which stablecoin balance the card spends first.

Viewing full card details

The number and CVV stay hidden until you pass a biometric check — a fingerprint or face prompt guards every reveal, on web and in the app.

Purchase approvals (3-D Secure)

Larger or unusual purchases trigger a challenge: the purchase pauses until you approve it with your passkey in Approvals. The approval signature is bound to that exact purchase. Declining is always one tap — refusing money movement is never harder than allowing it.

Everything leaves a trail

Every settings change — a freeze, a limit change, a channel toggle — is written to an internal security event feed with the acting account, whichever surface triggered it (app, web, or the co-pilot).

Set limits before you need them

The cheapest fraud protection is a per-purchase limit sized to how you actually use the card. A card that only ever pays a $12 subscription has no business with a $2,500 per-purchase ceiling.

Card declining unexpectedly? See Troubleshooting Declined Transactions.

Did this page help?
Edit this page on GitHub

← Previous

Deposits & Withdrawals

Next →

Freezing & Unfreezing Cards