Independent Sales Organizations (ISOs) play a key role in the payment processing industry. They connect merchants with processors and acquiring banks, help onboard businesses, and generate revenue through ongoing residual payments.

But not all ISOs operate the same way.

One of the most important decisions when launching or scaling an ISO is whether to operate as a retail ISO or a wholesale ISO. This is often framed as a business decision—but in reality, it is a legal one.

The structure you choose affects how risk is allocated, who bears responsibility for merchant activity, and how liability may arise if something goes wrong.

How Courts View the Role of an ISO

Courts consistently describe ISOs as intermediaries rather than financial institutions.

In Process America v. Cynergy Holdings, the court explained:

“An ISO’s primary role is to solicit new merchants and then provide first-line customer support.”

At the same time, ISOs operate within a system controlled by processors and acquiring banks. ISOs are often involved in facilitating contracts for credit card processing services, including negotiating pricing, monitoring fraud, and supporting merchants.

This dual role—sales-driven but contract-bound—defines how courts analyze ISO liability.

Retail ISO: Control Comes With Responsibility

A retail ISO works directly with merchants. It sources business, manages onboarding, and maintains ongoing relationships.

This model offers a high level of control. The ISO decides which merchants to bring in, how they are onboarded, and how the relationship is managed over time. From a business perspective, this can create a more stable and predictable portfolio.

But legally, that control comes with exposure.

Because the retail ISO interacts directly with merchants, it is often the first point of scrutiny in disputes involving misrepresentation, fraud, or improper onboarding. If a merchant claims they were misled or improperly enrolled, the retail ISO is typically the party closest to that conduct.

Wholesale ISO: Scale Through Networks, Risk Through Supervision

A wholesale ISO operates by building and managing a network of agents or sub-ISOs, rather than working directly with every merchant. This structure allows for rapid growth, as merchant acquisition is distributed across multiple independent channels.

However, this model shifts the nature of legal risk.

Even where the wholesale ISO does not directly interact with merchants, courts may still impose liability based on failure to supervise, control, or respond to misconduct within the network. The use of agents does not insulate the organization from responsibility—particularly where the ISO benefits from the conduct and retains some level of oversight.

In Matter of People of the State of New York v. Northern Leasing Sys., Inc., the court found liability based on:

“[…] respondents’ failure to oversee the Independent Sales Organizations, the forgeries, material misrepresentations […]”

The court further concluded that this structure “created an enterprise conducive to fraud.”

This reflects a broader legal principle: when an ISO builds a network-driven model, it must also implement meaningful oversight. Without it, the same structure that enables scale can expose the ISO to significant liability.

Agency Law: Why Control Matters

The legal relationship between an ISO, its agents, and other parties is often analyzed under agency law. In this context, the key issue is not how the relationship is labeled, but how it actually functions.

Courts focus on control.

As explained in Westmas v. Creekside Tree Serv., Inc.:

“Agency” is defined as the fiduciary relation which results from the manifestation of consent by one person to another that the other shall act on his behalf and subject to his control, and consent by the other so to act”.

And more specifically:

“An important factor in determining whether a person is an agent is the extent of control retained over the details of the work.”

This has practical consequences for ISOs. Even when individuals are described as independent contractors, an agency relationship may still exist if the ISO retains meaningful control over how work is performed.

In that case, liability can extend beyond the individual actor and reach the ISO itself.

For wholesale ISOs in particular, this means that growth through agents must be paired with clear supervision, defined responsibilities, and enforceable compliance standards.

Fraud Risk and Enforcement Exposure

Fraud and deceptive practices remain one of the most significant legal risks for ISOs, particularly where merchant acquisition is driven by aggressive sales practices or poorly supervised agents.

Regulators and courts do not focus only on individual misconduct—they examine whether the business structure itself enabled or failed to prevent fraud.

This is illustrated in Matter of People of the State of New York v. Northern Leasing Sys., Inc., where the court found that ISOs “misrepresented to those consumers the nature and terms of the EFLs” and, in some cases “forged the names of consumers or unilaterally altered the terms of the EFLs after they were signed.”

Importantly, the court did not treat these actions as isolated incidents. Instead, it focused on the broader system, concluding that the failure to supervise ISO activity contributed to widespread misconduct.

This reinforces a key point for both retail and wholesale ISOs: fraud risk is not limited to direct actions—it includes how the business is structured, how agents are managed, and whether adequate safeguards are in place.

Without proper oversight and compliance controls, an ISO may face not only contractual disputes, but also regulatory enforcement and significant liability.

Contracts Still Define the Business

Regardless of whether an ISO operates under a retail or wholesale model, its rights and obligations are ultimately defined by contract.

Processor and acquiring bank agreements determine key issues such as ownership of the merchant portfolio, entitlement to residual payments, transfer rights, and termination conditions. Courts consistently enforce these agreements according to their plain terms.

In Process America v. Cynergy Holdings, the court emphasized that:

“Cynergy “owns” the merchant agreements, and Process America’s “ownership” of the merchant agreements “will vest” only if certain contractual conditions are satisfied.”

Even where an ISO builds and services the merchant relationship, its ability to control or transfer that portfolio may be limited. The court further noted that:

“Section 2.6.B enumerates three conditions that must be satisfied before any transfer may take place […]”.

This highlights a critical reality of the ISO business model: the economic value of an ISO is not determined solely by its operations, but by the terms of its agreements.

Choosing the Right Structure

The choice between retail and wholesale ISO models depends on business goals—but must be evaluated through a legal lens.

A retail ISO may offer greater control and a more contained risk structure, while a wholesale ISO can enable faster scaling through a network of agents. However, each model carries different legal implications in terms of liability, supervision, and compliance.

Dilendorf Law Firm assists ISOs in evaluating and structuring their business models based on their specific goals, risk tolerance, and growth strategy. By aligning legal structure with operational needs, ISOs can position themselves for scalable growth while minimizing exposure.

Contact Us

If you are launching an ISO, negotiating a processor agreement, or planning to sell a merchant portfolio, experienced legal counsel can help protect your rights and structure your business for long-term value.

Dilendorf Law Firm assists and represents Independent Sales Organizations in negotiating ISO agreements, including provisions related to residuals, transfer restrictions, and Rights of First Refusal (ROFR), as well as in structuring retail and wholesale ISO models.

Contact us at info@dilendorf.com to discuss your matter.

Starting an Independent Sales Organization (ISO) in the payment processing industry can be highly profitable. ISOs generate recurring revenue through merchant portfolios and residual payments tied to transaction volume.

But building a successful ISO is not just about signing merchants. It is about structuring a business where you actually control your rights, revenue, and exit options.

As courts and industry practice consistently show, these issues are determined not by sales performance—but by contracts.

Dilendorf Law Firm assist businesses launching ISOs, negotiating processor agreements, and structuring merchant portfolio rights to protect long-term value.

Step 1: Define Your ISO Business Model

Before launching, you need to decide how your ISO will operate, as this decision will shape your growth strategy, risk exposure, and contractual relationships.

Retail ISO

A retail ISO functions primarily as a sales and relationship-driven business. It focuses on sourcing and onboarding merchants, often working with one or more processing partners to place those merchants with the provider best suited to their needs—based on pricing, service, risk profile, or technical integration.

Retail ISOs typically do not control the back-end processing, adjudicate merchant applications, or manage servicing at the processor level. Instead, their value lies in building and maintaining merchant relationships and steadily growing a portfolio through internal sales teams or independent agents.

When structured properly, this model can offer relatively low startup costs and scalable, recurring revenue through residual income.

Wholesale ISO

A wholesale ISO, by contrast, operates at a higher structural level, building and managing a network of sub-ISOs, agents, or referral partners.

Rather than focusing solely on direct merchant acquisition, the wholesale model emphasizes distribution and scale. This approach can accelerate growth but introduces additional legal and operational considerations, particularly around supervision, compliance, and contractual risk allocation.

Choosing between these models is a foundational decision. It determines not only how the ISO acquires merchants, but also how liability is distributed, how agreements with processors are structured, and how the business can scale over time.

Step 2: Form Your Legal Entity

Once you have defined your business model, the next step is to establish the legal entity through which your ISO will operate.

Most ISOs are structured as limited liability companies (LLCs) or corporations, depending on ownership, tax considerations, and long-term business goals.

This step is more than a formality. The entity you choose will serve as the contracting party in your agreements with processors, acquiring banks, and partners. It will also determine how liability is allocated and how profits are distributed.

From a legal perspective, proper entity structuring helps:

• limit personal liability for owners and principals
• create a clear ownership framework for partners or investors
• support future growth, including adding agents or sub-ISOs
• facilitate a potential sale of the business or merchant portfolio

In practice, processors and acquiring banks will evaluate the ISO entity itself during underwriting. They may review ownership structure, financial stability, and the backgrounds of principals before approving the relationship.

Because the ISO’s value is tied to contractual rights and revenue streams, forming the entity correctly at the outset is an important step in building a business that can scale and be monetized over time.

Step 3: Secure a Processor or Acquiring Bank Relationship

An ISO cannot operate independently—it must partner with a payment processor and an acquiring bank. This relationship is the foundation of the business, as the processor controls the infrastructure for transaction processing, settlement, and compliance.

To establish this relationship, the ISO must go through underwriting, which typically includes background checks, a review of the business model, and an assessment of risk and compliance procedures.

As recognized in Process America v. Cynergy Holdings, ISOs “[…] solicit merchants […] and provide first-line customer support,” while processors manage the core payment system.

Because processors control access to the network, they also retain significant authority over approval and termination, making this step critical when launching an ISO.

Step 4: Negotiate the ISO Agreement

Once you secure a processor relationship, the next—and most critical—step is negotiating the ISO agreement. This document defines the economic and legal foundation of your business.

The agreement governs key issues such as:

• ownership of the merchant portfolio
• how residuals are calculated and paid
• whether residuals continue after termination
• your ability to transfer or sell accounts
• termination rights and restrictions

As courts have made clear, these rights are entirely contractual. In Process America v. Cynergy Holdings, the agreement provided that the processor “owns” the merchant agreements, and even where ownership could “vest” in the ISO, transfer remained subject to strict contractual conditions.

This means that the value of your ISO—your residual income and your ability to sell your portfolio—depends directly on how this agreement is structured and negotiated at the outset.

For a more detailed breakdown of key provisions and negotiation strategies, see our article “Negotiating ISO Agreements: Key Tips for Agents & ISOs.”

Step 5: Complete Registration and Network Approval

After entering into an agreement with a processor or acquiring bank, the ISO must complete registration within the card network system. This typically involves sponsorship by an acquiring bank and registration with networks such as Visa and Mastercard.

The approval process includes underwriting and due diligence, where the processor and bank assess the ISO’s ownership, business model, and risk profile. They may also review compliance procedures and the types of merchants the ISO intends to onboard.

Although this step is often viewed as administrative, it is a key control point in the payment ecosystem. Approval can be delayed or denied if the ISO presents elevated risk, and ongoing compliance with network rules is required to maintain the relationship.

Step 6: Build Your Merchant Acquisition System

Once your ISO is approved and operational, the next step is building a reliable system for acquiring merchants. This can be done through a direct sales model or by working with agents and sub-ISOs, depending on your chosen structure.

In a retail model, the ISO develops its own sales channels—through internal teams, marketing efforts, or independent contractors—and manages merchant onboarding directly. In a wholesale model, the ISO scales by recruiting agents or partner ISOs who bring in merchants.

While this stage is focused on growth, it also introduces significant legal risk. The ISO is responsible for how merchants are onboarded and how services are represented. Misleading sales practices, onboarding high-risk merchants, or failing to supervise agents can lead to chargebacks, compliance issues, and potential termination by the processor.

For that reason, successful ISOs treat merchant acquisition not just as a sales function, but as a controlled process with clear guidelines, training, and oversight.

Step 7: Implement Compliance and Risk Controls

At this stage, the ISO must establish basic compliance and risk controls. This includes screening merchants, monitoring chargebacks, and ensuring adherence to card network rules and data security standards.

Even though ISOs are not always directly regulated, processors expect them to manage risk effectively. Weak compliance—especially onboarding high-risk merchants or failing to supervise agents—can lead to termination and loss of residuals.

Step 8: Structure Your Residual Income

Residual income is the core of an ISO business, but it is entirely defined by the ISO agreement. You need to understand how residuals are calculated, when they are paid, and under what conditions they can be reduced or terminated.

Key issues to review include:

• how residuals are calculated (percentage, split, tiered structure)
• when residuals are paid and whether there are delays or reserves
• whether residuals continue after termination
• conditions that may reduce or eliminate residuals (e.g., chargebacks, compliance issues)
• whether residuals depend on ongoing servicing obligations
• any rights of the processor to modify pricing or revenue splits

In many agreements, residuals are tied to merchant activity and continued compliance, and may not survive termination of the relationship. As a result, what appears to be recurring revenue can be subject to significant contractual limitations.

Because these provisions directly affect the long-term value of your business, it is important to review and structure them carefully.

If you are unsure how your residuals are defined or protected, seeking legal guidance can help you avoid costly mistakes. Contact Dilendorf Law Firm to discuss your matter.

Step 9: Understand Transfer Restrictions and Exit Strategy

Many ISO founders plan to eventually sell their merchant portfolio, but the ability to do so depends entirely on the terms of the ISO agreement.

These agreements often include transfer restrictions such as consent requirements, Rights of First Refusal (ROFR), and anti-assignment clauses. As a result, the processor may have the right to approve, block, or match a proposed sale.

Courts enforce these provisions strictly. In Process America v. Cynergy Holdings, the court held that transferring merchant accounts without complying with contractual conditions constituted a breach of the ISO agreement.

For a detailed discussion of how ROFR provisions operate and how they can affect portfolio sales, see our article “Rights of First Refusal (ROFR) in Merchant Portfolio Transfers.”

For this reason, exit strategy should be considered from the outset. The value of an ISO is closely tied to whether its portfolio can be transferred—and on what terms.

Step 10: Avoid Common Mistakes When Starting an ISO

Across the industry, new ISOs often make the same mistakes—many of which only become apparent when the business faces termination, loss of residuals, or a failed sale:

• Signing ISO agreements without negotiating key terms
• Assuming they “own” merchant accounts without reviewing contract language
• Ignoring transfer restrictions and ROFR provisions
• Relying on “lifetime residuals” that are actually conditional
• Failing to implement proper compliance and risk controls
• Scaling too quickly through agents without adequate supervision
• Not planning for an exit strategy from the outset

Avoiding these issues early can make a significant difference in whether the ISO ultimately retains value and control over its business.

Contact Us

If you are launching an ISO, negotiating a processor agreement, or planning to sell a merchant portfolio, experienced legal counsel can help protect your rights and structure your business for long-term value.

Dilendorf Law Firm assists and represents Independent Sales Organizations in negotiating ISO agreements, including provisions related to residuals, transfer restrictions, and Rights of First Refusal (ROFR), as well as in structuring retail and wholesale ISO models.

Contact us at info@dilendorf.com to discuss your matter.

Stripe is one of the most widely used payment processors for online businesses. It allows merchants to accept payments, manage transactions, and operate globally.

But when something goes wrong—such as a suspended account or frozen payouts—the impact can be immediate. Payments stop, revenue is interrupted, and business operations can quickly stall.

At Dilendorf Law Firm, we help merchants negotiate disputes with Stripe, including account suspensions, frozen funds, compliance reviews, and chargeback-related issues.

Why Stripe Can Suspend Accounts or Freeze Funds

Stripe operates under its Services Agreement, which gives the platform broad authority to manage risk and enforce its policies.

For example, Stripe requires that:

“User must use the Services solely for User’s Business Purposes and in compliance with the Documentation.”

It also prohibits certain activities:

“User must not […] use the Services to engage in any activity that is fraudulent, deceptive, exploitative, or harmful.”

And importantly, Stripe can change or restrict its services:

“Stripe may modify or discontinue any aspect of the Services or Stripe Technology, including imposing conditions on use of the Services or Stripe Technology […]”

Stripe also makes clear that third-party tools are used at the merchant’s own risk:

“User’s use of any Third-Party Service is subject to that Third-Party Service’s terms […] and is at User’s sole risk.”

What this means in practice:
Stripe has significant discretion to suspend accounts or hold funds if it detects risk—even if the merchant believes their business is legitimate.

The Most Common Reasons Stripe Freezes Accounts

In practice, Stripe disputes usually arise from a few recurring issues:

• High chargeback rates

Too many customer disputes can trigger immediate review or restrictions.

• Unusual transaction activity

Sudden spikes in sales or changes in customer behavior may be flagged as risky.

• Compliance issues

Problems with identity verification (KYC) or regulatory requirements.

• Restricted or high-risk products

Certain industries are closely monitored or prohibited.

• Rapid business growth

Scaling too quickly can appear suspicious from a risk perspective.

Stripe’s systems are designed to:

“[…] monitor, prevent and detect fraudulent transactions and other fraudulent activity on the Stripe platform.”

Even legitimate businesses can be affected by these controls.

Chargebacks: A Leading Cause of Stripe Disputes

One of the most frequent—and misunderstood—reasons for Stripe account restrictions is chargebacks.

A chargeback occurs when a customer disputes a transaction directly with their credit card issuer (e.g., Visa, Mastercard, American Express) instead of contacting the merchant. The issuing bank may reverse the payment and initiate a dispute through the card network.

Why Chargebacks Trigger Stripe Enforcement

From Stripe’s perspective, chargebacks are not just isolated disputes—they are risk signals.

High chargeback activity may indicate:

• potential fraud
• customer dissatisfaction
• misleading product descriptions
• operational issues (e.g., shipping delays)

As chargebacks increase, Stripe may:

• freeze payouts
• impose rolling reserves
• increase monitoring
• suspend or terminate the account

Even a legitimate business can be flagged if its dispute rate exceeds acceptable thresholds set by card networks.

Chargeback Thresholds and Risk Exposure

Card networks (e.g., Visa, Mastercard) impose strict thresholds for acceptable dispute rates.

If a merchant exceeds these thresholds:

• additional fees may apply
• the business may be placed in a monitoring program
• the payment processor may take protective action

Stripe must manage this exposure, which is why enforcement can occur quickly and sometimes without detailed explanation.

What Merchants Should Do When Facing Chargebacks

When chargebacks arise, merchants should act promptly and strategically. If not addressed properly, disputes can lead to frozen funds, increased monitoring, and potential account suspension.

• Respond promptly

Submit responses within required deadlines to avoid automatic loss of disputes.

• Provide supporting documentation

Include basic evidence such as proof of delivery, transaction details, and customer communications.

• Identify and address the issue

Determine why disputes are occurring and take steps to reduce them going forward.

• Monitor dispute activity

Keep track of dispute rates to avoid exceeding thresholds set by payment processors and card networks.

• Seek legal assistance if issues escalate

If chargebacks begin to impact your account or funds, it is advisable to consult experienced counsel.

An attorney can help evaluate the situation and negotiate with Stripe or other payment processors to resolve disputes and protect your business.

At Dilendorf Law Firm, we assist merchants in negotiating chargeback-related disputes with Stripe, including matters involving frozen funds and account restrictions.

What Courts Say About Payment Processor Disputes

Courts have consistently addressed disputes between merchants and payment processors such as Stripe and PayPal. While outcomes depend on the facts, several key principles are clear.

Broad Discretion Under User Agreements

Courts generally enforce the terms of payment processor agreements, especially where those agreements grant discretion to manage risk.

In Zepeda v. PayPal, Inc., the court explained that:

“[…] the user agreement contained at least two other provisions that gave defendant broad discretion to place holds on its users’ accounts […]”

This principle is central to most disputes involving frozen funds or account suspensions.

No Contractual Duty to Provide Detailed Explanations

Merchants often expect detailed explanations when accounts are suspended or funds are frozen. However, courts look to the contract to determine whether such obligations exist.

In Zepeda, the court emphasized that the agreement itself controls the scope of duties owed to users. Where no provision requires disclosure, courts are unlikely to impose such obligations.

Exercising Contractual Rights Is Not a Breach

Courts consistently hold that a party does not breach a contract by doing what the contract allows.

In Chen v. PayPal, Inc., the court stated:

“A party cannot commit a breach of contract by exercising a right secured to him or her by the contract.”

This principle is critical in Stripe disputes, where the platform relies on contractual provisions to justify enforcement actions.

Discretion Must Still Be Exercised in Good Faith

Even where agreements grant broad discretion, courts recognize limits.

As explained in Chen:

“Where an agreement gives a party discretion, that discretion must be exercised in a reasonable, non-arbitrary manner.”

This creates an important framework: while processors have significant authority, their actions may still be challenged if exercised improperly.

Control Over Funds Is Not Always with the Merchant

Another key issue in payment processor disputes is who actually “holds” the funds.

In RealPage Inc. v. Nat’l Union Fire Ins. Co., the court held:

“[…] the funds that were maintained in a commingled account in a third party’s name, at a third-party bank, which the insured could direct but not access, were not funds ‘held’ by the insured”

This reflects how payment processors operate—merchants often do not have direct control over funds during processing or review periods.

Stripe’s Role Further Limits Dispute Obligations

Stripe’s own Terms reinforce this structure.

For example:

“Any contract of sale made using the Consumer Services is directly between you and the Business User.”

And:

“Stripe will not intervene in any dispute between you and a Business User […]”

These provisions clarify that Stripe positions itself as a payment intermediary rather than a party to the underlying transaction.

What This Means for Merchants

Taken together, these authorities show that:

• payment processors have broad contractual discretion
• courts often enforce those agreements as written
• merchants may not control funds during processing
• legal challenges require a fact-specific and strategic approach

For this reason, disputes with Stripe are rarely resolved through informal communication alone.

Contact Us

If your Stripe account has been suspended or your funds have been frozen, it is important to act promptly. These issues can significantly disrupt your business operations and cash flow.

At Dilendorf Law Firm, we assist merchants in negotiating disputes with Stripe and other payment processors, including matters involving account suspensions, frozen funds, and chargeback-related enforcement actions.

In addition to Stripe-related disputes, we also advise clients on broader payment processing and ISO-related matters. Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

To schedule a consultation, please contact us at info@dilendorf.com or 212-457-9797.

Independent Sales Organizations (ISOs) play a central role in the payment processing ecosystem. ISOs typically recruit merchants, assist with merchant onboarding, and facilitate relationships between merchants, payment processors, and acquiring banks.

Although ISOs are not always the primary regulated financial institution in the payment processing chain, their activities operate within a complex legal and regulatory framework governing electronic payments, fraud prevention, and data security.

These regulatory considerations are often reflected in ISO agreements with processors and acquiring banks, which must carefully allocate compliance responsibilities and risk. Dilendorf Law Firm helps ISOs with negotiating these agreements and addressing regulatory risk exposure.

As a result, ISOs face regulatory and legal risks related to fraud prevention, anti-money laundering obligations, data security requirements, and contractual liability within the payment card ecosystem. Understanding these risks is essential for ISOs seeking to maintain stable relationships with processors and avoid regulatory scrutiny.

Federal Statutory and Regulatory Framework

Several federal statutes indirectly affect the operations of businesses participating in the payment processing ecosystem.

Risk Management Standards

Under 12 U.S.C. § 5464, the Federal Reserve may establish risk management standards designed to promote the safety and stability of payment systems. These standards are intended to support sound risk management, reduce systemic risks, and maintain financial stability within the financial infrastructure.

Although ISOs may not always fall directly within the scope of these rules, their activities—particularly merchant onboarding and transaction facilitation—can create regulatory exposure if they contribute to operational or compliance failures within the payment system.

Fraud Prevention in Electronic Transactions

Electronic debit transactions are governed in part by federal law, including 15 U.S.C. § 1693o-2, which focuses on fraud prevention and the use of cost-effective fraud prevention technologies.

While ISOs are not directly regulated under this provision, they play an important role in onboarding merchants and facilitating payment transactions. Weak merchant screening practices can expose processors and acquiring banks to fraud risks, which in turn can result in contractual or regulatory consequences for the ISO.

Anti-Money Laundering Compliance

Financial institutions must maintain anti-money laundering (AML) programs under 31 U.S.C. § 5318, which requires policies, procedures, and internal controls designed to detect and report suspicious financial activity.

Because ISOs often act as intermediaries between merchants and financial institutions, their onboarding and merchant monitoring practices may become relevant in AML investigations. Failure to perform adequate due diligence on merchants can lead to processor termination or regulatory scrutiny.

Industry Standards and Data Security Obligations

Beyond federal statutes, ISOs must comply with industry security standards and contractual obligations governing payment card transactions.

PCI Data Security Standards (PCI DSS)

Payment card transactions are governed by the Payment Card Industry Data Security Standards (PCI DSS), which establish requirements for protecting cardholder data across the payment processing ecosystem.

Courts have repeatedly emphasized the contractual importance of these security standards.

For example, in Paymentech, L.L.C. v. Landry’s Inc., the Fifth Circuit explained that the merchant agreement required compliance with payment brand security rules and imposed liability for security failures. The court noted that:

“The Merchant Agreement required Landry’s to comply with all applicable Payment Brand rules and data security standards, including its cooperation with any forensic investigation required by a Payment Brand in the event of a breach.”

When a major data breach exposed cardholder data, the payment networks imposed substantial financial assessments. The court further explained that:

“Visa levied approximately $12.5 million in assessments; Mastercard approximately $10.5 million.”

These cases illustrate how failures to comply with payment security standards can trigger contractual liability within the payment processing ecosystem.

Contractual Risk Allocation in the Payment Card System

The payment card system operates through a network of contractual relationships involving merchants, processors, acquiring banks, issuing banks, and payment networks.

Courts have recognized that these contractual relationships govern how losses are allocated when security failures occur. In Community Bank of Trenton v. Schnuck Markets, Inc., the court explained the structure of the electronic payment system:

“When a customer uses a credit or debit card at a retail store, the merchant collects the customer’s information […] the track data and the amount of the intended purchase are forwarded electronically to the merchant’s bank (the ‘acquiring bank’), usually through a payment processing company.”

The court emphasized that the system is governed primarily by contractual relationships among the participating entities in the payment network.

Fraud and Misconduct Risks in ISO Operations

ISOs may also face litigation or regulatory exposure when fraudulent conduct occurs in connection with merchant onboarding or equipment leasing arrangements.

In Matter of People of the State of New York v. Northern Leasing Systems, Inc., the court described allegations involving misconduct by ISO sales representatives in the credit card processing industry. The court noted that:

“The ISOs misrepresented to those consumers the nature and terms of the EFLs and failed to disclose that they were entering into contracts with two different companies.”

The court further explained that some agreements allegedly contained hidden or onerous terms and that in certain instances the ISOs “forged the names of consumers or unilaterally altered the terms of the EFLs after they were signed.”

Cases involving allegations of misconduct can also raise broader litigation risks. In Aghaeepour v. Northern Leasing Systems, Inc., plaintiffs asserted claims under the Racketeer Influenced and Corrupt Organizations Act (RICO) based on alleged misconduct connected to equipment leases and collection practices.

These cases demonstrate that inadequate supervision of sales practices or merchant onboarding activities can expose companies operating in the payment processing ecosystem to substantial litigation risk.

Mitigating Regulatory Risks for ISOs

To reduce regulatory exposure, ISOs should adopt comprehensive compliance and risk management practices.

Key steps may include:

• Implementing compliance programs
  ISOs should establish policies addressing fraud prevention, AML compliance, and merchant due diligence.
• Conducting thorough merchant screening
  Proper vetting of merchants can reduce the risk of facilitating fraudulent or high-risk transactions.
• Establishing oversight mechanisms
  Monitoring sales agents and merchant onboarding processes can help prevent misconduct.
• Negotiating contractual protections
  ISO agreements should clearly allocate liability for fraud, data security breaches, and regulatory compliance obligations.
• Regularly reviewing compliance policies
  Payment system regulations and network rules evolve frequently, making periodic compliance reviews essential.

Conclusion

Independent Sales Organizations operate within a complex legal environment shaped by federal regulations, payment network rules, and contractual obligations within the payment processing ecosystem.

Although ISOs are not always directly regulated financial institutions, their activities can expose them to significant regulatory and litigation risks related to fraud prevention, data security, and merchant onboarding practices.

Careful compliance practices and well-structured contractual arrangements are essential to mitigate these risks and maintain stable relationships with processors and financial institutions.

Contact Us

If you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

Contact us at info@dilendorf.com to discuss your matter.

Online marketplaces such as Shopify have become essential infrastructure for modern commerce. Thousands of merchants rely on these platforms to host storefronts, process payments, and distribute products to customers worldwide.

However, merchants occasionally face sudden disruptions — including account suspensions, frozen payments, or terminated storefronts. When such enforcement actions occur, the merchant’s business can effectively stop overnight.

Understanding the legal framework governing platform relationships is critical for merchants seeking to restore operations and protect their businesses.

Dilendorf Law Firm assists merchants in negotiating disputes with online platforms, including Shopify and other e-commerce marketplaces, and in resolving issues involving suspended stores, frozen payouts, and platform compliance investigations.

Why Shopify May Freeze a Merchant Account

Most online platforms operate under detailed Terms of Service that grant the platform broad authority to enforce compliance with platform rules.

For example, Shopify’s Terms of Service expressly provide that the company may restrict access to its platform:

“Shopify reserves the right to refuse a Merchant access to or use of all or part of the Shop for any reason and at any time without prior notice.”

This contractual authority allows the platform to suspend accounts when it believes a merchant has violated platform policies or applicable law.

Common reasons for Shopify enforcement actions include:

• alleged intellectual property infringement
• counterfeit product complaints
• payment processing or fraud concerns
• regulatory compliance issues
• violations of Shopify’s acceptable use policies
• disputes regarding ownership or control of merchant accounts

Because enforcement systems often rely on automated monitoring or third-party complaints, merchants may find their stores restricted without advance notice.

Platform Terms Limit Shopify’s Role in Merchant Disputes

Another important provision of the Shopify Terms of Service clarifies that the platform does not generally intervene in disputes between merchants and customers:

“As in other areas of the Service, Shopify is not obligated to intervene in any dispute arising between you and your customers.”

This means merchants may be responsible for resolving disputes involving refunds, chargebacks, or product complaints without direct platform assistance.

In addition, Shopify limits responsibility for third-party applications and integrations used by merchants:

“Your use of Third Party Services is entirely at your own risk and discretion.”

The Terms further provide that Shopify may disable access to such services:

“Shopify may disable access to any Third Party Services at any time in its sole discretion and without notice to you.”

Because many merchants rely heavily on third-party applications for payment processing, marketing, or shipping, disabling these services can significantly disrupt operations.

Platform Disputes Can Shut Down Entire Businesses

Modern e-commerce merchants often rely on a single platform to reach customers and process transactions. When platform access is restricted, the impact can be immediate and severe.

Courts have recognized the central role that online marketplaces play in today’s economy. In YCF Trading Inc. v. Skullcandy, Inc., the court described the scale and importance of large online platforms:

“Amazon is the world’s largest online retailer and allows third parties to sell products on its online e-commerce platform, providing third party sellers with exposure to the world marketplace on a scale that no other online retailer can currently provide.”

When marketplace listings are removed or suspended, sellers may lose access to their customers and revenue streams.

Business Disputes Can Lead to Shopify Account Restrictions

Account restrictions may also arise when disputes occur between business partners or competing claimants.

In Browne v. Zaslow, the court described how a Shopify account was created to host an online retail business:

“Beginning his work for the website, J. Browne opened an account with Shopify to serve as the third-party internet host.”

When a dispute arose regarding ownership of the business and its website, Shopify froze access to the account until the parties resolved their disagreement:

“Shopify informed the Parties that it would deny access to the REE account to all concerned until the Parties resolved their differences.”

Such disputes often require legal intervention because the platform may refuse to restore access until ownership issues are resolved.

Federal Consumer Protection Laws Also Affect Online Merchants

Merchants operating through online platforms must comply not only with platform policies but also with federal consumer protection laws.

In FTC v. Romero, the court emphasized that federal law regulates internet-based commerce:

“The Federal Trade Commission Act (FTCA) prohibits unfair or deceptive acts or practices in or affecting commerce.”

Federal regulations governing online orders also impose obligations regarding shipping representations:

“The MITOR prohibits a seller from soliciting any order for the sale of merchandise to be ordered by a buyer via the Internet unless […] the seller has a reasonable basis to expect that it will be able to ship any ordered merchandise.”

Failure to comply with these regulations can trigger enforcement actions from both regulators and platform operators.

Litigation Involving Shopify Platforms

Courts are increasingly addressing legal disputes involving Shopify and similar e-commerce platforms.

In Briskin v. Shopify, Inc., the Ninth Circuit addressed claims arising from Shopify’s role in processing online transactions and collecting user data.

The court explained how Shopify’s technology operates during online purchases:

“When he pressed the ‘Pay now’ button, he had no way of knowing that by doing so he submitted his personal data not to [the merchant], but to Shopify, an e-commerce platform that facilitates online sales for merchants with whom it contracts.”

The court also emphasized that traditional legal principles still apply to internet commerce:

“The emergence of the internet presents new fact patterns, but does not require a wholesale departure from the approach to personal jurisdiction before the internet age.”

These cases demonstrate that courts continue to apply established legal doctrines to modern e-commerce platforms.

Common Legal Issues in Platform Disputes

When merchants face Shopify account suspensions or payment holds, several legal issues frequently arise:

Contract interpretation

Platform relationships are governed by detailed Terms of Service agreements defining platform authority and merchant obligations.

Intellectual property complaints

Brands or competitors may file infringement complaints that trigger listing removal or store suspension.

Ownership disputes

Business partners or investors may dispute control of a merchant account.

Payment processing restrictions

Platforms may freeze payouts during fraud investigations or compliance reviews.

Regulatory compliance

Federal and state consumer protection laws impose obligations on merchants regarding advertising, delivery timelines, and product claims.

What Merchants Should Do If Shopify Freezes Their Store

When Shopify suspends a store or freezes payouts, merchants should take prompt and organized action.

1. Review the suspension notice

Merchants should carefully review any communication received from Shopify, including references to the Terms of Service, Acceptable Use Policy, or Shopify Payments rules.

Identifying the specific issue alleged by Shopify is essential before preparing a response.

2. Preserve business documentation

Merchants should immediately gather records demonstrating compliance with Shopify policies, including:

• supplier invoices
• fulfillment and shipping records
• customer communications
• refund and chargeback history
• intellectual property licenses

These records may be necessary to respond to platform investigations.

3. Respond clearly to Shopify’s investigation

If Shopify allows a response, merchants should provide a structured explanation supported by documentation.

An effective response typically includes:

• explanation of the issue
• supporting evidence
• confirmation of compliance measures
• corrective steps, if applicable

Incomplete responses often delay reinstatement.

4. Address intellectual property complaints

Many Shopify suspensions arise from trademark or copyright complaints.

Merchants should determine:

• who submitted the complaint
• whether the complaint is valid
• whether the products sold are authentic or licensed

Resolving such complaints may require providing proof of authenticity or negotiating with the rights holder.

5. Resolve account ownership disputes

If Shopify freezes an account because multiple parties claim control over it, the platform may refuse to restore access until the dispute is resolved.

Resolving such issues often requires reviewing corporate documents, operating agreements, or partnership agreements.

6. Investigate frozen Shopify Payments payouts

If merchant funds are frozen, Shopify may be investigating:

• chargeback risk
• fraud concerns
• suspicious transaction patterns
• regulatory compliance issues

Merchants should prepare documentation demonstrating legitimate sales and fulfillment activity.

Conclusion

Online marketplaces provide powerful tools for entrepreneurs and retailers, but they also create new legal risks and operational dependencies.

Account suspensions, payment holds, and platform enforcement actions can significantly disrupt a merchant’s business. Courts increasingly recognize the central role these platforms play in modern commerce, yet disputes often turn on the contractual terms governing the platform relationship.

Merchants facing Shopify enforcement actions should evaluate their legal options promptly and seek professional guidance to resolve the dispute efficiently.

Dilendorf Law Firm assists merchants in navigating platform disputes and negotiating with online marketplaces to protect their businesses and restore operations.

Contact Us

If you are facing issues with a suspended Shopify store or restricted merchant account, our firm can review the situation and discuss potential strategies for addressing the dispute.

Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

To schedule a consultation, please contact us at info@dilendorf.com.

Merchant portfolios are often the most valuable asset of an Independent Sales Organization (ISO).

Over time, ISOs develop relationships with merchants that generate recurring revenue through residual payments tied to credit and debit card processing.

Because of the economic value of these portfolios, ISO agreements frequently include Rights of First Refusal (ROFR) that govern how and when a portfolio may be transferred.

Dilendorf Law Firm helps Independent Sales Organizations on negotiating ISO agreements, including provisions governing portfolio transfers and Rights of First Refusal. Careful negotiation of these clauses at the contract stage can significantly affect an ISO’s ability to sell or monetize its merchant portfolio in the future.

Federal and state courts have repeatedly addressed the enforcement of ROFR provisions in commercial contracts and merchant services agreements.

These decisions provide important guidance regarding notice requirements, matching obligations, and the consequences of failing to comply with contractual transfer restrictions.

The Role of ROFR Clauses in ISO Agreements

A Right of First Refusal gives a designated party the opportunity to purchase an asset before it can be sold to a third party. In the merchant services industry, the holder of the right is often the processor or acquiring bank.

Unlike an option contract, a ROFR does not require the owner to sell the asset. Instead, it regulates the circumstances under which a sale may occur.

Courts have described this distinction clearly. In Seessel Holdings v. Fleming Companies, the court explained:

“[…] the right of first refusal, although closely akin to an option, differs in that it does not give the holder the power to compel an unwilling owner to sell, but merely requires that when and if the owner decides to sell, he offers the property first to the holder of the right.”

In the context of ISO agreements, this means that if an ISO receives an offer to sell its merchant portfolio, the processor with ROFR rights must be given the opportunity to match that offer before the portfolio can be transferred.

Enforcement of ROFR Provisions in Merchant Portfolio Transfers

Federal and state cases addressing the enforcement of ROFR clauses in merchant services agreements provide significant guidance on how courts interpret these provisions.

A leading decision is Process America, Inc. v. Cynergy Holdings, LLC, which involved a dispute between an ISO and a processor regarding merchant portfolio transfers. The court described the fundamental structure of the merchant services industry and the role of ISOs:

“Process America is an Independent Sales Organization (“ISO”) that, prior to the termination of their relationship, solicited and referred merchants to Cynergy, a bankcard processor.”

The ISO agreement in that case required compliance with specific contractual conditions before any transfer of merchant accounts could occur. These conditions included providing notice, allowing the processor to exercise a right of first refusal, paying certain fees, and executing a new processing agreement.

When the ISO transferred a portion of the merchant portfolio to a third party without complying with those contractual provisions, the court concluded that the transfer violated the agreement.

The decision underscores a key principle: courts will enforce ROFR provisions in ISO agreements according to their precise contractual language.

When a ROFR Becomes Enforceable

ROFR provisions generally become enforceable when the asset owner receives a legitimate third-party offer.

In Kunelius v. Town of Stow, the First Circuit explained the legal effect of such an offer:

“Once a seller receives a bona fide offer, a right of first refusal (ROFR) ripens into an option to purchase the property at the price and otherwise on the terms stated in the offer.”

The court further emphasized that the holder must have access to the terms of the proposed transaction in order to decide whether to exercise the right.

This principle is particularly important in merchant portfolio transfers because the value of the portfolio may depend on multiple economic terms, including pricing structures, servicing arrangements, and residual payment streams.

The Requirement to Match the Third-Party Offer

Courts consistently require strict adherence to the terms of the third-party offer when exercising a ROFR.

In Seessel Holdings v. Fleming Companies, the court addressed whether the holder had properly exercised its first refusal right and concluded that the holder must accept the same terms offered to the third-party purchaser.

The court explained:

“[…] the right holder who agrees to meet the same terms and conditions as contained in a third-party offer must meet all of those terms.”

The decision further clarified that a party cannot exercise a ROFR while attempting to modify the underlying transaction. If the holder proposes alternative terms or refuses to finalize a contract matching the third-party offer, the attempted exercise of the right may be ineffective.

These principles frequently arise in disputes involving portfolio sales where the processor attempts to match a transaction but proposes different financing structures or contractual conditions.

The Exercise Period and Procedural Requirements

One of the most critical aspects of a ROFR clause is the exercise period and the procedures required to trigger and exercise the right.

There is no statutory default exercise period governing ROFR clauses. The enforceability of the right depends entirely on the contractual language negotiated by the parties.

A properly drafted ISO agreement should clearly define:

• The duration of the exercise period (typically measured in calendar days)
• The triggering event (such as receipt of a bona fide written offer)
• Notice requirements and delivery methods
• Whether failure to respond within the stated period constitutes waiver of the right

If these procedures are not clearly defined, disputes can arise during portfolio sales.

Delayed or Unreasonable Responses by Banks

Problems frequently arise when the processor or acquiring bank fails to respond within the required exercise period or attempts to delay the transaction.

For example, disputes may arise where the bank:

• Responds after the contractual deadline
• Requests additional information not required by the agreement
• Attempts to extend the exercise period unilaterally
• Attempts to renegotiate the transaction instead of matching the offer

Where the agreement clearly defines the exercise period, courts typically enforce the deadline strictly. Failure to exercise the right within that period may result in waiver of the ROFR, allowing the ISO to proceed with the third-party sale.

When the Agreement Does Not Specify an Exercise Period

Additional complications arise when an ISO agreement does not specify the time period for exercising a ROFR.

In such circumstances, courts may determine that the right must be exercised within a reasonable time, based on the surrounding circumstances and commercial expectations of the parties.

However, the absence of a defined deadline creates uncertainty and may delay transactions or discourage potential buyers. For this reason, carefully drafted ISO agreements typically include clear timelines and procedural rules governing ROFR rights.

At Dilendorf Law Firm, we assist ISOs in negotiating and structuring contractual provisions related to Rights of First Refusal in merchant services agreements.

Why ROFR Clauses Matter in Merchant Portfolio Transactions

ROFR provisions are common in ISO agreements because processors and acquiring banks seek to maintain control over the merchant relationships they service.

From a commercial perspective, these provisions help processors:

• Maintain continuity of merchant processing relationships
• Prevent portfolios from being transferred to competing processors
• Protect underwriting and risk management structures
• Preserve long-term merchant revenue streams

For ISOs, however, these provisions may significantly affect exit strategies and portfolio valuation. A buyer negotiating the acquisition of a merchant portfolio must recognize that the transaction could ultimately be acquired by the ROFR holder instead.

Conclusion

Rights of First Refusal play a central role in merchant portfolio transfers within the payment processing industry. Although these provisions do not prohibit portfolio sales, they can significantly influence the outcome of a transaction by determining who ultimately acquires the portfolio and under what conditions.

Courts consistently require strict compliance with ROFR provisions and enforce them according to the language of the governing agreement. For ISOs and processors alike, careful drafting and negotiation of these provisions is essential.

Contact Us

Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

Contact us at info@dilendorf.com to discuss your matter.

In the payment processing industry, merchant portfolios are the core economic asset of an Independent Sales Organization (ISO). They generate residual income, determine exit valuations, and form the foundation of business leverage.

Yet in disputes between ISOs, sub-ISOs, processors, and acquiring banks, one recurring question dominates:

Who actually owns the merchant portfolio?

Federal and state courts consistently provide the same answer:

Ownership, vesting, transfer rights, and residual control are determined by the contract — and courts enforce it strictly.

This article examines how courts analyze merchant portfolio ownership under ISO agreements, focusing on:

• Ownership triggers and vesting
• Transfer restrictions
• Post-termination residual rights
• Conditions precedent
• Survival clauses
• Ambiguity and course of performance

1. Ownership and Vesting: The Contract Controls

The leading appellate decision addressing merchant portfolio ownership is:

Process America, Inc. v. Cynergy Holdings, LLC, 839 F.3d 125 (2d Cir. 2016)

In Process America, the ISO argued that its portfolio ownership vested once it met contractual benchmarks. The agreement defined an “Ownership Trigger Date,” after which ownership would shift.

However, the Second Circuit emphasized that even after the trigger date, the ISO could not freely transfer the merchant agreements. Section 2.6.B imposed strict conditions, including:

• Granting the processor a right of first refusal
• Paying an exit fee
• Executing a new processing agreement acceptable to the processor and bank

The court enforced these conditions as written.

Key takeaway: “Ownership” language in ISO agreements does not necessarily mean unrestricted control. Vesting may be conditional and subject to compliance with multiple contractual prerequisites.

2. Transfer Rights and Restrictions Are Enforceable

In Process America, the ISO solicited merchants and transferred portions of the portfolio without complying with Section 2.6.B. The court found this conduct violated the agreement and caused damages due to merchant attrition.

Courts treat ISO agreements as sophisticated commercial contracts. If the agreement imposes:

• A right of first refusal
• Exit fees
• Consent requirements
• Replacement processing agreements

those restrictions will be enforced.

An ISO cannot circumvent transfer conditions simply because it sourced the merchant relationship.

3. Post-Termination Control and Reserve Funds

Portfolio disputes often arise after termination.

In the related bankruptcy proceeding In re Process America, Inc., 588 B.R. 82 (Bankr. E.D.N.Y. 2018), the court held that the processor was not obligated to release reserve funds until merchant agreements were terminated pursuant to the contract.

Post-termination rights — including reserves and residuals — are governed strictly by the agreement’s language. Courts do not imply broader rights beyond the text.

4. Residual Rights After Termination

Residual income survival is frequently misunderstood.

In Universal Bankcard Systems, Inc. v. Bankcard America, Inc., 998 F. Supp. 961 (N.D. Ill. 1998) the sub-ISO agreement provided that Universal was entitled:

“[…] to receive residuals over the lifetime of its accounts as long as the ISO services the account, […] whether or not this Agreement has been terminated.”

However, the same agreement gave the lead ISO the right:

“[…] sell, at its sole discretion, any portion or all of its merchant base, and in said event, upon the completion of said sale to a bona fide third party, the right of [Universal] to receive residuals arising from said accounts shall cease.”

This dual structure illustrates a critical principle:

Lifetime residual language can be contractually limited by a sale-of-portfolio clause.

Even strong residual survival provisions may be extinguished upon a qualifying sale.

5. The ISO’s Role in Merchant Relationships

Courts also analyze how ISO agreements fit within the broader processing structure.

In Spread Enterprises, Inc. v. First Data Merchant Services Corp., 298 F.R.D. 54 (E.D.N.Y. 2014) the court described the contractual architecture between merchants and processors:

Processors “[…] enter into contracts with different Merchants by which [they agree] to perform several processing functions for the Merchant, such as the authorization, batching, clearing and settlement functions of a credit card transaction.”

Merchant agreements are often:

• Between merchant and acquiring bank
• Sponsored by a processor
• Serviced by an ISO

Thus, an ISO’s “ownership” may refer only to economic rights — not legal ownership of the merchant contract itself.

6. When Do Residual Rights Actually Vest?

Courts distinguish between:

• Accrued rights
• Conditional rights
• Contingent rights

Under federal law, a right is considered vested when it is unconditional and immediately claimable. See Romines v. Great-West Life Assurance Co., 73 F.3d 1457 (8th Cir. 1996).

In the payment processing context, courts routinely examine whether contractual conditions precedent were satisfied before termination.

In Lawson v. Heartland Payment Systems, LLC, 548 F. Supp. 3d 1085 (D. Colo. 2020) the court addressed commission and residual claims in the processing industry employment context.

The court emphasized that compensation rights depend on satisfaction of contractual conditions. If installation, execution, or servicing requirements are not complete at termination, commissions may not vest.

Vesting depends on performance of contractual conditions — not expectations.

7. Conditions Precedent and Contractual Precision

Several courts have refused to recognize vesting where required steps were not completed.

If an ISO agreement ties residual rights to:

• Executed merchant contracts
• Approved applications
• Installed terminals
• Active servicing

then those elements must be satisfied before vesting occurs.

Absent fulfillment of conditions precedent, residual claims may fail.

8. Ambiguity and Course of Performance

When contractual language is ambiguous, courts may examine extrinsic evidence.

For example, in Orkin v. Albert, 162 F.4th 1 (2025), the court relied on the parties’ conduct — including forwarding of residual payments — to interpret ownership intent.

However, where the language is clear, courts will enforce the agreement as written, even if the result appears harsh.

Conclusion: Portfolio Ownership Is a Contractual Allocation of Risk

The consistent judicial theme across Process America, Universal Bankcard, Spread Enterprises, and related decisions is unmistakable:

Ownership, vesting, transfer rights, and residual survival depend entirely on the contractual structure.

An ISO may believe it “owns” its portfolio. But unless the contract supports that belief — and all conditions are satisfied — courts will enforce the agreement as written.

Merchant portfolio disputes are not emotional disputes about business relationships.

They are contractual disputes governed by precise drafting.

Contact Us

Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

Contact Dilendorf Law Firm at info@dilendorf.com to schedule a confidential consultation.

 

Venue provisions in an ISO agreement are not secondary terms. They determine where and how disputes over residual payouts, portfolio ownership, termination, rights of first refusal, or indemnification will be resolved.

The choice between federal court, state court, and arbitration can materially affect cost, timing, leverage, and outcome.

For ISOs, venue is a strategic business decision—not merely a procedural clause.

Arbitration: The Dominant ISO Model

Most modern ISO agreements require mandatory arbitration, typically administered by:

• AAA (American Arbitration Association)
• JAMS
• NAM (National Arbitration and Mediation)

Arbitration clauses are strongly favored under the Federal Arbitration Act (FAA).

In Henry Schein, Inc. v. Archer & White Sales, Inc., 586 U.S. 63 (2019), the Supreme Court made clear:

“Under the Federal Arbitration Act (FAA), arbitration is a matter of contract, and courts must enforce arbitration contracts according to their terms.”

The Court further emphasized:

“The Federal Arbitration Act does not contain a ‘wholly groundless’ exception, and courts are not at liberty to rewrite the statute passed by Congress and signed by the President.”

Similarly, in AT&T Mobility LLC v. Concepcion, 563 U.S. 333 (2011), the Court reinforced the federal policy favoring arbitration and the principle that arbitration agreements must be enforced as written.

The practical takeaway for ISOs is straightforward: arbitration clauses—including venue designations, delegation provisions, and class-action waivers—are rarely invalidated.

Venue Under the FAA

The FAA also governs arbitration-related venue mechanics.

In Cortez Byrd Chips v. Bill Harbert Constr. Co., 529 U.S. 193 (2000), the Supreme Court held that the FAA’s venue provisions in §§ 9–11 are permissive rather than restrictive, meaning courts may confirm or vacate arbitration awards in more than one permissible venue.

However, compelling arbitration under 9 U.S.C. § 4 is treated differently. Federal courts have recognized that § 4 contains mandatory language requiring arbitration to proceed within the district where the petition to compel is filed.

These distinctions matter when drafting arbitration and venue language in ISO agreements.

Federal and State Court Litigation

If an ISO agreement designates litigation rather than arbitration, forum-selection clauses are also strongly enforced.

In The Bremen v. Zapata Off-Shore Co., 407 U.S. 1 (1972), the Supreme Court held:

“Forum-selection clauses are prima facie valid and should be enforced unless enforcement is shown by the resisting party to be unreasonable under the circumstances.”

The Court further explained:

“Where the choice of a forum was made in an arm’s-length negotiation by experienced and sophisticated businessmen, absent some compelling and countervailing reason, it should be honored by the parties and enforced by the courts.”

In other words, once a venue clause is agreed upon, courts will rarely disturb it.

Why ISOs Often Choose Arbitration

ISOs frequently accept arbitration because it offers:

• Faster resolution
• Confidential proceedings
• Streamlined procedures
• Decision-makers with commercial expertise

Confidentiality alone can be critical in disputes involving residual streams, merchant portfolios, or termination rights.

The Cost Reality

Arbitration is often faster—but not necessarily cheaper.

Unlike courts, arbitration requires:

• Administrative filing fees
• Arbitrator hourly compensation
• Institutional fees (AAA, JAMS, NAM)
• Hearing logistics and scheduling costs

In complex ISO disputes—particularly those involving forensic accounting, portfolio valuation, or multi-year residual calculations—arbitration costs can exceed federal court litigation.

Additionally, arbitration awards are subject to extremely limited judicial review. Errors of law are rarely grounds for reversal.

Arbitration and Venue: Strategic Review Before Signing

An arbitration clause should be reviewed carefully before signing an ISO agreement. ISOs should confirm:

• Which organization will administer the arbitration (AAA, JAMS, or NAM);
• Where the arbitration will take place;
• Whether the case will be decided by a single arbitrator or a panel;
• How arbitration fees and attorneys’ fees are allocated;
• How broadly the clause is drafted;
• Whether any claims are carved out for court relief.

Language covering disputes “arising out of or relating to” the agreement may capture nearly all claims, including termination, indemnification, rights of first refusal, liability caps, and residual calculations.

Because courts “must enforce arbitration contracts according to their terms,” and forum-selection clauses are “prima facie valid,” venue provisions are rarely negotiable after a dispute arises.

A mandatory arbitration clause combined with fee-shifting may increase financial exposure. Conversely, a carefully negotiated clause can preserve leverage in a dispute with a payment processor or sponsoring bank.

Venue is not merely procedural—it is strategic.

Protect Your Position Before You Sign

At Dilendorf Law Firm, we represent ISOs and payment industry participants in negotiating ISO agreements, including arbitration clauses, venue provisions, residual payout protections, rights of first refusal, and risk allocation mechanisms.

Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

Contact us at info@dilendorf.com to protect your residual income, portfolio rights, and strategic position.

 

Independent Sales Organizations (ISOs) play a central role in the merchant services ecosystem. They solicit merchants, build portfolios, generate residual income streams, and serve as intermediaries between merchants and acquiring banks.

However, ISO–merchant bank agreements are sophisticated commercial contracts that define ownership, compensation, liability exposure, and dispute mechanisms. Courts enforce these agreements strictly according to their plain language.

Accordingly, ISOs must approach these contracts as long-term risk-allocation instruments, not merely referral arrangements.

Before signing a contract with a merchant bank, an ISO should carefully evaluate the following critical issues.

1. Portfolio Ownership and Control

Portfolio ownership is one of the most consequential provisions in any ISO agreement.

In Process Am., Inc. v. Cynergy Holdings, LLC, 839 F.3d 125 (2d Cir. 2016), the U.S. Court of Appeals for the Second Circuit described the ISO’s role:

“Process America is an Independent Sales Organization (“ISO”) that, prior to the termination of their relationship, solicited and referred merchants to Cynergy, a bankcard processor.”

The dispute centered on who owned the merchant portfolio after termination and whether the ISO could transfer or solicit those accounts. The court enforced the contract as written.

The Second Circuit emphasized:

“In interpreting a contract under New York law, words and phrases should be given their plain meaning, and the contract should be construed so as to give full meaning and effect to all of its provisions.”

ISOs must confirm:

• Who owns merchant agreements during the term;
• When ownership vests, if at all;
• Whether the portfolio can be assigned or transferred;
• How termination affects ownership rights.

Ownership provisions directly affect enterprise value and exit strategy.

2. ISO’s Rights Under a Right of First Refusal (ROFR)

Many ISO agreements grant the acquiring bank a Right of First Refusal (ROFR) over the ISO’s portfolio or a proposed sale transaction.

A ROFR gives the holder a preemptive right to match a bona fide third-party offer before the ISO may complete a transfer. Because it restricts transferability, courts interpret ROFR clauses narrowly and strictly according to their text. See Kaiser v. Bowlen, 455 F.3d 1197 (10th Cir. 2006).

The Exercise Period and Procedures Must Be Expressly Defined

There is no statutory default exercise period. The enforceability of a ROFR depends entirely on the contractual language.

The agreement must clearly define:

• The duration of the exercise period (in calendar days);
• The triggering event (such as receipt of a bona fide written offer);
• Notice requirements and delivery method;
• That failure to respond within the stated period constitutes waiver.

Courts have limited or invalidated ROFR provisions where essential terms were missing or indefinite. See Mr. W Fireworks, Inc. v. NRZ Inv. Group, LLC, 677 S.W.3d 11 (Tex. 2023); Crescent Homes SC, LLC v. CJN, LLC, 445 S.C. 164 (2023). Vague phrases such as “within a reasonable time” create litigation risk.

In the ISO context, strict compliance with contractual transfer provisions is critical. In Process Am., Inc. v. Cynergy Holdings, LLC, 839 F.3d 125 (2d Cir. 2016), the court enforced portfolio-transfer and ROFR-related provisions according to their plain meaning.

Because a ROFR can materially affect liquidity and valuation, its timing and procedural mechanics must be drafted with precision to avoid unintended restraints on transferability.

3. Commission Structure and Residual Rights

Compensation is the economic foundation of the ISO relationship.

Most ISO agreements provide for:

• A share of the merchant discount rate (residuals);
• Upfront bonuses or performance incentives;
• Revenue splits tied to portfolio performance;
• Adjustments based on chargebacks or risk metrics.

In Process America, residual payments became central to the dispute. The contract provided that residuals would continue unless termination was based on a material breach. The enforceability of those provisions depended entirely on contractual language.

ISOs must evaluate:

• How commissions are calculated;
• Whether the split is fixed or subject to unilateral adjustment;
• Whether the bank may modify pricing or fees;
• Under what circumstances residuals may be withheld;
• Whether residual rights survive termination.

Residual stream stability is critical to valuation. Even minor pricing adjustment clauses can materially affect long-term income.

4. Non-Solicitation and Post-Termination Exposure

ISO agreements frequently include post-termination non-solicitation provisions.

In Process America, the ISO was found liable for soliciting merchants after termination. The court rejected arguments that prior breaches excused later conduct.

The Second Circuit explained:

“A partial breach by one party does not justify the other party’s subsequent failure to perform; both parties may be guilty of breaches, each having a right to damages.”

ISOs must assess:

• Duration and scope of non-solicitation;
• Whether restrictions apply to affiliates;
• How non-solicitation interacts with ROFR provisions;
• Whether residual forfeiture is triggered by violation.

Post-termination restrictions are routinely enforced.

5. Liability Caps and Risk Allocation

Merchant bank agreements commonly include liability-limitation provisions.

The Second Circuit observed:

“New York courts have routinely enforced liability-limitation provisions when contracted by sophisticated parties, recognizing such clauses as a means of allocating economic risk in the event that a contract is not fully performed.”

ISOs must determine:

• Whether liability is capped and at what amount;
• Whether indemnification is excluded from the cap;
• Whether carve-outs exist for gross negligence or willful misconduct;
• Whether liquidated damages provisions apply.

Courts treat these clauses as negotiated economic risk allocation.

6. Indemnification for Card Network Assessments

Card organizations may impose fines and reimbursement obligations through acquiring banks.

In Banc of America Merchant Services, LLC v. Arby’s Restaurant Group, Inc., 2021 NCBC 41 (N.C. Super. Ct. 2021), the agreement required payment of:

“[…] all assessments, fines, penalties, fees, Card issuer reimbursements and similar charges imposed by Card Organizations on BANK (the ‘Card Organization Penalties’), directly related to MERCHANT’s Card transactions or based on MERCHANT’s actions or failure to act with respect to compliance with the Card Organization Rules or Merchant’s breach of Section 13 (Information Security)”

The court clarified:

“A claim for contractual indemnity is a claim for direct damages, not consequential damages.”

ISOs must carefully evaluate indemnity exposure, particularly in data breach scenarios.

7. Data Security and Contractual Risk Allocation

In Cmty. Bank of Trenton v. Schnuck Mkts., Inc., 887 F.3d 803 (7th Cir. 2018), issuing banks sought tort recovery following a data breach. The court rejected the attempt:

“For more than fifty years, state courts have generally refused to recognize tort liabilities for purely economic losses inflicted by one business on another where those businesses have already ordered their duties, rights, and remedies by contract.”

The court further explained:

“Courts invoking the economic loss rule trust the commercial parties interested in a particular activity to work out an efficient allocation of risks among themselves in their contracts.”

Risk allocation must be negotiated at contract formation. Courts rarely expand remedies beyond the contract.

8. ISO Rights and Protections

Beyond compensation and ownership, ISOs should ensure the agreement clearly defines their rights, including:

• Access to merchant performance data;
• Audit rights to verify commission calculations;
• Transparency in fee adjustments;
• Notice requirements before pricing changes;
• Cure periods before termination;
• Protection against unilateral reassignment of the portfolio.

Rights not expressly granted may not be implied.

9. Dispute Resolution Mechanisms

Dispute Resolution Mechanisms

An ISO agreement should clearly define how disputes will be resolved, as these provisions frequently determine leverage, cost exposure, and procedural advantage in the event of conflict.

Most merchant bank agreements include mandatory arbitration clauses.

Under 9 U.S.C. § 2 (Federal Arbitration Act), arbitration agreements are deemed: “[..] valid, irrevocable, and enforceable, save upon such grounds as exist at law or in equity for the revocation of any contract”

The U.S. Supreme Court reinforced this principle in AT&T Mobility LLC v. Concepcion, 563 U.S. 333 (2011), holding that state rules that interfere with arbitration are preempted when they:

“[…] stand […] as an obstacle to the accomplishment and execution of the full purposes and objectives of Congress.”

As a result, arbitration clauses in ISO agreements are generally enforced according to their terms.

Even where ISO agreements are adhesion contracts, courts do not invalidate arbitration provisions solely on that basis. In commercial disputes, courts emphasize enforcing contractual language as written and avoiding interpretations that render provisions “superfluous or meaningless.” (Process Am., Inc. v. Cynergy Holdings, LLC, 839 F.3d 125 (2d Cir. 2016))

ISOs must therefore carefully review:

• Whether arbitration is mandatory or optional;
• The scope of disputes covered (including arbitrability determinations);
• Governing law and venue selection;
• Allocation of arbitration costs and fees;
• Whether class action waivers are included;
• Whether certain claims (such as injunctive relief or collection actions) are carved out.

Carve-out provisions may create procedural imbalance if, for example, the bank reserves the right to litigate certain claims in court while requiring the ISO to arbitrate all disputes.

Cost allocation is also critical. For example, the Ponca Tribe of Nebraska Code § 6-12-9 provides that in adhesion contracts:

“[…] the drafting party shall bear all costs and fees of the dispute resolution process, including arbitrator compensation”

While jurisdiction-specific, this illustrates how governing law can materially affect enforcement and financial exposure.

Dispute resolution provisions are not procedural formalities. They directly influence enforcement of liability caps, indemnification rights, commission disputes, and termination conflicts.

Because arbitration clauses are broadly enforced under federal law, ISOs must negotiate these provisions carefully before execution of the agreement.

Key Considerations for ISOs

Before entering into a merchant bank agreement, an ISO should assess portfolio ownership, ROFR provisions and their defined timing mechanics, commission and residual structure, non-solicitation restrictions, indemnification exposure, liability caps, reserve requirements, and dispute resolution terms.

At Dilendorf Law Firm, we advise ISOs and payment industry participants on contract negotiation, risk allocation, and dispute resolution.

Whether you are negotiating an ISO agreement, planning to sell a merchant portfolio, or exploring the launch of your own ISO—whether retail or wholesale—legal guidance can help you structure your business, manage risk, and protect your rights.

Contact us at info@dilendorf.com to protect your enterprise value and contractual rights.