Can this agreement be signed electronically?

Yes. Electronic signatures are legally valid in the United States under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states. Ensure the signing method demonstrates intent, consent, attribution, and reliable record retention to meet the ESIGN four‑part test.

Is notarization required for merchant agreements?

Typically no for ordinary merchant agreements. Notarization may be needed for related instruments (deeds, powers of attorney) or per state-specific requirements; confirm if a counterparty or bank requests notarized signature or a wet‑notary acknowledgment.

What authentication strength should be used?

For standard risk merchants, email plus SMS OTP is common. For higher-risk merchants or regulatory requirements, use knowledge-based ID proofing, photographic ID analysis, or multi-factor authentication to strengthen signer attribution.

How do I correct a signed mistake?

Execute an amendment signed by the same authorized parties, or void and re-execute a corrected agreement. Record the correction and maintain all versions with time-stamped audit logs for auditability.

What if parties have different governing law preferences?

Negotiate the governing law clause before signature. If the parties cannot agree, processors often default to their home state or customer’s primary business state; unresolved conflicts can delay onboarding.

Where should executed agreements be stored?

Store executed copies with the platform audit trail in an access-controlled repository. Maintain retention per applicable laws (IRS, HIPAA where relevant) and ensure records are exportable for audits or regulatory requests.

Electronic Signature
Templates
Miscellaneous
Merchant Agreement MPA Test

Merchant Agreement MPA Test

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

Merchant Agreement MPA Test

Parties

Merchant Legal Name Service Provider / Acquirer Legal Name

This Merchant Processing Agreement (the Agreement) is entered into as of (Effective Date), by and between (Merchant) and (Provider).

WHEREAS

WHEREAS, Merchant conducts business selling goods and/or services to consumers and desires to accept card-based and other electronic payments; and

WHEREAS, Provider is engaged in the business of payment processing and acquiring and has the technical, operational and regulatory capacity to provide processing services to Merchant subject to the terms of this Agreement; and

NOW, THEREFORE, in consideration of the mutual covenants contained herein, the parties agree as follows.

Scope of Work

Services to Be Provided

Merchant engages Provider to perform payment authorization, capture, settlement, chargeback management, reporting, and related services as described in the Services to Be Provided. Provider shall perform services in a commercially reasonable manner in accordance with industry standards and applicable law.

Payment Terms

Fees and Consideration Payment Schedule Late Fee / Interest on Overdue Amounts

Unless otherwise agreed in writing, all fees are due in accordance with the Payment Schedule. Provider may offset any amounts owed to Merchant against fees, chargebacks, and indemnified losses. Merchant is responsible for all taxes related to amounts due under this Agreement, excluding taxes based on Provider's net income.

Term and Termination

The term of this Agreement shall commence on and shall continue until unless earlier terminated as provided herein.

Termination Notice Period

Either party may terminate this Agreement for convenience by providing the other party the notice specified above. Either party may terminate immediately for material breach by the other party, insolvency, or regulatory prohibition. Termination shall not relieve either party of obligations accrued prior to termination.

Confidentiality

"Confidential Information" means non-public information disclosed by one party to the other, including business, financial, technical, transaction and cardholder data. Each receiving party shall (i) use Confidential Information only for the performance of this Agreement, (ii) restrict disclosure to its employees, agents and subcontractors with a need to know and ensure they are bound by confidentiality obligations at least as protective as this clause, and (iii) protect Confidential Information with at least reasonable care.

Confidential Information does not include information that is: (a) in the public domain other than through breach of this Agreement; (b) rightfully received from a third party without restriction; or (c) independently developed without use of the disclosing party's Confidential Information. Upon termination or request, receiving party shall return or destroy Confidential Information and certify such destruction upon request.

Breach of this confidentiality provision may cause irreparable harm for which monetary damages are inadequate; the disclosing party shall be entitled to seek injunctive relief in addition to any other remedies.

Indemnification

Each party shall indemnify, defend and hold harmless the other party from and against any third-party claims, losses, liabilities, damages, and expenses (including reasonable attorneys' fees) arising from the indemnifying party's gross negligence, willful misconduct, breach of this Agreement, or violation of law in connection with the performance of its obligations hereunder.

Governing Law

Governing Law State

This Agreement shall be governed by and construed in accordance with the laws of the state specified above without regard to conflict of law principles. The parties consent to the exclusive jurisdiction of the courts located in that state for disputes arising under this Agreement, except where injunctive or other equitable relief is sought.

Entire Agreement

This Agreement, including any exhibits and appendices attached hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous negotiations, agreements and understandings, whether written or oral. No amendment or waiver shall be effective unless in writing and signed by both parties.

Miscellaneous

Neither party may assign its rights or obligations under this Agreement without the prior written consent of the other party, except to an affiliate or in connection with a sale of substantially all assets or a merger. If any provision of this Agreement is held invalid, the remainder shall continue in full force and effect.

Signatures

Merchant:

By:

Date:

Provider:

By:

Date:

What the Merchant Agreement MPA Test Is

The Merchant Agreement MPA Test is a standardized merchant services contract template used to document terms between a merchant and a payment processor or acquiring bank. It defines parties, scope of services, fee schedules, chargeback and dispute procedures, data handling and security obligations, termination rights, and governing law. Organizations use this form to confirm pricing, PCI and data-protection responsibilities, and signature authority before enabling merchant accounts. The MPA Test can be completed as a traditional paper agreement or executed electronically using an ESIGN/UETA-compliant platform.

Why a Clear Merchant Agreement Matters

A well-prepared Merchant Agreement reduces payment disputes, clarifies liability for fraud or chargebacks, and documents compliance responsibilities such as PCI and data retention. Clear terms support operational onboarding and reduce downstream reconciliation and audit friction.

Who Typically Prepares and Signs This Form

Use appropriate signatory authority and retain executed copies for audit, underwriting, and tax purposes.

Small and mid-size merchants who accept card and ACH payments; need documented processor terms and fee schedules.
Payment processors and acquiring banks; require completed agreements to enable merchant accounts and manage underwriting risk.
Legal, risk, and finance teams; verify contract language, fee calculations, and indemnity clauses prior to signature.

Core Components of the Merchant Agreement MPA Test

The agreement typically includes operational, financial, compliance, and legal sections that define responsibilities, security expectations, and dispute processes.

Parties

Full legal names and entity types for merchant and processor, including EIN or tax ID where applicable to support tax and compliance checks.

Services

Detailed description of payment acceptance methods, transaction types (card, ACH), gateway access, settlement timing, and supported currencies or card brands.

Fees

Clear fee schedule: interchange passthrough, processor markup, monthly or per-transaction fees, chargeback fees, and any minimums or reserves.

Risk & Chargebacks

Procedures for chargeback handling, dispute timelines, merchant reps and warranties, reserve requirements, and conditions for withholding funds.

Data & Security

PCI compliance obligations, encryption or tokenization requirements, breach notification timings, and data retention or deletion policies.

Termination & Law

Termination notice periods, post-termination settlement, indemnities, limitation of liability, and governing state law for dispute resolution.

Stepwise Completion Checklist

Complete the agreement in this sequence to streamline review and minimize back-and-forth with the processor.

01

Gather Documents: Collect EIN, articles, voided check, and underwriting paperwork.
02

Fill Core Fields: Enter party names, address, TIN, and effective date.
03

Review Fees: Confirm interchange, markups, and chargeback charges.
04

Sign and Deliver: Execute by authorized signer and transmit to processor.

Configuring an Online Completion Workflow

Set up a digital workflow that enforces required fields, signer order, and authentication to reduce processing errors.

Field	Configuration
Required Fields	Make legal name, TIN, and signature mandatory
Signer Order	Set merchant to sign first, processor to countersign
Authentication	Use email + SMS code or stronger ID proofing for high-risk merchants
Retention	Enable automatic archival in PDF/A with audit trail

Where to Send the Completed Agreement

Route the executed MPA Test to the correct processor team to avoid delays in merchant onboarding and funding.

Underwriting Inbox: Processor underwriting reviews KYC and underwriting documents.
Risk Team: Risk verifies high-risk product descriptions and chargeback history.
Merchant Services: Enablement team configures merchant account settings.
Accounting/Settlement: Finalize funding schedule and reserve parameters.

Digital Signing and Platform Requirements

Ensure the selected platform supports retention, audit logs, and, if required, a Business Associate Agreement for HIPAA compliance.

Authentication: Email, SMS, or stronger ID proofing
Audit Trail: Capture IP, timestamp, and signer actions
Document Formats: PDF and DOCX support recommended

Representative eSignature Vendor Comparison for Executing the MPA Test

Comparing common vendor pricing and baseline capabilities helps determine which platform matches your compliance and volume needs.

	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 trial, no card	Varies	Varies	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA)	Yes	Yes	No	No

Security and Compliance Controls to Include

Encryption: TLS 1.2/1.3; AES-256 at rest

Audit Trail: Signed event log with timestamps

Access Controls: Role-based permissions and MFA

HIPAA Support: BAA available when PHI involved

Certifications: SOC 2 Type II, ISO 27001

Regulatory: 21 CFR Part 11 and PCI DSS support

Key Risks and Potential Penalties

Breach of Contract: Damages and indemnity exposure

Unenforceability: Missing signature or authority

Backup Withholding: 24% withholding for incorrect TIN

Regulatory Fines: PCI or data-protection penalties

Chargeback Losses: Reserve draws and fee exposure

Reputational: Customer trust and settlement delays

Common Preparation Mistakes to Avoid

Using an informal or trade name instead of the legal entity name delays underwriting and may invalidate authority.
Leaving the effective date blank or inconsistent between pages creates ambiguity for fee accruals and notice deadlines.
Failing to attach required underwriting documents such as voided checks, articles, or KYC materials causes processing delays.
Not specifying settlement timing or reserve terms leads to disputes over holds and funding schedules.

Real-World Examples of MPA Execution with eSignature

These customer examples illustrate how organizations used eSignature and online workflows to complete merchant agreements and speed onboarding.

Optica Ventures — Brian Fitzgibbons

Optica needed a straightforward signing flow for customers and partners.

The interface is simple and easy-to-use.
Brian reported that the solution made it easier for both internal teams and customers to complete agreements quickly while preserving a clear audit trail for compliance and reconciliation.

Xerox — Kodi-Marie Evans

Xerox required integrated signing inside NetSuite for merchant setup and contract control.

Integration with NetSuite streamlined workflows.
Kodi-Marie noted that the flexibility to get signatures in the right format and tie them to ERP records reduced manual entry and improved transaction consistency across teams.

Key Dates and Deadlines to Track

Track effective, renewal, termination, and payment timing carefully; those dates trigger obligations and dispute windows.

Effective Date:

Enter MM/DD/YYYY; starts contractual obligations

Renewal Notice:

Typically 30–60 days before renewal window

Termination Notice:

Follow specified notice period, commonly 30 days

Payment Terms:

Settlement schedule defines funding cadence

Record Retention:

Begin statutory retention from execution date

Typical Processing Milestones from Draft to Live

Milestones show the typical sequence and who performs each task during merchant onboarding.

01

Drafting

Prepare agreement and attach underwriting documents

02

Internal Review

Legal and finance review terms and fees

03

Signing

Authorized signer executes and returns agreement

04

Enablement

Processor activates account and funds begin

Typical Signatory Roles

Merchant Authorized Officer

Chief operations or finance officer authorized to bind the merchant. This person confirms business details, settlement bank account, and accepts risk allocation and fee schedules on behalf of the entity.

Processor Representative

An officer or authorized signatory from the acquiring bank or processor who confirms underwriting acceptance, account parameters, reserve conditions, and activation criteria for merchant services.

Practical Tips for Accurate Completion

Use consistent naming, attach required exhibits, and enforce signer authentication to reduce disputes and expedite activation.

Verify Legal Names

Cross-check the merchant name against formation documents and taxpayer records to prevent underwriting mismatch and potential tax withholding or refund issues.

Use Strong Authentication

Require at least email plus SMS code, or ID proofing for high-risk merchants to strengthen attribution and reduce fraud.

Attach Supporting Docs

Include voided check, articles, and KYC attachments in the same submission to prevent iterative requests from underwriting teams.

Archive Signed Copy

Store the executed agreement and audit trail in a secure, access-controlled archive for the required statutory retention period.

FAQs and Troubleshooting for the Merchant Agreement MPA Test

Common questions about electronic execution, notarization, and disputes are covered below to help avoid delays and ensure enforceability.

Need help? Contact support

Can this agreement be signed electronically?
Yes. Electronic signatures are legally valid in the United States under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states. Ensure the signing method demonstrates intent, consent, attribution, and reliable record retention to meet the ESIGN four‑part test.
Is notarization required for merchant agreements?
Typically no for ordinary merchant agreements. Notarization may be needed for related instruments (deeds, powers of attorney) or per state-specific requirements; confirm if a counterparty or bank requests notarized signature or a wet‑notary acknowledgment.
What authentication strength should be used?
For standard risk merchants, email plus SMS OTP is common. For higher-risk merchants or regulatory requirements, use knowledge-based ID proofing, photographic ID analysis, or multi-factor authentication to strengthen signer attribution.
How do I correct a signed mistake?
Execute an amendment signed by the same authorized parties, or void and re-execute a corrected agreement. Record the correction and maintain all versions with time-stamped audit logs for auditability.
What if parties have different governing law preferences?
Negotiate the governing law clause before signature. If the parties cannot agree, processors often default to their home state or customer’s primary business state; unresolved conflicts can delay onboarding.
Where should executed agreements be stored?
Store executed copies with the platform audit trail in an access-controlled repository. Maintain retention per applicable laws (IRS, HIPAA where relevant) and ensure records are exportable for audits or regulatory requests.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now