Who Is the Merchant of Record in a Telehealth-Pharmacy Business Model?

The merchant of record in a telehealth-pharmacy business model is generally the entity that contracts with the patient for the charged service or product, identifies itself at checkout and on the card statement, controls pricing and refunds, receives the proceeds, and accepts transaction responsibility. In a multi-party arrangement, that answer must match the contracts, disclosures, licenses, and actual flow of funds—not just the entity operating the website.

Why this is a business-model question, not only a payments question

A medical group, pharmacy, management company, and technology platform may all participate in one patient experience. That does not mean they should all be presented as one seller or route every transaction through one merchant account.

The merchant-of-record decision affects customer authorization, refunds, chargebacks, processor underwriting, patient communications, and regulatory review. It also requires counsel to examine the structure under applicable state rules, including professional-entity, pharmacy, fee-splitting, ownership, consumer-protection, privacy, and telehealth requirements. Federal sources do not establish one universal merchant of record for every telehealth-pharmacy arrangement.

For payment-planning context, the healthcare payment-processing hub provides a broader starting point. The specific question here is narrower: which entity is actually selling what the patient believes they are buying?

A five-part test for identifying the merchant of record

Use this test as an investigation framework before completing a processor application. It is not a legal conclusion.

If different entities answer these questions, the structure may be acting like an agency, billing-service, marketplace, or principal-seller model. That difference should be resolved and disclosed rather than hidden inside a generic platform description.

Common telehealth-pharmacy structures

Separate clinical and pharmacy charges

The medical group may be the merchant of record for a consultation or other professional service it contracts to provide. The pharmacy may separately charge for prescription products it lawfully dispenses and sells. This model can make the transaction easier to explain when the receipts, refund rules, statement descriptors, and patient support contacts are also separate.

The medical group and pharmacy still need written agreements addressing communications, data handling, fulfillment questions, and responsibility for disputes. A technology platform can support the workflow without becoming the seller merely because it hosts the checkout experience.

A pharmacy charges for a combined offering

A pharmacy may charge one amount for medication-related services it is legally authorized to provide and represent. That does not automatically authorize the pharmacy to bill for clinical services performed by an independent medical group. Counsel should review the exact services, patient-facing language, professional relationships, and applicable state requirements.

FDA materials direct consumers to verify online pharmacies through state board resources and to confirm relevant pharmacy credentials and prescription practices. Website ownership or payment collection does not, by itself, establish authority to dispense or sell prescription products.

A platform or management company charges the patient

If a platform or management company sets the price, presents the bundle, takes payment, receives proceeds, controls refunds, and manages the customer relationship, an acquirer may view that entity as the principal seller rather than as a software vendor or limited billing agent.

That model can be commercially workable in some circumstances, but it usually requires closer review. The entity should not imply that it is the licensed clinician or pharmacy if independent organizations perform those roles. Its contracts should clearly address agency authority, funds flow, chargebacks, refunds, patient disclosures, protected health information, and regulatory responsibilities.

Management company bills on behalf of others

A management company may perform billing, collections, claims administration, or related payment functions for a covered entity. HHS describes payment functions broadly, and a third party may perform such functions under an appropriate business-associate arrangement when protected health information is involved.

However, performing billing for another entity does not automatically make the management company the principal seller or merchant of record. The checkout language, receipts, contracts, refund obligations, and flow of funds should support the limited role being claimed.

What underwriters are likely to examine

A processor or acquiring bank will generally want the proposed account to match the customer-facing business. Review may include:

• The legal entity and owners applying for the account;
• The name shown on the website, checkout page, receipt, and card statement;
• Whether the business sells clinical services, prescription products, subscriptions, or a bundle;
• The identities and licensing information of the medical group and pharmacy;
• Who controls prices, cancellations, refunds, and fulfillment complaints;
• Whether recurring charges are clearly disclosed and authorized;
• Prior refunds, disputes, complaints, and chargeback activity;
• Whether related entities are routing sales through one merchant account;
• Whether the applicant is acting as principal, agent, marketplace, billing service, or payment facilitator; and
• Whether PHI is shared with management or technology vendors under appropriate arrangements.

A mismatch between the legal merchant, checkout seller, statement descriptor, and entity receiving funds can create avoidable underwriting questions. It may also make it harder to show that a patient authorized the charge. FTC guidance emphasizes that businesses should take steps to ensure charges are authorized, particularly when recurring billing or negative-option terms are involved.

For related operational issues, review this guide to recurring billing, refills, and chargebacks in telehealth. Card-not-present pharmacy transactions also raise separate fulfillment and dispute questions discussed in card-not-present medication payment processing.

A pre-application investigation workflow

Before starting a confidential prequalification, assemble one transaction map:

• Describe the purchase. State whether the patient buys a consultation, a prescription product, a subscription, a bundled experience, or multiple separate items.
• Identify each contracting party. Match every promise in the checkout flow to the entity legally responsible for making it.
• Capture the patient experience. Save screenshots or drafts of the landing page, checkout, consent language, receipt, email confirmation, statement descriptor, cancellation instructions, and refund policy.
• Trace the money. Document which entity submits the charge, receives funds first, pays providers, and absorbs refunds or chargebacks.
• Map regulated roles. Identify the medical group, clinicians, pharmacy, platform, and management company without blending their independent responsibilities.
• Review data flows. Determine whether the management company or technology vendors access PHI and whether appropriate HIPAA agreements and controls are needed.
• Obtain counsel and processor review. Ask qualified counsel to evaluate state-law structure and provide the processor with a complete, accurate description of the model.

This workflow is more useful than selecting a merchant account first and trying to retrofit the business model afterward.

Questions to resolve before choosing who charges the patient

The following questions should be answered in writing:

• Who legally accepts the patient as a customer?
• Who decides the price and whether the patient is eligible for the service?
• Is the patient buying clinical care, medication, a subscription, or a bundle?
• Which entity appears on checkout, receipts, confirmations, and card statements?
• Who issues refunds and responds to chargebacks?
• Does the management company set medication pricing, take title to products, or resell them?
• Which entity receives patient funds first?
• Does any entity advertise itself as the clinician or pharmacy when it is not one?
• Are recurring charges, cancellation terms, and any pre-consultation charges clearly disclosed and affirmatively authorized?

The answers should align across the website, contracts, processor application, and internal operating procedures. If they do not, pause and resolve the inconsistency before launch.

How MDLaunchr fits into the evaluation

MDLaunchr is the brand behind WhiteLabelClinic.com, one platform in the white-label telehealth infrastructure category. It is not the treating medical group, pharmacy, law firm, regulator, or guarantor of payment-processing approval. Its role is to help qualified businesses evaluate and coordinate the technology, operational, compliance, clinical-network, and fulfillment relationships involved in launching telehealth services.

For a multi-party model, that coordination can help organize the transaction map and documentation questions. The final merchant-of-record structure still requires review by qualified legal, clinical, pharmacy, privacy, and payments professionals. Businesses ready to examine processing fit can start a confidential prequalification and explore how MDLaunchr and WhiteLabelClinic.com can support a compliance-first telehealth launch.

Frequently asked questions

Is there one federally required merchant of record for telehealth pharmacies?

No single federal rule in the reviewed sources assigns that role to every telehealth-pharmacy arrangement. The designation depends on the actual contracts, customer disclosures, services, funds flow, authority, and underwriting presentation. State-specific legal review remains necessary.

Can a management company be the merchant of record in healthcare?

It may be possible in some structures, but operating a website or performing billing does not automatically make the management company the principal seller. If it controls pricing, presents the offer, receives funds, and handles refunds, the arrangement may receive closer review. Counsel should evaluate agency authority, professional-entity rules, pharmacy rules, fee-splitting concerns, and consumer disclosures.

Does HIPAA determine who the merchant of record is?

No. HIPAA covered-entity and business-associate status are separate from merchant-of-record status. A company may perform payment or practice-management functions for a covered entity, while the underlying medical group or pharmacy remains the customer-facing seller.

Should a medical group and pharmacy use separate merchant accounts?

Separate accounts may provide a clearer structure when the medical group charges for professional services and the pharmacy charges for products it lawfully dispenses. It is not a universal requirement. The appropriate approach depends on the transaction design, contracts, disclosures, funds flow, and applicable state review.

What should a business submit during prequalification?

Prepare entity and ownership information, website and checkout materials, patient agreements, pricing and refund policies, statement descriptors, clinical and pharmacy relationship documents, funds-flow diagrams, recurring-billing disclosures, and relevant privacy or HIPAA documentation. Describe the full model accurately rather than presenting a management company or platform as a simple software vendor if it controls billing.

Disclaimer

This article is for general educational and business-planning purposes only. It is not legal advice, regulatory advice, payment-processor advice, medical advice, or a determination that any particular business structure is permitted. Laws, licensing requirements, processor policies, and enforcement positions can change. Consult qualified counsel and appropriate clinical, pharmacy, privacy, and payments professionals before launching or changing a telehealth-pharmacy model.