How to Evaluate a Payment Processor: The Operator's Checklist

Choosing a payment processor is one of the most consequential infrastructure decisions a growing business makes. Get it wrong, and you're locked into years of excess costs, brittle integrations, and limited flexibility. Here's how operators who've been through it approach the evaluation.

Start With Your Actual Requirements, Not a Feature Matrix

Most processor evaluations start backwards — comparing feature lists before understanding what the business actually needs. Before you open a single vendor website, document your requirements:

Volume and velocity: Monthly transaction count, average ticket size, peak processing periods. A business processing $500K/month has fundamentally different options than one processing $50M/month.

Payment methods: Card-present, card-not-present, ACH, international cards, local payment methods, recurring billing, marketplace payouts. Every payment method you need narrows your options.

Integration depth: Are you embedding payments into a platform (PayFac model), or do you need a standalone processing relationship? This single question changes the entire evaluation.

Compliance environment: PCI scope, industry-specific regulations (healthcare, cannabis, high-risk), and data residency requirements all constrain your choices.

Decoding Pricing: Interchange-Plus vs. Flat-Rate vs. Tiered

Payment processing pricing is deliberately opaque. Understanding the three dominant models is essential:

Interchange-plus: The processor passes through the actual interchange rate (set by Visa/Mastercard) and adds a fixed markup. This is the most transparent model and typically the cheapest at volume. You'll see statements showing the actual interchange category for each transaction.

Flat-rate: A single blended rate for all transactions (e.g., 2.9% + 30¢). Simple, predictable, but you're overpaying on debit transactions and low-risk card types. Best for businesses under $500K/year where simplicity matters more than optimization.

Tiered: Transactions are bucketed into "qualified," "mid-qualified," and "non-qualified" tiers with different rates. This model is designed to benefit the processor, not you — the processor decides which tier each transaction falls into. Avoid this model.

Beyond the headline rate, watch for: gateway fees, PCI compliance fees, batch settlement fees, chargeback fees, monthly minimums, statement fees, and early termination fees. These ancillary charges can add 20-40 basis points to your effective rate.

Integration Quality: The Cost Nobody Calculates

A processor with a 10-basis-point pricing advantage but a poorly documented API will cost you more in engineering time than you'll ever save on processing fees. Evaluate integration quality rigorously:

API design: Is the API RESTful with clear documentation? Are SDKs maintained for your tech stack? Is the sandbox environment actually functional (many aren't)?

Webhook reliability: How does the processor handle webhook delivery failures? Is there retry logic? Can you query for missed events? Unreliable webhooks create silent failures that corrupt your transaction records.

Token vault portability: If you need to switch processors later, can you migrate your stored card tokens? Token portability is rarely discussed during sales but becomes critical during migration. Some processors use network tokens (portable), others use proprietary vaults (locked in).

Developer support: When your integration breaks at 2am during a peak sales event, is there a human engineer you can reach? Test this before you sign.

Contract Terms That Matter

Processor contracts are designed by the processor's lawyers, not yours. Pay attention to:

Term length and auto-renewal: Many contracts auto-renew for 1-3 years with a 30-60 day cancellation window. Miss the window and you're locked in.

Pricing guarantees: Does the processor guarantee your interchange-plus markup for the contract term, or can they adjust rates with 30 days notice? Get rate locks in writing.

Reserve requirements: Some processors hold a percentage of your processing volume in reserve, especially for new merchants or industries they consider higher-risk. Understand the reserve percentage, hold period, and release conditions.

Exclusivity clauses: Some contracts prohibit you from processing with other providers. This limits your ability to optimize by routing different transaction types to different processors.

When to Bring in an Advisor

If you're processing over $1M annually, the economics justify bringing in a payments advisor. A good advisor brings three things you don't have: a current view of the processor landscape (it changes faster than you think), benchmarking data to know whether a pricing proposal is competitive, and negotiation leverage from representing multiple merchants.

The evaluation process should include a formal RFP to at least 3-4 processors, with standardized questions that make proposals comparable. An advisor manages this process and interprets the responses — identifying the hidden costs and contract terms that look standard but aren't.