Establishing secure connection…Loading editor…Preparing document…

Merchant Agreement

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

MERCHANT AGREEMENT

This Merchant Agreement ("Agreement") is entered into as of by and between Merchant Name: with principal place of business at , and Provider Name: with principal place of business at .

WHEREAS

WHEREAS, Merchant operates an e-commerce and/or point-of-sale business and desires to engage Provider to facilitate payment processing, transaction routing, and related merchant services on the terms set forth herein.

WHEREAS, Provider is duly authorized and capable of providing payment processing services, settlement, risk management, and technical integration services and is willing to provide such services to Merchant pursuant to this Agreement.

SCOPE OF SERVICES

Provider shall provide merchant acquiring and payment processing services including, but not limited to, transaction authorization, clearing and settlement, chargeback handling, reporting, and technical integration necessary for Merchant to accept card-based and electronic payments in accordance with this Agreement.

PAYMENT TERMS

Fees and charges payable by Merchant to Provider shall include processing fees, transaction fees, and any other charges expressly set forth in this Agreement. Provider is authorized to deduct fees from settlement amounts in accordance with the terms below.

TERM AND TERMINATION

This Agreement commences on the Start Date and, unless earlier terminated in accordance with this Agreement, shall continue until the End Date or until terminated by either party upon the required notice.

Either party may terminate this Agreement immediately for material breach by the other party that remains uncured for thirty (30) days after written notice of such breach. Provider may suspend processing immediately if Merchant presents elevated risk of fraud, violates card brand rules, or otherwise jeopardizes settlement or chargeback exposure.

CONFIDENTIALITY

Each party shall treat as confidential all non-public information disclosed by the other party in connection with this Agreement, including business terms, technical materials, pricing, financial and customer information ("Confidential Information"). Confidential Information shall not include information that (a) is or becomes generally available to the public other than by breach of this Agreement, (b) was in the receiving party's possession prior to disclosure by the disclosing party, or (c) is rightfully obtained from a third party without restriction. The receiving party shall protect Confidential Information with at least the same degree of care it uses to protect its own confidential information, but in no event less than reasonable care.

COMPLIANCE, SECURITY AND REPRESENTATIONS

Merchant represents and warrants that its business and transactions comply with applicable law and card brand rules. Merchant shall maintain required security standards including applicable payment card industry standards and shall cooperate with Provider in any security reviews or remediation. Provider shall perform services in compliance with applicable laws and industry standards but does not guarantee settlement of transactions not compliant with card brand rules.

CHARGEBACKS, RESERVES AND INDEMNIFICATION

Merchant shall be responsible for chargebacks, refunds, and disputes arising from its transactions. Provider may establish reserves, holds, and chargeback procedures in its reasonable discretion to cover potential liabilities. Merchant shall indemnify and hold harmless Provider, its affiliates and agents from and against any losses, claims, damages, fines, and expenses arising from Merchant's breach of this Agreement, fraudulent activity, or failure to comply with applicable law.

LIMITATION OF LIABILITY

Except for willful misconduct or gross negligence, neither party shall be liable for incidental, special, punitive, or consequential damages, and Provider's aggregate liability arising out of or relating to this Agreement shall not exceed the total fees paid by Merchant to Provider in the twelve (12) months preceding the claim.

RECORDS, AUDIT RIGHTS

Merchant shall retain records necessary to substantiate transactions and compliance with this Agreement for a period of and shall provide such records to Provider upon reasonable request for audit or investigation purposes.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. The parties submit to the exclusive jurisdiction of the state and federal courts located in that State for disputes.

ENTIRE AGREEMENT

This Agreement, together with any exhibits, schedules, and accepted onboarding documentation, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings, proposals, negotiations, and agreements, whether written or oral. No amendment shall be effective unless made in writing and signed by authorized representatives of both parties.

NOTICES

MISCELLANEOUS

Assignment: Neither party may assign this Agreement without the prior written consent of the other, except that Provider may assign to an acquirer or affiliate in connection with an acquisition or change of control. Severability: If any provision is held unenforceable, the remainder will remain in full force and effect. Waiver: Failure to enforce any right is not a waiver.

Merchant Printed Name:

By:

Date:

Provider Printed Name:

By:

Date:

Enter text✕

What a Merchant Agreement Is and when it applies

A Merchant Agreement is a contract between a merchant and a payment processor, acquiring bank, or service provider that sets out the terms for card acceptance, transaction processing, fees, chargeback handling, settlement timing, security obligations, and termination. It typically covers obligations of both parties, PCI and data-security requirements, reserve or holdback provisions, prohibited activities, and reporting. Merchants use this agreement when onboarding to accept credit or debit card payments, to change processors, or to document new product or distribution channels tied to payment processing.

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.

Why a clear Merchant Agreement matters for operations and risk

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.

Required data commonly requested in the agreement

Legal Business Name: Exact registered name
Doing Business As: DBA name if applicable
Tax ID / EIN: Employer Identification
Primary Contact: Name, email, phone
Bank Account Details: Routing and account numbers
Processing Volumes: Average monthly volume

Step-by-step: completing the Merchant Agreement

Follow this sequence to reduce errors and accelerate approval when submitting a Merchant Agreement to a processor or acquiring bank.

  • 01
    Gather documents: Collect EIN, bank info, and business license
  • 02
    Complete fields: Fill legal name, DBA, and merchant address
  • 03
    Review fees: Confirm processing, chargeback, and reserve terms
  • 04
    Authorized signature: Have an authorized officer sign and date

Online setup: recommended workflow settings

Configure these workflow options when preparing the agreement for e-signature to ensure compliant execution and auditability.

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

Routing depends on whether you are onboarding with a processor, updating terms with an acquirer, or documenting a reseller arrangement.

  • 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

Expect variable review times depending on underwriting depth, risk profile, and required supporting documents.

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

Chargeback Liability: Merchant pays chargebacks
Reserve Withholding: Funds held as security
Termination: Account closure and loss of processing
Regulatory Fines: PCI or privacy penalties
Tax Withholding: Backup withholding 24%
Reputational Risk: Customer trust erosion

Real-world examples of Merchant Agreement use

These case summaries show how organizations use Merchant Agreements to accelerate onboarding and maintain compliance while integrating payment workflows.

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

Adopt these practices to reduce review cycles and downstream disputes when preparing a Merchant Agreement.

Standardize templates
Use a single vetted template that includes required disclosures and aligns with your bank’s underwriting checklist to prevent version conflicts and expedite approvals.
Verify identity
Confirm signer authority with corporate records or board resolution before submission to avoid execution challenges and potential non-enforceability.
Document volumes
Provide realistic monthly and peak processing estimates; accurate volume data prevents surprise reserve adjustments and helps the processor size fraud monitoring rules.
Preserve audit trail
Retain signed PDFs and detailed audit logs (IP, timestamp, signer email) so you can resolve disputes and demonstrate proper execution in regulatory or network investigations.

eSignature vendor pricing and capability snapshot for Merchant Agreement execution

Comparing common eSignature vendors can help procurement choose a solution that meets cost, compliance, and volume needs for executing Merchant Agreements.

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

Answers to common questions about validity, signing methods, and document retention for Merchant Agreements.


Need help? Contact support

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