Are electronically signed merchant agreements legally enforceable?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA adoption, electronic signatures are generally legally valid when intent, consent, attribution, and record retention are present.

When is a written notarization required?

Most merchant agreements do not require notarization. If a specific state or transaction type demands notarization, the agreement should state that requirement and follow the state's notary rules.

Who must sign the agreement on behalf of the merchant?

An individual with authority to bind the legal entity must sign; include title and capacity. Corporations often provide a board resolution or certificate of incumbency when requested.

How can I revoke or cancel the merchant agreement?

Follow termination clauses in the agreement, which typically require notice and cure periods. Immediate termination may be allowed for fraud or material breach per the contract terms.

What supporting documents should I attach?

Common attachments include formation documents, EIN verification, voided check or bank letter, government ID for authorized signer, and proof of DBA where applicable.

Can consumer-facing disclosures be provided electronically?

Yes, but consumer-facing financial disclosures require an ESIGN disclosure and a consent process that demonstrates the recipient can access and retain electronic records in accordance with 15 U.S.C. §7001(c).

Electronic Signature
Templates
Finance
Financial Merchant Agreement

Financial Merchant Agreement

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

FINANCIAL MERCHANT AGREEMENT

This Financial Merchant Agreement ("Agreement") is entered into on the day of , by and between:

Parties

Merchant Legal Name Merchant Address Merchant Contact (phone / email) Processor / Financial Services Provider Processor Address

Entity Type and Identification

Merchant Entity Type: Corporation Limited Liability Company (LLC) Partnership Sole Proprietorship

Merchant Tax Identification Number / EIN

Recitals

WHEREAS, Merchant operates a business that accepts payment card and other electronic payment methods for goods and/or services; and

WHEREAS, Processor provides payment processing, settlement, and related financial services under the terms set forth below.

Definitions

For purposes of this Agreement, capitalized terms not otherwise defined shall have the meanings set forth in this section and throughout the Agreement. "Chargeback" means a disputed transaction returned by an issuer or card network to Processor. "Settlement" means the transmission of funds to Merchant in accordance with the Settlement Terms.

Services and Scope

Processor shall furnish Merchant with payment processing services, including authorization, clearing and settlement of electronic payment transactions, chargeback processing, and reporting as described herein. Processor's obligation is limited to services expressly set forth in this Agreement; ancillary services may be provided subject to additional terms and fees.

Description of Processing Services

Fees, Charges, and Settlement

Merchant shall pay Processor the fees set forth below. Fees are exclusive of taxes unless otherwise stated. Processor may change fees upon prior written notice as permitted by this Agreement.

Processing Fee (percentage per transaction) Transaction Fee (flat per transaction) Monthly/Account Fee Reserve / Hold Amount (if applicable) Chargeback Fee

Settlement Instructions

Settlement Bank Name Routing Number Account Number Settlement Cycle

Chargebacks, Refunds, and Disputes

Merchant shall maintain accurate records and comply with all issuer, card brand and network rules. Merchant is responsible for responding to chargebacks and must supply requested documentation within the timeframes required by the card networks. Processor reserves the right to debit Merchant account for chargebacks, fees, and associated costs.

Chargeback Hold Period (days)

Compliance and Security

Merchant agrees to comply with all applicable payment card industry standards, data security standards, and applicable laws and regulations. Merchant shall implement and maintain reasonable safeguards to protect cardholder data and shall notify Processor promptly of any security breach affecting payment data.

Merchant acknowledges that failure to maintain compliance may result in termination, fines, or assessment of remediation costs.

Merchant Acknowledges PCI Compliance

Merchant represents and warrants that it will maintain required PCI DSS compliance and any applicable data security standards.

Representations, Warranties and Covenants

Each Party represents and warrants that it has full power, authority and legal right to enter into and perform its obligations under this Agreement. Merchant represents that all transactions submitted are bona fide and comply with applicable law. Processor represents that it is authorized to provide the services described herein.

Indemnification and Limitation of Liability

Merchant shall indemnify, defend and hold Processor harmless from and against any and all claims, liabilities, losses, damages, costs and expenses (including reasonable attorneys' fees) arising out of Merchant's breach of this Agreement, negligent or willful misconduct, or violation of applicable laws. Processor's liability for direct damages shall be limited to actual direct damages up to the aggregate amount of fees paid to Processor in the preceding six (6) months. Neither Party shall be liable for incidental, consequential, punitive or special damages.

Limitation of Liability Amount

Term, Renewal and Termination

This Agreement shall commence on the Effective Date and remain in effect for an initial term of months, and shall automatically renew for successive terms of the same duration unless either Party provides written notice of termination at least days prior to the end of the then-current term. Processor may terminate immediately for material breach, fraud, or network rule violations.

Confidentiality

Each Party shall treat the other Party's Confidential Information as proprietary and shall not disclose such information except as required by law or as necessary to perform obligations under this Agreement. Confidential Information excludes information that is publicly available through no breach of this Agreement.

Audit Rights and Records

Processor may audit Merchant's compliance with this Agreement and card network rules upon reasonable notice during normal business hours. Merchant shall retain transaction records and supporting documentation for a minimum of months and shall provide copies upon request.

Governing Law and Notices

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. All notices required under this Agreement shall be in writing and delivered to the addresses listed below.

Notice to Merchant (address for legal notice) Notice to Processor (address for legal notice)

Miscellaneous

This Agreement, together with any schedules and addenda executed by the Parties, constitutes the entire agreement between the Parties and supersedes all prior agreements relating to the subject matter hereof. No amendment shall be effective unless in writing and signed by authorized representatives of both Parties.

Additional Terms / Special Instructions

Signatures

Merchant Printed Name:

By:

Date:

Processor Printed Name:

By:

Date:

What the Financial Merchant Agreement Is and Why it Matters

A Financial Merchant Agreement is a written contract between a merchant and a payments provider, acquiring bank, or payment facilitator that sets the terms for card and electronic payments. It typically defines parties, merchant responsibilities, permitted payment types, settlement timing, fees, reserve requirements, chargeback and dispute processes, data security obligations (including PCI compliance), and termination rights. The agreement records operational rules for processing transactions, fraud mitigation, and funding, and it establishes who bears which financial and regulatory risks during the business relationship.

Why a Clear Financial Merchant Agreement Protects Both Parties

A well-drafted Financial Merchant Agreement reduces ambiguity about fees, chargebacks, reserves, and data responsibilities, which lowers dispute risk and supports regulatory compliance. It also documents operational expectations for settlement timing, reporting, and security controls to help both merchant and processor limit exposure.

Who Typically Uses a Financial Merchant Agreement

Different organizations need merchant agreements to set payment and risk rules before processing begins.

Retail and e-commerce merchants that accept card or ACH payments and need settlement, chargeback, and fee terms clarified.
SaaS platforms and marketplaces that act as payment facilitators or require sub-merchant onboarding and underwriting rules.
Acquirers, independent sales organizations, and payment processors who underwrite merchants and enforce risk and compliance controls.

The agreement aligns expectations across finance, operations, and compliance stakeholders while documenting remedies and termination conditions.

Key Parties and Typical Roles

Merchant Owner

Small-business owner or corporate payments lead responsible for providing accurate business identity, bank account details, and supporting KYC documents. They must ensure operational compliance with chargeback handling, refunds, and any required PCI scope-reduction steps.

Acquirer / Processor

The acquiring bank or payment processor that underwrites the merchant, sets reserve and fee arrangements, enforces PCI and fraud controls, and handles settlement and chargeback flows under the contract terms.

Core Sections a Professional Merchant Agreement Should Include

A complete Financial Merchant Agreement addresses both commercial and operational topics so parties can process payments with predictable responsibilities and controls.

Parties & Definitions

Clearly identify legal entities, doing-business-as names, and define key terms such as 'Chargeback', 'Settlement', 'Reserve', and 'Authorized Transactions' to avoid later interpretation disputes.

Payment and Settlement Terms

Specify accepted payment methods, settlement schedule, funding delays, and cutoff times, including when transactions post to merchant accounts and how currency conversion or refunds are handled.

Fees, Reserves and Holds

Detail monthly fees, per-transaction fees, rolling reserves, minimums, and conditions that trigger holds or reserve increases to give merchants predictable cost expectations.

Chargebacks and Fraud Handling

Describe dispute procedures, merchant obligations to produce evidence, timelines for response, and financial responsibility for chargebacks and fraudulent or unauthorized transactions.

Data Security and Compliance

Allocate PCI DSS responsibilities, encryption and storage rules for cardholder data, and any data-handling obligations to satisfy applicable law and card brand rules.

Termination and Remedies

Provide termination triggers, cure periods, final settlement mechanics, indemnities, limitation of liability, and post-termination data retention or return obligations.

Step-by-Step: Prepare, Complete, and Execute the Agreement

A clear sequence reduces processing time: gather documents, fill fields, verify identity, and distribute executed copies.

01

Collect documents: Gather formation docs, EIN letter, and KYC ID.
02

Complete form: Enter bank, fee, and settlement details accurately.
03

Attach support: Upload voided check and ownership verification documents.
04

Sign and distribute: Execute signatures and provide copies to finance and processor.

How to Configure an Online Signing and Onboarding Workflow

Set workflow options to match underwriting and compliance requirements before sending the agreement for signature.

Field	Configuration
Signer authentication	Email + SMS code or KBA for high-risk merchants
Payment processing	Connect gateway API and settlement account for verification
Document retention	Set retention period and export PDF/A for archival
Notifications	Enable signer reminders and finance team alerts

Where to Send, File, and Store the Signed Agreement

Routing ensures underwriting, legal, and accounting receive the executed agreement and supporting records.

Acquiring bank: Send executed copy to the acquirer for underwriting files.
Payment processor: Provide contract and bank details to enable settlement setup.
Merchant records: Store a signed copy in accounting and contract management systems.
Compliance archive: Retain evidence for audits and regulatory requests.

Digital Signing and Integration Requirements

Choose a platform that supports secure eSignature, audit trails, and your existing integrations to streamline onboarding.

Document formats: PDF and DOCX are standard for signed agreements.
Integrations: Salesforce, NetSuite, Google Workspace, and Box simplify routing and storage.
Security and compliance: Use TLS and AES encryption and confirm HIPAA BAA if needed.

Ensure the platform supports in-person and remote signatures, audit trails, conditional fields, and API access to automate execution and retention for compliance purposes.

eSignature vendor comparison for executing Financial Merchant Agreements

Basic pricing and compliance features influence cost and suitability when executing high-volume merchant agreements; signNow appears first for direct feature comparison.

	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	Yes	Yes	Yes	Yes
Bulk Send	Yes	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Security and Data Elements Typically Included

PCI obligation: Cardholder protection required

EFT authorization: Bank debit/credit authorization

Bank details: Routing and account numbers

Reserve terms: Reserve percentage and triggers

Chargeback policy: Dispute handling rules

KYC documents: Ownership and identity proofs

Common Financial and Compliance Risks to Watch

Contract disputes: Missed obligations, financial exposure

Chargeback losses: Increased refunds and fees

Regulatory fines: Noncompliance with payment laws

Fraud liability: Unauthorized transactions cost merchant

Data breaches: PCI scope and breach costs

Bank holds: Reserve increases and funding delays

Frequent Preparation Errors to Avoid

Providing incorrect bank routing or account numbers delays settlement and can trigger return fees that slow merchant funding.
Failing to identify an authorized signer causes underwriters to reject the contract or request additional proof of authority.
Using vague fee descriptions or undefined chargeback handling terms creates disputes and ambiguous liability during collections.
Omitting PCI and data-handling language leaves unclear responsibilities and increases exposure in the event of a breach.

Practical Tips for Accurate and Efficient Completion

Follow these best practices to reduce onboarding time, support compliance, and simplify future audits or disputes.

Centralize supporting documents

Keep a single folder with formation documents, EIN verification, voided check, and identity documents so you can attach consistent, verified materials during onboarding and avoid repeated requests.

Standardize fee schedules

Use a clear, itemized fee table with examples for common transaction sizes to reduce negotiation friction and prevent later disputes over ambiguous language.

Limit authorized signers

Designate a small list of authorized signers with titles in the agreement and require corporate resolution or POA if signing authority deviates from recorded roles.

Document change control

Track amendments with dated addenda and initials; require the same signing procedure for changes as for the original to preserve enforceability.

Frequently Asked Questions About Financial Merchant Agreements

Answers to common legal and operational questions help clarify enforceability, signing authority, and document management for merchant agreements.

Need help? Contact support

Are electronically signed merchant agreements legally enforceable?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA adoption, electronic signatures are generally legally valid when intent, consent, attribution, and record retention are present.
When is a written notarization required?
Most merchant agreements do not require notarization. If a specific state or transaction type demands notarization, the agreement should state that requirement and follow the state's notary rules.
Who must sign the agreement on behalf of the merchant?
An individual with authority to bind the legal entity must sign; include title and capacity. Corporations often provide a board resolution or certificate of incumbency when requested.
How can I revoke or cancel the merchant agreement?
Follow termination clauses in the agreement, which typically require notice and cure periods. Immediate termination may be allowed for fraud or material breach per the contract terms.
What supporting documents should I attach?
Common attachments include formation documents, EIN verification, voided check or bank letter, government ID for authorized signer, and proof of DBA where applicable.
Can consumer-facing disclosures be provided electronically?
Yes, but consumer-facing financial disclosures require an ESIGN disclosure and a consent process that demonstrates the recipient can access and retain electronic records in accordance with 15 U.S.C. §7001(c).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now