Credit Card Surcharge Program Checklist

Direct answer

Do not enable a surcharge from a terminal menu until the program has passed written eligibility and configuration review. Confirm the merchant, location, sales channel, card product, processor, acquirer, and jurisdiction are eligible; obtain any required registrations or notices; calculate the allowed amount under current rules; exclude debit and prepaid transactions; disclose the surcharge before payment; itemize it correctly on receipts; and test refunds, tips, taxes, split tenders, wallets, and card-type recognition. Network and legal requirements can change and differ by place. AMP is not representing this page as a legal review or authorization to surcharge. The acquiring provider and qualified jurisdiction-specific advisers should approve the implemented design before it is used.

The launch gates

Gate one is authority: identify the acquiring bank or processor responsible for the merchant account and obtain its current surcharge instructions. Gate two is jurisdiction: list every state or other jurisdiction where the customer transaction occurs and ask qualified counsel or an appropriate authority about current restrictions. Gate three is product eligibility: document how credit is distinguished from debit and prepaid, including wallets and cards processed without a PIN. Gate four is amount: preserve the provider’s calculation and evidence for any cap or cost-based limit; never infer a permitted percentage from a competitor’s sign. Gate five is notice and disclosure: complete required network/acquirer notices and place approved language at entry, point of sale, online checkout, and receipt as applicable. Gate six is operations: test tax, tips, partial approvals, refunds, split tender, recurring payments, offline mode, and reporting. Gate seven is monitoring: assign an owner to review rule updates, complaints, configuration drift, and statement charges.

Why a cap is not a recommendation

Suppose a vendor proposes adding 3% to a $50 eligible credit transaction, producing a $1.50 surcharge and $51.50 subtotal before any relevant tax treatment. That arithmetic only shows the configured amount. It does not establish that 3% is permitted, that it is no greater than the merchant’s applicable cost, that the transaction is eligible, or that disclosures are adequate. If the same branded card is actually debit or prepaid, surcharge treatment may be prohibited under network rules even when run “as credit.” If a $10 partial refund occurs, the system also needs a documented method for the associated surcharge. Obtain written answers and test with the provider; do not use this example as a rule statement.

Build a topic-specific comparison

For a proposed credit-card surcharge program, compare like with like and retain the evidence behind every score. Collect acquirer instructions from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare merchant category and locations under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers. Define an acceptance result for jurisdiction inventory, identify which document or reproducible test proves it, and record limitations instead of reducing the result to yes or no. Ask who supplies, configures, bills, supports, and can change notice records; preserve the answer with the controlling proposal or agreement rather than relying on a meeting note. Test cost calculation with ordinary and difficult cases from this business, including a correction or failure path, so the comparison reflects daily work instead of a sales script. Score approved signs separately for current fit, implementation effort, continuing ownership, and exit risk; a strong feature can still create an unacceptable operational dependency. Collect checkout screens from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare receipt samples under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers. Define an acceptance result for refund logic, identify which document or reproducible test proves it, and record limitations instead of reducing the result to yes or no. Ask who supplies, configures, bills, supports, and can change card-product detection; preserve the answer with the controlling proposal or agreement rather than relying on a meeting note.

Calculate the relevant costs

The cost model for a proposed credit-card surcharge program should expose dollars, timing, uncertainty, and operational effort. Quantify eligible credit volume as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model actual merchant cost at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace configuration and signage to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls staff training, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination. Measure complaints separately from revenue or gross payment volume so a percentage headline does not hide dollars, staff effort, customer loss, or cash-flow timing. Reconcile actual refund adjustments after launch to the approved model, investigate the variance, and update the forecast without retroactively changing the original assumptions. Quantify monitoring as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model provider fees at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace tax handling to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls remediation when rules change, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination.

Common mistakes

Use these failure patterns as review prompts, then document the control or owner that addresses each one.

• Surcharging signature debit or prepaid because the terminal did not request a PIN.
• Using an old cap copied from a blog instead of current network and acquirer material.
• Completing network notice but overlooking jurisdiction, processor, signage, receipt, or e-commerce requirements.
• Applying a percentage above the merchant’s applicable cost merely because software permits it.
• Failing to reverse or adjust the surcharge consistently on full and partial refunds.
• Assuming one configuration works across every location, channel, merchant account, and wallet.

Implement and test this topic

Implementation for a proposed credit-card surcharge program is complete only when topic-specific success and failure paths have passed. Turn this into a witnessed acceptance test: attempt eligible credit. Record the starting configuration, expected result, actual result, identifiers, owner, and follow-up for any exception. Assign a trained role to debit, restrict permissions to what that role needs, and document the exact point where staff must stop and escalate. Exercise prepaid in normal operation and under a realistic failure, correction, timeout, or duplicate condition; a single successful attempt is not adequate evidence. Pilot wallets with limited exposure where practical, preserve a continuity or rollback path, and name the person authorized to pause the launch. Verify reporting and reconciliation after card-not-present, because a customer-facing success message does not prove settlement, downstream synchronization, or correct accounting. Revisit tips after the first operating cycle and look for manual workarounds, support delays, configuration drift, customer confusion, or terms that differed from implementation. Turn this into a witnessed acceptance test: tax. Record the starting configuration, expected result, actual result, identifiers, owner, and follow-up for any exception. Assign a trained role to split tender, restrict permissions to what that role needs, and document the exact point where staff must stop and escalate. Exercise partial approval in normal operation and under a realistic failure, correction, timeout, or duplicate condition; a single successful attempt is not adequate evidence. Pilot full and partial refunds with limited exposure where practical, preserve a continuity or rollback path, and name the person authorized to pause the launch. Verify reporting and reconciliation after offline transactions, because a customer-facing success message does not prove settlement, downstream synchronization, or correct accounting. Revisit every location after the first operating cycle and look for manual workarounds, support delays, configuration drift, customer confusion, or terms that differed from implementation.

Verify the decision

Verify a proposed credit-card surcharge program with current, appropriately authoritative material and reproducible business records. Use dated Visa and Mastercard surcharge publications for the claims it is positioned to support, save its publication or version date, and distinguish direct evidence from interpretation. Cross-check the acquirer’s written approval and instructions against the implemented configuration and the controlling agreement; general documentation may not describe negotiated terms or enabled features. Record who reviewed applicable regulatory material, when it was reviewed, what question it answered, and which material uncertainty remains before a decision can be approved. Recheck qualified local review without relying on vendor marketing whenever the provider, network rule, jurisdiction, product version, sales channel, or business workflow changes materially.

Primary and authoritative sources

Links were accessed 2026-09-08. Confirm the current version before relying on a rule or requirement.

1. Credit and Debit Card Surcharges — Visa
2. Merchant Surcharge Rules — Mastercard
3. Electronic Code of Federal Regulations, Regulation Z — Consumer Financial Protection Bureau