US BUYER’S GUIDE · 5 PRODUCTS

Payment Processing

Which payment stack fits your sales channels, transaction mix and operational workload?

Compare US payment providers for online checkout, invoices, recurring charges and connected payment operations.

Research desk · Oct 20, 2026 · Methodology

YOUR SHORTLIST STARTS HERE

Compare the options.

Sort by

Highest documented score first. Fit adds up the 28 feature checks below, including AI, across documented plans. Entry price does not include every capability. Unknown evidence appears as a range.

Product / good fit for	Pricing context	Documented fit	Next step
Stripe Businesses wanting developer flexibility alongside no-code payment options.	Usage basedsuccessful domestic online card transactionPayments Standard	84–100/100 documented fit 84% evidence coverage	Full research →
Adyen Larger merchants with an integration team and complex payment requirements.	Usage basedtransaction and methodConfigured payments	72–100/100 documented fit 72% evidence coverage	Full research →
PayPal Merchants adding PayPal and Venmo alongside card acceptance.	Usage basedtransaction by methodBusiness payments	67–100/100 documented fit 67% evidence coverage	Full research →
Square Small operators connecting checkout and everyday business workflows.	$0.00location/monthFree	46–100/100 documented fit 46% evidence coverage	Full research →
Authorize.net Businesses evaluating a gateway with an existing or new merchant account.	$25.00month plus transaction feesGateway / All-in-One	38–100/100 documented fit 38% evidence coverage	Full research →

BEYOND A FEATURE CHECKMARK

How deep does the capability go?

Choose up to 3 for a closer look →

28 weighted checks: core capabilities contribute 32 points and workflow depth contributes 68. AI is included at the weight shown for this category. Expand Evidence for scope and sources, or ask for the same demonstration from each supplier.

Show checksShowing fewer rows does not change the score.

Payment Processing features for all 5 products
Feature / base weight	Stripe 84–100/100 documented fit Core capabilities32 / 32 pts10/10 checks with established status Workflow depth52.3–68 / 68 pts12/18 checks with established status	Adyen 72–100/100 documented fit Core capabilities26.4–32 / 32 pts8/10 checks with established status Workflow depth45.9–68 / 68 pts11/18 checks with established status	PayPal 67–100/100 documented fit Core capabilities26.4–32 / 32 pts8/10 checks with established status Workflow depth40.8–68 / 68 pts9/18 checks with established status	Square 46–100/100 documented fit Core capabilities24.8–32 / 32 pts8/10 checks with established status Workflow depth21.6–68 / 68 pts5/18 checks with established status	Authorize.net 38–100/100 documented fit Core capabilities18.4–32 / 32 pts5/10 checks with established status Workflow depth20–68 / 68 pts4/18 checks with established status
Core capabilityOnline payment checkout4.8 points · Accept a customer payment through a hosted or integrated checkout.	Supported4.8 / 4.8 pts Evidence Hosted Checkout and Payment Links support online collection. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Online payment integrations support merchant checkout. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence PayPal offers online checkout for business payments. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Square supports online checkout and online collection. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence The gateway supports online merchant payment collection. Official documentation · Oct 15, 2026Source
Core capabilityCards plus alternative methods4.8 points · Offer card acceptance and at least one supported wallet or bank-payment method.	Supported4.8 / 4.8 pts Evidence Cards and multiple alternative payment methods are documented. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Multiple card and alternative payment methods are documented. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence The documented acceptance options include cards, PayPal and Venmo. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed generic payment source does not establish the full non-card method list. Not verified · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Recurring-payment documentation explicitly covers card and eCheck methods. Official documentation · Oct 15, 2026Source
Depth checkPartial refunds7.2 points · Refund less than the original payment and retain the remaining balance. Ask for a demonstration Refund one item from a multi-item payment and show the remaining refundable amount. A scenario to run with the supplier; not a completed product test.	Supported7.2 / 7.2 pts Evidence The Refunds API supports repeated partial refunds up to the original total. Official documentation · Oct 15, 2026Source	Supported7.2 / 7.2 pts Evidence The payment testing guide explicitly includes partial refund flows. Official documentation · Oct 15, 2026Source	Not verified0–7.2 / 7.2 pts Evidence The reviewed documentation does not establish this specific workflow: partial refunds. Not verified · Oct 15, 2026Source	Supported7.2 / 7.2 pts Evidence Refunds support custom amounts up to the remaining sale total. Official documentation · Oct 15, 2026Source	Supported7.2 / 7.2 pts Evidence Transaction details provide full or partial refund actions. Official documentation · Oct 15, 2026Source
Depth checkCustomer authentication controls7.2 points · Support an additional cardholder authentication flow such as 3D Secure. Ask for a demonstration Run a payment that requires cardholder authentication and show the resulting status. A scenario to run with the supplier; not a completed product test.	Supported7.2 / 7.2 pts Evidence The payment flow supports automatic or explicitly requested 3D Secure authentication. Official documentation · Oct 15, 2026Source	Supported7.2 / 7.2 pts Evidence Checkout supports 3D Secure authentication and returns authentication outcomes. Official documentation · Oct 15, 2026Source	Supported7.2 / 7.2 pts Evidence Expanded Checkout supports 3D Secure cardholder authentication. Official documentation · Oct 15, 2026Source	Not verified0–7.2 / 7.2 pts Evidence The reviewed documentation does not establish this specific workflow: customer authentication controls. Not verified · Oct 15, 2026Source	Not verified0–7.2 / 7.2 pts Evidence The reviewed documentation does not establish this specific workflow: customer authentication controls. Not verified · Oct 15, 2026Source
Core capabilityInvoice-based collection3.2 points · Create or send an invoice for customer payment.	Supported3.2 / 3.2 pts Evidence Stripe Invoicing is separately priced from basic card processing. Official documentation · Oct 15, 2026Source	Not verified0–3.2 / 3.2 pts Evidence Payment tokenization is not proof of an invoice-creation product. Not verified · Oct 15, 2026Source	Not verified0–3.2 / 3.2 pts Evidence Subscription documentation does not establish merchant invoice creation. Not verified · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Square provides customer invoicing. Official documentation · Oct 15, 2026Source	Not verified0–3.2 / 3.2 pts Evidence Merchant invoice creation was not established by the reviewed recurring-payments source. Not verified · Oct 15, 2026Source
Core capabilityRecurring customer charges3.2 points · Schedule repeat payments or subscriptions using stored payment credentials.	Supported3.2 / 3.2 pts Evidence Subscription management uses the separately priced Billing product. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Tokenization supports subscription and unscheduled repeat charges. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence The subscriptions product and API support repeat customer charges. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Recurring invoices are documented. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Automated Recurring Billing schedules card or eCheck charges. Official documentation · Oct 15, 2026Source
Depth checkFailed recurring payment recovery4.8 points · Retry a failed renewal or provide a recovery workflow for an unpaid recurring charge. Ask for a demonstration Fail a renewal and show the retry or payment recovery sequence. A scenario to run with the supplier; not a completed product test.	Supported4.8 / 4.8 pts Evidence Subscription billing supports retries and configured handling after retries are exhausted. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: failed recurring payment recovery. Not verified · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Failed subscription payments are retried with configured failure thresholds. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: failed recurring payment recovery. Not verified · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Automatic Retry preserves suspended recurring subscriptions for recovery. Official documentation · Oct 15, 2026Source
Depth checkStop or pause recurring billing4.8 points · Cancel or suspend future recurring charges without erasing payment history. Ask for a demonstration Stop a subscription and show its history and next-charge state. A scenario to run with the supplier; not a completed product test.	Supported4.8 / 4.8 pts Evidence Subscriptions can cancel immediately or at the end of the billing period. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: stop or pause recurring billing. Not verified · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Subscription cancellation and suspension produce documented status events. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: stop or pause recurring billing. Not verified · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence ARB documentation describes editing, suspension and cancellation of recurring subscriptions. Official documentation · Oct 15, 2026Source
Core capabilityTransaction-level reports3.2 points · Inspect payment, refund and fee records for reconciliation.	Supported3.2 / 3.2 pts Evidence Payment and balance reporting exposes transaction detail. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Settlement Details reports expose payment-level amounts and transaction costs. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Detailed transaction settlement reports require approved-merchant and SFTP access. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Payment reporting provides transaction information. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Reporting APIs expose gateway transaction history. Official documentation · Oct 15, 2026Source
Core capabilityPayout or settlement reporting3.2 points · Connect transactions with the settlement or payout reported by the provider.	Supported3.2 / 3.2 pts Evidence Payout reconciliation reports connect activity with payouts. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Settlement Details supports transaction-to-settlement reconciliation. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Settlement reports support reconciliation for approved merchants with SFTP setup. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Transfer reporting supports payment-to-payout reconciliation. Official documentation · Oct 15, 2026Source	Not verified0–3.2 / 3.2 pts Evidence Gateway history does not itself establish merchant-bank payout reconciliation. Not verified · Oct 15, 2026Source
Depth checkGross, fees and net reconciliation4.8 points · Inspect transaction or settlement records distinguishing gross collections, fees and net proceeds. Ask for a demonstration Trace a payout to gross payments, fees and net proceeds. A scenario to run with the supplier; not a completed product test.	Supported4.8 / 4.8 pts Evidence Stripe financial reports expose payment, fee and balance activity. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Settlement details expose transaction-level amounts and fees for payout reconciliation. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Capture notifications expose gross amount, PayPal fee and net proceeds. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: gross, fees and net reconciliation. Not verified · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: gross, fees and net reconciliation. Not verified · Oct 15, 2026Source
Depth checkDispute evidence workflow4.8 points · Receive a dispute and submit or manage supporting evidence through a supported workflow. Ask for a demonstration Open a dispute and show where evidence and response deadlines are managed. A scenario to run with the supplier; not a completed product test.	Supported4.8 / 4.8 pts Evidence Disputes accept evidence through the Dashboard or API. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence Dispute management accepts supporting documents through Customer Area or the API. Official documentation · Oct 15, 2026Source	Supported4.8 / 4.8 pts Evidence The Disputes API accepts evidence including proof of delivery or refunds. Official documentation · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: dispute evidence workflow. Not verified · Oct 15, 2026Source	Not verified0–4.8 / 4.8 pts Evidence The reviewed documentation does not establish this specific workflow: dispute evidence workflow. Not verified · Oct 15, 2026Source
Core capabilityPayment API2.4 points · Create or manage payment transactions using a documented developer API.	Supported2.4 / 2.4 pts Evidence Payment APIs and SDKs are documented. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Sessions and Advanced API flows are documented. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Checkout and subscriptions developer interfaces are documented. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence The platform offers payment APIs. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Payment, profile, recurring and reporting APIs are documented. Official documentation · Oct 15, 2026Source
Core capabilityPrebuilt checkout or connectors2.4 points · Use a prebuilt payment component, checkout or supported connector.	Supported2.4 / 2.4 pts Evidence Hosted Checkout and prebuilt payment UI are available. Official documentation · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence A prebuilt component or connector needs specific evidence beyond the reviewed API-flow record. Not verified · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence The checkout product provides a prebuilt integration path. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence The app marketplace and connected payment tools offer prebuilt integration options. Official documentation · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence A prebuilt checkout component or connector needs a feature-specific source. Not verified · Oct 15, 2026Source
Depth checkWebhook delivery recovery3.2 points · Document delivery retries or a supported way to recover failed event notifications. Ask for a demonstration Make an event endpoint fail and show retry or replay behavior. A scenario to run with the supplier; not a completed product test.	Not verified0–3.2 / 3.2 pts Evidence The reviewed documentation does not establish this specific workflow: webhook delivery recovery. Not verified · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Failed webhooks enter a retry queue with troubleshooting and retry tools. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Failed webhook delivery is retried, with duplicate-safe processing recommended. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Webhook delivery is retried; event IDs let integrations suppress duplicate processing. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Failed webhook notifications are retried up to ten times. Official documentation · Oct 15, 2026Source
Depth checkDuplicate payment request protection4 points · Use a documented idempotency or duplicate-request mechanism when retrying payment requests. Ask for a demonstration Submit the same payment request twice and show how duplication is prevented. A scenario to run with the supplier; not a completed product test.	Supported4 / 4 pts Evidence Idempotency keys preserve the response when a payment API request is retried. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence Payment modification requests accept an Idempotency-Key header. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence State-changing operations support idempotency keys for retry protection. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence CreatePayment accepts an idempotency key for safe request retry. Official documentation · Oct 15, 2026Source	Not verified0–4 / 4 pts Evidence The reviewed documentation does not establish this specific workflow: duplicate payment request protection. Not verified · Oct 15, 2026Source
Core capabilityMachine-learning fraud screening2.4 points · Use explicitly documented machine learning to assess payment fraud risk.	Supported2.4 / 2.4 pts Evidence Radar explicitly uses machine learning to evaluate payment fraud risk. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Advanced machine-learning risk controls require Protect premium. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Machine-learning Fraud Protection is restricted to eligible card integrations. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Square risk evaluations use proprietary machine-learning models. Official documentation · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence Fraud rules were found, but machine-learning fraud screening was not established. Not verified · Oct 15, 2026Source
Core capabilityAI payment acceptance optimization2.4 points · Use documented AI or machine learning to improve authorization, authentication or retry decisions.	Supported2.4 / 2.4 pts Evidence The reviewed AI record documents payment-acceptance optimization; optional product fees can apply. Official documentation · Oct 15, 2026Source	Supported2.4 / 2.4 pts Evidence Uplift documents payment-acceptance optimization. Official documentation · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence The reviewed Fraud Protection source does not establish AI payment-acceptance optimization. Not verified · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence Business-data questions do not establish AI authorization or retry optimization. Not verified · Oct 15, 2026Source	Not verified0–2.4 / 2.4 pts Evidence AI payment-acceptance optimization was not established. Not verified · Oct 15, 2026Source
Depth checkExplain machine-learning risk flags3.2 points · Expose risk indicators, reasons or review context for a machine-learning risk decision. Ask for a demonstration Open an ML-flagged transaction and show the information available to a reviewer. A scenario to run with the supplier; not a completed product test.	Supported3.2 / 3.2 pts Evidence Radar risk evaluation exposes risk levels and review context for transactions. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Risk notifications expose triggered-rule results and review outcomes. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Fraud Protection exposes risk-filter results for transaction review. Official documentation · Oct 15, 2026Source	Supported3.2 / 3.2 pts Evidence Risk evaluations show transaction risk indicators for merchant review. Official documentation · Oct 15, 2026Source	Not verified0–3.2 / 3.2 pts Evidence AFDS rule results are documented, but ML-specific explanations were not established. Not verified · Oct 15, 2026Source
Depth checkHuman control over AI risk handling4 points · Allow a merchant to review, override or configure the handling of machine-learning risk decisions. Ask for a demonstration Show how staff review or change the handling of an ML risk flag. A scenario to run with the supplier; not a completed product test.	Supported4 / 4 pts Evidence Radar supports review, allow lists and merchant rules alongside ML risk decisions. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence Risk handling supports manual review alongside automated risk decisions. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence Fraud Protection allows merchant configuration and handling of flagged payments. Official documentation · Oct 15, 2026Source	Supported4 / 4 pts Evidence Merchants can review flagged transactions and choose the appropriate handling. Official documentation · Oct 15, 2026Source	Not verified0–4 / 4 pts Evidence AFDS manual review exists; control of an explicitly ML-driven decision was not established. Not verified · Oct 15, 2026Source
Depth checkMeasure AI risk-model false positives on labelled payments2.5 points · Demonstrate “Measure AI risk-model false positives on labelled payments” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Measure AI risk-model false positives on labelled payments” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkAuthorise now and capture funds later2.5 points · Demonstrate “Authorise now and capture funds later” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Authorise now and capture funds later” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Supported2.5 / 2.5 pts Evidence An eligible PaymentIntent in requires_capture can be captured later, up to its capturable amount. PaymentIntents API; supported payment methods; authorisation remains subject to expiry and capture limits. Official documentation · Oct 21, 2026Source	Supported2.5 / 2.5 pts Evidence The documented preauthorisation workflow captures funds manually after the final amount is known. Eligible preauthorisation workflow; configure manual capture; method-specific expiry and rules apply. Official documentation · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkAccept a partial card authorisation2.5 points · Demonstrate “Accept a partial card authorisation” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Accept a partial card authorisation” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Supported2.5 / 2.5 pts Evidence Eligible card payments can authorise the available balance and collect the remainder by another method. Checkout API v69+ advanced flow; support activation; eligible Visa/Mastercard issuers; not Sessions flow. Official documentation · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkIncrease an existing eligible authorisation2.5 points · Demonstrate “Increase an existing eligible authorisation” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Increase an existing eligible authorisation” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Supported2.5 / 2.5 pts Evidence Eligible uncaptured payments support requests to increase their authorised amount. PaymentIntents API; requires_capture and incremental_authorization_supported must be true; issuer approval and attempt limits apply. Official documentation · Oct 21, 2026Source	Supported2.5 / 2.5 pts Evidence A supported preauthorisation can be increased or decreased before manual capture. Preauthorisation; Adyen-acquired payments, supported methods and merchant categories; issuer approval and expiry apply. Official documentation · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkRefresh network tokens after a card replacement2.5 points · Demonstrate “Refresh network tokens after a card replacement” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Refresh network tokens after a card replacement” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkConfigure the customer bank-statement descriptor2.5 points · Demonstrate “Configure the customer bank-statement descriptor” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Configure the customer bank-statement descriptor” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Supported2.5 / 2.5 pts Evidence Card charges can combine an account-level statement prefix with a transaction-specific suffix. Latin-character and length rules apply; dynamic suffixes are card-only; issuing banks control final display. Official documentation · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkRestrict API keys to specified payment operations2.5 points · Demonstrate “Restrict API keys to specified payment operations” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Restrict API keys to specified payment operations” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source
Depth checkTrace and resolve a failed merchant payout2.5 points · Demonstrate “Trace and resolve a failed merchant payout” with a sample record; show the result, permissions and required plan. Ask for a demonstration Demonstrate “Trace and resolve a failed merchant payout” with a sample record; show the result, permissions and required plan. A scenario to run with the supplier; not a completed product test.	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source	Not verified0–2.5 / 2.5 pts Evidence This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified · Oct 21, 2026Source

WHAT WE MEASURE

The criteria behind the score.

The established 20 checks contribute 80 points. Eight new operational checks contribute 20 points. AI checks are included in their own group and are excluded when AI priority is set to zero. These assess documented capability scope, not measured performance. Adjust group priorities in the comparison tool.

See the complete calculation →

Checkout & payment methods 24%
Match the channels and methods your customers actually use.
Invoices & recurring payments 16%
Repeat charging and collection workflows can require separate products.
Payouts & reconciliation 16%
Finance must match gross orders, fees, refunds and net deposits.
APIs & integration options 12%
Implementation flexibility and available connectors affect ownership cost.
AI fraud & payment optimization 14.5%
Assess documented risk or acceptance intelligence and its paid tiers.
Operational detail 17.5%
Specific workflow, integration and control checks beyond the established rubric.

THE PRACTICAL BUYER’S GUIDE

How to choose payment processing.

A payment processor should be compared using your real transaction mix, not one headline percentage. Online cards, keyed payments, ACH, international cards, refunds and disputes can have different costs and operational consequences. A gateway-only service also requires a merchant account, while an integrated platform may combine acceptance, payout reporting and risk tools. Decide whether you want payment links that a small team can launch quickly or infrastructure that developers will embed in a larger product. Fraud AI belongs in this comparison, but its value depends on false declines and review work as well as fraud losses.

Model a representative transaction basket

Create a worksheet with monthly card volume, average ticket size, transaction count, card-present share, international-card share and ACH usage. Include refunds, disputes and expedited payouts. Apply each provider's named fee schedule to that same basket. A low percentage can be offset by a higher fixed charge on small transactions, and interchange-plus pricing cannot be compared honestly without assumptions about the cards used. Keep optional products such as billing, tax calculation, enhanced fraud protection and marketplace payouts on separate rows. The result should explain what changes the bill rather than pretend a single universal cheapest provider exists.

Trace one order through the entire money flow

During evaluation, follow a successful payment, a failed payment, a refund and a dispute from checkout through the payout report and accounting export. Ask which identifier links the customer order to the bank deposit and where fees appear. If you sell subscriptions, test a failed renewal and a replacement card. If you operate a platform, map responsibilities for onboarding sellers and handling disputes before selecting a connected-account product. Confirm whether a payment link, hosted checkout or fully customized integration fits the team you have. A developer-friendly API is valuable only if someone owns its operation.

Evaluate risk tools with conversion in mind

Ask how the risk system explains decisions, how your team reviews a blocked transaction and whether rules can be tested before enforcement. Machine-learning fraud screening is a different type of AI from a merchant-facing conversational assistant. Compare it on the intended payment task. Request the precise product tier, additional fees and implementation requirements for advanced models or custom rules. In a pilot, record legitimate orders declined as well as suspected fraud caught. Never treat a vendor's general claim of better authorization or less fraud as a prediction of your own business's outcome.

What changes the total cost?

Transaction percentage plus fixed fee, card origin, payment method and average order value.
Billing, enhanced fraud tools, disputes, refunds, currency conversion and faster payouts.
Gateway or merchant-account charges, engineering work and ongoing reconciliation.

Where purchases go wrong

Comparing gateway-only fees with an all-in-one processing rate.
Assuming a subscription-management product is included in the base card rate.
Choosing fraud settings without measuring legitimate orders that are declined.

Bring these questions to the demo

Can we reconcile a payout containing payments, refunds, fees and a dispute?
Which fees apply to our online, in-person, international and ACH mix?
Who owns retries, webhooks and failed-payment recovery in our integration?
Which fraud AI features are included, optional or restricted by account eligibility?

Questions buyers ask

Is a percentage rate enough to compare processors?

No. Fixed fees and the transaction basket matter. A business with many small orders may experience a different effective rate from one with fewer large invoices. Model the same volume, ticket size and optional services for every provider.

Does accepting payments mean the provider is our accounting system?

No. Payment reporting explains the movement of money, while accounting records the wider business. Verify the integration and how gross sales, fees, refunds and deposits map to the ledger. An exported total alone may not provide enough detail.

Should every business use advanced fraud AI?

Start with the risk and operating workflow you need. Advanced controls can be useful, but may add fees and review tasks. Evaluate whether the configuration improves your actual balance of fraud loss, legitimate acceptance and staff effort.

Payment Processing

Compare the options.

Stripe

Adyen

PayPal

Square

Authorize.net