4855: Goods or Services Not Provided

If you’ve landed here because you’re dealing with a chargeback with this reason code, there’s something that matters to know initially: reason code 4855 has been retired. Mastercard consolidated it into reason code 4853, which is now the umbrella code for a wider number of fulfillment and service failures. The core issue - goods or services not provided - is still very much a valid dispute category, just filed under a different code.

I’ll cover what reason code 4855 was, how it worked, and what merchants and cardholders need to know now that it has been folded into 4853. Whether you’re trying to make sense of a dispute you’ve received or researching how these claims are evaluated, you’re in the right place.

What Chargeback Reason Code 4855 Actually Covered

Reason code 4855 sat within Mastercard’s Cardholder Disputes category - which already tells you quite a bit about its job. This was not about fraud in the traditional sense - it was about a transaction that processed correctly but where the cardholder never got what they paid for.

The core of every 4855 dispute was the same: a customer paid and nothing showed up. That could mean a physical product that never arrived in the mail, a service that was scheduled but never performed, or an online buy that was never delivered or made accessible.

Consider a contractor who takes a deposit and never starts the job, or an online retailer that charges a card on the day of purchase but never ships the package. These are the types of situations 4855 was built to help with - cases where there’s no question about whether the card was used legitimately, but every question about whether the merchant held up their end of the deal.

Digital goods and services were a real part of this too. A subscription that charges but never activates, or a software license that never gets delivered to the buyer’s inbox, would fall into this territory. The format of the purchase did not matter much - what mattered was that the cardholder paid for something and received nothing in return. Merchants dealing with these claims frequently should understand why digital goods businesses face elevated dispute scrutiny.

It’s worth mentioning that 4855 applied to completely undelivered transactions and situations where only part of what was purchased was delivered. If a merchant shipped two out of four items and charged for all four, the undelivered portion could still be disputed under this reason code. In cases like that, a partial refund before the dispute closes can complicate things further.

Merchants across almost every industry could find themselves on the receiving end of a 4855 dispute. Retail, travel, home services, and software were all common areas where these claims came up. The connecting thread was always a failure to deliver - not any unauthorized use or identity theft.

Because these disputes were rooted in what the merchant did or didn’t do after the transaction, they landed squarely in the Cardholder Disputes bucket instead of the fraud categories. That distinction matters because it shapes how the dispute gets handled and what evidence is relevant. Merchants who never respond to a dispute at all typically lose by default, regardless of what actually happened.

Why Mastercard Retired 4855 and Moved It Into 4853

Mastercard consolidated 4855 into reason code 4853 as part of a wider effort to smooth along its dispute framework. The two codes covered situations that were closely related and Mastercard decided one umbrella category made more sense than keeping them separate.

Code 4853 is titled “Cardholder Dispute” and it covers a variety of situations where a cardholder feels they didn’t get what they paid for. Folding 4855 into it means that non-delivery and non-performance disputes now sit alongside other merchandise and service complaints instead of having their own standalone code.

For cardholders, this change is mostly administrative. The dispute process itself works the same way - you still report that goods or services weren’t delivered and your bank still submits the chargeback on your behalf. The category label is different, but the underlying claim is the same.

Merchants do need to pay attention here though. Because 4853 is wider, a chargeback filed under it could relate to a few different problems - not just non-delivery. Merchants need to read dispute notices to know what the cardholder is claiming before putting together a response.

The evidence standards haven’t changed in any real way. Merchants defending against a non-delivery claim still need to show proof of shipment, delivery confirmation, or documentation that a service was completed. The consolidation didn’t lower the bar or raise it.

One helpful difference is in how disputes get categorized internally - by banks, payment processors and dispute management tools. If your system tracks chargebacks by reason code, you might see non-delivery cases grouped with a wider set of cardholder disputes instead of broken out on their own. That can make it slightly harder to analyze patterns in your chargeback data unless your processor gives you more granular detail.

The retirement of 4855 doesn’t create any new obligations for merchants or cardholders - it’s a structural change to how Mastercard organizes its rules instead of a change to the rules themselves. The substance of what qualifies as a valid dispute - and what a merchant needs to fight one - stayed the same.

Filing Deadlines and the Rules Cardholders Must Follow

Cardholders have 120 days to file a dispute when goods or services weren’t received. That window starts from the expected delivery date or from the date the cardholder realized the goods or services weren’t going to show up. Missing that dispute window means losing the right to dispute through the chargeback process, so it’s worth keeping track of dates from the second something goes wrong.

The 120-day rule exists because banks and card networks need a basic boundary for what they’ll investigate. If you don’t have it, disputes could come in years after a transaction and there’d be no way to fairly resolve them - it also gives cardholders enough time to follow up with the merchant before escalating to their bank.

There’s a separate rule that applies to low-cost online goods, and it works very differently. Any online goods purchased at or under $25 USD has to have been bought within 15 minutes of the cardholder entering their login credentials for a dispute to be valid under this reason code. That tight window is there to help with a pattern of unauthorized purchases made in quick succession after account access; fraudulent activity tends to happen fast.

Dispute Type	Time Window	Starting Point
General goods/services not received	120 days	Expected delivery date or date issue was realized
Digital goods at or under $25 USD	15 minutes	When cardholder entered login credentials

These two timeframes serve different purposes, which is why they look so different on paper. The 120-day window gives cardholders room to resolve a dispute after waiting on something that never arrived. The 15-minute rule is more targeted, and it’s about a type of transaction where speed is the whole point.

If a cardholder misses the 120-day window, their bank will probably reject the dispute before it even reaches the merchant. The deadline isn’t flexible, and banks don’t have discretion to waive it. Getting the dates right before filing is one of the most helpful things a cardholder can do to protect their case.

How the Fair Credit Billing Act Backs Up Cardholder Disputes

The reason cardholders can dispute a charge at all depends on a federal law passed in 1974: the Fair Credit Billing Act, or FCBA - it gives consumers the legal right to challenge charges they believe are unauthorized or incorrect. If you don’t have it, your only actual option would be to argue directly with the merchant and hope for the best.

The FCBA was designed to protect consumers from billing errors on credit accounts. A charge for goods or services that were never delivered fits squarely into that category. The law treats it as a billing dispute, which means your card issuer has a legal obligation to investigate instead of just taking the merchant’s word for it.

That distinction matters because it changes the dynamic entirely. The bank isn’t doing you a favor by accepting your dispute. They’re following a process that federal law puts in place - it’s a real distinction, and that’s also the case if a merchant pushes back or claims the charge was valid.

For merchants, the FCBA shapes how they have to work too - it creates accountability on both sides of a transaction. Merchants who collect payment without delivering what was promised aren’t just in breach of contract - they’re part of a dispute process backed up by consumer protection law.

The Federal Trade Commission enforces the FCBA and publishes guidance for consumers on how to use their rights. The FTC makes it clear that cardholders can dispute charges that don’t match what was agreed to - like situations where a product was never shipped or a service was never performed. That guidance lines up directly with what the 4855 reason code covers.

One helpful thing the FCBA does is place responsibility on card issuers to acknowledge a dispute within 30 days and resolve it within two billing cycles. That timeline gives cardholders a structured process to follow instead of an open-ended waiting game - it also means merchants are working within a defined window to respond and provide evidence.

The law doesn’t guarantee that every dispute will go in the cardholder’s favor, but it does guarantee that the dispute gets a fair look. That foundation is what makes the entire chargeback system work as an actual consumer protection tool instead of just a policy that card networks can change whenever they feel like it.

Keeping Disputes From Derailing You - On Either Side

A few helpful reminders worth keeping close:

• Watch your deadlines. Both cardholders and merchants operate within strict timeframes. Missing a response window can mean losing a dispute you would have otherwise won.
• Keep thorough records. Receipts, confirmation emails, delivery tracking, and communication logs are the foundation of any strong case on either side of a dispute.
• Know what the rules are actually protecting. These codes exist to ensure that consumers receive what they pay for - and to give merchants a fair process for challenging claims that are not valid.

Disputes can be frustrating in the moment, but the process is more structured and navigable than it may appear. With the right documentation, a clear sense of the timeline, and a calm strategy, cardholders and merchants are well equipped to see a fair resolution. You have more tools at your disposal than you might know - use them. For specific situations like a hotel or accommodation dispute or a car rental damage claim, starting with a tailored template can make the process significantly easier.