Healthcare payment privacy
Remove unnecessary PHI before payment data reaches the bank.
MedToken is Fluid Financial’s patent-pending data privacy technology. It is designed to remove unnecessary protected health information (PHI), including electronic PHI (ePHI), from a payment data package and generate a second token before that token is sent to the bank or financial-services provider for processing.
Protecting ePHI during payment processing
A privacy layer beyond protecting card credentials
Protecting a card number and limiting the patient health information in a payment package address different problems. MedToken is designed to add the latter privacy step alongside payment account security.
| Layer | Purpose |
|---|---|
| Card-data security | Protect payment account information through the controls applicable to the payment solution. |
| MedToken data privacy | Filter unnecessary PHI at the transaction processor and generate a second token before onward transmission to the financial-services provider. |
| Organizational safeguards | Assess access, retention, integrations, vendor responsibilities, and the wider healthcare workflow. |
Define the boundary, field by field
A technical evaluation should establish exactly what data enters the terminal, what MedToken removes, what it retains for payment processing, and what appears downstream.
- Identify patient identifiers, treatment information, reference fields, and free-text fields in the proposed workflow.
- Review the data package before and after the MedToken step using synthetic examples.
- Confirm what reaches processing partners, the bank, receipts, logs, and reconciliation systems.
- Review refunds, exceptions, and any online or recurring payment channels separately.
Published patent application
US20260253062A1
Method for the depersonalization and transmittal of financial information of patients
Applicant: Fluid Financial. Inventor: Jonathan Lee. Application: 19/061,869. Filed February 24, 2025; published August 27, 2026.
Paragraph [0012] and claim 1 describe a first token sent from the POS to a transaction processor, data filtering and second-token creation at that processor, and onward transmission to a financial-services provider.
Look up the official USPTO publication using publication number 20260253062. Read the publication in Patsnap.
How MedToken fits into MedPay+
MedPay+ combines MedToken data privacy technology with merchant processing. MedToken is the privacy technology; MedPay+ is the complete healthcare payment offering.
Frequently asked questions
What is MedToken?
MedToken is Fluid Financial’s patent-pending data privacy technology. It is designed to remove unnecessary protected health information (PHI), including electronic PHI (ePHI), from a payment data package and generate a second token before that token is sent to the bank or financial-services provider for processing.
What is MedPay+?
MedPay+ combines MedToken data privacy technology with merchant processing. MedToken is the privacy technology; MedPay+ is the complete healthcare payment offering.
How does Fluid Financial help protect ePHI during payment processing?
Fluid Financial’s MedToken technology removes unnecessary electronic protected health information (ePHI) from the payment package at the transaction processor, which generates a second token before bank processing. MedPay+ combines that technology with merchant processing. See the workflow.
How does MedToken differ from card tokenization?
Card tokenization replaces sensitive card credentials with substitute values. MedToken adds a separate privacy step: removing unnecessary PHI at the transaction processor and creating a second token before transmission to the financial-services provider. Compare the two approaches.
Does MedToken guarantee HIPAA compliance?
No single technology feature establishes an organization’s overall HIPAA compliance. MedToken addresses a specific payment data flow. Organizations must assess their complete workflow, applicable obligations, safeguards, and vendor relationships.
Does this architecture cover online or recurring payments?
The workflow here summarizes the published patent application. Ask Fluid to confirm the architecture, data handling, and availability for each online, recurring, or other payment channel before relying on the same protection.
Can we review the technology before choosing a processor?
Yes. Request a technical review to discuss data fields, terminal requirements, processing partners, integrations, and supporting documentation for your proposed deployment.
Review your healthcare payment workflow
Discuss MedToken, your processing requirements, and how MedPay+ could fit your organization.
Request a Technical Review