Friendly Fraud: Friendly fraud occurs when a valid card transaction is disputed without a legitimate basis. It can be intentional, such as seeking a refund while keeping the purchase, or unintentional, such as forgetting a transaction or failing to recognize a billing descriptor.
Multiple Triggers: The blog identifies intentional abuse, customer confusion, dissatisfaction, and family fraud as common drivers. Because these situations arise after an otherwise legitimate transaction, ordinary fraud screening may not prevent them.
True Fraud Differs: True fraud involves stolen payment credentials used without the cardholder’s authorization, while friendly fraud involves an invalid dispute of an authorized transaction. Merchants should distinguish the two because the appropriate response differs between fraud prevention, customer resolution, and representment.
Prevent Confusion: Recognizable billing descriptors, accessible customer service, clear purchase terms, reasonable refund processes, and controls around family or stored-payment use can reduce situations that lead customers to dispute legitimate purchases.
Build Representment Evidence: When an invalid dispute occurs, merchants should preserve records connecting the cardholder to the purchase and showing fulfillment. Relevant evidence can include IP and device information, shipping records, AVS and CVV results, 3-D Secure authentication, account activity, delivery records, and customer communications.
Friendly fraud occurs when a cardholder disputes a legitimate purchase without a valid reason for reversing the payment. It can begin with an honest mistake, such as failing to recognize a charge, or a deliberate attempt to keep goods or services without paying. It can also be called first-party misuse or chargeback fraud.
Consider a customer who buys a jacket, receives it, and later tells the bank it never arrived. The merchant has already paid for the item and delivery. A chargeback then removes the sale proceeds and can add a dispute fee.
Other cases are less clear. A forgotten renewal or an unfamiliar business name can turn a satisfied customer into someone reporting suspected fraud. Merchants need a way to identify what happened, resolve confusion, and challenge claims their records contradict.
A chargeback is a payment reversal initiated through the cardholder's issuer. Friendly fraud describes the misuse behind some chargebacks. A dispute can also result from stolen credentials, a billing mistake, or a valid complaint about a purchase.
| Category | What happened | Merchant response |
|---|---|---|
| Friendly fraud | An authorized purchase is disputed on grounds that the transaction records do not support. | Investigate the claim and submit relevant evidence when a valid defense exists. |
| True fraud | Someone uses payment credentials without proper authorization. | Review fraud controls and any applicable liability protection. |
| Merchant error | The merchant processes a duplicate payment, delivers damaged goods, or otherwise fails to uphold their end of the deal. | Correct the underlying issue to avoid future valid disputes. Ensure customers with legitimate issues can contact customer support. |
The cardholder's allegation and the underlying cause can differ. A dispute labeled unauthorized might involve a forgotten purchase, stolen credentials, or activity by another household member.
A customer orders from a familiar store but sees the parent company's name on the card statement. Unable to connect the charge with the purchase, the customer reports it as unauthorized.
Merchants should ensure their billing descriptor is something customers will recognize and includes a customer support phone number to help avoid these disputes.
A customer agrees to an annual software subscription, forgets the renewal date, and disputes the next payment.
Records of the subscription agreement and billing notices can help establish what was authorized. The cancellation history also needs review. If a merchant continued billing after an effective cancellation, the customer may have a valid dispute. Treating every subscription complaint as friendly fraud can conceal a billing problem.
A family member uses a saved card to buy a game or digital content. The cardholder sees the charge and reports fraud without recognizing who made the purchase.
These cases often fall into a gray area. Prior permission, account access, and the circumstances of the purchase affect the analysis. A shared address or device does not automatically settle whether use was authorized.
A customer receives an order and falsely reports non-delivery, or uses a service and later denies purchasing it. Another customer may seek a chargeback to bypass a return deadline despite having no valid dispute grounds.
Merchants need to examine the chargeback reason code and collect evidence that effectively disproves it. proof of delivery, AVS and CVV matching, and customer communication records can all be valuable evidence in these cases.
The financial impact can include the reversed payment, merchandise or service costs, shipping, dispute fees, and staff time. Even reversing the chargeback will leave some of those expenses unrecovered.
Frequent disputes can also affect a merchant's relationship with its processor or acquiring bank. Elevated dispute activity can lead to additional fees, restrictions, or account reviews. It can also result in enrollment in card network monitoring programs like Visa's VAMP, which carry their own financial consequences.
Start with the reason given for the dispute and the transaction records. Check whether the customer contacted support or received a refund.
Records that contradict a claim deserve closer review. A customer may report non-delivery after emailing about the fit of an item. A customer denying a software purchase may have used the account throughout the paid period. Repeated disputes connected to the same account may also warrant investigation.
These are leads, not conclusive findings. An account can be taken over, a delivery can reach the wrong address, and a customer can have several legitimate complaints. Keep unresolved cases separate from confirmed operational errors and well-supported cases of first-party misuse.
Use a billing descriptor customers can connect with the storefront or service. Check how it actually appears on statements, including any processor prefix or shortened wording.
Receipts should connect the business name, order details, and payment amount. Explain split charges and provide updates when shipping or billing is delayed.
Show renewal terms, cancellation options, delivery expectations, and refund conditions where customers make decisions. Subscription reminders should identify the service, upcoming amount, billing date, and cancellation route.
Support teams need access to order, payment, and refund status. A customer asking where a refund went should receive a specific answer. Preserve the request and resolution so the dispute team can reconstruct events later.
Encourage customers to contact the business with questions and make that process as easy as possible. A report by Mastercard and Javelin Strategy & Research found that only 25% of customers contact the merchant before filing a dispute. The more a merchant can increase that number, the more chargebacks they can avoid.
Connect transaction IDs with order records, delivery confirmation, customer communications, and the terms presented at purchase. Digital businesses should retain relevant account activity and records of service use. A dispute team needs to locate these records before its response deadline.
Fraud detection tools can provide supporting information. AVS checks billing address details, while CVV checks the security code on the customer's card. A match does not fully establish who completed the purchase, as someone using a stolen card can enter the correct code. However, it serves as one important piece of evidence toward identifying the customer.
Retain verification results where appropriate, but never retain the CVV itself after authorization. PCI DSS prohibits merchants from storing that code after authorization, including for recurring purchases.
Order Insight and Ethoca Consumer Clarity make purchase information available through participating issuer channels. Depending on the service and integration, cardholders or bank staff can see details that help identify a transaction before it becomes a chargeback.
This can resolve a recognition problem while preserving the sale. Its effectiveness depends on issuer participation and the quality of the information the merchant supplies.
Chargeback prevention alerts give participating merchants an opportunity to resolve reported issues before they become chargebacks by issuing a refund. Similarly, Rapid Dispute Resolution, or RDR, applies merchant-defined rules to automatically resolve eligible Visa pre-disputes by returning funds.
Refund-based prevention gives up the payment to avoid further dispute costs. Review the transaction value, fulfillment status, fees, and account exposure when setting rules. Measure the revenue refunded alongside the chargebacks prevented, and check for previous credits before issuing another refund.
Merchants can challenge an invalid chargeback by submitting evidence through their processor or acquirer. This process is called representment.
Begin with the reason code, the issuer's claim details, and the deadline shown in the dispute notice. A merchant's submission deadline can be earlier than the network deadline because the processor needs time to handle the response.
Build the response around the disputed facts. Showing that a customer bought an item does not answer an allegation that it arrived damaged. A delivery record may address non-receipt but leave questions about authorization unresolved.
| Cardholder's claim | Potentially useful evidence | What to establish |
|---|---|---|
| The purchase was unauthorized | Relevant authentication results, account activity, device data, prior transaction history, and customer communications | A supported connection between the purchase and an authorized user, or an applicable liability protection |
| The merchandise never arrived | Delivery records with the full address, signatures where available, and messages acknowledging receipt | Delivery of the disputed order as agreed |
| A digital service was not provided | Activation, access, download, or usage records tied to the relevant account and paid period | Provision and use of the specific service |
| A subscription was canceled | Accepted subscription terms, cancellation requests, confirmations, and billing timestamps | Whether the disputed payment occurred before or after an effective cancellation |
| A promised refund was not received | Refund date, amount, payment reference, and processor records | Whether the credit was issued and how it relates to the disputed payment |
Each network and reason code has its own requirements. The table is a starting point for assembling records; the applicable dispute category determines what the response needs to establish.
Keep the explanation short, factual, and chronological. Include readable copies of relevant records in the required format. Do not depend on a reviewer following external links or searching a long set of terms for the relevant clause.
Visa Compelling Evidence 3.0 provides a defined evidence route for eligible Visa card-absent fraud (reason code 10.4) disputes. Its standard purchase-history criteria use two qualifying prior transactions from the same merchant, generally 120–365 days old at the dispute date, that meet Visa's fraud-history conditions.
At least two data elements must match across the purchases: user ID, IP address, shipping address, or device ID/fingerprint. One match must be the IP address or device ID/fingerprint. Qualifying data can support prevention through Order Insight or a response after a dispute.
If a merchant chooses to use 3-D secure, some fraud disputes may qualify for liability protection. Check the recorded authentication outcome and applicable rules before accepting liability.
Friendly fraud can turn a completed sale into a loss long after a merchant has delivered on its promise. That uncertainty is part of accepting card payments, but an issuer’s initial decision to reverse a payment does not always settle whether the customer’s claim is valid.
Merchants deserve an opportunity to have their side of the transaction considered. When the records support a challenge, pursuing it can protect revenue the business has earned. The goal is a fair outcome: customers retain protection against genuine problems, and merchants have a way to defend legitimate sales against mistaken or dishonest claims.
No. A customer may forget a purchase or fail to recognize the merchant's name. Other cases involve deliberate false claims. The merchant needs to investigate the transaction before deciding how to respond.
No. Unauthorized payments, duplicate charges, undelivered orders, and other qualifying problems can support legitimate disputes. An authorized purchase can still have a valid service or billing complaint attached to it.
Yes, when the case permits a response and the evidence supports a valid defense under the applicable rules. The submission should address the specific claim and meet the processor's deadline. A complete receipt alone does not guarantee recovery.
Screening can identify suspicious purchases and known patterns of abuse, but a legitimate customer's future dispute may be impossible to predict at checkout. Clear communication, retrievable records, and appropriate dispute tools address different parts of the problem.