Business ISO Agreement
What a Business ISO Agreement Covers
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.
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
-
01Gather documents: Collect formation, TIN, and banking authorization documents before drafting.
-
02Complete fields: Fill entity names, fees, effective date, and contact information accurately.
-
03Review compliance: Confirm PCI, AML, and any HIPAA requirements with legal or compliance teams.
-
04Sign and distribute: Obtain authorized signatures and share fully executed copies with stakeholders.
Parallel tasks to keep onboarding on schedule
Underwriting:
PCI validation:
Bank setup:
Technical integration:
Training:
Monitoring:
Where to send the executed agreement and related materials
-
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
| 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
| 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 |
Key legal and financial risks from errors or omissions
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
Typical timelines and processing expectations
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
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
-
Are electronic signatures legally binding?
Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and record retention are satisfied.
-
When is a notary or witness required?
Notarization or witness requirements depend on the document type and state law; deeds, certain powers of attorney, and some state forms may require notarization or witnesses.
-
Do I need a BAA for healthcare data?
Yes. If the agreement or related processing touches protected health information, include a HIPAA business associate agreement and specify safeguards and breach notification procedures.
-
How do I handle signer authentication?
Match authentication strength to risk: email for low risk, SMS or KBA for higher value merchants, and multi-factor for critical approvals.
-
Can I revise the signed agreement later?
Amendments require mutual consent and a signature or execution in the same manner as the original; track versions and preserve prior copies per retention policy.
-
Which signNow plans support bulk onboarding?
Bulk send is available on Business Premium and higher tiers; Site License offers usage-based options for very high volume signature invites.