Establishing secure connection…Loading editor…Preparing document…

Business MOTO Document

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

BUSINESS MOTO DOCUMENT

This Business MOTO Document (the "Agreement") is entered into Effective Date: by and between the parties identified below for the provision and acceptance of mail-order and telephone-order payment processing services (MOTO).

Parties

Merchant Identifier (MID):    Entity Type: Corporation LLC Individual/Sole Proprietor

Recitals

WHEREAS, Provider is engaged in the business of providing payment card processing services, including acceptance and settlement of card-not-present transactions initiated by mail or telephone (MOTO); and

WHEREAS, Merchant desires to obtain from Provider certain MOTO processing services and Provider is willing to provide such services subject to the terms and conditions set forth in this Agreement; and

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

Scope of Work

Provider shall provide Merchant with MOTO payment acceptance, authorization routing, settlement, reporting, and dispute support as described below. Services shall include fraud screening parameters agreed by the parties, daily batch settlement to the Merchant's designated account subject to holdback and reserve requirements, and access to transaction reporting. Any ancillary services (e.g., recurring billing setup, tokenization) shall be set forth in the Scope of Work description below.

Payment Terms

Fees for the Services shall consist of interchange pass-through plus a processing fee and any monthly or per-transaction fees as set forth below. Merchant authorizes Provider to deduct fees from settlement proceeds.

Provider may withhold funds or establish a rolling reserve to cover anticipated chargebacks and indemnity obligations where risk indicators justify such actions. Merchant will be notified in writing of reserve terms and release schedule.

Term and Termination

Term Commencement Date:    Term Expiration Date:

Either party may terminate this Agreement for material breach that remains uncured thirty (30) days after written notice specifying the breach. Provider may suspend services immediately upon discovery of fraud, suspected fraudulent activity, violation of payment network rules, or where required by an acquiring bank or card brand. Termination shall not relieve Merchant of payment obligations incurred prior to termination.

Confidentiality

Each party shall maintain as confidential all non-public business, technical, and financial information disclosed by the other party in connection with this Agreement. Confidential information shall not include information that is publicly available without breach of this Agreement or required to be disclosed by law or regulatory authority, provided the disclosing party is given prompt notice where permitted. Confidentiality obligations shall survive termination of this Agreement for a period of years.

Compliance and Security

Merchant shall at all times comply with applicable card brand rules, payment network standards, and maintain compliance with the Payment Card Industry Data Security Standard (PCI DSS) to the extent applicable to Merchant's business and processing model. Merchant agrees to implement recommended fraud mitigation measures and to cooperate with Provider in any investigations related to unauthorized transactions or data compromise.

Merchant represents and warrants that it will not store full cardholder magnetic stripe data, card verification values (CVV/CVC), or other prohibited data elements in violation of card brand rules.

Indemnification

Merchant shall indemnify, defend and hold Provider harmless from and against any and all claims, losses, liabilities, fines, and expenses (including reasonable attorneys' fees) arising from Merchant's breach of this Agreement, negligence, willful misconduct, violations of card network rules, or fraudulent activity. Provider's indemnification obligations, if any, shall be limited to claims arising from Provider's gross negligence or willful misconduct.

Limitation of Liability

EXCEPT FOR LIABILITY ARISING FROM A PARTY'S GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR INDEMNIFICATION OBLIGATIONS, NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, AND THE AGGREGATE LIABILITY OF EITHER PARTY SHALL NOT EXCEED THE FEES PAID OR PAYABLE TO PROVIDER UNDER THIS AGREEMENT DURING THE PRIOR TWELVE (12) MONTHS.

Governing Law; Dispute Resolution

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws provisions. Claims arising under this Agreement shall be resolved by binding arbitration if the parties mutually agree in writing; otherwise, exclusive jurisdiction shall lie in the state or federal courts located in the governing state.

Entire Agreement; Amendments

This Agreement, together with any written schedules, exhibits, and addenda executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings. No amendment or waiver shall be effective unless in writing and signed by authorized representatives of both parties.

Notices

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses set forth above or such other address as a party may designate by notice. Notices shall be deemed given upon personal delivery, three (3) business days after deposit in the United States mail, or one (1) business day after delivery to a national overnight courier.

Execution

The persons executing this Agreement on behalf of the parties represent and warrant that they are duly authorized to execute this Agreement and to bind the party on whose behalf they sign.

Provider Printed Name:

By:

Date:

Merchant Printed Name:

By:

Date:

Enter text✕

What the Business MOTO Document Is and When It Applies

A Business MOTO Document captures cardholder authorization for mail-order or telephone-order (MOTO) transactions where the customer is not physically present. It records authorization language, transaction amount, billing details, and evidence of consent so merchants can process card-not-present payments and defend against chargebacks.

Why a Clear MOTO Authorization Matters

A complete MOTO Document reduces chargeback risk, documents payer consent under electronic-signature law, and helps meet PCI and recordkeeping expectations. It establishes who authorized payment, when, and for what amount.

Why a Clear MOTO Authorization Matters

Who Typically Prepares and Signs This Document

Teams that handle remote payments and recurring invoicing rely on the Business MOTO Document to record authorization and compliance details.

  • Merchant payment managers and treasury teams who reconcile transactions and respond to disputes.
  • Customer service representatives taking phone or postal payment instructions and creating authorization records.
  • Payment processors and acquirers who need documented consent to settle or dispute chargebacks.

Properly completed MOTO Documents reduce operational friction across accounting, risk, and customer-service workflows.

Typical Signers and Roles

Payment Manager

A mid-level or senior employee who oversees merchant settlement, maintains authorization logs, and responds to issuer inquiries. They ensure the MOTO Document matches processor and PCI requirements and coordinate with finance for reconciliations.

Authorized Purchaser

The customer or an authorized representative who provides payment details and consent by phone or mail. Their recorded authorization and identifying information serve as the primary evidence in disputes.

Step-by-Step: How to Complete a Business MOTO Document

Follow a consistent sequence to capture authorization details, record identity checks, and save an auditable record for disputes and compliance.

  • 01
    1. Record identity: Verify cardholder name and billing address; note method used.
  • 02
    2. Capture authorization: Read and record the exact consent language and amount.
  • 03
    3. Timestamp and evidence: Log date/time and, if applicable, retain the audio recording reference.
  • 04
    4. Store securely: Save a redacted copy in encrypted storage and document retention location.

Typical eSubmission Flow for a MOTO Authorization

A repeatable digital workflow reduces errors and creates an audit trail that supports dispute resolution and regulatory compliance.

  • Upload document: Add the MOTO form (PDF/DOCX) to the signing platform.
  • Place fields: Insert name, date, checkbox, and signature fields where required.
  • Send to signer: Deliver via secure email link or capture consent via recorded call reference.
  • Capture audit trail: Preserve timestamps, IP, and authentication steps with the signed record.

Suggested Platform Settings for MOTO Workflows

Configure authentication, field behavior, and retention so the executed document meets evidentiary and PCI expectations.

Field Configuration
Authentication Email link with optional SMS code for stronger verification
Signature Type Allow typed or drawn signature; store timestamp and signer IP
Data Masking Mask PAN except last four digits; do not store CVV
Retention Enable secure retention and export to encrypted archive

Technical and Integration Considerations

Ensure the signing platform supports required file types, integrations, and security features before deploying MOTO templates.

  • Formats: PDF, DOCX, HTML, Excel
  • Integrations: Salesforce, NetSuite, Google Workspace, Box
  • Security: TLS, AES-256, audit trail

These capabilities let you embed MOTO templates into CRM, ERP, and document-storage workflows while preserving compliance controls.

How a MOTO Authorization Differs from a Recurring Payment Agreement

Compare core characteristics so you choose the correct template for single-authorization versus ongoing billing arrangements.

Criteria MOTO Authorization Recurring Payment Agreement
Signature method phone/recording written or electronic
Presence required cardholder remote cardholder remote or onsite
Billing cadence single charge scheduled recurring charges
Common issue chargebacks cancellation disputes

eSignature Vendor Pricing and Feature Snapshot

Compare starting price, trial availability, bulk-send capability, audit trail, HIPAA readiness, and envelope caps across common eSignature vendors; signNow appears first per supplier ordering rules.

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 Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Varies by plan Varies by plan Varies by plan Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Varies by plan Varies by plan Varies by plan Varies by plan
Envelope Cap No envelope cap 100 envelopes/user/year limit Varies by plan Varies by plan Varies by plan

Essential Elements to Include in a Professional MOTO Document

A robust MOTO Document combines clear authorization language, identity evidence, payment details, storage rules, and dispute-handling terms to create defensible proof of consent.

Authorization Clause

State the exact payment authorization language, specifying one-time or recurring charges, and the precise amount or billing formula to avoid ambiguity.

Card Data Handling

Record only permitted card data (last four digits); explicitly note that CVV will not be stored and full PAN retention is restricted under PCI DSS.

Identity Evidence

Document verification steps such as AVS result, recorded voice consent reference, or SMS code used during the phone authorization process.

Cancellation & Revocation

Include a clear revocation procedure and effective date; describe notice method and allow reasonable time to process cancellations.

Dispute & Chargeback Response

Specify documentation the merchant will retain for disputes and explain how customers can contact billing or customer-service teams to resolve issues.

Legal & Governing Law

Identify governing state law for interpretation and reference ESIGN (15 U.S.C. §7001) and applicable state UETA or ESRA provisions on electronic consent.

Supporting Documents and Export Options

Collect these attachments and export formats alongside the MOTO Document to support audits, reconciliations, and dispute responses.

Supporting Documents

Include merchant terms, voice-recording reference, AVS/CVV results, and invoices to create a full evidence package for chargeback defense.

Export Formats

Save final executed records as PDF/A for long-term retention; retain native DOCX or CSV extracts for reconciliation and import to accounting systems.

Redaction & Masking

Export redacted versions that mask PAN beyond last four digits for business use while preserving audit metadata for disputes.

Audit Certificate

Attach the platform's certificate of completion (audit trail) that shows timestamps, IP addresses, and authentication steps.

Common Mistakes That Increase Risk

  • Storing full PAN or CVV instead of masking or encrypting, which violates PCI DSS and increases breach exposure.
  • Using vague authorization language like 'authorize charges' without specifying amounts or cadence, which complicates disputes.
  • Failing to record or preserve evidence of consent (timestamps, audio reference, or audit trail) needed for issuer inquiries.
  • Not aligning retention practices with IRS, HIPAA where applicable, and internal data-minimization policies, raising compliance risk.

Security Controls and Compliance to Consider

Transport Encryption: TLS 1.2 or 1.3
Data Encryption: AES-256 at rest
Certifications: SOC 2 Type II, ISO 27001
Regulatory Coverage: PCI DSS certified
Healthcare Controls: HIPAA compliant (BAA required)
Electronic Records: 21 CFR Part 11 support where required

Immediate Consequences of Incomplete or Noncompliant Forms

Chargeback Liability: Issuer may reverse payment and assess fees
PCI Fines: Processor or network penalties for noncompliance
Fraud Exposure: Unauthorised charges and financial loss
Legal Disputes: Contract claims over authorization validity
Reputational Harm: Customer trust and retention decline
Regulatory Penalties: Fines under sector-specific rules

Key Timing Rules and Typical Deadlines

Track settlement windows, evidence retention, and common dispute timelines to ensure documentation supports timely responses.

Transaction Settlement:

Captures typically settle within 1–3 business days

Chargeback Window:

Issuer dispute windows typically range 60–120 days

IRS Recordkeeping:

Retain billing records at least 3 years (IRC §6501(a))

Audio Retention:

Retain recorded consents per policy and PCI guidance

Customer Cancellation:

Allow reasonable processing time after receipt of revocation

Processing Milestones from Authorization to Archive

Sequence key milestones so teams know what to capture and when to escalate during a dispute lifecycle.

01

Authorization Captured

Record consent, verification results, and timestamp immediately

02

Payment Processed

Submit to processor and document settlement reference

03

Dispute Monitoring

Monitor issuer notifications for 60–120 days

04

Archive Records

Move executed documents to secure long-term storage

Practical Tips to Reduce Chargebacks and Compliance Risk

Consistent procedures and documented evidence materially improve dispute outcomes and reduce operational overhead.

Use explicit consent language
Craft the authorization text to specify the amount, frequency, and any variable calculation method. Include the merchant name and a clear statement that the cardholder consents to charges to avoid ambiguity during issuer reviews.
Limit stored card data
Store only the PAN last four, expiration, and a token if available. Never retain CVV and ensure full PAN is encrypted and justified under PCI DSS to reduce breach scope and fines.
Preserve verifiable evidence
Retain timestamps, IP addresses, recorded-call references, or signed e-documents. This metadata is typically decisive in chargeback representment and in meeting ESIGN attribution standards.
Regularly review workflows
Audit MOTO practices quarterly for authentication strength, template clarity, and retention compliance. Update forms in response to dispute trends or regulatory changes.

Real-World Examples of MOTO Document Use

These condensed examples illustrate how businesses apply MOTO authorizations in common scenarios and the evidence they preserve for disputes.

Subscription Onboarding

A software vendor enrolls a customer by phone, records verbal consent and stores the MOTO Document with amount formula

  • Uses tokenization to avoid storing PAN
  • Retains audit trail and recurring schedule for dispute defense and billing reconciliation.

One-Time Service Charge

A field service company takes payment over the phone for an on-site repair, logs authorization and AVS results

  • Captures technician job ID
  • Keeps the MOTO authorization and invoice until post-termination retention period elapses.

Frequently Asked Questions About Business MOTO Documents

Answers to common operational, legal, and technical questions about executing, storing, and disputing MOTO authorizations.


Need help? Contact support

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