Payment gateway providers — how to shortlist one.
Every payment gateway providers list is out of date by the next quarter. What lasts is a merchant-side RFP shortlist you can re-run against the market whenever a contract cycle opens. This page is that shortlist, with BazPay's own answers on every row.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services companies. Direct regional acquiring, interchange++ reporting, one API and one signed-webhook stream — operated by NEWERA PAYMENT TECHNOLOGIES LTD.
What makes a payment gateway provider worth shortlisting
Four things separate a credible online payment gateway provider from the rest — before price ever enters the conversation. These are the reasons product, engineering and finance teams stay after the migration is paid for.
-
One provider, one contract
BazPay is the gateway and the regional acquirer for its book. Procurement contracts one entity, and the entity that authorises your traffic is the same one that settles the funds — no chain of reseller agreements to unpick when something goes wrong.
-
Predictable regional scope
Regional merchant underwriting is published up front. There is no waiting on a bespoke risk committee — either the model fits the policy or it does not, and you find out in the first conversation.
-
Transparent economics
Interchange, scheme fees and gateway margin appear line-by-line on every settled transaction. The rate card is on the website. Finance teams reconcile against the source instead of chasing a monthly summary.
-
Migration path from an existing provider
Vault imports, network-token portability and debit-order mandate handover are scoped inside onboarding. Old and new webhook streams run in parallel until the new stack proves out under real load.
The kinds of payment gateway providers you will meet
Most shortlist confusion comes from treating every provider as one category. They are not. Below are the four structural types merchants in the EU, UK, Australia, Canada and New Zealand encounter, in roughly the order they appear in a procurement search.
-
Direct acquirer
Direct regional acquirer with gateway
One provider holds scheme membership, runs the gateway software and settles the merchant. BazPay operates in this shape for merchants across the EU, UK, Australia, Canada and New Zealand — clean chargeback attribution, interchange++ visibility, no reseller layer.
- Named MID
- Interchange++
- Own settlement
-
Aggregator
Aggregated PSP / reseller
A reseller sitting on top of a downstream acquirer under a shared merchant identifier. Fast to sign, cheap to trial — trade-offs land later in blended reporting and diluted chargeback attribution.
- Shared MID
- Blended rate
- Fast onboarding
-
Orchestrator
Payment orchestrator
A software layer that fans your traffic across several downstream gateway providers. Useful for very high volumes with strong redundancy needs; adds an integration layer and a second contract.
- Multi-gateway
- Smart routing
- Two contracts
-
Regional
Regional acquirer
A national-scope acquirer optimised for one market — typically strong on local scheme economics, sometimes limited on cross-border coverage. Merchants in the EU, UK, Australia, Canada and New Zealand selling into a single market often shortlist a regional acquirer alongside a wider provider.
- Local schemes
- Single market
BazPay's own shape is described on payment processors for the processor role and merchant acquiring for the licence side.
A ten-row RFP for online payment gateway providers
Ten rows will separate a shortlist of five providers cleanly. Ask every provider the same questions in the same order and score the answers, not the pitch. BazPay's answers appear on the right column so you can compare directly.
| Criterion | BazPay | What to ask any provider |
|---|---|---|
| Direct vs reseller | Direct regional acquirer, named MID | State the model and the licensed entity |
| Underwriting scope | Regional (published list) | Published policy, not a case-by-case decision |
| MID structure | Named MID per merchant | Shared / aggregated MID / other |
| PCI scope on merchant | Merchant SAQ A (hosted fields, vault) | What the provider requires from you |
| 3-D Secure 2 | 3-D Secure 2.2 with exemption logic | Version and exemption engine present or absent |
| Reporting | Interchange++ per transaction | Line detail or blended summary |
| Webhook contract | Signed HMAC, replay-protected, idempotent | Signature scheme + delivery guarantees |
| Settlement | Per-scheme cycle to your local settlement account | Cadence, aggregation, corridor |
| Migration support | Vault + mandate import scoped in onboarding | Who runs the migration and how |
| Status / incident | Public status page + signed webhooks | Where operational health is published |
Rate structure on the pricing page. The operational envelope around the API on payment gateway services.
A repeatable process for shortlisting providers
Six stages describe how a mature payments team runs a provider selection. Each stage has an artefact — a longlist, a scored RFP, a reference summary — that survives the people involved and works again next contract cycle.
-
Longlist
Assemble a longlist of providers based on region, scheme coverage and vertical fit — often 5-10 names in the first pass.
-
Filter
Apply hard criteria (direct vs reseller, MID structure, PCI scope, reporting depth). Most longlists shrink by half at this step.
-
Shortlist
Score the remainder against a written RFP. Ask each provider the same questions in the same order and score the answers, not the pitch.
-
Reference
Talk to a reference customer at each shortlisted provider. Ask about migration, incident handling and roadmap — the questions marketing pages do not answer.
-
Pilot
Board sandbox and integrate against the finalists. Post real test traffic. A day of sandbox exposes more than a week of demos.
-
Board
Sign, board under the chosen provider, migrate the vault and cut over. Keep the runner-up in play for six weeks in case something breaks in production.
Provider features that survive due diligence
Below are the platform features BazPay ships to every merchant. They map to the RFP criteria above and are the same features procurement should look for in any credible regional provider.
-
REST API
One endpoint reaches cards, wallets, local APMs and SEPA Instant — the response object shape does not change between rails.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout so raw PAN never touches your stack.
-
Gateway-side vault
Store credentials once and re-use them across renewals, upgrades and one-clicks — portable if you ever change provider.
-
Network tokens
Visa and Mastercard network tokens refresh automatically after card reissue; card-on-file charges keep working.
-
3-D Secure 2.2 engine
Frictionless flow first; PSD2 exemption logic claims TRA, low-value, trusted-beneficiary and MIT where permitted.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change; delivery retries on an exponential schedule for up to 72 hours.
-
Interchange++ reporting
Every settled transaction breaks out interchange, scheme fees and gateway margin for line-level reconciliation.
-
Public status page
Rail health per network and incident timelines published in the open — the operational surface every credible provider should ship.
One REST call. Every provider should be this compact.
A credible payment gateway provider gives developers a REST API you can read in an afternoon and integrate against without a demo. If you cannot post your first charge in a sandbox on the same day you signed up, that is a signal about how the rest of the relationship will feel.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"descriptor": "ACME EU LTD",
"metadata": { "order_id": "ORD-10842" }
}The response returns a canonical charge object with the authorisation code, the MID it posted against, the interchange bucket and any exemption applied. Full schema in the API reference; handler samples in the developer docs.
Who BazPay serves as a regional payment gateway provider
BazPay is scoped to four regional merchant profiles with predictable chargeback ratios and clean AML posture. Underwriting policy is unchanged whether you shortlist BazPay against one competitor or five.
-
E-commerce sellers
DTC brands and multi-country storefronts running Shopware, Magento 2, WooCommerce or PrestaShop. Local card acceptance without stitching regional PSPs.
-
Subscription software
SaaS teams billing monthly and annual plans with card-on-file renewals, MIT exemptions and dunning-aware retries.
-
Professional services
Agencies, consultancies and B2B service firms invoicing recurring retainers with named-payer trust lists and enforced 3-D Secure 2 over a set ceiling.
-
Digital publishers
Membership renewals, single-issue purchases and paywall unlocks reconciled per SKU on one MID.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is locally licensed and is not an Australian, US or Polish-domiciled acquirer.
Security and compliance baselines every provider should meet
The floor for a credible online payment gateway provider is PCI DSS Level 1 on its own environment, authentication with 3-D Secure 2, GDPR compliance for merchants in the EU, UK, Australia, Canada and New Zealand and named scheme registrations. Anything below that floor is a red flag on your shortlist.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted fields and gateway vault keep card data out of your stack
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on every card charge
- GDPR
- In-region data residency; DPA on request
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
- Scheme registrations
- Visa VIRP and Mastercard SPoC/PCI-CP where required
Provider selection questions merchants ask us
How do I choose between payment gateway providers?
Score every provider against the same written RFP, not a demo. The questions that matter most across online payment gateway providers are: is the entity a direct acquirer or a reseller, what MID structure will you sit on, does reporting arrive at interchange++ line detail, is the API versioned with a documented deprecation policy, and how are status and incidents communicated. Answers separate credible providers from the rest.
Is there an authoritative payment gateway providers list I can start from?
No single authoritative list stays current — the market shifts every quarter as licences move, resellers get acquired and networks add new members. Any 'list of payment gateway providers' article is a snapshot. The durable approach is a written RFP shortlist you re-run against the market when a contract cycle opens.
Are there Australian payment gateway providers that fit a regional merchant?
BazPay is an locally licensed direct payment gateway provider and does not hold an Australian acquiring licence. An regional-headquartered merchant with Australian customers can still authorise cross-border card traffic on the same regional acquiring contract, and Australian-issued cards authorise on the international scheme rails. A merchant that is Australian-domiciled and needs a locally licensed acquirer should shortlist Australian payment gateway providers directly.
What is the difference between a payment gateway provider, a processor and an acquirer?
An acquirer holds the licence with the card schemes and settles the merchant. A processor moves the authorisation message between merchant, schemes and issuers. A gateway provider is the software layer that gives merchants a REST API into the whole stack. BazPay combines all three functions for its regional book, so there is no reseller between you and the network.
Which industries does BazPay board?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants. BazPay is not a merchant of record and does not act as a marketplace of third-party PSPs.
How is BazPay priced compared with other providers?
Card processing runs on interchange++ — every settled transaction shows interchange, scheme fees and the gateway margin as separate lines. Local payment methods carry their own scheme rate and are never blended into a headline card rate. Current rates and any minimums are published on the pricing page.
What migration support does BazPay offer when switching from another provider?
Vault imports, network-token portability and debit-order mandate migration are planned inside onboarding under scheme-approved processes. Old and new webhook streams run in parallel until traffic is proven on the new stack, and a named integration manager owns the cutover window with your on-call.
How do developers evaluate a payment gateway provider?
Read the API reference before the sales call, verify signature and idempotency semantics against the developer docs, and spin up a sandbox key inside 30 minutes. Any provider whose sandbox needs a scheduled demo is going to be slow to answer real questions once you are live.
Put BazPay on your provider shortlist
Share your business model, volumes and existing provider and we will confirm boarding fit and likely rate structure inside one working day. Sandbox keys are available so integration work can begin in parallel — see also all products, the wider network payment gateway and packaged payments solutions.