Card on file means a customer has authorized your business to store their payment card so you can charge it later without asking for the number again. Your payment provider keeps it as a token, outside your own files. Before storing it you need the customer's consent to an agreement on how and when you will charge it, and Visa's rules list what that agreement must cover.
A card on file, which Visa calls a stored credential, is a customer's card number or payment token kept by a merchant or its payment provider to process future transactions. A card held only to finish a single purchase, such as a hotel's no-show charge on one reservation, falls outside Visa's stored-credential agreement rules.
How a card on file actually works
When a customer agrees to keep a card on file, the card details go to your payment provider's secure storage, often called a vault. The provider sends back a token: a stand-in value that lets you charge that card through the provider but is useless to anyone who steals it from your systems. Your software shows the card brand and last four digits so staff know which card is which. Nobody in your business needs to see the full number again.
Visa's rules add two mechanics worth knowing. After the cardholder agreement is in place and before the first charge, the merchant must either submit an authorization for the amount due or, if nothing is owed yet, an account verification (a zero-amount check). If that first request is not approved, the merchant must not store the card. Later charges carry an indicator showing whether they are recurring, installment or unscheduled.
One detail never goes into storage: the security code. The PCI Security Standards Council says storing card verification codes for card-on-file or recurring transactions is prohibited, and that neither the customer's consent nor encryption makes it acceptable. Stored-card charges run without it.
Who starts the charge: CITs and MITs
Visa sorts stored-card payments by who initiates them and on what schedule, and the type affects what your agreement must say.
| Type | What it means | Example |
|---|---|---|
| Cardholder-initiated (CIT) | The customer actively takes part, using the stored card instead of typing it | A customer clicks "Pay with saved card" on an invoice |
| Recurring (merchant-initiated) | Charges at fixed, regular intervals, no more than a year apart | A monthly service plan |
| Installment (merchant-initiated) | A series of charges for a single purchase, spread over time | A $3,000 job paid in six monthly parts |
| Unscheduled credential on file (merchant-initiated) | A fixed or variable charge that isn't on a set schedule, made under the customer's standing consent | Charging for a repair the customer approved by text |
Before a customer-initiated charge, Visa's rules require the merchant to validate the cardholder's identity, for example with a login. A charge you start relies instead on a standing instruction the customer agreed to in advance, which is what the authorization is for.
The authorization you need
Visa's rules (the Visa Core Rules and Visa Product and Service Rules, October 2026 edition) say that before storing a card for future charges, the merchant must get the cardholder's express informed consent to an agreement. That agreement must contain, among other things:
- a description of the goods or services, the total purchase price, and your cancellation and refund policies;
- any surcharge, where surcharging is permitted, with the required disclosures;
- your location, plus an address, email and phone number for questions about the charges;
- the card that will be charged (last four digits only), and how the cardholder will be told about changes to the agreement;
- the amount, or how it will be worked out, and the currency;
- how the stored card will be used, with the timing and frequency of charges or, for unscheduled charges, the event that will prompt one; and
- when the agreement expires, if it does, and the length of any trial or introductory period.
The terms for the specific type of charge must be shown clearly when the customer consents, separately from your general terms and conditions. The merchant has to keep the agreement for as long as it lasts and provide it to the cardholder or the card issuer on written request, and may use the stored card only as agreed.
Visa revises these rules regularly, and other card brands have their own, so confirm the current requirements with your processor.
A credit card on file authorization form: checklist
Whether the form is on paper, in a booking flow or a checkbox on a payment page, it should capture:
| Section | Example wording for a pool-service plan |
|---|---|
| Card identified | Visa ending 4417 |
| What will be charged | $180 for weekly service, plus approved repairs |
| When | On the 1st of each month; repairs within two days of your written approval |
| How variable amounts are set | Repairs charged at the quoted price you approve by text or email |
| Fees | Any surcharge, if you apply one, and its rate |
| Changes | We will email you at least 30 days before any price change |
| How long it lasts | Until you cancel |
| How to cancel | Email or call us; cancellations take effect before the next charge |
| Refund policy | Your policy, in plain words |
| Your business details | Legal name and contact details, including your location |
| Customer's agreement | Signature or recorded electronic acceptance, with the date |
The 30-day notice and two-day timing in that table are business choices, not network rules. Pick terms you can keep, and send the customer a copy of what they agreed to.
Bank accounts on file
The same idea applies to ACH, under different rules. For recurring debits from a consumer's bank account, Regulation E says preauthorized transfers may be authorized only by a writing signed or similarly authenticated by the consumer, and that whoever obtains the authorization must give the consumer a copy. Your processor can tell you how its payment pages capture that authorization.
Using a card on file for repeat billing
Say a pool-service company has 140 weekly customers on a $180 monthly plan, all with cards on file (the figures are hypothetical). On the 1st of the month it charges $25,200 (140 × $180) without sending a single invoice. Compare that with mailing 140 invoices and waiting for the checks.
The work moves to the exceptions. Suppose 5 of the 140 cards decline, mostly because they have expired or been replaced. That is $900 (5 × $180) the company has to chase. A sensible routine:
- Notify each customer on the day of the decline, with a link to pay and update the card.
- Retry only as your processor and the card network rules allow, and ask your processor what those limits are before you set a retry schedule.
- Pause service after a stated number of days, as your agreement says, rather than letting the balance grow.
Fewer cards fail if replacements reach you automatically. Visa runs an account updater service, Visa Account Updater, and its rules require issuers to enroll most of their card ranges in it, so new card details can flow to merchants when a card is replaced. Whether you receive those updates depends on your processor, so ask whether it offers updater services for the brands you accept. For the follow-up process on payments that still fail, see our guide to dunning.
Field businesses get a second benefit. When a technician finishes an approved repair, the office can charge the stored card under the customer's agreement instead of sending an invoice or calling for a number, which is the point of avoiding phone payments for regular customers. A setup we put together can include a Customer Vault that stores payment methods, along with recurring payments that charge customers automatically on the schedule you set. For fixed plans, the mechanics are covered in our guide to recurring billing.
Frequently asked questions
How long can I keep a card on file?
For as long as the agreement with the customer lasts. Visa's rules expect the agreement to state when it expires, if it does, and allow the stored card to be used only as agreed. When a customer cancels, or the relationship ends, delete the stored card through your provider. Keeping cards you no longer have permission to charge adds risk and no benefit.
Does the authorization have to be on paper?
Visa's rules call for the customer's express informed consent to a written agreement that you keep and can produce on request; they do not specify paper. Many businesses record acceptance electronically, such as a checkbox on a payment page with the terms shown and the acceptance logged. For consumer bank debits, Regulation E requires a writing signed or similarly authenticated. Confirm your format with your processor.
What happens when a stored card expires?
The next charge is likely to decline unless the card details have been updated. Account updater services can supply the new expiration date or number automatically when the issuer takes part. If not, ask the customer to update the card through a secure link rather than reading the new number over the phone.
Sources
- Visa: Visa Core Rules and Visa Product and Service Rules (PDF, 24 October 2026), Tables 5-19 to 5-21 and section 8.6.1, accessed 15 November 2026
- PCI Security Standards Council: FAQ: Can card verification codes/values be stored for card-on-file or recurring transactions?, accessed 15 November 2026
- Electronic Code of Federal Regulations: 12 CFR 1005.10, Preauthorized transfers (Regulation E), accessed 15 November 2026