DashForDevsDocs
DocsNewsAPI v1
dashfordevs.comSign in

© 2026 DashForDevs

DocsNewsdashfordevs.comLegalStatus
DocsStorefront PaymentsSaved Cards
Introduction
Getting Started
Authentication
Products
Categories
Cart
Checkout
Blog
Reviews
Webhooks
Customers
Orders
Inventory
Shipping
Discounts
Affiliates
Email
Media & Files
Analytics & Tracking
Locations
Tax
Global Data
SEO
Error Handling
Geography
Finance
Automations
Page Types
Surveys
Billing & Subscriptions
Storefront Payments
Stripe IntegrationAuthorize.netPayment FlowSaved CardsPayment WebhooksGoogle Pay
SDK Reference
REST API
Storefront Architecture
Notifications
Security
Team & Permissions
Migrations & Import
Calendar & Appointments
Contact Forms
AI Bots
Dashboard API
Deployment
Changelog
Troubleshooting
Recipes
CLI & Deployment
Image Pipeline
White-label Platforms
Records Engine
Platform Modules
Platform Security
Site Keys & Client Sites
Use Cases
Operations

Saved Cards

Allow customers to save payment methods for faster checkout.

Updated March 29, 2026

On this page
  • Overview
  • How Saved Cards Work
  • Using Saved Cards
  • Next Steps

Overview

For returning customers, saved cards allow faster checkout. Card tokenization and storage are handled securely by the payment processor.

How Saved Cards Work

When a customer completes checkout while authenticated, their card token can be saved for future purchases. The raw card number is never stored — only a secure reference token from the payment processor.

Using Saved Cards

Saved card functionality is managed through the payment processor's portal and the dashboard.

Next Steps

  • Payment Flow — Payment lifecycle
  • Payment Processing — Tokenization
PreviousPayment FlowNextPayment Webhooks

On this page

  • Overview
  • How Saved Cards Work
  • Using Saved Cards
  • Next Steps