Authorization Clause
State the exact payment authorization language, specifying one-time or recurring charges, and the precise amount or billing formula to avoid ambiguity.
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.
Teams that handle remote payments and recurring invoicing rely on the Business MOTO Document to record authorization and compliance details.
Properly completed MOTO Documents reduce operational friction across accounting, risk, and customer-service workflows.
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.
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.
| 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 |
Ensure the signing platform supports required file types, integrations, and security features before deploying MOTO templates.
These capabilities let you embed MOTO templates into CRM, ERP, and document-storage workflows while preserving compliance controls.
| 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 |
| 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 |
State the exact payment authorization language, specifying one-time or recurring charges, and the precise amount or billing formula to avoid ambiguity.
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.
Document verification steps such as AVS result, recorded voice consent reference, or SMS code used during the phone authorization process.
Include a clear revocation procedure and effective date; describe notice method and allow reasonable time to process cancellations.
Specify documentation the merchant will retain for disputes and explain how customers can contact billing or customer-service teams to resolve issues.
Identify governing state law for interpretation and reference ESIGN (15 U.S.C. §7001) and applicable state UETA or ESRA provisions on electronic consent.
Include merchant terms, voice-recording reference, AVS/CVV results, and invoices to create a full evidence package for chargeback defense.
Save final executed records as PDF/A for long-term retention; retain native DOCX or CSV extracts for reconciliation and import to accounting systems.
Export redacted versions that mask PAN beyond last four digits for business use while preserving audit metadata for disputes.
Attach the platform's certificate of completion (audit trail) that shows timestamps, IP addresses, and authentication steps.
Captures typically settle within 1–3 business days
Issuer dispute windows typically range 60–120 days
Retain billing records at least 3 years (IRC §6501(a))
Retain recorded consents per policy and PCI guidance
Allow reasonable processing time after receipt of revocation
Record consent, verification results, and timestamp immediately
Submit to processor and document settlement reference
Monitor issuer notifications for 60–120 days
Move executed documents to secure long-term storage
A software vendor enrolls a customer by phone, records verbal consent and stores the MOTO Document with amount formula
A field service company takes payment over the phone for an on-site repair, logs authorization and AVS results