The short answer
Every business pays payment processing fees. The real question is where that cost lands on the invoice.
A business can quietly raise every service rate by several percent so card fees become invisible, or it can keep the base price tied to the actual service and let the client choose the payment method.
For a client paying by ACH bank draft, the second model is cheaper. For a client who wants credit card convenience, float, or rewards points, the fee is visible, capped, and optional.
Hiding the fee does not make it disappear. It simply moves the cost onto everyone, including customers who never use the more expensive payment method.
“Isn’t that just the cost of doing business?”
Yes. Payment processing is a cost of doing business.
So are software, insurance, rent, payroll, licensing, and taxes. I understand why someone would say, “That is your cost of doing business. Why are you passing it to me?”
That is a reasonable question. The problem is that it assumes there is only one honest way to handle the cost. There are actually two:
- Bake it into every rate. Quietly increase the price for every customer, regardless of how they pay.
- Keep the base rate lower and disclose the payment cost. Let customers use ACH at the lowest direct price, or choose a card and pay the associated fee.
Option one is not more generous. It is simply better hidden.
And businesses rarely bake in the exact processing cost. A prudent business adds a buffer because card costs vary by card type, rewards programs, corporate cards, transaction volume, and processor pricing. That means the customer may pay an inflated price every month, even when paying by ACH.
At USTech.Ninja, I would rather show you the choice than quietly make it for you.
The math is not complicated
Here is a simplified example using rounded figures. This is an illustration, not a quote.
Assume the actual monthly service price is $500.
Visible pass-through model
- Pay by ACH bank draft: $500
- Pay by credit card: $500 plus a visible capped fee
- Assume, for illustration, that the capped fee is $6
The ACH customer pays $500 because ACH does not create the same card processing cost.
The card customer pays $506 because they chose the payment rail that creates the additional cost.
Baked-in model
Now assume the provider raises the service price to $525 so credit card processing is invisible.
Every customer pays $525:
- ACH customer: $525
- Credit card customer: $525
- Cash customer: $525
- Every month, whether the customer uses a card or not
Over one year, the ACH customer pays $300 more than they would have paid at the $500 base rate. That customer is effectively subsidizing a payment method they never used.
That is the sharp part of the baked-in model. It makes cash and ACH clients help fund everyone else’s airline miles and credit card rewards.
Credit card rewards are not free money. They are funded in part by interchange fees paid by merchants. Nobody is doing anything wrong by using a rewards card. They are choosing a payment rail with a real cost attached. The only question is whether that cost is paid by the person choosing the rail or distributed across everybody.
What everyone else already does
This is not an unusual concept.
Gas stations have displayed cash and credit prices on the same sign for decades. The customer can choose convenience, and the business can account for the different costs.
Ticketing, travel, and delivery platforms show a base price plus fees. A restaurant delivery order may include the food subtotal, a platform fee, a delivery fee, and a tip. Most people understand that the delivery company does not hide its entire cost structure inside the price of the burger.
Sales tax is another familiar example. It appears as a separate line at checkout, calculated and disclosed. Customers may not enjoy paying it, but they understand that visibility is preferable to pretending it does not exist.
The same principle applies here. A payment processing fee is a cost connected to a particular payment method. It should be disclosed clearly rather than buried in every service price.
According to J.D. Power’s 2026 U.S. Merchant Services Satisfaction Study, 35 percent of small businesses now include surcharges for customers who use credit cards. That is up from 34 percent in the prior study, according to J.D. Power reporting summarized by Brookside Payments.
That does not mean everybody should use a surcharge. It does show that the practice is no longer exotic. The market is sorting out whether to absorb, disclose, discount, or pass through payment costs.
One broader 41 percent versus 59 percent split is also sometimes repeated in payment-industry commentary. I have not found a reliable primary survey behind that specific comparison, so I am not presenting it as established market data. The safer conclusion is that both models are common, and neither deserves to be treated as automatically dishonest.
The rules matter
Credit card surcharging is generally allowed in most U.S. states, but it is regulated. The rules are not uniform, and a business cannot simply choose a percentage and apply it everywhere.
The important basics include:
- Credit card surcharges generally cannot be applied to debit or prepaid cards, even if a customer presses “credit” at the terminal.
- Visa limits the surcharge to the lower of the merchant’s actual cost of acceptance or 3 percent, according to Visa’s merchant surcharging guidance.
- Mastercard generally limits the surcharge to the lower of the merchant’s effective discount rate or 4 percent, and it cannot exceed the merchant’s actual cost. See Mastercard’s merchant surcharge rules.
- Disclosure is generally required at the point of entry, at checkout, and on the receipt.
- The surcharge should appear as a separate line item rather than being quietly mixed into the service price.
- Connecticut, Maine, Massachusetts, and Puerto Rico prohibit credit card surcharges, subject to changes in law and specific legal interpretations.
There can also be state-specific caps, notice requirements, and distinctions between a surcharge, a cash discount, and dual pricing.
That is why the clean approach is to keep the charge visible, capped, and disclosed. This is general education, not legal advice. Any business implementing a payment fee should confirm the current rules with its payment processor and legal adviser.
Why managed services use recurring billing and autopay
Managed IT is not a one-time delivery.
A monthly managed service fee supports continuous endpoint monitoring, patching, security tools, cloud license renewals, alert response, maintenance, documentation, and the readiness to help when something breaks. Those costs exist even during a quiet month when nobody submits a support ticket.
For a small business, managed IT services in Phoenix also need to be predictable. Chasing checks, reconciling manual transfers, and following up on missed invoices uses administrative time that should be spent maintaining client systems.
There is a practical security issue, too. A missed payment can interrupt a software renewal, cloud license, monitoring tool, or security service. That is dangerous for the client, not just inconvenient for the provider.
Autopay and payment choice are separate ideas:
- Autopay protects continuity.
- ACH provides the lowest direct price.
- Credit cards provide convenience, payment float, and rewards points, with a visible processing fee.
The goal is not to punish anybody. The goal is to keep the service active and let the client choose how to pay for it.
How we handle payment fees
Our policy is straightforward:
- The base rate represents the service, not the service plus a hidden processing buffer.
- The card fee is capped rather than open-ended.
- The fee is published on the invoice.
- It is not discovered after the fact.
- Our agreements state the fee terms in writing.
- Our agreements also allow periodic rate increases within a defined limit, so pricing changes are governed by the agreement rather than appearing as a surprise renegotiation.
A capped pass-through and a percentage markup are not the same thing. A cap protects the client on a larger invoice. An uncapped percentage grows with the invoice total.
If a client has a question, we explain the math. If there is a transition issue, we can discuss covering the cost for a period with the client’s knowledge. What we do not want to do is pretend the cost does not exist while recovering it somewhere else.
The honest downside
There is a real psychological cost to adding a fee on top of a bill.
Some clients would rather see one number. That is a legitimate preference, and I understand it. A single total is easier to read, easier to approve, and easier to explain internally.
Our answer is not that visibility is always more comfortable. It is that an inflated base rate becomes a permanent cost for every client, while a visible fee can be questioned, explained, or avoided by using ACH.
You can argue with a line item. You cannot argue with a rate that was quietly built to include it.
Baked-in markup versus visible capped pass-through
| Question | Baked-in markup | Visible capped pass-through |
|---|---|---|
| What does the base rate represent? | Service cost plus a hidden processing buffer | The service itself |
| What does an ACH client pay? | The inflated rate | The lower base rate |
| What does a card client pay? | The same inflated rate, whether the markup covers the real fee or not | Base rate plus the disclosed capped fee |
| Who absorbs the card cost? | Everyone, including ACH and cash clients | The client choosing the card |
| What happens on a large invoice? | The percentage markup grows with the invoice | The cap limits the additional charge |
| Can the client question it? | Not easily, because the cost is hidden | Yes, it appears as a separate line |
| Permanent or optional? | Permanent for every client | Optional based on payment method |
| What can the client see? | One simple total | Base service price, payment fee, and total |
| What is easier? | Psychologically easier for the client and administratively easier for the provider | More transparent, but requires explanation |
Which stage are you in?
Stage one: One number, no breakdown
You have no idea what you are paying for. You also cannot tell whether your rate includes a payment cost you never created.
Stage two: One number with a footnote
You know there is a fee somewhere, but nobody has clearly explained how it works. You have not asked what ACH would save you.
Stage three: An invoice you can read
You know the base rate, the card fee, the cap, and the ACH alternative.
Stage three is not about choosing the cheapest option. It is about being able to see what you are choosing between.
Practical takeaways
- Ask your provider whether payment processing is included in the base rate.
- If there is a separate fee, ask how much it is and whether it is capped.
- Check whether ACH is available and whether it removes the card fee.
- Ask what happens to your rate if you change payment methods, and get the answer in writing.
- If you charge payment fees, disclose them at intake, at checkout, and on the invoice, and confirm your state allows the structure.
- Compare the total annual cost, not just the monthly headline. That is where hidden markups become visible.
If you want to see the actual math on your own invoice, schedule an introductory call with us. We are happy to walk through it line by line, explain what the fee represents, and show you what the alternatives would cost.
