Visa 13.8 - Original Credit Transaction Not Accepted: What It Is and How to Respond

Niche code: Visa 13.8 applies to Original Credit Transactions (OCTs) - push payments used for payouts, prizes, and settlements. If you're a typical e-commerce merchant, you are unlikely to encounter this code. It is most relevant to platforms, marketplaces, and insurers that initiate Visa Direct or OCT disbursements.

Visa 13.8 applies to Original Credit Transactions (OCTs) - a Visa transaction type used to push funds to a cardholder's account without a corresponding purchase. Common uses include prize payouts, insurance settlements, marketplace seller payouts, and refunds issued outside the standard refund flow. This dispute arises when the cardholder's bank declined or failed to apply the OCT to their account.

The key question is whether the OCT was successfully sent and accepted by the network, or whether it was declined or failed to post at the issuer side. Network response codes at the time of submission are your primary evidence.

Common reasons you received this dispute

1Issuer declined the OCT because the account is not enabled to receive push credits
2The recipient's card is closed, expired, or the account has been restricted
3OCT amount exceeded the issuer's maximum receive limit for push transactions
4OCT was submitted to the wrong account number or an account belonging to a different cardholder
5Technical failure at the issuer prevented the credit from posting despite network acceptance

Can you win this dispute?

Fight this dispute if...

✓You can prove the OCT was successfully sent and accepted by the network - network acceptance is distinct from a declined OCT
✓Your clearing records confirm the OCT was accepted and the non-posting was an issuer-side failure after acceptance

Accept this chargeback if...

✗The OCT failed to reach the cardholder due to a declined or failed transaction on the network
✗Network response codes show the OCT was not accepted - the cardholder did not receive the funds

Evidence checklist

✅ Required
OCT transaction record showing submission and network response: The full record of the OCT including the network's response code - whether it was accepted, declined, or resulted in an error.
✅ Required
Clearing records showing whether the OCT was accepted or declined: The settlement record confirming the outcome of the OCT at the network clearing stage.
⭐ Strongly recommended
Payment gateway logs showing OCT status: The gateway-level record confirming what was submitted and what response was received.
⭐ Strongly recommended
Network response codes at time of submission: The specific response code from Visa's network at the time the OCT was submitted - this determines liability.

How to write your response

Your response must centre on the network response to the OCT. If the OCT was accepted by the network, demonstrate this clearly with response codes and clearing records. If it was declined, the focus should shift to whether the decline was due to an issuer-side account restriction beyond your control.

Reference the specific OCT reference number, the account to which it was directed, and the network's response. If the OCT was declined due to an account restriction on the recipient's side, note this clearly.

“We respond to chargeback [reference] under Visa 13.8. Exhibit A shows the OCT submission record for transaction [ID] directed to account [last four]. Exhibit B shows the network response code [code] confirming the OCT was [accepted/declined] at [date/time]. [If accepted:] The OCT was accepted by the network - we request reversal of this chargeback and ask the issuer to investigate the posting failure on their side.”

Key deadlines

Response window: 30 calendar days from the notification date.

Retain all OCT records including network response codes for a minimum of 18 months to cover the full dispute window.

How to prevent this chargeback

1
Verify recipient account eligibility before sending OCTs: Not all Visa accounts support push transactions. Before sending an OCT, verify the recipient's account can receive push credits - this capability check should be part of your disbursement onboarding flow.
2
Use Visa's account validation service before high-value OCTs: For significant disbursements, validate the account before initiating the OCT to confirm it is active and capable of receiving push credits.
3
For marketplace payouts: use Visa Direct or a purpose-built disbursement platform: Dedicated disbursement platforms handle OCT compliance automatically and provide the documentation trail needed to respond to 13.8 disputes.
4
Maintain records of all OCTs including network response codes: Every OCT should be logged with its submission timestamp, network response code, and whether it cleared. This record is your entire defence for 13.8 disputes.

Frequently asked questions

What is Visa 13.8?

A dispute arising from an Original Credit Transaction (OCT) - a push payment - that was not successfully received by the cardholder. The dispute arises when the cardholder's bank declined or failed to apply the OCT to their account.

What is an OCT?

An Original Credit Transaction is a Visa payment type used to push money directly to a cardholder's account - used for prize payouts, insurance settlements, marketplace seller payouts, and refunds issued outside the standard refund flow.

Who typically sends OCTs?

Typically platforms, marketplaces, and insurers - not typical e-commerce merchants. If you received a 13.8 dispute, you are likely operating a disbursement, payout, or settlement function.

How long do I have to respond to a Visa 13.8 chargeback?

30 calendar days from the chargeback notification date. Retrieve your OCT submission and network response records immediately - whether the OCT was accepted or declined by the network is the central question.