MedToken · Data privacy
An additional privacy layer designed to remove unnecessary patient health information before payment information reaches the financial-services provider. Explore MedToken.
Healthcare payment privacy
MedPay+ brings together MedToken data privacy technology and merchant processing. MedToken strips unnecessary PHI from the payment package and retokenizes it before transmission to the bank.
An additional privacy layer designed to remove unnecessary patient health information before payment information reaches the financial-services provider. Explore MedToken.
MedToken combined with merchant processing for healthcare organizations. Review your payment acceptance needs and privacy workflow together. Explore MedPay+.
Understand your current effective rate and available pricing options alongside your privacy requirements. Upload & Analyze My Statement.
Understand the additional tokenization step and which information is needed for processing. Read the tokenization guide.
Review terminal configuration, downstream systems, integrations, and evidence for your proposed deployment. Prepare a security review.
Separate payment data safeguards from your wider HIPAA responsibilities. Read about healthcare payment privacy.
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.
MedPay+ combines MedToken data privacy technology with merchant processing. MedToken is the privacy technology; MedPay+ is the complete healthcare payment offering.
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.
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.
Discuss MedToken, your processing requirements, and how MedPay+ could fit your organization.
Request a Technical ReviewPreparing a regulatory review? Explore EO 14117 and healthcare payments and state health-data privacy, with official sources and practical questions for your team.