Crypto Payments for Telehealth — the Consult Ends, the Dispute Window Shouldn't

The pain: fifteen minutes of care, four months of exposure

Look at a telehealth charge the way an issuing bank does. Someone pays $60, or $180, or $400 from a phone. There is no store, no card terminal, no signature, no shipment and no tracking number. The "product" was a conversation on a video call. Three weeks later the patient's symptoms haven't improved, the referral didn't go where they hoped, or a family member finds an unfamiliar line on the statement.

Then they call their bank.

Card-not-present is the highest-risk transaction category on the card rails, and telehealth is card-not-present by definition — there is no version of your business where the patient is standing in front of a terminal. That single structural fact puts you in the same underwriting bucket as digital goods and remote services, which is where the dispute rates and the pricing live.

The dispute reasons repeat with unnerving consistency:

• "Services not rendered." The patient attended the call, but nothing you can hand a bank looks like delivery.
• "Not as described." A clinical outcome the patient hoped for didn't happen, and dissatisfaction with medicine becomes a payments problem.
• "I don't recognize this charge." A descriptor the patient doesn't associate with the practice they booked, or a card shared inside a household.
• Subscription drift. A monthly care membership the patient forgot about, cancelled by disputing rather than by clicking cancel — often with several months clawed back at once.
• Stolen-card fraud. Remote, instant, internationally accessible services are attractive to card testers for exactly the reasons they're convenient for patients.

And here is the part that makes telehealth different from every other card-not-present vertical. When you fight one of these, the acquirer asks for evidence that the service was delivered. For a software company that's a server log. For you it's a session record, an appointment note, a prescription, a chart. You are being asked to route clinical information through a dispute pipeline built for shipping receipts, read by people with no relationship to your patient and no obligation under the confidentiality rules you operate under. Regulators treat telehealth as clinical practice with the full weight that implies — the U.S. Department of Health and Human Services' provider guidance is explicit that remote care carries the same privacy and record-keeping duties as care delivered in a room. So most practices make the rational choice: they don't submit the evidence, and they lose.

What an unsolved dispute problem actually costs a telehealth practice

Put numbers around it. Card-not-present healthcare and wellness services are commonly underwritten in the elevated tier: roughly 3.5%–6% plus a per-transaction fee, against 1.5%–2.9% for an ordinary low-risk merchant. On $300,000 of monthly consult revenue, the spread between a 2.5% baseline and a 5% high-risk rate is $7,500 a month — $90,000 a year before a single dispute is filed.

Then the disputes themselves. Each one carries a fee typically between $15 and $100, non-refundable whether you win or lose — and on a service with no delivery artifact you can safely disclose, you mostly don't win. Two hundred consults a month with a 1.5% dispute rate is three chargebacks: the refunded revenue, the fees, and staff hours assembling a case you'll probably abandon.

Then the ratio. Card networks run dispute-monitoring programs against your chargeback percentage, and the thresholds are unsentimental — Visa publishes its dispute monitoring program rules openly. Cross the line and you enter remediation; stay across it and the account closes. Mainstream gateways start getting nervous around 1%.

Then the reserve. Practices classified high-risk routinely have 5%–10% of volume held for up to 90 days. At $300,000 a month with a 10% / 90-day reserve, roughly $90,000 of your own revenue is parked in someone else's account — working capital you can't use to pay your clinician panel, license your platform, or acquire patients.

And then the thing that actually ends practices: termination. The account closes on notice, mid-month, reserve still held. Patient intake stops. Rebooking a card processor as a healthcare merchant takes weeks of underwriting during which you are treating patients you can't bill through your normal flow. Providers in sensitive specialties — mental health, sexual and reproductive health, weight management, dermatology, addiction medicine — hit this most often, because those are precisely the categories where acquirers de-risk first and ask questions later.

Why cards and bank rails fail telehealth specifically

None of this is a bad underwriter or bad luck. It's the architecture of the rail.

A card payment is a reversible promise, not a payment. Authorization gives you a claim that can be undone for roughly 120 days. Someone has to carry four months of risk on every consult, and it isn't the network — it's your acquirer, who prices it into the rate, the dispute fee and the reserve. The reserve isn't a punishment; it's collateral against a liability the rail genuinely creates.

Your risk score is set by how patients might feel later. Underwriting doesn't assess your clinicians' credentials, your platform's security or your outcomes. It estimates how often a dissatisfied remote patient calls their bank. Medicine has uncertain outcomes by nature, so the model itself generates the risk — no amount of clinical excellence removes it.

The defense mechanism is incompatible with confidentiality. Every other merchant fights disputes with delivery evidence. You'd be fighting them with patient information. That asymmetry means your effective win rate is far lower than your theoretical one, and acquirers know it, which is part of why the category prices the way it does.

The statement line is itself a disclosure. A card charge writes a permanent, third-party-readable record — visible to whoever else sees that statement — that a person paid a specific clinic. In sensitive specialties this generates real disputes from real patients doing damage control, and it makes some patients avoid the appointment entirely.

Cross-border care is where the rail simply stops. A specialist consulting patients in another country runs into international declines, FX markups the patient didn't agree to, and cards that plain don't work for the corridor. Meanwhile the payment your patient can actually make — a stablecoin transfer they already use for freelance income or savings — has no equivalent on your checkout page.

And you don't only collect; you pay. Modern telehealth runs on a distributed panel of contracted clinicians, often across many countries. International wires cost $15–$50, take 3–7 business days, bounce on a mistyped IBAN, and don't reach some of the countries your best clinicians live in.

How Payzum handles crypto payments for telehealth, in both directions

Payzum is a non-custodial, crypto-only payment processor. That one design choice removes most of what makes this vertical expensive — and it does it on both sides of the ledger, because a telehealth practice is simultaneously a merchant and a payer.

Intake: a consult fee that cannot be reversed

An on-chain payment is final once it confirms. There is no issuer, no 120-day window, no representment, and therefore no chargebacks. No dispute ratio to monitor, no monitoring program to be enrolled into, no dispute fees, no rolling reserve — and, critically for you, no situation in which defending your revenue requires disclosing anything about a patient's care. The evidence question never arises, because there is no dispute to answer.

You collect however your funnel actually works: hosted checkout (redirect, modal or inline in your existing booking flow), payment links and buttons generated per consult type and sent by email or messenger, invoices with expiration and overpayment detection for treatment plans and multi-session packages, and recurring subscriptions for care memberships. It's drop-in — it runs beside your current card checkout rather than replacing it.

Settlement: the money is already yours

Funds route directly to wallets your practice controls. Payzum never holds, pools or custodies them — settlement is the payment. There is no Payzum balance, so there is nothing for a risk committee to freeze, nothing to reserve, and no merchant account whose termination would strand your intake. Confirmation is fast enough to be operationally invisible: roughly 0.4 seconds on Solana, about 2 seconds on Base and Polygon — the patient is paid-up before they've joined the waiting room.

Volatility: quote and hold in dollars

Optional auto-conversion settles incoming crypto as USDC or USDT the moment it lands. Your consult prices stay dollar-denominated, your books stay dollar-denominated, and the fee you owe a contracted clinician next week is a dollar number backed by dollar-pegged reserves. Price risk never touches your balance sheet — which matters especially for practices operating in soft-currency markets, where the stablecoin is often the more stable side of the transaction.

Memberships: recurring care billing that doesn't die by dispute

Subscriptions cover the model most telehealth practices are moving toward: a monthly membership that includes messaging, a follow-up, and a scheduled review. On card rails that plan leaks constantly — expired cards, issuer declines, and cancellations executed as chargebacks that claw back several months at once. On-chain, recurring billing has no expiry date and no reversal path: the membership ends when the patient ends it, on your dashboard, where you can see it.

Payouts: your clinician panel, batched

The other half of the problem is paying people. Payzum does mass payouts: upload a CSV for BTC, LTC and DOGE, or send EVM stablecoin payouts across Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche. One batch, your whole panel of contracted doctors, therapists, nurse practitioners, interpreters and reviewers — minutes instead of days, from your own wallet, with no correspondent banks and no coverage gaps in the countries your clinicians actually live in. The same mechanism handles referral partners and affiliate arrangements where your jurisdiction permits them.

Controls your compliance officer will ask about

2FA, encrypted secrets, and a complete audit log of every movement in and out. Signed webhooks notify your platform the instant a consult fee confirms, so the appointment slot is released and the video room provisioned automatically — no human in the loop, no gap between payment and access. A REST API with API keys and an integration playground covers whatever your patient portal needs that hosted checkout doesn't. KYC is built into the product.

One honest note on privacy, because the temptation to overclaim here is strong: an on-chain payment carries no clinical information and produces no card-statement line item naming your practice. That is a genuine improvement for patients in sensitive specialties. It is not anonymity — public blockchains are public, and your own obligations for patient records, consent and data handling are unchanged by how the bill gets paid.

How it works, step by step

Two flows, both configured from the dashboard. Most practices have intake live within days, because there is no processing history to underwrite.

1. Connect the wallets you already control. One for patient intake, optionally a second for the payout treasury if your accountant prefers them separated. Payzum never holds keys — these are your wallets, on the chains you choose from Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche.
2. Price your services and turn on auto-convert. Create a payment link per consult type — initial assessment, follow-up, second opinion, urgent slot — and a subscription plan per membership tier. Enable auto-conversion to USDC or USDT so every payment lands dollar-pegged regardless of what the patient sent.
3. Wire payment to access. Drop hosted checkout into your booking flow, or send the link when the appointment is confirmed. Point signed webhooks at your platform so a confirmed payment releases the slot and provisions the video room automatically. No-shows who never paid stop consuming clinician time; invoices with expiration make "I'll pay before the call" a deadline instead of a hope.
4. Run the payout cycle. When your clinician settlement window closes, export approved amounts, map wallet addresses, and send the batch: CSV for BTC/LTC/DOGE, or EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche. Your panel is paid the same day, wherever they are.
5. Reconcile from the audit log. Every intake and every payout carries an on-chain reference and a dashboard record. Finance reconciles against a ledger that is independently verifiable — a materially easier conversation with an auditor than a processor statement plus a reserve schedule.

Use cases in telehealth

What this looks like in practice, for the kinds of providers that book calls with us:

• A mental-health practice losing memberships to disputes. Roughly 400 monthly members on a card-billed care plan, with a steady trickle of chargebacks that are really cancellations — several months reversed at a time, plus fees. They add a stablecoin option beside cards at signup. The cohort that takes it is younger, online-native and already holds USDT. That slice of the book now carries zero reversals, the blended dispute ratio drops below the monitoring threshold, and nothing changes for card-paying patients.
• A specialist consulting patients in other countries. Second-opinion consults at $250–$600, patients in Latin America, MENA and Southeast Asia, and a card checkout that declines a meaningful share of them outright while adding FX markups to the ones that pass. A payment link in USDC settles in seconds from any of those corridors, at the price that was quoted, with no correspondent bank in the middle. The same pattern medical tourism clinics use for deposits, applied to remote consults.
• A platform paying a 60-clinician panel across a dozen countries. Fortnightly settlements, most between $200 and $3,000, going to countries where wires cost more than the smallest payment is worth and take a week. They batch the whole cycle as USDC on Polygon or Base. The panel is paid the same day, "where is my payment" tickets disappear, and payment speed becomes a recruiting argument instead of a liability.
• A provider that just lost its merchant account. Terminated mid-quarter after a category review, reserve held 90 more days, replacement underwriting quoted at six weeks. Non-custodial crypto intake goes live in days because there is nothing to underwrite — connect a wallet, publish a checkout. The practice keeps billing while the new acquiring relationship is negotiated, and afterwards keeps the crypto rail as redundancy that costs nothing to hold.
• A hybrid clinic with a physical front desk. Remote consults billed by link and membership, in-person visits taken at the counter with a POS QR generated fresh per sale and PIN logins for reception staff. One rail, one ledger, both channels — with per-terminal analytics so the front desk reconciles at close.

Payzum vs a card processor for telehealth — comparison

Common objections, answered

Does this make our practice HIPAA-compliant, or handle patient data for us?

No. Payzum processes payments, not patient records — it never receives, stores or needs clinical information, and nothing here changes your obligations for records, consent, security or data handling under whichever regime applies to you. What changes is narrower and concrete: because on-chain payments can't be disputed, you are never asked to submit evidence about a patient's care to defend your revenue. That removes a specific, recurring conflict. It does not remove your compliance program, and you should build both with your own counsel.

Is this a way around licensing or telemedicine rules?

No, and it shouldn't be treated as one. Telehealth is regulated as clinical practice — licensure, cross-state and cross-border practice, prescribing, standards of care — and the rail you collect on has no bearing on any of it. Payzum works with providers that hold the authorizations their markets require. What changes is the payments layer: you stop paying a risk premium for reversal exposure that doesn't exist on-chain, and you stop depending on an account a third party can close.

Do enough of our patients actually pay in crypto?

You don't need all of them. Telehealth skews young, online-native and international — and the fastest-growing patient pools for cross-border consults are in exactly the regions where stablecoin balances are already ordinary. Every point of volume that moves on-chain is volume with no dispute exposure, no reserve and near-zero fees, and it pulls your blended chargeback ratio down at the same time. The economics work at the margin from the first month, which is why most practices start with it as an option rather than a replacement.

How do refunds work if there are no chargebacks?

Deliberately and by you. Finality means the patient's bank can't reverse a payment unilaterally; it doesn't mean you can't issue a refund. You send the funds back from your wallet under your own refund policy, on your own timeline, with an on-chain record of both legs. The difference is that your refund policy is set by your practice rather than enforced retroactively by an issuer four months later.

We already have a processor. Why add another rail?

Because redundancy in a de-risked category isn't optional, and this kind costs nothing to hold. Payzum is drop-in and runs alongside your existing checkout. Most practices start with one side — often payouts, where the pain is measurable in days and support tickets — and add intake later. The point is that the next category review or ratio letter becomes an inconvenience instead of an outage.

What about settling to our bank account?

Payzum is crypto-only and does not settle to a fiat bank account. Funds arrive as crypto — optionally auto-converted to USDC or USDT — in wallets you control, and converting to local currency is a step you run yourself through whatever off-ramp your jurisdiction and banking relationships allow. That's a real trade-off, and it's the honest counterweight to everything above: part of what a card processor's percentage buys you is the fiat leg and the custodial conversion that comes with it.