> ## 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.01 Release Notes Production Release Date: January 30, 2024 * **[Vindicia Subscribe Internal Notes for 2024.01 Release](2024.01_tp_internalNotes)** ## Announcements ### Vindicia GPT in the Vindicia Knowledge Center The [Vindicia Knowledge Center](https://docs.vindicia.com/category/releasenotes) has introduced a generative AI search feature, **Vindicia GPT**. The new Vindicia GPT allows you to ask a question in the Vindicia Knowledge Center search bar and receive a single curated answer of Vindicia's publicly available information. The feature introduced a user-friendly question/answer format as an additional layer to the existing search capabilities available in the Knowledge Center. For more details, see [Vindicia GPT Overview in Knowledge Center Tour](https://docs.vindicia.com/bundle/site_tour/page/site-tour.html#d400e133) ## Subscribe Features ### Subscribe Merchant Portal 2.0 Enhancements * **GDPR Erase Accounts for Merchant Super Users** - With this release, Vindicia will empower Super Users role holders to manually delete individual customer accounts, upon customer request, in compliance with GDPR, from the Account search and Account details pages. See [Account GDPR Erase](https://docs.vindicia.com/bundle/Subscribe_Portal2_User_Guide/page/topics/accountWorking.html#ariaid-title10) in Subscribe Portal 2.0 User Guide. GDPR Erase Action button appearing for an Account Details page (VIN-26996) ## Payments Features ### Merchant Advice Code and Network Response Code Support With this release, Vindicia is extending its support for Authorization Codes for the following payment providers: * **Adyen** - Support will be available for Merchant Advice Codes (MAC) and Adyen's Refusal Reason Codes * **Braintree** - Support will be available for Merchant Advice Codes (MAC) and Network Response Codes * **Orbital Stratus** - Support will be available for Merchant Advice Codes (MAC) and Network Response Codes * **Paysafe** - Support will be available for Merchant Advice Codes (MAC) only 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. For more information about Merchant Advice Codes and Network Response Codes, see [Authorization Response Codes](https://docs.vindicia.com/bundle/vindiciaPaymentRegulations/page/topics/authorizationResponseCodes.html). Contact Vindicia Client Technical Support to discuss implementation. (VIN-20340, VIN-18198, VIN-27469, BIMS-953) ### Cardinal Commerce - 3DS Required Data Change Vindicia supports 3DS via native payment providers or it leverages Cardinal Commerce (a Visa solution) for authentication. From this release, Cardinal Commerce has changed its data requirements and merchants using the solution must provide these to continue using Cardinal Commerce 3DS support. Cardinal commerce requires that the following formerly optional data fields will now become **required** fields by the Visa Secure program in the EMV® 3-D Secure authentication request (AReq) message. In Vindicia, these fields are part of the Subscribe API in different objects such as **ExtendedVerification** and they are now required fields for Cardinal Commerce integration: * Browser IP Address: Appears in Vindicia SOAP API as **PaymentMethod** > **ExtendedVerification** > **BrowserRemoteAddress** * Browser Screen Height: Appears in Vindicia SOAP API as **PaymentMethod** > **ExtendedVerification** > **BrowserScreenResolution** * Browser Screen Width: Appears in Vindicia SOAP API as **PaymentMethod** > **ExtendedVerification** > **BrowserScreenResolution** * Cardholder Billing Address City: Appears in Vindicia SOAP API as **PaymentMethod** > **BillingAddress** > **City** * Cardholder Billing Address Country: Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **BillingAddress** > **Country** * Cardholder Billing Address Line 1: Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **BillingAddress** > **Addr1** * Cardholder Billing Address Postal Code: Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **BillingAddress** > **PostalCode** * Cardholder Billing Address State: Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **BillingAddress** > **District** * Cardholder Email Address: Appears in Vindicia Subscribe SOAP API as **Account** > **EmailAddress** * Cardholder Name: Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **AccountHolderName** * Cardholder Phone Number (Work / Home / Mobile) (At least one of these fields must be provided) Appears in Vindicia Subscribe SOAP API as **PaymentMethod** > **BillingAddress** > **Phone** **Note:** The minimum data requirements do not apply if there are local data privacy regulations that prohibit the data field from being shared. (VIN-28183) ### Cybersource Integration - Support for Brazil's Required Personal Tax ID Brazil tax law requires the personal tax ID - Cadastro de Pessoas Fisicas (CPF). In this release support for passing this input to Cybersource has been added as a custom data, Name Value Pair on the account object. Merchants wishing to pass the input should use: Name: vin:BrazilTax.federalTaxId Value: the customer's tax ID (VIN-28141) ### Litle Integration - Adding Support for XML Version 12 With this release, Vindicia's Litle integration will add support up to XML version 12. Merchants using XML version 10 or above, can integrate with the XML version 12. Existing merchants using the previous XML version are not required to upgrade and can continue without interruption. **Note:** Merchants wishing to integrate to Version 12, contact Vindicia Client Technical Support. (VIN-27564) ## Bug Fixes The following issues were solved in this release: | Ticket | Title | Description | | - | - | - | | CAT-433 | Transaction detail report data mismatch between recurring scheduled (Reports 2.0) report and one time on demand (Reports 1.0) | A data mismatch was detected in Transaction Detail report between a recurring report from Reports 2.0 and a one time report from Reports 1.0. The issue has been resolved. | | DOCS-791 | Documentation added for Stripe Chargeback Configuration | Information on how to configure Stripe Merchant Account and chargeback configuration in the Stripe Portal was added to Vindicia's How To Guide. | | DOCS-814 | User role access to dashboard issue | The user role documentation was showing incorrect permissions for dashboard access. The issue has been fixed. | | PORT-3617 | Subscribe Merchant Portal 2.0 - Product CSV download missing description column | The Product CSV download was missing the description column. Issue has been resolved. | | PORT-3703 | Subscribe Merchant Portal 2.0 - Reverse a payment not working correctly | An issue was encountered when trying to reverse a payment in Subscribe merchant portal 2.0. The issue was found to be a typo of a data identifier and has been resolved. | | VIN-23523 | Access to Vindicia IDP Care Console available to non-admin users | Non-admin users were able to access Vindicia IDP Care console from within Vindicia Portal. The issue has been resolved and only super users can access Care Console. | | VIN-27237 | REST API - Campaign code separator "-" added by default for an additional batch when no separator input provided | A separator was added when generating codes without providing separator input. The separator was different than the one used in 1st batch creating inconsistencies. Issue has been resolved and the separator is kept consistent for all batches. | | VIN-27493 | Carrier Billing - adding and deleting metadata for payment method issue | Unable to remove metadata from carrier billing payment method. Issue was resolved. | | VIN-27601 | Subscribe Merchant Portal 2.0 - saving sales tax exemption failure | Addition of a sales tax exemption to an account was failing. Issue has been resolved. | | VIN-27613 | PayU Integration- non tokenized payment method issue | Prior to this release there was a specific transaction flow where Vindicia was sending a non-tokenized payment method to PayU, which the current integration version does not support. This has been corrected to always use the tokenized payment method | | VIN-28138 | Subscribe Merchant Portal 2.0 - Server error when accessing campaign list | A server error was encountered when trying to view campaign list. 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.