Most chargebacks are not lost on the merits — they are lost to a forgotten date. Tell us your deadline once and we email you 15 days and 3 days before it, with a calendar file as backstop. The date is yours, confirmed by you: your bank's date controls — this is the alarm clock, not the referee.
Save your deadline — we watch the calendar
Free, no account. Don't have your deadline yet? Work it out with the deadline calculator or Scan to Dispute first — the reminder block also appears under their results.
Advertisement
How it works
Three steps, and the two backstops
Confirm your date. Type the deadline you already worked out — the date is spelled back to you in words ("Monday, March 15, 2027") so a slipped digit is easy to catch. This service never invents a date for you; if you don't have one yet, the calculator computes it from the published rules.
Tick the box, save. The consent box starts unticked — always; pre-ticked consent is a dark pattern and this is the anti-trap site. Saving stores only your email, the date and the moment you asked.
Get reminded twice — plus a file that can't fail silently. A confirmation email arrives straight away so you can whitelist us. Then reminders land 15 days and 3 days before the date. And the calendar file you download at signup carries its own alarms on the same schedule, in your own calendar app, whether or not any email survives a spam filter.
The honest limits
The date is an estimate, and your bank's date controls. Federal clocks run from the day your statement was sent; network clocks run from processing dates; your issuer can be stricter than both. A reminder service that "guaranteed" your deadline would be lying to you — this one reminds you about the date you confirmed, early enough that a few days of disagreement cannot hurt you. That is exactly why there are two reminders, and why the first one comes a full 15 days out.
Email can fail; that is planned for. Reminders are sent over authenticated SMTP (SPF/DKIM-aligned) from hello@chargebackclock.com, never from a bulk sender. Even so: spam filters exist, inboxes fill up, people change addresses. The calendar file is the backstop that depends on none of that. Download it. Every time.
Why deadlines decide chargebacks
The two-clock problem, the 60-day federal windows, and why "I'll do it next week" is the most expensive sentence in a dispute — explained in the companion guide.
You give us an email address and the dispute deadline you have already worked out (or one our calculator or Scan to Dispute just gave you). We email you twice: 15 days before the date and 3 days before it. The moment you sign up you also get a calendar file (.ics) with its own alarms on the same schedule, so the reminder does not depend on email alone. Every email carries a one-click link that deletes your record completely.
No — and be suspicious of any service that guarantees one. The date is the one you confirmed, computed from the information you entered. It is an estimate for planning: your bank's date controls, and if your bank gives you a different date, follow your bank. Treat the reminder as a backup alarm, never as the official deadline itself.
That risk is real, and the design assumes it. At signup we send one confirmation email immediately, so you see our address in your inbox once and can check your spam folder and whitelist us before it matters. And the calendar file you download at signup rings its own alarms (15 days and 3 days before, at 9:00) even if no email ever arrives.
Only three things: your email address, the deadline date, and the moment you consented. No account, no card details, nothing about the charge itself. The record deletes itself automatically 7 days after the deadline passes, and you can delete it at any time with the one-click link in every email — deletion is complete, not just an unsubscribe flag.
No. The confirmation and the two reminders are all this service ever sends — no newsletter, no offers, no marketing. That is also a legal design choice: the emails stay purely about the reminder you asked for.
Sources (checked October 24, 2026): Fair Credit Billing Act, 15 U.S.C. §1666 (60 days from the statement being sent, credit cards); Regulation E, 12 CFR §1005.11 and §1005.6 (60 days, debit; liability tiers); FTC, "CAN-SPAM Act: A Compliance Guide for Business" (ftc.gov — accurate From/subject, working unsubscribe, postal address; the transactional categories are read narrowly, so these emails are built to the full commercial standard); ICO consent guidance (ico.org.uk — consent freely given, specific, informed and unambiguous; withdrawal as easy as consent); Hostinger support, "PHP Mail limitation explained" (why sending is authenticated SMTP, never raw mail()).
General information only — not legal advice. A reminder is a planning aid built on a date you supplied. Your cardholder agreement governs your dispute; verify close calls with your issuer.
Chargeback Clock