Establishing secure connection…Loading editor…Preparing document…

Business ISO Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

BUSINESS ISO AGREEMENT

This Business ISO Agreement ("Agreement") is entered into as of by and between:

Principal Name:    Principal Address:

ISO Name:    ISO Address:

RECITALS

WHEREAS, Principal is engaged in the business of providing payment processing services and related products and desires to engage ISO to solicit merchants and facilitate enrollment of merchants for the Principal's services pursuant to the terms set forth herein;

WHEREAS, ISO represents that it has the expertise, personnel, and facilities to market, solicit and support merchant accounts, and ISO desires to market and resell Principal's services in accordance with the terms of this Agreement;

WHEREAS, the parties desire to set forth their respective rights and obligations with respect to the appointment and authorization of ISO to solicit merchants for Principal under the terms and conditions of this Agreement.

SCOPE OF WORK

ISO shall solicit, enroll and provide first-line support to merchants for the Principal's payment processing services. ISO's specific responsibilities include merchant solicitation, collection of merchant documentation, facilitation of underwriting submissions, merchant onboarding assistance, and limited ongoing merchant support as further described below and in any exhibits attached to this Agreement.

PAYMENT TERMS

Compensation to ISO shall be calculated and paid in accordance with the following terms. Principal shall pay ISO the fees set forth below for merchants enrolled and accepted by Principal in each settlement period.

All payments are subject to reconciliation and adjustment for chargebacks, refunds, and other merchant liabilities. Principal may set off any amounts owed by ISO against payments owing to ISO upon notice to ISO.

TERM AND TERMINATION

Term: This Agreement commences on and, unless earlier terminated as permitted herein, shall continue through .

Termination for Cause: Either party may terminate immediately upon written notice if the other party materially breaches any obligation and fails to cure within thirty (30) days after receipt of written notice specifying the breach. Termination for insolvency, fraud, or regulatory action affecting the ability to perform may be immediate without cure.

Effect of Termination: Upon termination, ISO shall cease all solicitations and return all confidential materials. Principal shall pay ISO amounts due for services rendered through the effective date of termination subject to offsets for chargebacks and other liabilities.

CONFIDENTIALITY

Each party shall maintain in confidence all non-public information disclosed by the other party that is designated as confidential or that reasonably should be understood to be confidential ("Confidential Information"). Confidential Information shall not include information that: (a) is or becomes publicly available other than by breach of this Agreement; (b) was rightfully known to the recipient prior to disclosure; (c) is lawfully received from a third party without restriction; or (d) is independently developed without use of the disclosing party's Confidential Information.

The receiving party shall not disclose Confidential Information except to employees and contractors who have a need to know and are bound by confidentiality obligations no less protective than those herein. Upon termination or written request, receiving party shall return or destroy Confidential Information. The parties acknowledge that monetary damages may be insufficient and that injunctive relief may be appropriate to prevent further breaches.

COMPLIANCE; REPRESENTATIONS

ISO represents and warrants that it will comply with all applicable laws, card network rules, anti-money laundering and sanctions requirements, and Principal's reasonable policies and procedures related to merchant onboarding and transaction processing. ISO shall not make representations or promises to merchants inconsistent with Principal's programs.

INDEMNIFICATION

Each party shall indemnify, defend and hold harmless the other party from and against any third-party claims, losses, liabilities, damages and expenses (including reasonable attorneys' fees) arising from the indemnifying party's breach of this Agreement, negligence, willful misconduct, or violation of applicable law. The indemnified party shall provide prompt written notice of any claim and reasonably cooperate in the defense.

LIMITATION OF LIABILITY

Except for indemnification obligations and breaches of confidentiality or willful misconduct, neither party shall be liable to the other for consequential, special, incidental, punitive or lost profit damages. Aggregate direct damages shall be limited to the greater of (i) amounts paid or payable to ISO in the twelve (12) months preceding the event giving rise to the claim or (ii) $50,000.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles. Venue for any dispute shall be in the state or federal courts located within that state.

ENTIRE AGREEMENT; AMENDMENT

This Agreement, together with any exhibits and schedules expressly incorporated herein, constitutes the entire agreement between the parties relating to the subject matter and supersedes all prior and contemporaneous agreements and understandings. No amendment shall be effective unless in writing and signed by authorized representatives of both parties.

NOTICES

Notices shall be deemed given when delivered personally, sent by nationally recognized overnight courier, or three (3) business days after deposit in the U.S. mail, postage prepaid, to the addresses set forth above or such other address as either party may specify in writing.

MISCELLANEOUS

Relationship of the Parties: The parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture or employer-employee relationship. ISO shall not bind Principal without prior written consent.

Assignment: Neither party may assign this Agreement except with the prior written consent of the other, except that Principal may assign to an affiliate or successor in connection with a merger or sale of substantially all of its assets.

Principal

Printed Name:

By:

Date:

Title:

Independent Sales Organization (ISO)

Printed Name:

By:

Date:

Title:

Enter text✕

What a Business ISO Agreement Covers

A Business ISO Agreement is a contract used when an Independent Sales Organization (ISO) or reseller provides services to a merchant or vendor on behalf of a payment processor or acquiring bank. The document defines commercial terms, responsibilities for underwriting and chargeback management, fee splits, term and termination, data security obligations, and compliance requirements for card networks and applicable law. It often addresses onboarding steps, service-level expectations, indemnities, and assignment rights. For businesses handling cardholder data or regulated information, the agreement may include specific controls, audit rights, and references to HIPAA or PCI obligations where relevant.

Why this agreement matters for merchants and ISOs

The Business ISO Agreement allocates risk and operational responsibilities that affect payments, compliance, and revenue flow. Clear contract terms reduce onboarding delays, limit exposure to chargebacks and fines, and set enforceable expectations for service delivery and data protection.

Why this agreement matters for merchants and ISOs

Which organizations and roles typically rely on a Business ISO Agreement

Typical users include parties involved in merchant acquiring, payments reselling, or third-party service delivery where fee sharing and compliance are necessary.

  • Merchant owners and finance teams who accept card payments and need clarity on fees and chargeback liability.
  • Independent Sales Organizations and ISO account managers who resell processing services and manage merchant relationships.
  • Legal, compliance, and risk officers at processors or acquirers responsible for underwriting, PCI, and regulatory obligations.

The agreement also serves as a reference for compliance, risk, and operations teams during onboarding and audits.

Step-by-step: completing a Business ISO Agreement

Follow this sequence to prepare the agreement for signature and onboarding with minimal delays.

  • 01
    Gather documents: Collect formation, TIN, and banking authorization documents before drafting.
  • 02
    Complete fields: Fill entity names, fees, effective date, and contact information accurately.
  • 03
    Review compliance: Confirm PCI, AML, and any HIPAA requirements with legal or compliance teams.
  • 04
    Sign and distribute: Obtain authorized signatures and share fully executed copies with stakeholders.

Parallel tasks to keep onboarding on schedule

Use this checklist to manage concurrent activities that speed merchant activation.

01

Underwriting:

Submit financial docs and business profile for risk review.
02

PCI validation:

Confirm merchant PCI-DSS level and remediation steps if required.
03

Bank setup:

Provide ACH authorization and banking details for settlement.
04

Technical integration:

Coordinate API keys, test transactions, and endpoint configuration.
05

Training:

Schedule staff training on chargeback processes and reporting.
06

Monitoring:

Plan post-activation fraud monitoring and alerts.

Where to send the executed agreement and related materials

Route the signed agreement and supporting documents to the parties that require them for onboarding, compliance review, and settlement setup.

  • Processor onboarding: Send executed contract to the acquiring bank or processor onboarding team.
  • ISO records: Retain a signed copy in the ISO's contract repository and compliance file.
  • Merchant file: Give the merchant an executed copy for their records and reconciliation.
  • Compliance review: Provide KYC and underwriting documents to the compliance officer.

Common digital workflow settings for agreement processing

Configure workflow fields and authentication options to match risk and compliance needs.

Field Configuration
Signature type Electronic signature with audit trail
Authentication Email + SMS or KBA for higher-risk merchants
Document retention Encrypted storage for minimum retention period
Bulk send Use bulk templates for multiple merchant onboarding

Digital signing and submission considerations

Determine needed platform capabilities such as audit trails, advanced authentication, and integrations before choosing a signing solution.

  • Audit trail: Capture timestamp, IP, and signer data
  • Advanced auth: Support SMS, KBA, or two-factor methods
  • Integrations: Connect to CRM, ERP, and storage systems

eSignature vendor pricing and compliance snapshot

Compare common vendor starting prices and key compliance features relevant for Business ISO Agreement execution and secure storage.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Security and compliance controls to specify in the contract

Encryption: TLS 1.2/1.3 and AES-256 at rest
Certifications: SOC 2 Type II and ISO 27001
Privacy: CCPA and GDPR compliance options
Healthcare: HIPAA BAA required where PHI is processed
Regulatory: 21 CFR Part 11 support where applicable
Accessibility: WCAG 2.0 Level AA conformance

Key legal and financial risks from errors or omissions

1099 Penalties: $60 / $130 / $330 per form
Intentional Disregard: $660+ per form, no cap
I-9 Violations: $281–$2,789 per violation
Backup Withholding: 24% withholding rate
Chargeback Exposure: Liability shifts if underwriting clauses unclear
Data Breach Costs: Potential fines and remediation expenses

Common mistakes to avoid when preparing the agreement

  • Using informal or ambiguous fee language that leaves settlement and reserve calculation undefined.
  • Failing to identify an authorized signer or using a name variant that doesn't match formation documents.
  • Omitting PCI or BAA obligations when handling cardholder or protected health information.
  • Neglecting to specify notice methods, leading to disputes over termination or fee changes.

Practical tips for accurate and efficient execution

Adopt standard templates and digital workflows to reduce manual errors and accelerate merchant activation.

Use standardized clauses
Standardize fee tables, liability caps, and indemnity language across templates so underwriters and legal can perform faster, consistent reviews and reduce bespoke drafting time.
Require authorized signers
Document corporate authority and attach formation or resolution evidence to avoid disputes about signer capacity and to streamline downstream bank acceptance.
Digitize with audit trails
Use electronic signatures that capture timestamps, IP addresses, and signer authentication to create admissible records and simplify compliance reviews.
Align retention policies
Set retention schedules consistent with IRS, HIPAA, and state rules to avoid premature destruction and to ensure availability for audits or litigation.

Typical timelines and processing expectations

Expect variable review and onboarding times; build checkpoints into your activation project plan.

Underwriting review:

Typically 3–10 business days depending on completeness

PCI validation:

Varies by SAQ level; remediation can extend timeline

Bank setup:

ACH and settlement setup usually 5–15 business days

Technical integration:

API or gateway testing often takes 1–2 weeks

Full activation:

End-to-end onboarding commonly 7–30 business days

Real-world examples: how teams apply the agreement

Two compact case summaries show common scenarios and outcomes when using standardized ISO agreements and eSignature workflows.

Tim Martin — Martin Properties

The team standardized merchant onboarding to reduce manual steps and speed activations.

  • They used e-signatures and templates for leases and merchant forms.
  • The result was faster execution with consistent compliance controls across mobile and desktop signing, improving turnaround without compromising records retention or auditability.

Dan Rotelli — BIS

They prioritized SOC 2 and ESIGN compliance when selecting providers.

  • Emphasis on secure audit trails and access controls.
  • Choosing a provider aligned with those certifications simplified internal approvals, satisfied partners' security requests, and reduced legal review cycles for each merchant engagement.

Frequently asked questions about Business ISO Agreements

Answers to common legal, technical, and operational questions when preparing, signing, and storing the agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users