Discover · Chargeback reason codes
Discover 4757 chargeback: Violation of Operating Regulations explained
Checked
Discover reason code 4757, Violation of Operating Regulations (older letter code TF), is a dispute that Discover itself initiates because a transaction broke its operating regulations. Fiserv's guide gives 120 days and no later than 540 days, and offers no specific defence. Stripe also lists 6050 Disputes Compliance. Ask your processor which rule was cited and answer that rule directly.
- Category
- Compliance
- Time limit for the bank to file
- 120 days, no later than 540 days (Fiserv guide, 2016)
- Time limit to respond
- Your processor's deadline: Stripe says usually 7–21 days depending on the network; Adyen gives 25 days for Discover
- Typical evidence
- Evidence answering the specific rule cited
- Can it be prevented?
- Yes: follow Discover's acceptance rules
- Who usually wins
- Depends on the rule cited
What PlatformDTC does
PlatformDTC answers this kind of dispute with its standard evidence pack built from the order: customer name, email, IP address, billing and shipping address, items bought, carrier, tracking and ship date, the refund policy, and any refund already issued. With "Answer a chargeback automatically" switched on, it sends the response to the bank for you before the deadline.
What it means
Discover says the transaction did not comply with its operating regulations.
Older Discover documentation pairs 4757 with the letter code TF.
Why customers file it
Acceptance or processing practices that break network rules.
Evidence that wins
Respond to every Discover chargeback, even small ones, as Discover itself advises. Send:
- The rule cited and evidence that the transaction complied
- Order, authorization and delivery records
How to prevent it
- Follow card acceptance and processing rules
- Ask your processor about any compliance notices
For developers
On Stripe the dispute object arrives with reason "general" and the card network's own code in payment_method_details.card.network_reason_code; listen for charge.dispute.created and read evidence_details.due_by for the deadline.
Discover does not publish its dispute rules publicly; the codes and names here are the ones Stripe reports, and the defences come from processor guides.
Frequently asked questions
- Who starts a 4757?
- Discover itself, for a breach of its operating regulations.
- Is there a standard defence?
- Fiserv's guide gives none; answer the specific rule cited.
Sources
- Dispute categories and network reason codes — Stripe
- Dispute Management Guide, Discover chapter (Rev 04/16) — First Data (Fiserv)
- Dispute reason codes: Discover — Adyen
Related
- 4762 — A late dispute raised after the normal chargeback window, within 2 years of processing.
- 7030 — The cardholder says they did not make an online, phone or mail order purchase.
- 7010 — The cardholder denies an in-person purchase.
- 4866 — A counterfeit chip card was used where the chip was not read.
- 4867 — A lost or stolen chip-and-PIN card was used where chip and PIN were not used.
- 4752 — The cardholder does not recognize the charge on their statement.