Eric Kuvykin

By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.

Treat the proposal as a checkout change

Adding a card-related charge changes what a customer sees, what an employee explains and what the accounting system records. The work begins before a terminal setting is enabled. A merchant needs a consistent plan for advertised prices, receipts, online carts, refunds and customer questions, together with a current review of applicable law, network rules and the acquiring agreement.

This guide deliberately does not provide a universal surcharge percentage or a state-by-state permission chart. Those details can change and depend on the transaction and the business. Start with the network’s current merchant resources and obtain written confirmation from the acquiring provider about the proposed configuration.

Document the exact customer journey

Write down the transaction types that the business accepts: counter sales, phone orders, invoice links, website orders and recurring charges. Identify where the customer first sees a price and where any additional amount would appear. A disclosure that is clear at a register may be absent from a telephone script or an emailed quote.

Ask the provider to demonstrate how different card types are identified and how excluded transactions are handled. Do not assume an employee can reliably classify a card by its appearance. Request sample receipts and refund examples rather than relying on a screenshot from a different merchant’s setup.

Model the effect on the business

Build a small worksheet using actual sales counts and average tickets. Compare the intended revenue effect with software charges, implementation time and possible changes in customer behavior. Include a scenario in which some customers choose another payment method or abandon a purchase. This is a sensitivity exercise, not a prediction that customers will respond in a particular way.

Also decide who can approve a pricing exception. If employees routinely waive a charge without recording why, the accounting result will be difficult to explain. A short exception log can show whether the policy is creating avoidable service problems.

Test before the public switch

Use a controlled test approved by the provider to examine a purchase, a void, a full refund and a partial refund. Check the printed and electronic receipts against the customer-facing explanation. Confirm that the general ledger separates the additional amount in a way the accountant understands.

A New York merchant should route the final design through a current local pricing and disclosure review. The same discipline applies to a Florida or New Jersey business, but one jurisdiction’s answer should not be copied into another’s policy. Keep the review date, the source links and the provider’s written response together.

Assign one person to maintain the signs, scripts and online text. Schedule a follow-up after the first statement closes, then compare the actual results with the original model. If complaints or unexplained adjustments increase, pause and investigate the specific step causing confusion before expanding the policy.

Sources and next steps

Primary reference: Visa’s merchant surcharging resources. Use the current resource and confirm implementation details with the provider or appropriate adviser.

Related reading: Interchange and Merchant Processing Costs: A Statement Review Guide; How to Read a Merchant Processing Statement Without Losing the Detail.

For the wider operating context, continue to the New York business operations guide on All State Merchants. Its state and local resources complement the payment workflow discussed here.

Eric Kuvykin writes about payments, fintech and business operations. Browse the article library for additional practical guides.