Skip to main content
Release Date: June 2nd, 2021 Parent topic:Vindicia Subscribe-2021.05 Release Notes

​
Payment Features

​
Visa Response Codes

Visa has re-allocated its response codes to four different categories as announced in the previous release. The end-purpose of this change is to maximize the efficiency of the retry process by defining clear response codes and behaviors. The following categories, each defining the retry policy, were defined:
  • Category 1: Issuer will never approve transaction (reattempt not allowed)
  • Category 2: Issuer cannot approve the transaction at this time (reattempt allowed)
  • Category 3: Data Quality concern (re-validate data prior to reattempt)
  • Category 4: Generic response code (reattempt allowed) In addition, when re-attempt is allowed, there is a limitation of 15 attempts over 30 days.
Merchants must revise their current retry policy to ensure that the 15 retries within 30 days limitation is avoided. A fine of 10c/transaction is expected. For details of the response mapping changes, see the Change to Softcode spreadsheet in VIN-10158. (VIN-9274)

​
Purchase Return (Refund) Authorization Mandate

Visa and Mastercard have issued mandate directives requiring merchants to request authorization for every cardholder refund or return transaction. New response codes have been added by the card issuers to support this initiative. Payment Processors handle this change by providing their own response codes to indicate the refund state. Vindicia is enforcing this change in its system behavior by displaying the response codes according to the received responses and proceeding in the authorization flow accordingly. For more details of existing and newly added refund error codes, see Refund Authorization Codes Excel. (VIN-9767)

​
Subscribe Features

​
FiServ File Data Gateway Integration

Internal operational endpoint change for connecting to FiServ. MessageWay file system is being decommissioned so we are integrating into FiServ File Data Gateway for all of FDMS batch traffic. This feature deployment to production has been delayed and will be addressed in the coming weeks. For compass URL and more details, see Jira ticket (VIN-7448)

​
Internal Fixes