To test a processor for one month before you commit, ask the provider in writing whether a limited test is possible and on what terms, log every payment, deposit and problem for the whole month, and at month end price the same payments both ways. This page is a test plan. It does not say that any processor offers a trial, because we do not know any provider’s terms, so each one is a question to put in writing. In the made-up month below, the test costs $224.85 less than the current setup on the same payments, and the same log still fails the deposit rule that was written before day one. Every figure is invented to show the method. None of it is a promise, and none of it is a price from a real processor. You repeat the steps with your own sales.

Step 1: Ask for the test in writing before you move a single sale

A test month starts with questions, not with an application. Put each of these to the provider by email, so the answers have a date, and keep the replies in the same folder as your daily log.

  • Is a limited test possible, and what is the smallest set of sales I can send through, such as one register, one website or one day of the week?
  • How many days does the test run, and what is the exact start and end date in writing?
  • Does anything start on the day I sign the application, such as a notice period, a minimum or a charge, and what does it cost to stop on the last day of the test?
  • Are the fees on test payments the same lines as the full quote I would sign? Please send both in writing, side by side.
  • How many days after a payment do I get the deposit, and on which days do deposits not go out?
  • If a payment is refunded or disputed during the test, which fees come back and which stay?
  • Who answers when something goes wrong, how do I reach them, and how fast do you answer in writing?
  • Does starting the test change anything in my current agreement with my current processor?

Count the questions before you send them. There are eight above. A short answer is an answer, and so is a no. If a provider says a limited test is not possible, you can still ask for the full written quote and price it on your last three months of statements, which is a different method from a test month.

Before the test starts, also write down three things for yourself: which sales go through the test, the start date, and the end date. Write them on the first page of the log, and send only those sales through the test, so the payments on both sides match at month end.

See NPS’s page: “When Does Switching Processors Pay for Itself? A Break-Even Worksheet“.

Step 2: Record these eight things every day

The month is only as good as the log. One line per day, the same eight fields every day, written at the end of the day while the day is still in your head.

  1. The date.
  2. The number of payments.
  3. The dollars processed.
  4. The number of refunds.
  5. The number of disputes received.
  6. The date the written answer says the deposit is due.
  7. The date the deposit actually arrived.
  8. Anything that went wrong or needed support, with the time you asked and the time you were answered.

Keep the log in one place and fill it in every day, including the quiet ones. A quiet day with zero payments still belongs in the log, because it is part of the month you are pricing.

Daily log fields

Eight things to record every day of the test

  • Write the date
  • Count the number of payments
  • Record the dollars processed
  • Count the number of refunds
  • Count the number of disputes received
  • Note the date the deposit was due per the written answer
  • Note the date the deposit actually arrived
  • Log anything that went wrong, with the time you asked and the time you were answered
Fill in the line every day, including quiet days with zero payments, so the whole month is priced.

Here is week 1 of a made-up test, Monday to Sunday. It is invented. The payments and dollars for the week are 177 payments and $7,924.

  • Monday: 21 payments, $905
  • Tuesday: 24 payments, $1,070
  • Wednesday: 19 payments, $860
  • Thursday: 28 payments, $1,262
  • Friday: 31 payments, $1,488
  • Saturday: 33 payments, $1,502
  • Sunday: 21 payments, $837

Add the seven days and you get 177 payments and $7,924, the same as the week 1 line in Step 3. In the made-up log, the Thursday deposit arrived one day after the date in the written answer. That goes in field 8 on the Thursday line and it comes back in Step 5. A second deposit, in week 3, arrived two days after its written date. Those are the two late deposits that Step 5 counts.

At the end of the month, add up your own log and ask whether the provider can send a report of total payments and dollars for the test dates. If it can, compare the report with your own log. If the two do not match, write the difference down and ask in writing for an explanation, and settle that before anything gets priced.

Step 3: Price the same payments both ways at month end

Our arithmetic rounds each payment’s fee to the cent, half up, multiplies by the count of payments, then adds the fixed monthly lines.

Two invented price lists are in play. The current setup is invented: 2.74% + 16 cents per payment and a $14 monthly line. The test quote is invented too: 2.18% + 7 cents per payment and a $29 monthly line. Neither is a price from a real processor and neither is an NPS price. The made-up shop takes three sizes of payment, $22, $58 and $135. A $22 payment costs 76 cents on the invented current setup and 55 cents on the invented test quote. A $58 payment costs $1.75 and $1.33. A $135 payment costs $3.86 and $3.01.

Per-payment fee by ticket size

What each ticket size costs on each invented setup

Payment size Current setup fee Test quote fee
$22 payment 76 cents 55 cents
$58 payment $1.75 $1.33
$135 payment $3.86 $3.01
Saving per payment is 21 cents, 42 cents and 85 cents at each size; a month with more large payments saves more.

The four made-up weeks, each priced both ways on the per-payment lines only:

  • Week 1: 95 payments of $22, 68 of $58 and 14 of $135, which is 177 payments and $7,924. Current setup $245.24, test quote $184.83.
  • Week 2: 92 payments of $22, 70 of $58 and 17 of $135, which is 179 payments and $8,379. Current setup $258.04, test quote $194.87.
  • Week 3: 48 payments of $22, 36 of $58 and 6 of $135, which is 90 payments and $3,954. Current setup $122.64, test quote $92.34.
  • Week 4: 100 payments of $22, 96 of $58 and 29 of $135, which is 225 payments and $11,683. Current setup $355.94, test quote $269.97.

Add the weeks and the made-up month is 671 payments and $31,940. The per-payment lines come to $981.86 on the current setup and $742.01 on the test quote, a gap of $239.85. Now add the monthly lines, $14 on one side and $29 on the other. The current setup totals $995.86 and the test quote totals $771.01. In the made-up month, the test costs $224.85 less on the same payments. That is $239.85 less on the per-payment lines, minus the $15 by which the test quote’s monthly line is higher.

Invented example costs

What the made-up month cost each way

  • Test quote total$771.01Test quote (invented)2.18% + 7 cents per payment, $29 monthly line, 671 payments, $31,940 processed
  • Current setup total$995.86Current setup (invented)2.74% + 16 cents per payment, $14 monthly line, same 671 payments
Every figure is invented to show the method; none is a price from a real processor.

To compare on one scale, divide the total fees by the total dollars processed in the same month. The current setup comes to $3.12 per $100 and the test quote to $2.41 per $100 in the made-up month. You can run the same steps with your own numbers.

Invented setups compared

Current setup vs. test quote on the same payments

Rate per payment
Current setup (invented)2.74% + 16 cents
Test quote (invented)2.18% + 7 cents
Monthly line
Current setup (invented)$14
Test quote (invented)$29
Total for made-up month
Current setup (invented)$995.86
Test quote (invented)$771.01
Cost per $100 processed
Current setup (invented)$3.12 per $100
Test quote (invented)$2.41 per $100

In the made-up month, the test costs $224.85 less on the same payments.

Neither is a price from a real processor and neither is an NPS price.

If a quote is interchange pass-through plus a markup, ask for the test month’s report to show the card cost and the markup on separate lines, so you can see which piece the gap comes from. Ask which card types were in your test month, because business and commercial cards can cost more. Level 2 and Level 3 data can lower interchange, so ask whether any of your test payments carried it.

See NPS’s page: “Merchant Account Costs: What to Add Up Before You Compare Rates“.

Step 4: Check the month for weak spots before you trust the total

Check these four things before you read the total as a verdict.

1. The half-month checkpoint. After weeks 1 and 2 the made-up log shows 356 payments and $16,303. On the per-payment lines the current setup is $503.28 and the test quote is $379.70, a gap of $123.58. Read a checkpoint on the per-payment lines only, and take the monthly line difference off once, at the end. Add both full monthly lines at the checkpoint and the gap looks like $108.58, while the finished month shows $224.85. In this made-up month, doubling the checkpoint gap gives $247.16, close to the finished $239.85 on the per-payment lines, because weeks 1 and 2 were close to the month’s average. Doubling the 356 payments gives 712, though, against 671 in the finished month, because week 3 was slow. If your second half looks different from your first, the doubled figure will miss, so compare your own weeks.

2. A slow week. Week 3 was slow, at 90 payments and $3,954, and it saved $30.30 on the per-payment lines, the smallest of the four weeks. Suppose a month had four weeks shaped like week 3. That is 360 payments and $15,816, a saving of $121.20 on the per-payment lines, and $106.20 once the $15 monthly difference comes off. Compare your own test weeks with your last three months, and write down whether the test month was a normal one.

3. The mix of ticket sizes. In the invented lists the saving per payment is 21 cents on a $22 payment, 42 cents on a $58 payment and 85 cents on a $135 payment. So in these invented lists, a month with more large payments saves more per payment, and a month with more small payments saves less. If your test month had an unusual mix, say so in the log before you decide.

4. Refunds and disputes. The made-up month had 9 refunds and 1 dispute received. We do not price them here, because what a refund or a dispute costs on each side is a question for each processor in writing. Put the counts in the log anyway, so the question has numbers behind it.

See NPS’s page: “How a Slow Month Changes the Cost of a Monthly-Fee Processor“.

Step 5: Write the decision rule before day one

If you write the pass mark after you see the total, the total will pick the mark. Write the rule first and date it. The made-up rule has four parts, and all four must pass. The thresholds are invented.

Five-step test plan

How to run a one-month processor test

  1. Ask for the test in writingPut each question to the provider by email, so the answers have a date, and keep the replies in the same folder as your daily log.
  2. Record eight things every dayOne line per day, the same eight fields every day, written at the end of the day while the day is still in your head.
  3. Price the same payments both ways at month endRound each payment’s fee to the cent, multiply by the count of payments, then add the fixed monthly lines.
  4. Check the month for weak spots before you trust the totalCheck the half-month checkpoint, a slow week, the mix of ticket sizes, and refunds and disputes.
  5. Write the decision rule before day oneWrite the pass mark for cost, deposits, support and records, and require all four.
  1. Cost: the test month comes in at least $50.00 below what the current setup would have charged on the same payments.
  2. Deposits: at most one deposit arrives later than the date in the written answer.
  3. Support: every question is answered within one business day.
  4. Records: if the provider can send a report of total payments and dollars, it matches your own log.

Here is how the made-up month scores. Cost passes, because $224.85 is above $50.00. Deposits fail, because two deposits arrived late, one on the Thursday of week 1 and one in week 3, and the rule allows one. Support fails, because four of the five questions were answered within one business day and the fifth took three business days. Records pass, because the made-up log and the made-up report both show 671 payments and $31,940. Two of four pass, so the rule says not yet. The next step in the made-up case is to ask the processor in writing about the two late deposits and the slow answer, and then decide whether a second, shorter test is worth running.

A fifth question can sit beside the rule: how many payments a month does the test quote need before it costs less? With a monthly line $15 higher than the current setup, brute-force counting in the invented lists gives these answers, one ticket size at a time. At a $22 payment, the test quote is cheaper from 72 payments a month. At a $58 payment, it is cheaper from 36. At a $135 payment, it is cheaper from 18. Find your own average payment, find your own monthly count, and see where you sit against the number for your own ticket size.

Last, write the rule for what happens after a pass. Ask each provider in writing for the full agreement before you sign anything beyond the test, and ask whether the price on the test month is the price on the agreement. If the answers are not in writing, treat the test as proof of nothing.

See NPS’s page: “Cheapest Payment Processing in 2026: What You Really Pay and How to Compare“.

Bottom line

A one-month test is five steps. Ask for the test and its terms in writing. Log eight things every day. Price the same payments on both setups at month end, with each payment’s fee rounded to the cent and the monthly lines added after. Check the half month, the slow week, the ticket mix and the refunds and disputes. Write the pass mark before day one. In the made-up month the test quote cost $771.01 and the current setup $995.86, a gap of $224.85, and the test still did not pass because of two late deposits and one slow answer. Those are invented numbers for the method, not a promise. Your own log decides your own result.

You can also run your own numbers through our savings calculator.

Who wrote this, and where NPS fits

Nationwide Payment Systems (NPS) publishes this guide. We are a payments company based in Fort Lauderdale, Florida, in business since 2001, and we sell merchant accounts and invoicing software, so we are not neutral. We offer interchange pass-through pricing, ACH, a payment gateway and Smart Invoicing, and we also offer flat-rate options. We do not publish a price list. The study we cite was written by our CEO. NPS offers a free statement review. Browse more in our payments guides.

Frequently asked questions

How long should a one-month processor test last?

Run it for one full calendar month of your own sales, so the monthly line, the slow weeks and the busy weeks all show up in the log. A shorter test can still be useful for the daily log, but check it against your own weeks before you trust it. In the made-up example, the two-week checkpoint gap of $123.58 on the per-payment lines doubled to $247.16, close to the finished $239.85, and the finished month showed $224.85 once the monthly lines were added.

Can I test a processor without moving all of my sales?

You can ask whether a limited test is possible and what the smallest set of sales is, and the provider’s written answer settles it. We do not know any processor’s terms and this page makes no claim about them. If you send only part of your sales, write down which sales they are on page 1 of the log, so the payments on both sides match at month end.

What should I log every day of the test?

Log eight things: the date, the number of payments, the dollars processed, the number of refunds, the number of disputes received, the date the deposit was due, the date it arrived, and anything that went wrong with the time you asked and the time you were answered. Fill in the line every day, including quiet days with zero payments, so the whole month is priced.

How do I compare the test month with my current processor?

Price the same payments on both setups. Round each payment’s fee to the cent, multiply by the number of payments, then add the fixed monthly lines. Divide the total fees by the total dollars processed in the same month to compare on one scale. In the made-up month, 671 payments and $31,940 cost $995.86 on the invented current setup and $771.01 on the invented test quote, which is $3.12 and $2.41 per $100.

What decision rule should I write before the test starts?

Write a pass mark for cost, deposits, support and records, and require all four. The made-up rule asked for at least $50.00 below the current setup, at most one late deposit, every question answered within one business day, and a provider report, if one is available, that matches the log. The thresholds are invented. Write your own, date the page, and score the month against it afterward.

Does NPS offer a statement review?

Yes. NPS offers a free statement review.

Does the study say interchange pass-through would cost less in my test month?

The study says so only for the average tickets in its model, not for your test month. NPS’s 2026 pricing study is a cost model built from published rate schedules, not a survey, and it comes from a processor that sells pass-through pricing. In the model, interchange pass-through costs 19% to 31% less than flat rate for online and invoice sales across average tickets of $15 to $2,500, and one example is $50,000 a month in invoices at a $150 average ticket, which keeps about $6,100 a year. Flat rate can still win for very small tickets and for brand-new, very low-volume businesses. Your own log decides your result.