First-Party Fraud

What first-party fraud is

First-party fraud is deception by the person whose identity or account is involved. The person uses their own details or access to obtain a financial benefit from a business or financial institution. That makes it different from third-party fraud, where someone uses another person's identity or payment information.

For a merchant, a familiar example is a customer making a genuine card purchase and later claiming it was unauthorized. The customer can dispute the charge with their bank, which can start a chargeback. A disputed charge alone does not prove fraud or intent.

First-party fraud reaches beyond chargebacks, so your controls need to cover applications and account activity too.

More than a disputed card purchase

First-party fraud also covers deception involving credit and customer accounts. A loan applicant who exaggerates income or invents employment history is committing application fraud. A borrower who builds a payment record, obtains a larger credit limit, spends it and stops paying is using a bust-out scheme.

Other examples include false refund or insurance claims, misuse of a return policy and account takeover involving the account holder's access. Friendly Fraud is the card-dispute form of this broader category: it involves a person disputing a legitimate transaction, whether through confusion or deliberate abuse.

What it costs your business

A false card dispute can take away the sale revenue and the goods or services you already provided. You also spend staff time gathering records and responding, and a chargeback fee can add to the loss. Repeated disputes can raise your chargeback ratio and increase your exposure to network monitoring.

Visa and Mastercard rules generally give cardholders 120 calendar days from the transaction or expected delivery date to dispute a charge, with outer limits up to 540 days for some delayed-delivery cases, as of 2026. Your response window is set by your processor and is often 20 to 30 days, so late evidence can leave a valid sale unrecovered.

For a loan or account-based business, false application details can lead to unpaid balances, collection work and losses after credit is extended. A clear billing descriptor helps with card disputes by making it easier for customers to recognize a legitimate charge.

What you can actually change

You cannot prevent every customer from misrepresenting a purchase or application. You can make legitimate activity easier to verify and make policies harder to exploit.

• Use a recognizable billing descriptor and send order, renewal and delivery confirmations.
• Keep dated records of applications, account logins, delivery, service use, refunds and customer communications.
• Use identity checks and multi-factor authentication where the transaction or account risk warrants them.
• Make refund and cancellation terms easy to find, then review disputes and policy abuse for repeat patterns.

1. 01
   Review your descriptor. Compare the name customers see on card statements with your business name, receipts and order confirmations.
2. 02
   Save usable evidence. Keep delivery, login, usage and customer-contact records organized so staff can respond within the dispute deadline.
3. 03
   Tighten account checks. Match identity checks and monitoring to the risks in your sales, lending or account-opening process.

Frequently asked questions