Surcharge Refund Records: Preserve the Pricing Version Applied to the Sale | Eric Kuvykin

Reviewed October 17, 2026. This operational guide replaces an earlier general overview. The original publication date and URL are retained.

A refund can occur after a business changes its checkout pricing. The return workflow needs the original sale’s approved pricing record rather than an assumption that today’s settings apply.

Identify the original pricing evidence

Retain the order reference, receipt, adjustment line, charged total and configuration version in effect at the sale. Separately record the current version. Do not overwrite historical pricing evidence when a terminal setting changes. The required treatment must be confirmed under current network requirements, applicable law and acquirer instructions; this worksheet does not prescribe a surcharge rate or legal refund formula.

Design a cross-version test

In a provider-approved environment, create a sale under configuration A, change to configuration B and then initiate its refund. Ask the provider which record determines the adjustment and whether a partial return behaves differently from a full return. Use approved test credentials. A test amount is an input for checking the workflow, not evidence that a pricing practice is permitted.

Reconcile each component separately

For an illustrative merchandise return of $40 from a $100 sale, list merchandise, original pricing adjustment, any returned adjustment and the resulting credit as separate fields. Compare the approved expected result with the receipt, processor record and accounting entry. Do not simply apply the current percentage to the return or assume that a merchandise-only refund completes every obligation.

Keep the exception and approval together

If the system uses an unexpected version, preserve screenshots, references and configuration identifiers and obtain the provider’s written explanation. Name who can approve a correction through the original payment workflow. Mastercard publishes merchant surcharge requirements; verify the applicable instructions before release. The completed record should explain which policy and software version governed the refund, who checked it and how the customer’s credit reconciles.

Sources and related reading

Primary reference: Mastercard’s merchant surcharge requirements. Examples and worksheets are illustrative operational analysis, not reported client results.

Continue with the AMS New York merchant reading path and merchant technology decision worksheet.

Share this article