Third-Party Fraud
- Third-party fraud is somebody who was never given access using the card or identity. It was taken, not handed over: stolen data, a breached account, a hijacked login
- If the owner handed it over, however they were persuaded, that's second party instead. Definitions vary across the industry: why they don't match
- The cardholder is the victim. They didn't authorize anything
- Different from first-party fraud, which includes friendly fraud (the cardholder knowingly disputing a charge they made, without a valid reason)
- Detect via device signals, address mismatches and bursts of repeated attempts (velocity)
- Prevent with 3D Secure (the card's bank checks the shopper), AVS/CVV (billing address and security code checks) and device fingerprinting (recognizing the phone or computer). Eligible 3DS can give you liability shift. Without it, check the dispute's other defenses and your contract
Think an order was placed with a stolen card? Don't ship it yet. Check it against the signals below, and if it doesn't clear, cancel and refund.
Third-party fraud occurs when somebody who was never given access uses a card or identity. It was taken, not handed over. Stolen card data, a breached account, a hijacked login.
If the cardholder handed their details over, even after being deceived, that's second-party fraud instead. The difference is whether a handover happened at all.
Without an eligible 3D Secure sale, expect to carry the loss when the cardholder disputes, unless another defense in the dispute's rules applies (Visa rules, 24 October 2026, Tables 11-29 and 11-32, pp. 706-716). The card was stolen, the cardholder is innocent, and you shipped goods to a fraudster.
How Stolen Cards Reach You
Where Fraudsters Get Card Data
| Source | What's Stolen |
|---|---|
| Data breaches | Card numbers, CVVs, billing addresses |
| Phishing | Full card details, passwords. If the cardholder typed them in themselves, this site calls it second party. The dispute you get looks the same |
| Skimming | Mag stripe data (card-present) |
| Account takeover | Saved cards in compromised accounts |
| Card testing | Validated stolen cards |
| Dark web markets | Bulk card data for sale |
Why Your Business Is Targeted
| Factor | Why Fraudsters Like It |
|---|---|
| Digital goods | Instant delivery, no shipping address |
| High-value items | Electronics, jewelry, gift cards |
| Easy resale | Popular brands, liquid markets |
| Weak fraud controls | No 3DS, no velocity limits |
| Fast shipping | Less time for detection |
Detection Signals
High-Risk Indicators
Use these in your risk scoring. The priorities are illustrative, so look for a legitimate cause before you decide:
| Signal | Priority to Check | What It Could Be |
|---|---|---|
| Shipping ≠ billing address | Next | A fraudster's address. Or a gift |
| AVS mismatch | Next | Wrong billing address. Or a move or a typo |
| CVV mismatch | First | The code doesn't match. That doesn't tell you where the card is |
| New account + high-value order | First | Possibly created for fraud. Or a new customer |
| Device seen on prior fraud | First | A link to earlier fraud. Devices get shared |
| IP location ≠ billing country | Next | A mismatch. Travel and VPNs do this |
| Multiple cards same device | First | Possibly cycling stolen cards. Or a family's device |
| Rush shipping selected | Next | Possibly wants goods before detection. Or a real deadline |
Velocity Red Flags
| Pattern | What It Could Mean |
|---|---|
| Multiple orders, different cards, same address | Possibly a drop address. Or a household |
| Multiple orders, same card, different addresses | Possibly testing before a big purchase. Or gifts |
| Multiple failed transactions, then success | Possibly card testing |
| High-value order from new account | Possibly new account fraud. Or a new customer |
Prevention Strategies
1. Use 3D Secure
Start here. On eligible fully authenticated sales, 3D Secure shifts fraud liability to the issuer.
| Without 3DS | With an eligible 3DS sale |
|---|---|
| You can carry the fraud loss, unless another defense applies | Issuer covers the fraud loss |
| A harder response. Track your own win rate | Send the authentication record and the loss moves |
| A stolen number can get past weak checks | The card's bank checks the shopper too, sometimes without asking them anything |
Track your own win rate by reason code.
See 3DS implementation guide for setup.
2. Verify Address and CVV
| Check | What to Do |
|---|---|
| AVS | When the customer's in the online checkout, check street number and ZIP where supported. Treat a mismatch differently from an unavailable result (Stripe's verification checks) |
| CVV | Collect it when the customer's in the checkout, and decide what a mismatch does. Later merchant-initiated charges follow your stored-credential rules, with no fresh code |
| Shipping address | Flag if different from billing |
3. Device Intelligence
Device fingerprinting (what it reads) can link devices. The rest depends on your provider's fields (Fingerprint's list is one):
- Devices linked to prior fraud
- VPN/proxy usage, if your provider reports it
- How long that provider has seen the device, which isn't the hardware's age
- Multiple accounts same device. Check for a shared device
4. Velocity Controls
Set velocity limits (how to tune them) on:
- Orders per hour/day from same device
- Cards used per account
- Failed authorization attempts
- Orders to same shipping address
High-Risk Scenarios
Shipping to Drop Addresses
Fraudsters use:
- Rented mailboxes
- Vacant homes
- Package forwarding services
- "Reshipping mule" addresses (recruited victims)
Detection: Address was never associated with the cardholder. That's a lead, not proof. People ship to work, to gifts and to other addresses.
Digital Goods Fraud
Higher risk because:
- Instant delivery (no time to detect)
- No shipping address to verify
- No tracking or signature
- Easy resale (gift cards, game codes)
Prevention: Send more digital-goods orders through 3DS, for example by triggering it at a lower order value.
Gift Card Fraud
Gift cards are "as good as cash":
- Can be resold instantly
- Value can be moved or spent fast, and getting it back can be hard. Keep the card and receipt and contact the issuer right away (FTC guidance)
- A target for card testing too
Prevention: Limit quantities, require 3DS, delay delivery.
Responding to Third-Party Fraud
When You Catch It Before Shipping
- Cancel the order: Don't ship
- Refund if captured: Avoid a chargeback. If one's already open, handle it inside the case
- Block the device and email: Prevent retry
- Contact with care: Use a verified contact you already had, not the order's, because the real cardholder may be someone else
When Cardholder Disputes
Check the actual claim, any credit already given and the eligible defenses first (Stripe's response guide):
| Situation | What to Do |
|---|---|
| Goods not yet shipped | Accept, unless the claim or a credit already given says otherwise |
| Digital goods delivered | Respond if you can tie the access to the cardholder or an authorized user. Track your win rate |
| Physical goods delivered | Respond if the evidence fits an allowed route. Tracking and a signature don't show the cardholder authorized it |
| Eligible 3DS sale | Liability shift: the issuer covers the fraud loss |
With true third-party fraud, the cardholder really IS innocent. Fighting is a long shot without 3DS liability shift or qualifying CE 3.0 history. Focus your energy on prevention.
Fighting Third-Party Chargebacks
If you must fight (and you have evidence):
| Evidence | What It Can Show |
|---|---|
| Eligible 3DS authentication | The fraud loss sits with the issuer |
| CE 3.0 history | Qualifying earlier purchase history. Ask your processor: "Does this Visa fraud dispute qualify for CE 3.0, and which earlier purchases match?" |
| Signed delivery confirmation | Someone at that address received it, not that the cardholder authorized it |
| IP + device consistency | A possible link to earlier activity. Tie it to the cardholder or an authorized user |
Without 3DS, these disputes are hard to win. Track your own win rate by reason code.
See Compelling Evidence for details.
Prevention Checklist
- 3D Secure on eligible transactions (all, or risk-based)
- AVS checked where supported
- CVV collected where supported, with a decision on mismatches
- Device fingerprinting active
- Velocity limits configured
- High-risk products (gift cards, electronics) have extra scrutiny
- Digital goods have higher friction
- Address verification flags ship ≠ bill
Next Steps
Preventing third-party fraud?
- Implement 3DS: Liability shift on eligible sales
- Add device fingerprinting: Track fraudster devices
- Configure velocity rules: Catch patterns
Detecting third-party fraud?
- Review AVS/CVV settings: Baseline protection
- Check risk scoring: Combine signals
- Review the warning signs: What to flag for review
Fighting third-party chargebacks?
- Check 3DS liability: Were you protected?
- Review CE 3.0 evidence: What can you prove?
- Accept if true fraud: Focus on prevention
Related Topics
- Prevent Fraud: The fraud hub
- 3D Secure: Liability shift for eligible card-not-present fraud
- AVS & CVV: Address and card verification
- Device Fingerprinting: Tracking fraudster devices
- Velocity Rules: Pattern-based detection
- Card Testing: How stolen cards are validated
- Account Takeover: Compromised customer accounts
- Compelling Evidence: Fighting fraud chargebacks
- Risk Scoring: Combining fraud signals
- First-Party Fraud: Customer-initiated fraud (different problem)
- Friendly Fraud: Real purchases, knowingly disputed without a valid reason