Types of payment providers

The providers above fall into three groups, and most businesses end up using more than one. The 9 global processors handle cards almost anywhere and are the usual default for a first integration. The 27 regional gateways exist because a local acquirer often converts far better in its own market: it supports the payment methods people there actually use, settles in the local currency, and looks domestic to the issuing bank rather than like a foreign transaction. The 4 crypto networks settle in digital assets, and several convert to ordinary currency before payout.

Those categories are also the filter buttons above, so you can narrow the list before opening any individual provider page.

How to choose a payment provider

The instinct is to compare fee tables first. That is usually the wrong order. A provider that is fractionally cheaper but does not support the payment method your customer expects will lose you the whole sale, not a percentage of it, so the more useful questions are where your customers are, what they normally pay with, and which currency you want to be paid in.

After that, weigh how much onboarding each provider expects. Some open an account in a day; others price and underwrite for scale and expect meaningful monthly volume before they are interested. Each provider page here states which markets and methods it covers and links to the provider's own pricing, because published rates change without notice and a stale figure on our page would be worse than none.

Using several payment providers at once

One integration connects you to every provider on this page, which changes what choosing one actually costs. Normally a provider decision is close to permanent: the integration is built against that provider's API, so replacing it means development work, testing and a release. That is what makes merchants stay on a provider that stopped suiting them.

Through PaymentHood the provider is configuration rather than code. You can run a local gateway for domestic cards and a global processor for everyone else, add a regional provider when you open a new market, or move away from one entirely, and your checkout never changes. Because the payment tokens are issued by the provider rather than by us, the switch does not invalidate saved customer payment details either. That is also why the first choice matters less than it appears to: it is reversible.

Provider FAQ

Frequently Asked Questions

PaymentHood connects to more than 30 payment providers, covering global processors, regional gateways across Africa, the Middle East, South Asia and Europe, and crypto payment networks. You integrate once and activate whichever of them you need, and the full current list is on this page with a dedicated page for each provider.

Yes. Running several providers at once is the main reason to use an orchestration layer. You might take domestic cards through a local gateway for better approval rates while routing international customers elsewhere, and PaymentHood decides which provider handles each payment without your checkout code knowing the difference.

You activate the new provider in your PaymentHood dashboard and it takes effect immediately. There is no code change, no redeployment and no new plugin to install, because your integration talks to PaymentHood rather than to the provider directly. Stored customer tokens stay valid because they were issued by the provider, not by us.

No. PaymentHood takes no percentage and no per-transaction cut at any volume, whichever providers you enable. Each provider bills you directly for its own processing fees on the terms you agreed with them. PaymentHood's only paid plan is Premium at $29 a month, which adds white-label checkout branding and nothing to your transaction cost.

Start from where your customers actually are rather than from a fee table. The provider that settles in your customers' currency and supports the methods they already use will usually beat a cheaper one they cannot pay with. Because switching later costs nothing, the first choice matters far less than it does with a direct integration.

A payment gateway moves one transaction from your checkout to a bank. Payment orchestration sits above several gateways and decides which one each transaction should use, handling routing, failover and reconciliation across all of them. You still need at least one gateway; orchestration is what stops you rebuilding when you add the second.