Visa Chargeback Reason Code 12.1: Processing Errors
Table of Contents
- What is Visa chargeback reason code 12.1?
- What causes code 12.1 chargebacks?
- What's the time limit to respond to code 12.1 chargebacks?
- How can merchants fight code 12.1 chargebacks?
- How can merchants prevent code 12.1 chargebacks?
- About Visa chargeback reason codes
Merchants who receive a chargeback for a transaction placed with a Visa card may encounter reason code 12.1, which indicates an improperly processed transaction that the cardholder does not believe they should be responsible for paying. The actual underlying cause of this chargeback is usually merchant error. Merchants who believe they have received an invalid chargeback under reason code 12.1 may be able to represent the transaction and reverse the chargeback with the right compelling evidence.
What is Visa chargeback reason code 12.1?
Visa chargeback reason code 12.1 falls under the “Processing Errors” category. The shorthand description is “Late Presentment.” This code indicates the merchant waited too long to finish processing a transaction, and the account was no longer in good standing when the transaction was completed.
Transaction processing is a multi-step operation, and while it is common for all of the steps to be completed within a few moments of each other, this is not mandatory and is not always the case.
Many days can pass between the start of a transaction and its final presentment to the issuing bank, and as long as the card is still in good standing the transaction would be considered valid. But if the card expires, exceeds its credit limit, gets lost or stolen, or is otherwise rendered unusable during that time, the merchant may end up vulnerable to this type of chargeback.
What causes code 12.1 chargebacks?
This chargeback is usually caused by merchant error. In most cases, a credit card sale goes from start to finish quite quickly, but sometimes there are reasons to wait before finalizing a transaction. If the merchant waits too long, this chargeback can occur.
Perhaps the merchant agreed not to charge the card until a product was received in stock and ready to ship, or perhaps there was a miscommunication between the merchant and the cardholder that took some time to resolve.
Whatever the reason, if too much time passes or the card is no longer valid when the merchant finally presents the charge, either the cardholder or the issuer can exercise their chargeback rights against the merchant.
When a presentment is considered late because something happened to take the card out of good standing—such as theft, a data breach, or the cardholder exceeding their spending limit—it’s not really the merchant’s fault per se, but it is nevertheless the delay in processing that makes the transaction subject to a “Late Presentment” chargeback.
What's the time limit to respond to code 12.1 chargebacks?
The acquirer or merchant has 30 days to respond to a chargeback filed under reason code 12.1.
How can merchants fight code 12.1 chargebacks?
Merchants can only fight code 12.1 chargebacks if the charge was processed before the applicable deadline or if the cardholder has already been refunded.
Your chargeback response should include the following:
- A transaction receipt or other documents showing that late presentment did not actually occur.
- If you have already processed a refund for the transaction in question, provide documentation that proves you have credited the cardholder’s account.
- If you have resolved the issue directly with the cardholder, provide proof, such as written correspondence, that proves they no longer wish to dispute the charge.
How can merchants prevent code 12.1 chargebacks?
Merchants can prevent code 12.1 chargebacks by ensuring any delay in processing a transaction follows the card network rules and guidelines. In these scenarios, merchants must be aware of the relevant deadlines and should be careful not to wait too long before finalizing the transaction.
Sometimes, it may be safer to cancel the transaction, contact the cardholder, and start over.
The following tips can help you avoid this kind of chargeback:
- Try to finish and submit transactions on the same day you authorize them.
- Always present transactions to the issuing bank within the allowable timeframe.
- Send completed transactions to your payment processor as soon as possible—preferably on the day of sale.
- If you want to delay processing a transaction, use an authorization hold to ensure funds will be available.
About Visa chargeback reason codes
Reason codes are alphanumeric codes that provide the justification for granting a chargeback. Pursuant to the Fair Credit Billing Act of 1974, cardholders have the right to dispute unauthorized or erroneous charges, and issuing banks must reverse a disputed transaction if the cardholder’s claim is valid.
When a cardholder contacts their issuing bank to dispute a transaction and receive a chargeback, the dispute is assigned a reason code that most closely matches the substance of the cardholder’s claims. The reason code provides the merchant and other stakeholders in the dispute with a concise explanation for why a chargeback has been granted.
Each card network—Visa, Mastercard, American Express, and Discover—defines and maintains their own unique set of reason codes, which are applied to disputes by the banks that issue credit and debit cards under their brands.
Visa specifies 46 reason codes under the categories of Fraud, Authorization, Point-of-Interaction Error, Consumer Disputes, and Processing Errors. Visa uses a numeric scheme for its chargeback reason codes.
Understanding chargeback reason codes is one of the most essential parts of effective chargeback management. Identifying the chargeback reason code and the evidence required to fight it is the first step in chargeback representment, and analyzing your chargeback reason codes can provide you with insights into what types of disputes are causing you the most trouble. With this information, you can determine the root causes of your chargebacks and take action to prevent them from reoccurring.