> ## Documentation Index > Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Vindicia Internal Notes for Subscribe 2023.04 Release Production Release Date: April 27, 2023 **Parent topic:**[Vindicia Subscribe - 2023.04 Release](2023.04_tp_subscribeReleaseNotes) ## Subscribe Features ### Vindicia IDP Integration Improvements The following changes were made to improve our Vindicia IDP integration: * For merchants set up with Vindicia IDP, when a user is created in the slm system, that user is automatically added in Vindicia IDP (VIN-18698) * For merchants set up with Vindicia IDP, when a user is deleted in the slm system, that user is automatically deleted in Vindicia IDP (VIN-20826) * With this update, Users using extenal IDPs or Vindicia IDP can no longer change their email address in the Subscribe Merchant Portal **My Settings** page. (VIN-22006) ## Payment Features ### Chase Paymentech Integration - Network Response Codes and Merchant Advice Codes Vindicia utilizes authorization response codes that are received from payment providers to understand the reason for a failure, designate as a hard (R) or soft (D) fail, and enable smart retries when relevant. With this release, Vindicia incorporates support for response codes that originate from the card networks (Network Codes and Merchant Advice Codes - MAC) for Chase Paymentech. The card network response code supply an additional layer of data about the failure type and help enable smart retries, when possible. Card networks have reassigned their response codes to four different categories. This change maximizes the retry process's efficiency by defining clear response codes and behaviors.​ The following categories were defined by card networks and are supported by Vindicia for network codes: * **Category 1**: The issuer will never approve the Transaction (reattempt is not allowed)​ * **Category 2**: The issuer cannot approve the Transaction at this time (reattempt is allowed)​ * **Category 3**: Data quality concern (re-validate data before reattempt)​ * **Category 4**: Generic response code (reattempt is allowed)​ ​Additionally, when a reattempt is allowed, there is a limitation of 15 attempts over 30 days.​ ​For Merchants processing through Chase Payments, Vindicia allows merchant to choose whether to use Chase's response codes for retry logic or to enable the category allocation and/or use the card network response codes. **Note:** If the merchant does not request a change to network codes, no change occurs and the system functions as before. For details on how merchants can choose the priority of which network response codes to consider first, see the [Retry Policy](https://docs.vindicia.com/bundle/subscribeMerchantConfiguration/page/topics/retryPolicy.html) chapter in in the Merchant Configuration Guide. Additionally, the **network\_response\_code** and **merchant\_advice\_code** fields were added to the tx\_disposition\_log table. (VIN-20882, VIN-16984) ### JusPay Integration - Gateway Response Codes for Checkout.com Vindicia utilizes authorization response codes that are received from payment providers to understand the reason for a failure, designate as a hard (R) or soft (D) fail, and enable smart retries when relevant. With this release, Vindicia incorporates support for response codes that originate from processors behind the gateway (and closer to the payment failure) such as when using JusPay as a gateway and Checkout.com as the payment processor. These response code supplies an additional layer of data about the failure type and help enable smart retries, when possible.​​ For more details on configuring Checkout.com via JusPay, see the [JusPay Configuration page](https://docs.vindicia.com/bundle/subscribeMerchantConfiguration/page/topics/jusPayConfiguration_r.html). (VIN-19915) ## Data Improvements ### RetainChargeback Risk Handling With this release, changes were made to reduce the risk of a Forced Deposit. The following changes have been implemented: * The Retain Config file has been deployed in all Production gear workers. * New Technical Chargeback Codes have been added to the Retain Config file to ensure we are accounting for all of the technical chargebacks when calculating the risk. The following **Reporting Reason Codes** were added: | Reporting Reason Code | Description | | - | - | | 11.2 | Declined Authorization | | 11.3 | No Authorization | | 4807 | Warning Bulleting File | | 4808 | Requested/Required Authorization Not Obtained | | 4812 | Account Number Not on File | | 70 | No Verification/Exception File | | AT | Authorization Related, Issuer Challenges the Validity of a Card… | * Force deposit has been disabled on cards that had a previous chargeback. For example, forced deposit is not applied to a credit card transaction if the payment method has any record of chargeback. * The new**transaction\_log** creates a record of the transactions that were meant to use forced deposit but did not. * The **check\_chargeback\_for\_forcedeposit** feature flag will be added for all merchants. (VIN-18014) ### Retain Blacklist Management The new **BL Reason Code ID** and **Description** columns have been added to the blacklist table and Blacklist Reason Code table respectively to reflect the reason the BIN was added to the table: | BL Reason Code | Description | | - | - | | BL001 | cb\_threshold | | BL002 | VisaNonCompliance | | BL003 | MCNonCompliance | | BL004 | PREPAID | | BL005 | ComplianceAdjacentBINs | | BL006 | BankIssues | | BL007 | Other | Current data from the SOAP note was migrated to the new **BL Reason Code** column. * **BL004** and its description was assigned to the BINs with the SOAP Note **PREPAID**. * **BL001** and its description was assigned to the BINs with the SOAP Note **cb\_threshold**. * Other BINs in the blacklist have an empty Reason Code column. The scripts that added BINs to the Blacklist were updated. Currently, the Reason Code in the script is mandatory and the SOAP note is optional. **Note:** If multiple BINS are added by file, they must be split by Reason. (VIN-20706) ## Internal Fixes The following issues were solved in this release: | Ticket | Title | Description | | - | - | - | | PORT-2156 | Subscribe Merchant Portal 2.0 - Enter/Return Key Did Not Submit the Login Credentials | Users were unable to log into the Subscribe Merchant Portal 2.0 by pressing the Enter key when submitting login credentials. This issue has been fixed. | | PORT-2893 | Subscribe Merchant Portal 2.0 - User Role Dropdown for Admin Merchant User in QA10 | The **User Role** dropdown list did not appear on the **Create Report** screen of the **Merchant Users** page. This issue has been fixed. | | BIMS-798 | Braintree Integration - Revenue Share Value Parameter | The merchant identifier sent to Braintree for revenue sharing identification was not updated. This issue has been fixed. | ### Known Issues This release has the following known issues. * In Subscribe Merchant Portal 2.0, the **Merchant User** Report may show incorrect status for merchant users that use identity providers to login to the Portal. * Merchants using Vindicia IDP, can view user status in the Vindicia IDP Care Console. * Merchants using external Identity providers, such as OKTA or MS Azure, can check user status in their respective IDP Portals. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.