Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →If an AI agent or AI subscription charged you without permission, act on two tracks immediately: report the transaction to your card issuer or bank through its official channel, and ask the AI provider to refund the payment and investigate the account. Save the statement line, receipt, account and agent logs, and every message before anything changes.
For a U.S. credit card, a written billing-error notice generally must reach the issuer within 60 calendar days after the statement showing the charge. Debit-card and electronic-transfer protections use different notice windows, including rules tied to two business days after loss or theft of a card or access device and a 60-day statement period in other cases. The correct deadline, liability and reimbursement depend on your country, payment rail, account type, transaction date and issuer rules.
As an Amazon Associate I earn from qualifying purchases.
Start with the first 30 minutes
Stop additional charges without destroying evidence
- Do not delete the AI account, receipts, logs or emails yet. Export or photograph the information first.
- Check whether the charge is one payment or a recurring authorization. If a subscription is still active, cancel renewal in the account settings after saving the account page and cancellation confirmation.
- If you see unfamiliar activity, sign out other sessions and revoke unknown API keys or connected applications. Do not rely on account security changes as a substitute for a payment dispute; they prevent new charges but do not reverse an existing one.
Call the financial institution using a trusted channel
Use the telephone number printed on the physical card, the bank’s official mobile app or a branch you already know. Avoid numbers in an unexpected email, text message or pop-up. Tell the representative that the transaction is unauthorized, not merely that you want to cancel a subscription. Ask for the case number, the evidence they want, the deadline for written notice and whether the card or account should be replaced.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRecord the transaction before it changes
Write down the merchant descriptor exactly as it appears, amount, currency, posting date, transaction date if different, transaction or invoice number, payment rail and the last four digits of the funding account. A descriptor may differ from the AI product’s public name, so keep both names in your notes.
#1 Best Overall
Identify the payment rail before choosing the dispute route
The funding method controls the notice rules and who can provide temporary credit. Use the statement, wallet history or invoice to classify the charge.
| Payment rail | First report | Key timing noted in U.S. guidance | Evidence to preserve | Parallel action and escalation |
|---|---|---|---|---|
| Credit card | Card issuer; then the AI merchant | Written billing-error notice should reach the billing-inquiries address within 60 calendar days after the statement showing the charge (Consumer Financial Protection Bureau, 2024). | Statement page, receipt, account history, cancellation record, agent or API logs, and correspondence | Ask the issuer for its written dispute process. Visa directs consumers to the issuer for unauthorized-charge disputes. Keep the issuer case open until the refund is posted and the issuer explains how to update the case. |
| Debit card or U.S. electronic transfer | Bank or credit union immediately | CFPB guidance describes a general 10-business-day investigation period, a two-business-day window after loss or theft of a card or access device, and a 60-day statement rule in other situations. Temporary credit may be required when an investigation takes longer, subject to exceptions (CFPB, 2026). | Account statement, transfer confirmation, device-loss timeline, login history and any police or fraud report | Follow the bank’s electronic-transfer procedure and ask when provisional credit will appear. Escalate through the bank’s complaint channel and the applicable consumer-protection authority if unresolved. |
| Digital wallet | The wallet and the linked card or bank | Protection depends on the wallet terms, funding source and jurisdiction; no single deadline applies to every wallet. | Wallet transaction screen, linked-account statement, wallet case number and device/session records | Open parallel cases and retain both numbers. The linked issuer’s rules still matter even when the wallet displays the charge. |
| Invoice or business account | Vendor, accounting team and the funding institution | Contract terms, bank rules and local law control; an invoice due date is not a substitute for a fraud notice. | Invoice, purchase order, authorization policy, user-access logs, API keys and approval history | Freeze compromised credentials, require a second approver and use the organization’s formal vendor-dispute process. |
Preserve evidence that can prove the payment was unauthorized
Financial institutions and merchants decide disputes from records, not from a description alone. Make a dated evidence folder and keep original files as well as copies.
- Payment records: Save the statement line, receipt, invoice, wallet screen and any authorization or renewal notice. Capture the URL or screen path where the transaction appears.
- AI-account records: Export subscription history, organization or workspace membership, user invitations, agent run history, API usage, token consumption and account settings.
- Access records: Preserve login alerts, device names, IP or location information shown by the service, password-reset messages, multifactor-authentication events and connected-app permissions.
- Communications: Keep support tickets, chat transcripts, emails and the date and time of every phone call. Record representative names when provided and every case number.
- Your timeline: Note when you first noticed the charge, when you lost a device or access credential if applicable, when you contacted the bank and merchant, and what each party promised.
The Federal Trade Commission advises contacting the seller or issuer quickly and keeping copies of dispute documents. Do not edit screenshots to highlight a line; save an untouched original and make a marked copy if needed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use the credit-card billing-error process
Make the call, then send written notice
A phone call can block a card or start an investigation, but a U.S. credit-card billing-error dispute also requires written notice to the billing-inquiries address shown on the statement. Send it within the 60-calendar-day period described in the table, keep a complete copy and obtain proof of delivery. Sending it to a payments address or the general customer-service email may delay processing.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Identify the account, the transaction date and amount, state that you did not authorize the AI-agent payment, explain that you are requesting correction of a billing error, and attach copies rather than originals. Ask the issuer to tell you whether it needs a fraud affidavit, replacement card or additional identity verification.
Do not close the case when the merchant promises a refund
Tell the issuer that you have contacted the merchant, but keep the formal dispute open until the credit is visible and the issuer tells you how to update or withdraw the case. A merchant’s promise in chat is not the same as a posted refund. If the merchant issues a credit, send the confirmation and posting date to the issuer so the account is not credited twice.
Understand what the issuer may request
Common requests include a signed statement, proof that you controlled the account, confirmation that you cancelled a recurring service, or a description of who had access to the device or API key. Answer accurately. Do not claim a payment was stolen if you authorized the original subscription but dispute a later renewal; describe the exact event you did not authorize.
Handle debit cards and electronic transfers differently
Debit-card and electronic-transfer cases can involve money leaving a deposit account immediately, so notify the bank or credit union as soon as you discover the transaction. The CFPB’s 2026 guidance describes a general 10-business-day investigation period. It also identifies a two-business-day notice window after loss or theft of a card or access device and a 60-day statement rule for other situations; the applicable rule depends on the transfer and the facts. When a longer investigation is allowed, temporary credit may be required, subject to exceptions.
Tell the bank whether the card itself was lost, whether credentials were compromised, whether an electronic transfer was initiated through online banking, and whether you still possess the device. Ask what date the bank treats as your notice date, when provisional credit will be issued, and what documents are required. If the bank says the transaction was authorized because a valid password or token was used, explain any evidence of account takeover, unfamiliar device access or a compromised API key.
Replace a compromised debit card and change the related online-banking credentials through the bank’s official process. Monitor the account for small test transactions and additional transfers while the investigation is pending.
Report wallet, invoice and business-account charges on both sides
Digital wallets
Open a case with the wallet and another with the linked card issuer or bank. A wallet may show a merchant dispute as pending while the underlying card has already posted the transaction. Give each party the other case number and explain whether the wallet was funded by a card, bank account or stored balance. Do not assume that a wallet’s purchase-protection policy replaces the funding source’s dispute rights.
Invoices and business accounts
Notify the vendor’s billing or security contact and your accounting or treasury team. Suspend the affected user, rotate API keys, preserve approval and audit logs, and check whether the invoice bypassed your purchase-order or dual-approval controls. If an employee authorized the AI service but an attacker changed the billing destination, describe the account takeover separately from the underlying service purchase.
Rank #4
Ask the AI provider for a refund and an account investigation
Contact the provider through the support address or in-product help path you used for the account, and send a concise written request. Include the merchant descriptor, amount, currency, date, invoice or transaction number and the account identifier. State that you did not authorize the payment and request:
- Confirmation of the account, workspace or API key that generated the charge;
- Logs showing the purchase, renewal or payment-method change, with timestamps and time zone;
- Immediate cancellation of recurring billing and revocation of unknown sessions, users, connected applications and keys;
- A refund to the original payment method; and
- Written confirmation of the case number and the provider’s retention or investigation steps.
Do not send a full card number, security code or password. A legitimate support team should not need those details to locate a transaction. If the provider refuses to share internal logs for security reasons, ask for a transaction reference and a statement that the account was reviewed; give that response to the issuer.
Message you can adapt
Subject: Unauthorized AI-agent payment — refund and account investigation requested
I did not authorize the payment identified by the merchant descriptor, amount, currency, date and transaction number shown in my account records. Please stop any recurring billing, secure the account, identify the workspace or credential that created the charge, and refund the original payment method. Please confirm the case number and provide written confirmation of the investigation. I have also notified my card issuer or bank.Secure the account, devices and credentials
After preserving evidence, change the AI-service password and any reused password, enable multifactor authentication, revoke unknown sessions and rotate API keys. Review organization members, delegated billing permissions, browser extensions and connected applications. If the account uses single sign-on, review the identity provider’s active sessions and recovery methods.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Scan devices for malware when you see unfamiliar software, browser redirects, new administrator accounts or repeated credential theft. If a work device may be compromised, involve the organization’s security team before wiping it so logs are not destroyed. Security remediation stops repeat charges; it does not itself create a refund or chargeback.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Know what can delay or weaken a dispute
- Waiting for merchant support: A support queue does not pause an issuer’s notice deadline. Notify the financial institution first and pursue the merchant in parallel.
- Using an untrusted phone number: Fraudsters sometimes impersonate billing departments. Start with the card, bank or wallet application you opened yourself.
- Calling a charge unauthorized when it was a mistaken renewal: Distinguish an account takeover, an unrecognized descriptor, a cancelled subscription that renewed, and a service-quality complaint. The remedies and evidence differ.
- Deleting the account: Deletion can remove logs needed to establish what happened. Export records and obtain the merchant case number before closing anything.
- Submitting duplicate disputes: Tell every party about existing cases and any refund. Duplicate credits can be reversed and may complicate the investigation.
- Ignoring currency or cross-border issues: The posted amount, conversion rate, merchant location and local consumer law may differ from the AI provider’s invoice. Record both currencies and ask which entity processed the payment.
- Assuming a valid login proves authorization: An attacker can use a stolen session, API key or compromised mailbox. Provide the access timeline and device evidence instead of guessing who acted.
Escalate when the first response is inadequate
- Request the issuer’s or bank’s written explanation, the evidence relied on and the next review step. Keep the case number and all submission receipts.
- Send any missing documents in one organized package with a cover page listing the transaction and timeline.
- If the financial institution or provider does not resolve the case, use its formal complaint or executive-escalation channel.
- For a U.S. financial-institution dispute, submit a complaint to the applicable consumer-protection channel and include the institution’s response, dates and case number. Do not send passwords or complete card numbers in a complaint.
- For a business account, involve counsel, an insurer or a contracted incident-response team when the amount, data exposure or operational impact is material.
Escalation agencies can review handling and compliance, but they cannot guarantee that every disputed payment will be reimbursed. Continue monitoring the account while a complaint is pending.
What outcome to expect
A merchant refund is usually posted back to the original funding source, while a card dispute may appear as a temporary or provisional credit during investigation. A provisional credit is not necessarily final; it can be removed if the issuer concludes the transaction was authorized or the evidence is incomplete. Ask when the investigation is considered closed and how to challenge an adverse decision.
Keep the final statement, refund confirmation or decision letter with your evidence folder. If the provider credits only part of the amount, compare the posted credit with the original currency and transaction fee, then notify the issuer of the remaining balance. If there is no credit, request the precise reason and the appeal route rather than reopening the same case repeatedly.
Prevent another unauthorized AI charge
- Use a dedicated virtual or low-limit payment method for experimental AI services where your issuer permits it.
- Turn on transaction alerts and review recurring payments monthly.
- Limit who can create agents, add payment methods, invite users or change billing permissions.
- Set usage, spending and API-rate limits inside the AI service and at the organization level.
- Require multifactor authentication and separate administrator and billing accounts.
- Review connected applications, browser sessions and API keys after staff or contractor access ends.
- Keep invoices, approvals and cancellation confirmations in a central, dated record.
The safest sequence is consistent: preserve the record, notify the official issuer or bank promptly, send any required written notice, ask the AI provider for a parallel refund and investigation, and secure every credential that could create another charge.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
