Establishing secure connection…Loading editor…Preparing document…

Transaction Dispute Form

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

Transaction Dispute Form

This form must be completed and submitted as soon as a disputed transaction is identified. Transaction Dispute Forms must be received within 90 calendar days from original transaction(s) settlement date. Otherwise your dispute rights might be compromised. Complete all fields in this form. Incomplete forms will delay the dispute process.

Important Note: This transaction dispute form is not intended to dispute why a transaction was declined or used for submission of requests for additional documentation.

If you have additional questions, please contact the phone number on back of your card.

Card Number
Date of Settled Transaction
Transaction Amount
Merchant Name

REASON FOR DISPUTE- PLEASE CHOOSE ONLY ONE

Date card lost or stolen: Police Report Number: State:

I acknowledge that all information contained or submitted with this declaration is true.

CARD HOLDER(S) SIGNATURE(S): signatures of all persons authorized to use the card are required.

Note: Please use a separate sheet of paper using the exact format above if additional dispute explanation is required and/or additional transactions need to be disputed. Date and signatures are required both on this form and any attachments. Failure to do so could affect transaction dispute rights.

Fax or mail the completed form to:

Cardholder Services

Fax Number: (954) 377-0072

Cardholder Services

P.O. Box 550578

Ft. Lauderdale, FL 33355-0578


Instructions for Completing the Transaction Dispute Form

1. Complete all fields in the form. Incomplete forms will delay the dispute process.

2. Sign and Date the form.

3. Fax or Mail the form to Cardholder Services (contact information is at the bottom of the form). If you fax this form, please save your fax transmittal/confirmation. If you mail this form, please send via registered mail and save your receipt. Otherwise this could affect transaction dispute rights.

REQUIRED FIELDS

Cardholder name – Name of the cardholder as printed on the front of the Debit Card

Cardholder mailing address – Cardholder’s mailing address

City and state – Cardholder’s mailing address city and state

Cardholder phone # – Cardholder’s primary phone number including area code in case we have questions regarding this dispute

Zip Code – Cardholder’s mailing address zip code

Debit Card number – 16-digit account number printed on the front of the Debit Card

Date of Settled Transaction – Date the transaction posted/settled to the account. A transaction cannot be disputed until it has settled.

Transaction Amount – Total purchase amount for the transaction in question

Merchant Name – Name of the merchant location where the disputed transaction occurred

TRANSACTION DISPUTE PROCESS

If you suspect fraud or error on your card:

1. Contact the number on the back of your card immediately.

2. If this is an unrecognized transaction ask the customer service representative to have your card reported as lost/stolen. If your card is not reported as lost/stolen you may receive a letter instructing you to have your card reported as Lost/Stolen before moving forward with your dispute.

3. Complete the Transaction Dispute Form and fax or mail to Cardholder Services (contact information on bottom of page 1). It must be received within 90 days of the original transaction date.

4. Your account will receive a provisional credit within 10 business days as long as the Transaction Dispute Form is valid and received within 90 days of the original transaction settlement date.

5. If Cardholder Services requests that you provide additional dispute documentation, it must be received within 20 calendar days from the date listed on the letter sent to you in order to avoid having the provisional credit reversed.

o Submission of a police report should not be considered a substitute for responding to follow up affidavits received requesting signatures or other dispute documentation.

6. If the Merchant for the transaction provides adequate documentation to deny your claim (within 30 calendar days of the provisional credit), then the provisional credit will be reversed and the dispute will be denied.

7. The typical time frame for a disputed transaction to be considered complete with permanent credit on your account is within 60 calendar days from the date the completed Transaction Dispute Form is received.

Important Note: The transaction dispute process is not intended to dispute why a transaction was declined or submission of requests for additional documentation. Please contact the number on the back of your card if you have any questions.

Enter text✕

What a Transaction Dispute Form Is

A Transaction Dispute Form is a standardized written or electronic notice used to formally report and document an unauthorized, incorrect, or contested financial transaction to the payment processor, card issuer, merchant, or bank. It captures identifying information about the payer and the account, the disputed charge details, relevant dates, transaction IDs, supporting evidence, and the claimant’s statement of the reason for dispute. Submitting this form starts internal investigation, chargeback, or remediation workflows and creates an audit trail that may be required for regulatory compliance or later legal proceedings.

Why a Complete Dispute Form Matters

Use a Transaction Dispute Form to preserve written evidence, trigger formal investigation, and meet documentation requirements imposed by card networks or federal regulations. A complete form reduces processing delays and strengthens your position during chargeback or refund reviews.

Why a Complete Dispute Form Matters

Who Typically Prepares and Submits This Form

Consumers, merchant support teams, bank dispute specialists, and payment processors commonly prepare or request this form during an investigation.

  • Cardholders disputing unauthorized, duplicate, or incorrectly billed transactions with merchants or issuers.
  • Merchant customer-service representatives documenting evidence, timelines, and refund or chargeback requests.
  • Bank and card issuer dispute analysts compiling records to meet network rules.

Correct routing and appropriate signatory authority ensure the dispute proceeds without avoidable delays and supports any required remediation or recovery.

Core Sections to Include on the Form

Essential sections of a Transaction Dispute Form outline the parties, full transaction details, reason codes, supporting evidence, requested remedy, and signer certifications.

Parties

Identify claimant and respondent by full legal name, account numbers, contact information, and relationship to the transaction; ensure names match government ID or account records to avoid processing errors.

Transaction Details

Record date, time, merchant name, transaction ID, authorization code, currency, amount, and billing descriptor, and any refunds or partial credits previously posted; accurate IDs expedite network reconciliation.

Reason Code

Select the applicable dispute reason code (fraud, duplicate, canceled recurring, goods/services not received, billing error) and provide a concise narrative describing why the charge is contested.

Evidence

Attach screenshots, receipts, emails, proof of return or cancellation, and correspondence. Number exhibits and reference them in the narrative to support timeline reconstruction for adjudication.

Requested Remedy

State the remedy sought—refund, reversal, partial credit, or adjustment—and whether you accept a replacement, refund to original payment method, or merchant credit, and provide any preferred settlement deadlines.

Certification

Sign and date the form, declare under penalty of perjury when applicable that the information is true to your knowledge, and include preferred contact authorization.

Step-by-Step: Submitting a Dispute

Follow these sequential steps to complete and submit a Transaction Dispute Form for bank or card disputes.

  • 01
    Gather Evidence: Collect receipts, communications, and screenshots for the disputed charge.
  • 02
    Complete Form: Fill all required fields and sign accurately.
  • 03
    Attach Documents: Upload or attach numbered exhibits supporting claim.
  • 04
    Submit: Send to issuer, merchant, and keep a copy.

What Happens After You Submit

This overview explains routing, authentication, and the investigation flow after a Transaction Dispute Form is submitted.

  • Issuer Intake: Issuer logs claim and assigns case ID.
  • Preliminary Review: Verify account ownership and basic eligibility.
  • Merchant Response: Merchant provides evidence or issues refund.
  • Resolution: Chargeback, refund, or case closure notification.

Configuring an Online Submission Workflow

Configure the digital workflow to collect signatures, attachments, and routing rules for dispute intake and tracking.

Field Configuration
Authentication Email + SMS code; optional KBA for high-risk claims
Attachments PDF, JPG, PNG; limit 10MB per file
Routing Auto-route by issuer BIN or merchant category code (MCC)
Notifications Email receipts and status updates to claimant and agent

Platform Capabilities for eSubmission

Platforms used to submit Transaction Dispute Forms must support secure file upload, tamper-evident signatures, and comprehensive audit trails.

  • File Formats: PDF, DOCX, JPG supported
  • Integrations: Bank portals, CRM, and case systems
  • Authentication Options: Email, SMS, KBA, SSO

Security and Compliance Considerations

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Trail: Timestamped events, IP, and actions
Access Controls: Role-based access and MFA
BAA Availability: HIPAA BAA available upon request
Data Residency: EU-U.S. Data Privacy Framework supported
Certifications: SOC 2 Type II, ISO 27001, PCI DSS

Common Preparation Challenges

  • Missing transaction identifiers, such as authorization codes or merchant transaction IDs, is a common issue that significantly lengthens investigations and can result in a denied dispute.
  • Submitting screenshots without native transaction records reduces evidentiary weight; prefer original receipts, processor logs, or merchant emails where possible to substantiate timelines.
  • Using ambiguous reason descriptions instead of standardized network reason codes often causes misclassification and routing errors that slow resolution and increase the chance of denial.
  • Failing to retain a copy of the signed form and exhibits can complicate appeals or legal action; ensure both parties receive identical records with audit logs.

Consequences of Errors or Misrepresentation

Missed Deadlines: Chargeback rights waived
Incomplete Evidence: Investigation delays, higher denial risk
Incorrect Signatory: Form may be rejected
False Claims: Potential civil or criminal penalties
Data Breach Risk: Exposes sensitive account data
Backup Withholding: Incorrect TIN may trigger 24% withholding

Timing and Filing Expectations

Time limits vary by card network, issuer rules, and state consumer protection laws; timely filing preserves rights and chargeback eligibility.

Immediate Notice:

Report unauthorized charges as soon as discovered.

Card Network Deadlines:

Typically 60–120 days from statement date for disputes.

Issuer Requirements:

Some issuers require notice within 30 days of statement.

Evidence Retention:

Keep supporting records for at least one year.

State Consumer Laws:

Statutes may extend or modify dispute periods.

Comparing eSignature Vendors for Dispute Forms

High-level vendor comparison for common features and compliance considerations when selecting an eSignature provider for Transaction Dispute Forms.

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

Frequently Asked Questions and Practical Answers

Answers to frequent questions about completing, submitting, and contesting Transaction Dispute Forms, including eSigning and documentation best practices.


Need help? Contact support

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