Reason code

This code is used when an issuer disputes a second presentment from the acquirer, claiming that the Acquirer Reference Data provided doesn't match the original transaction details, and no supporting documentation was received or required. Essentially, the issuer asserts that the information submitted by the acquirer in response to a chargeback is incorrect or invalid.

To address a chargeback under Reason Code 4905, provide evidence that the Acquirer Reference Data is accurate and corresponds to the original transaction. This may include:

• Transaction Logs: Detailed records from your payment system showing the transaction's processing and any associated reference data.
  
  
• Audit Trails: Comprehensive logs that track changes or actions taken on the transaction, demonstrating consistency in reference data.
  
  
• Internal Memos or Notes: Any internal communications or notes related to the transaction that can shed light on the reference data's validity.

‍

To minimize the risk of such chargebacks under reason code 4905

• Standardize Reference Data Formats: Ensure that all reference data follows a consistent format to reduce the chance of discrepancies.
  
  
• Implement Data Validation Checks: Use automated systems to validate reference data before submission to catch errors early.
  
  
• Train Staff on Data Accuracy: Educate employees on the importance of accurate data entry and the potential consequences of errors.
  
  
• Establish Clear Communication Channels: Maintain open lines of communication with issuers to quickly resolve any discrepancies before they escalate.

‍