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/Transaction Statuses

Help Center

Understanding Transaction Statuses

Every payment moves through a small, fixed set of states. Knowing what each one means tells you whether to wait, retry, or contact support.

The states

ParameterTypeDescription
preparedoptionaltransientThe payment is built and signed but not yet submitted to the network or rail.
pendingoptionalin flightSubmitted and waiting for on-chain confirmations or rail settlement. On-chain USDC usually settles within minutes; cross-chain transfers can take longer.
settledoptionalfinalConfirmed and irreversible. The money moved.
failedoptionalfinalThe rail or network rejected it after submission — funds do not leave your balance.
rejectedoptionalfinalRefused before submission: a policy, limit, or validation check said no. The response says which.

Card purchases additionally show declined when the card itself refuses — see Declined Transactions.

Checking a transaction on-chain

On-chain payments carry a transaction hash (0x… on EVM chains, a base58 signature on Solana). Open the transaction in the app and tap the hash to view it on the network's block explorer — if the explorer shows it confirmed but FurlPay still says pending, give it a minute for confirmations to reach our required depth; the depth scales with the amount.

When to worry

A pending deposit past 30 minutes is worth a look. First ask the co-pilot "where is my deposit?" — it checks your pending transactions directly. If the sender's explorer link shows a different network than you selected on the deposit screen, that is the usual cause; open a ticket in the stablecoins category with the tx hash (safe to share — a hash reveals nothing secret).

Deposits credit at network speed, not FurlPay speed

FurlPay detects deposits by watching the chain. The wait is the network's confirmation time plus a safety margin that scales with the amount — small deposits credit fastest.
Did this page help?
Edit this page on GitHub

← Previous

Privacy & Data Protection

Next →

Gasless Transfers