Analyze my chargebacks

Visa reason code 12.4: meaning and how to respond

Visa code 12.4 covers a transaction processed with the wrong payment credential. Learn when it applies, how to respond, and the deadlines.

What Visa code 12.4 means and when it applies

Visa code 12.4, “Incorrect Account Number,” covers a transaction processed with the wrong Payment CredentialThe number or other identifier that represents the cardholder’s account and is used to process a transaction.. In practice, the payment or credit was posted to a different account from the one that should have received it. This is a processing-error dispute, not a fraud claim or dissatisfaction with a purchase.

The issuer may file a 12.4 dispute when at least one of these two conditions applies:

  1. A transaction or an Original Credit Transaction (OCT)A transaction initiated by a merchant, acquirer, or agent that sends a credit to a Payment Credential or bank account. used the wrong Payment Credential. An OCT sends money to the specified account instead of charging it. In the US Region, this trigger also includes an Adjustment of an ATM Cash Disbursement or a PIN-Authenticated Visa Debit Transaction.
  2. An ATM Deposit AdjustmentA correction made by the acquirer to a deposit completed at an ATM, such as when a deposited item cannot be accepted. used the wrong Payment Credential. In this situation, the error affects the account linked to the deposit adjustment.

Source for both conditions: Visa Core Rules §11.9.3.1, Table 11-66 (ID# 0030292).

Even when one of those conditions exists, a 12.4 dispute is invalid if at least one of these situations applies:

  1. The transaction was an ATM Cash Disbursement. The exclusion applies to the cash disbursement itself, not to an ATM Deposit Adjustment covered by this code.
  2. The transaction used Straight Through ProcessingA Visa processing method that requires the acquirer to register and sign a participation agreement.. This method is handled separately and falls outside code 12.4.
  3. The Payment Credential does not correspond to any card issued or outstanding, and there is a capture or approval record. All of these requirements must be present: no card was issued or remains outstanding for the Payment Credential and there is at least one of these two records, an ImprintA record of card data transferred to the Transaction Receipt. It may be electronic or manual. or an AuthorizationThe process in which the issuer, Visa, or another authorized participant approves the transaction..
  4. The transaction was chip-initiated and contains a valid CryptogramA value created from a combination of specific key data. It helps validate the origin and integrity of the data.. Both elements are required: chip initiation and a valid Cryptogram.
  5. The transaction was a Mobility and Transport TransactionA contactless payment at a fare gate, turnstile, or other urban transit access point. The amount may be calculated from one or more taps during the trip.. This payment type follows separate rules.
  6. The transaction was a Mobile Push Payment TransactionA credit transaction initiated by the cardholder on a phone or tablet to pay for goods or services, add money, or withdraw money.. This transaction type also falls outside code 12.4.

Source for all six exclusions: Visa Core Rules §11.9.3.2, Table 11-67 (ID# 0030293).

The filing deadline is also part of validity. The general rule gives the issuer 120 calendar days from the Transaction Processing Date or the Processing Date of the ATM Deposit Adjustment. For a US Domestic Adjustment of an ATM Cash Disbursement or a PIN-Authenticated Visa Debit Transaction, the 120 days run from the Transaction Date of the Adjustment. After the applicable deadline, the issuer cannot file a 12.4 dispute.

Source for the filing deadline: Visa Core Rules §11.9.3.3, Table 11-68 (ID# 0030294).

When the error occurred and no exclusion applies, the issuer returns the transaction to the acquirer, the institution that represents the merchant in the Visa network, and disputes the amount. If the actual issue is different, see nearby codes: 12.2 for an incorrect transaction code, 12.3 for incorrect currency, 12.5 for an incorrect amount, and 11.2 or 11.3 when Authorization is the issue.

Deadlines for each party under Visa 12.4

1 block represents 10 calendar days.

  1. IssuerFile the 12.4 disputeThe clock starts when the transaction or ATM Deposit Adjustment is processed by Visa.
    Up to 120 calendar days
  2. AcquirerSubmit a Visa-permitted defense pathThe clock starts when the dispute is processed by Visa.
    Up to 30 calendar days
  3. IssuerRespond to the acquirer’s defenseThe clock starts when the acquirer’s defense is processed by Visa.
    Up to 30 calendar days
  4. AcquirerRespond to the issuer’s pre-arbitration attemptThe clock starts when the issuer’s pre-arbitration attempt is processed by Visa.
    Up to 30 calendar days
  5. IssuerAsk Visa to decide the caseThe clock starts when the acquirer’s pre-arbitration response is processed by Visa.
    Up to 10 calendar days
These are the time limits set by Visa.Your deadline to submit documents may be shorter; confirm it with your acquirer.Source:Visa Core Rules, Tabela 11-68 (ID# 0030294), p. 730, e Tabela 11-2 (ID# 0030213), pp. 671-673

Who files the dispute and what happens next

The issuer, the bank or institution that maintains the cardholder’s account, files the 12.4 dispute based on its own records. The rule does not require a cardholder complaint or statement of loss.

When filing the case, the issuer provides one of two certifications:

  1. The wrong Payment Credential was used.
  2. The Payment Credential does not appear in the issuer’s master fileThe issuer’s record used to verify which Payment Credentials it maintains., and no Authorization was obtained. Both facts must be true for this second certification: the Payment Credential does not match any credential in the issuer’s records and the transaction was not authorized.

Source for the certifications: Visa Core Rules §11.9.3.4, Table 11-69 (ID# 0030546).

The case is processed in VROLVisa Resolve Online is the system where the issuer and acquirer exchange the dispute, response, and case documents.. If the merchant has a valid basis to respond, it gives its documents to the acquirer. The acquirer submits the Dispute ResponseThe acquirer’s formal response to the issuer’s dispute, including the basis and documents for the defense. within 30 calendar days of the Dispute Processing Date.

In Category 12, the issuer makes the pre-arbitration attemptThe issuer’s formal request for the acquirer to reconsider the defense before the case proceeds to Visa for a decision. and, if the case remains unresolved, asks Visa for arbitration. The acquirer responds at both stages. This is the Collaboration flow; it does not include a stage called “second presentment.”

Source for the process and deadlines: Visa Core Rules §11.2.3, Table 11-2 (ID# 0030213).

Before building a defense, check whether this dispute is invalidProving any one condition is enough to challenge the dispute's validity.
  • The transaction is an ATM Cash Disbursement.
  • The transaction is a Straight Through Processing Transaction.
  • Both of these are true: no card was issued or is outstanding for the Payment Credential, and at least one of these records exists: an Imprint or an Authorization.
  • Both of these are true: the transaction was chip-initiated and it contains a valid Cryptogram.
  • The transaction is a Mobility and Transport Transaction.
  • The transaction is a Mobile Push Payment Transaction.
  • The issuer filed the dispute more than 120 calendar days after the Transaction Processing Date or the Processing Date of the ATM Deposit Adjustment.

Source:Visa Core Rules §11.9.3.2, Tabela 11-67, ID# 0030293, e §11.9.3.3, Tabela 11-68, ID# 0030294

How to reduce the risk of this code

Visa’s guidance is direct: train staff to follow the correct transaction-processing procedures and, when the payment method supports it, swipe the magnetic stripe or read the chip instead of keying in the Payment Credential. This reduces the risk of entering or routing the wrong credential.

Also retain the Transaction Receipt and Authorization records. The receipt must contain the applicable elements required by Visa, including the masked Payment Credential on the cardholder’s copy, the Authorization Code when applicable, the Visa name, a description of the purchase, the merchant’s name and location, the return and refund policies, the amount, currency, date, and transaction type. These records do not prevent the error, but they allow the merchant and acquirer to verify which Payment Credential was processed and prepare a defense when the dispute is wrong.

Source for the prevention measure: Visa Dispute Management Guidelines for Visa Merchants, Condition 12.4, p. 32. Source for the receipt content: Visa Core Rules §5.9.2.2, Table 5-33 (ID# 0027843).

Evidence the merchant and acquirer need to gather

Clarify the payment data

Before collecting documents, compare the Payment Credential shown in the dispute with the one on the merchant’s receipt and confirm whether the transaction was authorized. If the Payment Credential does not match the receipt or no Authorization was obtained, Visa’s guidance is to accept the dispute.

If there is a valid basis to respond, the defense must establish at least one of Visa’s four accepted paths. One complete path is enough. Within the selected path, however, all of the requirements listed below must be met:

  1. The correct Payment Credential was processed. Provide the Transaction Receipt required by §5.9.2.2 or another record proving the same fact. If the dispute concerns a Payment Credential that does not appear in the issuer’s master file, also provide the authorization logThe record of the Authorization request and response. Here, it shows which Payment Credential was submitted and that the transaction was approved.. This log is conditional; it is not an additional requirement for every 12.4 dispute.
  2. The merchant already issued a credit or Reversal that the issuer did not address. Provide documentation of the credit or Reversal showing the amount and Processing Date. The record must show a merchant-issued credit or Reversal that the issuer did not address when filing the dispute. If the issuer already applied the credit and disputes only a remaining amount, this path does not resolve that balance.
  3. The cardholder no longer disputes the transaction. Provide a letter or email written by the cardholder stating that they no longer dispute the transaction. A statement the merchant writes on the cardholder’s behalf does not replace that document.
  4. The dispute is invalid. Provide the record establishing at least one of the six exclusions in Table 11-67 or a missed deadline under Table 11-68. For the exclusion involving a Payment Credential with no card issued or outstanding, both forms of proof are required: evidence of that credential status and an Imprint or an Authorization. The chip exclusion also requires both elements: a chip-initiated transaction and a valid Cryptogram.

Source for the four defense paths: Visa Core Rules §11.9.3.5, Table 11-70 (ID# 0030295). Source for the operational documents: Visa Dispute Management Guidelines for Visa Merchants, Condition 12.4, p. 32.

Frequently asked questions

When does Visa apply chargeback code 12.4?

It is the “Incorrect Account Number” dispute condition. The issuer may use it when a transaction or Original Credit Transaction was processed using the wrong Payment Credential, or when an ATM Deposit Adjustment used the wrong credential. In the US Region, the transaction trigger also includes an Adjustment of an ATM Cash Disbursement or a PIN-Authenticated Visa Debit Transaction. Code 12.4 covers a processing error, not fraud or dissatisfaction with a purchase.

Does the cardholder need to contact the issuer before it files a 12.4 dispute?

No. The rule does not require a cardholder statement. The issuer files the dispute with one of two certifications: the wrong Payment Credential was used; or the transaction was processed to a credential that does not appear on the issuer’s master file and no Authorization was obtained.

What does the merchant need to submit to challenge a 12.4 dispute?

The acquirer submits a Dispute Response in VROL. The defense must establish at least one of Visa’s four accepted paths: the correct Payment Credential was processed, a merchant credit or Reversal was not addressed by the issuer, the cardholder no longer disputes the transaction, or the dispute is invalid.

When should the merchant accept a 12.4 chargeback?

Visa’s guidance says to accept when the Payment Credential on the dispute does not match the one on the merchant’s receipt or when the transaction was not authorized. In those situations, the receipt-and-authorization-log defense path does not apply.

Does every 12.4 defense require an authorization log?

No. In addition to the receipt or equivalent record, the authorization log is required when the dispute concerns a transaction processed to a Payment Credential that does not appear on the issuer’s master file. The log shows that Authorization was obtained for that credential.

How long does the issuer have to file a 12.4 dispute?

The general deadline is 120 calendar days from the Transaction Processing Date or the Processing Date of the ATM Deposit Adjustment. For a US Domestic Adjustment of an ATM Cash Disbursement or PIN-Authenticated Visa Debit Transaction, the 120 days run from the Transaction Date of the Adjustment.

View all Visa chargeback reason codes or return to Knowledge.

First step

Start with your chargeback history.

Sparsu uses the data you already have to size the opportunity, recognize patterns and identify which data can improve the next decisions.