Partner-only since 2017 · PCI DSS Level 1 · Built in Franklin, TN

One gateway for every channel your merchants run. And it doesn't sell to them behind your back.

Fluid Pay is a payment gateway for ISOs, agent groups, ISVs, and vertical SaaS platforms. Twenty-plus products on one API and one dashboard. We have never boarded a merchant ourselves, and that is not changing.

For technical evaluation: Developer documentation (sandbox reference, no login required to read).

Powering the stack for

ISOs & Agents Independent Software Vendors Platform & marketplace operators

Active merchants

12,408 +214

Monthly volume

$48.2M

Auth rate

99.2%

  • ApprovedVISA •• 4242 $124.502s
  • SettledMC •• 8801 $48.0014s
  • ApprovedAMEX •• 0039 $2,310.0031s
  • RefundedVISA •• 1199 −$19.991m
  • ApprovedDISC •• 7722 $89.992m
{ "amount": 12450, "currency": "usd", "source": "tok_2Nz…" }

Reliability

99.99%

Gateway uptime, rolling 12 months

Track record

2017

Partner-only since day one. No direct sales motion.

Non-compete

0

Merchants we have ever boarded ourselves

Compliance

L1

PCI DSS Service Provider

01/Who sells Fluid Pay

Six kinds of partner. One platform underneath.

ISOs, agent groups, ISVs, vertical SaaS, acquirers, white-label resellers. Each has a page written for how it actually goes to market. Same API and dashboard underneath.

02/Why this exists

Most gateways quietly compete with the partners selling them.

They run their own BIN. They take merchants direct. They bolt new features onto fifteen-year-old infrastructure and call it modern. Your portfolio pays for it, and your margins do too.

The gateway becomes the competitor

Their PayFac or BIN means every merchant you sign is a merchant they could quietly take next quarter.

Legacy, on-prem stack

Single-region racks and weekend deploy windows. Outages are scheduled, scale isn't.

Pricing that won't sit in a spreadsheet

Tiered surcharges, mystery fees, and cliff renewals that quietly chew through your residuals.

Tooling you can't brand

Their logo on your merchant portal. Their support emails. Your brand, demoted.

Runs in the cloud, not in a rack

Google Cloud, multi-region failover, auto-scaling, continuous deploys. Volume spikes don't turn into support tickets.

White-label down to the SSL cert

Your brand on the merchant portal, the receipts, the emails, the terminal screens. We stay out of every surface a merchant sees.

Non-compete by design

No PayFac. No BIN. No direct boarding team. We don't underwrite merchants. We build for the partners who do.

WatchDog fraud engine

Rules and ML that learn from your portfolio, not generic internet traffic. Sensitivity tunes per MID, not per vendor default.

Reporting that actually loads

Sub-second portfolio queries. Decline reason codes, attempted fraud, settlement timing. Filter and export without leaving the page.

Processor-agnostic

Switch acquirers without ripping out the gateway. Same API, same dashboard, same merchants on the other side of the move.

04/The non-compete, in writing

Four lines we will never cross.

The whole business is built on one premise: we do not compete with the partners selling us. It is not a clause buried in a contract. It is the shape of the company, and it has not moved since 2017.

  • We will never board a merchant directly.
  • We will never underwrite a merchant account.
  • We will never share your portfolio data with anyone, including other partners.
  • Your customers stay your customers. Full stop.

100%

Non-compete commitment

PCI DSS Level 1, multi-region cloud, audited annually. Zero merchants boarded direct. Zero portfolio raids on partners. Zero plans to change any of it.

06/From a partner

“Fluid Pay figured out what we needed on the first call. A gateway that works for us, not around us. The non-compete is not a slide in a deck. It is how the company actually operates.”

IP

ISO partner

Southeastern U.S., 10+ years in payments

07/Next steps

Two ways in. One partner-only platform.

Apply when you want partnership review and onboarding. Book a demo when you want a technical walkthrough first. Same team on the other end either way.