How to Dispute a Charge on Your Account: Step-by-Step Guide and Timelines

Disputing a charge on your credit or debit card account begins with securing your account, gathering evidence, and contacting your bank or issuer right away. Under rules like the Fair Credit Billing Act (FCBA), you typically have 60 days from the statement date when the error first appeared to file for billing errors. General timelines extend to 120 days from the transaction date for many cards, such as Mastercard. Banks like Chase require disputes within 60 days of the statement, while sources like Stripe note 120 days as typical. Acting quickly maximizes your protections.

This process supports everyday cardholders dealing with unauthorized transactions, billing errors, or unresponsive merchants. Secure your account first to avoid further issues, then try reaching the merchant if possible, and file a formal dispute online or by phone with your issuer. Banks acknowledge disputes in writing within 30 days and resolve them within two billing cycles, per Chase. In 2026, checking your bank's terms remains key for payment network protections.

Understand Your Dispute Timelines

Timelines vary by card type, error category, and issuer policies, so review your statements and terms right away. For billing errors under FCBA protections, consumers must dispute within 60 days of when the first bill with the error was sent, as outlined by Chase. Similarly, chargebacks911 advises lodging a dispute within 60 days of the statement date on which the error appeared for the strongest legal protections, and Chase echoes submitting within 60 days of the transaction first appearing on the statement.

In contrast, general disputes often allow 120 days from the transaction date. Stripe states consumers typically have 120 days to dispute a transaction, while chargebackhelp notes cardholders have 120 days for Mastercard transactions through their issuer, starting from the transaction date. These differences highlight statement-date focus for FCBA billing issues versus transaction-date starts for broader claims. Prioritize the shorter window if unsure, and always confirm with your issuer to avoid missing deadlines.

Valid Reasons to Dispute a Charge

Not every unwanted charge qualifies, but legitimate cases fall into clear categories. Valid reasons include fraud, where unauthorized use occurs without your permission. Authorization errors happen when a merchant charges without proper approval, such as duplicate transactions. Processing errors involve incorrect amounts or details, like a billing mistake not matching the purchase. Fulfillment errors cover goods or services not delivered as promised, including non-receipt or defective items.

Chargebacks911 classifies legitimate chargeback claims as fraud, authorization errors, processing errors, or fulfillment errors. Identifying your situation within these helps build a strong case. Gather receipts, emails, or photos as evidence, but stick to issuer guidelines rather than assuming approval.

Step-by-Step Process to Dispute a Charge

Follow this workflow to initiate and track your dispute effectively.

1. Secure your account first: For unauthorized transactions, take immediate steps to prevent more charges, such as locking your card or changing details, as recommended by N26.

2. Contact the merchant if possible: Attempt resolution directly, especially for fulfillment issues, but proceed to your bank if unresponsive.

3. File the dispute with your bank: Once the charge posts, dispute online through your account portal or call the number on the back of your card, per Chase.

4. Provide evidence: Submit details like transaction info, communications, and supporting documents.

5. Track the response: Your bank must acknowledge the dispute in writing within 30 days and investigate, resolving within two billing cycles, according to Chase.

Europe-consommateurs notes banks assist with chargebacks if payment networks offer protection, so reference your contractual documents.

Choosing the Right Path: Bank Dispute vs. Merchant Contact

Decide based on responsiveness and protections using this practical decision tree:

• Start with the merchant: Reach out directly for quicker refunds on clear errors, like fulfillment issues. Document all attempts (emails, calls) as evidence.

• Escalate to bank if unresponsive: If no resolution or reply within a reasonable time, initiate a formal dispute with your issuer, as advised by N26.

• Check protections first: Before filing, review your bank's FAQs, terms, and payment network rules (e.g., Visa, Mastercard) to confirm eligibility, per europe-consommateurs.

Merchant contact suits cooperative cases; bank disputes provide formal leverage for fraud or non-response. In 2026, digital portals from issuers like Chase streamline this, but evidence strengthens outcomes.

FAQ

How soon must I dispute a charge under FCBA rules?
Under FCBA, dispute billing errors within 60 days of when the first bill with the error was sent, as per Chase.

What's the difference between 60-day and 120-day dispute windows?
The 60-day window applies to FCBA billing errors from the statement date (chargebacks911, Chase), while 120 days is general from the transaction date, such as for Mastercard (Stripe, chargebackhelp).

What should I do first for an unauthorized transaction?
Keep your account secure and prevent more unauthorized transactions, then pursue chargeback if the merchant is unresponsive (N26).

How does the bank respond after I file a dispute?
The bank acknowledges in writing within 30 days and resolves within two billing cycles (Chase).

Can I dispute a charge if the merchant won't refund me?
Yes, if the merchant is unresponsive, initiate a chargeback with your bank (N26).

Where do I check my bank's specific dispute protections?
Review your contractual documents, terms, and bank FAQs for payment network protections (europe-consommateurs).

Next, log into your bank's app or portal to check recent statements and dispute options. If needed, call the back-of-card number for personalized guidance from Consumoteca, your consumer resource.