Stored Credentials

Stored credentials let you save a customer's card and charge it again later - for subscriptions, recurring billing, or any saved card payment where the customer isn't there to re-enter their details. Card data is captured and held by Super on a PCI-compliant basis, so you only ever handle a token reference (pm_), never raw card numbers.

Tokens and payment methods are the same thing

Throughout these docs, "token" and "payment method" refer to the same concept: a stored card reference (pm_) you can charge without the customer present.

How It Works

Stored credentials are built from two linked resources - a customer and a payment method - created in that order:

  1. Create a customer. A customer is the central record (cus_) that everything else hangs off. Create one before storing any card against them.
  2. Create a payment method. Create a payment method (pm_) against the customer. It starts in REQUIRES_ACTION until card details are attached.
  3. Attach the card. How the payment method reaches ENABLED depends on where the card comes from:
    • New customer - use a Setup Intent with the <super-card> component to collect the card. Super handles PCI capture and 3DS, then moves the payment method to ENABLED.
    • Migrating from another provider - Super backfills the card automatically after the token import. See Migrate to Super.
  4. Charge the saved card. Once ENABLED, use the payment method id to take off-session payments.

Key Objects

Object ID Prefix What it's for
Customer cus_ A known individual in your business. The central record that payment methods are linked to.
Payment method pm_ A stored card credential linked to a customer. Charged off-session once ENABLED.
Setup intent si_ A short-lived session passed to the <super-card> component to collect a new customer's card.

💡You never handle raw card numbers. Super captures and stores card data on a PCI-compliant basis - you work only with the pm_ reference.

Explore Stored Credentials

Work through the resources in order, or jump to migration if you're bringing cards across from another provider.

Customers - Create and manage the customer records that payment methods are linked to.
Tokens - Store and manage saved card tokens against a customer for recurring, off-session payments.
Migrate to Super - Bring your existing customers and card tokens across from another provider.

Using Saved Cards

Once a payment method is ENABLED, take payments with it from the Saved Card Payments flows:

Save a Card & Take Payment
Charge a Saved Card

Updated 20 days ago