What Is Account Takeover Fraud and How Do You Stop It?

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000+ merchants.
.avif)
TL;DR:
- Account takeover fraud is the use of a real customer account by someone who is not its owner, so the history looks trustworthy.
- Detect it from combinations of signals, such as a reset, a new device, and a new delivery address before one order.
- Passkeys resist the phishing and code relay that defeat SMS and app codes.
- Hold suspect orders for review after checkout and before fulfillment, since login controls miss some takeovers.
- Accept disputes the real customer confirms, and refund through chargeback alerts where you can.
Account takeover (ATO) fraud happens when someone else gets control of a real customer account. They use stolen passwords, phishing, a SIM swap, or a hijacked session. Then they place orders, spend stored value, or change account details.
For a merchant, the account is genuine. The person in the current session is not. ATO is one of several types of payment fraud, and this guide covers the account-level version.
What Is Account Takeover Fraud?
Account takeover fraud is the unauthorized use of an existing account by someone who is not its owner. That is the core account takeover meaning: the login is real, the history is real, and the intent is not.
This is why ATO is hard to spot. A familiar email, years of order history, and a saved card all make the session look normal. So check how the account was accessed and what changed, not only the payment.
Securing the account and handling the unauthorized orders are two separate jobs. Each needs its own decision and its own record.
How Big Is Account Takeover Fraud?
- $15.6B
- Reported US account takeover losses in 2024, up from $12.7B in 2023
- 36%
- Rise in account takeover suspicious activity reports, 2024 vs. 2023
- $262M+
- Losses across 5,100+ FBI IC3 account takeover complaints, Jan to Nov 2025
- 22%
- Of breaches in the 2025 Verizon DBIR began with compromised credentials
Sources: Federal Reserve Financial Services (February 2026, citing one industry study and FinCEN reports); FBI Internet Crime Complaint Center (November 2025); Verizon 2025 Data Breach Investigations Report.
Most of these figures come from banking. But the attack inputs are the same for a store login. Verizon found that infected users reused passwords widely: only 49% of their passwords across services were distinct.
Credential stuffing made up a median 19% of authentication attempts in the same research (25% at enterprises, 12% at small businesses). One password reused from an old breach can open a customer's store account.
Established Accounts Still Need Current-Session Checks
In its October 22, 2026 fraud research announcement, TransUnion describes attacks that exploit existing customer relationships, not only new accounts. That supports checking activity across the whole customer relationship. It does not give an ecommerce account takeover rate.
What this means for merchants: a saved card and years of orders prove a relationship, not consent for today's purchase. Say a password reset is followed by a new delivery address and an unusual order. Compare the session, account-change, and order records before you ship. Judge the combination, not one change on its own.
How Account Takeover Happens
Most takeovers start with stolen credentials, phishing, an abused recovery flow, or a stolen session. The attacker then changes contact details, adds a delivery address, or spends through a saved payment method. When the cardholder did not approve the purchase, it becomes card-not-present payment fraud.
A new delivery address can also point to a triangulation fraud scam. In that scheme, goods bought with stolen card details ship to a buyer who has no idea.
| Entry method | How it works | What you see on your side |
|---|---|---|
| Credential stuffing | Bots replay username and password pairs leaked from other sites against your login page | Bursts of failed logins across many accounts and rotating IPs, with a few successes |
| Phishing and fake support | Customers land on a lookalike login page, or someone posing as support talks them into sharing a one-time code | A valid login and correct code, followed at once by recovery or contact changes |
| Infostealer malware and session theft | Malware on the customer's device captures saved passwords and session cookies | A session that is already logged in, from a device you have not seen, with no login challenge |
| Recovery abuse | The attacker uses password reset, a support request, or a hijacked inbox to take the account | A reset request followed by an email, phone, or address change |
| SIM swap | The customer's phone number moves to the attacker's SIM, so SMS codes arrive there | A correct SMS code on a new device, then sensitive account changes |
| Impersonation and search ads | Fraudsters pose as support or buy search ads that copy a real business to collect logins and codes | Customers reporting calls, texts, or sites that did not come from you |
Here is an illustrative sequence. It shows why each step is easy to miss:
- Dozens of failed logins arrive from rotating IPs. One succeeds on a three-year-old account.
- Within minutes, the email address and phone number change.
- A new shipping address is added. The saved card buys two high-resale items.
- The order confirmation goes to the new email, so the real customer sees nothing.
- Weeks later, the customer spots the charge and disputes it.
Account Takeover Fraud Examples by Business Model
The attack looks different depending on what the account holds. These illustrative patterns show where the value sits and which control catches it first.
| Business model | What the attacker takes | Early warning sign | First control to add |
|---|---|---|---|
| Retail store with saved cards | High-resale goods shipped to a new address | Address added minutes before checkout | Hold the order for review before fulfillment |
| Loyalty or rewards program | Points redeemed for gift cards or transferred out | Email change followed by a full balance redemption | Step-up check before redemption or transfer |
| Gift card or store credit balance | Stored value spent or moved to another account | Balance drained in one session from a new device | Delay first-time transfers and notify the old email |
| Subscription or SaaS account | Plan upgrades, add-ons, or access resold | Billing contact changed before an upgrade | Confirm billing changes through the established channel |
| Digital goods and game keys | Instant-delivery codes resold quickly | Many small purchases right after login | Velocity limits on new devices for instant delivery |
Stored value is the fastest target because nothing has to ship. For balance abuse that does not involve a takeover, see the guide to gift card fraud.
Account Takeover vs. Identity Theft and Related Fraud
| Fraud type | What the attacker uses | Who controls the account | Typical dispute claim |
|---|---|---|---|
| Account takeover | A real customer's credentials or session | The attacker, inside a genuine existing account | Unauthorized transaction |
| Identity theft (new account fraud) | Stolen personal data to open a new account | A new account in the victim's name | Unauthorized transaction, or the cardholder never opened the account |
| Friendly fraud | The cardholder's own authorized purchase | The genuine customer | Fraud or not-received claim despite a valid purchase |
| Card testing | Stolen card numbers tried with small charges | No account needed, often guest checkout | Unauthorized small charges |
| Stolen-card checkout | Stolen card details typed in at checkout | The attacker, on a new or guest account | Unauthorized transaction |
The key difference from identity theft: a takeover needs no new account. New-account checks never fire, and the account's history adds false trust. That is why account takeover identity theft cases are handled differently from new-account fraud.
Automated attacks such as card testing fraud and BIN attacks target the card number, not the account. Promo abuse is the mirror image: the real account owner abuses the offer.
Account takeover is also different from intentional friendly fraud. In a takeover, someone else controls the account. Do not label the real customer as abusive because their history includes orders placed during the compromise. If the cardholder made the purchase and later disputed it, that is first-party fraud, not ATO.
How to Detect Account Takeover
Account takeover detection works best on combinations of signals. No single signal proves fraud. Use this table to decide what to check next.
| Signal | Why it matters | What to check |
|---|---|---|
| Failed logins in bursts, then one success | The pattern matches credential stuffing | Failure ratio by IP range and by account, and what the successful session did next |
| Contact details changed before a purchase | The attacker may be redirecting account control | Whether the real customer recognizes the change |
| New device plus unusual spending | The session differs from normal behavior | Authentication, order pattern, and customer confirmation |
| Delivery destination changed after checkout | Goods may be redirected | Who approved the change and fulfillment status |
| Recovery requests followed by sensitive actions | Recovery may have been abused | Recovery events, verification, and later access |
| One device or IP touching many accounts | Account farming or a stuffing run | Accounts accessed, orders placed, and overlap with failed logins |
| Unexpected stored-value or payment activity | The account may be cashed out | Affected transactions and containment options |
A new device or location is not proof on its own. Travel, a new phone, and genuine recovery create the same signals. Give customers an easy review path so they can clear a false alarm without sharing extra personal data.
The last checkpoint is the order itself. Chargeflow Prevent scans orders after checkout and before fulfillment. A suspect order can be held, verified, or cancelled before goods ship. It sits behind your login controls and does not replace them.
{{cta}}
How to Prevent Account Takeover Fraud
Account takeover prevention starts with strong login, safe recovery, and alerts for important changes. The OWASP authentication guidance covers both normal login and higher-risk events. Give your recovery flow the same care as the login screen.
Ask for extra verification before sensitive changes, such as payment, payout, or delivery updates. The OWASP transaction authorization guidance separates logging in from approving a specific action. It also stresses server-side checks. A confirmation screen is not enough if the action can skip it.
Choose Multifactor Authentication That Resists Phishing
| Method | Stops credential stuffing | Stops phishing and real-time relay | Customer friction |
|---|---|---|---|
| Password only | No | No | None |
| Email or SMS one-time code | Yes | No. Codes can be phished or relayed, and SMS is exposed to SIM swap | Low |
| Authenticator app code | Yes | Partly. A real-time relay can still capture the code | Medium |
| Push approval | Yes | Partly. Repeated prompts can wear a customer down into approving | Low |
| Passkey or security key | Yes | Yes. The credential is bound to your real domain | Low to medium |
A Microsoft study looked at Azure accounts with suspicious activity. Multifactor authentication cut the risk of compromise by 99.22% overall and by 98.56% where credentials had leaked.
NIST's Digital Identity Guidelines (SP 800-63B-4) say verifiers must offer at least one phishing-resistant option at the AAL2 assurance level. For merchants, that points to passkeys as the strongest customer-facing option.
Add Friction Only When Risk Rises
Challenge risky sessions and let low-risk returning customers through. The OWASP credential stuffing guidance recommends conditional multifactor prompts. It warns that IP blocking and device fingerprints alone are easy to evade.
Account protection
Add checks at the sensitive moments
Password and attempt controls
Check new passwords against known-breach lists and rate-limit by account, device, and connection pattern rather than IP alone.
Sensitive changes
Step up authentication when a session changes payment, payout, or delivery details.
Trusted notifications
Send an alert to the old email or phone when key details change.
Customer education
Tell customers you never ask for a one-time code by phone or text. The FBI reports criminals posing as support teams to get these codes. Some also buy search ads that copy real businesses.
Secure recovery
Give customers a secure way to report and recover a compromised account.
Before goods leave
Check odd orders or new ship-to addresses before you ship.
Use the established contact and recovery routes. Travel, replacement devices, and genuine account recovery can produce similar signals.
Which Account Takeover Solutions Stop Which Attacks?
No single tool covers every entry point. Map each account takeover fraud solution to the attack it stops, what it misses, and who owns it. Gaps between layers are where takeovers get through.
| Layer | Stops | Misses | Usual owner |
|---|---|---|---|
| Bot management and rate limits | Credential stuffing at scale | Phishing, malware, and low-volume manual logins | Engineering or security |
| Breached-password checks | Reused passwords from known leaks | Fresh phished passwords and session theft | Engineering |
| Passkeys or security keys | Phishing, code relay, and SIM swap | Session cookies stolen by malware after login | Engineering and product |
| Risk-based step-up checks | Logins and changes from unusual devices | Attackers who copy the customer's device profile | Fraud or risk team |
| Change notifications to the old contact | Silent email, phone, or address changes | Attacks where the inbox is already hijacked | Product and support |
| Order review after checkout, before fulfillment | Takeover orders that pass login controls | Stored value spent instantly with no shipment | Fraud or operations |
| Chargeback alerts | Disputes on takeover orders that already settled | Losses already shipped or redeemed | Payments or finance |
Most merchants need the top four layers on the login and recovery flow, plus one checkpoint on the order. Stores with stored value or instant delivery should weight step-up checks highest, because there is no shipping window to stop the loss.
Contain a Suspected Takeover and Preserve the Timeline
Give one person ownership of the incident. They secure the account, keep the logs, and list affected orders. A password reset does not undo every attacker action.
Incident response
Secure the account and trace the affected activity
1Revoke and recover access
End the attacker's sessions and reset the stolen password through your normal recovery flow.
2Restore account settings
Review and restore changed contact details, delivery addresses, and saved payment settings.
3Preserve the timeline
Preserve login, recovery, device, and order logs.
4Identify affected value
List every order and balance change made while the account was compromised.
5Keep one incident record
Keep security decisions and support exceptions in a shared incident record.
Fixing the account and fixing the payment are two separate jobs. Check shipping, refund, and dispute status before you move money.
Check fulfillment status before you act on an order. An unshipped order, a package in transit, and delivered digital value each need a different response. Coordinate any hold, cancellation, refund, or entitlement change with your provider's tools and your customer obligations.
Contact the customer through a trusted route, not the contact details changed during the incident. Explain what happened in plain terms. Do not promise that every financial issue is already solved. Support and payments can use the shared dispute operations workflow to keep one consistent record.
Should You Fight a Chargeback From an Account Takeover?
Usually not, if the real customer confirms the compromise. When a payment is disputed, read the chargeback reason code and check the deadline. Takeover orders usually arrive as unauthorized-transaction claims.
| Network | Typical code for a takeover order | What the issuer is saying |
|---|---|---|
| Visa | 10.4 Other Fraud, Card-Absent Environment | The cardholder did not authorize this card-not-present purchase |
| Mastercard | 4837 No Cardholder Authorization | The cardholder did not take part in or approve the transaction |
| American Express | F29 Card Not Present | The card member denies a card-not-present charge |
| Discover | UA02 Fraud, Card-Not-Present Transaction | The cardholder denies a card-not-present transaction |
For the full Visa list, see Visa chargeback reason codes. Logs showing someone used the account do not prove the real cardholder approved the purchase. Look at the payment evidence and any liability shift before you decide.
| Situation | What to check | Likely response |
|---|---|---|
| Customer confirms the compromise and the order has not shipped | Fulfillment status and order time against the account changes | Cancel and refund. Accept any dispute that still follows |
| Customer confirms the compromise and goods were delivered | Delivery address added during the incident | Accept the dispute and use the address change to tune your step-up rules |
| Dispute filed, but device, IP, and address match earlier undisputed orders | Whether the history really matches | This is not a takeover pattern. Consider contesting |
| The order was authenticated with 3D Secure 2.0 | Authentication data held by your processor | Check whether liability shifted to the issuer before accepting |
| A chargeback alert arrives before a dispute opens | Whether the order is already refunded | Refund through the alert to prevent the chargeback |
Treat Visa Compelling Evidence 3.0 as a test, not a defense. It needs two undisputed prior transactions between 120 and 365 days old. At least two data elements must match across all three orders, and one must be an IP address or device ID.
A true takeover usually runs from a new device and a new address, so those elements fail to match. The real customer's past orders do not prove the intruder was the cardholder. When they do match, you may be looking at friendly fraud instead.
For a supported response, write a short timeline of account and payment events. Say what each record shows and what is still uncertain. The evidence standardization guide keeps security logs readable without flooding the reviewer.
If you already started a refund, match it against any dispute debit before you issue another credit. The workflow for a chargeback after a refund connects the records. Fixing account access does not close an open payment case.
Chargeback alerts let you refund a flagged transaction before it becomes a formal dispute. Chargeflow Alerts refunds each alert within 24 hours of receipt. For cases that still reach chargeback and are worth contesting, Chargeflow's automated chargeback recovery organizes the evidence and manages the response.
{{cta}}
Measure Recovery Quality and Control Effectiveness
Track time to secure the account, affected orders, fulfillment stopped, refund completion, repeat compromise, and customer recovery. Keep these apart from chargeback win rate. Accepting a valid unauthorized claim quickly can be the right outcome, even with no funds recovered.
Count the full cost of a takeover order, not only the refund. The LexisNexis Risk Solutions True Cost of Fraud study covers US and Canadian retail and ecommerce merchants. It puts the total cost at more than $5 for every $1 of direct fraud loss.
Fraud reports and disputes both feed card network ratios such as the Visa Acquirer Monitoring Program. A stuffing wave can raise your ratio even when every order is refunded.
Review false alarms and customer effort next to fraud losses. If a control keeps blocking normal recovery or travel, adjust the review process. For digital platforms, the guide to preventing chargebacks for digital goods adds detail on entitlement and usage records.
Takeover controls work best as one layer of your wider ecommerce fraud prevention stack and merchant fraud protection program. Attackers move to the weakest layer. Keep account security ownership clear, because dispute tooling does not replace session management or account recovery.
Frequently Asked Questions
What is account takeover fraud?
Account takeover fraud is when someone gains control of an existing customer account and uses it to buy goods, spend stored value, or change details. The account is genuine, but the person in control is not.
How does account takeover happen?
Most attackers use passwords leaked from other sites, phishing, fake support calls, malware, SIM swaps, or a weak recovery flow. They then change contact and delivery details before they spend.
What are examples of account takeover fraud?
A saved card ships goods to a new address. Loyalty points get redeemed for gift cards. Store credit is drained in one session. A subscription is upgraded right after the billing contact changes.
What is the difference between account takeover and identity theft?
Identity theft uses stolen personal data to open a new account in the victim's name. Account takeover hijacks an account that already exists, so new-account checks never fire and the history looks trustworthy.
How can you detect account takeover?
Look for signals that appear together. Examples are failed logins then a success, a new device, or contact changes right before a purchase. Route borderline cases to review.
How do you prevent account takeover without adding friction for customers?
Use risk-based step-up checks instead of challenging every login. Ask for a stronger check on new devices, recovery events, and payment or delivery changes. Offer passkeys, which are strong and easy to use.
Does multifactor authentication stop account takeover?
It blocks most compromise attempts, but not all. SMS and app codes can still be phished or relayed, so phishing-resistant methods such as passkeys add protection.
Is account takeover the same as friendly fraud?
No. In account takeover, someone else controls an existing account. In intentional friendly fraud, the buyer approved the purchase and disputes it anyway. Do not blame the real account owner for an intruder's actions.
Does resetting a password resolve an account takeover?
Not on its own. Also review active sessions, recovery methods, contact changes, and affected transactions. The right steps depend on how the account was compromised.
Do account logs prove a disputed payment was authorized?
No. Account logs show activity in the account, not cardholder consent. In a takeover case, that activity may belong to the intruder.
Catch Takeover Orders Before They Ship
Chargeflow Prevent scans orders after checkout and before fulfillment.

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.














.avif)


