What Visa Reason Code 13.8 Means
Visa reason code 13.8 falls under the Consumer Disputes category and is titled Original Credit Transaction Not Accepted. It is filed when a cardholder disputes an Original Credit Transaction (OCT) — a push payment where funds are sent directly to the cardholder's Visa account without being tied to a prior purchase. The cardholder asserts they did not agree to receive this payment or did not request it, and the issuer reverses the credit through the chargeback process.
OCTs are used by gaming and gambling platforms for prize payouts, peer-to-peer payment services, gig economy platforms paying contractors, insurance companies making settlements, and merchants who issue refunds via push payment rather than standard credit reversal.
Code 13.8 is increasingly relevant as Visa Direct and similar push payment rails grow. If your platform uses OCTs for payouts, you need documented cardholder consent to receive funds at the card-level — not just account-level consent. A cardholder who signed up for your platform did not necessarily consent to OCT receipt on every card they later add.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Visa | 13.8 | Original Credit Transaction Not Accepted | This page |
| Mastercard | 4853 | Cardholder Dispute | MC catch-all; unsolicited push payment disputes fall here |
Common Trigger Scenarios
- Gaming or gambling payout to unrecognized account. A player requests a payout but the platform sends it to a card the player does not recognize or has not designated for payouts, triggering a dispute on the receiving card.
- Marketplace seller payout disputes. Gig economy platforms or marketplaces that pay contractors via OCT may face disputes when the receiving card is closed, changed, or when the contractor disputes the amount.
- Unsolicited credit transfer. A platform sends funds to a card account as part of a promotional offer, referral bonus, or goodwill credit — but the cardholder did not request or acknowledge the payment.
- Insurance or settlement payment disputes. A cardholder or policyholder disputes an OCT settlement payment, claiming they did not agree to receive the payment on their card or the amount is incorrect.
- Account that cannot accept OCTs. Some card accounts have issuer-side restrictions blocking OCT receipt. If the payment processes despite these restrictions and is then reversed by the issuer, it can appear as a 13.8 dispute.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the OCT transaction date |
| Merchant Response Window | 30 days | From acquirer receipt of dispute; processor deadline may be shorter |
| Pre-Arbitration | 30 days | After representment rejection, if escalation is warranted |
Evidence You Will Need
- Cardholder consent documentation showing the recipient agreed to receive OCT payments to this specific card account — the registration record, terms acceptance, or payment destination confirmation
- Payout request record showing the cardholder or account holder initiated or confirmed this specific payment
- Platform account history showing the card on file was the designated payout destination and has previously received OCTs the cardholder acknowledged
- Terms of service acceptance specifically including language about OCT receipt and the cardholder's agreement to receive payments on their registered card
- Payout notification records showing the cardholder received advance notice of the payment (email, in-app notification, or SMS) prior to the dispute
- Identity verification confirming the recipient and the cardholder are the same person — relevant in scenarios where someone disputes a payment they received on behalf of themselves
How Merchants Lose This Dispute
- No specific consent to receive OCTs on this card. Platform-level account consent is not the same as card-level OCT consent. If you cannot document that this cardholder agreed to receive push payments on this specific card, the dispute stands.
- Sending to a card not designated by the cardholder. If the platform selected the payout destination rather than the cardholder, there is no consent evidence to produce.
- Amount disputes bundled as 13.8. If the cardholder is disputing the amount of the OCT rather than its existence, you need amount documentation. Pure consent evidence will not address an amount discrepancy.
- Ignoring the technical nature of the dispute. Some 13.8 disputes arise from issuer-side restrictions on OCT receipt. In those cases, the underlying transaction may be technically correct but the issuer's system cannot accept it — these cases require processor-level investigation.
Response Framework Overview
- Confirm the cardholder is the OCT recipient. Verify the account that received the payment belongs to the person who consented to receive it on your platform.
- Locate the consent documentation. Pull the terms acceptance, card registration record, or payout request that covers this specific OCT.
- Document the payout request sequence. Show the timeline from the payout trigger (e.g., game win, sale completion, settlement approval) to the OCT initiation.
- Provide prior successful OCT history. If the cardholder has received previous OCTs from your platform without dispute, this establishes an established relationship and undermines an "unsolicited" claim.
- Address the specific dispute reason. Confirm whether the dispute is about consent, amount, or a different concern and tailor your evidence accordingly.
Prevention Tips
- Obtain explicit card-level OCT consent during card addition. When a cardholder adds a card to your platform for payout purposes, include an explicit acknowledgment that the card will receive OCTs. Store this acceptance with a timestamp.
- Send pre-payout notifications. Notify the cardholder before processing the OCT — "Your payout of $X will be sent to your card ending in XXXX within 24 hours." This creates a record that the cardholder was informed.
- Confirm payout destination at withdrawal time. Require the cardholder to confirm their payout card at the point of each withdrawal request rather than defaulting to the card on file from registration.
- Monitor OCT acceptance rates. Issuers that block OCTs generate declined transactions before the chargeback stage. Consistent declines from certain BINs indicate issuer restrictions that should be addressed with alternate payment methods.
Frequently Asked Questions
What is an Original Credit Transaction (OCT)?
An Original Credit Transaction (OCT) is a Visa push payment — a credit initiated by the sender (merchant, platform, or payer) that pushes funds directly to a cardholder's Visa account. OCTs are used for prize payouts, insurance settlements, peer-to-peer transfers, marketplace seller payouts, and gaming winnings. Unlike a standard refund (which reverses a prior purchase), an OCT creates a new credit to the account.
Why would a cardholder not want to receive a credit?
Several reasons: the cardholder did not request the payment and considers it suspicious, the account has restrictions that prevent it from accepting OCTs, the cardholder has closed or frozen the account, or the OCT was sent without proper prior agreement and the cardholder disputes its legitimacy. Some issuers also block OCTs from certain merchant categories by default.
Who is typically affected by Visa 13.8 disputes?
Code 13.8 primarily affects platforms that use OCTs for payouts: gaming and gambling platforms, peer-to-peer payment services, insurance companies making claim payments, gig economy platforms paying workers, and merchants issuing refunds via OCT rather than standard credit. Any business that initiates push payments to cardholder accounts may encounter this code.
How is 13.8 different from a standard refund dispute?
A standard refund credit reverses a prior purchase transaction and links back to the original sale record. An OCT is an independent payment with no prior purchase to reference. Code 13.8 specifically addresses the rejection of an OCT — the cardholder is saying they did not agree to receive this push payment, not that a refund was owed and not received.