When choosing a payment gateway, the relative importance of authorization rates, local payment method coverage, and pricing depends on the merchant’s business model, target markets, customer base, and transaction structure. A gateway that declines several percentage points more transactions than a competitor can cost more in lost revenue than any difference in per-transaction pricing, in many cases. The 12-step payment gateway selection criteria framework below gives you a structured approach to evaluate any provider objectively.
There is no single universal benchmark for payment approval rates. Performance can vary materially by market, card type, issuer, transaction type, customer status, fraud settings, routing configuration, and measurement methodology. Providers should therefore be compared using the same merchant cohort and a consistently defined metric, ideally segmented by country, issuer, payment method, and decline reason. As a simplified illustration, if two providers process the same $10 million of attempted payment volume and one approves five percentage points more, the difference would equal up to $500,000 in additional approved payment value before refunds, chargebacks, retries, fulfilment costs, and other adjustments.
This guide walks you through everything needed to pick the right gateway in 2026 – complete with a scoring matrix, 15 questions for every provider, and a migration playbook. Provider capabilities, pricing, and regulatory requirements change frequently. Validate current terms directly with providers and legal counsel.
What Is a Payment Gateway and How Does It Work?
A payment gateway is the technology layer that connects your checkout page to the banking networks that approve or decline a transaction. It does not hold or move money – its job is to securely capture payment details, encrypt them, and pass them along the chain that decides whether a sale goes through.
A typical card payment moves through five main stages. The authorization process is usually completed within seconds under normal conditions, while capture, clearing, and settlement take place later:
- Payment data collection and tokenization – the customer enters card or payment details at checkout. The gateway securely encrypts and, where applicable, tokenizes the data before it is submitted for processing.
- Transmission to the processor – the payment data is sent to the processor or acquiring bank, which routes the transaction through the relevant card network, such as Visa or Mastercard.
- Authorization request – the card network forwards the request to the customer’s issuing bank. The issuer checks factors such as available funds, card status, authentication results, and fraud signals.
- Approval or decline – the issuing bank returns its decision through the card network and processor. This part of the transaction is generally completed within a few seconds.
- Capture, clearing, and settlement – after authorization, the merchant or payment provider captures the approved payment, either automatically or later, depending on the setup. The transaction then proceeds through clearing and settlement, with funds typically reaching the merchant according to the agreed settlement schedule.
The gateway primarily handles steps 1 and 4, capturing data and relaying the decision back to checkout, while acting as the secure conduit for step 2. It is generally described as “the messenger, not the bank.” This is one reason gateway selection can affect authorization rate: a gateway with better tokenization, retry logic, and routing intelligence can turn a borderline decline into an approval, even though the underlying processor and issuing bank are identical.
Gateway, Processor, PSP, Acquirer, MoR, or Orchestrator: What’s the Difference?
Before evaluating any provider, confirm which type of solution your business actually needs. These roles describe different technical, commercial, and financial functions within the payment chain. They may be provided by separate companies or combined within a single full-stack platform, depending on the provider, product, and market.
- Payment gateway – captures, encrypts or tokenizes, and transmits payment data between the merchant’s checkout and the processing or acquiring infrastructure. A standalone gateway generally does not provide the merchant account or settle funds.
- Payment processor – provides the technical infrastructure used to transmit authorization, clearing, and transaction messages between the relevant participants. A processor does not necessarily provide the merchant account, act as the acquirer, or maintain the merchant’s direct card-scheme relationship.
- Payment service provider (PSP) – is a merchant-facing provider that may bundle gateway services, processing, alternative payment methods, reporting, fraud tools, and access to one or more acquirers. The exact scope varies: a PSP may act through acquiring partners, operate as a payment facilitator, or provide acquiring itself in certain markets.
- Acquirer or acquiring bank – establishes or sponsors the merchant’s card-acceptance relationship, performs merchant underwriting, submits transactions into the card-scheme ecosystem, facilitates settlement, and assumes defined merchant and scheme-related risks. Depending on the setup, the merchant may have a dedicated merchant account or operate under an aggregated model.
- Merchant of Record (MoR) – acts as the seller to the end customer for the covered transaction and generally assumes responsibility for payment collection, applicable indirect-tax handling, refunds, disputes, and chargebacks within the scope of its agreement. The exact allocation of legal and compliance responsibilities depends on the contract and jurisdiction.
- Payment orchestrator – connects multiple PSPs, processors, acquirers, gateways, or payment methods through a common integration and routing layer. It may support routing, failover, cascading, token management, and performance testing, but it does not automatically replace the underlying regulated or acquiring entities.
Full-stack providers such as Stripe and Adyen may combine several of these functions, but their legal and operational roles can differ by country, product, and transaction flow. For illustration, some US flat-rate offerings advertise pricing around 2.9% plus $0.30 for a successful domestic card transaction. This is provider-specific pricing, not a universal processor or PSP market rate.
Understanding Payment Processor Pricing Models
Before calculating your effective rate, you need to know which pricing model the provider uses – because the same headline rate can mean very different actual costs depending on your card mix.
PayPal – Best for Consumer Trust
-
Interchange-plus (cost-plus) pricing separates the underlying interchange and card-network fees from the processor’s markup. A quote might be expressed as interchange plus 0.30% and $0.10 per transaction, allowing the merchant to see the processor’s added margin separately from the underlying card costs.
There is no universal processing-volume threshold at which interchange-plus becomes more economical than flat-rate pricing. The result depends on the merchant’s card mix, average transaction value, share of regulated debit cards, cross-border volume, processor markup, and additional fees. Debit, commercial, premium, and international cards should also be assessed separately: regulated debit transactions may carry relatively low underlying costs, while corporate, premium, and cross-border cards can be more expensive. Merchants should compare pricing models using their actual transaction data rather than relying on a fixed monthly-volume benchmark. - Flat-rate bundles interchange and markup into a single blended rate (e.g., 2.9% + $0.30). Simple to forecast, but merchants with a high share of debit or corporate cards may pay more than they would under a well-negotiated interchange-plus plan, depending on card mix and processor markup. Stripe and Square use flat-rate pricing.
- Tiered (bundled) sorts transactions into "qualified," "mid-qualified," and "non-qualified" buckets, each with a different rate. Providers control which transactions land in which tier. Tiered pricing may make cost reconciliation more difficult because transactions are assigned to provider-defined pricing categories rather than showing the underlying interchange and markup separately.
How to use this: Request interchange-plus quotes even if the provider defaults to flat-rate. For higher monthly volumes, interchange-plus pricing may be worth comparing against flat-rate pricing because savings can outweigh the added invoicing complexity, depending on card mix and processor markup.
The 12-Step Framework for Choosing a Payment Gateway
The steps below cover every dimension that affects payment performance – from fee transparency to local method coverage and migration planning. Use the scoring matrix in the next section to compare providers side by side.
Step 1: Map Your Transaction Profile
This profile also shapes how you choose payment processor terms that fit your business: subscription-heavy models need retry logic and card updater services, while high-volume businesses are most sensitive to per-transaction fees.
Step 2: Understand the Full Fee Structure
The headline rate is rarely the full picture. True payment processing fees can include setup fees, monthly or gateway fees, PCI compliance fees, chargeback or dispute-related fees, refund fees, batch or settlement fees, cross-border surcharges, and currency conversion markups. Exact fees vary by provider, plan, merchant category, region, and contract terms, so every item should be confirmed in writing before signing. For high-risk merchants, a rolling reserve may withhold a portion of processing volume – the exact percentage and duration are set by the provider based on the merchant’s risk profile and should be confirmed in writing before signing.Early termination fees, sometimes called “deconversion fees,” vary by provider and contract terms and should be confirmed in writing before signing.
Step 3: Evaluate Approval and Success Rates
Approval rate is an important payment-performance metric because differences in authorization outcomes can materially affect approved payment volume.
Approval rates should be treated as merchant- and cohort-specific performance metrics rather than universal industry benchmarks. Results vary by geography, issuer mix, card type, transaction type, customer status, authentication flow, fraud settings, routing configuration, and the denominator used to calculate the rate.
Ask each provider for approval-rate data covering a merchant cohort comparable to your own. Domestic and cross-border transactions should be assessed separately, using the same time period, transaction population, and metric definition. Cross-border traffic may perform differently from domestic traffic, but no fixed percentage-point gap applies across all merchants or markets.
A meaningful share of soft declines may be recoverable through retry logic, account updater services, network tokens, or routing changes. The actual recovery rate should be validated using segmented provider data or a controlled test rather than a general market average.
Step 4: Assess Settlement Speed
Settlement options can range from instant or expedited payouts to next-day, two-day, or several-business-day funding. Availability depends on provider terms, country, payment method, acquiring setup, and merchant risk profile. High-risk businesses may face longer payout windows, reserves, or additional review before funds are released. Settlement speed directly affects working capital. Ask what triggers a fund hold.
Step 5: Match Local Payment Methods to Your Geography
Accepting only international card schemes in markets with a dominant local payment method can meaningfully reduce conversion – the exact impact varies significantly by market and audience. The critical methods by region:
- India:
UPI dominates retail payment volumes in India. According to RBI-reported FY25 data, UPI accounted for about 84% of total transactions processed in India’s retail payment systems. Monthly UPI transaction volume crossed 2,000 crore for the first time in August 2025, reaching 2,001 crore transactions. A provider without UPI support may be a weak fit for many Indian e-commerce use cases.
- Brazil:
According to the Worldpay Global Payments Report 2026, Pix accounted for an estimated 42% of Brazilian e-commerce transaction value in 2025. This figure is a third-party market estimate and should not be attributed to Banco Central do Brasil. Separately, the BCB reports that more than 170 million individuals have used Pix; this refers to people who have completed at least one Pix transaction rather than the number of registered users.
- The Netherlands:
The Dutch e-commerce market remains strongly oriented toward bank-based payments, with iDEAL | Wero continuing to play a central role at checkout. As the phased transition from iDEAL to iDEAL | Wero began in 2026, merchants should confirm that their payment provider supports the current branding, customer flow, technical requirements, and migration timetable. Other important local payment methods across major markets include BLIK in Poland, PayPal and invoice-based payments in Germany, M-Pesa in Kenya, and Fawry in Egypt.
Step 6: Scrutinize Fraud and Chargeback Tools
Visa’s VAMP merchant threshold is reported at 1.5% on April 1, 2026, in the US, Canada, EU, APAC, and LATAM, while CEMEA remains at 2.2%. The threshold applies only once the relevant monthly volume floor is reached, so merchants should verify the current regional rules with their acquirer. Mastercard’s Excessive Chargeback Merchant monitoring can apply when a merchant reaches at least 100 chargebacks in a calendar month and a monthly chargeback-to-transaction ratio of 1.5% or higher, subject to Mastercard’s program rules and monitoring period. Effective fraud tooling commonly includes 3D Secure 2.0, velocity checks, device fingerprinting, and IP geolocation, though the right mix depends on your risk profile.
From April 2025, Visa’s consolidated VAMP program replaced the previous VDMP and VFMP frameworks. Under VAMP, since April 1, 2025, TC40 fraud alerts – including those resolved via Rapid Dispute Resolution – now count toward the VAMP ratio, while non-fraud disputes resolved through RDR remain excluded.
The merchant ‘Excessive’ threshold drops from 2.2% to 1.5% on April 1, 2026 (US, Canada, EU, Asia-Pacific; LATAM already at 1.5% since April 2025; CEMEA remains at 2.2%). Acquirer-level thresholds are set separately at 50–70 bps.
Step 7: Check Integration Options and Technical Fit
For payment gateway implementation, most mature providers offer hosted checkout, iFrame, and server-to-server API options. For recurring payments, confirm card account updater support – expired credentials without automatic refresh can create subscription failures that may not always surface as visible errors.
Step 8: Review Contract Terms and Exit Conditions
Before signing, review minimum processing commitments, rolling reserve terms, and who owns the payment tokens if the relationship ends. Providers that lock tokens into proprietary formats can make migration more expensive. Prefer network tokens or a PSP-agnostic vault.
Step 9: Understand Regulatory and Compliance Fit
Gateways handling card data are generally expected to maintain PCI DSS compliance. Merchants processing in-scope electronic payments in the European Economic Area should confirm support for PSD2 Strong Customer Authentication, 3DS2, and any exemptions relevant to their transaction model. The applicable requirements depend on factors such as the payment type, transaction parties, initiation channel, and eligibility for a specific SCA exemption. Regulated verticals need acquirer relationships built for those categories. Confirm certifications and ask which acquiring banks the provider uses in your key markets.
Step 10: Evaluate Scalability and Resilience
Higher-performing gateways usually aim to minimize authorization latency under peak load and should be able to provide latency benchmarks from production-like environments. Higher checkout latency is generally associated with increased cart abandonment, though the exact threshold varies by audience, device, and platform. Look beyond the uptime SLA to the actual failover architecture.
Step 11: Decide Between Single PSP, Multi-PSP, and Orchestration
Single PSP works for early-stage businesses in one geography. Multi-PSP setups tend to become more valuable when expanding internationally or when approval rates start declining. Payment orchestration adds a routing layer across multiple providers, which can help lift approval rates and reduce dependency on any single provider. The case typically becomes compelling at $5 – 10M of annual processing volume. BillBlend positioning: BillBlend provides cascading, smart routing, and A/B testing through a single API.
Step 12: Test Before You Commit
Negotiate a soft-launch phase: route 5 – 10% of traffic to the new provider for two to four weeks. Track approval rate, latency, and chargeback ratio. Set go/no-go criteria in advance.
Payment Gateway Selection Criteria: 12-Point Scoring Matrix
Score each provider 1–5 on every criterion, then weigh by your priorities. This payment gateway selection criteria matrix is the tool most procurement teams skip – and the one that prevents the most expensive switching decisions.
| Criterion | Priority |
|---|---|
| Transaction fee (effective rate) | High |
| Authorization / success rate | High |
| Settlement speed | Medium |
| Local payment method coverage | High |
| Fraud and chargeback tools | High |
| Rolling reserve terms | Medium |
| Contract flexibility / exit terms | Medium |
| Integration complexity | Medium |
| Recurring payments / card updater | Medium |
| Compliance and regulatory fit | High |
| Uptime and technical resilience | High |
| Support quality | Medium |
15 Questions to Ask Every Provider Before Signing
These questions surface what doesn’t appear in a sales deck. Use them on every call.
- What is your approval rate for my specific card mix, geography, and transaction type?
- Can you provide 90-day performance data from a reference merchant in my vertical?
- What percentage of soft declines are retried, and what is the recovery rate?
- What are the rolling reserve percentage and release schedule for my business?
- What are the exact fees for chargebacks, refunds, currency conversion, and PCI compliance?
- What does early termination cost, and under what conditions can you terminate?
- Who owns the payment tokens if I switch providers?
- Do you support network tokens and card account updater services?
- Which acquiring banks do you use in my primary markets, and what is their risk appetite?
- Are fraud rules self-configurable, or do you manage them?
- What is your uptime SLA, and what compensation applies if it is breached?
- What is end-to-end authorization latency at peak traffic?
- Does your sandbox accurately reflect production behavior?
- Can I run a soft launch at reduced volume before full migration?
- What triggers a fund hold, and what is the dispute process?
How to Choose the Best Payment Gateway for High-Risk Businesses
Online gambling is commonly classified under MCC 7995 and is generally treated by acquiring banks as a high-risk category, though specific risk-tier treatment can vary by acquirer.
Licensing is usually a core onboarding requirement for regulated gambling operators. Acquirers typically require valid licensing – MGA, UKGC, Curaçao eGaming, Gibraltar – before onboarding, and unlicensed applications are commonly rejected.
Cost structure differs materially. Licensed iGaming operators may face higher fees, rolling reserves, and longer settlement windows than standard e-commerce merchants. Exact terms vary by acquirer, jurisdiction, licensing status, transaction mix, and chargeback history.
Multiple acquirer relationships are generally considered important. A recognized failure mode in the industry: an acquiring bank exits the gambling vertical and terminates affected operators at once. Look for gateways with multiple acquirer relationships per jurisdiction. For a deeper look at fraud prevention, see BillBlend’s Online Gaming Fraud 2026 guide.
Do you have any more questions?
Fill out the form, and we will contact you
*By submitting this application, you consent to the processing of your personal data in accordance with the privacy policy.
Migrating to a New Gateway Without Downtime
Switching providers is, in large part, a token ownership problem: card-on-file tokens stored in a current gateway’s proprietary format generally cannot be reused by a new provider without a migration plan.
- Provider-to-provider credential migration may be possible when both parties support a secure transfer process, contractual approval has been obtained, and the token or credential formats are compatible. PCI DSS validation alone does not guarantee token portability.
- Gradual migration – new customers go to the new gateway immediately; existing subscribers stay on the old gateway until the natural rebill.
- PSP-agnostic token vault – a centralized vault independent of any PSP, the cleanest architecture for large subscriber bases.
BIN table updates are a frequently overlooked migration task. Since Visa and Mastercard mandated the expansion from 6-digit to 8-digit BINs in April 2022, an incomplete BIN table at a new gateway can cause misrouted transactions and incorrect card-type identification – confirm your new provider’s BIN database is fully updated and ask about their refresh cadence before go-live.
Run both gateways in a dual-PSP parallel setup, routing an increasing traffic share to the new provider while monitoring approval rates against the baseline. For a broader look at provider options, see BillBlend’s best payment processors guide.
Payment Gateway Checklist Before You Sign
Use this payment gateway checklist before committing to any provider:
Fees and Financials
- Calculate the effective rate across all shortlisted providers and compare.
- Review rolling reserve terms – percentage, duration, and release conditions.
- Confirm chargeback, refund, and currency conversion fees in writing.
- Confirm monthly minimums and early termination fees in writing.
Performance and Technical Fit
- Request approval rate data segmented by region, card type, and issuer.
- Confirm latency benchmarks for peak traffic.
- Confirm uptime SLA and what compensation applies if breached.
- Verify soft decline retry logic and test it.
- Confirm the card account updater service for recurring payments.
- Test the sandbox with a representative transaction mix.
Legal, Compliance, and Migration
- Verify current PCI DSS v4.0.1 validation documentation.
- Verify regulatory fit for all operating jurisdictions.
- Review token ownership and portability terms in the contract.
- Confirm fund hold triggers and the dispute process.
- Agree on a token migration plan with the current provider.
- Agree on a soft launch plan with go/no-go criteria defined in advance.
- Confirm the new provider’s BIN table update process and refresh cadence.
Payment Gateway Provider Overview: Who Fits Which Use Case
The 12-step framework above works for any provider. Below is a non-exhaustive orientation by use case – not a ranking, since the right choice depends on your transaction profile from Step 1.
Global / multi-market businesses
- Stripe – available in Stripe-supported countries and regions; strong developer experience and broad global payment acceptance. Confirm current country availability and supported local payment methods directly on Stripe’s Global Availability page.
- Adyen is an enterprise-focused payment platform that combines gateway, processing, and acquiring capabilities in one platform, with access to local payment methods through a single integration. Available methods depend on merchant location and target markets.
- Braintree (PayPal) – strong PayPal wallet coverage, competitive for North America and Europe.
- BillBlend is positioned as a high-risk payment gateway and orchestration solution with features such as cascading, smart routing, A/B testing, segmentation, and risk/fraud tools.
India
- Razorpay – wide UPI, card, and wallet coverage; strong developer tooling; dominant in domestic Indian e-commerce.
- PayU India – long-established, strong bank relationships – supports all major domestic methods.
- Cashfree Payments – competitive on payout speed and API flexibility; strong for platforms and marketplaces.
- BillBlend – native UPI, PhonePe, Paytm, and IMPS support alongside global card schemes. Best fit for international and high-risk merchants (iGaming, forex, subscriptions) entering India who need local methods combined with cross-border acquiring.
Brazil
- PagSeguro / PagBank – Brazilian provider with Pix, QR Code Pix, card brand, digital wallet, and online payment capabilities.
- Cielo – a large Brazilian payment provider with retail and e-commerce solutions, including payment links, checkout, API e-commerce, gateway tools, Pix, QR Code, and broad card brand acceptance.
- Stripe Brazil – Stripe lists Brazil among its supported countries/regions; merchants should confirm current local method support and pricing directly with Stripe.
Provider capabilities, pricing, and market availability change frequently. Validate current terms directly with each provider using the 15 questions in this guide.
Choosing a Payment Partner, Not Just a Gateway
The 12-step framework above is intended to structure the variables that commonly affect payment performance. Picking the best gateway in 2026 means matching approval rate, local method coverage, and settlement speed to your specific markets.
If you operate in high-risk verticals or cross-border markets, this evaluation is also the moment to reconsider whether a single-PSP strategy is still appropriate. Where approval rates are declining and multi-market complexity is increasing, the case for orchestration can become more compelling – though whether it makes sense depends on volume, risk profile, and markets.
BillBlend positioning: BillBlend is positioned for businesses that need multi-region payment orchestration, local payment method coverage, smart routing, cascading, and high-risk acquiring support. Before relying on any specific capability, validate current availability, pricing, regulatory fit, and acquirer coverage with the BillBlend team. Contact the team to discuss your requirements.
Provider capabilities, supported countries, pricing, reserves, settlement timelines, and regulatory requirements change frequently. Use this guide as a buyer’s framework, not legal, compliance, or financial advice. Validate current terms directly with providers, acquirers, and legal counsel before signing.
FAQ: How to Choose a Payment Gateway in 2026
What is the difference between a payment gateway and a payment processor?
A gateway securely captures and transmits payment data. A processor provides the technical infrastructure for processing transaction messages. An acquirer establishes or sponsors the merchant’s card-acceptance relationship and facilitates settlement. A PSP is the merchant-facing provider that may bundle some or all of these functions. Full-stack platforms can combine several roles, but the exact legal and operational structure varies by provider, product, and market.
What approval rate should I expect from a good gateway?
There is no universal approval-rate target for a “good” gateway. Establish a baseline using your own transaction data and compare providers on the same merchant cohort, geography, card mix, transaction type, fraud configuration, and measurement period. Domestic and cross-border traffic should be evaluated separately. A material decline from your own baseline – or a statistically meaningful difference in a controlled provider test – warrants analysis of decline codes, routing, authentication, tokenization, and fraud rules.
What is a rolling reserve, and how does it affect cash flow?
A rolling reserve withholds a percentage of processed volume for a defined period as a chargeback buffer – exact terms are set by the provider based on risk profile. As an illustrative example, a 10% reserve on $500K/month would mean roughly $50,000 continuously unavailable – worth factoring into a true cost-of-ownership comparison using your provider’s actual terms.
How do I switch payment gateways without losing subscription data?
Three approaches:
- Secure provider-to-provider credential migration – may reduce disruption where the incumbent permits data export, the new provider supports import, both parties have appropriate PCI DSS validation for the services involved, and the transfer is tested in advance. Proprietary provider tokens may not be portable.
- Gradual migration, letting subscribers rebill on the old gateway.
- PSP-agnostic token vault for long-term flexibility. Run both in parallel during the transition.
Which payment gateway is best for iGaming?
A vertical specialist. Requirements: valid gambling license, multiple acquirer relationships per jurisdiction, native 3DS2 and fraud tooling, and pricing/reserve terms suited to high-risk categories – exact figures vary by acquirer and should be confirmed directly. Acquirer concentration risk is commonly cited as one of the more common failure modes in this vertical.
What local payment methods are critical for India and Brazil?
For India, UPI is commonly considered essential – roughly 84% of digital retail payment volumes, per RBI/NPCI data (see Step 5 above for the monthly transaction figure and source).
For Brazil, Pix has become a dominant payment method (42% of purchase value – reported by Rio Times Online, citing Central Bank context; direct BCB dataset not located), with approximately 179 million users by late 2025 (see Step 5 above for source). A gateway lacking these two may struggle to compete effectively in those markets.
How do I evaluate fraud tooling before signing?
Ask: Are rules self-configurable? Is 3DS2 supported? What is the false-positive rate? Request a sandbox walk-through of rule configuration. Providers without self-serve rule management can create operational bottlenecks as your transaction mix evolves.
