Telehealth payments

Billing Descriptors for Telehealth: Discreet Without Being Unrecognizable

Patients want a charge nobody else can read into. Card networks want a name the patient recognizes. A good descriptor does both, by leaving clinical words out rather than hiding who you are.

By VyaPayPublished 7 min read

Use the brand name patients signed up under, add a website or phone number they'll recognize, and leave out anything that names a condition or a drug. Visa requires the merchant name to be the one you primarily use with customers, so discretion can't come from billing under an unfamiliar company name. It comes from what you leave off the statement.

A billing descriptor is the merchant name, plus details such as a phone number or website, that a cardholder sees for a transaction on a statement or in a banking app. Visa's rules call it the merchant name and require it to match the name the merchant primarily uses with customers, consistently across authorization, clearing and dispute records.

What Visa requires of your merchant name

Recognizability. Section 1.5.1.12 of the Visa Core Rules (24 October 2026 edition) sets four expectations for the merchant name:

  • It is the name the merchant primarily uses to identify itself to customers.
  • It is displayed on the merchant's website or app.
  • It is used consistently: on the receipt and in authorization, clearing and dispute records.
  • For e-commerce, the website address can stand in for the name, unless the address is unrelated to the merchant name.

The same section tells acquirers to correct merchant names that confuse cardholders. That makes your descriptor partly the acquirer's problem, which gives it a reason to look at yours during boarding.

In our reading of §1.5.1.12, several names telehealth companies reach for don't fit. A holding company's legal name, a management company's name the patient never sees, a professional corporation's registered name, or a deliberately vague label such as "Online Health Services" all fail the same test: the patient didn't buy from anything called that. The name the patient knows is the brand on your site, your emails and your app, and the descriptor should be that brand.

Why an unrecognizable descriptor turns into a dispute

A patient who doesn't recognize a charge may call their bank, and the bank can treat the call as fraud. For a card-not-present charge, that is Visa Dispute Condition 10.4 (Other Fraud – Card-Absent), and you are now answering a fraud claim for a visit that happened. The same thing can happen when someone else reads the statement: a spouse or parent sees an unfamiliar name on a shared card and reports it.

Subscriptions add a second route. A patient who forgot about a renewal and sees a name they can't place may dispute it as fraud, or as a cancelled recurring transaction (Condition 13.2) if they believe they cancelled. A recognizable descriptor doesn't stop the second complaint, but it moves the conversation from "who is this?" to "I meant to cancel," which you can answer with your cancellation records. How each dispute type plays out, and what evidence wins it, is in telehealth chargebacks.

So the discreet-but-unrecognizable descriptor fails twice. It protects the patient's privacy from the household only until someone asks the bank what the charge is, and it turns ordinary forgetfulness into fraud claims.

What to put in a telehealth descriptor, and what to leave out

Put in what identifies you; leave out what identifies the treatment.

ElementInclude?Reason
The brand name on your site, emails and appYesThe name Visa expects you to use with customers
Your website's root domainYes, where it matches the brandVisa allows the website address for e-commerce unless it's unrelated to the name
A customer-service phone number that someone answersYes, where your acquirer supports itGives the patient a call to make other than the one to their bank
Drug names, doses or "Rx"NoTells anyone reading the statement what was prescribed
Condition words, such as weight, hair loss or anxietyNoSame problem, one step removed
A holding, management or practice entity name patients never seeNoNot the name used with customers; the kind of confusion acquirers must correct
Generic labels or initialsNoDiscreet to the point of unrecognizable

One case needs a decision earlier than the descriptor. If your brand name itself names a condition, the descriptor will too, because Visa wants the name you use with customers. For that business, discretion has to be designed into the brand, or into a trade name you really do use with patients on your site, in your emails and in your app. Choosing a different name only for the statement is the mismatch §1.5.1.12 exists to prevent.

Static and dynamic descriptors

A static descriptor is set on your account when you're boarded and appears on every transaction. A dynamic descriptor, sometimes called a soft descriptor, is text your system sends with each transaction, inside the format and length your acquirer allows, and it can add detail to the fixed name. An illustrative example: BRANDNAME*RENEWAL, where BRANDNAME is the name patients already know you by. Length limits and formats vary by acquirer and card brand, so get yours from the processor rather than from a blog post.

Dynamic descriptors earn their keep in a few places:

  • Separating charge types you bill yourself, such as a first visit and a monthly renewal, so the patient can tell them apart.
  • Marking a renewal as a renewal, which helps the patient who forgot they signed up.
  • Keeping a brand change consistent while you migrate, as long as the processor knows about it.

The same rules apply to the dynamic part as to the rest. No product names that reveal treatment, no patient details, and nothing that drifts away from the name the patient knows. If your pharmacy partner charges for medication separately, its charge carries its own merchant name, and your patient will see two lines. Tell them both names before the first statement arrives.

Descriptors are patient data too

The descriptor is the payment field with the widest audience. Section 1179 of HIPAA keeps the law's requirements off a financial institution's payment activities, but it doesn't take your own systems out of HIPAA, and what you send into payment fields starts in your systems. Anyone who reads the statement, opens the banking app or handles the household's bills can read the descriptor.

So treat it as the strictest case of a wider rule: keep diagnoses and drug names out of descriptors, order descriptions, receipts and webhook payloads, and let reference IDs point back to your clinical records. The full list of payment fields where patient information leaks, and what to put in each instead, is in our explainer on HIPAA Section 1179 and payment processing. Bank debits raise the same question, since an ACH debit shows a company name on the patient's bank statement too.

Make the name familiar before the statement arrives

The statement is the last place a patient should learn your billing name. Put it in front of them earlier:

  1. At checkout, next to the price: "Charges appear as BRANDNAME, brandname.com."
  2. In the confirmation email and the receipt, in the same words.
  3. In renewal reminders, which double as a chance to cancel before the charge rather than dispute it after.
  4. On the phone line in the descriptor, which should reach someone who can explain the charge and process a refund.

Before launch, charge a staff card and look at the result on a statement and in more than one banking app, since some apps display a shortened or reformatted name. Check it against your site header and your emails. Repeat after any rebrand, new domain or new product line, and tell your processor before the change, not after.

When a patient does ask their bank about a charge, purchase detail can settle the question before it becomes a chargeback. VyaPay's VyaShield shares purchase-inquiry data and automates dispute responses so more disputes stop before they become chargebacks, and because VyaPay runs its own processor, descriptor setup sits with the same team that makes the underwriting call. Ask us how your descriptor would read.

Frequently asked questions

Can I bill under a different company name to keep charges private?

Not if it's a name patients don't know you by. Under Visa's rules the merchant name has to be the one you primarily use with customers, and acquirers must correct names that confuse cardholders. Privacy comes from keeping conditions and drug names out of the descriptor.

What is a soft descriptor?

Another name for a dynamic descriptor: text your system sends with each transaction, within your acquirer's limits, that adds detail to your fixed merchant name, such as marking a charge as a renewal.

Should a telehealth descriptor include a phone number?

Where your acquirer supports it, yes, and it should reach a person who can explain the charge. A patient who can call you has less reason to call the bank.

Does a vague descriptor reduce chargebacks?

It can do the opposite. A name the patient doesn't recognize invites a call to the bank, and that call can end up as a fraud dispute on a charge that was legitimate.

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.