Blog

The safest way to understand how agents sell dual pricing is to identify the actual pricing model first, verify current state and card-network rules, make customer-facing prices match the POS, test cash, credit, debit, receipts and refunds, train the merchant before launch, and audit the installation after real transactions begin.

A bad dual-pricing installation rarely begins with a defective terminal. More often, it starts because the sales explanation, merchant agreement, pricing display, processor program and POS behavior describe different things.

The salesperson may call the program a cash discount. The terminal may add an amount at checkout. The menu may show only the lower price. The receipt may label the difference a processing fee. Staff may tell customers the bank imposed it. Meanwhile, the processor may have approved a completely different pricing structure.

That mismatch is where complaints, forced reprogramming and merchant distrust begin.

For agents, ISOs, relationship managers and POS resellers, dual-pricing compliance is therefore an implementation discipline, not a terminology exercise. State law determines what a jurisdiction permits. 

Card-network rules control use of the networks. The acquirer can impose additional program conditions. The POS determines what can actually be programmed. Operational controls determine whether the merchant continues using the approved setup after installation.

Those five layers need to align.

How Agents Sell Dual Pricing Without Creating Compliance Problems

The field workflow should begin before a proposal is signed.

1. Identify the pricing model the merchant actually wants: Determine whether the merchant wants two displayed prices, a genuine discount from a standard price, or an additional amount triggered by eligible credit-card use. Do not begin with a product name from a sales sheet.
2. Identify every jurisdiction involved: A single-store restaurant is easier to evaluate than a merchant with locations in four states, an ecommerce store and remote invoicing.
3. Verify current law and regulatory guidance: Check statutes, Attorney General or consumer-protection guidance and relevant court decisions where necessary.
4. Verify current network requirements: Visa and Mastercard do not have identical surcharge rules, and neither should be treated as a substitute for state law.
5. Confirm the acquirer’s approved program: A pricing structure can be lawful in principle and still fall outside the processor’s supported configuration or merchant agreement.
6. Inspect payment mix: A merchant with heavy debit usage has a different operational profile from one receiving primarily commercial credit cards.
7. Confirm card-product recognition: The POS or processing platform needs to distinguish products appropriately where the approved pricing model depends on card type.
8. Decide what customers will see before payment: Menus, shelf labels, estimates, invoices, online product pages and checkout screens matter as much as terminal programming.
9. Program the POS to match that presentation: The advertised transaction must be the transaction the system executes.
10. Install required disclosures: Use the exact requirements applicable to the approved program instead of generic “cash discount” signs purchased from a terminal vendor.
11. Run test transactions: Cash, eligible credit, debit, prepaid where available, refunds, voids and any channel the merchant actually uses should be tested.
12. Inspect receipts: A receipt frequently reveals whether the implementation behaves differently from the pitch.
13. Train the owner or manager: Make sure the merchant understands what the program is and what cannot be changed casually.
14. Train frontline employees: Customers interact with servers, cashiers, service writers and reception staff—not the underwriting department.
15. Audit after launch: Review real transactions during the first week and again after the merchant has operated the program long enough for edge cases to appear.

Agents already accustomed to [treating merchant-services sales as an ongoing advisory and support role] rather than a one-time terminal placement are better positioned for this kind of implementation discipline.

Dual Pricing, Cash Discounts, and Surcharges Are Not Interchangeable

The first compliance problem to eliminate is using these terms as synonyms.

They describe different ways of presenting and applying prices.

This table is an operating framework, not a nationwide legal classification. A state regulator may focus on how prices are advertised and what happens at checkout rather than the label printed on a program brochure.

Dual Pricing

In a true two-price presentation, the customer is shown two prices in advance—for example, a cash price and a card price.

The operational question is not merely whether the terminal can calculate those two prices. It is whether the merchant’s menu, shelf label, service quote or other pricing display communicates them consistently with applicable law and the approved acquiring program.

Dual pricing should never be sold with the blanket statement that it is “always legal.” State pricing rules, consumer-protection law, acquiring requirements and the actual mechanics of the transaction still matter.

Cash Discount

A genuine cash discount begins from the standard price and reduces that price when the customer uses the qualifying form of payment.

Visa’s current public guidance states that a cash discount must be a reduction from the standard price. Its merchant surcharge Q&A also explains that properly structured discount pricing can be presented by showing the card price or by listing card and cash prices side by side.

That is materially different from displaying $100, charging $103 when a card is presented and calling the extra $3 a “cash discount.”

Credit-Card Surcharge

A surcharge is an additional amount associated with the customer’s use of an eligible credit card.

That structure triggers its own set of issues: which card products may be surcharged, how much may be charged, advance notification requirements, customer disclosure, receipt treatment, state restrictions and requirements imposed by the acquirer.

An agent should therefore begin the discovery conversation with transaction mechanics:

What does the customer see before tender is chosen, and what changes when the payment method changes?

That question is much more useful than asking what the vendor calls the program.

What an Agent Must Never Conflate

Several common sales statements create problems because they substitute a shortcut for an actual compliance analysis.

“Dual pricing, cash discount and surcharge are basically the same thing.”

They are not. They can produce different advertised prices, checkout behavior and network obligations. Explain the exact structure being installed.

“Just call the card fee a cash discount.”

The label does not control the substance of the transaction. If an amount is added because a customer selects a credit card, regulators or networks may treat it according to what actually happened.

“Debit is okay if we run it as credit.”

Wrong for surcharge purposes. A debit product remains a debit product even when processed without a PIN or when a terminal presents a “credit” routing option. Visa expressly states that a U.S. merchant may not surcharge a Visa debit or prepaid card merely because “credit” was selected at the terminal.

“The sign makes everything compliant.”

A sign does not repair an incorrect menu, shelf price, online checkout, receipt or POS configuration.

“Every state allows this.”

State law remains relevant, and materially different rules exist among states.

“The POS company handles compliance.”

POS capability is only one layer. The merchant, acquirer and other parties may have obligations that no terminal configuration can satisfy automatically.

“You’ll never pay processing fees again.”

Even where a pricing model shifts some card-acceptance economics to customers, merchants can still incur processor fees, equipment charges, monthly fees, debit costs, chargebacks and other expenses. Economics depend on the contract and tender mix.

“The receipt doesn’t matter if the signs are correct.”

For surcharge programs, both Visa and Mastercard impose receipt-related requirements. A receipt can also reveal that a supposed discount program is actually behaving like an added card fee.

How to Explain Cash Discount vs Surcharge Without Misleading the Merchant

Illustrative merchant explanation — use only when it accurately describes the approved program.

A cash discount and a credit-card surcharge work differently. With a genuine cash discount, the regular price is established first and the customer receives a reduction for using the qualifying payment method. A surcharge starts with the normal or advertised price and adds an amount when an eligible credit card is used.

A two-price program instead presents the applicable cash and card prices before payment. Because state rules and processor programs treat these structures differently, we need to decide which one you are actually installing before we configure the POS, displays and receipts.

The explanation should continue with the merchant’s specific facts: whether debit is included in the pricing presentation, whether ecommerce is involved, what appears on menus or estimates and how the processor has approved the configuration.

Do not simplify the pitch until it changes the underlying meaning.

Credit and Debit Cannot Be Treated as the Same Card Type

One of the most serious implementation errors is assuming that a Visa or Mastercard logo identifies a transaction as credit.

The logo identifies the network. It does not by itself tell the agent whether the underlying product is credit, debit or prepaid.

Visa’s current U.S. guidance states that surcharges may apply only to qualifying credit-card purchases and may not be imposed on Visa debit or prepaid cards. Visa also specifically says that selecting “credit” for a debit card does not transform the card into a credit product.

Mastercard likewise states that its U.S. surcharge permission applies to Mastercard-branded credit cards and that surcharges are not permitted on Debit Mastercard or Mastercard prepaid cards.

That makes card-product identification an implementation issue, not an academic distinction.

If the approved program depends on credit-card eligibility, the agent needs to know:

• how the processor identifies the product;
• whether the POS receives sufficient card-product information;
• whether the pricing logic excludes prohibited products;
• how contactless and mobile-wallet transactions are classified;
• what happens with prepaid cards;
• whether card-not-present channels use the same logic.

Current Visa Surcharge Rules Agents Need to Understand

As of September 2026, Visa’s published U.S. rules and merchant guidance contain several requirements directly relevant to a surcharge installation.

Visa permits surcharging only in circumstances allowed by applicable law and limits U.S. surcharges to eligible credit-card transactions. Debit and prepaid products cannot be surcharged.

Current Visa guidance states that the surcharge may not exceed the merchant discount rate applicable to the surcharged Visa credit transaction or 3%, whichever is lower. That is why agents should not copy the historical 4% Visa limit still found in older payment-industry articles.

Visa also requires the merchant to notify its acquirer in writing at least 30 calendar days before publicly announcing or first assessing a surcharge, whichever is earlier. Visa’s public merchant page likewise tells U.S. merchants to provide their acquirer 30 days’ notice.

Visa’s April 2026 rules require clear and prominent surcharge disclosure at both the point of entry and point of transaction. 

The point-of-transaction disclosure must state the exact amount or percentage, state that the merchant is assessing the surcharge and that it applies only to credit transactions, and state in the U.S. that the amount does not exceed the applicable Visa merchant discount rate. 

Visa specifies channel-specific presentation rules for face-to-face, ecommerce, mail-order and telephone transactions.

For ecommerce, Visa requires disclosure on the first page referencing accepted credit-card brands and again at checkout. The cardholder must have an opportunity to cancel after surcharge disclosure.

Visa also requires surcharge identification on the transaction receipt. Its public reporting page describes the surcharge as appearing separately after the subtotal and before the final transaction amount.

For refunds, Visa’s current rules require the surcharge to be refunded with the transaction; on partial refunds, the surcharge is prorated.

Agents installing an actual Visa surcharge program should work from Visa’s current U.S. merchant surcharge requirements and the acquirer’s program documentation rather than an old sales handout.

Mastercard Surcharge Rules Are Similar in Some Areas, but Not Identical

Mastercard should be evaluated separately.

Its current U.S. merchant guidance permits brand-level or product-level surcharging on qualifying Mastercard credit transactions, subject to its rules and applicable law. Debit Mastercard and Mastercard prepaid products may not be surcharged.

For a brand-level surcharge, Mastercard states that the merchant generally may charge no more than the lesser of its average effective merchant discount rate for Mastercard credit acceptance or Mastercard’s maximum surcharge cap. 

Mastercard’s currently published maximum cap is 4%. Product-level surcharging follows a different cost-based calculation under Mastercard’s rules.

Mastercard also requires advance notice. Its rules require at least 30 days’ written notice to Mastercard and the merchant’s acquirer before surcharging begins. Mastercard maintains a registration process for this purpose.

Customer disclosure is also required. Mastercard’s public guidance requires clear disclosure at the point of interaction and disclosure of the surcharge amount on the receipt.

Mastercard’s current rules further state that when a purchase containing a brand-level or product-level surcharge is fully or partially refunded, the associated surcharge must also be fully or proportionately refunded.

The applicable rule set should be checked directly through Mastercard’s current merchant surcharge rules and registration guidance.

The practical lesson is simple: do not create one “Visa/Mastercard rule” in your installation manual. Maintain separate network references.

A Pending Visa/Mastercard Settlement Is Not Yet a Current Rule Change

Agents also need to distinguish present rules from proposed future changes.

On June 9, 2026, the U.S. District Court for the Eastern District of New York granted preliminary approval to a superseding settlement in the long-running In re Payment Card Interchange Fee and Merchant Discount Antitrust Litigation. 

The settlement proposes changes affecting card acceptance, surcharging and interchange practices. It remained subject to final court approval at the time of this article.

Preliminary approval does not mean every proposed term is already an operative network rule.

Agents should continue using current Visa, Mastercard, acquirer and state requirements unless and until relevant settlement provisions become effective.

State Surcharge Law Differences Can Change the Entire Sales Recommendation

State law can make a program straightforward in one location and unsuitable in another.

A reliable state review should consider:

• the merchant’s physical locations;
• applicable consumer transactions;
• ecommerce and remote-payment circumstances;
• the state’s surcharge statute;
• Attorney General or consumer-protection guidance;
• price-advertising rules;
• restrictions on payment-method fees;
• relevant court decisions.

Connecticut

Connecticut remains a particularly important example because its Department of Consumer Protection expressly distinguishes prohibited surcharges from permitted cash discounts.

Connecticut DCP states that a business generally may not impose an additional charge because a consumer uses one payment method instead of another. It specifically warns that labels such as “transaction fee,” “processing fee” or “non-cash adjustment” can still describe an unlawful surcharge if the transaction operates that way.

The state does permit properly disclosed cash discounts. DCP says an in-person business can satisfy its clear-and-conspicuous disclosure requirement by displaying both cash and credit prices wherever prices are listed, or by visibly posting the specific cash-discount amount or percentage. Online businesses must provide notice in sections where prices appear and at checkout.

That makes Connecticut a useful training example: changing the receipt label does not fix an added payment-method charge.

New York

New York takes a strong price-display approach.

Under current Department of State guidance implementing General Business Law § 518, a business imposing a permitted credit-card surcharge must display the highest total price, excluding sales tax, before the customer incurs the charge.

New York expressly gives examples in which displaying both a cash and credit price is acceptable, as is displaying the higher credit price and advertising a cash discount. Merely posting a register sign such as “4% credit card processing fee” while showing only the lower base price is not the same thing.

For an agent, that means the conversation cannot stop at signage. Menus, price lists, shelf tags and service quotes may need attention.

See New York’s current credit-card surcharge guidance before deploying a New York program.

Massachusetts

Massachusetts remains materially different from states where ordinary credit-card surcharging is permitted.

Massachusetts General Laws Chapter 140D, Section 28A currently states that no seller in a sales transaction may impose a surcharge on a cardholder who chooses a credit card instead of cash, check or similar means. The same statute permits properly disclosed discounts from the regular price designed to induce payment by cash, check or similar methods.

Legislative proposals have been introduced that would change the state’s treatment of surcharging, but pending bills are not current law.

A Massachusetts merchant therefore should not be sold a conventional credit-card surcharge simply because the agent used a nationwide surcharge map that omitted an update.

California

California requires more nuance than the outdated phrase “California bans credit-card surcharges.”

Civil Code § 1748.1 contains surcharge language, but California’s Attorney General explains that a 2018 federal appellate decision prevented enforcement of the statutory prohibition against the merchants involved and that the state generally applies that decision to similarly situated merchants. California still prohibits deceptive or misleading pricing practices.

Separate price-transparency requirements also matter. California’s SB 478, effective July 1, 2024 and later amended for certain food-service businesses, generally requires advertised or listed prices to include mandatory fees. 

The Attorney General’s FAQ says an avoidable credit-card processing fee generally does not have to be included in the advertised price when the customer can avoid it using another payment method, but the treatment differs if card payment is effectively mandatory.

That combination is exactly why agents should research current law rather than repeat a one-line state classification.

State Examples Verified as of September 2026

Verified as of September 2026. Rules can change; current state and acquiring requirements should be checked before installation.

How Agents Should Verify a State

Do not outsource state-law research to a colored map in a sales deck.

Use a repeatable hierarchy:

1. Read the current statute: Confirm that you are looking at the current codified provision rather than an old legislative summary.
2. Check Attorney General guidance: AG offices often explain how consumer-pricing statutes are enforced.
3. Check the consumer-protection regulator: Some states publish practical FAQs that answer questions the statute does not.
4. Review controlling court decisions when they materially affect enforcement: California is an obvious example.
5. Check current network rules: State permission does not override card-brand conditions.
6. Check the acquirer’s program documentation: The processor may support only particular configurations.
7. Escalate unresolved questions: A salesperson should not invent a legal interpretation to save a deal.

Do not treat another agent’s recollection, an old PDF, a processor marketing map or a POS manufacturer’s sales sheet as current legal authority.

Not Every Merchant Is a Good Dual-Pricing Candidate

The right question is not, “Can the terminal do dual pricing?”

It is, “Can this merchant operate the pricing model accurately every day?”

Operational fit is usually stronger where pricing is relatively simple, customer-facing prices are easy to update, the POS supports the approved structure, employees are stable and the merchant is willing to make required menu, shelf or service-display changes.

Merchants with meaningful cash or check usage may also have a clearer economic reason to consider differentiated pricing.

Complexity rises quickly with:

• large retail catalogs;
• ecommerce;
• subscriptions;
• recurring billing;
• locations in multiple states;
• complicated tips;
• large debit-card share;
• marketplace transactions;
• negotiated B2B contracts;
• invoice-heavy operations;
• merchants unwilling to change advertised prices.

Those are not automatically poor candidates. They simply require more design work, and another pricing model may sometimes fit better.

Good merchant qualification is also part of avoiding the broader sales and onboarding mistakes that can damage long-term merchant relationships.

The Dual-Pricing Installation Checklist Agents Should Use Before Go-Live

Before Programming

Confirm all of the following:

• the actual program type;
• merchant states and jurisdictions;
• processor/acquirer approval;
• POS model and software version;
• tender types accepted;
• card-product identification;
• ecommerce or card-not-present channels;
• recurring transactions;
• existing advertised prices;
• merchant agreements or customer contracts that may affect pricing.

If a merchant operates several systems—counter POS, online ordering, invoicing and recurring billing—do not assume one configuration applies to all four channels.

Price Configuration

Test how the software calculates:

• cash price;
• card price;
• posted base price;
• sales tax;
• gratuity;
• discounts;
• coupons;
• refunds;
• voids;
• partial refunds.

Tax treatment should be confirmed for the jurisdiction and pricing model involved. Do not assume that tax is always calculated before or after a price differential in the same manner.

Customer-Facing Display

Walk the customer journey.

Inspect:

• entrance;
• register;
• printed menu;
• digital menu;
• shelf;
• service board;
• estimate;
• invoice;
• online product page;
• shopping cart;
• checkout page.

What the merchant advertises needs to reconcile with what the POS eventually charges.

Transaction Testing

Run or simulate transactions using the payment channels the merchant will actually accept:

• cash;
• eligible credit;
• debit;
• prepaid if possible;
• refund;
• void;
• partial refund;
• tipped purchase;
• keyed transaction;
• ecommerce transaction;
• recurring transaction where applicable.

Save representative receipts with the installation documentation.

Signage Alone Does Not Fix a Bad Price Display

A merchant can have a perfectly designed sign beside the register and still have a defective implementation.

Different customer-facing surfaces perform different jobs.

Entrance signage may satisfy a network requirement for a surcharge program.

Checkout disclosure tells the customer what happens at payment.

Shelf labels and menus establish the prices customers rely on while deciding what to buy.

Service menus, quotes and estimates can become the customer’s expected transaction price.

Online product pages and carts influence what the customer believes an online purchase will cost before authorization.

The field audit should therefore ask:

• Does the customer know the applicable price before choosing payment?
• Does that displayed price match the POS?
• Are two prices displayed wherever the relevant state requires them?
• Does the printed menu match the digital menu?
• Do shelf labels reconcile with checkout?
• Does the ecommerce flow disclose the applicable price before authorization?
• Have obsolete signs from a previous program been removed?

Do not create “universal” signage language from scratch. Visa, Mastercard, states and acquirers can impose different disclosure content and placement requirements.

For example, Visa’s current surcharge rules include detailed point-of-entry and point-of-transaction requirements, including channel-specific minimum presentation standards.

That level of specificity is another reason not to substitute a generic “3% non-cash adjustment” sticker for an actual program review.

Receipt Formatting Must Match the Program the Agent Sold

Receipts are where hidden contradictions become visible.

Suppose the sales pitch described a cash discount. The menu displays $20. The terminal charges $20.60 to a card. The receipt shows:

• Subtotal: $20.00
• Processing Fee: $0.60
• Total: $20.60

That receipt deserves immediate review because the mechanics may not match the pricing model described to the merchant.

For an actual surcharge program, Visa requires the surcharge to be clearly disclosed on the transaction receipt, and Mastercard likewise requires receipt disclosure of the surcharge amount.

There is no single receipt design that agents should treat as universally correct for every dual-pricing or cash-discount program.

The safer approach is conceptual consistency:

Two-price example

• Item/card price: $20.60
• Cash discount when applicable: reflected consistently with the approved structure
• Final tender amount: matches the price the customer was shown

Surcharge example

• Purchase subtotal
• Clearly identified eligible credit-card surcharge
• Final total

The precise formatting should follow current network, acquirer and legal requirements for that program.

Menu, Shelf, Service and Ecommerce Pricing Need Separate Review

Restaurants

A restaurant installation requires more than terminal configuration.

Check printed menus, QR-code menus, ordering tablets, menu boards and online ordering platforms. Then test what happens when tax and gratuity are added.

Servers need a short, accurate explanation. They should not be forced to interpret payment law at the table.

A restaurant whose terminal displays two prices but whose menu shows only a lower amount may still have a serious price-disclosure problem, particularly in states such as New York where the displayed highest card-inclusive price is central to compliance.

Retail

Retail can be operationally harder because the number of SKUs multiplies the opportunity for mismatch.

Inspect:

• shelf strips;
• price stickers;
• promotional signage;
• sale prices;
• coupon treatment;
• customer-facing displays;
• scanned prices.

A dual-pricing system that calculates two totals internally does not automatically correct hundreds of old shelf tags.

Service Businesses

For salons, repair businesses, contractors and professional services, the customer often sees pricing through:

• service menus;
• estimates;
• quotes;
• work orders;
• invoices.

If a customer approves a $500 estimate and the payment screen later produces $515 without a structure that was properly disclosed and permitted, the problem began before the card was tapped.

Ecommerce

Online programs need their own checkout review.

Inspect:

• product page;
• cart;
• payment-method selection;
• checkout;
• authorization screen;
• confirmation;
• receipt.

Visa’s current surcharge rules expressly address ecommerce disclosures and require an opportunity to cancel after surcharge disclosure.

Do not assume that an in-store signage package makes the ecommerce implementation compliant.

Merchant Education at Signing Prevents Problems the Terminal Cannot Fix

Merchant education at signing is not paperwork. It is implementation training.

Before go-live, the merchant should understand:

• which pricing model has been approved;
• what terminology accurately describes it;
• how cash and card pricing operate;
• how credit differs from debit;
• which state-specific limitations apply;
• what signs or price displays must remain in place;
• what appears on receipts;
• how refunds work;
• how voids work;
• how tips are handled;
• where tax treatment must be confirmed;
• whether online transactions use the program;
• what happens when prices change;
• why employees need consistent explanations;
• whom to call before changing the configured percentage.

The salesperson should also make clear which issues belong to state law, which belong to card-network rules and which are simply processor-program requirements.

That prevents the common merchant reaction six weeks later: “I thought your processor handled all that.”

Documenting the Installation

Where appropriate, retain an acknowledgment containing:

• program type;
• pricing model;
• merchant state;
• configured rate or price differential;
• signage or disclosure materials provided;
• installation date;
• training completed;
• receipt test completed;
• credit/debit test completed;
• merchant approval.

A signed document does not waive a state statute, network rule or merchant agreement.

Its value is operational. It records what the merchant was trained to use.

Give Employees One Accurate Explanation, Not Five Improvised Ones

Frontline staff can undo a technically correct installation in one sentence.

Illustrative customer-facing language — use only when it matches the merchant’s approved pricing model.

For a true two-price presentation:

“We display both payment prices. The cash price is lower, and the card price is the amount shown for paying by card.”

For a genuine cash discount:

“The listed standard price applies, and we provide the posted discount when you use the qualifying payment method.”

For an approved credit-card surcharge:

“We apply the disclosed surcharge to eligible credit-card transactions. It does not apply to debit or prepaid cards.”

Do not teach employees to disguise a surcharge as a:

• technology fee;
• non-cash adjustment;
• admin fee;
• service charge;
• convenience fee

simply because those words seem less objectionable.

The name cannot be used as a workaround for transaction mechanics.

Customer Reactions Should Be Managed With Clarity, Not Promises

Customers can respond in several ways.

Some will pay without comment. Some will choose cash. Some will ask why two prices exist. Some will complain about the higher amount. Others may believe a charge appeared unexpectedly because they noticed it only when the receipt was printed.

Do not promise merchants that customers “won’t care” or that complaints disappear after a week.

A better preparation conversation is:

• make the price visible;
• make employee explanations consistent;
• avoid surprise changes at checkout;
• give staff a method for escalating complaints;
• monitor what customers are actually saying.

Price transparency cannot guarantee acceptance, but it removes avoidable confusion.

The First 30 Days Matter More Than the Sales Presentation

Closing the merchant is the beginning of the implementation, not the end.

Day 1

Verify:

• entrance and checkout disclosures;
• menu or shelf pricing;
• POS settings;
• receipt output;
• cash transaction;
• credit transaction;
• debit transaction.

Fix any mismatch before the merchant processes significant volume.

Week 1

Ask about:

• customer questions;
• staff explanations;
• refund behavior;
• overrides;
• incorrectly classified transactions;
• complaints;
• discrepancies between channels.

Review several real receipts rather than relying only on the installation test.

Day 30

Revisit:

• merchant satisfaction;
• complaint volume;
• changes to pricing;
• whether signs remain in place;
• processor notices;
• debit handling;
• support tickets;
• staff turnover;
• whether the merchant has changed menus or online prices;
• requests to modify the program.

A good local agent’s advantage is often continuing support rather than the ability to make the initial sale, which is why post-sale merchant support and relationship building] belong in the operating model from the beginning.

The Failures That Cause Reprogramming, Complaints, and Merchant Churn

Pricing mistakes do not all produce the same consequence. Depending on the circumstances, the response might be a customer complaint, correction request, reprogramming, feature disablement, acquirer compliance action or termination.

Agents should focus on finding the error early rather than exaggerating what will happen.

Surcharge Applied to Debit

What went wrong: The pricing logic treated every Visa or Mastercard card as eligible credit.

How to catch it: Test known debit products and inspect transaction classification.

Correction: Stop the improper application and have the processor correct the card-product logic.

Prepaid Card Treated as Surchargeable Credit

What went wrong: Prepaid was not excluded.

How to catch it: Review processor configuration and test prepaid products when practical.

Correction: Confirm current network treatment and update the POS/acquirer configuration.

Added Fee Called a Cash Discount

What went wrong: The displayed price stayed low while a card-triggered amount was added later.

How to catch it: Compare menu or shelf price with receipt mechanics.

Correction: Rebuild the pricing display and transaction logic so the approved model is accurately represented.

Wrong State Configuration

What went wrong: A program developed for one jurisdiction was installed elsewhere.

How to catch it: Include state verification in underwriting and deployment records.

Correction: Review current state law before continuing the pricing program.

Outdated Network Percentage

What went wrong: The salesperson used an old surcharge cap from historical materials.

How to catch it: Compare configuration with current Visa and Mastercard requirements.

Correction: Recalculate based on current card-brand and merchant-cost limitations.

Missing Required Notice

What went wrong: Required acquirer/network notification was never completed.

How to catch it: Make notification confirmation a pre-launch field.

Correction: Follow the current network and acquirer process before implementation continues.

Menu Shows Only the Lower Price

What went wrong: POS logic changed, but customer-facing pricing did not.

How to catch it: Perform a physical walk-through.

Correction: Update the price presentation according to applicable law and program design before go-live.

Shelf Tag Does Not Match Checkout

What went wrong: The software was changed without a merchandising update.

How to catch it: Randomly scan representative SKUs.

Correction: Synchronize shelf and transaction pricing.

Ecommerce Difference Appears Too Late

What went wrong: Disclosure occurs only after the customer has effectively committed to payment.

How to catch it: Complete the full checkout path as a customer.

Correction: Move disclosures and pricing presentation to the required stage.

Receipt Contradicts the Program

What went wrong: The receipt labels an added amount that was described as something else.

How to catch it: Save sample receipts from each tender type.

Correction: Fix both programming and merchant-facing documentation.

Merchant Changes the Percentage Manually

What went wrong: The merchant assumes the configured amount is a freely adjustable markup.

How to catch it: Compare current settings with installation records.

Correction: Restore an approved configuration and retrain management.

Staff Gives a Misleading Explanation

What went wrong: Employees invent their own description.

How to catch it: Ask staff how they explain the price difference.

Correction: Give them one approved, plain-language script.

Merchant Removes Signs

What went wrong: The installation was compliant only on launch day.

How to catch it: Review photos or revisit the location.

Correction: Restore required disclosures immediately.

Refund Logic Is Wrong

What went wrong: The original surcharge or price difference is not handled according to the program and applicable rules.

How to catch it: Test full and partial refunds.

Correction: Work with the processor to configure the approved refund behavior.

Unsupported Recurring Transactions

What went wrong: The merchant expands an in-person program into recurring billing without reviewing authorization, disclosure and system support.

How to catch it: Ask about every payment channel during onboarding and periodic reviews.

Correction: Remove unsupported transactions from the program until the acquirer confirms an approved structure.

A Convenience Fee Is Not a Backup Name for a Surcharge

When an agent discovers that surcharging is restricted, the solution is not to rename it a convenience fee.

Visa’s rules treat convenience fees as a separate construct. In the U.S., Visa describes a convenience fee as payment for a bona fide convenience represented by an alternative payment channel outside the merchant’s customary payment channel, rather than a fee charged solely for card acceptance. Visa’s public guidance also states that a convenience fee generally must be a flat amount rather than a percentage.

The exact requirements depend on the network and merchant circumstances.

The safe sales principle is straightforward: a convenience fee should be sold only when the approved program actually satisfies convenience-fee requirements.

Changing the Label Does Not Necessarily Change the Transaction

“Non-cash adjustment” is perhaps the clearest example of why agents should focus on mechanics.

Connecticut’s Department of Consumer Protection specifically notes that charges described as a “transaction fee,” “processing fee” or “non-cash adjustment” can constitute a prohibited surcharge when an amount is added because of payment method.

A regulator or network may ask:

• What price was advertised?
• What did the consumer see before payment?
• What payment method triggered the additional amount?
• Was the customer offered a true discount?
• What did the receipt show?

The descriptor alone does not answer those questions.

That principle also applies to “technology fee,” “administrative fee” and “service charge.” Those labels may describe legitimate fees in other contexts, but they should not be used to disguise a payment-method surcharge.

Refunds and Voids Need Their Own Test Plan

Refund testing belongs on the installation checklist because real merchant operations are messier than a single completed sale.

Test:

• full refund;
• partial refund;
• same-day void;
• return from a dual-price transaction;
• return from a surcharge transaction;
• tip adjustment where applicable.

For an actual Visa U.S. credit-card surcharge, Visa’s current rules require a full surcharge refund when the purchase is fully refunded and a prorated surcharge refund on a partial refund. Mastercard likewise requires its brand- or product-level surcharge to be fully or proportionately refunded with the transaction.

For dual-pricing or discount programs, use the processor’s approved implementation rather than inventing a refund formula at the counter.

The receipt from the refund should also be reviewed. Refund logic that only works in the processor’s back office but produces confusing customer documents can still generate disputes.

Compliance Protects Residuals by Protecting the Merchant Relationship

Residual income depends on an active merchant relationship.

That makes compliance operationally relevant to the agent’s book, but the order matters: transparency protects the merchant first; durable residuals are a consequence of maintaining a useful, trusted relationship.

Accurate implementations tend to produce:

• clearer expectations;
• fewer “you never told me that” calls;
• fewer emergency reprogramming requests;
• less confusion over debit transactions;
• fewer pricing surprises;
• more confidence in the agent’s advice;
• less incentive for the merchant to replace the provider after a complaint.

A merchant who understands what was installed is also more likely to call before changing it.

That gives the agent an opportunity to review a proposed ecommerce channel, new location or pricing change before it creates a problem.

What Not to Do for Residuals

Short-term selling tactics can create long-term attrition.

Do not:

• hide how the pricing model works;
• use vague terminology because the accurate term sounds harder to sell;
• tell merchants “everyone does this”;
• rush an installation before prices are updated;
• ignore state differences;
• leave employees untrained;
• blame the processor when the original pitch was inaccurate;
• promise “zero processing cost”;
• discourage merchants from reading disclosures.

Residuals become fragile when the merchant’s understanding of the deal differs from the actual transaction.

A smaller portfolio of merchants who understand and trust their setup can be more durable than a larger book built on aggressive claims and emergency reprogramming.

Four Hypothetical Field Scenarios

Scenario 1 — Restaurant Menu Mismatch

A restaurant has a POS correctly configured to display two payment prices at checkout. Its printed menu, however, shows only the lower cash figure.

This is not automatically cured by a sign beside the register.

The agent should inspect the state’s price-display requirements, the acquiring program and the merchant’s full menu environment. In New York, for example, current guidance centers on displaying the highest credit-card-inclusive price or both prices before purchase rather than merely announcing a later percentage fee.

The launch should be delayed or corrected until the restaurant’s menus, digital ordering surfaces and POS presentation agree.

Scenario 2 — Debit Card Problem

A retailer asks the agent to apply 3% to “every Visa and Mastercard.”

The agent should stop there.

Network logo is not card type. Visa and Mastercard both prohibit applying their U.S. credit-card surcharge rules to their debit and prepaid products.

The correct next question is whether the processor and POS can identify eligible products and exclude ineligible ones.

Scenario 3 — Multi-State Merchant

A repair chain operates stores in Connecticut, New York and Massachusetts.

The owner wants one configuration, one sign and one staff script.

That assumption is unsafe.

Connecticut generally prohibits payment-method surcharges while permitting qualifying cash discounts; New York permits surcharging subject to its price-display requirements; Massachusetts currently retains a statutory credit-card surcharge prohibition.

The program should be designed location by location rather than copied across the portfolio.

Scenario 4 — Staff Misrepresentation

A customer asks why the card total is higher.

The employee says:

“The bank charges this fee, not us.”

If the merchant is actually imposing the charge, that explanation is misleading.

The agent should retrain staff to describe what the merchant’s approved program actually does without assigning responsibility to a bank or network that did not impose the customer-facing fee.

Common Agent Mistakes

Several errors appear repeatedly because they make the sales process easier in the moment:

• Calling every program cash discount: Start with mechanics, not the vendor label.
• Using an old state surcharge map: State statutes, enforcement guidance and court decisions change.
• Treating signature debit as credit: Transaction routing does not change the underlying card product for surcharge eligibility.
• Using an outdated surcharge cap: Visa currently uses a 3% ceiling subject to the lower merchant-cost limit, while Mastercard currently publishes a 4% maximum subject to its cost rules.
• Failing to verify processor support: A technically possible POS feature may not be an approved acquiring program.
• Installing signs without inspecting prices: The rest of the customer journey still matters.
• Ignoring receipts: Receipts often reveal whether the actual transaction matches the pitch.
• Forgetting ecommerce: Online disclosures can have their own network and state requirements.
• Ignoring subscriptions: Recurring billing introduces authorization and price-consistency issues that an in-person installation may not address.
• Skipping staff training: Employees will create their own explanations when none is supplied.
• Promising zero processing cost: It is more accurate to explain the merchant economics of the approved program.
• Failing to retest after a price change: Menu updates, new promotions and POS migrations can break an implementation that was correct on launch day.

Myth vs Reality

FAQ

Selling Dual Pricing Responsibly Is an Implementation Discipline

How agents sell dual pricing successfully has much less to do with quoting a percentage than with making every part of the merchant’s operation tell the same story.

The sales explanation should match the legal environment. The program documentation should match network and acquirer rules. The merchant’s menu, shelves, estimates and online prices should match what the POS charges. Receipts should match the program. Employees should know how to explain it. Debit, refunds and edge cases should be tested rather than assumed.

When those elements align, the merchant receives a transparent payment-pricing system instead of a compliance problem disguised as a feature.