Establishing secure connection…Loading editor…Preparing document…

Merchant Service Application

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

Merchant Service Application and Business Agreement

RECITALS

WHEREAS, Merchant Name: operates the business identified in this application and seeks to obtain payment processing services from Processor Name: ; and

WHEREAS, Processor will evaluate the merchant's transaction profile, risk, and documentation and, subject to acceptance, provide acquiring, settlement and ancillary services under the terms set forth in this application and the attached agreement; and

WHEREAS, Merchant certifies that all information provided herein is true and authorizes Processor to verify any information, obtain consumer or business credit reports where permitted, and to seek banking and processing references as necessary.

APPLICANT (MERCHANT) INFORMATION

Corporation    LLC    Partnership    Sole Proprietor

PRINCIPAL / OWNER INFORMATION (List all individuals owning 25% or more)

PROCESSING PROFILE

Estimated Monthly Card Volume:    Average Ticket:    Largest Single Ticket:

Primary Processing Method:    Card Present (Retail)    E‑commerce    MOTO / Phone Order

Average Monthly Chargeback Rate (if applicable):    Anticipated Card Present %:

BANKING / SETTLEMENT (ACH) DETAILS

Checking    Savings

PROCESSING HISTORY & RISK DISCLOSURES

Has the business experienced chargebacks exceeding 1.5% in the last 12 months?    Yes    No

Has the merchant or principals filed for bankruptcy, had a merchant account closed for cause, or been indicted for fraud?    Yes    No

SCOPE OF WORK

The Processor shall provide acquiring, authorization, settlement, and risk monitoring services necessary to accept credit and debit card transactions for the Merchant's business as described below. Merchant hereby requests the services described and agrees to provide all required documentation and reasonable cooperation.

PAYMENT TERMS

Merchant agrees to pay fees, charges and assessments as set forth in this application and any separately executed fee schedule. Fees may include interchange, assessment, processor markups, chargeback fees, monthly account fees, equipment rental or purchase fees, and other applicable amounts.

TERM AND TERMINATION

The term of the services shall commence on: Start Date: and shall continue until End Date: unless earlier terminated in accordance with this Agreement.

Either party may terminate this Agreement for convenience upon written Notice Period (days): . Processor may terminate immediately for cause upon discovery of material misrepresentation, suspected fraud, excessive chargebacks, or violation of card brand rules.

CONFIDENTIALITY

Each party agrees that any non-public business, technical or financial information disclosed by one party to the other in connection with this application and related services will be held in confidence and used solely to perform obligations under this Agreement. Confidential information does not include information that is or becomes public without breach, is independently developed, or is required to be disclosed by law.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the state of: without regard to conflict of law principles. Venue for any dispute shall be in the courts located within that state unless otherwise required by applicable card brand rules.

ENTIRE AGREEMENT

This application, together with any fee schedule, addenda and the Processor's standard merchant agreement incorporated herein by reference, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior discussions, proposals and agreements. No amendment will be effective unless in writing and signed by both parties.

AUTHORIZATION AND CERTIFICATIONS

The undersigned certifies under penalty of perjury that the information provided is true, complete and correct. Merchant authorizes Processor to obtain business and personal credit reports, to verify banking and processing relationships, and to share information with card brands, acquirers, and risk-monitoring providers as necessary for onboarding and ongoing services. Merchant acknowledges that providing false or misleading information is grounds for immediate account denial or termination and may subject Merchant to civil or criminal liability.

Merchant Printed Name:

By:

Date:

Processor Printed Name:

By:

Date:

Enter text✕

What the Merchant Service Application Is and when it applies

A Merchant Service Application is the account-onboarding form submitted to a payment processor, acquiring bank, or gateway to establish card-acceptance services for a business. It collects business identification, ownership details, banking routing info, processing volumes, average ticket size, and documentation for KYC and underwriting. Processors use the application to evaluate risk, determine pricing, and enable card brand enrollment. The application may trigger additional verification steps such as enhanced KYC, merchant category review, or site inspection depending on risk indicators and card brand rules.

Why a complete Merchant Service Application matters

A well-prepared application speeds underwriting, reduces manual follow-up, and helps avoid account holds or higher initial reserve requirements. Accurate information supports regulatory and card-brand compliance and provides a clear audit trail acceptable under ESIGN (15 U.S.C. §7001) and state UETA frameworks.

Why a complete Merchant Service Application matters

Who typically completes or signs a Merchant Service Application

Different roles provide distinct information: owners supply identity details, finance teams provide banking data, and operations complete processing specifics.

  • Business owner or authorized signatory provides legal business name, EIN, and ownership percentages.
  • Finance or accounting officer supplies bank routing, account number, and proof of deposit or voided check.
  • Payment operations or IT supplies processing volume estimates, average ticket size, and integration details.

Knowing which party supplies each section reduces errors and accelerates approval.

Representative signers and their roles

Owner / CEO

The business owner or chief executive is usually the authorized signer for merchant agreements and warranties. This person must match the name on government identification and provide consent for credit and background checks; mismatches can delay underwriting and require notarized affidavits.

Payment Operations Manager

Operational leads complete technical sections, provide projected volumes, and coordinate gateway integration. They often act as primary contact for onboarding, post-approval configuration, chargeback handling, and any subsequent updates to processing profiles.

Step-by-step: filling and submitting the Merchant Service Application

Follow these core steps in order to minimize review cycles and reduce time to approval.

  • 01
    Gather documents: Collect EIN, articles, voided check, and owner ID scans.
  • 02
    Complete form: Enter legal names, contact details, and processing estimates.
  • 03
    Upload support: Attach bank proof, lease, ownership, and relevant licenses.
  • 04
    Submit and monitor: Send to processor and check status for follow-up requests.

Customizing and automating the online application workflow

Configure the digital workflow to reduce manual entry and ensure required fields are validated before submission.

Field Configuration
Required Fields Mark legal name, EIN, and bank details required.
Conditional Logic Show additional fields when high-risk category selected.
Authentication Enable email or SMS verification for signer attribution.
Template Naming Use clear names, include version and date for auditability.

Where to send the completed Merchant Service Application

Choose the correct recipient and method based on the processor's onboarding instructions to avoid routing delays.

  • Payment Processor: Upload to processor portal per onboarding checklist.
  • Acquiring Bank: Submit documents directly if instructed by the acquirer.
  • Payment Gateway: Attach application when requesting gateway merchant credentials.
  • Email or Secure Upload: Follow processor encryption and file format requirements.

Digital signing and delivery: technical needs

Use an eSignature platform that supports secure uploads, audit trails, and the authentication level your processor requires.

  • Integrations: Salesforce, NetSuite, Google Workspace supported
  • File Formats: PDF, DOCX, and Excel accepted
  • Authentication: Email, SMS code, and 2FA options

Typical timelines and processing expectations

Processing times vary by provider and risk profile; plan for initial underwriting, KYC verification, and any additional compliance checks.

Initial review time:

Typically 3–7 business days for standard applications.

KYC / documentation:

May add 5–10 business days when additional documents required.

PCI onboarding:

PCI attestation or remediation can take 2–4 weeks.

High-risk review:

High-risk industries may require 3–6 weeks for approval.

Going live:

After approval, credentials typically activate within 24–72 hours.

Key onboarding milestones from application to live processing

A typical merchant onboarding follows sequential milestones; tracking each stage helps predict go-live timing and required follow-up.

01

Submit Application

Complete form and upload required documentation for initial intake.

02

Underwriting Review

Processor evaluates risk, identity, and transaction history.

03

Contracting & Reservation

Agreements finalized and any reserve or rolling reserve set.

04

Activation & Testing

Test transactions and gateway configuration before full live processing.

Common preparation mistakes that slow merchant onboarding

  • Using inconsistent business names between application and formation documents causes manual verification and delays.
  • Submitting handwritten or low-resolution scans of IDs and voided checks that fail automated identity checks.
  • Underestimating processing volumes, which can trigger mid-contract renegotiation or sudden reserve increases.
  • Omitting owner SSN or providing P.O. boxes without physical address proof, leading to KYC exceptions.

Risks and potential consequences of incomplete or incorrect applications

Account delays: Slower approval and onboarding
Higher reserves: Increased holdbacks or rolling reserves
Contract rejection: Application denial by acquirer
Chargeback exposure: Greater financial liability for disputes
PCI non-compliance: Fines and increased audit frequency
AML concerns: Suspicion escalations and reporting

Security and compliance features to verify on eSubmission platforms

Encryption in transit: TLS 1.2 / 1.3
Encryption at rest: AES-256
Audit Trail: Detailed timestamps and IPs
Certifications: SOC 2 Type II
PCI Compliance: PCI DSS certified
HIPAA Support: BAA available

eSignature vendor comparison for Merchant Service Application workflows

A neutral pricing snapshot helps choose an eSignature provider that fits volume, compliance, and integration needs; signNow appears first for direct 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, no card Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real examples of onboarding using an eSignature workflow

These short examples show how timely, accurate applications help merchants go live and stay compliant.

Optica Ventures (COO)

Optica consolidated templates and reduced follow-ups by standardizing uploads.

  • They used digital verification for owner IDs.
  • The interface simplicity shortened underwriting cycles and made it easier for customers to return signed documents quickly.

Martin Properties (Founder)

Martin Properties processed leases and merchant applications online to expedite tenant payments.

  • Mobile signing enabled field staff to complete forms on site.
  • They reported full compliance with built-in security and consistency across devices, improving turnaround for new merchant setups.

Practical tips for accurate and efficient completion

Follow these pragmatic steps to reduce common errors and speed approval.

Verify legal names
Confirm entity and owner names against formation documents and government ID to avoid identity mismatches that trigger manual review.
Prepare bank proof
Upload a recent voided check or bank letter showing routing and account numbers to verify deposit destination and prevent payout issues.
Document industry specifics
Attach licenses, permits, or sample invoices that clarify business model and reduce the need for follow-up underwriting questions.
Use validated templates
Standardize field validation and required-document checklists in your template to reduce submission rejections and save time.

Frequently asked questions about Merchant Service Applications

Answers address common legal, technical, and submission issues encountered during merchant onboarding.


Need help? Contact support

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