How to Compare Two Merchant Processing Proposals Line by Line

By Raied Muheisen | Merchant services and Clover POS experience | Last reviewed June 18, 2026

Two merchant-processing proposals cannot be compared responsibly by looking at one percentage or monthly payment. Each proposal must be rebuilt into the same categories: card-network costs, processor markup, transaction charges, monthly account fees, gateway and software, equipment, implementation, and contract obligations.

The worksheet below is designed to be copied into a spreadsheet or printed. Enter only terms shown in the proposal or confirmed in writing.

Merchant proposal comparison worksheet

Comparison line	Current provider	Proposal A	Proposal B	Evidence or question
Pricing model				Interchange-plus, flat-rate, subscription, tiered, or hybrid?
Processor markup				Percentage and per-item components?
Card-present pricing				Which devices and transaction conditions qualify?
Keyed/online pricing				Gateway, token, and transaction charges?
Monthly account fees				Statement, minimum, PCI, account, support?
Chargebacks/refunds				Fees, process, and refund treatment?
POS software and apps				Plan, users, locations, integrations, add-ons?
Equipment				Purchase, lease, placement, financing, return?
Installation/training				Scope, owner, timing, and extra charges?
Contract/cancellation				Term, renewal, notice, damages, data export?

Start with the current statement

Use several representative months rather than one unusually high or low period. Record sales volume, transaction count, refunds, chargebacks, card-present and card-not-present mix, total fees, equipment, software, and other charges. Our statement guide explains the categories.

Separate wholesale cost from provider pricing

In an interchange-plus proposal, identify the stated markup above card-network and assessment costs. In a flat-rate proposal, determine which transaction types receive the stated rate and what falls outside it. In tiered pricing, request a clear explanation of qualification rules. Read the interchange-plus versus flat-rate guide before deciding which presentation is easier to evaluate.

Model transaction charges

A per-transaction charge affects a high-transaction, low-ticket business differently from a lower-transaction, high-ticket business. Use the business’s actual transaction count and mix. Include authorization, batch, gateway, token, AVS, keyed, ecommerce, refund, and other relevant line items rather than applying one rate to total volume.

Expose software and equipment

A proposal may shift costs out of processing and into software, apps, equipment, financing, installation, support, or connectivity. List each separately. Confirm device ownership, warranty, replacement, return obligations, and whether cancellation of processing also cancels the other agreements. See POS equipment lease versus purchase.

Compare operational fit

Price does not repair a poor workflow. Ask each provider to demonstrate the exact menu, inventory, online ordering, invoicing, recurring billing, employee, reporting, accounting, and multi-location tasks the business uses. Record which features are native and which depend on a third party.

Normalize the contract

• Initial term and automatic renewal.
• Cancellation notice and delivery method.
• Early-termination or liquidated-damages language.
• Equipment lease or financing duration.
• Software and gateway cancellation.
• Rate-change and pass-through provisions.
• Data access and export after termination.
• Personal guaranty, reserve, or security-interest language where present.

Decision rule

Do not choose the lowest modeled month automatically. Choose the proposal with the clearest complete cost, acceptable contract, workable implementation, reliable support ownership, and operational fit. Keep assumptions visible so the comparison can be updated when the business mix changes.

After choosing, follow the onboarding checklist or the processor-switching plan.

General educational worksheet only. Actual costs and contract obligations depend on the written agreements and transaction mix.

Run more than one comparison scenario

A useful worksheet models the current transaction mix, a slower month, a higher-volume month, and a plausible change in card-not-present share. It should also show the effect of transaction count independently from sales volume. This prevents a proposal from looking universally favorable because it was tested against only one month.

Label every assumption and keep one column for items the vendor has not confirmed. An unanswered contract, equipment, or integration question is not zero cost; it is an unresolved implementation risk that should remain visible in the decision.

Build a normalized monthly cost model

Translate each proposal into the same rows and use the business’s actual transaction mix. A useful model contains variables rather than one vendor’s preferred example.

Model component	Input	Calculation approach
Sales volume	Representative card volume by channel	Apply only the pricing that qualifies for each channel
Transaction count	Count by in-person, keyed, online, and other types	Multiply by applicable per-item charges
Processor markup	Percentage and per-item markup	Separate from underlying network costs where disclosed
Fixed account fees	Monthly, annual, minimum, PCI, gateway, support	Convert annual items to the same comparison period
Software and apps	Registers, locations, users, integrations, add-ons	Use complete required configuration
Equipment	Purchase, lease, rental, installation, shipping	Show upfront cash and total contractual obligation separately

Run four required scenarios

1. Current mix: representative recent volume, transactions, channels, and services.
2. Slow month: lower volume with the same fixed monthly costs.
3. Growth month: higher volume and transaction count without assuming identical card mix.
4. Channel shift: more card-not-present, online, delivery, invoice, or recurring activity.

These scenarios expose proposals that rely on one unusually favorable assumption. Do not invent growth; use a clearly labeled planning scenario and keep it separate from observed history.

Score contract and operational fit

Criterion	Weight	Proposal A score	Proposal B score	Evidence
Complete modeled cost
Pricing transparency
Workflow demonstration
Implementation ownership
Support and replacement
Contract flexibility
Data access and export

Choose weights before seeing final vendor scores. Require a document, demonstration, or written answer in the evidence column. A confident sales answer without supporting terms should remain unresolved.

Test the exact workflow

Give both vendors the same demonstration script. A restaurant might require modifiers, kitchen routing, split checks, tips, handhelds, online orders, refunds, and end-of-day reporting. A retailer might require variants, barcodes, partial receiving, returns, inventory adjustments, gift cards, staff permissions, and multi-location transfers.

Record which functions are native, which require an app, which require a higher plan, and which the vendor cannot demonstrate. Include the vendor and support owner for every third-party component.

Proposal red flags

• The full merchant, software, equipment, or lease agreement is unavailable before signature.
• A quoted rate has no definition of qualifying transactions.
• Network costs, processor markup, and other services are combined without explanation.
• Equipment is called free without ownership and return terms.
• A savings comparison uses a different transaction mix from the current statement.
• The provider will not model refunds, chargebacks, keyed, online, or international activity.
• Cancellation of processing is presented as canceling every related agreement.
• Implementation tasks have no named owner or acceptance test.

Create a one-page decision memo

Before signing, summarize the selected proposal, alternatives considered, statements used, modeled scenarios, pricing assumptions, unresolved risks, equipment ownership, software dependencies, implementation owners, contract term, cancellation method, and reason for the decision. Attach the proposal and agreements. This memo makes later billing or service changes easier to evaluate.

Annual comparison review

Repeat the normalized comparison after a material change in volume, channel mix, locations, software, or equipment. Do not assume a provider is now expensive because total fees rose; determine whether the cause was more sales, more transactions, changed card mix, new services, network changes, or provider pricing.

Build an evidence file before you choose

A clean comparison should be reproducible by someone who did not attend the sales calls. Save the dated proposal, program guide, application, equipment order, software order, sample statement, pricing schedule, and written answers to material questions in one folder. If a promise affects the decision, it belongs in writing.

Claim to verify	Evidence to request	Why it matters
“No contract”	Termination, renewal, and notice sections of the actual agreement	A month-to-month service can still have equipment or software obligations
“Free equipment”	Ownership, return, replacement, and damage terms	The device may be conditional, loaned, or recovered through other charges
“Next-day funding”	Funding schedule, cutoff time, excluded days, and hold provisions	The headline does not explain weekends, holidays, reserves, or exceptions
“Rate guarantee”	Exact fees covered, exclusions, and amendment rights	Interchange and network costs may change even when a provider markup is fixed
“Includes support”	Support hours, escalation path, replacement process, and response commitments	Availability matters most when payments stop during operating hours

Separate known cost from conditional exposure

Put every line item into one of three buckets: predictable recurring cost, usage-dependent cost, or conditional exposure. Monthly software belongs in the first bucket. Transaction and authorization charges belong in the second. Early termination, chargeback, retrieval, PCI noncompliance, equipment return, and reserve exposure belong in the third. This prevents an attractive monthly estimate from hiding a contract risk that only appears later.

Questions for the final reference call

If the provider offers a customer reference, ask operational questions instead of “Are you happy?” Useful prompts include: How long did implementation take? Which promised feature required extra work? How quickly was the most serious support issue resolved? Did deposits and statements match the proposal? What would you insist on documenting before signing?

Approval rule

Choose only after the decision-maker has reviewed the normalized cost model, workflow fit, implementation plan, contract exposure, and evidence file. A salesperson’s revised quote should trigger an updated comparison—not an immediate signature. Record the selected proposal, the reasons it won, the risks accepted, and the date for a post-launch review.