Payments

Your merchant account. Your money. Your margins.

Corevia is not a payment facilitator and never wants to be. You connect your own processor, you are the merchant of record, and settlement goes straight to your bank. Corevia never holds your funds and takes no percentage of GMV — the platform orchestrates the order, not the money.

How it works

Bring your own processor.

There are two lanes into the platform, and both of them end at your bank account. Nothing in the design requires Corevia to sit between you and your revenue.

Connect your own Stripe accountA standard OAuth connection, and the platform uses direct charges — so the connected account is the merchant of record, not Corevia. Their underwriting, their bank account, their chargebacks, their statement descriptor. You keep the processing relationship you negotiated.

Or your existing high-risk merchant accountThe second lane runs your current high-risk account through a supported gateway — Authorize.Net, NMI or Braintree. This exists because generalist processors commonly classify telehealth as a restricted category, and compounded therapies sit squarely in high-risk. The platform is built for that reality rather than pretending it away.

Settlement never passes through usFunds move from the patient's card to your processor to your bank. Corevia writes the order, the subscription and the reconciliation entry — it never receives, pools or disburses your money.

No money transmitter license, because none is neededCorevia never takes custody of funds, so it does not become a money transmitter and requires no MSB or money transmitter licensure. That is an architectural choice, not a legal opinion we are asking you to accept.

No percentage of GMVCorevia is paid for the platform, not for your volume. Your unit economics improve as you scale instead of being taxed by the vendor that processes the transaction.

Three hard constraints

The rules that shape the payment design.

Each of these is a line the platform will not cross, because crossing it would change what kind of company Corevia is — or what a card statement discloses about your patient.

PCI scope stays light — card data never touches Corevia servers

Checkout uses hosted fields and Elements rendered by your processor. The card number is captured inside their frame and exchanged for a token; Corevia sees the token, never the pan. Proxying a raw card number would drag a healthcare platform into full cardholder-data compliance, and that is a different company with a different audit surface. We decline the scope deliberately.

No PHI on the payment rail

Payment processors are not covered entities and most will not sign a Business Associate Agreement — so nothing that could reveal a condition is sent to them. The descriptor and the metadata carry an amount and an opaque order reference, and nothing else: no diagnosis, no medication name, no condition-revealing program name. Say it plainly — a medication name printed on a card statement is a disclosure, and it is read by whoever opens the envelope.

Telehealth merchant certification is yours, and we help you run it

Because you are the merchant of record, telehealth merchant certification — LegitScript being the one most processors ask for — attaches to your entity, not to Corevia. That is the honest consequence of owning your own account. We treat it as an onboarding workstream: we tell you what the certifier will ask for, supply the platform-side evidence about clinical workflow, licensure enforcement and prescribing controls, and sequence it alongside processor underwriting so it is not the thing that delays your launch.

Still the platform's job

What the platform still does.

Staying out of the funds flow is not the same as staying out of the commercial model. The billing logic lives with the clinical record, where refunds, pauses and prescriptions have to agree with each other.

Subscriptions and recurring programs

Monthly and multi-month programs, prepaid terms, titration-linked plan changes and mid-cycle upgrades, all executed on your account.

Recurring

Multi-party revenue splits

Brand, practice, pharmacy and platform shares modeled per program and applied per order, so the split is a rule rather than a spreadsheet.

Splits

Refunds and pauses, reconciled to the chart

A pause, a refund or a cancellation moves the clinical program with it — no patient left paying for a stopped therapy, and no therapy running on a canceled plan.

Reconciled

Per-brand pricing

Every brand on the platform carries its own catalog, price points, discounts and promotional rules — isolated from every other tenant.

Multi-brand

Failed payments that don't interrupt care badly

Retries, dunning and grace behavior are configured per program, so a declined card triggers outreach rather than an abrupt clinical stop where continuity matters.

Continuity

Reporting per brand

Revenue, retention, refunds and program-level performance reported per brand and roll-up, reconciled against the clinical record rather than against a payout file alone.

Analytics