California Credit Card Surcharge Law: What Merchants Can and Cannot Do

California credit card surcharge law confuses merchants because two separate rule systems govern it and they do not say the same thing. State law sets one boundary. Visa and Mastercard operating rules set another, usually tighter one. Your processor agreement sits on top of both. A practice can be lawful under state law and still get you fined or terminated for breaking network rules, which is the mistake most merchants actually make.

The short version of where California landed

For years California had a statute barring credit card surcharges. Courts held it unconstitutional as applied to truthful surcharge labeling, and the practical result is that California merchants may surcharge credit card transactions provided they follow card network requirements and disclose accurately. That is the operating reality today. Because this area has moved through litigation and legislation more than once, confirm the current state of the rule with your processor and your counsel before you launch a program.

What card network rules require

These are the constraints that bite in practice, and they apply nationally:

• You must register your intent to surcharge with the card networks, generally with advance notice, and notify your acquirer.
• The surcharge is capped. Visa and Mastercard both set a ceiling, and it cannot exceed your actual cost of acceptance for that transaction.
• You cannot surcharge debit cards or prepaid cards, including a debit card run as credit. This is the rule most often broken by accident, because terminals that are not configured correctly will happily surcharge a debit transaction.
• The surcharge must appear as a separate line item on the receipt, clearly labeled.
• Disclosure must appear at the point of entry, at the point of sale, and on the receipt.
• Brand level and product level surcharging have different rules about consistency across brands.

Any of those violated will surface eventually, usually through a customer complaint routed to the network. The fix is configuration, not intent, which is why the terminal or gateway setup matters more than your posted sign. If you are evaluating a setup, ask your card processing provider to demonstrate a debit transaction running without a surcharge before you go live.

Where SB 478 fits

SB 478, effective July 2024, is the state's junk fee law. It does not ban surcharging. It changes how prices must be advertised: the price a consumer sees must include mandatory fees, excluding government imposed taxes and, in some cases, shipping. The relevant question for a surcharge is whether it is genuinely avoidable. A fee a customer can escape by paying another way is treated differently from a fee every customer pays no matter what.

Which means the dangerous design is not the surcharge itself. It is the flat percentage tacked onto every order, described as a card fee, that a customer cannot avoid because you only accept cards. That is much closer to a mandatory fee that belongs in the advertised price. Have counsel look at your specific setup rather than reasoning by analogy.

Cash discounting is a different animal

Some merchants avoid surcharge rules by posting a higher price and offering a discount for cash. Done properly, that is a genuinely different structure and it has historically had more legal room. Done improperly, which is common, it is a surcharge with the label changed, and the networks look at substance rather than what the sign says.

The distinguishing question is what the posted price is. If your menu, shelf tags and website show the higher price and cash buyers get a reduction at the register, you have a discount. If they show the lower price and card buyers get an addition, you have a surcharge and all the surcharge rules attach.

Practical alternatives to consider first

Surcharging is not the only way to reduce card cost, and it carries customer relationship risk in competitive markets. Before building one:

1. Move to pass-through pricing so you can see what interchange actually costs on your mix rather than guessing.
2. Fix interchange qualification issues. Missing address data, late settlement and card not present entry on transactions that could be present all push you into higher categories.
3. Move large invoices to bank debit, where cost is flat per item rather than proportional. This is often bigger than any surcharge program.
4. Reduce disputes. Chargebacks carry fees and, past roughly 0.9 to 1 percent of monthly transactions, network monitoring programs that cost far more than interchange.

If you do surcharge, do it completely

Half implemented surcharge programs are the ones that generate liability. A complete implementation means registration filed, terminals configured to identify debit and exclude it, signage at the entrance and at every register, checkout copy that states the percentage before payment selection, receipts with a separate labeled line, and staff who can explain it in one sentence. Ecommerce needs the disclosure before the customer enters card details, not on the confirmation page.

Also decide what happens on refunds. If you surcharge a sale and later refund it, the surcharge generally goes back with it. Build that into your refund process rather than handling it case by case.

The compliance posture to hold

Treat surcharging as a program with an owner, documentation and periodic review, not as a switch someone flipped. Keep records of your registration, your cost of acceptance calculation supporting the percentage you charge, and your disclosure screenshots. If a network inquiry arrives, those documents are the whole defense.

None of this is legal advice, and the interaction between state consumer protection law and network rules is exactly the kind of thing that shifts. Confirm the current requirements with your processor and your counsel, then build the program properly or do not build it at all.