By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.
Begin with a purchase that later changes
A surcharge policy is incomplete if it explains only a successful sale. Customers also return items, reduce an order, cancel a service or discover a duplicate payment. The business needs a reviewed explanation of how those events affect every part of the amount charged.
Before configuring anything, obtain current legal and acquiring-provider guidance for the actual business and transaction types. This guide does not supply a universal surcharge limit or a legal answer about refunds. It describes the records and test cases that make the reviewed policy easier to implement consistently.
Make a small transaction matrix
List a normal purchase, a void before completion, a full refund, a partial refund and a corrected duplicate. For each case, record the original sale amount, any additional amount, the adjustment and the customer’s final net payment. Have the provider demonstrate the supported behavior using approved tests.
Compare the terminal receipt, emailed receipt and order history. If one screen labels an amount differently, ask whether the discrepancy is merely presentation or changes the accounting. Save sample receipts beside the provider’s explanation rather than relying on staff to remember the demonstration.
Give staff words they can use accurately
Write a short explanation based on the reviewed policy and tested behavior. A cashier should know what the system will do, what requires a manager and when support must investigate. Avoid a blanket promise that every adjustment appears immediately in a customer’s banking app.
For a New York merchant, review the final signs, displayed prices and online wording through a current local compliance check. A template used elsewhere should not be assumed suitable. If several locations share a website, confirm that the relevant location and payment journey receive the correct customer information.
Reconcile after launch
Keep a log of customer questions and exceptions during the first operating cycle. Connect each item to the transaction reference and the action taken. If an employee manually overrides the system, preserve the approval and reason so the accountant can explain the difference.
Review a complete statement and a sample of refunds after launch. Confirm that the policy, receipts and financial records tell the same story. If the tested behavior and the live behavior diverge, pause the affected configuration and obtain a clear provider response before extending it to additional channels.
References and related reading
Primary resource checked for this review: Visa’s current merchant rates, fees and rules resources. Confirm the current requirements and implementation with the responsible provider or appropriate adviser.
Continue with Surcharging: Questions to Resolve Before Changing Checkout Prices and How to Read a Merchant Processing Statement Without Losing the Detail.
For state and local business resources alongside this operating checklist, use the New York business operations guide on All State Merchants.
