For ISOs · Partner-only since 2017

A gateway built for ISO portfolios.

Card-present and ecommerce on one stack. A non-compete that holds up under pressure. Reporting that lets you see what is happening in your portfolio before the bank calls.

For technical evaluation: Developer documentation (sandbox reference, no login required to read). For term definitions, use the payments glossary.

Why partners choose Fluid Pay
Non-compete by design Level 1 PCI · multi-region cloud 20+ products, one API
01What slows teams down

Problems we hear from ISO network programs

  • Residuals leaking to the gateway

    Many "partner-friendly" gateways quietly take direct merchants, run side ISO programs, or push referral fees that eat your margin. You need a structural non-compete, not a slogan in a deck.

  • A split stack across channels

    Different systems for terminals, ecommerce and CNP means different support queues, two onboarding flows, and reporting that does not line up. ISOs need one lifecycle view, not three.

  • Reporting you cannot run a portfolio on

    When you cannot see per-MID and per-channel behavior, the chargeback spike lands at the bank before it lands in your dashboard. Anomaly detection should not be a separate tool with a separate login.

02What changes with Fluid Pay

Outcomes we optimize for

  • One stack across every channel a merchant uses

    Virtual terminal, EMV terminals, ecommerce checkout, recurring billing, vault, surcharging. Same API, same dashboard. You train support once.

  • Reporting built for portfolio operators

    Per-merchant, per-MID, per-channel views. Anomaly flags so you see the chargeback spike before the bank does.

  • Migrations that do not require a rewrite

    The Gateway Emulator speaks the dialects of the legacy gateways most merchants are leaving, so the move is usually a config change, not a code project. The deal stays closed and the residual stays yours.

Next step for ISO network teams

Apply when you are ready for partnership review. Book a demo when you want a technical walkthrough first.