Features Are Table Stakes. Here's What Actually Makes a Gateway Defensible.

TL;DR

1. Routing, tokenization, hosted forms and SDKs are standard. If a gateway pitch leads with them, it is selling what everyone has.
2. In high-risk, the parts that are hard to copy are acquirer connectivity and risk tooling that keeps a portfolio healthy. Both take years.
3. White-label switching costs are real. Once your brand, your merchants' tokens and your routing run on a gateway, leaving is a project. That is a reason to choose carefully, not a selling point.
4. Pricing (a fixed fee per transaction, no basis points, no revenue share) is a wedge, not a moat. Anyone can copy a price.
5. Deployment choice (on-prem or cloud) matters to some PSPs. It is a smaller advantage.

Stop comparing feature lists

Put five gateway websites side by side and you'll find the same list: multi-acquirer routing, failover, tokenization, a hosted payment page, an iFrame, Pay-by-Link, plugins, mobile SDKs, 3-D Secure. IPG39 has all of them. So do most serious competitors.

That's fine. Table stakes matter. A gateway without failover or tokenization isn't a candidate. But a feature an engineering team can ship in a quarter isn't what keeps an ISO or PSP on a platform for ten years, and it isn't what decides whether your high-risk portfolio keeps processing next year.

If you're choosing a white-label gateway partner, ask a harder question: what does this partner have that a well-funded newcomer couldn't build in twelve months?

1. Acquirer access is the slow part

In high-risk categories (subscriptions, nutraceuticals, dating and similar), the bottleneck is rarely software. It's whether there are acquirers on the other end who understand those categories and are willing to work with them.

That access isn't bought. It is built through integrations, certification work and years of relationships with acquirers' risk and partnership teams. IPG39 has Shift4, Worldline, Amex, CCBILL, Paynt and Silverflow integrated. A new gateway can write an acquirer connector. It can't fast-forward the trust behind it.

Be clear about what this does and doesn't mean. Connectivity gives your merchants a path to acquirers. It does not decide who gets approved. Every acquirer underwrites under its own policy and the card schemes' rules, and some draw hard lines:

1. Shift4/Finaro Europe has a prohibited-industry list.
2. American Express does not accept adult digital content, gambling or virtual currency.
3. Gambling needs a licence, wherever it's offered.

A partner who tells you their connections get any merchant boarded is telling you something no gateway can promise.

2. Risk tooling is how a high-risk portfolio survives

High-risk portfolios rarely fail in one day. They drift. Decline rates creep up, chargebacks build on a few merchants, and by the time the acquirer or a scheme monitoring programme flags it, the options are fewer.

This is where the gateway earns its keep. IPG39 includes a built-in risk engine with 17+ configurable risk rules per MID, chargeback caps, and a fraduefender prevent-alert integration. Per-MID rules let you enforce the limits you agreed with each merchant and with your acquirers. Chargeback caps let you act on a merchant before one bad month becomes a portfolio problem.

The point is managing the portfolio properly, so it stays inside scheme thresholds because it's healthy. That's not the same as hiding from monitoring. Splitting volume across MIDs or otherwise trying to stay under the radar is the fastest way to lose acquirer relationships, and we don't build for it. Good risk tooling makes the numbers better. It doesn't make them look better.

Why is this defensible? Because rule sets that reflect what actually goes wrong in high-risk portfolios come from operating in them. Generic gateways tend to offboard these merchants rather than manage them.

3. Switching costs: the honest version

Here's the part vendors usually leave out of the brochure.

With a white-label gateway, your brand is on the portals and payment forms. Your merchants' card tokens live in the gateway's vault. Your routing logic, acquirer connections and risk rules are configured there. Once that's in place, changing gateways means migrating tokens, re-integrating merchants and rebuilding routing. That is a real project.

That's a moat for the gateway. For you, it's a reason the partner decision matters more than the feature comparison. Before you commit, ask:

1. How are tokens handled if we ever leave?
2. Who owns the merchant relationship and the brand, on paper?
3. What happens to our routing and risk configuration?
4. How fast does the partner add new acquirers?

A partner worth staying with is happy to answer those questions up front.

4. Pricing is a wedge, not a moat

IPG39 is priced as a fixed fee per transaction: no basis points, no revenue share. For an ISO or PSP, that matters. Your cost doesn't climb with ticket size or volume, and your margin stays yours instead of being shared with your infrastructure vendor.

But be realistic. Any competitor can match a price tomorrow. Pricing is a good reason to start a conversation. It shouldn't be the reason you stay. If a gateway's whole pitch is that it's cheaper, ask what happens when someone else is cheaper.

5. Deployment choice: smaller, but real

IPG39 can run on-premise or in the cloud. For most ISOs a managed cloud deployment is the simple answer. Some PSPs have regulatory, data-residency or internal policy reasons to keep the gateway inside their own environment, and for them it matters a lot. It's a niche advantage, not a headline.

A note on compliance and timelines

IPG39 is PCI DSS Level 1. That's a baseline you should expect from any gateway partner, not a differentiator, so verify it and move on.

On timelines, two numbers apply to two different jobs. A single merchant integration typically goes live in 4 to 8 weeks. Rolling out the gateway for a whole ISO or PSP portfolio is more complex and takes about 14 weeks.

So what should you actually evaluate?

Skip the feature checklist; everyone passes it. Instead, weigh:

1. Acquirer depth in your categories, and how candid the partner is about what acquirers won't accept.
2. Risk tooling that helps you run a healthy portfolio, per MID.
3. Exit terms for tokens, brand and configuration, because switching costs cut both ways.
4. Pricing that leaves the margin with you, knowing it's the easiest thing to copy.
5. Deployment that fits your regulatory reality.

Talk to us

If you're an ISO or PSP in high-risk and you're weighing gateway partners, tell us about your portfolio and your acquirer setup. We'll be straight about where IPG39 fits and where it doesn't.

Talk to Field39