Friendly Fraud Explained: When Real Buyers Dispute Real Orders

Friendly fraud is when the real cardholder makes a purchase and later disputes it with their card issuer. Stripe describes it as a legitimate cardholder making a purchase and then disputing it at a later date, and notes that it is also called first-party misuse or first-party fraud. The card was not stolen. The person who paid is the person who complains.

Sometimes it is deliberate. Often it is not. A buyer who does not recognize a charge on a statement, or someone in a finance team who sees an unfamiliar name, may file a dispute without ever contacting you. That is why most of the defense against friendly fraud is ordinary record keeping and clear communication, not special fraud tooling.

How friendly fraud differs from stolen-card fraud

Stripe defines a fraudulent payment as one the cardholder did not authorize, and says most are made with stolen cards or card numbers. In that case someone other than the cardholder used the card. With friendly fraud, the cardholder did authorize the payment and then contested it.

Stripe gives two broad reasons this happens:

• Accidental: the cardholder did not recognize the transaction on their statement.
• Deliberate: for example, buyer's remorse, or an attempt to get goods without paying for them.

The difference matters because your evidence is different. Stripe notes that fraud disputes are hard to win because in many cases the claim is correct, and that if you believe a payment really was fraud, the appropriate action is to accept the dispute or decline to challenge it. With friendly fraud the facts may be on your side, but only if your records show who ordered, what they agreed to and where the goods went.

How it shows up in your Stripe account

Stripe groups card network reason codes into a small set of categories. Friendly fraud usually arrives under one of these:

• Fraudulent: the cardholder says they did not authorize the payment. Stripe calls this the most common reason for a dispute.
• Unrecognized: the cardholder does not recognize the payment. Stripe says this is effectively indistinguishable from the fraudulent reason.
• Product not received, product unacceptable or credit not processed: the buyer says the order never arrived, was not as described, or should have been refunded.

The category alone does not tell you whether a dispute is friendly fraud. You find out by comparing the claim with your own records. For the wider process, see how disputes and chargebacks work.

Use a statement descriptor buyers recognize

Stripe lists a recognizable statement descriptor as a way to prevent both fraudulent and unrecognized disputes. It recommends a descriptor that customers easily recognize and that reflects the URL or business name they would associate with the purchase, such as your website domain or business name.

For a business-to-business supplier, think about who reads the statement. Often it is someone in accounts payable who never saw the order. A descriptor that matches the name on your website, invoices and receipts gives them something to match. Our page on statement descriptors covers the details.

Send receipts that make the charge easy to match

Stripe recommends sending receipts on payment so customers can remember what they paid for, and points out that a receipt gives the customer an easy way to reply and get in touch. A useful receipt for a business or research buyer shows:

• your business name, matching your statement descriptor
• the order number, date, amount and currency
• the products ordered, described exactly as they were on the product page
• the ship-to name and address
• how to contact you about the order

If the buyer's organization uses purchase order or invoice references, show those too. The easier it is to match a charge to an internal record, the less reason anyone has to open a dispute just to find out what a charge was.

Show your policies in full and record the agreement

Stripe recommends making your terms and policies easy to find and requiring customers to agree to them. It warns that issuers can be specific about how policies are presented: a checkbox that only contains a link might be rejected as evidence that the customer was aware of the policy. Stripe suggests showing the full policy on the checkout page, or in a pop-up the customer must accept before submitting the order.

On friendly fraud specifically, Stripe says clear return policies, prominently displayed at checkout and agreed to before purchase, can help. Keep a record of the exact policy text the buyer accepted on the date they ordered. Our guide to refund and return policies for B2B research suppliers covers what those policies usually contain.

Keep delivery proof with the order

For physical goods, Stripe says shipping to a verified billing address and requiring a signature on delivery can help combat friendly fraud. It also recommends carriers that provide online tracking and delivery confirmation. Keep the label, carrier, tracking number and delivery confirmation with the order. Stripe notes that card issuers do not follow links, so tracking evidence has to be submitted as screenshots or documents.

Records that answer a friendly fraud dispute

To counter a fraudulent or unrecognized dispute, Stripe says you need to show that the legitimate cardholder, or an authorized representative such as an employee, made the payment. The evidence it lists includes:

• evidence linking the person who received the products to the cardholder
• a shipping address that matches a billing address verified with AVS, or the address of a business connected to the cardholder
• shipping documentation that shows the full delivery address
• evidence of one or more earlier payments on the same card that were not disputed
• any communication in which the customer acknowledges the purchase

Stripe also supports Visa Compelling Evidence 3.0, which lets a business challenge friendly fraud by showing earlier non-fraud transactions with the same cardholder. Stripe says it identifies qualifying transactions in your Stripe history and pre-populates much of the response. It cannot do this for payments processed elsewhere, so Stripe recommends including the customer's IP address, email address, shipping address and product descriptions in your Stripe transactions. For a full list of what to keep per order, see payment records to keep.

Talk to the buyer before you respond

Stripe recommends contacting the customer when a dispute arrives where you can, and keeping a record of all communication, because it may help you understand the complaint and can be submitted as evidence. Many friendly fraud cases are a finance team that did not recognize a charge. A short, neutral message with the order details is often enough for them to recognize it.

If the buyer tells you they will withdraw the dispute, Stripe still recommends submitting evidence, so the issuer knows you are not accepting it. Keep every message factual and neutral, and do not pressure the buyer.

What these steps cannot do

None of this prevents every dispute. Stripe says it does not influence the outcome of a dispute, which is decided by the cardholder's bank. Stripe also notes that dispute activity is calculated on the disputes you receive, not on whether you win or lose them, so preventing confusion in the first place matters more than winning later.

Claddr records buyer checks, signed attestations, holds and payments against each order in a tamper-evident audit record that you can export for a date range. That keeps the order history in one place when you assemble a response. It does not decide the outcome of any dispute.