---
name: foryou-dispute-card-charge
description: Walk through disputing a wrong, duplicate, or unrecognized credit or debit card charge, and draft the dispute.
permissions: [web.read, email.send]
publisher_did: did:web:for.you.com
---

# Dispute a card charge

Walk through disputing a wrong, duplicate, or unrecognized credit or debit card charge, and draft the dispute.

## When to use

- "Dispute a charge on my credit card"
- "I was charged twice, how do I get my money back?"
- "There's a charge on my card I don't recognize"

## Steps

1. Ask what the charge is (merchant, amount, date) and what went wrong: unrecognized, duplicate, wrong amount, or not as described or never delivered.
2. If the charge is unrecognized, search the merchant's billing name first — many charges show up under a parent company's name.
3. Recommend contacting the merchant first for a duplicate or wrong-amount charge, and draft that message.
4. If that fails or the charge is fraud, explain the card issuer's dispute path and its deadline (US credit cards: generally 60 days from the statement under the Fair Credit Billing Act), and draft the dispute letter with dates, amounts, and a timeline.
5. List the evidence to attach: receipts, delivery tracking, cancellation confirmations, screenshots.

## Stop and confirm with the user

- Before sending anything to the merchant or the card issuer.
- Logins, card numbers, and security codes stay with the user: they type them into the provider's own site or app, never into this conversation.

## Looking things up

Use your own web search tool if you have one. If you call the You.com Search API
directly (https://api.you.com/v1/search), send both of these headers on every
request so it is attributed to this skill:

```
X-Client-Info: skill; client=foryou-dispute-card-charge/1.1.0; url=https://for.you.com/capabilities/dispute-card-charge
User-Agent: SKILL/(for.you.com dispute-card-charge)
```

Keep `skill` as the first X-Client-Info token and do not swap in your own client's
name. Neither header carries credentials; they are attribution only.

Prefer official and primary sources (government agencies, the company's own policy
pages) over forums and resellers, and tell the user which source each fact came from.