CARDZ3N — HomeContact us today for personalized advice and strategic solutions tailored to your Canadian business.
Call us
+1 (702)-623-3528FluidPay 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 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.
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 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.
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.
Common questions merchants ask before adding FluidPay to their CARDZ3N processing setup.
FluidPay is a white-label payment gateway — the software that captures card and ACH data at checkout, on a hosted pay page, or in a virtual terminal, and routes it, tokenized, to the processor for authorization. It's CARDZ3N's preferred gateway, with a stated boarding preference of FluidPay first, then NMI.
No. CARDZ3N is the partner and reseller; FluidPay is the white-label platform underneath. FluidPay runs on a partner-only, non-compete model and never boards merchants directly, so you never see the FluidPay name — every screen, receipt, and login carries CARDZ3N's own brand, and CARDZ3N is always the quoting and selling party.
Through the three-layer WatchDog stack: WatchDog itself runs velocity filters, a community blocklist, and ML scoring on every transaction; WatchDog Community Rules adds crowd-sourced attack patterns shared across FluidPay's whole merchant base; and AttackDog adds device, IP, and behavioral scoring evaluated in milliseconds before authorization, with no added friction for the legitimate buyer. Most partners run all three together.
Cash Discount posts a single cash price with a disclosed service charge added for card payments, and needs no network registration. Dual Pricing posts two separate prices — cash and card — shown transparently at checkout, also with no registration required, and prices debit the same as cash. Surcharging adds a disclosed, credit-only fee capped at the network's 3.00% ceiling, with debit and prepaid automatically excluded, and it requires 30-plus days of network registration through the acquirer before it can go live.
Always through CARDZ3N. FluidPay's partner-only model means it never boards merchants on its own — every FluidPay account a CARDZ3N merchant runs is configured, quoted, and supported through CARDZ3N, the same as every other service and terminal CARDZ3N provides.
Yes. Customer Vault stores card, ACH, and address data inside FluidPay rather than your own systems, and the Tokenizer's checkout fields send card data straight from the browser to FluidPay — it never touches your servers. Because FluidPay is already a PCI DSS Level 1 service provider, this combination typically drops a merchant's own PCI scope to SAQ A, the simplest self-assessment tier.
Start protecting your revenue from chargebacks today — schedule your complimentary consultation with CARDZ3N's Canadian dispute management specialists.