What evidence is required for representment?

Provide clear transaction metadata, proof of delivery or service, signed authorizations, receipts, communications with the cardholder, and any system logs (IP, timestamp). Number exhibits and explain how each item supports the reason code to allow issuer reviewers to match claims to evidence.

Can the Chargeback Response be e-signed?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA where adopted. For consumer-facing records, provide required disclosures and retain reproducible records showing intent, attribution, and consent to electronic transactions.

Is notarization required for affidavits?

Not generally required for standard chargeback representments, but some issuers or specific affidavits may request notarized statements. If a notary or RON is required, follow state rules for identity proofing and retention; retain notary journals and any audio-video RON recordings.

What happens if you miss a deadline?

Late submissions are often rejected; the issuer or card network may deny representment if evidence arrives after the allowed window. Check for secondary options such as arbitration or card network escalation, but expect lower chances of reversal and possible financial impact.

Who must sign the representment?

An authorized merchant representative should sign, typically a chargeback manager, merchant owner, or an officer with authority. Document signer's name, title, and date. If signing electronically, record authentication method and preserve the audit trail to prove attribution.

How long should records be retained?

Keep representment records until the dispute is resolved plus at least three years; financial records should be retained at least three years per IRC §6501(a). If PHI appears, retain six years per 45 CFR §164.530(j).

Electronic Signature
Templates
Finance
Chargeback Response Template

Chargeback Response Template

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

CHARGEBACK RESPONSE TEMPLATE

Merchant and Processor Information

Merchant Legal Name DBA / Trade Name Merchant Address

Merchant Phone

Merchant Email

Acquirer / Payment Processor Acquirer Account / MID

Cardholder and Transaction Details

Cardholder Name:

Card Number (last 4): Card Brand:

Transaction Date: Transaction Amount: Currency:

Authorization Code: Merchant Order/Invoice #:

Acquirer Transaction ID: Chargeback Case ID:

Chargeback Date: Reason Code:

Reason Code Narrative

Chargeback Case Details & Key Dates

Original Transaction Amount

Dispute Amount

Response Due Date

Retrieval Request Received

Evidence Checklist (mark all that apply)

Sales receipt / transaction record

Signed receipt or cardholder signature

Delivery tracking and carrier proof of delivery

Proof of signature at delivery (name printed matches cardholder)

Terminal logs / IP address / AVS / CVV results

Billing descriptor and order confirmation

Order confirmation and communication with cardholder

Refund / return policy presented at purchase

Written correspondence with cardholder regarding the charge

CCTV or photographic evidence (if applicable)

Other Evidence Description

Chronology and Merchant Narrative

Chronology of Events

Refund and Fulfillment Details

Refund Amount Issued (if any)

Refund Date

Refund Transaction ID

Fulfillment Details / Tracking

Representment Statement and Certification

The merchant certifies that all evidence provided in this response is genuine, pertains directly to the referenced transaction, and is maintained in the merchant's business records. The merchant further represents that it complied with applicable card network rules, obtained authorization for the transaction where required, and followed the stated refund and delivery procedures set forth at the time of sale.

By submitting this response, the merchant acknowledges that knowingly submitting false or misleading evidence may subject the merchant to assessment of chargeback fees, reversal of funds, fines under card network rules, and civil liability. The merchant agrees to hold the acquirer and card issuer harmless from claims arising from the merchant's failure to maintain records or from inaccurate representations.

Representative Contact for Follow-up

Attachments

Attach the following documents to support representment: sales receipt, signed proof of delivery, carrier tracking, terminal logs, IP/AVS/CVV reports, order confirmation, and all relevant email/text communications with the cardholder. Identify each attachment below.

Attachment List / File Names

Merchant Declaration and Signature

I, the undersigned authorized representative of the merchant named above, declare under penalty of perjury and by the authority vested in me by the merchant that the information and evidence provided in this Chargeback Response are true, complete, and maintained in the ordinary course of business. I request that the acquirer and card network consider this representment and reverse the chargeback based on the enclosed documentation and explanation.

Merchant Name:

By (Authorized Representative):

Title:

Date:

What the Chargeback Response Template Is

Chargeback Response Template is a standardized document merchants use to dispute a cardholder’s chargeback with the card issuer or payment processor. It collects transaction identifiers, proof of delivery or service, signed receipts or authorization records, and a narrative explaining why the charge is valid. The template organizes evidence to meet card network and issuer requirements, the merchant’s chargeback representment process, and supports timely submission within disputable timeframes. Use of a consistent template reduces errors, ensures required fields are present, and speeds internal review and external submission workflows.

Why a Standard Template Matters for Representments

Provides a clear framework for assembling evidence, meeting issuer and card network documentation standards, and improving the likelihood of successful representment. It saves time for operations teams by standardizing required fields, reducing incomplete submissions, and facilitating consistent internal review.

Who Prepares and Submits This Template

Merchant operations, chargeback and fraud teams, payment processors, and third-party dispute vendors typically complete this template.

In-house merchant operations: prepares documentation and submits evidence to acquiring bank or processor.
Fraud or chargeback specialists: analyze transaction history, gather receipts, and draft the dispute narrative.
Third-party dispute vendors: compile exhibits, format files per issuer rules, and manage timelines.

Use the template to centralize evidence, maintain an audit trail, and improve consistency across representments.

Representative Roles Who Sign or Approve

Chargeback Manager

Responsible for compiling transaction evidence, coordinating with customer service and finance, and ensuring timely submission to the acquirer. Reviews authorization logs, delivery confirmations, and any signed authorizations to build a clear representment packet that meets card network requirements.

Fraud Analyst

Analyzes chargeback reason codes, identifies patterns of abuse, and extracts supporting records such as IP addresses, timestamps, and communications. Works with legal or vendor partners to validate evidence and recommends representment strategy based on issuer rules and historical outcomes.

Essential Fields to Include

Transaction ID: Acquirer or processor reference number.

Transaction Date: MM/DD/YYYY timestamp of sale.

Amount: Currency and decimal cents (USD).

Cardholder Name: Full legal name as on card.

Proof of Delivery: Tracking number, signature, delivery date.

Authorization Data: AVS, CVV response, approval code.

Consequences of Incomplete or Incorrect Responses

Chargeback Loss: Irrecoverable transaction amount.

Fees and Fines: Issuer or network penalties apply.

Higher Processing Rates: Merchant may face fee increases.

Reserve Requirements: Processor may require rolling reserve.

Account Termination: Excessive ratio risks losing account.

Legal Exposure: False evidence can trigger liability.

Common Mistakes to Avoid

Missing or mismatched transaction identifiers (e.g., wrong authorization code or order number) that prevent issuers from matching evidence to the dispute.
Incomplete proof of delivery—omitting tracking numbers, signed delivery receipts, or clear delivery dates—reduces chances of a successful representment.
Using vague or argumentative narratives instead of concise, factual timelines and itemized evidence weakens the merchant’s position.
Submitting files in unsupported formats or exceeding size limits can delay processing or cause automatic rejection by the issuer.

Step-by-Step: Complete the Chargeback Response Template

Follow these steps to complete a Chargeback Response Template accurately, attach required evidence, and submit within the issuer’s timeframe.

01

Identify: Record charge date, amount, and authorization code.
02

Collect: Attach receipts, delivery proof, and communications.
03

Explain: Write a concise timeline and reasoned narrative.
04

Submit: Send to acquirer or processor with audit trail.

Where to Send a Completed Response

Chargeback responses are submitted to the acquiring bank or processor, which forwards representments to the card network and issuer for review.

To Acquirer: Primary submission route; follow processor-specific portal or email instructions.
Card Network: Issuer reviews through Visa, Mastercard, etc., per network rules.
Payment Processor: Some processors handle evidence assembly and portal uploads.
Alternate Channels: Use certified mail or RON-notarized affidavits when required.

Anatomy of a Professional Chargeback Response Template

A professional template organizes required fields and supporting exhibits to align with issuer and card network expectations, improving clarity during representment.

Header

Include merchant name, merchant ID (MID), acquirer name, contact details, and a unique representment reference. Clear header information helps issuers quickly route and process the dispute packet and reduces matching errors.

Transaction Details

List card brand, cardholder name, last four digits, transaction date, amount, authorization code, and order ID. Accurate transaction metadata is critical for issuer matching and timely adjudication.

Evidence Index

Provide a numbered exhibit list for receipts, invoices, delivery records, signed authorizations, IP logs, or customer communications. Numbered exhibits let reviewers associate narrative points with supporting files.

Narrative

Compose a concise, chronological statement explaining the transaction, authorization, delivery, and why the charge is valid. Avoid argumentative language; stick to verifiable facts and timestamps.

Attachments

Attach PDFs, screenshots, and logs. Ensure files are legible, properly named, and within size limits. Use PDF/A when possible to preserve formatting and metadata for long-term preservation.

Signature

Include merchant signature, printed name, title, and date. If using electronic signatures, document method, authentication, and retention of the audit trail to prove intent and attribution.

Key Deadlines and Time-Sensitive Actions

Chargeback representments depend on strict issuer and network deadlines; submit timely evidence to avoid automatic losses or deadline-based denials.

Notification Receipt:

Note date you received the chargeback notice; deadlines typically run from this date.

Issuer Deadline:

Typical network windows fall between 30 and 45 days; verify with your acquirer.

Evidence Window:

Submit organized exhibits as soon as possible; late evidence often excluded.

Appeals:

Some networks permit later arbitration or re-presentment; follow network procedures.

Record Dates:

Keep submission timestamps and delivery confirmations for audit and rebuttal.

Typical Chargeback Milestones from Notice to Outcome

Typical milestone timeline for a chargeback from notice through final resolution, showing submission, review, and outcome stages.

01

Notice Received

Document the notice date and reason code; start internal review.

02

Evidence Collection

Gather receipts, tracking, logs, and communications; number exhibits.

03

Submit Representment

Upload packet to acquirer portal or send via processor email.

04

Issuer Decision

Track outcome, note reversals or losses, and update metrics.

Configure Online Workflows for Repeating Cases

Configure online templates and automated workflows to collect evidence, route approvals, and log audit trails for each chargeback case.

Field	Configuration
Template Name	Chargeback Response Template configured with required fields.
Authentication	Use email access and optional SMS two-factor code.
Auto-numbering	Auto-generate unique representment ID per case.
Attachments	Accept PDF, DOCX, HTML, Excel; files named by exhibit.
Audit Trail	Record IP, timestamps, user actions, and certificate.

Distribution Channels and Technical Requirements

Use integrated eSignature platforms and processor portals to distribute and sign chargeback response documents securely.

File Formats: PDF, DOCX, HTML, Excel supported.
Integrations: Connectors: Salesforce, NetSuite, Microsoft 365, Google Workspace.
Authentication: Email, SMS, KBA, and SSO options.

Electronic Signature vs Cryptographic Digital Signature

Quick comparison: electronic signatures versus cryptographic digital signatures and their typical implications for chargeback evidence.

Criterion	Electronic Signature	Digital Signature
Legal Status	acceptable under esign/ueta	acceptable under esign/ueta
Typical Evidence	audit trail, click-to-sign	pki certificate, hash
Non-repudiation Strength	moderate	high
Implementation Complexity	low	high

eSignature Pricing Snapshot for Chargeback Workflows

Comparison of common eSignature options for preparing and delivering Chargeback Response Templates; signNow appears first for reference.

	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	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About Chargeback Responses

Answers to common questions on evidence, signatures, notarization, deadlines, signatory authority, and record retention for representments.

Need help? Contact support

What evidence is required for representment?
Provide clear transaction metadata, proof of delivery or service, signed authorizations, receipts, communications with the cardholder, and any system logs (IP, timestamp). Number exhibits and explain how each item supports the reason code to allow issuer reviewers to match claims to evidence.
Can the Chargeback Response be e-signed?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA where adopted. For consumer-facing records, provide required disclosures and retain reproducible records showing intent, attribution, and consent to electronic transactions.
Is notarization required for affidavits?
Not generally required for standard chargeback representments, but some issuers or specific affidavits may request notarized statements. If a notary or RON is required, follow state rules for identity proofing and retention; retain notary journals and any audio-video RON recordings.
What happens if you miss a deadline?
Late submissions are often rejected; the issuer or card network may deny representment if evidence arrives after the allowed window. Check for secondary options such as arbitration or card network escalation, but expect lower chances of reversal and possible financial impact.
Who must sign the representment?
An authorized merchant representative should sign, typically a chargeback manager, merchant owner, or an officer with authority. Document signer's name, title, and date. If signing electronically, record authentication method and preserve the audit trail to prove attribution.
How long should records be retained?
Keep representment records until the dispute is resolved plus at least three years; financial records should be retained at least three years per IRC §6501(a). If PHI appears, retain six years per 45 CFR §164.530(j).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now