Healthcare payment privacy
Understand the scope of product and compliance statements.
These disclosures explain how to interpret MedToken and MedPay+ information while evaluating a healthcare payment deployment.
Product names and patent status
MedPay+ combines MedToken data privacy technology with merchant processing. MedToken is the privacy technology; MedPay+ is the complete healthcare payment offering.
MedToken is patent-pending, as confirmed by Fluid Financial. A pending application does not establish a granted patent or an exclusive market position.
Security and privacy scope
The MedToken overview follows the published application: a first token goes from the POS to a transaction processor, which filters the data and creates a second token before forwarding it to the financial-services provider. Confirm device support, field handling, integrations, and channel-specific scope before deployment.
Product descriptions are not a guarantee of zero PHI exposure across all systems, immunity from penalties, or organization-wide HIPAA compliance.
Processing and pricing
Processing services, pricing, equipment, funding, and deployment timing depend on the selected arrangement and underwriting. Any fee-offset or dual-pricing option is subject to applicable requirements and eligibility.
Request the service terms and disclosures that apply to your proposed configuration.
Documentation and vendor relationships
Verify the current patent record and any security assessment directly. Review the scope and date of reports rather than relying on a general badge. Determine business-associate responsibilities from the services and information involved.
Prepare a technical review · Review HIPAA-related considerations.
Review your healthcare payment workflow
Discuss MedToken, your processing requirements, and how MedPay+ could fit your organization.
Request a Technical ReviewEO 14117 and state-law statements
MedPay+ product descriptions do not establish blanket compliance with Executive Order 14117, the DOJ Data Security Program under 28 CFR Part 202, CISA security requirements, or every state privacy law. Request the applicable assessment, control mapping, scope, exclusions, and implementation evidence before relying on a specific compliance representation.
Federal data-security guide · State health-data privacy guide.