Can I keep a client's card on file and charge it later?
EB
Eric Baxter
Checked November 16, 2026
Short answer
Yes, if the card is stored by your payment processor (Stripe, Square, PayPal) and the client agreed, in advance and in writing, to what you may charge and when. Never write a card number down, keep it in a form response, or store it in a spreadsheet or notes app; that breaks PCI rules and the processor's terms. The card networks treat a charge you start without the client present as a merchant-initiated transaction, and it is only valid against a prior agreement with that client.
What the card networks require
Stripe's documentation describes the rule plainly: credential-on-file is a card network requirement for businesses that store a customer's card and charge it in future transactions, and the business must declare how the stored card will be used. The networks split charges into two kinds:
Kind | Who starts it | What you need |
|---|---|---|
Customer-initiated (CIT) | The client, at checkout or by clicking "pay" on an invoice | Nothing beyond a normal checkout |
Merchant-initiated (MIT) | You, later, without the client present | A prior agreement with the client authorizing you to store and charge the card |
The agreement should cover every scenario you might charge for. Stripe's guidance: disclose every scenario to the customer when they consent to save the card. If you saved the card for a deposit and later charge a no-show fee that was never mentioned, that charge is easy to dispute.
What to put in the consent
Which card will be saved, and that it is saved with your processor, not by you.
What you may charge: the balance due, a no-show or late-cancellation fee, recurring sessions, add-ons the client requests.
When: on the booking date, after the session, on the 1st of each month.
How much, or how the amount is set.
How the client can remove the card or cancel the arrangement.
Plain words beat legal boilerplate here. A sentence such as "I agree that my card may be charged the remaining balance on the day of the session and a $50 fee if I cancel inside 24 hours" is exactly what a dispute reviewer wants to see.
What you must never do
Collect card numbers in a form, email, text, DM or intake document.
Store the CVV anywhere; processors are not allowed to keep it after authorization, and neither are you.
Charge an amount the client did not agree to, or for a reason they were not told.
Keep charging after the client has asked you to stop or the card's brand has changed; Stripe notes that a brand change requires a new cardholder agreement.
How it works in Aventide
Aventide does not save cards today. Clients pay each deposit and invoice through your own Stripe account, and Aventide never sees the card number. To collect a balance, send an invoice from the client's record; the client pays it online and gets a receipt. Aventide takes 0% of these payments; Stripe's standard fee applies.
Questions people ask
Can I charge a no-show fee from a saved card?
Yes, if the fee and the trigger were in the policy the client accepted when the card was saved.
Can I store the card number in my CRM's notes field?
No. That is exactly the storage PCI rules forbid.
What if the client gave me the number over the phone?
Enter it directly into your processor's dashboard or a virtual terminal while on the call, then do not keep it anywhere else.
Does saving a card need a contract?
Consent, not necessarily a full contract. A checkbox with clear text at checkout is standard; a signed contract clause is stronger for larger or recurring amounts.
Will the client have to re-authenticate later charges?
Usually not. When the card is saved correctly as credential-on-file, later off-session charges are marked merchant-initiated and go through without the client present.
Last checked: November 16, 2026 against Stripe's documentation. Card network rules change; your processor's terms govern. Stripe is a trademark of Stripe, Inc.
