Telehealth payment processing becomes difficult when a single price hides several different services. A customer may believe they bought medication, while the business records a consultation fee, a membership and a separate pharmacy charge. If clinical eligibility or fulfillment changes, staff need to know exactly what was purchased and what should happen to the payment.
GLP-1 compounding developments make that clarity particularly important. This article reviews US federal sources checked September 21, 2026 and the operating questions a merchant should bring to a payment consultation. It does not advise patients on treatment or decide whether a particular prescription or compounding arrangement is lawful.
Retire the old shortage-era explanation
FDA's April 1, 2026 clarification says semaglutide and tirzepatide are absent from both its shortage list and the 503B bulks list. It distinguishes individual-patient compounding under 503A from outsourcing-facility conditions under 503B. A prescriber-documented significant difference matters to the 503A copy analysis; simply calling a product personalized does not establish the applicable exemption. The same FDA page records the earlier shortage-related enforcement-discretion timelines, which ended in 2025. FDA compounding-policy update.
Do not carry a 2024 explanation into your current checkout, application or customer script without review. Ask the clinical and pharmacy team to document the present basis for the actual service, including the entities involved and destinations served. The payment team should receive the resulting operating requirements, not attempt to make the clinical determination.
Distinguish proposals from current requirements
On April 30, 2026, FDA announced a proposal to exclude semaglutide, tirzepatide and liraglutide from the 503B bulks list. Describe that source as a proposal, not a finalized new prohibition. A later notice extended comments through July 30, 2026. The primary materials reviewed for this article do not establish a later final determination. FDA proposal; Federal Register extension.
That distinction does not create permission to compound or process payments. Existing requirements still matter. Build a scheduled source review into your operating process, with a named owner and an instruction for pausing affected offers when your qualified advisers identify a problem. A saved screenshot of a supplier's old FAQ is a poor substitute for a current assessment.
Marketing and product sourcing must agree
In March 2026, FDA announced warning letters to 30 telehealth companies over allegedly false or misleading compounded GLP-1 claims. Issues included implying sameness with approved drugs and obscuring the source through branding. The announcement explains that compounded drugs are not FDA-approved or the same as approved generics. Warning letters communicate the agency's concerns; they are not court judgments against every telehealth business. FDA warning-letter announcement.
Review the complete customer journey for ownership and sourcing clarity. Who provides the consultation? Who dispenses? Who charges the customer? Who handles a failed delivery? If different organizations perform those jobs, give staff a map that matches the customer-facing disclosures and the payment agreement.
Avoid branding that leaves the support agent unable to explain which entity supplied the service. That confusion can become a refund problem even when the transaction technically succeeds.
Define the event that earns each charge
Create a simple service ledger before discussing automation. List the consultation, ongoing membership and medication-related component separately where those components exist in your actual model. For each, document the price, the event authorizing payment, the event recording delivery and the person responsible for a correction.
Walk through the situation in which a consultation happens but no prescription follows. Then walk through a prescription followed by a fulfillment delay. Your clinical obligations, reviewed terms and commercial arrangements should determine what is charged or refunded. A payment integration should implement those decisions consistently.
Do not assume a successful card authorization means a service has been delivered. Staff should be able to distinguish an appointment booked, consultation completed, pharmacy handoff accepted and order shipped. Choose system labels that describe confirmed facts rather than a single ambiguous “complete” status.
Design exceptions before adding recurring billing
A renewal can arrive while an earlier order is unresolved. Decide how the business detects that condition and which team reviews it. If fulfillment is unavailable, an automated payment cycle should not continue simply because nobody updated a spreadsheet.
Build a support path for duplicate charges, partial refunds, canceled appointments and membership cancellation. Record the original transaction reference, the action taken and the customer communication. Keep clinical records in the appropriate clinical system; a payment-support view should contain only the information its users need.
Test the handoff using synthetic records. Simulate a delayed pharmacy response, a repeated system notification and a refund that succeeds at the provider but has not yet updated the customer portal. The team should have a clear way to investigate each result without creating an extra charge.
Our payment-integration planning guide explains how to define these system responsibilities before writing the connection.
Bring the actual business model to underwriting
A telehealth merchant account discussion should identify all participating entities, websites, products, services and payment flows. Include relevant licensing and pharmacy documentation for qualified review, available processing history, refund experience and prior provider notices.
Explain whether the business takes payment for its own service or routes funds connected to another provider. Describe recurring charges, average transaction values and the time between payment and delivery. These facts help establish the questions that must be resolved; this article does not promise eligibility with any processor or gateway.
Stratamize's high-risk ecommerce assessment provides a starting point for the commercial workflow. Healthcare-specific legal, clinical and privacy decisions belong with the appropriate specialists.
The operational checklist
- Replace outdated shortage explanations with a dated source review.
- Identify consultation, membership, dispensing and fulfillment responsibilities.
- Match each charge to a clearly described service and authorization event.
- Define no-prescription, delayed-fulfillment and cancellation outcomes.
- Ensure marketing accurately identifies product status and sourcing.
- Test duplicate notifications, refunds and unresolved renewals.
- Prepare an honest account file covering every entity and sales channel.
Questions telehealth operators ask
Are all compounded GLP-1 arrangements prohibited?
This article does not make that blanket claim. The FDA materials describe different conditions and restrictions. Have the specific arrangement reviewed; a generic telehealth label cannot establish compliance.
Can changing payment providers resolve a product-status issue?
No payment approval changes FDA requirements. Establish the service and product position first, then assess provider eligibility and technical fit.
Should the first meeting include patient records?
Use redacted or synthetic workflow examples. Explain the handoffs and payment problem without sending patient charts or identifiable medical information.
Scope the payment work with Joseph
Book with Joseph to map the commercial journey, identify account-preparation gaps and scope the payment connections. Bring the service description and one exception your staff struggles to resolve. That gives the discussion a concrete starting point while qualified clinical and legal advisers handle the decisions within their disciplines.