White Label Payment Gateway: How Reselling Works
Payment Processing Fundamentals

White Label Payment Gateways: How Agencies and SaaS Firms Resell Payments

A white label payment gateway lets agencies and SaaS firms sell payments under their brand. See the revenue math, network rules and when PayFac fits.

Five smiling colleagues stand together in a bright modern office with desks, glass walls and potted plants

Photo: Pixabay

On this page 6 sections
  1. What a White Label Payment Gateway Rebrands and What Stays the Same
  2. Who Resells Branded Gateways
  3. The Revenue Math, Including One Fast-Growing Client
  4. Four Rules Agencies Get Wrong
  5. White Label Gateway vs. Payment Facilitator vs. Referral Partner
  6. Questions to Put to Every White Label Provider

Key takeaways

  • Clients who are growing pay you more through processing residuals than through gateway markup, so put most of your negotiating effort into how the residual program defines profit.
  • Since March 31, 2025, an iframe checkout makes your client answer for every script on the payment page under SAQ A. A redirect to the provider's hosted page doesn't.
  • Taking client sales through your own merchant account counts as laundering under card network rules, and a MATCH listing generally lasts five years.
  • Visa requires a direct acquirer agreement once a sponsored merchant passes $1 million a year in Visa volume. That limits how far a PayFac can keep its largest users in-house.

A white label payment gateway is gateway software sold under your brand instead of the provider's, which agencies, ISOs and software companies resell to clients as their own product. You earn the gap between your wholesale cost and the fees you charge, plus processing residuals if you also place the merchant accounts. The one thing you can't rebrand is the merchant account. Every client still needs its own, approved by a bank-sponsored acquirer, and that rule sets the limits of what you can build.

Card payments run on three pieces that people tend to lump together. The gateway captures and encrypts card data from a checkout, invoice or virtual terminal and passes it on. The processor routes the transaction to the card networks. Underneath both sits the merchant account, the contract with an acquiring bank that lets a business accept cards and get paid. A white label deal, also sold as a private label payment gateway, rebrands the first piece and nothing else.

What a White Label Payment Gateway Rebrands and What Stays the Same

The parts you can usually put your name on:

  • the merchant login and reporting dashboard
  • the virtual terminal
  • hosted payment pages and payment links
  • recurring billing screens
  • emailed receipts
  • developer documentation, on fuller programs

Branding depth varies by provider. Fuller programs run the dashboard on your own domain and send receipts from your own email address. Basic tiers swap in your logo and colors and stop there. Behind the screen, the gateway company still runs the servers and the card vault.

Your brand ends at the software. The cardholder's statement shows your client's business name, the client's merchant agreement names the acquiring bank, and Visa and Mastercard rules apply exactly as they would with the provider's logo on the login page.

Who Resells Branded Gateways

Web design and development agencies are the most natural fit. An agency that builds WooCommerce or Magento stores already chooses each client's payment setup, so putting its brand on the gateway turns that choice into recurring revenue. It also means the client calls a familiar agency when checkout breaks. MannyPay works with web design firms on client payment setups, including gateway integrations with WooCommerce and BigCommerce.

ISOs and independent agents use branded portals so a merchant sees one name from the first sales call to the last support ticket. A small sales office with its own virtual terminal and dashboard looks established, and merchants have less reason to go around the agent to the gateway company.

SaaS platforms want payments inside the product. A gym membership tool needs recurring billing that keeps stored cards current. A wholesale ordering portal has buyers who expect ACH plus the extra invoice data that corporate cards reward, covered in our guide to Level 2 and Level 3 processing for B2B cards.

Online marketplaces often start here and outgrow it. A branded gateway works while every seller has its own merchant account. Once you want to take one payment and split it among sellers, you are in payment facilitator territory, covered below.

The Revenue Math, Including One Fast-Growing Client

Resellers earn from two main streams. The first is a markup on gateway fees: you buy access at a wholesale monthly and per-transaction price and resell it at prices you set. The per-transaction spread matters for clients with many small orders and barely registers for a contractor sending a few large invoices.

The second is a processing residual, earned when you place the merchant account itself as an agent or ISO. You receive a share of the margin between what the merchant pays to process and your buy rate, monthly, for as long as the merchant processes and your contract stays in force. Agencies often add a third source: setup fees, or a care plan that bundles payments in without itemizing them.

Every figure in this example is illustrative, not a quote or a typical market rate. Assumptions: 40 client merchants, each processing $15,000 a month in card sales. You pay $10 a month per merchant for gateway access and charge $25. After the split with your provider, your share of the processing margin equals 0.2% of client volume. Per-transaction gateway fees are left out to keep the math readable.

Income streamCalculationMonthly
Gateway fee margin40 × ($25 − $10)$600
Processing residual$600,000 × 0.2%$1,200
Total$1,800

That is $21,600 a year before your own costs, and support time is the biggest of them, because merchants call whoever's name is on the login screen.

Now look at a single client. Under these assumptions, a typical $15,000-a-month store earns you $45 a month: $15 in gateway margin and $30 in residual. If one store grows to $100,000 a month, its gateway margin stays at $15 while its residual rises to $200, for $215 in total. That one client is worth nearly five typical ones. Gateway margin grows only when you add clients; residuals grow when existing clients sell more. If your client list includes a few stores that are scaling, the residual side of the deal deserves most of your negotiating attention.

That negotiation starts with how a program defines profit, before the split percentage. A generous split of a padded buy rate can pay less than a smaller split of a clean one. MannyPay's agent and ISO partner program offers up to 80% true profit splits with no markup on buy rates, plus monthly residual payments and detailed monthly reporting.

Four Rules Agencies Get Wrong

Running Client Sales Through Your Own Account Is Laundering

Collecting client payments through the agency's own merchant account and paying clients out later is not white labeling. The card networks allow one business to accept cards on behalf of others only through a registered structure. In Visa's payment facilitator model, the facilitator contracts with an acquirer, signs each sponsored merchant, and receives and distributes settlement on their behalf. Mastercard's rules require the acquirer to register a payment facilitator with Mastercard.

Without that registration, the arrangement is treated as laundering (also called factoring), one of the reasons an acquirer can terminate a merchant and add it to MATCH, Mastercard's file of terminated merchants and their owners. Acquirers check MATCH before approving new accounts, and a listing generally stays for five years unless the acquirer that added it removes it. The clean structure is for each client to apply for and own a merchant account in its own name.

Iframe and Redirect Checkouts Aren't the Same Under PCI DSS

Ask the gateway provider for its PCI DSS attestation of compliance. That document covers the provider's systems, not your client's website.

Most agencies already know that hosted payment pages keep card entry off the client's server and qualify the client for SAQ A, the shortest self-assessment. Fewer know that the method of embedding now matters. The PCI Security Standards Council removed two script-security requirements from SAQ A effective March 31, 2025, and replaced them with an eligibility criterion: the merchant must confirm its site isn't susceptible to script attacks that could affect its e-commerce systems. Per PCI SSC FAQ 1588, as summarized by SecureTrust, that criterion applies to sites that embed the provider's payment form in an iframe, not to sites that redirect customers to the provider's hosted page.

So the agency's build choices land in the client's compliance paperwork. A redirect keeps the client's SAQ A simplest. An iframe looks better but makes the client answer for every script on that page, including the analytics and chat widgets the agency installed. A custom checkout that posts raw card numbers through your server pulls that server into scope. Plan fraud controls in the same conversation, including 3-D Secure authentication and clear rules for AVS and CVV mismatches.

Underwriting Belongs to the Acquirer

You submit applications; the acquirer decides who is approved. Clients in regulated categories such as CBD or vape need an account underwritten for the business they actually run, with the correct merchant category code (MCC). That usually means a high-risk merchant account, and the legality of their products varies under state and federal law. Placing them on a low-risk account under a vaguer description ends with the merchant losing the account and your standing with the acquirer damaged.

Loss Liability Is Set by Your Contract

Chargebacks hit the merchant's account first. Your role decides who pays when a merchant can't cover them. Referral partners and most agents carry no merchant losses. An ISO's liability is assigned in its agreement with the sponsoring bank, and many of those agreements push losses to the ISO. Read the liability, reserve and indemnification clauses before you sign, and have a lawyer review them; this section is general information, not legal advice.

White Label Gateway vs. Payment Facilitator vs. Referral Partner

Referral partnerWhite label gateway resellerPayment facilitator (PayFac)
Brand clients seeThe provider'sYours on the softwareYours, including onboarding
Who underwrites merchantsAcquirerAcquirerYou, under the sponsor's rules
Merchant accountEach client's ownEach client's ownSub-merchants under your master account
Loss liabilityNoneSet by contractYours, to your acquirer
Onboarding speedStandard underwritingStandard underwritingFast for low-risk sellers
Effort to launchLowModerateHigh: registration, KYC, monitoring, reserves
Share of processing marginSmallestModerateLargest

As a referral partner, you introduce merchants and collect a share without running anything. A white label reseller puts its brand on the software and takes on first-line support. A payment facilitator goes much further: it onboards sub-merchants under its own acquirer contract, handles identity checks and sanctions screening (what online sellers must screen under OFAC is a useful primer), monitors transactions, and absorbs losses its sub-merchants can't cover. Visa's rules hold the acquirer responsible for the acts of both its facilitators and their sponsored merchants, which is why sponsors scrutinize facilitators closely.

Two Visa rules shape the decision for software companies. A sponsored merchant that passes $1 million a year in Visa volume needs a direct merchant agreement with the acquirer, according to Visa's Core Rules as summarized by Tagada, so your largest users may end up contracting with the bank anyway. And Visa's payment facilitator and marketplace risk guide requires a facilitator to register as a High Risk Internet Payment Facilitator before signing high-brand-risk merchants. A platform serving vape shops or nutraceutical sellers takes on more than a typical PayFac.

PayFac status makes sense when payments are central to your product, your users are many small businesses that want to take payments the day they sign up, and you have capital for reserves and staff for risk work. Marketplaces that split payouts end up here; most agencies and early-stage SaaS companies don't. Managed PayFac providers sit in between, giving you branded onboarding while they carry most of the registration and risk work in exchange for a smaller margin share. Our guide to embedded payments for SaaS works through that trade-off.

Questions to Put to Every White Label Provider

Ask each provider the same questions and get the answers in writing.

  • Branding depth. Own domain and email sender, or only a logo swap?
  • Token portability. A written commitment that the card vault can be exported if you leave. Without it, your clients' saved cards stay with the provider.
  • Processor choice. Connections to more than one processor, so you can move merchants when pricing or approval terms change.
  • Platform fit. Support for the carts and accounting tools you build on; start with the payment gateways and integrations your clients already run.
  • Recurring and B2B features. Card-on-file updating, ACH, and Level 2 and Level 3 data fields.
  • Checkout options. Both redirect and iframe hosted pages, so each client can choose its PCI DSS path.
  • Support split. Who answers a merchant's late-night call when the gateway is down.
  • Contract terms. Residual vesting, termination, non-solicitation and loss liability, line by line.

This week, list your ten largest clients with each one's monthly card volume, average ticket and checkout platform. Send that list to every provider you're weighing and ask them to model your margin on those numbers instead of a sample client. If you'd rather test demand before your brand goes on anything, sign up as a MannyPay referral partner or talk to the MannyPay team. Clients who need a merchant account now can request a free quote; a MannyPay specialist responds within one business day.

Sources

  1. Visa's Payment Facilitator Model (Visa)
  2. Visa Payment Facilitator and Marketplace Risk Guide (Visa)
  3. Find a Payment Facilitator (Mastercard)
  4. PCI DSS v4.0.1 Requirements: Key Updates and What They Mean for Small Businesses (SecureTrust)
  5. PCI DSS v4.0 and the Evolution of the SAQ for E-commerce Merchants (VikingCloud)
  6. Payment Facilitator: Visa Rules and How to Register (Tagada)
  7. Mastercard MATCH List: What It Is and How to Get Off It (Chargebackstop)
  8. Payment Facilitator Operational Guidelines & Procedures (NetPay)

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading