Scope of Services
Describe the exact services provided, payment rails supported, card types accepted, gateway or terminal responsibilities, and any limitations on transaction types.
A professionally drafted Merchant Services Contract reduces payment disruptions, clarifies fee structures, allocates operational risk, and documents compliance and data-security responsibilities under PCI and applicable privacy laws.
The form is usually completed by the merchant contact, operations manager, or authorized officer who can bind the business.
Final signatures are often executed by a person with contracting authority and stored with corporate vendor records for compliance and audit purposes.
| Field | Configuration |
|---|---|
| Signer Order | Sequential or parallel routing to signers |
| Authentication | Email by default; SMS or KBA if higher assurance |
| Attachments | Require ID, voided check, and certificate of formation |
| Audit Trail | Enable IP, timestamp, and action logging |
Confirm the eSignature platform supports required formats, authentication, and audit logging before sending the contract.
| 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, trial available | Yes, trial available | Yes, trial available | Yes, trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/yr limit | Varies by plan | Varies by plan | Varies by plan |
Describe the exact services provided, payment rails supported, card types accepted, gateway or terminal responsibilities, and any limitations on transaction types.
List interchange, assessment, processor markups, monthly minimums, chargeback fees, and settlement timing to ensure predictable reconciliation.
State PCI-DSS obligations, encryption requirements, breach notification timelines, and responsibilities for protecting cardholder data during processing and storage.
Define chargeback handling, merchant liabilities, representment procedures, holdbacks, reserves, and thresholds that can trigger underwriting actions.
Specify initial term, automatic renewals, notice periods, termination for cause, and early termination fees if applicable.
Set indemnification scope, exclusions, and caps on liability; include insurance requirements where appropriate for large merchants.
Optica Ventures streamlined onboarding by standardizing merchant addresses and bank verifications
Xerox used system integration to map contract fee fields into NetSuite for automated reconciliation
As COO, the signer has operational authority to accept payment-processor terms for multiple locations, coordinate terminal provisioning, and ensure necessary supporting documentation is submitted for underwriting and compliance.
A director of operations or finance can review fee schedules, confirm settlement bank accounts, and bind the company to chargeback and reserve terms when authorized by board or company bylaws.