Merchant Agreement
What a Merchant Agreement Is and when it applies
Why a clear Merchant Agreement matters for operations and risk
A well-drafted Merchant Agreement reduces operational ambiguity, sets measurable performance and fee expectations, allocates liability for fraud and data breaches, and documents remediation steps for chargebacks and disputes. Clear terms support underwriting, compliance with card network rules, and regulatory obligations such as PCI and applicable privacy laws.
Who typically completes or signs a Merchant Agreement
The agreement is completed and signed by roles responsible for payments, compliance, and legal authority within the merchant and by an authorized operations contact at the processor.
- Payments Manager — responsible for transaction setup and reconciliation; provides bank account and reporting contacts.
- CFO or Finance Lead — reviews fee schedules, reserves, and indemnity language before signing.
- Authorized Signer — executive with authority to bind the business to contract terms and bank mandates.
Accurate role identification speeds onboarding and ensures the signer has binding authority to accept fees, reserve terms, and compliance obligations.
Typical signers and their responsibilities
Owner
The business owner or CEO signs for small entities and is responsible for accepting all merchant account terms, fee schedules, and liability clauses. Ensure the person signing is authorized on company formation documents.
CFO
The chief financial officer or finance director reviews settlement timing, reserve requirements, and chargeback procedures, then signs to accept ongoing financial obligations and reporting responsibilities.
Step-by-step: completing the Merchant Agreement
-
01Gather documents: Collect EIN, bank info, and business license
-
02Complete fields: Fill legal name, DBA, and merchant address
-
03Review fees: Confirm processing, chargeback, and reserve terms
-
04Authorized signature: Have an authorized officer sign and date
Online setup: recommended workflow settings
| Field | Configuration |
|---|---|
| Signer Order | Sequential order with merchant last |
| Authentication | Email + SMS code for higher assurance |
| Reminders | Automated reminders at 3 and 7 days |
| Retention | Enable PDF export and audit trail retention |
Where to send the completed Merchant Agreement
-
Processor: Return signed copy to the processor onboarding team
-
Acquiring Bank: Submit account and contract to the acquiring bank
-
Internal Records: Store an execution copy in corporate records
-
Payment Service: Provide signed terms to any third-party PSP
Electronic signing and file-format requirements
Merchant Agreements should be executed in a format that preserves signatures, timestamps, and a complete audit trail.
- File Types: PDF and DOCX accepted
- Audit Trail: IP, timestamp, and action log
- Integrations: CRM and accounting system sync
Typical timelines and processing expectations
Application submission:
Provide completed agreement and docs immediately
Underwriting review:
Usually 3–10 business days
Account activation:
Often within 1–5 business days after approval
Reserve periods:
Held per contract, often 90–180 days
Fee disputes:
Investigations may add 15–45 days
Common mistakes that delay merchant onboarding
- Submitting mismatched legal names or TINs can trigger verification failures and onboarding delays with the acquiring bank.
- Incomplete or inaccurate bank account information causes failed settlements and manual reconciliation work for finance teams.
- Omitting expected disclosures about restricted products or high-risk categories leads to immediate underwriting exceptions or account holds.
- Failing to disclose third-party gateways or reseller relationships causes compliance gaps and potential contract breaches.
Penalties and operational risks from errors or breaches
Real-world examples of Merchant Agreement use
Tech Data — Enterprise integration
Tech Data streamlined contract execution to align payments with enterprise systems.
- Integration reduced manual handoffs.
- The signed Merchant Agreement enabled faster invoice-to-cash cycles and clearer liability allocation between processor and reseller, improving reconciliation and internal controls across multiple business units.
Fertility Centers — Healthcare compliance
Fertility Centers required strict PHI safeguards in processing agreements.
- A BAA was attached.
- The executed Merchant Agreement clarified encryption, breach reporting, and audit obligations, ensuring card processing activities met clinical privacy requirements while allowing patient payments to be accepted online.
Practical tips for accurate and efficient completion
eSignature vendor pricing and capability snapshot for Merchant Agreement execution
| 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 | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
FAQs: execution, enforceability, and e-signature questions
-
Is an electronic signature legally binding?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws. Ensure intent, consent, attribution, and retention are demonstrable to satisfy legal validity.
-
Do consumer disclosures apply?
If the agreement creates consumer-facing electronic records (financial or consumer-credit related), ESIGN requires a clear consent disclosure and a mechanism to withdraw consent per 15 U.S.C. §7001(c).
-
When is notarization required?
Most Merchant Agreements do not require notarization. If a state or specific bank requires a notarized or witnessed signature for a particular clause, follow that requirement; RON may be acceptable where permitted.
-
What if the signer’s name differs from legal records?
Mismatched signer names or TINs can cause underwriting delays or trigger backup withholding. Provide corrective documentation or an officer certification to reconcile differences.
-
How long should I retain the signed agreement?
Retain signed Merchant Agreements for the active contract term plus a minimum of three years; follow industry-specific or federal retention rules (IRS, HIPAA) where applicable.
-
Can I use click-to-sign or checkbox consent?
Yes, provided you capture intent, consent, and an audit trail linking the action to the signer. For higher-assurance needs, add multi-factor authentication or certificate-based signatures.