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/Declined Transactions

Help Center

Troubleshooting Declined Transactions

A decline always has exactly one cause, and every cause has a fix you can apply yourself. Work down this table — it is ordered by how often each one actually happens.

Causes and fixes

ParameterTypeDescription
Card frozenoptionalmost commonYou (or the co-pilot, at your request) froze it. Cards -> Unfreeze, retry.
3-D Secure approval pendingoptionallarge purchasesThe purchase is waiting for you in Approvals. Approve with your passkey within the challenge window or it declines automatically.
Per-purchase limitoptionalsingle payment too bigRaise the per-purchase limit in card settings, retry, then set it back.
Daily limit reachedoptionalcumulativeWait for the midnight UTC reset, or raise the daily limit for today.
Channel disabledoptionalwrong contextAn online-only card used in person (or vice versa). Enable the channel in card settings.
Insufficient balanceoptionalcheck fundingThe card spends your stablecoin balance. Top up, or change the card's asset priority if funds sit in a different token.

Finding the cause fast

The declined transaction appears in your history with the reason in its subtitle. Faster still: ask the co-pilot "why did my card decline?" — it reads the card's state (frozen, limits, spent-today) directly. Pending 3-D Secure challenges live in Approvals, and enabling notifications means the approval prompt reaches you while you are still at the checkout.

When it is the merchant, not you

If the card is unfrozen, within limits, on the right channel, and funded — and the decline persists — the refusal is coming from the merchant's side. Retry once; if it repeats, open a ticket in the cards category with the merchant name and timestamp and we can see the authorization attempt from our end.

Declines cost nothing

A declined authorization never moves money and never charges a fee. The amount some merchants show as "held" is their pre-authorization releasing, not a charge.

Related: Freezing & Unfreezing, Managing Virtual Cards.

Did this page help?
Edit this page on GitHub

← Previous

Freezing & Unfreezing Cards

Next →

SDK & API Support