> ## 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 Subscribe - 2023.04 Release
Production Release Date: April 27, 2023
* **[Vindicia Internal Notes for Subscribe 2023.04 Release](2023.04_tp_internalNotes)**
## Subscribe Features
### Subscribe Merchant Portal 2.0 Enhancements
* **Adding Campaign Code to Existing Subscriptions** - With this release, changes were made allowing you to apply a campaign code to an existing subscription without editing the subscription itself.
A new **Apply Campaign Code** button was added in the **Actions** panel. When used, a window appears that allows the user to enter the **Campaign Code**, whether to add to an eligible billing plane, and choose which of the Subscription items to apply. You can apply the **Campaign Code** at the following levels:
* **Subscription**
* **Product**
* **Item**
(PORT-2283)
* **Transaction Summary Details in Search Results on the Transaction List Page** - With this release, a summary of all transactions included in the search results page is displayed. The transaction summary includes amount totals, refunds and is sorted by currency. (VIN-20803/PORT-2695)
* **Email Address Settings for External IDP and Vindicia IDP Users** - With this update, Users using extenal IDPs or Vindicia IDP can no longer change their email address in the Subscribe Merchant Portal 2.0 **My Settings** page. (VIN-22006)
## Payment Features
This release includes the following new 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.
(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.
(VIN-19915)
### Chase Paymentech Integration - Card-on-File Support for Apple Pay
With this release, Card-on-File is supported for Apple Pay in the Chase Paymentech payment provider.
(VIN-22964)
## Bug Fixes
The following issues were solved in this release:
| Ticket | Title | Description |
| - | - | - |
| VIN-17034 | Subscribe Merchant Portal 2.0 - Issue with Search Results on Transactions Page | Subscribe Merchant Portal 2.0 used the time zone settings in the user's web browser for Transaction search results instead of the time zone defined in **My Settings**. This issue has been fixed. |
| VIN-20208 | Subscribe REST API - Create Subscription Error Due to Unicode Characters | An issue in the Create Subscription API caused calls with Unicode characters to fail. This issue has been fixed. |
| VIN-20414 | Subscription Creation - Subscription Remained in a Processing Status After Capture | When a Subscription was created with a campaign that included a discounted first Transaction, the Subscription remained in a Processing status, even after capture. This issue has been fixed. |
| PORT-2695 | Subscribe Merchant Portal 2.0 - Transaction Summary in the Transaction Search List Page Displayed Limited Results | **Transaction Summary** on the **Transaction Search List** did not display the full summary of Transactions in the search results. 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.