Merchant Identity
Include full legal business name, DBA, EIN or tax identifier where relevant, DBA address, and a primary contact with phone and email so the merchant is unambiguously identified for billing and compliance.
A consistent EMV Document Template reduces misconfiguration, speeds onboarding, and preserves an auditable record of who approved card-acceptance settings. It clarifies responsibilities among merchant, acquirer, processor, and integrator while supporting PCI and card-brand attestation workflows.
Typical participants prepare, review, or sign EMV templates during merchant onboarding and terminal provisioning.
The completed template becomes part of the merchant file used for support, audits, and future configuration changes.
The merchant owner or authorized officer provides legal acceptance of EMV acceptance terms, confirms terminal counts and locations, and signs to authorize settlement and chargeback handling. This signature affirms the merchant understands processing responsibilities and any funding holds.
An operations manager or technical lead from the integrator or acquirer attests to device configuration, EMV application parameter mapping, and test completion. Their signature documents who configured terminals and who is responsible for future changes.
Include full legal business name, DBA, EIN or tax identifier where relevant, DBA address, and a primary contact with phone and email so the merchant is unambiguously identified for billing and compliance.
Record terminal model, manufacturer, serial number or device ID, firmware version, and physical location. These values are essential for remote troubleshooting and for card-brand attestations.
List acquirer name, acquiring bank identification, processor account numbers, Merchant ID (MID), and any routing details required for settlement or reconciliation.
Capture AIDs, TAC lists, floor limits, CVM rules, and terminal action codes. Precise EMV parameter mapping prevents transaction declines and ensures consistent authorization behavior.
Include pre-cert and post-cert test steps, expected test transactions, approved test cards, approval signatures, and dates to document successful certification with the acquirer and card brand.
Add brief terms covering liability allocation, chargeback handling, equipment custody, and signature blocks for merchant and integrator acceptance to create an auditable contract record.
| Field Mapping | Template field | Destination metadata |
|---|---|
| Merchant Legal Name | Populate customer.name in CRM |
| Terminal Serial | Store as device.serial in asset registry |
| Certification Status | Set workflow.status to 'Certified' when signed |
| Signers and Order | Define signer roles and sequential or parallel routing |
Choose a platform that supports the file formats and integrations your operations use.
Confirm the platform can produce tamper-evident signed PDFs, retain audit trails, and export metadata for reconciliation and audits.
| 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 trial | Trial available | Trial available | Trial available | 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/year | Varies by plan | Varies by plan | Varies by plan |