Telehealth payments

Recurring Billing for Subscription Telehealth: Card on File, Account Updater, Tokens and Visa's Retry Limits

A membership only earns money if the renewal goes through. This is the plumbing behind it: what you store, how it stays current, and how often Visa lets you try again.

By VyaPayPublished 7 min read

Under Visa's October 2026 rules you may never retry a Category 1 decline, and may reattempt Categories 2, 3 and 4 up to 20 times in 30 days. The retry limit is the last piece of recurring billing. Before it come the patient's consent to store a card and charge it on a schedule, storage that keeps the card number out of your systems, and tools that keep stored cards current when they're reissued.

A card-on-file transaction is a charge to a card the cardholder has agreed to let a merchant store and use again, either when the cardholder starts a purchase or on a schedule the merchant runs. A telehealth membership's renewals are card-on-file charges, and the consent given at signup is what authorizes every one that follows.

Consent that names the amount, the schedule and how to stop it, captured at signup and kept where you can find it. A patient who agreed to "membership billing" in a terms page they scrolled past has agreed to very little you can show anyone. At minimum, the signup screen should state:

  • the amount of each charge, or how it is calculated if it varies;
  • the interval, in plain words;
  • when the first renewal falls;
  • how to cancel, and any restriction on cancellation or refunds, with the acknowledgement Visa's §5.4.2.5 requires before final checkout.

Introductory offers need extra care. If the first month is free or discounted, the signup screen should say what the full price is, the date it starts, and that the card will be charged then unless the patient cancels. A patient who remembers only the intro price can end up disputing the first full charge.

Record what the patient saw: the terms version, the timestamp and the screen content. Your gateway will also expect each charge to be flagged: whether it is the first use of the stored card or a later one, and whether the patient started it or it is a scheduled charge you started. Those flags travel with the transaction, so make sure your integration sends them correctly. The legal side of auto-renewal disclosures, including the FTC's position and state laws, is in subscription billing rules for telehealth.

Bank debits work differently. Regulation E (12 CFR 1005.10(b)) requires recurring electronic transfers from a consumer's account to be authorized in writing or by a similarly authenticated method, with a copy to the consumer. If you offer ACH for memberships, the details are in ACH and eCheck for telehealth memberships.

Where should the stored card live?

Not in your systems. Tokenization lets your application keep a token while the card number sits in the processor's vault, so your EHR, CRM and support tools never hold anything an attacker could charge. PCI DSS v4.0.1, whose future-dated requirements became mandatory on March 31, 2025, still applies to any part of your environment that handles card data, and hosted payment fields plus tokenization are how you shrink that part.

VyaPay's VyaCloud tokenization works this way: card data never touches your servers, and your membership records store the token. The renewal job charges the token, not a card number.

How do account updater and network tokens keep cards current?

By replacing reissued card details without asking the patient, through two different routes. Both are industry tools offered through the card networks and supported, or not, by individual processors, so ask any processor you are evaluating which it supports.

ToolWhat it doesWhat to ask a processor
Account updaterWhen a participating issuer reissues a card, the network's updater service passes the new number or expiry date to the merchant's processor, which updates the stored credentialDo you support it, which networks, and how do updates and closed-account notices show up in reporting?
Network tokensThe card network issues a token in place of the card number, tied to your business, and can keep it linked to the new card when the issuer reissuesDo you provision network tokens, and what happens when a token can't be used?

Neither tool covers every card, since both depend on issuer participation. An updater can also tell you a card was closed. That's your cue to contact the patient, not to start retrying.

How many times can you retry a declined recurring charge?

Never, for a Category 1 decline, and up to 20 times in 30 days for the rest. Visa's October 2026 rules sort declines into four categories:

CategoryVisa's descriptionReattempts allowed
1Issuer will never approveNone
2Issuer cannot approve at this timeUp to 20 in 30 days
3Data qualityUp to 20 in 30 days
4GenericUp to 20 in 30 days

Vendor blogs still quote 15; the current rulebook says 20. Treat 20 as a ceiling, not a target. A Category 3 decline means something in the request is wrong, and in our view retrying the same bad data twenty times just spends your allowance, so fix the data first. Ask your processor how it maps issuer response codes to these categories.

Log every attempt with the date and the category returned, per card. If your acquirer asks how your billing stays inside Visa's limits, that log is the answer, and it also shows you which retry days actually recover payments.

A dunning schedule that stays inside the rules

Fewer, better-spaced retries, with the patient told early. Here is one pattern, as an example rather than a rule:

  1. Day 0, decline. Classify it. Category 1: stop retrying, email the patient a secure link to update the card. Category 3: correct the data, then retry.
  2. Day 1. First retry for Categories 2 and 4. If it fails, send the patient the update link.
  3. Days 3, 5 and 7. Further retries, each logged with the decline category returned.
  4. Day 7 onwards. Pause the membership, decide with your clinical team what happens to the next shipment, and tell the patient where things stand.
  5. Day 30. In this example, retries stop here and any further charge waits for the patient to update the card.

That is four retries in all, well inside the limit. Keep the emails plain: no drug names or conditions in subject lines or previews, since a dunning email can land on a shared screen. VyaPay's saved cards and recurring billing, payment links and email invoices cover the collection side of this schedule; if you want to walk through it against your own membership, talk to us about your program.

Pre-renewal notices and the disputes they prevent

Tell the patient before you charge, especially after a long interval, a free or discounted first period, or a price change. A renewal the patient expected gives them little reason to dispute it. One they forgot about can become a Visa 13.2 Cancelled Recurring Transaction dispute or a fraud claim from someone in the household who didn't recognize it.

Put the plan name, amount and date in the notice, with a cancel link that works. Store the notice with the consent record, because it belongs in the evidence you send if a dispute arrives anyway. How to answer each dispute type is in telehealth chargebacks.

Frequently asked questions

Is Visa's retry limit 15 or 20?

Twenty reattempts in 30 days for Categories 2, 3 and 4, under Visa's October 2026 rules. Older vendor material still says 15. Category 1 declines get no retries at all.

Should a telehealth company use account updater or network tokens?

They solve the same problem by different routes, and they aren't exclusive: where a processor supports both, a merchant can use both. Both depend on issuer participation, so neither will catch every reissued card.

Do I need fresh consent when a membership price changes?

We'd treat a price change as a change of terms: notify the patient before the first charge at the new price and record their acknowledgement. Ask counsel which state auto-renewal laws apply to the change.

Can we keep encrypted card numbers in our EHR?

Keep them out entirely. With tokenization your systems hold a token, and PCI DSS applies to any system that stores, processes or transmits card data, encrypted or not.

Sources

Talk to the team that underwrites you

Tell us what you prescribe or sell, how you bill and who your pharmacy partners are. You'll be talking to the people who run VyaPay's processor and make its risk decisions.

or call 833-4-VYAPAY

Let’s meet up!

Tell us about your business and someone from our team will reach out.