How to Compare Payment Gateway Providers: A Merchant Checklist

Gate one is identity and geography: will the proposed contracting entity onboard your exact legal company, ownership structure and settlement account? Gate two is activity: are your actual products, distribution model and customer markets within the written scope? Gate three is transaction flow: can the arrangement support subscriptions, delayed capture, refunds or third-party sellers where required? Ask for a precise response to each gate, with exclusions and outstanding conditions.

An unanswered critical gate puts the candidate on hold. A confirmed conflict excludes it from this procurement round. This prevents a technically attractive gateway from winning a comparison that it cannot fulfil. For specialist businesses, separate the commercial introduction from the acquiring or underwriting decision and identify who is authorized to confirm each.

Choose the payment methods that matter to your customer mix, then inspect the supported implementation. Adyen’s documentation separates methods, processing currencies, settlement currencies, features and integrations rather than treating them as interchangeable attributes. [5] Build your own equivalent matrix. Does the method support the refund pattern, recurring arrangement and capture sequence you need? Is it available through the plugin you plan to use, or only through a different integration?

A wallet logo alone cannot answer those questions. Ask the technical team to demonstrate the required flow in a test environment and identify account-level activation requirements. Keep optional enhancements outside the minimum launch specification so a long feature list does not distract from a missing essential capability.

Use the same volume, transaction count, customer-country mix and currency assumptions for every proposal. Adyen’s pricing page illustrates why a processing component and a payment-method component can need separate treatment; other products can have separate prices. [1] The original calculation below uses invented quotes, not rates from any named provider. Both offers cost $3,000 for transaction processing on $100,000 across 2,000 transactions, even though their headline percentages differ. After the stated extras, the totals are $3,860 and $3,360.

The $500 difference is worth investigating, but neither quote wins until eligibility and settlement are acceptable. Add refunds, disputes, failed-payment fees and implementation costs where relevant; do not assume an omitted line is free. Record whether the calculation includes taxes and minimum commitments.

A reserve affects liquidity even when it is potentially recoverable, so it belongs beside the cost comparison rather than being disguised as a processing fee. Under a hypothetical arrangement withholding 5% of $100,000 of eligible monthly sales, $5,000 is initially unavailable. That is separate from the fee totals above; release depends on the actual contract.

Request a dated cash-flow example showing capture, availability, payout initiation and bank arrival. Stripe explicitly distinguishes payout frequency from the time pending funds take to become available. [2] Also distinguish the currency charged to a customer from the currency arriving in the bank; Stripe’s currency documentation treats these separately. [3] Ask which party converts, on what basis, and whether a second conversion occurs at your bank.

A successful test purchase is the beginning of acceptance testing. Follow it through capture, partial refund, cancellation, webhook delivery and reconciliation. Test a network timeout and verify that retry behaviour does not create duplicate orders. Check how your system distinguishes an unpaid order, an authorized amount and a captured transaction.

Give finance a sample payout report and require them to trace the net amount back to individual sales and deductions. These are proposed procurement checks, not claims that every gateway implements the same controls. For migration, establish whether stored credentials can be transferred, who must authorize the transfer, and what subscriptions would require customer action. An inexpensive integration can become expensive if essential reconciliation or migration work was excluded from the project estimate.

Ask who handles integration incidents, payout queries, disputes and changes to the approved business scope. Request support hours, escalation routes and any contractual service levels instead of inferring them from a chat response. Obtain termination notice, outstanding-fee treatment, data export and credential portability terms before signing.

Outsourcing checkout also leaves merchant responsibilities to resolve: PCI SSC says merchants must understand shared duties and confirm their validation obligations with the relevant compliance-accepting entity. [4] Ask your provider or acquirer for the requirements applicable to the actual implementation. A hosted payment page may reduce the work in your environment, but it is not permission to ignore your website, access controls or the security responsibilities set out in the agreement.

After the gates, evaluate eligible candidates against four practical questions: complete cost, usable cash, required payment behaviour and operational effort. Rate the evidence as documented, demonstrated, proposed or unknown. Keep an owner and a deadline against every open item. Weight the criteria according to your business: an invoiced B2B operation may prioritize reconciliation, while a subscription company may prioritize renewal continuity and migration.

Do not average away a critical failure with several attractive extras. Where the result depends on an assumption, rerun the calculation with a plausible alternative. For example, increase the cross-border share or refund count and see whether the preferred offer changes. A comparison that changes winner under small assumption changes needs more evidence before commitment.