National merchant dispute guidance
What Is First-Party Misuse?
First-party misuse occurs when a cardholder disputes a genuine transaction that the cardholder, or someone authorized to use the account, actually made. The dispute may result from confusion, a forgotten purchase, household use, or an intentional attempt to avoid paying.
The short answer
A genuine purchase can still be disputed
First-party misuse is different from classic third-party fraud. In third-party fraud, an outside person uses stolen payment credentials. In first-party misuse, the disputed transaction is connected to the legitimate cardholder or an authorized user, although the cardholder may not recognize or remember it.
Common scenarios
Why first-party misuse happens
Statement confusion
The billing descriptor may look unfamiliar or differ from the storefront name, so the cardholder does not connect the statement entry to the purchase.
Forgotten purchase
A delayed shipment, recurring subscription, advance reservation, or older order can be disputed after the customer forgets the transaction.
Household use
A family member or other authorized person may use a stored credential, while the primary cardholder does not recognize the order.
Intentional misuse
A customer may dispute a valid purchase after receiving or using the goods or services, sometimes seeking a refund outside the merchant's normal process.
Investigation
How merchants can review a disputed transaction
Start with the case notice
Confirm the case type, reason, transaction, deadline, and submission rules in the merchant's approved processor, acquirer, or payment-provider portal.
Reconstruct the order
Match the payment to the order number, customer account, item or service, amount, transaction date, fulfillment event, communications, and any refund or cancellation activity.
Look for recognition context
Check whether the descriptor, receipt, confirmation message, subscription reminder, or support history could explain why the cardholder did not recognize the charge.
Separate evidence from assumptions
Document what the records show without labeling the cardholder's motive. A merchant generally cannot determine intent from the dispute notice alone.
Use the approved response channel
Submit a concise answer with legible, relevant records. Keep the case number, submitted files, timestamp, and provider confirmation for reconciliation.
Useful records
Build a clear transaction timeline
Order identity
Order numbers, item or service descriptions, dates, amounts, and customer-facing receipts help connect the payment to a specific purchase.
Account and device context
Provider-permitted account, login, device, or authentication data may help establish continuity with prior customer activity.
Fulfillment
Delivery, pickup, appointment, access, or service-completion records can show what happened after authorization.
Customer communication
Confirmation notices, subscription reminders, support exchanges, cancellation requests, and refund records help explain the sequence of events.
Prevention
Reduce avoidable transaction confusion
Use a recognizable descriptor
Choose an approved descriptor customers can connect to the business and reinforce that name on receipts and order confirmations.
Send timely confirmations
Provide clear purchase, delivery, renewal, cancellation, and refund notices so customers can identify what happened and when.
Make support easy to find
Give customers a practical way to ask about an unfamiliar charge or resolve a service issue before escalating it to an issuer.
Keep connected records
Use stable identifiers across payment, order, fulfillment, subscription, support, and refund systems so staff can build a reliable timeline.
Common questions
First-party misuse FAQ
Is first-party misuse always intentional?
No. Official Visa and Mastercard materials describe both mistaken and intentional disputes of genuine transactions.
Is friendly fraud the same term?
The terms are often used together, but terminology can vary by network, provider, and workflow. Follow the wording in the live case.
Can a merchant prevent every case?
No. Clear descriptors, communications, support, and records can reduce confusion and improve response readiness, but they do not guarantee a particular outcome.
What should a merchant submit?
Submit only relevant evidence allowed by the provider that directly addresses the dispute reason and connects the cardholder to the genuine transaction.
Last editorial review: August 11, 2026. Sources reviewed: current official Mastercard and Visa guidance on first-party misuse and friendly fraud. Network and provider processes can change.
Next step
Make genuine purchases easier to recognize
Review descriptors, customer messages, support paths, and recordkeeping together so staff can prevent confusion and investigate disputes consistently.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US