Use a zero-dollar (zero-value) authorization to verify a card and store it for future use without charging the cardholder

domain: payments · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Submit an authorization request with a $0.00 amount plus AVS and/or CVV data instead of running a nominal $1 ghost authorization.
  2. Route the zero-value auth through your gateway's dedicated account-verification endpoint/flag if one exists, rather than a generic sale endpoint, so it's coded as a verification, not a sale.
  3. Read back the issuer's approval/decline and AVS/CVV match results to decide whether to store the card on file.
  4. Store the resulting payment token/card-on-file reference only after a successful verification response, and don't attempt to capture or settle the $0 authorization since there is nothing to capture.
  5. Budget for the small per-transaction verification fee some networks assess on these calls, rather than assuming verification is entirely free.
  6. Use this pattern for free-trial signups, hotel/car-rental pre-stay verification, and card-on-file storage instead of authorizing $1 and voiding it, which networks discourage.

Known gotchas

Related routes

Create a Stripe SetupIntent to collect and store ACH debit authorization for future off-session payments
stripe.com · 6 steps · unrated
Store a card with Adyen and charge it for recurring payments using the shopperReference model
adyen.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans