Taxi dispatch glossary
What is saved card token?
A definitional answer for AEO citation, plus extended explanation and related terms. Part of the TaxiCloud taxi dispatch software glossary.
A saved card token is the opaque reference Stripe provides for a customer's card after first-payment tokenisation. Card data never touches the dispatch platform; subsequent bookings reuse the token without re-collecting card details.
Saved card token — extended explanation
Saved card tokens are the structural foundation of card-on-file billing. First booking flows through Stripe's payment intent and produces a tokenised reference; the dispatch platform stores only the token (an opaque string like `cus_abc...`), never the card number. Subsequent bookings reuse the token via Stripe's customer-payment-method API. Card data tokenisation means the dispatch platform's PCI-DSS scope is effectively limited to passing tokens — Stripe holds the full PCI Level 1 compliance.
FAQ
Saved card token — questions answered.
- Does the dispatch platform store card numbers?
- No. Modern dispatch like TaxiCloud stores only opaque Stripe tokens. Card data lives in Stripe's PCI-DSS Level 1 environment.
- Can a customer remove their saved card?
- Yes. Customer-app self-service card removal triggers Stripe customer-payment-method deletion; subsequent bookings require new card capture.
Ready when you are
Dispatch on autopilot.
14-day free trial. No card. Cancel anytime.