Visa Reason Code 13.9: Non-Receipt of Cash or Load Transaction Value

What Visa Reason Code 13.9 Means

Visa reason code 13.9 falls under the Consumer Disputes category and is titled Non-Receipt of Cash or Load Transaction Value. It covers two distinct but related scenarios: (1) an ATM cash withdrawal where the cardholder's account was debited but the machine did not dispense the requested cash — a full or partial dispense failure; and (2) a prepaid or stored-value card load where the cardholder paid the load amount but the value did not appear on the target card.

This chargeback type is specific to ATM operators, prepaid card networks, and financial services platforms that handle stored-value loads. Traditional retail merchants will rarely encounter this code. The dispute resolution depends almost entirely on machine-side technical records.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• ATM cash jam or mechanical failure. The dispensing mechanism jams mid-dispense, resulting in no cash or partial cash delivery. The account is debited for the full amount while the cardholder receives less or nothing.
• ATM communication failure during dispense. The machine authorizes the transaction and debits the account, but a network timeout during the dispense phase results in no physical cash being released.
• Short dispense (partial cash received). The cardholder requested $200 but the machine dispensed only $100 due to a cassette jam or counting error. The full $200 was charged.
• Prepaid card load not credited. The cardholder swipes their payment card at a reload terminal, the payment is captured, but a processing error between the terminal and the prepaid platform means the load value never appears on the prepaid card.
• ATM out-of-service mid-transaction. The ATM powers down or goes out of service after capturing the authorization but before completing the dispense. The transaction settles but no cash was delivered.

Key Deadlines & Timeframes

Evidence You Will Need

• ATM electronic journal entry for the specific transaction, showing the dispense event, dispense amount, and any error codes at the exact time and date of the dispute
• Vault/cassette reconciliation report showing no unexplained cash surplus that would indicate a successful full dispense (surplus cash = cash was dispensed and not claimed; no surplus = dispense failure)
• Terminal error log documenting any mechanical, communication, or software errors during the disputed transaction window
• For prepaid loads: load platform transaction log showing whether the load was successfully posted to the target prepaid account and the timestamp of posting
• Network transaction record from your switch or processor confirming the transaction was authorized and settled, alongside the dispense/load confirmation status
• Balancing report showing the ATM cash balance before and after the disputed transaction period, used to confirm the vault accounting matches the dispense records

How Merchants Lose This Dispute

• Journal shows error code or dispense failure. If the electronic journal records an error during dispense, the chargeback is valid. Attempting to dispute it with generic evidence will fail and incur additional arbitration fees.
• No vault reconciliation data. Without vault balancing records, you cannot prove the cash was actually dispensed. A journal entry alone without supporting vault data is insufficient for high-value ATM disputes.
• Delay in pulling journal records. ATM journals are typically stored locally and may be overwritten by newer transactions. Pulling the journal within 24-48 hours of dispute notification is critical. Delays mean lost records and lost disputes.
• Prepaid load processor confirmation not obtained. For prepaid load disputes, if you cannot get a load confirmation from the prepaid platform's records, the cardholder's claim that value was not loaded stands unchallenged.

Response Framework Overview

1. Pull the electronic journal immediately. This is time-sensitive. Access the ATM journal for the transaction date, time, and amount before records are overwritten.
2. Run vault reconciliation for the dispute date. Compare the expected vault balance to the actual balance to determine if cash was dispensed into or retained by the machine.
3. Confirm dispense status. The journal and reconciliation together determine your defense position: successful full dispense (proceed to representment) or failure/partial (accept the chargeback or partial credit).
4. For prepaid loads: contact the prepaid platform immediately for the load event record showing credit to the cardholder's stored-value account.
5. Document your findings. Whether you are defending or accepting, document the investigation clearly for your processor and for your internal maintenance records.

Prevention Tips

• Archive ATM electronic journals for at least 18 months. Journal data is the foundation of every 13.9 defense. Remote journal archiving to a central server prevents loss due to local storage limits or machine failures.
• Perform daily vault reconciliation. Same-day balancing identifies dispense discrepancies before they compound and before dispute windows close.
• Implement real-time dispense monitoring. Modern ATM management platforms can flag incomplete dispense events in real time, allowing you to proactively contact affected cardholders and reverse charges before chargebacks are filed.
• For prepaid loads: require load confirmation receipt. Terminals should not capture payment until a confirmed load acknowledgment is received from the prepaid platform. Hold-and-confirm architecture eliminates most load failure disputes.

Frequently Asked Questions

What types of transactions does Visa 13.9 cover?

Code 13.9 covers two primary scenarios: ATM cash dispensing failures (the cardholder was charged for a cash withdrawal but the machine did not dispense the cash or dispensed less than the requested amount), and prepaid card or stored-value load failures (the cardholder paid to load value onto a prepaid card but the value was not credited to the card).

What journal data do ATM operators need to defend a 13.9 dispute?

ATM operators need the electronic journal entry for the specific transaction, showing the dispense event status (successful, partial, or failed), the cassette counts before and after the transaction, any error codes logged by the ATM at the time of the transaction, and the vault reconciliation report showing no unexplained cash excess that would indicate a dispense failure.

What if the ATM showed an error but the cardholder was still charged?

If the ATM logged a dispense error or the transaction was not completed normally, the cardholder's claim is likely valid. In this case, the ATM operator should confirm the dispense failure through journal records, reverse the charge, and document the corrective action. Attempting to defend a confirmed dispense failure will result in lost arbitration and additional fees.

How does the 13.9 rule apply to prepaid card loads?

For prepaid card loads, code 13.9 applies when a cardholder pays to add value to a prepaid or stored-value card and the value does not appear on the card. This can happen due to processing errors between the load terminal and the prepaid card platform, communication failures during the load transaction, or system errors where the charge is captured but the load confirmation is not processed.

Related Codes & Resources