Stored Payment Tokens

Replace your customer’s Primary Account Number (PAN) with a unique, secure token at checkout.

What are Stored Payment Tokens?

Securely offer the convenience of recurring billing and easy online payments. Stored payment tokens exchange stored primary account numbers with merchant-specific payment tokens.

Top Content Icon

Features of Stored Payment Tokens

Account Updates

Token Management

Enhanced Security

Domain Restriction Control (DRC)

Stored Payment Tokens Keep Business Moving Securely

Stored Payments Tokens are a network tokenization solution that enables the secure shift to digital payments which provides an array of benefits across the payments value chain.

Improves Customer Experience

Enhances Security

Provides Token Interoperability

How it Works

Learn more about the many ways Stored Payment Tokens can work. Additional Use Cases can be found in the documentation tab.

Ways to enable Stored Payment Tokens?

A smiling woman wearing a white blazer in a meeting.

Work with one of our payment partners

Coming Soon

A laptop and tablet displaying technical content

Connect to our APIs

View API Specs

Product FAQ

What is the difference between a Stored Payment Token and a Cloud Wallet solution?


We define each product based on two factors:

  1. Payment experience that the product enables and;
  2. The relationship between the Cardholder and the Merchant. With Stored Payment Tokens the Cardholder has a direct relationship with the Merchant. The Cardholder intentionally stores their payment credentials with that Merchant for the purpose of recurring and stored payments. With Cloud Wallets the Cardholder has a direct relationship with a wallet for the purpose of paying at multiple Merchants, such as guest checkout.

Do Discover Stored Payment Tokens replace the need for Account Updater?


Yes. Discover Stored Payment Tokens are automatically updated through an API connection, eliminating the need for a manual request from the Merchant. Discover Stored Payment Tokens also offer the additional benefit of storing a Payment Token instead of the Cardholder’s PAN. Once available, Merchants will be able to route Debit tokens to Discover Global Network (DGN) or PULSE the same way they do today with PAN.

Who can become a token requestor?


A Merchant, Acquirer, Payment Gateway, wallet or other digital enabler that supports Merchants can potentially become token requestors. Please reach out to your relationship manager for additional details about becoming a token requestor.

Are tokenized transactions treated any differently from a fraud or risk perspective?


At this time, there is not a difference, at the network level, between tokenized vs. non-tokenized transactions. However, there could be slight process nuances with some products. For example, Secure Remote Commerce (SRC) token transactions have a richer authentication process, but the Network is not making decisions or declining transactions for fraud/risk scoring.

What is the implementation process for a Merchant to use Discover Stored Payment Tokens?


A Merchant, an Acquirer, or other entity that supports Merchants can work with us directly to implement the product.

  1. Legal Agreement Framework.
  • Acquirer – subject to Stored Payment Tokens language in Acquirer Operating Regulations.
  • Direct Merchant - subject to Stored Payment Tokens language in Merchant Operating Regulations.
  • Payment Gateway or other entity that works with Merchants – will need to execute Payment Enabler Product Agreement (PEPA)
  1. Connection and Certification.
  • Client provides URL endpoints to connect to our API and certifies their code to test cases.
  1. Testing and Launch.
  • Once certification is complete and launch plan is in place, client is boarded in production and launch begins.

NOTE: For all environments, Third-Party Gateway certificates must be certificate authority (CA) signed as this is a standard production gateway requirement. JSON Web Encryption (JWE) certificates can be self-signed.

Capabilities that Enable Tokenization

Merchant-Initiated Transactions (MIT)

To enable tokenization MIT must be supported. Once enabled, it allows merchants to charge a customer’s card for a recurring payment.

Explore MITLink

Payment Account Reference (PAR)

When enabling tokenization PAR is optional but increases security by assigning a non-financial reference value to each unique PAN to link a Payment Account.

Explore PARLink
Discover Logo

© 2024 Discover Financial Services