FluidPay Payment Gateway

FluidPay is a white-label payment gateway — the software layer that captures card and ACH data at checkout, in a hosted pay page, or through the virtual terminal, then routes it, tokenized, to the processor for authorization. It is CARDZ3N's preferred gateway: the stated preference order for new merchant boarding is FluidPay first, then NMI, with USAePay used for boarding. Merchants never see the FluidPay name on anything — every screen, receipt, and login carries CARDZ3N's own brand instead.

FluidPay in the CARDZ3N Stack

FluidPay operates on a partner-only, white-label model — it has never boarded merchants directly since going partner-only in 2017, and it never will. That non-compete structure is exactly why it fits CARDZ3N's stack the way it does: CARDZ3N is the sole quoting and selling party for every FluidPay account a merchant runs, configured and supported end to end, with FluidPay itself invisible behind CARDZ3N's own brand. PCI DSS Level 1 service and a 99.99% uptime target sit behind that brand without ever surfacing it.

CARDZ3N's gateway preference for new merchant boarding is FluidPay first, then NMI, with USAePay used for boarding — FluidPay earns the top spot on the strength of its product breadth: a 20+ product catalog spanning platform tools, payment acceptance, billing and revenue automation, security and vault services, fraud and risk tooling, and three distinct pricing programs, all switchable by configuration rather than re-integration.

The Customer Vault & PCI Scope

Customer Vault stores cards, ACH accounts, and addresses inside FluidPay rather than in the merchant's own systems — one vault instance powers the Virtual Terminal, Recurring Billing, Processa mobile POS, E-Invoicing, and the Tokenizer, so a payment method is stored once and charged everywhere. Because FluidPay is already a PCI DSS Level 1 service provider, storing card data this way typically drops the merchant's own PCI scope to SAQ A — the simplest self-assessment tier.

The Tokenizer is what makes that scope reduction work at checkout: a pre-built, themeable checkout UI component library — not iframes — with real form fields, autofill, and accessibility support. Card data goes straight from the customer's browser to FluidPay, so it never touches the merchant's servers at all, and the same fields can tokenize directly into Customer Vault within a live transaction. Multiple payment methods and addresses can be stored per customer, with shared customer records across multi-location or franchise groups.

Store once, charge everywhere — the same Customer Vault token that powers a Virtual Terminal sale also powers Recurring Billing, E-Invoicing, and Processa mobile checkout, with the Tokenizer keeping card data off the merchant's servers entirely.

WatchDog Fraud Protection

WatchDog is FluidPay's core fraud engine, launched in 2021: velocity filters, a community blocklist, and machine-learning scoring run on every transaction. Rules can act pre-authorization, declining a transaction before it ever hits the network, or post-authorization, flagging it for review — and because CARDZ3N owns the rulebook for its own merchant portfolio, the ML models adapt using CARDZ3N's own transaction data rather than generic internet-wide traffic.

WatchDog is really three layers working together. WatchDog Community Rules adds a crowd-sourced pattern layer — known attack patterns like card-spinning and BIN-testing, captured once across FluidPay's entire merchant base and pushed out to every opted-in merchant, positioned as a second line behind CAPTCHA rather than a replacement for it. AttackDog adds device fingerprinting, IP intelligence, and behavioral signal scoring, evaluated in milliseconds before authorization, with zero added friction for the legitimate buyer — no CAPTCHA, no OTP, no extra fields. Most partners run all three layers together.

  • WatchDog: velocity filters, community blocklist, and ML scoring on every transaction, priced per-MID
  • WatchDog Community Rules: crowd-sourced attack patterns pushed to every opted-in merchant
  • AttackDog: device, IP, and behavioral scoring in milliseconds, zero added customer friction
  • Partner-owned rulebook: templates defined by CARDZ3N, tuned by merchants within set bounds

Pricing Programs Compared

FluidPay runs Cash Discount, Dual Pricing, and Surcharging on one shared engine across the Virtual Terminal, hosted payment pages, ecommerce checkout, and supported card-present terminals — switchable by configuration, not re-integration. The three programs differ mainly in what happens at the register and what compliance work is required up front. Note: this covers how FluidPay's programs work; it isn't CARDZ3N pricing, which is quoted per merchant.

  • Cash Discount: single posted cash price, disclosed service charge on card, no network registration required
  • Dual Pricing: two posted prices shown transparently at every checkout surface, debit priced same as cash, no network registration
  • Surcharging: disclosed credit-only fee capped at the network 3.00% ceiling, debit auto-excluded, 30+ day network registration required
  • All three: real-time BIN lookup keeps debit and prepaid cards handled correctly before the auth call runs

Frequently Asked Questions

Common questions merchants ask before adding FluidPay to their CARDZ3N processing setup.

What is FluidPay?
Is FluidPay the same as CARDZ3N?
How does FluidPay's fraud protection work?
What's the difference between cash discount, dual pricing, and surcharging?
Does CARDZ3N sell FluidPay directly, or do I sign up with FluidPay myself?
Does the Customer Vault actually reduce my PCI compliance burden?

Bereit, dich anzumelden?

Machen Sie den ersten Schritt zum Erfolg und vereinbaren Sie Ihre kostenlose Beratung mit CARDZ3N