Compliance for Agents: What You Cannot Say in a Pitch

Most agents who cross a compliance line do not know they have. The prohibited statements are not exotic; they are the ordinary reassuring things a salesperson says to move a hesitant merchant along, and several of them sound like good service. That is what makes them worth learning as a list rather than as a principle.

The rules exist because an agent speaks for the acquiring bank whether or not either party thinks of it that way, and a promise made in a car park is a promise the bank is on the hook for.

You cannot promise approval

Not "you're approved," not "this is a formality," not "I've never had one turned down," not "don't worry, you'll get it." Underwriting makes the decision and an agent has no authority to make it in advance.

The variants are what catch people. "You'll be fine" is a promise. "I can't see any reason they'd say no" is a promise wearing a hedge. So is describing an application as a formality, or telling a merchant to go ahead and order signage. If a merchant would reasonably hear the decision as already made, it is a promise.

What you can say is what happens next: here is what underwriting reviews, here is what they will ask for, here is what I need so nothing is asked for twice.

You cannot promise a funding time

This is the most commonly broken rule in the industry because merchants ask directly and the answer feels harmless. It is not. Funding timing depends on batch timing, the bank, the day of the week, holidays, and risk review, and none of those is under an agent's control.

"Next business day" as a guarantee is the specific phrase to avoid, including the softer forms: "you'll have it tomorrow," "it's next day," "money hits Tuesday." Describing how settlement generally works is fine. Committing to a date is not, and a merchant who planned payroll around your answer and did not get it has a grievance with a bank rather than with you.

You cannot present yourself as the bank

An agent represents a program that operates through an acquiring bank. Saying "we're the bank," "we underwrite in house," or "we hold your funds" misdescribes the arrangement, and in some framings misdescribes a regulated activity.

Related and just as common: implying a merchant's funds are insured in a way they are not, or that the relationship is a banking relationship. Be plain about what you are. Merchants do not care as much as agents fear, and the ones who do care would rather be told.

You cannot manufacture endorsement

Two forms. The first is implying an association that does not exist, that a card network endorses your program, that a trade association recommends you, that a supplier has partnered with you when they have not.

The second is subtler and more common: using another company's marks to suggest sponsorship. Card network logos are governed by rules about acceptance marks and how they may be displayed, and an agent decorating a proposal with them to look official is misusing them. The same applies to naming recognisable customers without permission.

Rates, and the disclosure that travels with a claim

You may quote what you are authorised to quote, and you must quote it completely. Two failures recur.

• Quoting a percentage without the per-transaction amount. On a small-ticket merchant the fixed piece is most of the cost, and a percentage alone is not the price.
• Quoting one rate for a business with two. A merchant who takes both card-present and card-not-present payments has two rates, and presenting one as though it covers everything is a misquote even when the number is accurate.

The other half is the conditional fees. Where a claim like "no monthly fee" is made, the conditions that could produce one travel with it, in the same document, visible. A footnote in a file the merchant does not have is not a disclosure. This is why the disclosure is attached to the claim as a single component rather than left to whoever assembles the proposal.

Things that sound compliant and are not

• "Guaranteed savings." You cannot guarantee a figure that depends on a mix you do not control and a future you cannot see.
• "No contract" where a term or an equipment lease exists somewhere in the arrangement.
• "Free terminal" where the cost is recovered elsewhere. Free has a meaning.
• "We'll beat any rate." Unbounded and unkeepable, and it invites a merchant to test it.
• "Cancel anytime with no fees" without having read the schedule you are describing.

Why this is self-interested rather than imposed

It is tempting to read all of this as the compliance department making selling harder. The reverse is closer to true.

Every prohibited statement above is a claim you cannot keep, and the moment it fails, it fails in front of the merchant whose residual you were counting on for years. An agent who promised two-day approval and delivered three weeks has not just lost trust on that point; they have made every other thing they said negotiable. Precision about what you control and honesty about what you do not is the thing that survives the first delay, and the first delay always comes.

Optional add-ons and conditional fees are separate: the subscriptions module ($49/mo) bills only if you turn it on; processor-required fees apply only if triggered — e.g., $19.95/mo if the annual PCI security check isn't completed (we walk you through it in ~5 minutes), $25/mo if over 10% of card-present transactions are non-EMV. Full fee schedule shown before you sign.