The Annual Processor Scorecard: A Survey Template for Rating Fees, Support, and Uptime — and Deciding When to Switch 

A payment processor evaluation scorecard should rate six areas every year: effective cost, support responsiveness, funding reliability, dispute tooling, uptime, and contract flexibility. Score each from 1 to 5, weight the categories around your business model, and use the total to decide whether to stay, renegotiate, collect comparison quotes, or start switching processors.

A processor can be inexpensive and still be a poor vendor. Slow support, unreliable deposits, weak dispute tools, checkout interruptions, or restrictive contract terms can easily outweigh a modest difference in processing rates.

That is why an annual merchant services review should not begin with, “Can someone beat our rate?” It should begin with, “How well did our current provider perform during the last 12 months?”

The payment processor evaluation scorecard below turns that question into a repeatable annual review. It uses records you probably already have—processing statements, support tickets, deposit history, dispute records, outage logs, and your current agreement—so a small or midsize merchant can complete the core review without turning it into a weeks-long project.

Payment Processor Evaluation Scorecard at a Glance

Start with six dimensions and a 100-point weighted score.

Dimension	Default Weight	What You Are Measuring
Effective cost	25%	What accepting payments actually costs after relevant processor and platform charges
Support responsiveness	20%	How quickly a knowledgeable person takes ownership of real problems
Funding reliability	20%	Whether deposits arrive on the expected schedule and reconcile correctly
Dispute tooling	10%	How easily staff can receive, investigate, answer, and track disputes
Uptime and payment reliability	15%	Whether customers can pay when your business needs the system
Contract flexibility	10%	Renewal, cancellation, pricing-change, equipment, portability, and switching terms
Total	100%

Rate each category from 1 to 5.

Then calculate:

Weighted points = category weight × rating ÷ 5

For example, a 4/5 in a category weighted at 20% contributes 16 points to the final score.

What score means you should stay, renegotiate, or switch?

Final Score	Recommended Action
85–100	Stay. Fix isolated weaknesses during the normal account review.
75–84	Keep the provider, but negotiate measurable improvements.
65–74	Renegotiate and collect two or three comparison proposals.
55–64	Begin a structured replacement evaluation.
Below 55	Start the switching process now unless documented remediation is already working.

“Start switching” does not mean close the merchant account tomorrow. It means validate a replacement, identify migration dependencies, and prepare an orderly exit before another renewal or operational failure takes the decision out of your hands.

The thresholds are intentionally simple. Your business can also establish red-flag overrides for problems serious enough to justify action regardless of the total score.

Why an Annual Merchant Services Review Should Measure More Than Rates

Merchants often remember the processor relationship through a handful of events: a painful support call, an unexpected fee, one major outage, or a sales representative promising a lower price.

Those experiences matter, but they are not enough to rate your payment processor fairly.

The strongest review combines financial evidence and operational evidence.

A processor’s quoted markup should not be confused with the complete cost of accepting cards. According to Visa’s April 2026 U.S. interchange documentation, interchange reimbursement fees are transfers between financial institutions, while merchants pay a merchant discount to their financial institution that may include multiple processing services. 

That distinction is important when completing a payment processor evaluation scorecard because the cost category should be based on the merchant’s actual total processing expense—not one advertised rate or interchange figure. 

Visa’s current explanation of interchange is useful here. Visa describes interchange reimbursement fees as transfer fees between acquiring and issuing banks and separately explains that merchants negotiate and pay a merchant discount to their financial institution, which may include multiple processing services. That is why a merchant should not treat one advertised percentage or one interchange table as its complete acceptance cost.

Before assigning the cost score, normalize the numbers rather than comparing isolated rates. The methodology in benchmarking merchant processing costs explains how transaction volume, average ticket, card-present versus card-not-present activity, pricing model, transaction fees, and other charges can change the effective cost merchants actually experience.

Your annual review should therefore answer two separate questions:

1. What did accepting payments cost us?
2. How well did the provider perform for that cost?

A cheap processor with repeated outages may be poor value. A slightly more expensive processor with dependable funding, excellent support, and stable payment acceptance may be worth keeping.

Gather the Scorecard Inputs in About One Hour

The processor vendor scorecard template is most useful when it can be repeated consistently. You should not need a forensic audit every year.

For many merchants, the first-pass review can be assembled in roughly an hour.

Evidence	What to Pull	Target Time
Processing statements	Three representative months	10–15 min
Support history	Tickets, emails, escalation notes	10 min
Funding records	Settlement reports and bank deposits	10 min
Disputes	Recent cases and portal workflow	5–10 min
Uptime	Outage records, status history, staff notes	5 min
Contract	Agreement, amendments, renewal terms	10–15 min

Step 1: Pull three representative processing statements

Do not select only your busiest month or the month with the lowest fees.

Choose three months that represent normal operating conditions. If your business is highly seasonal, review a longer period or include one normal month, one peak month, and one slow month.

Capture:

• card-processing volume;
• transaction count;
• total processing-related charges;
• processor markup where identifiable;
• per-transaction or authorization charges;
• gateway or platform fees;
• monthly fees;
• PCI-related charges;
• dispute fees;
• annual fees allocated to the review period; and
• material one-time charges.

Then calculate a consistent effective-cost figure.

Effective processing cost = included processing expenses ÷ processed card volume × 100

The most important word is consistent. Use the same cost definition next year so the result can actually reveal whether the account became more or less expensive.

Step 2: Review support tickets instead of relying on memory

Pull support emails, portal cases, call notes, and escalation records from the previous 12 months.

For every material incident, record:

• first response time;
• time to a knowledgeable human;
• time to resolution;
• number of follow-ups required;
• whether the issue was escalated;
• whether ownership was clear; and
• whether the same problem returned.

A processor that answers in three minutes but sends the merchant through four departments should not automatically receive a strong support score.

Step 3: Match settlement records to actual deposits

Review several ordinary weeks plus any known problem periods.

Look for:

• deposits arriving later than the disclosed schedule;
• missing deposits;
• unexpected split funding;
• unexplained reserve deductions;
• unexplained holds;
• amount mismatches; and
• transactions that repeatedly require manual reconciliation.

Do not downgrade the processor for an expected banking holiday or a delay clearly caused by your bank rather than the processor.

Step 4: Review the dispute workflow

Open the processor’s dispute interface rather than relying on what a salesperson says it can do.

Check whether staff can easily identify:

• disputed transaction;
• dispute reason;
• response deadline;
• requested documentation;
• evidence submission status;
• final outcome; and
• historical dispute reporting.

This deserves a place on the payment processor evaluation scorecard because dispute management is time-sensitive operational work. Visa advises merchants to respond swiftly when contacted by their acquirer about a dispute.

Step 5: Reconstruct meaningful payment outages

Use gateway alerts, POS logs, processor status notifications, ecommerce monitoring, and staff reports.

But identify the actual cause.

A checkout failure might come from:

• processor infrastructure;
• gateway infrastructure;
• POS software;
• ecommerce software;
• merchant configuration;
• local internet;
• payment hardware; or
• another integrated provider.

A fair annual merchant services review should not penalize the processor for an outage it did not cause.

Step 6: Read the current contract, not the contract you remember signing

Pull the original agreement plus amendments and later pricing notices.

Review:

• initial term;
• current renewal term;
• cancellation notice requirement;
• early termination charges;
• equipment leases or commitments;
• reserve provisions;
• pricing-change language;
• gateway restrictions;
• exclusivity provisions;
• token or stored-credential portability; and
• obligations that continue after termination.

If nobody in the company can locate the current agreement, fix that before the next review.

How to Score Effective Cost

Cost should normally carry substantial weight, but “cheapest” should not automatically equal 5/5.

Use realized cost, transparency, and competitiveness together.

Effective-cost scoring rubric

5 — Excellent: Actual processing cost is competitive for the business’s volume, channel, ticket size, transaction mix, and service requirements. Fees are transparent and reconcile cleanly.

4 — Good: Overall cost remains competitive, with only minor pricing opportunities or a few low-impact charges worth discussing.

3 — Acceptable: Pricing is workable but there are meaningful savings opportunities, confusing charges, or several items that deserve renegotiation.

2 — Weak: Costs appear materially above reasonable alternatives, pricing has drifted significantly, or statements require repeated investigation.

1 — Poor: Pricing is substantially uncompetitive, repeatedly unexplained, materially different from the agreement, or too opaque for the merchant to determine what it is paying.

Avoid comparing one provider’s interchange-plus markup against another provider’s all-in effective rate. Visa’s explanation of merchant discount and interchange reinforces why these are not interchangeable figures.

How to Score Support Responsiveness

Support is one of the easiest categories to score emotionally, so concrete anchors matter.

Support scoring rubric

5 — Excellent: Serious issues receive a same-day knowledgeable human response, ownership is clear, escalation works, and problems rarely require repeated explanation.

4 — Good: Support is consistently reachable and competent, with occasional escalation friction.

3 — Acceptable: Most issues eventually get resolved, but complex cases sometimes require several calls, emails, or handoffs.

2 — Weak: Response quality or speed regularly creates extra work or leaves payment problems unresolved longer than the business considers reasonable.

1 — Poor: Critical issues routinely go unanswered, support cannot provide clear ownership, or operational problems remain unresolved through multiple contacts.

The phrase “same-day human callback = 5” is useful only as an anchor, not a universal SLA. A business operating overnight may reasonably require a much faster response for a payment outage.

Add a short processor satisfaction survey

Your finance manager may have a very different processor experience from your store manager or ecommerce team.

A short processor satisfaction survey can expose those differences.

Ask staff to rate these statements from 1 to 5:

1. Processor charges are understandable and predictable.
2. Support responds quickly enough for the severity of the issue.
3. Support can solve problems without unnecessary repeat contacts.
4. Deposits arrive when expected.
5. Disputes are easy to investigate and manage.
6. Payment acceptance is dependable during critical business periods.
7. Contract and account terms are understandable.
8. What processor issue caused the most unnecessary work this year?

Keep each question focused on one concept. Common survey mistakes that lead to useless feedback explains why vague, leading, and double-barreled questions make survey results harder to trust.

For teams creating a more formal processor satisfaction survey, the principles in best practices for designing and distributing effective merchant surveys can help keep the questionnaire short, neutral, and tied to a specific decision.

How to Score Funding Reliability

Fast funding has little value if the timing is unpredictable.

Measure what actually happened against the schedule the provider disclosed.

Funding scoring rubric

5 — Excellent: Deposits consistently arrive on the expected schedule and reconcile without recurring exceptions.

4 — Good: Rare exceptions occur, but they are explained quickly and corrected without meaningful disruption.

3 — Acceptable: Several exceptions occur during the year, although the provider generally explains and resolves them.

2 — Weak: Repeated delays, holds, or amount differences create reconciliation work or cash-flow uncertainty.

1 — Poor: Significant unexplained funding interruptions, missing deposits, or recurring holds materially disrupt operations.

Businesses with tight working capital can increase this category’s weight. A two-day delay has a different impact on a cash-intensive restaurant than on a well-capitalized professional-services firm.

How to Score Dispute Tooling

Do not make chargeback win rate the primary measure of processor quality.

The underlying transaction, cardholder claim, network rules, evidence, and deadlines all influence the result.

Instead, evaluate the system the processor gives you.

Dispute tooling deserves its own score because deadlines and workflow quality affect whether a merchant can respond effectively. Visa’s official dispute-resolution guidance tells merchants that when an acquirer contacts them about a dispute, a swift response is the best path toward resolution. 

Visa also advises merchants to keep clear return and cancellation policies, submit transactions promptly, and avoid duplicate processing. A processor should therefore score higher when its portal makes deadlines, evidence requirements, case status, and response actions easy to find.

Dispute-tooling scoring rubric

5 — Excellent: Immediate alerts, visible deadlines, easy evidence upload, clear status tracking, useful reporting, and a searchable case history.

4 — Good: Strong workflow with only a few manual steps or reporting limitations.

3 — Acceptable: Cases can be handled reliably, but staff must use separate systems, email, or manual tracking.

2 — Weak: Notifications, documentation, status tracking, or reporting are difficult enough to create avoidable risk.

1 — Poor: Staff cannot reliably identify deadlines, submit evidence, or understand case status.

Visa’s current merchant information describes disputes as reversals of transaction value and tells merchants that a swift response when contacted by an acquirer is the best path toward resolution.

That makes dispute workflow more than a convenience feature. It affects whether your team can act before a deadline expires.

How to Score Uptime and Payment Reliability

“99.99% uptime” is not enough information by itself.

Ask what service the figure measures, which failures are excluded, whether scheduled maintenance counts, and whether the number covers the actual payment path your business uses.

Uptime scoring rubric

5 — Excellent: No material processor-caused interruptions during the review period, or rare incidents were handled quickly with useful communication.

4 — Good: Minor incidents occurred but did not materially affect customers or revenue.

3 — Acceptable: A limited number of incidents affected operations, but recovery and communication were reasonable.

2 — Weak: Repeated payment interruptions or poor incident communication caused avoidable disruption.

1 — Poor: Serious or recurring processor-related failures materially interfered with payment acceptance.

For ecommerce, measure checkout, gateway, API, tokenization, and recurring-payment availability where those services are provided by the vendor being scored.

For counter retail, focus more heavily on terminal authorization, POS integration, settlement, device replacement, and the processor’s ability to support a store during an incident.

How to Score Contract Flexibility

Merchants often ignore contract flexibility when the relationship is going well.

That changes quickly when they want to leave.

Contract-flexibility scoring rubric

5 — Excellent: Contract terms are clear, renewal is manageable, pricing changes are transparent, and switching does not face major artificial barriers.

4 — Good: A few restrictions exist, but the merchant retains reasonable flexibility.

3 — Acceptable: Some notice, equipment, term, or portability restrictions create work but remain manageable.

2 — Weak: Renewal structure, cancellation charges, hardware commitments, or portability issues create meaningful lock-in.

1 — Poor: The merchant faces unusually restrictive, expensive, confusing, or operationally difficult exit conditions.

The goal is not to reward only month-to-month agreements. A multi-year contract can still receive a reasonable score when its obligations are clear, pricing is stable, and the termination structure is commercially manageable.

Weight the Payment Processor Evaluation Scorecard by Business Type

The same six dimensions can work across industries, but their weights should not be identical.

Suggested weighting

Dimension	General Default	Ecommerce	Counter Retail
Effective cost	25%	20%	25%
Support responsiveness	20%	15%	20%
Funding reliability	20%	15%	20%
Dispute tooling	10%	15%	10%
Uptime/reliability	15%	25%	20%
Contract flexibility	10%	10%	5%
Total	100%	100%	100%

Why ecommerce puts more weight on uptime

A material gateway or API failure can effectively close an ecommerce checkout even while the rest of the website remains online.

Ecommerce merchants may also depend more heavily on recurring credentials, fraud tools, tokenization, and card-not-present dispute workflows. That makes uptime and dispute tooling more important to the overall score.

Why counter retail puts more weight on support and funding

Physical businesses depend heavily on terminals, POS integrations, batch settlement, device replacement, and frontline troubleshooting.

A store can also feel funding delays immediately when large card settlements support inventory, payroll, or other short-cycle operating expenses.

The exact weighting is less important than one rule:

Set the weights before you score the processor.

Changing weights after seeing the results makes it too easy to engineer the answer you already wanted.

A Worked Payment Processor Evaluation Scorecard

Consider a counter retailer completing its annual review.

Dimension	Weight	Rating	Weighted Score
Effective cost	25%	3	15
Support responsiveness	20%	5	20
Funding reliability	20%	4	16
Dispute tooling	10%	3	6
Uptime	20%	5	20
Contract flexibility	5%	2	2
Total	100%		79/100

The processor scores 79.

The business should not automatically switch.

The score says something more useful: daily operations are strong, but pricing and contract flexibility deserve attention.

Instead of creating migration risk to solve a vague dissatisfaction problem, the merchant can negotiate the two weaknesses directly.

That is the main purpose of a processor vendor scorecard template: diagnose the relationship before choosing the remedy.

When to Switch Payment Processors: Use Thresholds Plus Red Flags

Businesses often ask for one number that determines when to switch payment processors.

The final score is helpful, but it should not be the only decision rule.

Score 85–100: Stay

The processor is performing strongly across the categories that matter to the business.

Record the baseline and fix any isolated low-scoring category. A strong score this year becomes valuable comparison data next year.

Score 75–84: Stay, but renegotiate

Identify the two lowest scores and ask for specific changes.

That could mean:

• lower or simplified pricing;
• a named escalation contact;
• improved reporting;
• clearer funding communication;
• better dispute access; or
• modified contract language.

Set a date to check whether the promised changes actually occurred.

Score 65–74: Get comparison quotes

At this point, the incumbent should have to earn the renewal.

Collect two or three credible alternatives and run each through the same payment processor evaluation scorecard.

Do not allow the incumbent to be judged on 12 months of real performance while prospective providers are judged on sales promises.

Score 55–64: Begin structured replacement planning

Multiple important weaknesses now exist.

Map the dependencies involved in moving:

1. merchant account;
2. payment gateway;
3. POS hardware;
4. ecommerce integration;
5. stored credentials;
6. recurring billing;
7. bank funding;
8. dispute access;
9. reporting; and
10. contract-notice requirements.

A score in this range answers the question of when to switch payment processors, but it does not mean terminating the current account before the replacement is ready.

Below 55: Start the exit process

A provider below 55 is failing enough weighted categories that continuing without testing replacements is difficult to justify.

Treat the change as an operational project, not an emotional cancellation.

Validate the replacement first. Then execute the migration under a controlled plan.

Add Red-Flag Overrides

A weighted average can hide a serious problem.

Create an automatic management review when there is:

• repeated unexplained funding suspension;
• recurring material processor-caused downtime;
• inability to receive or act on dispute notices;
• unexplained material pricing changes;
• serious unresolved security concerns;
• a major contract issue that was not disclosed clearly; or
• a critical operational problem that remains unresolved after reasonable escalation.

A red flag does not prove that a processor acted improperly. It simply means the issue is important enough that a good average score should not bury it.

Run the Same Scorecard Against Prospective Providers

One of the biggest problems with processor comparisons is the evidence imbalance.

You know everything that went wrong with your current processor.

You know only what the new salesperson chooses to tell you.

The solution is to run the same processor vendor scorecard template against every candidate—but score evidence, not promises.

Prospect evidence rubric

5: The claim is clearly supported by written pricing, contractual language, service documentation, demonstrations, or other verifiable evidence.

4: Strong evidence exists, although actual live performance cannot yet be confirmed.

3: The claim appears reasonable but remains only partly documented.

2: The salesperson provides broad assurances with limited evidence.

1: Documentation conflicts with the claim, important information is unavailable, or the provider will not answer clearly.

Then score the same six dimensions.

Ask for evidence of cost

Request the complete pricing schedule rather than only the headline rate.

Ask about:

• processor markup;
• transaction fees;
• monthly fees;
• gateway fees;
• dispute charges;
• PCI-related charges;
• annual fees;
• minimums;
• equipment costs; and
• pricing-change provisions.

Test support before signing

Ask a realistic question:

“If checkout stops working at 8:30 p.m. on our busiest Saturday, who owns the incident?”

Then find out:

• who answers;
• whether technical escalation is available;
• what hours apply;
• how critical incidents are prioritized; and
• whether the support commitment exists in writing.

Verify funding terms

Get the expected funding schedule in writing.

Ask how:

• weekends;
• holidays;
• cutoffs;
• reserves;
• risk reviews; and
• funding exceptions

can affect that schedule.

Demand a dispute demonstration

Have the provider show a real or realistic dispute workflow.

You should see how the system presents deadlines, evidence requests, case status, and reporting before giving the provider a high score.

Validate uptime claims

Ask for:

• historical status information;
• incident communication practices;
• maintenance policy;
• service-level commitments where applicable; and
• important infrastructure dependencies.

Read the contract

Do not score contract flexibility based on “there’s no long-term commitment” said during a call.

Review the agreement you will actually sign.

Add a PCI and Third-Party Oversight Check to the Annual Review

Security does not necessarily need to become a seventh weighted score. For most merchants, a separate annual pass/fail review works better.

PCI SSC says merchants that outsource payment processing still retain responsibilities related to the third parties involved. Its current guidance specifically describes maintaining appropriate agreements, understanding shared responsibilities, and monitoring applicable third-party compliance status at least annually.

That makes the annual merchant services review an appropriate time to confirm:

• which processor, gateway, or service-provider functions affect your cardholder-data environment;
• which PCI responsibilities belong to you;
• which responsibilities the provider performs;
• whether relevant compliance evidence remains current; and
• whether the services you actually use are covered by the provider’s evidence.

Do not assume that a generic “PCI compliant” statement answers all of those questions.

Use Staff Feedback Without Letting Anecdotes Control the Score

An internal processor satisfaction survey adds useful context, particularly when several departments interact with the processor differently.

Finance may report perfect deposits while the ecommerce team reports repeated gateway incidents. Frontline staff may struggle with terminal support that management never sees.

Use comments to investigate patterns rather than allowing one dramatic response to decide the score.

If staff submit open-ended feedback such as “support takes too long,” “deposits are difficult to reconcile,” and “nobody owns escalations,” group those comments consistently. Analyzing open-ended survey responses with simple coding and themes provides a straightforward way to convert free-text comments into recurring categories without pretending qualitative feedback is a precise statistic.

Build the Annual Review Into the Calendar Before Renewal

A scorecard that nobody runs is useless.

The calendar trigger should be based on your actual agreement, not January 1 by default.

Use this annual workflow

1. Identify the earliest renewal or cancellation-notice deadline in the agreement.
2. Work backward far enough to review performance and obtain alternatives.
3. Schedule evidence collection.
4. Run the processor satisfaction survey if multiple teams use the service.
5. Complete the six category scores.
6. Discuss any red flags separately.
7. Send improvement requests to the incumbent.
8. Collect comparison proposals if the score calls for them.
9. Record the final decision.
10. Schedule next year’s annual merchant services review immediately.

Starting roughly 90–120 days before an important notice or renewal deadline is a useful planning window for many merchants because it leaves room for review, negotiation, quoting, and technical due diligence.

It is not a universal cancellation period. Your agreement determines the actual deadline.

Save the evidence each year

Keep one annual folder containing:

• completed scorecard;
• category weights;
• processing statements;
• support history;
• funding exceptions;
• material dispute observations;
• outage records;
• employee feedback;
• contract version;
• competing proposals;
• negotiated changes; and
• final decision.

The second annual review becomes easier than the first. By year three, you can see whether the relationship is improving, stable, or deteriorating.

What the Scorecard Can—and Cannot—Tell You

A good scorecard creates discipline. It does not create certainty.

It can tell you:

• which areas of the relationship are weak;
• whether performance changed year over year;
• what should be renegotiated;
• whether alternatives deserve serious consideration; and
• what evidence should be requested from a new provider.

It cannot tell you automatically:

• whether another processor will perform better after implementation;
• what every business should weight most heavily;
• whether one outage was contractually excusable;
• whether every fee is unreasonable; or
• whether immediate termination is legally or commercially appropriate.

The payment processor evaluation scorecard should produce a better decision, not replace management judgment.

Real-World Example: Cheap Pricing Can Still Produce a Bad Score

Consider a hypothetical ecommerce merchant that is satisfied with its processor’s rates.

Its annual scores are:

Dimension	Ecommerce Weight	Rating	Points
Effective cost	20%	4	16
Support	15%	2	6
Funding	15%	4	12
Dispute tooling	15%	2	6
Uptime	25%	2	10
Contract flexibility	10%	3	6
Total	100%		56/100

The merchant originally believed the processor was performing well because pricing remained competitive.

The scorecard exposes a different problem.

Support, dispute management, and uptime—the categories that matter heavily to an ecommerce business—are consistently weak. Saving a few basis points does not compensate for an unreliable checkout.

The score of 56 does not mean “cancel today.” It means the company should begin evaluating replacement providers now rather than waiting for the next serious outage or renewal.

If You Publish Processor Scorecard Data, Separate Research From Opinion

A company can customize weights when evaluating its own processor.

Publishing statements such as “Processor A is the best processor for merchants” requires much more rigorous evidence.

If Merchant Surveys later collects payment processor evaluation scorecard responses across businesses, the published methodology should explain:

• who was eligible;
• how participants were recruited;
• sample size;
• field dates;
• business types represented;
• question wording;
• score construction;
• weighting;
• missing-data handling;
• subgroup sizes; and
• important limitations.

Turning survey data into a publishable industry report explains why sample size alone does not make an industry ranking representative and why composite-score methodology should be disclosed.

That distinction strengthens E-E-A-T as well as reader trust. A useful internal scorecard and a defensible public provider ranking are not the same research product.

Annual Payment Processor Review Checklist

Use this checklist before closing the review:

• Pull three representative processor statements.
• Calculate effective payment-processing cost consistently.
• Compare current costs with the prior annual review.
• Review material support tickets and escalation outcomes.
• Compare expected funding with actual deposits.
• Inspect the dispute-management workflow.
• Separate processor outages from unrelated technology failures.
• Read the current contract and amendments.
• Confirm renewal and cancellation-notice dates.
• Score all six dimensions from 1 to 5.
• Apply business-specific weights.
• Review red flags separately from the total score.
• Run a short processor satisfaction survey where multiple teams are involved.
• Review applicable third-party PCI responsibilities and evidence.
• Request comparison proposals if the score falls below your threshold.
• Run prospective providers through the same scorecard.
• Document the decision.
• Put next year’s review on the calendar.

Frequently Asked Questions

Make the Payment Processor Evaluation Scorecard an Annual Business Control

A processor should not keep your business simply because another renewal arrived before anyone reviewed the relationship.

Run the payment processor evaluation scorecard once a year using real evidence. Measure effective cost, support responsiveness, funding reliability, dispute tooling, uptime, and contract flexibility. Adjust the weights for the way your business actually accepts payments, and compare the result with the prior year.

If the score is strong, stay with confidence.

If it falls into the middle, negotiate the exact weaknesses instead of making a vague demand for a better rate.

If the score keeps falling—or crosses your replacement threshold—you will know when to switch payment processors before an outage, funding interruption, restrictive renewal, or service failure makes the choice for you.

The purpose of the annual merchant services review is not to create processor churn. It is to replace guesswork with evidence and make your payment provider earn the decision to stay.