← Back to library

Build a card dispute pack when a merchant won't refund

AI Guides (@free_ai_guides) posted a seven-prompt Grok Bot thread on recovering money; prompt six turns a refused or ignored refund into a file for your card issuer and pauses at the form. We add the FTC's plain rules for US credit card billing disputes and keep submission in your hands.

  • OutcomeWhen a company refuses a refund or never replies, get a dated dispute file for your bank, covering the charge, the purchase and every contact, plus a prefilled dispute form you submit yourself.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditAI Guides (@free_ai_guides)
View original
Works with
Grok BotChatGPT agentClaude

Published Oct 26, 2026Updated Oct 26, 2026AI dry run on sample input: passed Oct 26, 2026Source verified Oct 26, 2026

When should you use it?

  • A merchant turned down your refund, or has ignored you for two weeks
  • The amount is big enough that a formal card dispute is worth an hour
  • You have receipts, order pages and messages the agent can read

Not for: Charges you have not raised with the merchant yet (start with unwanted-charge-refund-recovery-audit); Suspected fraud or identity theft, which belongs with your bank's fraud team straight away; Letting the agent press submit, or filling in dates and amounts the records do not show

What do you need, and what do you get?

You need

  • The smallest amount you think is worth disputing, and which card paid
  • Receipts, order confirmations, listing or service terms, and delivery records
  • All messages with the merchant, plus notes of phone calls with dates and reference numbers
  • Access to your bank's online dispute form or its written dispute instructions

You get

  • A shortlist of charges that meet your amount and no-reply rules
  • One file per charge: the transaction, what was promised, what actually happened, and a dated contact log
  • The dispute form on your bank's site, completed from that file and left unsubmitted
  • Flags for gaps, such as an undated call or a dispute window that is about to close

How does it work, step by step?

  1. Set your rulesGive the agent your minimum amount and how many days the merchant has had to respond, then let it read statements and the inbox.
  2. Shortlist chargesKeep only charges the merchant refused or left unanswered past your cutoff. Drop anything where a refund is already in motion.
  3. Assemble each filePer charge, gather the statement line, the order or service terms, a plain account of the problem, and every contact in date order.
  4. Check the clockNote the statement date and your issuer's dispute window. For US credit cards, the FTC guide linked below explains the written billing-error notice and its 60-day limit.
  5. Fill, then stopLet it complete the bank's form from the file. Read every field yourself before deciding whether to submit.

The prompt

The original prompt by @free_ai_guides, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT agent and Claude. Values in lime are placeholders.

Original prompt by @free_ai_guides

Word for wordby @free_ai_guides
For anything over [AMOUNT] where the company refused or didn't reply in 14 days, build me the dispute pack for my bank: the charge, what I bought, what went wrong, and every email and call with dates. Fill in the bank's dispute form and stop before you submit.

Exactly as published by @free_ai_guides in X thread: 7 prompts to get your money back (prompt 6, the chargeback).

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt4 variables
Help me prepare card disputes, but do not submit anything.
Minimum amount: {min_amount}. Merchant response cutoff: {cutoff_days} days. Card and bank: {card_and_bank}.
Records you may read: {records_access}.

1) List charges at or above the minimum where the merchant refused a refund or has not answered within the cutoff. Skip any refund already in progress.
2) For each, build a file: statement line (date, amount, merchant), what I ordered and the terms that applied, what went wrong, and a contact log in date order with reference numbers.
3) Mark any missing date or document as missing. Never estimate dates or amounts.
4) Note the statement date and the dispute window from my bank's terms, and warn me if it closes within 14 days.
5) Fill in my bank's dispute form from the file, then wait while I check each field. Submitting is my decision.

What can go wrong?

  • Card dispute windows are limited and usually run from the charge or statement date, not from when the merchant went quiet. Check yours early.
  • Debit cards, payment apps and cards issued outside the US follow different rules from US credit cards; read your own bank's terms.
  • Guessed dates weaken a case. Mark any unknown call date as unknown instead of estimating it.
  • Filing while the merchant is still processing a refund can leave you with a double credit that gets reversed later.

Our take

A card dispute is often the last real lever after a merchant refuses, and most people lose it by waiting or by sending a messy story. The thread's prompt is useful because it sets clear entry rules (an amount floor and a response cutoff), asks for a dated record of every contact, and stops before the form goes in. We added two things it leaves out. First, the clock: card dispute windows are limited and usually counted from the charge or statement, so a slow merchant can quietly run out your time. For US credit cards, the FTC's guide explains the written billing-error notice and its 60-day limit; debit cards, payment apps and non-US cards work differently, so check your own bank. Second, honesty: an undated call should stay undated, and a refund already in progress should not be disputed at the same time. Use this after the merchant route, not instead of it; for the first ask, run unwanted-charge-refund-recovery-audit. In our dry run with fictional records (a $189 seat upgrade the airline refused to refund, a $42 debit card charge after a canceled plan with no reply for 20 days, a $15 charge under the $40 floor, and a $120 order where the seller replied five days ago), the agent shortlisted only the first two, built a dated contact log for each, flagged one phone call with no date as unknown, noted that the debit charge follows different rules, filled the mock bank form for the $189 charge and stopped before submitting.

Where the time goes back: Banks ask for the same facts every time. Having them dated and in one file turns an evening of digging through old mail into a short review.

FAQ

How is this different from unwanted-charge-refund-recovery-audit?
That audit drafts refund requests to the merchant. This one starts after the merchant has said no or gone silent, and builds the file your card issuer will ask for.
Will the agent submit the dispute for me?
No. It completes the form and pauses. You review it and choose whether to submit.
What deadline applies to my dispute?
It depends on the card and the country. For US credit cards, the FTC says your written billing-error notice has to arrive at the card company no later than 60 days after it sent the first statement with the error. Debit cards and other countries have their own rules, so check with your bank.
Is this legal advice?
No. It organizes your own records so the request is clear. Your bank decides the outcome.

Source and credit

The original prompt on this page is by @free_ai_guides, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
X thread: 7 prompts to get your money back (prompt 6, the chargeback)
Creator
AI Guides (@free_ai_guides)
Published on
X
Original date
Oct 25, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Grok Bot
AI dry run
Oct 26, 2026: passed. Dry-run tested by our AI test agent on sample input. Floor and cutoff applied; refund-in-progress skipped; no invented dates; debit flagged; nothing submitted.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 26, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Also see: Using Credit Cards and Disputing Charges by Federal Trade Commission (FTC). More official guidance we used; credited and linked only, nothing from it is reproduced word for word. Not legal or financial advice.

Are you the creator? Claim or correct this page.

More in Money & Admin

All 82 Money & Admin playbooks →

Related playbooks

Money & AdminPrompt✓ AI dry run

Audit internet and phone bills before you negotiate

Compare your current internet and phone plans to verified offers at your address, then get a negotiation draft you approve before anyone is contacted.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Money & AdminPrompt✓ AI dry run

Audit subscriptions from statements before you cancel

From 12 months of bank statements and billing emails, get a ranked cancel list with renewal dates, fees and evidence — then approve every cancel yourself.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Money & AdminPrompt✓ AI dry run

Check whether your car insurance renewal is competitive

Compare your renewal to like-for-like quotes on cover you approve, see what you would give up for a lower price, and keep purchase or cancel behind your approval.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Money & AdminPrompt✓ AI dry run

Run a Friday check on money you're owed

Each Friday, get a short tally of late orders, unexplained charges and renewals due within a month, with money owed split into confirmed and still to check.

Credit: AI Guides (@free_ai_guides)

Minutes
Money & AdminPrompt✓ AI dry run

Run a monthly personal subscription audit

Once a month, get a clean list of recurring charges with annual cost, unused or duplicate flags, and cancel or negotiate drafts you send yourself.

Credit: Miles Deutscher (@milesdeutscher)

Minutes