What an ISO Agreement Actually Commits You To

The agreement a funding source sends when you sign on as an ISO is usually short, arrives as a PDF, and gets skimmed for one number. Then it sits in a folder until something goes wrong.

It is worth more attention than that, because a handful of its clauses decide things that matter far more than the split: whether your clients remain yours, what happens if a deal defaults, and what you are personally on the hook for.

This is general commentary, not legal advice. Terms vary substantially between funding sources, and an agreement that governs how you get paid is exactly the kind of document worth having a lawyer read before you sign it. What follows is a guide to where to look, not a substitute for that review.

Who owns the client

The most consequential clause in most ISO agreements has nothing to do with money.

Look for language about solicitation, exclusivity, and what happens to a merchant after they fund. Some agreements are clear that the merchant remains your relationship and renewals route back through you. Others reserve the right for the funder to contact the merchant directly, renew them directly, and pay you nothing on the renewal — or a reduced amount, or a reduced amount for a limited window.

This matters enormously, because in this business renewals are where the money is. An arrangement where you source a client, get paid once, and then watch the funder renew them three times without you is not a partnership. It is a one-off referral dressed as a partnership.

Read specifically for: how long your claim on the merchant lasts, whether it survives if the merchant goes quiet for a period, and whether it survives termination of the agreement itself.

What happens on default

There is usually a clawback provision, and its shape varies more than people expect.

The common version: if a deal defaults inside some early window — often measured in the first handful of payments — some or all of your commission is returned. That is a reasonable protection for a funder against files that were never going to perform.

What to look at closely:

• The window. A short one is normal. A long one shifts real credit risk onto you.
• Whether it is partial or total. Pro-rated against payments actually received is very different from all-or-nothing.
• What triggers it. Default is one thing. Some agreements trigger on first missed payment, or on the merchant closing their account, or on any "breach" by the merchant — which is much broader.
• How it is collected. Netted against future commissions is survivable. A demand for repayment regardless of whether you have future commissions is a cash-flow event.

Representations you are making about the file

Buried in most of these agreements is a set of representations — statements you are warranting to be true about every deal you submit.

Typically: that documents are authentic and unaltered, that you have disclosed known existing positions, that you have not misrepresented the merchant's circumstances, and that you have the merchant's authorization to submit their information.

These are reasonable, and you should be able to sign them honestly. The point of reading them is to know what standard you are being held to — because if a submitted file turns out to contain a doctored statement, the representation you signed is what converts that from the merchant's problem into yours.

It is also why "the client sent me what they sent me" is a weaker position than most new brokers assume.

Indemnification and personal guarantees

Two things worth finding before you sign.

The indemnity clause sets out what you are covering the funder for. Indemnifying against your own misconduct or misrepresentation is standard. Indemnifying against anything arising from a submitted deal — including the merchant's conduct, which you do not control — is much broader, and worth negotiating or at least understanding.

A personal guarantee from you individually, if present, means your LLC is not the shield you may assume it is. Not every ISO agreement has one. It is worth knowing which kind you signed, because the answer changes what a bad file can cost you.

Exclusivity and submission restrictions

Some agreements restrict shopping the same file elsewhere while it is under review, or for some period after a decline. Some restrict it more broadly.

Both are worth knowing, and the narrow version is usually fine — submitting one file to six desks at once damages your standing with all of them anyway. The point is to know the rule you agreed to rather than discover it when a funder objects.

Termination and what survives it

Finally: how either side ends the relationship, on what notice, and what continues afterwards.

Commission on already-funded deals should survive termination. Renewal rights may or may not. Clawback obligations almost always do. Non-solicitation of merchants sometimes extends past the end of the agreement, which can quietly restrict your ability to keep serving clients you brought in.

The practical version

You will not negotiate most of these as a new ISO, and that is normal. The point is not to win every clause — it is to sign knowing which ones you accepted.

Three things worth doing regardless of size:

1. Keep every executed agreement in one place, current and complete. You will need to know what you agreed to, per funder, on the day something goes wrong.
2. Track the differences. Clawback windows and renewal rights vary by funder, and that variation should inform where a file goes.
3. Have counsel read the first few. Not every one forever — the first few, so you learn what normal looks like and can spot what is not.

The operators who get hurt by these agreements are rarely the ones who negotiated badly. They are the ones who never read past the split.