CenterFuze Payment and Healthcare Product Terms
Effective date: January 1, 2026
Version: 1.0
These Product Terms supplement the CenterFuze Customer Subscription Agreement. They use the modular structure common to mature payment platforms, including Stripe, while remaining original CenterFuze terms. Capitalized terms not defined here have the meanings in the Customer Subscription Agreement. If these Product Terms conflict with the Customer Subscription Agreement regarding the Payment Services or Healthcare Module, these Product Terms control; the DPA controls Personal Data and the BAA controls PHI.
1. Payment Services
CenterFuze provides software that enables Customer to send authorized payment instructions and receive transaction information through supported processors, including CardPointe and Worldpay. The processor, acquiring institution, payment network, and Customer's merchant agreement govern authorization, settlement, reserves, disputes, chargebacks, prohibited businesses, and regulated payment services.
Customer, not CenterFuze, is the merchant of record unless an Order Form expressly states otherwise. Funds settle to an account designated and controlled by Customer through its payment provider. CenterFuze does not accept deposits, maintain stored value, hold or pool Customer funds, or independently determine the recipient or timing of settlement. CenterFuze may transmit a refund, void, debit, or credit instruction only as authorized by Customer through supported functionality or as required to correct an error or comply with law.
Approved workflows replace payment-card credentials with provider-issued tokens. CenterFuze stores those tokens and limited metadata required for authorized functions, including card brand, last four digits, expiration information, transaction identifiers, status, and amounts. CenterFuze does not store full PAN, CVV, PIN data, or magnetic-stripe/track data. Customer must not place such data in free-text fields, support requests, uploads, logs, or unapproved integrations.
CenterFuze maintains PCI DSS compliance for its applicable assessed service-provider environment. Customer is responsible for its own merchant environment, websites, scripts, users, endpoints, networks, processor agreements, and PCI DSS obligations. On reasonable request and subject to confidentiality and access controls, CenterFuze will make applicable compliance evidence available for qualified review.
Customer authorizes CenterFuze and supported providers to process transaction and account information needed to provide the Payment Services, prevent fraud, secure the Services, comply with network/provider rules, and satisfy law. CenterFuze is not responsible for a provider's underwriting decision, reserve, chargeback, settlement delay, account closure, or outage, but remains responsible for its own contractual obligations.
2. Healthcare Module
The Healthcare Module is the only CenterFuze service approved for PHI. It may support eligibility, benefits, claims, remittance, appeals, insurance, billing, and related administrative workflows identified in the Documentation or Order Form. It does not provide medical advice, diagnosis, treatment, or autonomous clinical decision-making.
The BAA is incorporated when Customer activates the Healthcare Module for PHI. Activation requires acceptance by an authorized Customer representative. Customer must not submit PHI before activation and must use only approved fields, workflows, integrations, and Authorized Users. Customer is responsible for minimum-necessary use, lawful authorization, workforce access, and the accuracy of instructions.
CenterFuze will apply safeguards required of it as a Business Associate, including access controls, MFA for supported access, role-based permissions, audit logging, encryption for supported data flows, daily backups, secure development and release practices, incident response, and subcontractor obligations where required. No statement in these terms is a government certification or guarantee that Customer's use is automatically HIPAA compliant.
Authenticated Healthcare Module pages will not intentionally use advertising pixels, behavioral advertising, marketing enrichment, or session-replay tracking. Essential security and operational telemetry must be configured to exclude PHI or operate under an agreement and configuration permitted by HIPAA. PHI submitted to an unsupported location may be quarantined and removed or rendered unusable under CenterFuze's incident, retention, and deletion procedures, subject to legal preservation duties.
After termination, PHI follows the BAA. Where return or destruction is feasible, CenterFuze will make supported exports available during the 90-day post-termination period and then delete PHI from active systems. Protected residual backup copies remain isolated from ordinary use and expire under the backup lifecycle, unless law requires retention or return/destruction is infeasible as addressed in the BAA.
3. Suspension and changes
CenterFuze may suspend a Payment Services or Healthcare Module workflow when reasonably necessary to address unlawful activity, a provider or network requirement, unauthorized sensitive-data submission, security risk, missing BAA acceptance, or material violation of these Product Terms. CenterFuze will limit suspension to the affected functionality and provide notice where practicable.
Material changes apply prospectively under the Customer Subscription Agreement. CenterFuze will maintain a version archive and require renewed acceptance when a change materially expands regulated-data processing or Customer obligations.
4. Contact
CenterFuze, LLC
433 Plaza Real, Ste 275
Boca Raton, FL 33432