U.S. card acceptance / a statement-first journal
LAUNCH EDITION · 15 NOV 2026
Guides

Before you add a surcharge, check three rulebooks.

State law, card-network rules and your processor’s implementation need to agree. This is a review workflow, not a 50-state approval map.

U.S. / USDPrepared 15 Nov 20262 min read
State law, card-network rules and your processor’s implementation need to agree. This is a review workflow, not a 50-state approval map.

Do not start with the terminal setting

A setting in a checkout dashboard is not permission to use it. Record where the merchant operates, which customers and channels are involved, what card products are presented and which agreement governs processing. Then check the legal and network position before changing customer prices.

The network layer

Visa’s U.S. Q&A distinguishes credit from debit and prepaid, requires advance acquirer notice and links the charge to acceptance cost within its stated ceiling. Mastercard has its own notice, disclosure and cap framework. Treat those as separate source documents, not a single universal percentage.

The state layer

Connecticut’s DCP describes a prohibition on payment-type surcharges and a separate framework for legitimate discounts. New York’s §518 addresses the total displayed credit-card price and its cost constraint. These two examples demonstrate why an “allowed everywhere” label is unsafe; they are not a complete legal survey.

Use a decision record

Prepare a record with the jurisdiction, applicable legal source, source date, network version, acquirer response and implementation owner. A source date and the date you checked it are different fields. If the rule is unclear or subject to change, leave the status unresolved and seek qualified advice.

Do not copy the dated state list in a network FAQ and present it as a verified current state tracker. The sources desk links to the primary materials and explicitly records the limits of our coverage.

Test the customer journey

Before any permitted rollout, test a credit card, a debit card, a prepaid product, a refund, a partial refund and an online checkout. Inspect the shelf or menu price, payment page, final receipt and reporting export. Keep the tests in a controlled environment and use the processor’s approved procedure.

A purchase charged at $100 plus a hypothetical $3 amount must not be described in this site as automatically lawful. Mathematics can show a total; it cannot establish that the merchant has met disclosure, product, location and contract conditions.

Frequently asked questions

Is a 3% fee always permitted?
No. A ceiling in a network document is not universal permission. Applicable law, actual acceptance cost, card type, disclosures and contract terms still matter.
Does choosing “credit” make a debit card surchargeable?
Visa’s cited U.S. Q&A says it does not. The underlying card remains a debit card.
Is this a complete state-law database?
No. It is a source-led workflow with selected primary examples, not a 50-state legal opinion.

Check the source.

Sources consulted for this edition. Public prices are not personalized quotes; a source’s original date and its retrieval date are separate.

Visa · U.S. surcharging Q&A ↗Mastercard · U.S. surcharge rules ↗Connecticut DCP · credit-card surcharges ↗New York · General Business Law §518 ↗

Checked 2026-11-15 · Read the methodology