Merchant Services Agreement
What a Merchant Services Agreement Covers
Why a Clear Agreement Matters for Card Acceptance
A well-drafted Merchant Services Agreement reduces operational risk, clarifies fee structures, and limits disputes over chargebacks and reserves. It sets expectations for settlement timing, security obligations, and termination mechanics so both parties can manage cash flow and compliance with card network rules.
Who Typically Prepares or Signs This Agreement
Each signer should have authority to bind the organization and understand financial, operational, and compliance implications before execution.
- Small and medium merchants seeking card processing with defined fees and settlement terms.
- Financial and payments teams at larger merchants handling underwriting, reconciliation, and chargeback management.
- Payment processors, ISOs, and acquiring banks that onboard merchants and enforce PCI/network rules.
Step-by-Step: Completing a Merchant Services Agreement
-
01Collect company data: Assemble legal name, EIN, bank info.
-
02Confirm processing details: Specify transaction types and average ticket.
-
03Review fee schedule: Check interchange, processor, and assessed fees.
-
04Authorize and sign: Ensure an authorized officer signs with date.
How to Configure the Agreement for Online Completion
| Document Field | Configuration Setting | Notes | Field name | Required/Optional | Validation or guidance |
|---|---|
| Signature field placement and properties | Signature | Required | Timestamped |
| Initials for page acknowledgment | Initials | Optional | Each page initial |
| Bank account verification instruction | Text block | Required | Micro-deposit check |
| Underwriting checklist routing rule | Routing | Required | Route to underwriting queue |
Where to Send Signed Agreements and Next Steps
-
Merchant copy: Provide fully executed PDF to merchant for records.
-
Underwriting: Send to underwriting team for account activation.
-
Finance / accounts payable: Share fee schedule and settlement terms with finance.
-
Processor record: Retain in processor archive for audit trail.
Technical Requirements for Digital Completion and Storage
Confirm the solution can produce a tamper-evident signed PDF and a detailed certificate of completion for compliance and audit purposes.
- File formats: PDF, DOCX accepted
- Integration options: Salesforce, NetSuite, Google Workspace
- Security capabilities: TLS, AES-256 encryption
Typical Timelines and Processing Expectations
Underwriting turnaround time:
Usually 3–10 business days
Settlement schedule:
Daily batching; funds in 1–3 business days
Reserve review period:
30–180 days depending on risk
Dispute/chargeback response:
Typically 7–30 days to respond
Agreement notice periods:
Termination often requires 30–90 days' notice
Common Mistakes That Delay Merchant Onboarding
- Submitting inconsistent names between the Merchant Services Agreement and tax records, causing EIN verification failures and underwriting delays.
- Leaving bank routing or account numbers unverified, leading to failed settlements and additional manual remediation steps.
- Failing to disclose high-risk transaction types or cross-border processing, which can trigger holds, higher reserves, or application rejection.
- Using vague descriptions for processing volume or chargeback mitigation plans, which can cause conservative reserve and fee settings.
Key Risks and Financial Consequences
eSignature Vendor Pricing and Feature Snapshot for This Agreement
| 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 |
Real-World Examples of Merchant Agreement Use
Optica Ventures
Optica used an executed Merchant Services Agreement to standardize settlement terms across stores
- Reduced chargeback response time by centralizing dispute handling
- The company reported faster reconciliations and clearer responsibilities between merchant and processor after standardizing contract language.
Tech Data
Tech Data updated fee schedules in a master Merchant Services Agreement
- Implemented tiered pricing by transaction volume
- The revision clarified billing cycles and reduced billing disputes between finance teams and the processor.
Practical Tips for Accurate and Efficient Completion
Frequently Asked Questions About Merchant Services Agreements
-
Can this agreement be signed electronically?
Yes. Electronic signatures are legally binding under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention are satisfied.
-
Is notarization required for validity?
Most merchant services agreements do not require notarization. If a state or specific banking requirement requests notarization, follow the applicable state notary rules or RON procedures where allowed.
-
Who should sign for a corporation?
An authorized officer or agent with signatory authority should execute the agreement. Verify board or corporate resolutions if required to confirm signing authority.
-
What happens if bank details are wrong?
Incorrect routing or account numbers can lead to failed deposits or delays. Confirm bank verification or micro-deposit procedures before relying on automated settlements.
-
How are chargebacks managed contractually?
The agreement typically sets merchant responsibilities for disputes, timelines for response, and potential liabilities; maintain clear dispute-resolution procedures with required documentation.
-
Does eSigning meet PCI and HIPAA needs?
E-signatures can be used while maintaining PCI and HIPAA obligations, but ensure the platform supports encryption and BAAs where HIPAA applies and that PCI scope is managed.