A prospect signs up for a 14-day free trial of your software, your membership, or your subscription box. They poke around once, forget about it, and then a charge lands on their card two weeks later. What happens next — a quiet cancellation or a chargeback that costs you the revenue plus a dispute fee — often comes down to details you set up long before that card was ever charged: what your checkout disclosed, what email you sent at signup, whether you reminded them before the trial ended, and how easy you made it to cancel.
Those details are not just good manners. Visa and Mastercard both run detailed rulebooks for subscription merchants, enforced through your payment processor. Break the rules and you get lost disputes, fines passed through your acquirer, and in persistent cases higher processing costs or account termination. The good news is that compliance is mostly a checklist: disclosures, notifications, receipts, cancellation, and correct transaction plumbing.
Why the Card Networks Police Your Free Trial
From Visa's perspective, free trials that roll into paid subscriptions were generating multimillion-dollar operational costs: swollen call-center volumes at issuers, customer complaints, write-offs, and card closures and reissuances when frustrated cardholders decided the fastest way to stop a charge was to kill the card number. Cardholders forgot they had agreed to future charges, could not figure out how to cancel, and disputed the transactions — sometimes as fraud, sometimes as cancelled recurring billing, sometimes as goods never received.
To fix that, Visa updated its subscription-merchant policies effective April 2020. Mastercard runs a parallel set of negative-option billing rules. Both networks monitor subscription merchants proactively — Visa says so explicitly, including mystery shopping — so treating these requirements as optional is a losing bet.
One important piece of context: card-network rules sit on top of the law, not instead of it. The federal Restore Online Shoppers' Confidence Act (ROSCA) still governs how you disclose and cancel recurring charges, and state auto-renewal laws — California's prominent among them — add their own disclosure, consent, and reminder duties. The FTC's 2024 click-to-cancel rule was vacated by a federal appeals court in July 2025, but the underlying statutes never went away. If you sell subscriptions to US customers, read our guide to subscription auto-renewal law after the click-to-cancel vacatur alongside this one: this post covers what the networks demand, that one covers what the law demands, and you owe your customers both.
What Visa Requires From Subscription Merchants
Visa's policy applies equally whether you sell physical goods or digital services, as long as a free trial or introductory offer rolls into an ongoing subscription. Six requirements do most of the work.
1. Express consent at enrollment
At signup, the cardholder must expressly agree to enter an ongoing subscription with recurring payments. A pre-checked box the customer must un-check is the textbook example of what Visa means by a negative-option practice — consent must be an affirmative act, such as checking an unchecked box or clicking an explicit agreement next to a clear statement of the recurring terms. The disclosure must cover what they get, what they pay, and how often.
2. An instant copy of the terms, even when nothing is due
At enrollment, you must send the cardholder an electronic copy of the subscription terms — email or text message if they agreed to texts — even if the trial is free and no amount was due. Visa specifies the contents:
- Confirmation that the cardholder agreed to a subscription that continues unless they cancel
- The subscription start date
- A description of the goods or services
- The ongoing transaction amount and the billing frequency and date
- A link or other simple mechanism to cancel future transactions online
Many billing platforms skip this receipt for free trials — exactly the gap Visa is targeting.
3. A reminder at least seven days before the first paid charge
Before you initiate a recurring transaction following a trial, introductory, or promotional period — or when the recurring terms change, such as a price increase or a new billing interval — you must send an electronic reminder with a link to online cancellation at least seven days in advance. That reminder is the single most effective chargeback-prevention email a subscription business can send.
4. Receipts that spell out the deal
Transaction receipts issued when the agreement is established must disclose the length of the trial or promotional period, state clearly that the cardholder will be charged unless they cancel, show the amount and date of the initial transaction (even a zero amount) and of subsequent recurring transactions, and include the cancel link. Every charge after that should generate its own receipt with the same core facts.
5. Cancellation as easy as unsubscribing
You must offer an easy way to cancel the subscription or the payment method online, regardless of how the customer originally signed up. Visa's own benchmark is memorably concrete: cancellation should be about as easy as unsubscribing from an email list. If signup took two clicks on your website but cancellation requires a phone call during business hours, you are not meeting this standard.
6. Statement descriptors and the recurring indicator
For the first financial transaction at the end of a trial, Visa requires a trial-related descriptor — "trial," "trial period," or "free trial" — in the merchant-name field, so the charge is recognizable in statements, banking apps, and text alerts. The recurring-payment indicator must also be populated on that first transaction even when its amount differs from the ongoing charge. A cryptic descriptor is one of the most common triggers of "I don't recognize this charge" disputes — treat it as part of your product, not your processor's default.
Mastercard's Parallel Rules for Negative-Option Billing
Mastercard covers merchants that offer a free or low-cost trial of seven days or longer and then automatically enroll the cardholder in a paid plan, with carve-outs for categories such as healthcare, utilities, telecom, and insurance. If your SaaS, membership, or subscription box has a trial of a week or more, assume you are covered. The obligations rhyme with Visa's:
- Checkout disclosure. Trial terms, the amount and cadence of future payments, and due dates must be visible on the checkout page — not buried in linked terms — with a copy emailed to the customer at the point of payment.
- Confirmation after enrollment. Send a confirmation covering your company name, what was purchased, the trial length, the auto-renewal disclosure with full price, the next charge date, and cancellation instructions.
- A reminder before the trial ends. For trials longer than seven days, industry compliance guidance describes a reminder window of three to seven days before expiry; for subscriptions of six months or longer, seven to thirty days before the billing date. Map your reminder schedule to the stricter of the two networks' expectations — in practice, that means honoring Visa's at-least-seven-days rule and treating Mastercard's window as the latest acceptable moment.
- Receipts after every charge. Each receipt should repeat the core facts from the confirmation: what, how much, when next, and how to cancel.
- Easy online cancellation. A cancel button in the customer account or a clearly linked cancellation page satisfies this; support-email-only cancellation is tolerated only if the instructions and policy links are displayed prominently, including in the account profile.
One nuance if you ship physical goods: for trial offers tied to a physical product, the trial clock runs from when the customer receives the goods — build delivery confirmation into your billing logic.
The Plumbing Most Founders Miss: Stored Credentials, CIT, and MIT
The disclosures above are the visible half of compliance. The invisible half is how your transactions are flagged when they travel across the networks — the stored-credential framework both networks enforce.
The model has two transaction types. The first transaction, where the cardholder is present and agrees to the arrangement, is a cardholder-initiated transaction (CIT). That CIT establishes the relationship: the customer consents, you store the credential (usually as a network token in your processor's vault, not the raw card number), and the network returns a transaction identifier. Every later recurring charge is a merchant-initiated transaction (MIT) that must reference that original identifier, telling the issuer "this charge traces back to an agreement the cardholder made."
Get the flags wrong and two bad things happen. Issuers increasingly decline mis-tagged MITs outright, which shows up in your business as involuntary churn — customers who wanted to stay subscribed but whose renewals failed. And when a charge is disputed, correct CIT/MIT lineage is part of the evidence that the charge was authorized.
In practice, this means three things for a small business:
- Use a billing platform or gateway that handles stored-credential flagging, and confirm it does — don't assume. Ask your provider how it marks the initial agreement transaction versus subsequent recurring charges and whether it passes the network transaction ID through.
- Tokenize and keep tokens fresh. Network tokens paired with account-updater services survive card reissues far better than raw card numbers, which directly cuts involuntary churn.
- Never re-use a stored credential for a new, unagreed purpose. A credential stored for a monthly subscription cannot be charged for a one-off upsell without fresh cardholder action. That upsell is a new CIT, not another MIT.
What Happens When You Get It Wrong
The enforcement path most merchants actually feel is the dispute process. Under Visa's expanded Condition 13.5 (Misrepresentation), issuers can dispute charges where goods or digital content were bought through a trial or as a one-off purchase and the cardholder says they were never clearly told about further billing. The companion code, Condition 13.2 (Cancelled Recurring), covers charges made after the cardholder withdrew permission. Mastercard routes the same fact patterns through its own cardholder-dispute codes.
The burden of proof is where compliant merchants win and everyone else loses. To defeat a 13.5 dispute, you must show two things: that the cardholder expressly agreed to future transactions at signup, and that you electronically notified them — at the contact details they provided — before charging after the trial or promotional period. Screenshots of your checkout disclosure, the timestamped enrollment email, and the pre-billing reminder with delivery receipts are the evidence package. Merchants who can produce it win; merchants who kept the agreement in an untimestamped database row and never sent a reminder generally don't.
Beyond individual disputes, both networks monitor dispute activity through their acquirer programs, and the costs flow downhill: dispute fees on every case, potential fines passed through your processor, and for persistent offenders higher rates or loss of the merchant account. A leaky trial-to-paid experience costs you three times — in refunds, dispute fees, and processing risk.
The Bookkeeping Side: Trials and Renewals Deserve Their Own Ledger Discipline
Compliance work and bookkeeping work overlap more than most founders expect, because the same events the networks care about are the events your books must capture.
Deferred revenue for prepaid terms. When a customer pays annually upfront, you have the cash but you haven't earned it yet. Book the receipt as a liability — deferred revenue — and recognize it month by month as you deliver the service. Trials that convert mid-cycle create partial-period recognition. If your billing platform can't export a clean earned-versus-deferred schedule, reconcile it monthly in your ledger before you trust any revenue number.
A reserve for refunds and chargebacks. Subscription businesses should carry an explicit allowance against revenue for expected refunds and disputes, calibrated to your actual trial-conversion complaint rate. A sudden spike in that rate is often the first quantitative signal that a disclosure or reminder broke — your books become an early-warning system for a compliance failure.
Reconciliation by descriptor and event. Match processor settlements to your ledger at the event level — trial starts, conversions, renewals, cancellations, refunds — not just the daily payout total. Descriptor mismatches between what customers see on statements and what your support team sees in the dashboard are a recurring source of "unrecognized charge" confusion; keep a record of exactly what descriptor each plan and trial variant emits.
Dunning as a controlled process. Failed renewals need a retry schedule with customer notice at each step, and every retry attempt should be traceable in your records. That trail matters twice: it recovers revenue, and it documents that your MIT retries followed the agreed billing terms if a later charge is ever disputed.
Accurate books matter here more than in most businesses, because in a dispute your records are your defense exhibits. Tracking trials, conversions, renewals, and refunds separately turns tax-time reporting from archaeology into arithmetic.
A Compliance Checklist You Can Implement This Week
- Checkout shows trial length, post-trial price, billing frequency, and next charge date above the pay button, with an unchecked explicit-consent box.
- Enrollment triggers an immediate email with the full terms and a cancel link, even for zero-dollar trials.
- A pre-billing reminder goes out at least seven days before the first paid charge and before any price or interval change, with a cancel link.
- Every charge produces a receipt repeating the amount, next billing date, and cancellation path.
- Customers can cancel online in a couple of clicks, without calling or emailing.
- Post-trial charges carry a trial descriptor on statements, and the recurring indicator is set.
- Your gateway flags the signup as a CIT and renewals as MITs referencing the original network transaction ID.
- You retain timestamped copies of the checkout terms, enrollment confirmation, and reminders for every subscriber.
- Your ledger tracks deferred revenue, a refund and dispute reserve, and event-level reconciliation of trials, conversions, and renewals.
None of these items requires an enterprise billing stack — most subscription platforms support all of them as configuration. Work through the list once, verify each email sends by running a test subscription yourself, and re-check whenever you change plans, trials, or processors.
Keep Your Subscriptions and Your Books Audit-Ready
Recurring revenue is the most valuable revenue a small business can build, and it is also the most scrutinized — by card networks, by regulators, and eventually by your accountant. The merchants who thrive under that scrutiny are the ones whose billing flow and whose books tell the same story: clear terms, documented consent, timely reminders, easy exits, and a ledger where every trial, conversion, and renewal is accounted for.
As you tighten up your subscription billing, maintaining clear financial records is essential. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
