# Account Fraud
Source: https://paymentsandrisk.com/docs/fraud/types/application-fraud

Last updated 4 November 2026.

TL;DR

-   **Account fraud** means fake or malicious accounts created on your platform
-   Types: Bot signups, referral abuse, multi-accounting, fake reviews
-   It can be infrastructure for what comes next, and signup rewards, messages and verification can cost you before that
-   Detect via: device fingerprinting, email analysis, behavioral patterns
-   Prevent with: CAPTCHA, email verification, phone verification, rate limiting

Not every signup is a customer. A fake account can be the setup for something later. You may see this called application fraud, which means something broader in lending and onboarding ([classification](https://paymentsandrisk.com/docs/reference/fraud-classification/)).

Account fraud is **fake or abusive accounts** on your site or app. They can cost you at signup, through rewards, messages and verification ([Twilio Verify's pricing](https://www.twilio.com/en-us/verify/pricing) shows one way that's billed). The bigger trap is what they enable: [promo abuse](https://paymentsandrisk.com/docs/fraud/types/promo-abuse/), [refund fraud](https://paymentsandrisk.com/docs/fraud/types/refund-fraud/), fake reviews and [organized attacks](https://paymentsandrisk.com/docs/fraud/types/bust-out/).

## Why Fake Accounts Matter

| They Enable | How |
| --- | --- |
| [Promo abuse](https://paymentsandrisk.com/docs/fraud/types/promo-abuse/) | New account = new discount |
| [Referral fraud](https://paymentsandrisk.com/docs/fraud/types/promo-abuse/) | Self-refer across accounts |
| Velocity evasion | Spread activity across accounts |
| [Card testing](https://paymentsandrisk.com/docs/fraud/types/card-testing/) | Disposable accounts for testing |
| Fake reviews | Boost or attack products |
| Limit evasion | Getting around a purchase limit with extra accounts. Bulk buying for resale isn't fraud by itself |

## Common Patterns

### Bot Signups

Automated signups at scale:

-   Hundreds of accounts in hours
-   Similar registration patterns
-   Disposable email domains
-   Generic or random usernames

### Referral Fraud

Gaming referral programs:

-   Self-referral across accounts
-   "Referral farms" with fake accounts
-   Quick signup → claim reward → abandon

### Multi-Accounting

One person, multiple identities:

-   Evade account-level limits
-   Stack promotions
-   Bypass bans or restrictions
-   Separate fraud activity from "real" account

### Fake Review Fraud

Social proof that isn't.

-   Paid review rings
-   Competitor sabotage
-   Boosting new products artificially

## Detection Signals

Compare these with your real signups and your program's terms, and check shared devices and autofill before you assign a motive.

### Registration Red Flags

| Signal | Priority to Check |
| --- | --- |
| Disposable email domain | Next |
| Email pattern matches prior confirmed fraud | First |
| [Device](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/) seen on multiple accounts | First, once you've ruled out a shared, work or public device |
| Signup form completed faster than a person could type it | Next. [Autofill](https://support.google.com/chrome/answer/14271924?hl=en) does this too |
| Phone number from an internet calling (VoIP) provider | Next |
| Similar usernames across accounts | Next |

### Email Analysis

| Pattern | What It Suggests |
| --- | --- |
| john+1@gmail, john+2@gmail | Possibly multi-accounting. Plus addresses are also a normal feature |
| Random string @domain.com | Possibly bot-generated |
| Recently registered domain | Check its age against your own signup history; a new domain alone doesn't establish fraud |
| Known disposable domain | Possibly a temporary account |
| Email with no history in your enrichment provider's sources | Investigate with the other signup signals. Little history doesn't prove the account is fake |

### Device Signals

Device fingerprinting ([what it reads](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/)) can link accounts. The other signals depend on what your integration returns, so ask which fields you get and how sure they are:

-   Same device across multiple accounts
-   Emulator or automation tools, if your provider detects them
-   VPN/proxy usage, if your provider detects it
-   A reputation flag on the device, if you buy one. A match isn't confirmed fraud

### Behavioral Indicators

| Behavior | What It Could Be |
| --- | --- |
| No browsing before checkout | Possibly a script. Or a customer following a link |
| Immediate promo redemption | Possibly promo farming. Or someone who came for the promo |
| Referral link used instantly | Possibly self-referral. Or a friend who sent it |
| Never returns after signup | Possibly a throwaway account. Real signups can do this too |
| Review posted without purchase | Possible fake review |

## Prevention Strategies

### At Registration

None of these stops everything, so expect errors and workarounds.

| Control | What It Does |
| --- | --- |
| CAPTCHA | Challenges suspected bots ([how reCAPTCHA scores work](https://docs.cloud.google.com/recaptcha/docs/interpret-assessment-website)) |
| Email verification | Checks access to the address. A disposable or attacker-controlled address can still pass |
| Phone verification, plus a limit on reusing a number | Multi-accounting gets harder: each account needs a different verified number. A verified number doesn't identify a unique person |
| Rate limiting | Slows mass registration |
| [Device fingerprinting](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/) | Links repeat registrations |

### Email Verification Best Practices

| Level | Method | What It Does |
| --- | --- | --- |
| Basic | Send confirmation link | Checks the customer can reach that address ([Twilio's flow](https://www.twilio.com/docs/verify/api) is one) |
| Medium | Apply a disposable-domain rule | Rejects the domains it matches |
| Strong | Email risk scoring | Scores the address. A score doesn't prove fraud |

### Phone Verification

| Check | Why |
| --- | --- |
| SMS verification | Shows access to that number, not who holds it |
| VoIP detection | Flags virtual numbers. Some real customers use them |
| Phone line type | Mobile vs. landline vs. VoIP |
| Phone velocity | Same number, many accounts |

### Device Controls

Use the [device signals above](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#device-signals) here too. Each one is a reason to look closer, not proof.

## Account Linking

Here's what links accounts back together:

| Attribute | What It Links |
| --- | --- |
| Device fingerprint | Same device across accounts. Check shared households before calling it one person |
| IP address | Same network (less reliable) |
| Payment method | Same card across accounts |
| Shipping address | Same destination |
| Behavioral patterns | Similar navigation, timing |

## Response Playbook

### Confirmed Fake Account

1.  **Block the account**: Prevent further activity
2.  **Revoke benefits**: Cancel promos, referral rewards
3.  **Block the identifiers**: Device, email, phone, on your own block list
4.  **Check for linked accounts**: Find the network
5.  **Update rules**: Close the registration gap

### Mass Signup Attack

1.  **Enable rate limiting**: Slow the attack
2.  **Add friction**: CAPTCHA, phone verification
3.  **Review recent signups**: Find and remove fakes
4.  **Block infrastructure**: IPs, devices, email patterns

## Prevention Checklist

-   [ ]  CAPTCHA on registration
-   [ ]  Email verification required
-   [ ]  Disposable email domains reviewed. Some real customers use them
-   [ ]  Device fingerprinting enabled
-   [ ]  Rate limiting on signup endpoints
-   [ ]  Phone verification for high-value actions
-   [ ]  VoIP and virtual numbers flagged for review. Some real customers use them
-   [ ]  Account linking across devices
-   [ ]  Promo redemption limits per device

## Next Steps

**Preventing fake accounts?**

1.  [Add device fingerprinting](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/): Catch repeat registrations
2.  [Implement email verification](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#email-verification-best-practices): Check the address works
3.  [Set up rate limiting](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#at-registration): Slow mass signups

**Detecting fake accounts?**

1.  [Check registration signals](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#registration-red-flags): Score risk at signup
2.  [Analyze email patterns](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#email-analysis): Catch multi-accounting
3.  [Link accounts](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#account-linking): Find networks

**Responding to fake accounts?**

1.  [Follow response playbook](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#response-playbook): Block and revoke
2.  [Find linked accounts](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#account-linking): Catch the full network
3.  [Update prevention](https://paymentsandrisk.com/docs/fraud/types/application-fraud/#prevention-checklist): Close gaps

* * *

## Related Topics

-   [Prevent Fraud](https://paymentsandrisk.com/docs/fraud/): The fraud hub
-   [KYC & KYB for Fraud Prevention](https://paymentsandrisk.com/docs/fraud/prevention/kyc-kyb/): When and how to verify identity at onboarding
-   [Identity Verification](https://paymentsandrisk.com/docs/fraud/detection/identity-verification/): Passive and documentary verification methods
-   [Promo Abuse](https://paymentsandrisk.com/docs/fraud/types/promo-abuse/): What fake accounts enable
-   [Fraud Rings](https://paymentsandrisk.com/docs/fraud/types/bust-out/): Organized multi-accounting
-   [Device Fingerprinting](https://paymentsandrisk.com/docs/fraud/detection/device-fingerprinting/): Linking accounts by device
-   [Velocity Rules](https://paymentsandrisk.com/docs/fraud/detection/velocity-rules/): Detecting signup patterns
-   [Card Testing](https://paymentsandrisk.com/docs/fraud/types/card-testing/): Can use fake accounts
-   [Refund Fraud](https://paymentsandrisk.com/docs/fraud/types/refund-fraud/): Another fake account use case
-   [Account Takeover](https://paymentsandrisk.com/docs/fraud/types/account-takeover/): When real accounts are hijacked
-   [Risk Scoring](https://paymentsandrisk.com/docs/fraud/prevention/risk-scoring/): Scoring at registration
