HEALTHCARE PAYMENTS
Telehealth payment integration.
Copays, deposits, card on file, payment links and reconciliation, built around the patient journey and connected to your own processor.
6 min read · By Kevin Medina · Updated November 19, 2026
The short version
Telehealth platforms collect payments at booking, before the visit, after the claim and on recurring plans. We design and build the integration with your own processor, keep card data out of your scope where we can, and reconcile every payment to the encounter. We never hold funds and we do not hold payment licences.
Where payments show up in a telehealth journey
Telehealth rarely has one payment. It has several, spread across the patient journey, and each has different rules for timing, consent and failure handling.
| Moment | What happens | What the integration must handle |
| Booking | Deposit or no-show fee authorized | Authorization versus capture, release if the visit is cancelled |
| Pre-visit | Copay or visit fee collected | Amount from eligibility or the schedule, receipt back to the chart |
| Post-visit | Patient balance after the claim adjudicates | Payment link, partial payments, posting to the right encounter |
| Follow-up | Reminder and payment link by text or email | Expiring links, no card data in messages, status sync |
| Ongoing care | Membership or recurring plan | Stored credentials, consent record, retries and dunning |
Card on file and stored credentials
Card on file is where most telehealth payment work gets difficult. The card brands have rules for how a credential is first stored, how the patient consents, and how later charges are flagged as patient-initiated or merchant-initiated. A design that ignores those rules tends to show up later as declines.
- Store a token from your processor, never the card number.
- Record the patient's consent, the date, and what they agreed to charge.
- Flag first and subsequent charges the way your processor and the card brands require.
- Give the patient a clear way to update or remove the card.
Payment links
A payment link lets the patient pay from a text message or email without logging in to a portal. The link opens a hosted payment page, so the card details are entered on the processor's page and not in your app. Links should expire, tie to a single balance or encounter, and report their status back to the practice system. For teams that want a ready-made link flow, AskPay is one option. Teams with their own processor can also build links on the processor's hosted pages.
Refunds, partial payments and failed retries
- Refunds should reference the original payment and post back to the same encounter.
- Partial payments need a clear remaining balance and a rule for what applies first.
- Failed payments need a retry schedule, a patient-facing message, and a stop rule. Repeated retries on a declined card can cause problems with the issuer.
- Cancellations and no-shows should release authorizations as well as record fees.
PCI boundaries
The scope of your PCI work depends on where card data flows. Hosted fields and hosted payment pages keep card entry on the processor's side, and tokenization means your systems store a reference instead of the card. That generally shrinks the part of your environment that handles card data, but the exact scope depends on your integration. Confirm it with your acquirer or a qualified assessor before you design around it.
Healthcare adds privacy rules on top. Payment events can reveal that a patient received care, so treat receipts, messages and logs as health-related data and limit what they contain.
How we approach telehealth payment work
We do integration and engineering only. We never hold funds and we do not hold payment licences. You keep your own processor, merchant account and compliance program. The work follows the same three parts as all of our healthcare payment integration:
- Architecture. Map the payment moments, the systems of record, and the card data boundary before writing code.
- Integration. Connect the telehealth platform, your processor and the practice or billing system, with idempotent requests and clear error handling.
- Reconciliation and testing. Match payments, refunds and payouts to encounters, and test declines, partial payments and retries before launch.
Questions to answer before a build
- Which processor and merchant account will you use, and does it support hosted pages and tokens?
- Which payment moments are in scope: deposits, copays, balances, memberships?
- Where does the patient balance live today, and which system owns it?
- Do you need to support several providers, locations or entities?
- Which states or payers affect how and when you can collect?
For the longer version, read our blog post on designing payments around the patient journey.
Frequently asked questions
What is telehealth payment integration?
It is the engineering work of connecting a telehealth platform to a payment processor and to the practice or billing system, so copays, deposits, balances and memberships can be collected and posted to the right patient encounter.
Can we store a patient's card for later visits?
Usually yes, using a token from your processor, with the patient's consent recorded and each charge flagged as the card brands require. You should never store the card number yourself. Your processor and acquirer can confirm the exact rules for your setup.
How do payment links work for patients?
The patient receives a link by text or email and pays on a hosted payment page, so card details never pass through your app. The link should expire, tie to one balance, and report its status back to your system.
Does Paying.co process payments or hold patient funds?
No. We never hold funds and we do not hold payment licences. We integrate with your own processor and merchant account.
Does this affect our PCI scope?
Hosted fields, hosted payment pages and tokenization generally reduce how much of your environment touches card data, but scope depends on your design. Confirm it with your acquirer or a qualified assessor.
What do you need to scope a project?
Your telehealth or practice platform, the processor you use or are considering, the payment moments you want to cover, and where patient balances are kept today.
Building payments into a telehealth platform?
Tell us your platform, processor and the payment moments you need. We will scope the architecture, the integration and the testing.
Talk to us Book a meeting with a founder