> ## 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 - 2024.02 Release Notes

Production Release Date: February 27, 2024

* **[Vindicia Subscribe Internal Notes for 2024.02 Release](2024.02_tp_internalNotes)**

## Announcements

### User Management Self-Enabling

Vindicia is working on self-enabling administrative merchant users for management of the merchant user staff and their associated roles. The feature will be available as part of an extension of the Vindicia IDP in the next few months.

Rollout will begin in the upcoming months and migration will be communicated directly per merchant.

## Payments Features

### PayU Integration - Upgrade Paymentsos version to 1.3

From this release, Vindicia is upgrading its PayU integration from Paymentsos 1.2 to Paymentsos 1.3, the latest version.

This change will allow submitting Transactions to PayU in both a tokenized form or non-tokenized form.

(VIN-28218)

### Stripe Integration - CustomerID Display Change for Stripe Charge API

The Stripe CustomerID was stored by Vindicia with a **Customer** prefix and displayed accordingly on the portal as well.

From this release, the prefix for the CustomerID has been removed and the Portal custom data display shows only the CustomerID itself.

(VIN-26457)

### Merchant Advice Code (MAC) Support Extended

Vindicia receives Authorization response codes for every Transaction it submits, which explain the type of Transaction failure, and the relevant resolution and therefore serve as a decision point on whether a Transaction can be reattempted.

Authorization response codes that originate from the credit card issuer such as Merchant Advice Codes (MAC) supply an additional layer of detail about the Transaction failure type and help enable smart retries when possible.

With this release, Vindicia is extending its support for Merchant Advice Codes (MAC) for the following payment providers:

* Worldpay WPG (VIN-27933)
* FDMS Compass (VIN-20404)

Along with Vindicia's advisers and technical representatives, you can choose which authorization response codes gets top priority for the decision whether to retry capturing your Transactions.

## Bug Fixes

The following issues were solved in this release:

| Ticket | Title | Description |
| - | - | - |
| PORT-3727 | Subscribe Portal 2.0 - Subscribe tooltip Help not appearing in Chrome browser | The Subscribe tooltip Help topics were not appearing in certain browsers. The issue has been resolved. |
| VIN-28121 | Subscribe SOAP API- revoke call for account credits not working as expected | Revoke API call for account credits was returning an unexpected error for \$0 amounts. The issue has been fixed and a 400 error will be returned stating that **No credits available to process** |
| VIN-28821 | Cancelled subscription billed with a payment method update | A cancelled subscription was billed with a payment method update. The issue has been resolved. |
| VIN-28828, VIN-27493 | Subscribe Portal 2.0 - Metadata update or deletion for Carrier Billing Payment method in Subscribe Portal not working | Metadata update or deletion for Carrier Billing Payment method in Subscribe Portal was not stored correctly. The issue has been fixed. |
| VIN-28412 | Subscribe portal 2.0- Duplicate subscriptions appearing | Duplicate subscriptions appeared in Portal 2.0. The issue has been resolved. |
| VIN-28497 | General Ledger Report not completed | The General Ledger Report was running for long periods without completing the report due to faulty record collection. The issue has been resolved. |

### 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.