Parties
Identify the merchant, processor, and authorized sub-processors by legal name and address; include contact and escalation contacts, corporate status, and permitted assignment or subcontracting rules to prevent downstream liability disputes.
A Business EPPA Template clarifies fee schedules, security responsibilities, and liability limits to reduce onboarding delays and contractual disputes while supporting PCI and data-protection practices across merchant relationships.
Internal and external stakeholders from payments, legal, finance, and IT commonly prepare or review a Business EPPA Template to align operational and compliance requirements.
The template helps these groups agree on settlement mechanics, data handling responsibilities, dispute procedures, and the documentation required for merchant onboarding.
Identify the merchant, processor, and authorized sub-processors by legal name and address; include contact and escalation contacts, corporate status, and permitted assignment or subcontracting rules to prevent downstream liability disputes.
List supported payment methods (card brands, ACH, digital wallets), transaction types (recurring, one-time), geographic limitations, velocity limits, and any excluded categories or high-risk verticals requiring special underwriting.
Specify all fees (percentage and fixed), chargeback fees, monthly minimums, settlement schedules, reserve calculations, fee adjustments for currency conversion, and sample fee calculations or rounding rules to ensure clarity.
Assign responsibility for PCI scope, require encryption and tokenization standards, mandate regular vulnerability scanning, define breach notification timelines, and require evidence such as Attestation of Compliance or third-party audit reports.
Define chargeback timelines, required evidence formats, merchant obligations for representments, allocation of financial responsibility if thresholds exceeded, dispute escalation steps, and remediation measures after repeated chargebacks.
Detail termination for cause and convenience, cure periods, effects on settlements and reserves, post-termination data handling, surviving obligations, and responsibilities for unresolved disputes or indemnity claims.
| Field | Configuration |
|---|---|
| Signer Authentication | Email link with optional SMS code |
| Document Attachments | Require bank letter, PCI report PDF |
| Notifications | Email copies to legal and finance teams |
| Retention | Store signed PDF and audit trail for required period |
Use an eSignature platform that supports TLS/AES encryption, audit trails, secure storage, and integrations with payment and accounting systems.
Date entered as MM/DD/YYYY when obligations begin.
Settlement frequency typically daily or weekly per agreement.
Typically 7–30 days depending on card network rules.
Quarterly or as triggered by volume or chargebacks.
30–90 days' written notice commonly required for changes.
| 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 | 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/year | No cap | No cap | No cap |