13.8: Original Credit Transaction Not Accepted

This section walks through the mechanics of when an OCT is not accepted - like how the transaction flows back through the network, what response codes to look for, and how parties involved should manage the situation from an operational and regulatory standpoint.

What an Original Credit Transaction Actually Does

An Original Credit Transaction, or OCT, is a fund move that pushes money directly into a cardholder’s payment card account in real time - it runs on the Visa and Mastercard networks, but it works differently from a standard purchase reversal or refund. Instead of unwinding an existing transaction, an OCT is its own standalone move.

That distinction matters more than it might feel. A normal refund is tied to an original sale - it traces back through the same transaction record and credits the account from there. An OCT doesn’t need a prior purchase to reference - it moves funds outward from a business to a cardholder without any sale attached to it.

This makes OCTs helpful in situations where a traditional refund path doesn’t exist. Insurance businesses use them to pay out claims. Gaming and lottery platforms use them to send winnings. Gig economy platforms use them to pay drivers, couriers, or freelancers faster and directly to a card. Marketplaces and peer-to-peer services also use them to move money between parties without delay.

The appeal for businesses is simple. Moving money through the card network is faster and trackable than issuing a check or initiating a bank transfer. The recipient gets funds on a card they already use, and the business gets a confirmed delivery path through the network.

From the cardholder’s perspective, an OCT shows up as a credit on the account - funds in, not funds out. There’s no purchase, no receipt, and no merchant charge to match it to. That lack of context is actually where the uncertainty around code 13.8 starts, and the next section gets into that in more detail.

The core takeaway is that an OCT is a legitimate, purpose-built payment tool designed to fill gaps that standard transaction types couldn’t manage on their own.

When Cardholders Dispute an OCT Under Code 13.8

A 13.8 chargeback gets filed when a cardholder tells their bank that something went wrong on the receiving end of a credit push. There are a few scenarios that qualify, and it helps to know what they are.

The most common trigger is a cardholder saying the funds never showed up in their account. Another is a claim that the credit went to the wrong account. The third is a dispute over authorization - the cardholder says they never approved the transaction.

The issuing bank has as high as 120 days from the OCT processing date to file the dispute. That window matters because it means a chargeback can arrive long after the transaction looked like it completed successfully on your end.

The consumer protection foundation behind this is the Fair Credit Billing Act of 1974. That law gives cardholders the right to dispute transactions they didn’t authorize or that weren’t handled correctly, and it puts actual weight behind their claims when they go to their bank.

These disputes can happen even when you did nothing wrong. If your payment processor sent the funds to a non-matching account number, or if the receiving bank had a delay that the cardholder interpreted as non-receipt, the chargeback still lands in your lap. The cardholder’s experience is what drives the dispute - not necessarily the technical outcome of the transaction.

Issuers don’t always dig into the backend facts before filing. They hear from their cardholder that funds didn’t arrive and they act on that. By the time anyone looks at the processing records, the dispute is already in motion and the clock is already running on your response window.

Knowing why these disputes get filed - even in good-faith situations - is the foundation for learning about what happens if you don’t respond to them.

What Happens to Merchants When a 13.8 Dispute Lands

When a 13.8 dispute hits, the clock starts instantly. Merchants have 30 days to respond with a rebuttal and supporting evidence. Miss that window and the chargeback is automatically decided in the cardholder’s favor.

The financial hit is simple. The disputed amount gets pulled from the merchant’s account and a chargeback fee gets added on top. That fee changes by acquirer but usually sits between $20 and $100 per case.

Timeline Event	Who It Applies To	Time Allowed
Cardholder files dispute with issuer	Cardholder / Issuing Bank	120 days from transaction date
Issuer submits chargeback to acquirer	Issuing Bank	Within the dispute filing window
Merchant responds to chargeback	Merchant	30 days from chargeback notice

Here is where things get complicated for merchants with volume. Every dispute that gets filed counts toward a merchant’s dispute ratio regardless of how valid the underlying claim is. A well-documented, completely legitimate 13.8 case can still add to that number.

Visa monitors dispute ratios across all merchants. If a merchant crosses the threshold into Visa’s dispute watching programs, the consequences go well past individual chargebacks - it can mean higher processing fees, increased scrutiny from the acquirer, and in the worst cases, loss of card acceptance privileges.

A dispute that could have been won through a rebuttal can become a loss by default when ignored or met with a weak response, and that loss still counts. The ratio climbs either way, so the only move is to treat each case as worth fighting. Merchants who find themselves flagged as an excessive chargeback merchant face consequences that extend far beyond any single transaction.

How to Fight Back with a Strong Rebuttal

When a 13.8 chargeback lands, the window to respond is short and the bar for evidence is high. A weak or incomplete rebuttal usually loses - even when the merchant did everything right on their end.

The foundation of any good rebuttal is proof that the OCT was processed correctly and on time. Transaction records showing the original credit push, timestamps from your payment processor, and any confirmation from the card network are the core pieces. If you don’t have these, you’re asking the issuer to take your word for it.

Cardholder communication logs matter more than most merchants expect. If you told the customer a credit was on the way, keep a record of that. Emails, chat transcripts, or SMS threads can support your case by showing the cardholder was kept informed. A dispute that contradicts what actually happened on your side is much easier to fight with that documentation in hand.

Documentation at the time of the transaction is what makes or breaks a rebuttal later. Records created after the fact carry far less weight than logs generated in real time by your system. Capture everything at the point of processing - not when a dispute arrives.

The most common reason merchants lose winnable disputes is gaps in the paper trail. A transaction may have processed correctly, but if the supporting records are scattered, delayed, or incomplete, the issuer has no clean way to verify that. Disputes get decided on what you can prove - not what happened to be true.

Evidence Type	Why It Helps
OCT transaction record	Shows the credit push was initiated and processed
Processor timestamps	Confirms timing relative to the dispute window
Cardholder communication	Demonstrates the customer was informed of the credit
Network confirmation data	Verifies the transaction reached the card network

Put your rebuttal together as a chronological story. Issuers review many cases, and a well-organized submission is easier to rule in your favor than a disorganized packet of attachments.

Reducing OCT Disputes Before They Happen

Most 13.8 disputes don’t have bad intentions - they stem from a gap in communication. A cardholder doesn’t find a credit, assumes something went wrong, and files a dispute. That whole chain of events is preventable.

The most common oversight happens right at the start of the transaction. Sending an OCT to the wrong account number, a slightly outdated card, or an unverified recipient creates uncertainty that’s hard to walk back later. Confirming account details before sending a credit is one of the simplest ways to stop a dispute before it starts.

Sending a payment confirmation to the cardholder matters just as much. When someone receives a credit without any notice, they have no context for what it is or where it came from. A quick confirmation message - even a basic email - gives them that context and cuts back on the chance they’ll flag it as unfamiliar.

Clean transaction records are your safety net if a dispute does come through. Keep a log that ties each OCT to the original reason for the credit, the recipient’s verified account details, and the date it was processed. That documentation makes a rebuttal much easier to put together.

It also helps to look at your own process and find where a miscommunication could slip in. Think about who sends the credit, who notifies the cardholder, and whether those two things actually happen together every time.

A few helpful habits to build into your OCT process:

• Verify recipient account details before processing the credit
• Send a confirmation to the cardholder with the credit amount and reason
• Store a record of every OCT with the supporting context attached
• Use consistent and recognizable descriptor names so the credit is easy to identify

Small process improvements at the front end of a transaction do more to protect you than any amount of dispute management after the fact.

Keep Your OCTs Clean and Your Disputes Low

If there’s one thing worth holding onto from everything covered here, it’s this: documentation and communication are your two biggest levers. A well-timed, well-worded notification paired with a good paper trail can be the difference between a reversal and a write-off. These aren’t tough fixes - they’re habits, and habits get easier the more you build them into your workflow.

Take a few minutes to look at how your team is currently handling Original Credit Transactions from end to end. Are notifications going out promptly? Are records stored in a way that’s retrievable when a dispute comes in? Small gaps in the process tend to compound over time. Tightening things up now means fewer problems later - and a much stronger position if you ever need to fight one of these disputes. If recurring credits are part of your model, it’s also worth reviewing how credit card recurring billing intersects with your OCT workflows to stay ahead of any additional dispute triggers.