Healthcare payment privacy
Answers about MedToken, MedPay+, and payment privacy.
Understand the technology, the processing offering, and the questions to resolve for your deployment.
Product and privacy 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.
Implementation and pricing questions
Which practice systems integrate with MedPay+?
Ask Fluid to confirm support for your specific product, version, and workflow. Do not assume that an integration covers every payment channel or data field.
How much can our practice save?
Savings depend on your existing fees, transaction mix, and selected pricing model. Use StatementCheck to begin a review of your current statement.
How long does deployment take?
Timing depends on underwriting, equipment, integrations, configuration, and testing. Agree a deployment plan after the technical and processing review.
Is MedToken patent-pending?
Yes. Fluid Financial confirms a filed application remains pending. Request the applicable filing reference for due diligence; pending status is not a granted patent or security certification.
Review your healthcare payment workflow
Discuss MedToken, your processing requirements, and how MedPay+ could fit your organization.
Request a Technical ReviewFederal and state data privacy
How does MedPay+ relate to EO 14117? · What should providers review under state privacy laws?