Here's something most Louisiana retailers don't realize: charging customers extra for paying with a debit card has been illegal nationwide for years. Not "illegal in some states." Not "a gray area." Illegal everywhere, under federal law and every major card network's rulebook, since long before anyone in Baton Rouge drafted a new bill.
So why did Louisiana just pass a law banning something that was already banned?
Because "illegal" and "enforced" have never been the same thing. On August 1, 2026, Act 751 takes effect, and for the first time, Louisiana retailers who tack a "card fee" onto a debit transaction face a very specific, very local set of consequences: cardholder notice letters, a 30-day clock to refund, and civil penalties up to $500 per violation. The gap between what card network rules quietly required and what a shopkeeper actually got away with just closed.
If you run a retail business — or you're the bookkeeper reconciling one — here's what changed, why it matters even though the underlying rule isn't new, and what to check in your point-of-sale system before the deadline.
What Act 751 Actually Does
Louisiana Governor Jeff Landry signed SB 254 into law as Act 751 on June 2, 2026. It prohibits retail businesses from imposing a surcharge — defined as "any additional amount imposed at the time of a transaction that increases the charge to a cardholder for the privilege of using a debit card" — whenever a customer chooses to pay by debit instead of cash, check, credit card, or a similar payment method.
The law's definition of "retail business" is broader than the word suggests. It covers any person or entity engaged in the sale of goods or services — which sweeps in restaurants, service providers, contractors, and plenty of businesses that wouldn't call themselves a "retailer" in casual conversation.
Effective date: August 1, 2026.
Enforcement mechanism:
- A cardholder who's been surcharged on a debit transaction must send the business written notice.
- The business then has 30 days to stop the practice and refund the surcharge. Comply within that window, and the customer's private right to sue is extinguished.
- If the business doesn't cure the violation — or the violation is willful or repeated — the cardholder can sue, and courts can award attorney's fees, court costs, and investigative costs on top of the refund.
- Businesses that ignore an administrative or court order tied to a violation face civil penalties of up to $500 per violation.
- The Louisiana Attorney General is required to stand up both a toll-free phone line and an electronic reporting system so consumers can flag violations directly, and the AG's office can pursue enforcement independently of any private lawsuit.
That last point is the real teeth of the law. Before Act 751, a customer who got hit with an illegal debit surcharge had no obvious, low-friction way to report it, and no state agency with a mandate to chase it down. Now there's a hotline, a portal, and a statutory penalty schedule.
Wait — Debit Surcharges Were Already Illegal?
Yes. This is the part that trips people up, and it's worth spelling out because it changes how you should think about compliance.
Credit card surcharging and debit card surcharging are governed by completely different rulebooks:
- Credit card surcharges are a state-by-state patchwork. Most states allow them, subject to conditions — a cap (typically 3-4%), disclosure requirements, and advance notice to your payment processor and the card networks. A handful of states (Connecticut, Massachusetts, Maine, and Puerto Rico as of 2026) ban credit card surcharges outright.
- Debit card surcharges are not a state-law question at all. They're prohibited nationwide by a combination of the Durbin Amendment (federal law governing debit interchange) and the operating rules of Visa, Mastercard, and the other card networks. No state permits debit surcharging, because no state gets a vote — the restriction sits above state law.
In other words, Act 751 doesn't create a new prohibition. It creates a new enforcement channel for a prohibition that already existed. Before this law, a Louisiana merchant who illegally surcharged a debit transaction was primarily exposed to action from their card processor (which could mean losing the ability to accept cards at all) or a card network compliance flag — not a state civil penalty or a customer lawsuit. Act 751 adds a state-level track with its own penalties, its own cure period, and its own reporting infrastructure, layered on top of rules that were already in force.
For a business, that's the opposite of comforting. It means the risk of getting caught just went up, even though the underlying rule didn't change at all.
Why This Actually Happens So Often
If debit surcharging has always been against the rules, why did Louisiana lawmakers feel the need to act? Because the violation is common — often unintentional, sometimes not.
The usual failure mode is a point-of-sale system that adds a flat "card fee" or "processing fee" to every non-cash transaction, without distinguishing between a credit card and a debit card at the terminal. Card networks use BIN (bank identification number) recognition to detect this automatically — "running it as credit" doesn't fool the network's compliance systems even if it fools your cashier — but a lot of small businesses never get flagged by their processor before a customer complains. Some merchants also assume that because credit card surcharging is legal in Louisiana, any card surcharge is fine. It isn't. The card type at the point of sale is what matters, not the merchant's intent.
Common places this shows up:
- A generic "3% card fee" applied at checkout without excluding debit cards
- Contractors and service businesses invoicing through a payment link that doesn't distinguish card types
- Restaurants and quick-service spots that added blanket "processing surcharges" during the high-interchange-rate years and never revisited the policy
- Multi-location retailers where corporate sets pricing but individual store POS terminals were configured (or misconfigured) locally
What to Check Before August 1
- Ask your payment processor directly whether your surcharge program excludes debit and prepaid cards. Don't assume — get it in writing. If you use a "cash discount" or "dual pricing" program instead of a stated surcharge, confirm it's structured as a genuine price differential (a lower cash price) rather than a debit fee wearing a different label; the substance, not the name on the receipt, is what regulators look at.
- Audit your receipts. Pull a sample of recent transactions and confirm the surcharge line item — if any — never applies to debit or prepaid card payments.
- Train front-line staff. If a cashier can override the register to add a manual fee, that's a compliance gap no software setting fixes.
- Know the 30-day cure window exists, and use it. If a customer sends written notice of a violation, refunding promptly and in full within 30 days is what keeps the dispute out of court.
- Multi-location operators should check every terminal, not just headquarters. Franchise and multi-location businesses are exactly the profile most likely to have one non-compliant location slip through.
The Bookkeeping Side Nobody Mentions
Compliance deadlines like this one create a bookkeeping problem that's easy to overlook until it lands on your desk: what happens to the accounting when a surcharge gets refunded under the 30-day cure provision?
If your books have been recording debit surcharges as ordinary revenue (often lumped into sales or a miscellaneous fee income account), a refund isn't just a customer service transaction — it's a correction that needs to flow through your ledger cleanly, ideally against the same account the original surcharge hit, so your income statement doesn't quietly overstate revenue for a period. If you're also facing a civil penalty or legal costs tied to a violation, those need their own expense categorization, not a shrug and a debit to "miscellaneous."
This is where clear, auditable records earn their keep. If every transaction — including fee income, refunds, and any penalty payments — is tracked in a system where you can see exactly what happened and when, reconciling a compliance cleanup like this takes minutes instead of a week of digging through processor statements. Beancount.io gives you plain-text accounting that's fully transparent and version-controlled, so tracing exactly how much surcharge revenue you collected, refunded, and where it landed on your books is a query, not an archaeology project. Get started for free and keep your records ready for whatever the next compliance deadline brings.