A Visa stored credential is card account information that a merchant keeps to process future purchases. That can be a card number (PAN) or a payment token. Once you store it, Visa's framework asks you to get consent, flag the first payment, and identify every later payment correctly. Done right, issuers see clearer risk signals and approvals improve.
This guide explains the definition, the two transaction types, the payment models, the consent terms, and a step-by-step checklist your team can apply.
TL;DR
- A stored credential is account information kept by a merchant, its agent or a payment facilitator for future purchases. A card used for one transaction only is not a stored credential.
- Every stored-credential payment is either customer-initiated (CIT) or merchant-initiated (MIT). Each needs different flags.
- Get consent and disclosures before you store the card, and keep the agreement on file.
- Run an initial authorization or account verification, then use the required indicators and POS Entry Mode 10 on later payments.
- Stop charging after a decline or a cancellation.
Table of Contents
- What a Visa stored credential is
- Customer-initiated vs. merchant-initiated transactions
- Which payments can use a stored credential
- Getting consent before you store a card
- Flagging the first and later transactions
- A step-by-step checklist for merchants
- How this applies by business type
- Our perspective on stored credentials
- Run card-on-file payments with PaySec
- FAQ
- Sources
What a Visa stored credential is
Visa defines a stored credential as account information, including a PAN or payment token, that a merchant or its agent, payment facilitator or staged digital-wallet operator keeps for future purchases. The definition comes from Visa's stored credential transaction framework.
Two exclusions matter in practice:
- Data stored only to complete one specific transaction is not a stored credential under the framework.
- A credential that a digital wallet passes through, without the merchant storing it, is not a stored credential.
So a checkout that keeps no card data for later is outside the framework. A "save this card for next time" box, a subscription, or a vault of customer cards is inside it.
Stored credential vs. passkey vs. Flexible Credential
Search results for this term mix three different things. Keep them apart.
| Term | What it is | Who handles it |
|---|---|---|
| Stored credential (credential on file) | Card details or token kept by the merchant for future payments | Merchant, agent or payment facilitator |
| Visa Payment Passkey | A biometric method for authenticating the cardholder at checkout | Cardholder's device and issuer |
| Visa Flexible Credential | One Visa credential linked to two or more accounts or funding sources at the same issuer | Issuer chooses the funding account |
With Flexible Credential, Visa's U.S. merchant FAQ describes the merchant seeing a single credential while the issuer decides which account funds the payment. A passkey proves who the cardholder is. A stored credential is about how you keep and reuse card data. A merchant can use all three, and the stored credential rules still apply to the card data you keep.
Customer-initiated vs. merchant-initiated transactions
The framework splits every payment made with a stored credential into two groups.
Customer-initiated transaction (CIT). The cardholder actively authorizes the payment. Examples: a shopper checks out and enters a card, or a returning customer picks a saved card and clicks pay.
Merchant-initiated transaction (MIT). The merchant starts the payment without the cardholder actively taking part. A subscription renewal is the classic case. An MIT must rest on a prior agreement and a stored credential.
The framework document uses this split to decide how each payment is flagged. Get it wrong and the issuer sees a payment that looks unexpected, which raises the chance of a decline or a dispute.
A simple test for your team: who clicked pay? If the customer did, it is a CIT. If your system did, it is an MIT.

Where hosted checkout helps
The more card data your own systems touch, the more PCI work you carry. Keeping card entry on a hosted page is one way small merchants shrink that burden, and this overview of hosted checkout and PCI scope shows how that works for small businesses. Pair it with a tokenized vault so the credential you store is a token, not a raw card number. Our guide to tokenization vs. encryption explains the difference.
Which payments can use a stored credential
Visa's framework recognizes several payment models. Each one sits on top of a stored credential.
Card-on-file purchases
The customer saves a card and later buys again by selecting it. This is a CIT, since the customer actively authorizes each purchase.
Recurring payments
Fixed amounts at fixed intervals, such as a monthly software plan or a gym membership. The merchant initiates each charge, so these are MITs.
Installment payments
One purchase billed in several parts over time. The agreement should state the dates, the amounts, the currency and the total price.
Unscheduled credential on file (UCOF)
A charge triggered by an event rather than a calendar, for example topping up an account when the balance falls below a set level. The framework lists this as a separate type.
Industry-specific MITs
The framework also lists payments common in certain industries, when the credential was stored for future use:
- No-shows
- Delayed charges
- Incremental authorizations
- Reauthorizations
- Resubmissions
Restaurants, hotels, car rental and healthcare practices will recognize these. A restaurant that holds a card for a reservation and charges a no-show fee, or a practice that bills a balance after insurance settles, is working with this kind of MIT. The key point is that the customer agreed to the specific use when the card was stored.
Getting consent before you store a card
Consent is the first step, and it comes before any data is kept. According to the framework, the merchant must establish an agreement with the cardholder before storage, obtain consent, explain how the credential will be used, notify the cardholder of changes, and retain the agreement.
The agreement should cover these items, where they apply:
- The masked account number (last digits only)
- How you will notify the cardholder of changes to the agreement
- The expiry of the agreement, if there is one
- The merchant's location
- The amount, or how the amount is calculated
- Any fees or surcharges
- Cancellation and refund terms
- The schedule or the event that triggers a charge
- For installments: dates, amounts, currency and total price
Write this in plain language on the screen or form where the customer saves the card, and keep a record of the acceptance. For a deeper checklist, see our guide to card-on-file consent and POS Entry Mode 10.
A sample disclosure for a subscription
A clear subscription disclosure covers each item above in a few lines:
- "We will charge the card ending in 4242 for your plan on the first of each month."
- "The amount is $49 per month plus any applicable tax. We will email you 30 days before any price change."
- "You can cancel at any time from your account page. Cancellations take effect at the end of the paid period."
That example is an illustration of structure, not required wording. Adapt it to your own terms, and have your legal advisor review the final text.
Surcharge and fee disclosures
If you pass any fee to the customer, state it in the agreement. Surcharge programs have their own card brand rules and notice requirements, covered in our guide to card brand surcharge rules. If you are weighing the two approaches, the comparison of convenience fees vs. surcharges walks through the notice steps.
Flagging the first and later transactions
After consent, the framework requires an initial payment authorization or an account verification authorization. This first transaction establishes the stored credential, and it must be identified as the one that stores it. Visa's framework also requires indicators on later payments that show the credential is being used from storage.

Entry mode 10
Transactions that use a stored credential carry POS Entry Mode Code 10. The framework separates two cases:
- A cardholder-initiated stored-credential purchase uses entry mode 10 with no POS Environment value.
- An unscheduled credential on file transaction may use entry mode 10 together with POS Environment value C.
Your processor and gateway set these fields, so confirm with your integration team that each payment type maps to the right values.
Link MITs to the initial transaction
Issuers read the chain from the first transaction to each later one. Visa's newer tools build on this chain. Merchants often hear about the Visa network transaction ID, which ties later payments back to the original. A clean chain helps issuers recognize a legitimate recurring charge.
Why accurate flags matter
According to the framework, correct identification gives issuers greater risk visibility. It can increase authorization approvals and reduce customer complaints. Incorrect use of authorization data can also trigger fees, which our guide to the Visa misuse of authorization fee explains. If you hold funds before capturing them, review the preauthorization vs. capture checks as well.
A step-by-step checklist for merchants
Use this list when you launch or audit a card-on-file flow.
- Define the use. Decide whether you need card-on-file, recurring, installment, unscheduled or industry MIT payments. Write down the trigger for each.
- Draft the agreement. Include the items listed above. Show it before the customer saves a card.
- Capture consent. Record the date, the wording shown and the customer's acceptance. Keep it for as long as the agreement runs.
- Authorize the first payment. Run the initial payment authorization or an account verification, and mark it as the transaction that stores the credential.
- Store a token. Keep the credential in a tokenized vault instead of holding raw card numbers.
- Flag every later payment. Mark each as a CIT or an MIT, send the stored-credential indicators, and use entry mode 10 where the framework requires it.
- Notify of changes. Tell the cardholder before you change the amount, the schedule or the terms.
- Stop on decline or cancellation. Do not keep retrying a card after a decline that signals you should stop, and do not charge after the customer cancels.
- Keep details current. Cards expire and get reissued. An account updater service refreshes stored details so renewals keep going through.
- Add authentication where it fits. For customer-initiated payments, read our 3D Secure guide on fraud prevention.
Common mistakes to avoid
- Sending a recurring charge as if the customer had just checked out.
- Storing a card without a documented agreement.
- Skipping the initial authorization or verification.
- Failing to tell customers when terms change.
- Resubmitting charges after the customer has cancelled.
Each of these is a process fix. A short written runbook and a monthly review of declined recurring payments catch most of them.
How this applies by business type
Restaurants. Tabs, reservations and no-show fees depend on a card kept with the customer's agreement. Define the no-show charge in the booking terms, then flag it as an industry MIT.
eCommerce. Returning shoppers who pick a saved card are CITs. Subscription boxes and replenishment orders are MITs. Both need the same stored-credential setup at the first purchase.
SaaS and marketplaces. Monthly and annual plans are recurring MITs. Usage-based top-ups are unscheduled. Show the calculation method in the agreement.
Healthcare practices. Balances billed after a visit need the patient's agreement on file first. Keep payment data tokenized to limit what your systems hold.
CBD and other high-risk retail. Clean flags and clear consent records give issuers fewer reasons to question a charge. Plan the agreement text and the flagging before launch.
Our perspective on stored credentials
Stored credentials are where payment accuracy and customer trust meet. The rules are straightforward once a team writes them into the checkout flow: consent first, a flagged first payment, and the right indicators on every later charge.
We see the merchants who benefit most as the ones who treat the framework as part of how they bill, not as a one-time setup. Clear agreements, tokenized storage and correct CIT and MIT flags give issuers the information they need to approve legitimate payments.
That is why we pair compliant card-on-file handling with transparent pricing. PaySec offers Network Offset Pricing that passes through true wholesale interchange rates, with no hidden fees, no minimums and no long-term contracts. Our recurring billing, eCommerce gateway and fraud prevention services support the stored-credential workflow, and our reporting gives your team detailed visibility into each transaction. We support PCI DSS Level 1 and SOC 2 compliance so card-on-file programs run on a secure foundation.
PaySec Marketing Team
Run card-on-file payments with PaySec
If you bill customers on a schedule, save cards for return visits or charge after the fact, PaySec gives you the tools to do it cleanly. Our merchant services cover recurring billing, the eCommerce gateway, in-store and mobile processing, ACH and bank transfers, and fraud prevention. See how Network Offset Pricing works, or review the options on our pricing page.
Terminal placement is available at $0 per month through Free Placement. Ready to get started? Visit PaySec to begin.
FAQ
What is a Visa stored credential?
It is account information, such as a card number or a payment token, that a merchant or its agent keeps for future purchases. Credentials that a wallet only passes through, and data kept for one transaction, are not stored credentials. The definition appears in Visa's stored credential framework.
What is the difference between a CIT and an MIT?
A customer-initiated transaction is one the cardholder actively authorizes, such as checking out or choosing a saved card. A merchant-initiated transaction is started by the merchant without the cardholder taking part, such as a subscription renewal. An MIT depends on a prior agreement and a stored credential.
Do I need consent to store a card?
Yes. Under Visa's framework, you establish an agreement before storage, obtain consent, explain how you will use the credential, and keep the agreement on record. Include the amount or its calculation, the schedule or trigger, fees, and cancellation and refund terms.
What does POS Entry Mode 10 mean?
Entry Mode Code 10 identifies a transaction that uses a stored credential. A cardholder-initiated stored-card purchase uses it without a POS Environment value. An unscheduled credential-on-file transaction may pair it with POS Environment C. Your gateway or processor sets these fields.
Is a Visa passkey the same as a stored credential?
No. A passkey is a biometric way to authenticate the cardholder. A stored credential is card data a merchant keeps for later payments. Visa Flexible Credential is a third, separate product that links several funding accounts at one issuer to a single credential.
Sources
- Improving Authorization Management for Transactions with Stored Credentials, Visa
- Visa Flexible Credential Merchant FAQs (U.S. Region Only)

