%201.svg)
Payment Gateway Comparison: 18 Providers, Pricing and Business Fit
rétrofacturation?
Ce n'est plus votre problème.
Récupérez 4 fois plus d'rétrofacturation s et PRÉVENTION jusqu'à 90 % des messages entrants, grâce à l'IA et à un réseau mondial de 20 000 commerçants.
Plus de 600 avis- Compare 18 providers by the payment role and product configuration your business needs, including PSP, gateway, acquiring, wallet, and merchant-of-record models.
- Use published fee examples with their market and service scope, then price the same transaction mix across your proposals.
- Test checkout, settlement, refunds, reconciliation, and evidence retrieval in the proposed implementation.
- Compare dispute operations using consistent case definitions, data, and measured handling time.
- Chargeflow complements supported payment providers with specialized chargeback operations and connected evidence.
A payment gateway comparison evaluates how a payment provider fits your checkout, business model, markets, pricing requirements, integrations, and dispute operations. This guide covers 18 providers across gateway, PSP, acquiring, wallet, merchant-of-record, and embedded-payment models. Start with the role your business needs, then compare the complete implementation.
For an online store, compare checkout and reconciliation together. For SaaS, define who owns billing, tax, and the seller relationship. For retail, connect online and in-person operations. For international commerce, map legal entities, local payment methods, currencies, and settlement accounts.
In This Guide: Payment Gateway Comparison Table · Payment Gateway Pricing Comparison · Payment Gateway vs PSP vs Merchant of Record · Payment Gateway Questions
Payment Gateway Comparison Table
Providers are shown alphabetically. The business-fit descriptions are starting points for a shortlist, with an official source for each provider. A company can offer several operating models; specify the product and commercial agreement you are comparing.
18 payment providers compared by offering, fit, and implementation scope
- Documented Offering
- Digital commerce, subscription billing, and packaged commerce options. Provider documentation
- Business Fit
- Software and digital-product sales across markets.
- Define in Your Proposal
- Product package, billing and tax scope, and payout reporting.
- Documented Offering
- Payment processing and acquiring with online and in-person capabilities. Provider documentation
- Business Fit
- Commerce programs connecting payment methods, channels, and settlement.
- Define in Your Proposal
- Entity coverage, local methods, reconciliation, and dispute ownership.
- Documented Offering
- Payment acceptance alongside cross-border financial operations. Provider documentation
- Business Fit
- Businesses connecting payments, currencies, accounts, and transfers.
- Define in Your Proposal
- Acceptance fees, FX, account plans, entities, and settlement currencies.
- Documented Offering
- Gateway-only and merchant-account-plus-gateway options. Provider documentation
- Business Fit
- Merchants selecting a gateway and processing relationship.
- Define in Your Proposal
- Gateway scope, acquiring relationship, and combined fees.
- Documented Offering
- PayPal’s end-to-end payment platform. Provider documentation
- Business Fit
- Custom card and wallet checkout with transaction-level control.
- Define in Your Proposal
- Payment methods, pricing agreement, data access, and reconciliation.
- Documented Offering
- Digital payments with tailored commercial structures. Provider documentation
- Business Fit
- Online merchants planning payment performance and regional expansion.
- Define in Your Proposal
- Flat-rate or interchange++ proposal, integration, and reporting.
- Documented Offering
- Online payments with hosted checkout, payment links, recurring billing, a dual pricing program, and its own gateway. Provider documentation
- Business Fit
- Merchants bringing payment acceptance and business workflows together.
- Define in Your Proposal
- Gateway configuration, processor and underwriting terms, program type, and reporting.
- Documented Offering
- Payment technology and industry-focused software; completed its Worldpay acquisition on January 12, 2026. Provider documentation
- Business Fit
- Businesses connecting payment acceptance with vertical-specific operations.
- Define in Your Proposal
- Selected products, channels, industry workflows, contracting entity, and account structure.
- Documented Offering
- Online and in-person payment processing, merchant services with chargeback management, and a financial ERP. Provider documentation
- Business Fit
- Merchants and payment businesses seeking connected services and support.
- Define in Your Proposal
- Payment channels, onboarding, account support, and data connections.
- Documented Offering
- Payment services with standard, volume, and IC++ pricing options. Provider documentation
- Business Fit
- Businesses evaluating local payment methods and integrated commerce.
- Define in Your Proposal
- Country-specific methods, pricing model, and platform configuration.
- Documented Offering
- Payment infrastructure for international acceptance and additional financial services. Provider documentation
- Business Fit
- Businesses matching payment methods and services to their industry and markets.
- Define in Your Proposal
- Entity and method coverage, reconciliation, and integration scope.
- Documented Offering
- Merchant-of-record services for software and digital products. Provider documentation
- Business Fit
- Businesses seeking packaged checkout, billing, and sales-tax operations.
- Define in Your Proposal
- Product eligibility, included services, migration, and reporting.
- Documented Offering
- Branded checkout with card, wallet, and pay-later options by configuration. Provider documentation
- Business Fit
- Merchants offering PayPal and complementary checkout choices.
- Define in Your Proposal
- Checkout product, payment methods, protection eligibility, and account fees.
- Documented Offering
- Payment and financial-services infrastructure. Provider documentation
- Business Fit
- Businesses combining acceptance, payouts, and financial workflows.
- Define in Your Proposal
- Supported markets, payment methods, accounts, and APIs.
- Documented Offering
- Connected online, in-person, invoice, and mobile payment tools. Provider documentation
- Business Fit
- Businesses coordinating retail or service payments across channels.
- Define in Your Proposal
- Hardware, software plan, channel pricing, and reporting.
- Documented Offering
- Modular payments with checkout, billing, platform, and additional products. Provider documentation
- Business Fit
- Businesses building online commerce or platform payment workflows.
- Define in Your Proposal
- Selected modules, payment methods, integration, and commercial model.
- Documented Offering
- Platform-connected payment accounts and APIs. Provider documentation
- Business Fit
- Businesses evaluating or operating a platform-provided WePay account.
- Define in Your Proposal
- The platform’s current onboarding path, account terms, and support responsibilities.
- Documented Offering
- Payment acceptance across online, in-person, and embedded use cases; now part of Global Payments since January 12, 2026. Provider documentation
- Business Fit
- Businesses connecting payments with commerce and software operations.
- Define in Your Proposal
- Named product, contracting entity, markets, channels, migration dependencies, and support.
Payment Gateway Pricing Comparison
Use published rates as inputs to a scoped comparison. The figures below were checked October 4, 2026, and each row states its country, currency, and product. US card-processing references, gateway-only fees, EUR rates, and merchant-of-record packages cover different services. Price the same transaction mix and required capabilities before comparing totals.
Payment pricing examples with the service scope needed for a fair comparison
- Published Pricing Reference or Model
- US standard pricing: 2.9% + $0.30 per successful domestic online card transaction; 2.7% + $0.05 for domestic in-person Terminal cards. Custom pricing, including IC+, is available.
- Scope to Include
- Selected products, international cards, currency conversion, payment methods, and dispute services. Stripe bundles gateway and processing.
- Published Pricing Reference or Model
- US standard cards and digital wallets: 2.89% + $0.29; Venmo 3.49% + $0.49. Custom flat-rate or interchange-plus options are available for established merchants.
- Scope to Include
- Currency, card origin, payment method, optional tools, and contractual terms.
- Published Pricing Reference or Model
- US All-in-One (merchant account included): $25/month + 2.9% + $0.30 per transaction. US Gateway Only: $25/month + $0.10 per transaction + $0.10 daily batch fee. The pricing page lists a $0 chargeback fee on these card plans.
- Scope to Include
- The two configurations are different bundles. Gateway Only needs your own merchant account, so add your processor or merchant-account charges.
- Published Pricing Reference or Model
- Interchange++ on cards: a fixed $0.13 processing fee plus a 0.60% markup on interchange and scheme fees; payment methods such as iDEAL add a method fee (EUR 0.22). Adyen describes the published fees as indicative.
- Scope to Include
- Market, currency, contracted payment methods, and other separately priced products. Final pricing comes from your quote.
- Published Pricing Reference or Model
- The pricing page lists no numeric rates. It describes fully flat-rate and interchange++ structures priced to your business profile.
- Scope to Include
- Treat figures as a quote. Use the same transaction mix, payment services, markets, and support scope.
- Published Pricing Reference or Model
- Netherlands, EUR standard pricing: EEA consumer cards 1.80% + EUR 0.25, EEA commercial cards 2.90% + EUR 0.25, non-EEA cards 3.25% + EUR 0.25, iDEAL EUR 0.32. Volume pricing is available above EUR 100,000 per month.
- Scope to Include
- Country, payment-method mix, plan or contract, and platform services. Do not compare these EUR rates with US rates for the same merchant decision.
- Published Pricing Reference or Model
- Pay-as-you-go: 5% + $0.50 per Checkout transaction; custom pricing is available, including for products under $10.
- Scope to Include
- Merchant-of-record package (billing, tax and compliance included), and any agreed premium services. This covers a different scope than gateway or card-processing rates.
- Published Pricing Reference or Model
- 2Sell: 3.5% + $0.35; 2Subscribe: 4.5% + $0.45 per successful sale. 2Monetize and enterprise packages use tailored pricing. The pricing page does not state which plan includes merchant-of-record services.
- Scope to Include
- Product package, country-specific fees, tax responsibilities, and billing scope.
- Published Pricing Reference or Model
- Fees depend on the PayPal checkout product and payment method.
- Scope to Include
- Commercial transaction type, card or wallet funding, market, and currency.
- Published Pricing Reference or Model
- Payment fees vary by channel and plan; eligible businesses can discuss custom pricing.
- Scope to Include
- Online, in-person, invoices, software, hardware, and services.
- Published Pricing Reference or Model
- Published "as low as" starting rates: 2.3% + $0.20 online and 2.0% + $0.10 in person (US). Your account rate, ERP terms, and dispute fee come from a quote.
- Scope to Include
- Treat "as low as" as a starting rate, not a quote, and add ERP, fraud, compliance, and account fees.
- Published Pricing Reference or Model
- Offers a dual pricing program. Gateway and processor fees come from a written proposal.
- Scope to Include
- Processor relationship, program type, per-transaction gateway fee, recurring fees, refund treatment, and dispute fees.
- Published Pricing Reference or Model
- Account and spend plans alongside payment, FX, and transfer pricing.
- Scope to Include
- Payment acceptance and financial-services costs for each entity and workflow.
For Global Payments, Worldpay, Nuvei, Rapyd, WePay, and other providers without a numeric rate above, request a proposal for the named product and merchant entity. Keep standard published pricing and negotiated quotes in separate columns, with the effective date and currency recorded.
Worked Example: Compare the Same Payment Mix
Illustrative calculation using two published US standard rates for domestic online cards: 10,000 domestic-card transactions averaging $50 represent $500,000 in payment volume. At Stripe’s published 2.9% + $0.30 rate, processing is $17,500. At Braintree’s published 2.89% + $0.29 rate, it is $17,350. These calculations cover only the specified standard processing fees.
The $150 difference is one input to a business decision. Add the products you need, currency and card mix, contract terms, implementation, reconciliation, and dispute operations. Then evaluate customer experience and completed-payment performance using comparable traffic. Each provider’s complete proposal can support a different operating plan.
Operational cost example: 200 cases requiring ten minutes each create about 33.3 hours of work. At $30 per loaded labor hour, that is $1,000. Use your measured handling time and case volume when estimating the value of improved evidence collection or automation. This is a planning example, not a provider performance claim.
Payment Gateway vs PSP vs Merchant of Record
Payment models compared by role and commercial scope
- Role in the Payment Stack
- Transmits payment information between checkout and the processing chain.
- What Your Proposal Should Specify
- The processor, acquiring relationship, merchant account, and reporting connections.
- Role in the Payment Stack
- Packages payment acceptance services in one technical and commercial relationship.
- What Your Proposal Should Specify
- Included gateway, processing, acquiring, settlement, risk, and reporting services.
- Role in the Payment Stack
- Provides the merchant-side relationship for card acceptance and access to card-network processing.
- What Your Proposal Should Specify
- Merchant entities, countries, settlement, account terms, and dispute routing.
- Role in the Payment Stack
- Acts as the seller of record under its service model, with defined payment, tax, and related responsibilities.
- What Your Proposal Should Specify
- Seller responsibilities, eligible products, tax and billing scope, support, and payouts.
- Role in the Payment Stack
- Provides a recognizable customer payment experience that can work within a wider stack.
- What Your Proposal Should Specify
- Funding methods, checkout integration, customer and merchant protection, and reporting.
- Role in the Payment Stack
- Makes payment capabilities available inside a software platform.
- What Your Proposal Should Specify
- Platform and merchant roles, onboarding, account ownership, fees, and support.
Match the label to the actual product. For example, a provider can offer direct payment processing and a separate merchant-of-record product. Define who is the seller, who settles funds, who receives a dispute, and who submits evidence for the configuration you choose.
The answer changes by configuration. With Authorize.net, card chargebacks route through your merchant service provider. Stripe disputes run in the Dashboard and API, or Stripe handles them under its Managed Payments merchant-of-record option, and 2Checkout documents a bank-decided process with merchant evidence due within three working days (see 2Checkout vs Stripe). For Clover, the response deadline and fees come from your acquirer or processor (see Clover vs PayPal).
Map the Product to the Case Route and Connection
For ordinary card disputes, the issuer reviews evidence under network rules. A processor transports the response; a merchant-of-record product changes who is the seller and manages the case. Wallet and local-method claims have their own decision routes. Keep those distinctions when using this product-by-route reference.
| Fournisseur | Product/seller scope | Case route and response owner | Chargeflow processor catalog |
|---|---|---|---|
| 2Checkout | Selected 2Checkout product; verify whether the contract uses a MoR model. | Follow the 2Checkout case and exact product agreement. | Not listed |
| Adyen | Merchant’s acquiring/PSP account; card issuer decides ordinary card cases. | Merchant response through the configured Adyen dispute workflow. | Available |
| Airwallex | Merchant’s selected acquiring/PSP account. | Configured Airwallex case; verify card versus local-method route. | Nouveau |
| Authorize.net | Gateway plus the named merchant service provider/acquirer. | Card cases go through that merchant service provider, not a gateway-only response assumption. | Nouveau |
| Braintree | Merchant account and selected card or PayPal payment method. | Braintree card case or PayPal case, with separate case IDs and decision routes. | Available |
| Checkout.com | Merchant’s acquiring/PSP account and selected payment method. | Configured processor case; merchant response owner and case deadline. | Available |
| Dépôt | Exact processor/acquirer and merchant agreement need confirmation. | Follow the case notice’s processor/acquirer; do not infer from the service brand. | Available |
| Paiements internationaux | Named acquiring product and merchant entity. | Contracted processor/acquirer dispute channel; confirm exact product. | Available |
| Luqra | Exact processor/acquirer and merchant agreement need confirmation. | Follow the case notice’s processor/acquirer; public product scope is not a case owner. | Not listed |
| Mollie | Merchant’s PSP product and payment method. | Configured Mollie card or local-method case; confirm decision route. | Not listed |
| Nuvei | Named acquiring/PSP product and payment method. | Configured Nuvei case and merchant response owner. | Available |
| Rame | Paddle’s MoR product for eligible sales. | Paddle manages the payment case; merchant supplies requested product/service records. | Not listed |
| PayPal | Direct PayPal Checkout merchant account. | Resolution Center for PayPal claims; funding-card issuer cases are separate. | Available |
| Rapyd | Selected acquiring/PSP or platform product. | Confirm account, actual notice recipient and case channel for that product. | Not listed |
| Square | Merchant’s Square payment account. | Merchant response in Square; issuer decides ordinary card cases. | Available |
| Stripe | Stripe Payments: merchant is seller. Managed Payments: Stripe is MoR. | Payments card evidence goes through Stripe to issuer; Managed Payments has separate ownership. | Available for Stripe processor |
| WePay | Current platform/account and product scope unconfirmed. | Verify active account, processor and dispute owner before expanding this row. | Not listed |
| Worldpay | Named Worldpay acquiring product and merchant entity. | Use the contracted product’s dispute channel; ownership changes do not prove systems merged. | Not listed |
Shared join: ecommerce order ID → charged payment reference → refund reference → case ID → final balance adjustment. The seller, account and response owner must come from the selected product agreement and case notice. A connector’s presence does not establish coverage for every branded product, wallet route or case type.
Available/New statuses come from the Chargeflow integration catalog. “Not listed” means the current catalog does not name that provider, not that an API workflow is impossible. Confirm any API route with the team. Product-specific sources include Stripe’s decision-route guidance, Stripe’s MoR scope, Paddle’s MoR service scope and Square’s issuer-decision workflow. The detailed comparisons linked below cover the selected provider workflows. Unconfirmed account/product rows require the current agreement. Checked October 6, 2026.
Build a Shortlist Around Your Business
Illustrative payment shortlists: confirm current eligibility and the selected product
- Examples to Include in Your Evaluation
- Stripe, Braintree, Checkout.com, PayPal, and Authorize.net configurations.
- Demonstrate With Your Data
- Checkout, payment methods, saved credentials, refunds, and order matching.
- Examples to Include in Your Evaluation
- Adyen, Square, Worldpay, Global Payments, and Luqra configurations.
- Demonstrate With Your Data
- Payment and refund visibility across channels and locations.
- Examples to Include in Your Evaluation
- Paddle and relevant 2Checkout packages; compare direct-PSP architectures where you retain the seller role.
- Demonstrate With Your Data
- Billing, tax responsibilities, cancellations, payouts, and customer support.
- Examples to Include in Your Evaluation
- Adyen, Airwallex, Checkout.com, Mollie, Nuvei, Rapyd, Stripe, and Worldpay configurations.
- Demonstrate With Your Data
- Merchant entities, local methods, presentment and settlement currencies, FX, and reporting.
- Examples to Include in Your Evaluation
- Platform-provided WePay accounts, Stripe platform products, Rapyd, Deposyt, Luqra, and relevant acquiring arrangements.
- Demonstrate With Your Data
- Onboarding, support ownership, account relationships, reconciliation, and evidence access.
The groups overlap and are not exhaustive. They organize discovery conversations; they do not rank providers or imply that other providers lack a capability.
Test Settlement, Integrations, and Dispute Operations
Give each provider the same transaction file and workflow requirements. The most useful payment comparison records how the proposed configuration will work for your business, including the steps after checkout.
- Define the merchant’s markets and setup
List each merchant entity, shopper market, currency, and payment method you plan to support.
- Use the same transaction sample
Give each provider the same transaction file and workflow requirements.
- Test checkout and money movements
Complete representative payments, declines, authentication, retries, refunds, and a settlement trace.
- Verify integrations and evidence access
Show how a dispute reaches the responsible team and retrieve the transaction, order, fulfillment, and service records.
- Record outcomes and owners
Record results, owners, and a consistent definition of closed cases in the matrix below.
A reusable payment-provider evaluation with observable outcomes
- Exact Test
- Onboard each planned merchant entity and demonstrate required local payment methods.
- Record
- Entity eligibility, shopper markets, currencies, and contracted services.
- Exact Test
- Complete representative payments, declines, authentication, retries, and refunds.
- Record
- Successful outcomes, errors, manual steps, and customer experience.
- Exact Test
- Trace a captured payment through fees, payout, refund adjustment, and bank reconciliation.
- Record
- Capture cutoff, settlement initiation, bank arrival, references, and adjustment handling.
- Exact Test
- Show how a case reaches the responsible team.
- Record
- Notification channel, case ID, reason, actual deadline, and owner.
- Exact Test
- Retrieve transaction, authentication, order, fulfillment, policy, and service records.
- Record
- Fields available, permissions, submission channel, and measured handling time.
- Exact Test
- Trace a resolved case into recovered funds, fees, reversals, and finance reporting.
- Record
- A consistent definition of closed cases, costs, and retained revenue.
For a multi-PSP setup, use a shared order identifier and document refund routing, token portability, notification ownership, and reconciliation. Test the transition between providers with your implementation team. Record what the customer sees and how finance connects each event to the original order.
Measure Dispute Outcomes With Consistent Definitions
Provider capabilities are easiest to assess when the data uses the same definitions. Record the disputes received, cases challenged, responses submitted on time, final outcomes, evidence completeness, handling time, and net recovered revenue. State the denominator and time period for every rate.
For Visa monitoring, processors document the Visa Acquirer Monitoring Program (VAMP) with their own ratio definitions. Braintree describes CNP fraud reported via TC 40 plus opened chargebacks over settled transactions, and Adyen describes fraudulent transactions plus non-fraudulent disputes over sales count. Both list a 1.50% merchant ratio threshold from April 1, 2026, and Braintree documents a 1,500-instance count criterion. See Adyen vs Braintree and confirm the threshold and region for your merchant account.
Compare merchant populations and case types consistently before drawing conclusions about outcomes. A workflow test can show where automation and connected evidence add value without treating different merchants’ chargeback win rates as a provider ranking.
How Chargeflow Complements Your Payment Provider
Chargeflow’s integration documentation lists supported dispute sources separately from ecommerce, subscription, and customer-communication sources. For example, its catalog lists Stripe, PayPal, Braintree, Adyen, Checkout.com, Square, Nuvei, Global Payments, and Deposyt as available processor connections, with Airwallex and Authorize.net labeled New. Check the current catalog for your exact setup; the documentation table checked October 4, 2026 did not list Worldpay or Clover, and being featured in this comparison does not by itself establish native connection availability.
Your payment provider delivers the selected acceptance and financial services. Chargeflow adds specialized chargeback operations, including automated case handling, evidence enrichment, and analytics across supported connections. Schedule a demo to map the payment and evidence workflow for your shortlisted providers.
For storefront and order-data requirements, see the ecommerce platform comparison. For Klarna, Afterpay, Affirm, and Sezzle, see the BNPL comparison for merchants.
Explore Detailed Payment Provider Comparisons
Online Gateways and PSPs
- Adyen vs Airwallex
- Adyen contre Braintree
- Authorize.net vs Stripe
- Braintree vs Authorize.net
- Checkout.com contre Adyen
- Checkout.com contre Stripe
- Mollie contre Adyen
- Mollie contre Stripe
- Nuvei contre Stripe
- Rapyd vs Stripe
- Stripe contre Adyen
- Stripe vs Airwallex
- Stripe contre Braintree
- Worldpay contre Airwallex
- Worldpay vs Stripe
In-Person and Omnichannel Providers
- Clover contre Square
- Clover contre Stripe
- Global Payments contre Square
- Global Payments vs Stripe
- Global Payments vs Worldpay
- Stripe contre Square
Wallet and Branded Checkout Providers
Merchant-of-Record and Digital Commerce Providers
Platform and Service-Led Providers
Pay-Over-Time Providers
- Affirm vs Afterpay
- Affirm contre PayPal
- Klarna vs Affirm
- Klarna ou Afterpay ?
- Sezzle vs Affirm
- Sezzle vs Afterpay
- Sezzle vs Klarna
Payment Gateway Questions
What Is the Difference Between a PSP and a Payment Gateway?
A payment gateway transmits payment information from checkout to the processing chain. A PSP packages payment acceptance services that may include a gateway, processing, acquiring, settlement, and reporting. When comparing providers, specify the services included in the actual contract and identify which parties own settlement and dispute handling.
How Do I Compare Payment Gateway Fees?
Compare payment gateway fees using the same transaction volume, average order value, payment methods, card origins, currencies, and required products. Add monthly, gateway, processing, FX, refund, dispute, and operational costs. Keep gateway-only fees separate from acquiring charges and compare merchant-of-record packages using their full service scope.
Which Payment Gateway Fits an Ecommerce Business?
An ecommerce business should select a payment configuration that supports its storefront, customer markets, checkout requirements, refunds, and reconciliation. Compare the complete integration, including how orders and fulfillment records connect to payment and dispute references. Use the provider table to build a shortlist and validate it with representative transactions.
Should a SaaS Company Use a PSP or Merchant of Record?
A SaaS company can use a PSP while retaining its seller responsibilities, or evaluate a merchant-of-record package that takes on defined payment, tax, and related operations. Compare billing features, supported products and markets, migration, payouts, customer support, and data access. Match the model to the responsibilities your business wants to manage.
What Should Treasury Teams Compare Across Payment Providers?
Treasury teams should compare merchant entities, settlement currencies, payout timing, FX, reserves where applicable, reconciliation files, and account structure. Trace the same payment from capture to bank arrival and include refunds and dispute adjustments. This shows how the proposed payment stack connects to your cash-flow and financial reporting processes.
Can a Merchant Use Multiple PSPs?
A merchant can use multiple PSPs where its architecture and agreements support that setup. Define which transactions each provider handles and connect orders, refunds, disputes, and settlements through stable identifiers. Test token portability, routing, notifications, and finance reconciliation with the implementation team before expanding traffic.
Which Chargeback Solution Connects With PSPs and Gateways?
Chargeflow provides chargeback operations across the processor connections listed in its integration catalog. Supported payment sources bring in disputes, while connected commerce and customer-service systems can enrich evidence. Confirm the provider, merchant account, supported case types, and implementation path for your business.
Choose a Payment Stack With Clear Ownership
- Shortlist the operating models and products that fit your business.
- Compare commercial proposals using the same transaction mix.
- Demonstrate checkout, settlement, refunds, and evidence retrieval.
- Assign owners and definitions for dispute outcomes and finance reporting.
How This Comparison Was Prepared
Chargeflow Experts reviewed the linked provider documentation on October 4, 2026. This payment gateway comparison compares documented capabilities and operating models. Chargeflow lists integration pages for the featured providers, and native connection status is shown separately in its documentation. Provider descriptions explain business fit; they are not a performance ranking. Availability and commercial terms depend on your market, product, plan, and agreement.
Worked examples are illustrative calculations. The evaluation exercises are practical methods you can run with your own data; they are not claims that Chargeflow conducted a controlled test of the providers. Source links appear beside the facts they support.
rétrofacturation?
Ce n'est plus votre problème.
Récupérez 4 fois plus d'rétrofacturation s et PRÉVENTION jusqu'à 90 % des messages entrants, grâce à l'IA et à un réseau mondial de 20 000 commerçants.
.png)