Surcharging a debit card
run as credit — the most
common violation, explained

Every debit card can be run two ways at a terminal: as a PIN debit transaction, where the cardholder enters a PIN and the transaction routes over a debit network, or as a signature transaction, where no PIN is entered and the transaction routes over the Visa or Mastercard credit rails. To the terminal and the merchant, a signature-debit swipe looks identical to a credit card swipe — same prompt, same signature line, same authorization flow. That similarity is exactly where the most common dual-pricing violation lives: a surcharge program built to add a fee on "credit transactions" ends up surcharging a debit card the moment that card is run without a PIN, because the software is reading the transaction path instead of the card itself.

The card doesn't change — only the route does

A card's classification as debit, prepaid, or credit is determined by the issuing bank at the moment the card is issued, encoded in the card's BIN (bank identification number) — the first six to eight digits of the card number. That classification is permanent for the life of the card. Running a debit card without a PIN does not reclassify it as a credit card; it only changes which network rail carries the authorization. Visa's Core Rules state the surcharge prohibition in terms of card type, not routing method, and explicitly extend it to prepaid cards as well: merchants "must not surcharge debit or prepaid card transactions" under any circumstance, regardless of how the transaction was processed.

This is the detail that trips up otherwise-careful merchants. A cashier, a POS default setting, or a payment gateway rule that surcharges "any transaction not run as PIN debit" is building the surcharge decision on the wrong variable. The right variable is the card's issuer-assigned type, checked at the BIN level, independent of how the specific transaction happened to route.

Why this is the most common violation, not an edge case

Most dual-pricing and surcharge violations that get flagged in acquirer monitoring don't come from merchants who set out to break the rules — they come from software that was configured around the wrong signal. Terminals and gateways often default to distinguishing transactions by network path (debit network vs. credit network) because that's the data point that's cheapest and fastest to check at the point of sale. Checking the actual card type requires a BIN lookup against a maintained database, which is a step some low-cost or improperly configured surcharge tools skip or implement incorrectly.

The result is a program that works correctly most of the time — true credit cards get surcharged, PIN debit is correctly excluded — but silently fails on the specific case of signature debit. Because a signature-debit transaction looks and feels identical to a credit transaction at the counter, neither the cashier nor the customer typically notices anything wrong in the moment. The violation surfaces later: a customer checks their statement, sees a surcharge on what they know is a debit card, and disputes it or complains — or an acquirer's periodic compliance sweep catches the pattern across a merchant's transaction history.

The terminal can't tell the difference between a credit card and a signature-debit card. Your surcharge logic has to.

What a compliant setup actually checks

A properly configured surcharge program performs card-type identification at the BIN level before the fee is ever calculated, and it does this as a step separate from routing. In practice this means the payment gateway or processor maintains (or subscribes to) a current BIN table that flags debit and prepaid ranges, checks every incoming card against that table at authorization, and suppresses the surcharge line item entirely for any card that matches — independent of whether that specific transaction happened to run as PIN debit or signature debit. The merchant's terminal display and receipt should reflect this automatically; if a merchant or their staff has to manually decide whether to apply a surcharge based on how the card was run, the system is built on the wrong logic.

This is also why processor selection matters more than it might seem for a merchant considering dual pricing or surcharging. A processor whose surcharge tooling was built and tested against current network rules — with BIN-based exclusion as a default, not an optional configuration — removes this failure mode structurally. A merchant bolting a generic percentage-based fee onto an existing terminal without that underlying BIN logic is relying on someone downstream to have built it correctly, which isn't always true.

Cash discount programs sidestep this specific risk

A properly structured cash discount or dual-pricing program handles this differently and, on this specific failure mode, more safely. Instead of adding a surcharge line item that must be selectively suppressed for debit cards, a compliant dual-pricing program posts one price for all non-cash tenders — debit and credit alike — funded by a documented discount off that price for customers who pay cash. Because the non-cash price applies uniformly to every card type, there's no BIN-exclusion step that can be missed or misconfigured; the debit-detection failure mode doesn't exist in the same way it does in a surcharge model. Dual pricing carries its own separate signage and disclosure requirements — see our breakdown of the zero-processing-cost dual-pricing model — but it removes this particular trap.

What it actually costs a merchant when it goes wrong

The consequences scale with how long the misconfiguration runs undetected. A single disputed surcharge on a debit transaction typically means a refund to the cardholder and, at most, an isolated compliance note. A pattern across dozens or hundreds of transactions — the realistic outcome of a POS default that's been live for months — is what triggers acquirer-level consequences: mandatory refunds across the affected transaction set, fines assessed to the merchant's acquiring bank (which the acquirer's agreement typically allows it to pass through to the merchant), and in states with active surcharge statutes, potential exposure to a state attorney general complaint or private consumer action layered on top of the network-level consequences. Acquirers that see a recurring pattern of debit surcharging across a merchant's account — rather than a one-off error — can also treat it as grounds to terminate the merchant account, since the acquirer itself is contractually bound to enforce the card brand rules it operates under.

None of this requires bad intent. It requires an unaudited default setting running quietly for months, which is exactly why the quarterly compliance checklist we cover elsewhere on this desk should include an explicit line for "pull a debit-card sample and confirm zero surcharges appear" — not just a general read of the statement.

Frequently asked questions

Can I surcharge a debit card if it's run through as a credit transaction?

No. Visa and Mastercard rules bar surcharging any debit or prepaid card regardless of how the transaction is routed or authorized. A debit card run through the credit network — signature debit, no PIN entered — is still a debit card by BIN, and surcharging it is a rule violation even though the terminal processed it exactly like a credit transaction.

How does a terminal know if a card is debit or credit for surcharge purposes?

A compliant surcharge program checks the card's BIN — the first six to eight digits of the card number — against a database that identifies the issuing bank and card type, not the network path the transaction takes. Debit and prepaid BINs are excluded from the surcharge automatically before the fee is calculated, independent of whether the cardholder entered a PIN or signed.

What happens if a merchant surcharges debit cards by mistake?

The card networks can require refunds to affected cardholders, fine the merchant's acquirer (who typically passes the cost to the merchant), and in states with surcharge statutes, expose the merchant to consumer complaints or state attorney general action. Acquirers that detect a pattern of debit surcharging can also terminate the merchant account under the card brand rules they're bound to enforce.

Is a cash discount program a safer alternative to a debit-aware surcharge?

A properly built dual-pricing or cash discount program is inherently safer on this specific failure mode because it applies a non-cash price uniformly to every card — debit or credit — funded by a documented discount off a stated price, rather than adding a line-item surcharge that must be selectively suppressed for debit BINs. It removes the debit-detection step as a point of failure, though it still has its own disclosure and structuring requirements.

Does the card network's 3% surcharge cap even apply to debit cards?

The cap is irrelevant to debit because debit and prepaid cards cannot be surcharged at all, at any rate. The 3% Visa cap (4% for Mastercard, with dual acceptance meaning the lower 3% governs in practice) applies only to credit card transactions that are eligible for a surcharge in the first place.