Merchants who receive a chargeback for a transaction placed with a Visa card may encounter reason code 70, which indicates an improperly authorized transaction that the cardholder does not believe they should be responsible for paying. The actual underlying cause of this chargeback is usually either true fraud or merchant error. Merchants who believe they have received an invalid chargeback under reason code 70 may be able to represent the transaction and reverse the chargeback with the right compelling evidence.
What is Visa Chargeback Reason Code 70?
Visa chargeback reason code 70 falls under the “Authorization” category. The shorthand description is “Card Recovery Bulletin or Exception File.” This reason code is assigned when a transaction occurs on a date when the card account number is listed in the Card Recovery Bulletin applicable to the Visa Region (US Domestic excluded) where the merchant is located. It may also show up when a transaction is disputed because the amount was under the merchant’s floor limit and no authorization approval was obtained.
Card Recovery Bulletins and Exception Files are documents created by Visa that list credit card numbers that have been reported lost or stolen, are known to be counterfeited, or have other issues that should prevent them from being used. These lists have been distributed to merchants since the pre-digital era to prevent fraudulent and inappropriate transactions.
Fortunately, merchants no longer have to cross-check payment cards against hard copy documents to determine whether or not the card is acceptable to process.
When a merchant sends an authorization approval request, the response code should automatically indicate if a card has been placed on one of these lists. If that is the case, the merchant should not proceed with the transaction.
The response code may even direct them to hold on to the card and contact the issuing bank for further instructions.
What Scenarios Might Lead to This Chargeback?
When a card is lost, stolen, or otherwise compromised, the cardholder is supposed to report it to their issuer immediately. When they do so, the card will be placed on a Card Recovery Bulletin and/or Exception File to notify merchants that the card should not be used for processing.
Few merchants are personally scrutinizing the published versions of these lists nowadays, but any authorization request should let you know whether a card has been placed on them.
If a merchant ignores such a response and processes the card anyway—or does not obtain authorization approval in the first place—this chargeback is sure to follow.
What are the Important Timeframes?
For most disputes, Visa recommends that action be taken within 120 calendar days of the transaction. The acquirer and/or merchant have 20 calendar days to respond to this chargeback after it is filed.
How Can Merchants Fight this Chargeback Code?
Merchants can fight this chargeback if the basis for it is false or erroneous. Your chargeback response should include the following:
- Proof that the transaction was initiated with an EMV chip and offline authorization was obtained.
How Can Merchants Prevent this Chargeback Code?
Most chargebacks in the “Authorization” category can be avoided by remembering to always seek authorization approval and only proceed with transactions that receive a clear, unambiguous approval. Some codes offer the merchant and cardholder some leeway to try again, but any response that tells you that a card is on a Card Recovery Bulletin or Exception File is a big red flag warning you to go no further—you’re dealing with a card that Visa already knows to be problematic, and you are sure to be fully liable for any chargeback that results from processing it.
The following best practices can help you avoid this kind of chargeback:
- Always obtain authorization approval before processing any transaction.
- If a “decline” or ambiguous code is sent in response to an authorization request, ask the cardholder to furnish an alternate method of payment.
- Pay close attention to authorization response codes that indicate lost or stolen cards and follow the guidelines specified by your acquirer or payment processor.
- Never “force” a transaction to go through without authorization, or after receiving a non-approval response.
- Train your staff on proper transaction handling procedures.
- Use up-to-date payment terminals that are compatible with EMV chip technology.
- Avoid manually keying in transactions unless absolutely necessary.
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 of 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.