Tagada Rx for platform partners
You run a platform — a funnel builder, an agency, a telehealth enabler, a payment orchestrator — and your merchants (not you) sell the treatments. Tagada Rx is built so a partner can operate the whole clinical stack for a fleet of merchant stores without Tagada ever appearing patient-side.The decoupling promise applies fleet-wide. Every merchant store is a
standard Tagada store with the Rx add-on activated. Your merchants can use
Tagada-hosted storefront templates,
or you can keep them on your own funnel infrastructure and drive
everything through the Headless SDK
(browser) + Node SDK (your backend). Same
building blocks either way.
The two partner shapes
Payment layer only
Your merchants already have clinicians and pharmacies plugged in. They
apply with their LegitScript certificate; you take a markup on
processing (think Stripe Connect for regulated verticals). Integrate
headless with the Node SDK — no Tagada CRM required.
Full stack with TagadaRx
Your merchants need clinicians and pharmacies too. You operate the
white-label CRM; each merchant store activates the Rx integration
(clinical network, intake, cases, portal, ship-day rebilling). Your
margin flows through the CRM layer.
Fleet provisioning, per merchant store
Rx is activated per store, so a fleet is a loop over your merchants. From your backend, with your partner-scoped API key:affiliate (Tagada is
merchant of record, commission per case), and graduate to direct (their
own MIDs, full revenue) when volume justifies it — with zero storefront
changes.
Storefronts: hosted templates or your infrastructure
Option 1 — Tagada-hosted (fastest). Each merchant brand is one plugin instance of a storefront template mounted on its own domain — same code, per-brand config (branding, verticals, products, payment flow). Good when your merchants don’t have their own frontend stack. Option 2 — Your funnel infrastructure (headless). Your funnel builder renders the pages; the Rx bricks are API calls:(orderId, checkoutToken) pair. Your platform backend keeps the API-key
surface (tagada.rx.*) for provisioning and ops.
White-label rules
Patients must never see the platform plumbing:- Branding priority: the merchant’s brand first; the marketplace brand (e.g. TGD Care) when attribution is unavoidable; the platform name never.
- Storefront domains, transactional emails, questionnaires, and the patient portal all carry the merchant brand (hosted templates handle this via per-instance config).
- The white-label CRM is your operator surface: your team and your merchants manage cases, orders, and patients there under your brand.
Partner economics
Accruals post automatically at case submission (
accrualAmountMinor in the
submitCase response) and reverse automatically on clinician decline —
there is no billing call to make per case.
