The Practitioner Answer: It's the Merchant's Responsibility
CCSalesPro's own framing on this is explicit: any dual-pricing pitch content must make clear that the merchant, not the ISO or agent, bears legal responsibility for state-specific pricing-disclosure compliance. That is a practitioner-source position, not a court ruling, but it comes from the closest thing this niche has to a dominant training voice, and it lines up with how pricing-disclosure law is actually written: the laws in this research (state surcharge restrictions, New York's total-price rule, the Visa receipt and notice rules) regulate what a merchant discloses to its own customers, which is a decision the merchant, not the agent who sold them the processing relationship, ultimately controls and executes.
Why That Doesn't Mean an Agent Is Off the Hook
"The merchant is legally responsible for their own disclosure" does not mean an agent who gives bad advice, or actively encourages a merchant into a non-compliant setup, has no exposure at all. Reputational risk, relationship risk, and the practical fallout of a merchant getting hit with a compliance complaint they were coached into are all real, even where the strict legal liability sits with the merchant. An agent who wants a durable book of business treats the merchant's compliance seriously, not because the agent is the named defendant if something goes wrong, but because a merchant who gets burned does not stay a merchant for long, and attrition is already the chronic pain point in this niche.
Two Different Compliance Questions, Often Conflated
This is the distinction that matters most and gets blurred constantly. Question one: is the merchant's own pricing disclosure to their customers compliant with their state's dual-pricing or surcharging rules? That sits with the merchant, per CCSalesPro's framing. Question two: was the outreach that reached the merchant in the first place, the call, text, or voicemail drop that led to the sales conversation, itself TCPA-compliant? That is a completely separate question, and it does not transfer to the merchant at all. The party who ran that outreach, whether an agent, an ISO, or an outsourced calling or texting vendor, is the one holding that exposure, the exact exposure the NRS Pay case demonstrates.
What a Responsible Agent Still Does
Even with the legal line drawn the way CCSalesPro draws it, a few practices keep an agent on solid ground. Don't position yourself as the merchant's compliance advisor or attorney; point them toward their own counsel or a resource like the state-by-state guide on this site for the specifics. Document that pricing decisions, and the specific structure chosen (dual pricing vs surcharging), were the merchant's own call, not something the agent dictated. And separately, keep your own outreach practices (consent records, DNC scrubbing, channel choice) clean on their own terms, since that liability does not move to the merchant no matter how the pricing-disclosure question resolves.
How VA Horizon Draws This Line
VA Horizon's own role in this niche is getting an ISO or agent in front of a qualified, double-confirmed merchant meeting, not advising either party on pricing-disclosure law. Our compliance responsibility is the conversation we run to get that meeting booked: every SMS exchange happens through Human + AI SDRs on the VA Horizon Private CRM, with a full transcript behind it, which is exactly the kind of documented consent record the TCPA exposure in this niche turns on. What the agent and merchant discuss and agree to about pricing structure after that meeting is between them, the same separation CCSalesPro's framing describes.
What this means for you
- CCSalesPro's explicit position: the merchant, not the ISO or agent, bears legal responsibility for state-specific pricing-disclosure compliance.
- That does not eliminate an agent's reputational and relationship risk from bad pricing advice, especially given how attrition-sensitive this niche already is.
- Pricing-disclosure compliance (the merchant's responsibility) and outreach compliance under TCPA (the caller or texter's responsibility) are two separate questions, frequently conflated but not the same liability.
- The outreach-compliance exposure does not transfer to the merchant. It sits with whoever ran the call, text, or voicemail campaign that generated the meeting.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- CCSalesPro, the case for dual pricing: understanding Visa compliance
- classaction.org, NRS Pay TCPA settlement coverage (Walston v. National Retail Solutions, Inc.)