Skip to main content
Merchant SupportAgent Login
AMP Payment Systems
Menu

Payment & business solution

Surcharge Programs

Evaluate a separately disclosed charge on eligible credit-card transactions only after confirming current legal, network, processor, registration, cap, signage, receipt, and payment-identification requirements. Compare merchant fit, implementation steps, limitations, and complete-cost variables before selecting a provider.

Call a Payments Specialist
What is the first decision for Surcharge Programs?
current state and local law, network and processor rules, merchant category, credit versus debit or prepaid identification, cap calculation, required notices, ecommerce display, receipt treatment, refund logic, and approved provider configuration.
What capability matters most?
correct identification and treatment of eligible credit cards without applying the program to ineligible tenders
What should the written comparison include?
processing not recoverable through a surcharge; registration and operational review; compatible routing and POS software; signage, ecommerce changes, training, monitoring, support, and agreement terms

Plain-language definition

Surcharge Programs for merchant operations

A credit-card surcharge is an added, separately disclosed amount on an eligible credit-card transaction; it is distinct from dual pricing and a genuine cash discount.

Who it is for

  • Businesses that need correct identification and treatment of eligible credit cards without applying the program to ineligible tenders
  • Teams replacing a workflow constrained by the highest-risk failures are surcharging debit or prepaid, exceeding an allowed amount, missing notice or signage, disclosing too late, applying inconsistent rules across channels, or assuming the pos can identify eligible cards correctly
  • Decision-makers comparing complete written scope and terms

How evaluation and setup work

  1. 1Document current state and local law, network and processor rules, merchant category, credit versus debit or prepaid identification, cap calculation, required notices, ecommerce display, receipt treatment, refund logic, and approved provider configuration.
  2. 2Validate correct identification and treatment of eligible credit cards without applying the program to ineligible tenders.
  3. 3Compare itemized scope, responsibilities, pricing, and agreement terms.
  4. 4Configure, test, train, launch, and reconcile before retiring the previous workflow.

Day-to-day workflow

How Surcharge Programs works in practice

Before activation, the merchant and provider determine eligibility, notices or registration, permitted amount, channel support, signage, checkout disclosure, receipt display, refunds, and monitoring. Test consumer and commercial credit, debit run as credit, prepaid, tips, partial refunds, card-not-present activity, and every device or integration.

  • Map the current state: current state and local law, network and processor rules, merchant category, credit versus debit or prepaid identification, cap calculation, required notices, ecommerce display, receipt treatment, refund logic, and approved provider configuration.
  • Configure the operating path around correct identification and treatment of eligible credit cards without applying the program to ineligible tenders
  • Test normal sales, corrections, refunds, receipts, reporting, and an outage or fallback scenario.
  • Launch with named owners for staff questions, provider escalation, reconciliation, and post-launch review.

Implementation

What must be decided before Surcharge Programs goes live

The implementation requirement is specific: current state and local law, network and processor rules, merchant category, credit versus debit or prepaid identification, cap calculation, required notices, ecommerce display, receipt treatment, refund logic, and approved provider configuration. AMP can document dependencies and questions, but the merchant and applicable providers must confirm compatibility, account approval, responsibilities, testing, training, and support in writing.

  • Inventory devices, software, agreements, and integrations.
  • Assign responsibility for configuration, data, training, and acceptance testing.
  • Set cutover criteria and keep a workable fallback until the new path is stable.

Complete cost

Cost drivers for Surcharge Programs

processing not recoverable through a surcharge; registration and operational review; compatible routing and POS software; signage, ecommerce changes, training, monitoring, support, and agreement terms Compare recurring, transaction-based, one-time, optional, and exit costs separately. A proposal is incomplete if it omits equipment ownership, software term, support scope, or cancellation obligations.

Failure planning

Where Surcharge Programs can break down

The highest-risk failures are surcharging debit or prepaid, exceeding an allowed amount, missing notice or signage, disclosing too late, applying inconsistent rules across channels, or assuming the POS can identify eligible cards correctly.

  • Document who detects the problem and who can change the configuration.
  • Keep provider contacts and transaction evidence available.
  • Reconcile after recovery rather than assuming queued or retried activity settled correctly.

Decision guide

Compare Surcharge Programs against the practical alternative

Surcharging requires payment-type eligibility controls that dual pricing and cash discount structure differently. Compare legal and network constraints, customer response, debit share, channel support, operational monitoring, and remaining costs before selecting a model.

Compliance and configuration notice: Pricing-program notice: program treatment depends on the actual posted prices, payment types, checkout behavior, receipts, jurisdiction, card-network rules, processor policy, and provider configuration—not the label used. Requirements can change. Confirm the complete proposed workflow with the provider and qualified legal counsel before launch; this page is not legal advice.

Know before you decide

Limitations and responsibilities

  • The highest-risk failures are surcharging debit or prepaid, exceeding an allowed amount, missing notice or signage, disclosing too late, applying inconsistent rules across channels, or assuming the POS can identify eligible cards correctly.
  • Provider eligibility, features, approval, compatibility, and final terms are not guaranteed.
  • No payment or software configuration removes the merchant's security, reconciliation, training, and dispute responsibilities.

Complete-cost view

What can affect cost

  • processing not recoverable through a surcharge
  • registration and operational review
  • compatible routing and POS software
  • signage, ecommerce changes, training, monitoring, support, and agreement terms

Only a written proposal and agreement can establish actual pricing and terms.

Owner questions

Frequently asked questions

Which tenders require special control in a surcharge program?

The system must distinguish eligible credit cards from debit and prepaid cards, which generally cannot be surcharged under card-network rules. Test debit run as credit, wallets, commercial cards, tips, refunds, and every card-not-present channel.

What should be verified before enabling a credit-card surcharge?

Verify current state and local law, card-network and processor requirements, provider approval, any notices or registration, permitted amount, entrance and checkout disclosures, receipt display, ecommerce treatment, and refund logic. This is operational information, not legal advice.

Why is renaming a checkout fee not enough to make it compliant?

Treatment depends on the actual price presentation, tender identification, amount, timing of disclosure, receipt, and reversal—not the label. A surcharge is distinct from dual pricing and a genuine cash discount and must follow its applicable rules.

Can a surcharge recover every cost of accepting payments?

Not necessarily. Caps, ineligible tenders, customer mix, processing, equipment, software, support, chargebacks, and provider fees can leave costs with the merchant. No complete recovery or savings result is guaranteed.

Related next steps

Sources and review dates

Published 2026-08-03 · Modified

Bring AMP your surcharge programs workflow

Share the current process, the constraint you need to remove, and the systems that must remain. AMP can return a scoped next step without treating a headline rate or feature list as a complete recommendation.

Call AMP

Merchant processing options

Tell us how your business accepts payments

Secure request

Draft saved

Do not submit SSNs, full bank account numbers, passwords, or cardholder data. Information is used to respond to your request.