Payment Processor Pricing Comparison Table: Flat Rate vs Interchange Plus vs Custom

Overview

If you are choosing a payment processor for small business or evaluating a larger online payment processing stack, pricing model matters as much as the headline rate. Two providers can both advertise competitive credit card processing, yet produce very different total costs once you add gateway fees, chargebacks, refunds, PCI tools, recurring billing, and cross-border acceptance.

At a high level, most merchant pricing falls into three buckets:

• Flat rate: one published percentage, sometimes plus a fixed fee per transaction. This is common with all-in-one payment gateway products that package underwriting, checkout, and basic fraud tools together.
• Interchange plus: the processor passes through card-network interchange and assessment costs, then adds its own markup. This is often the clearest structure for merchants that want pricing transparency.
• Custom or enterprise pricing: negotiated pricing based on volume, geography, payment methods, fraud profile, support needs, or platform complexity.

Payment processing itself still follows the same basic path regardless of pricing model: a transaction is authorized, authenticated where required, and then settled. Source material from Ramp describes card payments as moving through authorization, authentication, and settlement, with authorization happening in seconds and final settlement taking longer. That operating reality matters because some processors price only the authorization layer while charging separately for settlement-related reporting, disputes, or payout acceleration.

Here is a practical pricing comparison table you can use as a starting matrix.

The safest evergreen interpretation is simple: there is no universally best payment processor pricing model. The best model depends on transaction mix, average order value, channel mix, risk, refund rate, and how much infrastructure you need around the core payment API or checkout flow.

How to compare options

The right comparison method is to model total effective cost, not just the advertised card rate. Merchants often spend too much time on the front-page percentage and too little time on the surrounding fees that show up after launch.

Use this checklist when building your own payment processing pricing table:

1. Map your payment mix. Split volume by card-present, ecommerce, wallet payments, ACH processing for businesses, subscriptions, and international sales. A processor that is strong for domestic card payments may be weak for ACH or multi currency checkout.
2. Estimate average ticket size. Fixed per-transaction fees matter more on low-ticket businesses. Percentage-based fees matter more on high-ticket businesses.
3. Separate domestic and cross-border volume. International payment gateway costs often include currency conversion, foreign card surcharges, and local method fees.
4. Include failure and risk costs. Chargeback prevention tools, 3D Secure 2, manual review, and fraud scoring may be bundled or billed separately.
5. Review settlement and reconciliation. Slow payouts and weak reporting can create hidden finance costs even when rates look attractive.
6. Check compliance scope. PCI DSS compliance support, tokenization payments, hosted fields, and vaulting can reduce operational burden, but some providers charge for advanced features.

A simple way to compare is to ask every provider for the same quote template:

• Domestic consumer card pricing
• Business and rewards card pricing treatment
• ACH pricing if relevant
• Digital wallet pricing and acceptance support
• Recurring billing or account updater costs
• Chargeback and dispute fees
• Refund fee policy
• Monthly platform or gateway fees
• PCI or compliance fees
• Cross-border and currency conversion markups
• Contract term, early termination, and reserve terms

This standardization matters because modern processors package more than credit card processing. PayPal highlights broad acceptance options including cards, PayPal, Venmo, invoicing, POS, and installment options. Stripe positions its platform around payments plus billing, fraud tools, issuing, and global acceptance. That means pricing comparisons should reflect the whole commercial stack, not just card acceptance in isolation.

When providers do not publish enough detail, use a three-layer framework:

• Processing fees: percentage, per-transaction, and pass-through network costs
• Platform fees: gateway, recurring billing, reporting, terminal, invoicing, API, or advanced support
• Risk and operations fees: fraud tools, dispute handling, reserves, payout acceleration, and reconciliation tooling

If you want a shortcut, compare quotes under three monthly volume scenarios: low, medium, and growth case. That prevents choosing a flat rate model that looks fine today but becomes expensive when your approval rate improves and volume scales.

Feature-by-feature breakdown

Pricing model is only one column in a useful merchant services pricing comparison. The better question is what each model tends to include, exclude, or hide.

1. Transparency

Flat rate wins on readability. A merchant can usually estimate fees quickly and start taking payments with minimal negotiation. This is especially helpful for a first-time merchant account setup or a business that wants to know how to accept card payments online without learning interchange tables.

Interchange plus pricing wins on auditability. You can usually see what the card networks and issuing banks take versus what the processor keeps. For finance teams and operators, that makes optimization easier.

Custom pricing can be transparent or opaque depending on the contract. Ask for line-item definitions, especially if the provider also bundles a payment gateway, fraud stack, orchestration, or recurring billing suite.

2. Integration complexity

Flat-rate providers often make onboarding easier with hosted checkout, prebuilt plugins, and a simpler payment API. That can reduce launch time and PCI exposure. For merchants without in-house engineering, that simplicity has real value.

Interchange-plus providers vary widely. Some offer excellent developer tooling; others assume a more traditional merchant account and gateway setup.

Custom enterprise deals usually make sense when integration depth matters: marketplaces, subscriptions, sophisticated routing, or international expansion. If you need guidance on technical evaluation, see Payment Gateway APIs Compared: Authentication, Webhooks, SDKs, and Documentation Quality.

3. Fraud and chargebacks

Chargeback prevention is part of pricing even when it is not labeled that way. Some processors include basic fraud screening. Others charge separately for rule engines, machine learning models, review queues, or dispute automation.

For ecommerce and subscription businesses, compare:

• 3D Secure 2 support
• AVS and CVV checks
• Tokenization payments and vaulting
• Chargeback management software integrations
• Friendly fraud workflows
• Evidence submission tools

A cheaper processing rate can be offset by higher fraud losses or weak dispute tooling. For a broader framework, see Payment Orchestration Platforms: When to Use One and How to Evaluate Vendors.

4. Recurring billing and subscriptions

If you bill customers repeatedly, compare more than the base card rate. Recurring billing may involve dunning, account updater services, proration logic, failed payment recovery, and subscription analytics. Some processors include only basic stored-card charging, while others charge separately for full billing products.

Subscription-heavy merchants should review Recurring Billing Systems Compared: Subscriptions, Dunning, and Failed Payment Recovery before deciding whether an attractive core rate actually supports the business model.

5. Cross-border and alternative methods

Processors with strong domestic pricing are not always the best fit for international payment gateway needs. PayPal emphasizes broad market and currency coverage, while Stripe emphasizes support for many currencies and payment methods. Those capabilities matter if you sell across borders, but they often carry separate pricing layers for currency conversion, local methods, and foreign-issued cards.

If global acceptance matters, compare:

• Supported settlement currencies
• Local acquiring availability
• Alternative payment methods and wallet payments integration
• FX spread or conversion markup
• Cross-border dispute handling

For a country-and-method view, see International Payment Gateway Comparison: Currencies, Methods, Fees, and Coverage.

6. Settlement and cash flow

Settlement timing is not usually a line item in ads, but it affects working capital. Ramp notes that card authorization is near-instant while final settlement can take several days, and ACH can take one to three business days. Providers may also differ on payout schedules, weekend timing, reserve holds, and risk reviews. A slightly higher rate may be justified if it improves cash flow predictability.

Use Settlement Times by Payment Method: Cards, ACH, Wallets, and International Transfers to compare the operational impact.

7. Merchant account structure

Some flat-rate providers abstract the merchant account experience into one platform. Traditional interchange-plus setups may separate the merchant account, payment gateway, and processor. Neither is automatically better. The right fit depends on whether you want one vendor or more control over each layer. For a clean explanation, see Merchant Account vs Payment Gateway vs Payment Processor: What Businesses Actually Need.

Best fit by scenario

You do not need the perfect processor for every business type. You need a pricing model that matches your economics and operating constraints.

Flat rate is usually the best fit when:

• You are launching quickly and want minimal setup friction
• Your monthly volume is still modest or unpredictable
• You value one contract and one dashboard over pricing granularity
• You need a bundled payment gateway for ecommerce, payment links, or simple invoicing

This model often works well for new online sellers, smaller brands, creators, service businesses, and merchants testing product-market fit.

Interchange plus is usually the best fit when:

• Your volume is stable enough to justify statement review
• You want pricing transparency and room to negotiate markup
• Your average order value makes blended flat rates expensive
• You have enough operations maturity to manage gateway, fraud, and reporting decisions deliberately

This model often suits established ecommerce, B2B payments, and merchants with a meaningful share of lower-cost debit or regulated card traffic.

Custom pricing is usually the best fit when:

• You process high volume or operate in multiple regions
• You need multi currency checkout, alternative methods, or local acquiring
• You run subscriptions, marketplaces, or platform payments
• You need tailored fraud models, SLA commitments, or dedicated account support

This model is common for scaling software platforms, international sellers, and businesses with specialized payment flows.

If you are still narrowing the field, Best Payment Processors for Small Business: Features, Fees, and Fit by Use Case and How to Accept Card Payments Online: Requirements, Providers, and Setup Steps can help you define the shortlist before requesting quotes.

A practical decision rule is:

• Choose flat rate if simplicity is worth more than optimization.
• Choose interchange plus if visibility and cost control are worth a little more admin.
• Choose custom if payments are strategic enough that negotiation, routing, and platform design meaningfully affect margin.

When to revisit

This is not a one-time decision. Revisit your payment processing pricing table whenever your business changes or the market does. The best time to review is before fees become a margin problem.

Update your comparison when:

• Your monthly volume changes materially
• Your average order value rises or falls
• You add subscriptions, invoicing, ACH, or in-person acceptance
• You begin selling internationally
• Your chargeback rate increases
• Your provider adds new platform fees or changes packaging
• A new payment gateway or orchestration option enters your market

Run this action plan every six to twelve months:

1. Export the last three months of payment statements.
2. Calculate your true effective rate including disputes, refunds, and software add-ons.
3. Break volume down by card type, geography, and payment method.
4. List the tools you actually use: recurring billing, wallet acceptance, fraud controls, invoicing, POS, reporting.
5. Request side-by-side quotes from at least two alternative providers using the same assumptions.
6. Check contract terms, reserves, payout timing, and migration complexity before comparing headline rates.

That review habit is where most savings come from. Not from chasing the lowest published number, but from matching pricing model to business model as your checkout, risk profile, and payment mix evolve.

The final takeaway is straightforward: a good payment processor pricing comparison should function like a living decision tool. Keep one table, update it when pricing or features shift, and judge every offer on total cost, operational fit, and room to scale.