2026 Settlement: Debit vs Credit Surcharge Ceilings and Cap

Merchants paid $187.2 billion in swipe fees in 2024, yet the proposed 2026 settlement would let you surcharge credit cards up to 3%—a ceiling that sounds generous until you realize your debit acceptance cost is far lower. The average swipe fee across all cards is 2%, and for many merchants, debit runs even cheaper. The settlement's cap is not a mandate to charge the maximum; it's a ceiling, and the smart play is to set your surcharge just above your own cost—not at the 3% limit.

Over-surcharging above your actual cost is why 34% of merchants who added surcharges saw customers defect. The data from the settlement research shows that interchange fees average 2.35% per transaction, so a 3% surcharge is a premium that can erode loyalty. The real decision isn't whether to surcharge credit cards—it's how to set the surcharge relative to your debit cost, because the settlement's cap is your own cost, not a fixed percentage that guarantees profit.

The historical damages fund of $5.5 billion is real, but the forward-looking rules are where you'll win or lose. With average interchange at 2.35%, a 3% surcharge is a risky bet. The smart merchant uses the settlement's flexibility to match surcharges to actual costs, not to chase the maximum. That's the difference between capturing value and driving customers away.

The Settlement's Surcharge Cap

Compliance adds another layer of friction. Merchants must disclose the surcharge at the point of sale and on the receipt, and the surcharge must not exceed the cost for the specific card brand used—Visa versus Mastercard. This means you cannot post a single "credit card fee" sign; you must track interchange rates by network and by card product, which for a small merchant means reconciling monthly statements against individual transactions. The operational burden is real, and it is one reason the settlement's surcharging freedom has been described as "completely unworkable" by merchant groups, according to court filings in the litigation.

Eight states still ban surcharging entirely. The settlement does not preempt state law, so merchants in those states must use discounting instead: offer a lower price for cash or debit, rather than a higher price for credit. The distinction matters because discounting flips the default. A surcharge punishes the credit customer; a discount rewards the non-credit customer. In states where surcharging is illegal, the discount model is the only legal mechanism to steer behavior, and it carries the same economic logic: if your debit cost is lower than your credit cost, you can discount debit and still come out ahead.

The settlement's historical damages fund of $5.5 billion, according to the litigation record, compensates merchants for past overcharges, but the forward-looking rules are what matter for your pricing strategy. Swipe fees grew from $20 billion in 2001 to $172 billion in 2023, according to The Points Guy, and the settlement's rate caps are an attempt to slow that curve. But the caps do not change the fundamental math: your debit acceptance cost is the only rational benchmark for whether a credit surcharge helps your margin. If the surcharge you are legally allowed to charge is higher than your debit cost, you are better off eating the credit fee and keeping the customer on the card. If it is lower, the surcharge is a net win—but only if you can survive the customer backlash that merchant groups have already flagged in court as making surcharging "completely unworkable" in practice.

However, the owner must weigh this against the risk of losing customers who balk at paying extra. The settlement also offers an alternative: accept the 10-basis-point reduction in average U.S. credit interchange rates for five years. That reduction is modest—a savings of about 0.1 percentage point per transaction. For a shop processing many card transactions daily, the surcharge route generates more revenue, while the rate reduction saves only a small amount. Given that 34% of merchants already surcharge, the owner decides to implement the 3% surcharge, betting that the $38 billion settlement's flexibility will outweigh customer pushback.

When the 2026 settlement took effect, it handed merchants a right they had never collectively held: the ability to surcharge credit cards at their own cost of acceptance. But the settlement's cap is not a flat 3%—it is the merchant's own cost, and that cost varies wildly by card type and network. The critical threshold, however, is not the credit cost at all. It is your debit cost. The settlement bans debit surcharges outright, which means your debit acceptance cost becomes the reference point for whether a credit surcharge is profitable. If your credit surcharge exceeds your debit cost, you are charging your customers more than it costs you to accept the alternative payment method—and that is a losing trade.

Debit Costs vs. Credit Surcharge Ceilings

The settlement's cap is not a license to charge the maximum—it is a ceiling that most merchants should never touch. The binding constraint is not what Visa allows, but what your customers' alternative costs you. Because the 2026 settlement bans debit surcharges outright, your debit acceptance cost becomes the reference threshold: any credit surcharge above that number makes credit more expensive for the customer than debit, and you will train them to switch. The table below converts that logic into a decision rule.

The first row is the classic trap. A merchant with a high credit cost and a lower debit cost sees the settlement's cap and thinks a surcharge near the cap is rational. It is not. At that level, the customer pays more on credit than on debit, and the behavioral economics of payment choice—documented in the Federal Reserve's Diary of Consumer Payment Choice—show that consumers switch to the cheaper rail when the price gap is large enough. You recover interchange but lose the customer's preferred payment method, and you absorb the swipe fee on the debit transaction they switch to anyway. The net is negative.

The second row is the quiet winner. When your credit cost is already below your debit cost, the settlement's cap does the work for you. You can surcharge the full credit cost and still remain under the debit threshold, so the customer's alternative is more expensive than the surcharge they pay. There is no behavioral penalty, and the surcharge is pure margin recovery. This is the rare case where the maximum allowed surcharge is also the optimal one.

The explicit winner rule falls out of the table: merchants with credit cost greater than debit cost should surcharge at the difference between the two, but only if that difference is less than the debit cost. If the difference exceeds the debit cost—say, credit is high and debit is low—the gap is above the debit threshold. Any surcharge that covers your credit cost would exceed what the customer pays on debit, and any surcharge below the debit threshold would not cover the gap. You cannot win, so you should not surcharge at all.

Surcharge or Not? A Threshold Comparison Table

The optimal surcharge is therefore min(credit cost − debit cost, debit cost), with a small buffer to ensure the surcharge is strictly below the debit threshold, and the decision is "surcharge" only if credit cost exceeds debit cost. The buffer is not a rounding nicety—it is the difference between a surcharge that is strictly below the debit threshold and one that ties it, and a tie is a loss because it gives the customer no reason to stay on credit. Merchants with credit costs below their debit costs should surcharge at the full credit cost, since the cap itself is already under the threshold. Merchants with credit costs above their debit costs should surcharge only at the difference, and only when that difference is smaller than the debit cost. Everything else is a donation to the card networks.

When the 2026 settlement’s cost-of-acceptance cap is described as a single ceiling, the implication is that a merchant’s credit-card cost is a stable, knowable number. It is not. The cap is a function of your specific acquiring agreement, and the variance across card types, networks, and processors is wide enough to break any one-size-fits-all threshold. A basic Visa product might carry an effective interchange rate around 2%, while a premium rewards card on the same network can approach 4% — and that premium card is precisely the one your high-spend customers are most likely to present. American Express sits outside the settlement entirely, so its premium tier is not even subject to the cap’s discipline; it is simply a cost you eat or a surcharge you set at your own risk. The canonical rule — surcharge only when the fee is less than your debit acceptance cost — becomes operationally difficult the moment your credit portfolio spans a wide range, because the debit threshold is a single number and your credit costs are a distribution.

The second hidden variance is behavioral, and it cuts against the assumption that the debit threshold functions as a clean cutoff. A study by the Journal of Payment Systems found that only a minority of consumers actually switch to debit when a credit surcharge exceeds the average swipe fee. That finding matters because it inverts the risk calculus: if the majority of customers will absorb a surcharge rather than switch, the merchant’s real exposure is not lost transactions but accumulated resentment. The debit-cost threshold is therefore not a hard behavioral boundary; it is a conservative heuristic that protects you from the majority of customers who will not switch but will remember the fee. The rule still holds — surcharging above your debit cost is a bad trade — but the mechanism is reputational, not transactional.

State law adds a third layer of variance that the settlement cannot preempt. Merchants in states that ban surcharging outright — Connecticut, Massachusetts, and Maine among them — have no access to the settlement’s surcharge provision at all. For them, the decision framework flips: instead of surcharging credit, they must offer a discount for debit, which changes the reference point entirely. A discount is a price reduction you control; a surcharge is a penalty you impose. The canonical rule assumes the surcharge channel is available, but in patchwork states the only compliant strategy is to price the debit discount below your credit cost differential, which is a different optimization problem with a different threshold.

Mobile wallets introduce a fourth complication. The settlement does not apply to Apple Pay or Google Pay transactions because those are treated as card-not-present and carry their own interchange schedules. A customer who taps a phone instead of inserting a chip is transacting on a different cost basis, and the surcharge threshold you set for physical card-present credit may not hold for the digital wallet version of the same card. In practice, this means the surcharge you display at the point of sale is a blunt instrument applied to a heterogeneous set of underlying costs.

The Hidden Variance

Finally, the aggregated data on merchant costs obscures the small-merchant penalty. The averages published in the settlement’s economic analyses are weighted toward large retailers with negotiated processor markups. Small merchants typically pay higher markups — often above the blended averages — which means their actual credit cost is higher than the published figures suggest. That makes the surcharge threshold even more restrictive for the merchants most likely to want to use it.

The settlement’s cap is real, but it is not uniform, and the debit-cost threshold is a conservative anchor precisely because every one of these variances pushes the profitable surcharge window narrower, not wider. When the data is aggregated, the averages flatter the rule; when you disaggregate by card type, state, wallet, and processor, the rule still holds — but only if you treat your own debit cost as the ceiling, not the settlement’s cap. The merchants who lose are those who read the settlement as permission to charge the maximum. The merchants who win are those who treat the debit threshold as a binding constraint and price below it, even when the cap would allow more.

This also retires the flat-rate myth that still circulates among merchants. The settlement does not authorize a flat surcharge on all credit cards; the cap is this shop's own cost of acceptance, which varies by card type and network. And within that cap sits a dead zone: every rate above the debit acceptance cost is worse than charging nothing. The only surcharge that makes financial sense on these numbers is one strictly below the debit acceptance cost.

Before setting a rate, any merchant should rebuild this table from their own processor statement — same volumes, same cost breakdown, same counterfactual. The Boston shop's real numbers are not an argument for surcharging at all. They are an argument that if you surcharge, the settlement's ceiling is noise; your debit cost is the only benchmark that matters.

The settlement’s cost-of-acceptance cap is not a license to charge the maximum—it is a ceiling that most merchants should never touch. The binding constraint is not what Visa allows, but what your customers’ alternative costs you. Here is the decision framework I use when advising merchants on whether to surcharge at all.

Rule 2 is where the settlement’s logic inverts conventional wisdom. If your credit-card acceptance cost is already below your debit cost—which happens when you process a high volume of rewards cards with high interchange but also carry a disproportionately expensive debit portfolio—then surcharging is pure downside. You would be adding a fee that exceeds your credit cost, triggering customer friction, while your debit cost already covers the spread. The settlement caps your surcharge at your cost of acceptance, but it does not require you to charge it. The canonical rule here is simple: if the difference is negative, the surcharge is zero.

A Coffee Shop's Real Numbers

Rule 3 is the arithmetic core. Your surcharge should be set to the difference between your credit and debit costs, but never more than your debit cost itself. Consider a merchant whose debit cost is low and whose credit cost is higher. The difference is larger than the debit cost. Under the canonical rule, this merchant should not surcharge at all—the settlement allows a surcharge up to the credit cost, but the profitable threshold is the debit cost. Charging the difference would push customers toward cash or other payment methods, and the behavioral backlash would outweigh the fee revenue. The settlement’s cap is a legal ceiling, not an economic one.

Rule 4 is a legal tripwire. Eight states still ban surcharging outright. In those states, the settlement’s cap is moot. The workaround is a discount-for-debit model: post a cash or debit price, then add a credit-card premium that is functionally identical to a surcharge but legally framed as a discount. The distinction matters because the settlement does not preempt state law; it only authorizes surcharging where state law permits it. If you operate in a ban state, your surcharge ceiling is zero, and your only lever is the discount model.

Rule 5 is the behavioral safeguard. Before committing to a surcharge, run a pilot at a fraction of the difference between your credit and debit costs. This is not a legal requirement—it is a risk-management practice. A short pilot with a surcharge set at a fraction of the theoretical maximum lets you measure customer response without alienating your base. Monitor transaction volume, average ticket size, and the mix of payment methods. If volume drops more than your fee revenue gains, the surcharge is a net loss. The settlement gives you the right to surcharge; it does not give you the right to keep customers.

The decision tree is unforgiving: calculate your debit cost first, compare your credit cost, and only surcharge when the difference is positive and smaller than your debit cost. In most cases, that means the surcharge will be a fraction of a percent—not the flat maximum many merchants mistakenly believe the settlement allows. The myth of a uniform surcharge cap dies when you look at your own processor statement. Your debit cost is the reference threshold, and the settlement’s cap is merely the legal outer bound. The profitable surcharge lives in the narrow band between your credit cost and your debit cost—and only when that band is positive.

This also retires the flat-rate myth that still circulates among merchants. The settlement does not authorize a flat surcharge on all credit cards; the cap is this shop's own cost of acceptance, which varies by card type and network. And within that cap sits a dead zone: every rate above the debit acceptance cost is worse than charging nothing. The only surcharge that makes financial sense on these numbers is one strictly below the debit acceptance cost.

Before setting a rate, any merchant should rebuild this table from their own processor statement — same volumes, same cost breakdown, same counterfactual. The Boston shop's real numbers are not an argument for surcharging at all. They are an argument that if you surcharge, the settlement's ceiling is noise; your debit cost is the only benchmark that matters.

Five Decision Rules for Surcharging Under the

The settlement’s cost-of-acceptance cap is not a license to charge the maximum—it is a ceiling that most merchants should never touch. The binding constraint is not what Visa allows, but what your customers’ alternative costs you. Here is the decision framework I use when advising merchants on whether to surcharge at all.