> ## 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.08 Release Production Release Date: August 29, 2023 * **[Vindicia Internal Notes for Subscribe 2023.08 Release](2023.08_tp_internalNotes)** ## Announcements ### Subscribe Merchant Portal 1.0 Deprecation Subscribe Merchant Portal 1.0 is planned for deprecation with September 2023 release. Merchants will need to migrate to Subscribe Merchant Portal 2.0 by that release. ### Access to HOA and PMT Static Files Via CDN In order to improve reliability and availability when accessing Subscribe's static content required for PMT (Payment Method Tokenization) and HOA (Hosted Order Automation), files are located at Content Delivery Network (CDN). Please change the URLs listed in your implementation as follows: | Existing URL | Change to | | - | - | | [https://secure.vindicia.com/ws/vindicia.js](https://secure.vindicia.com/ws/vindicia.js) | [https://cdn2.vindicia.com/ws/vindicia.js](https://cdn2.vindicia.com/ws/vindicia.js) | | [https://secure.vindicia.com/ws/vindicia-hosted-fields.js](https://secure.vindicia.com/ws/vindicia-hosted-fields.js) | [https://cdn2.vindicia.com/ws/vindicia-hosted-field.js](https://cdn2.vindicia.com/ws/vindicia-hosted-field.js) | | [https://secure.vindicia.com/ws/hosted-fields-ws-iframe.html](https://secure.vindicia.com/ws/hosted-fields-ws-iframe.html) | [https://cdn2.vindicia.com/ws/hosted-fields-ws-iframe.html](https://cdn2.vindicia.com/ws/hosted-fields-ws-iframe.html) | | [https://secure.vindicia.com/ws/imask.js](https://secure.vindicia.com/ws/imask.js) | [https://cdn2.vindicia.com/ws/imask.js](https://cdn2.vindicia.com/ws/imask.js) | Please make this change as soon as possible. **Important:** Existing URLs content will not be available after **Nov 1st, 2023**. ## Reports Features ### Chargeback Summary Report - Recurring Schedule Enhancement With this release, the **Chargeback Summary Report** can be run as a recurring report on a daily, weekly, and monthly schedule using Vindicia's Reports 2.0 data engine. (VIN-22250) ### Daily Schedule Frequency Support for Specific Recurring Reports With this release, the following reports can be run as recurring reports on a daily schedule using Vindicia's Reports 2.0 data engine: * **Churn Report** * **Projection Report** The **Campaign Redemption Report**, available using Vindicia's Reports 1.0, can now be run as a recurring report with a daily schedule option. (VIN-22949) ## Payments Features ### Cybersource Integration - Send Merchant Defined Data Based on Transaction Type With this release, Vindicia has added the ability to send Transaction Type data in Merchant Defined Data (MDD) to CyberSource. Merchants can use this data in different ways for example, apply their own fraud rules. The feature is enabled with a Name/Value Pair. Vindicia classifies Transactions as one of the following type values: * CardVerification * RealTimePayment * RecurringPayment To enable, contact Vindicia Client Technical Support. (VIN-22924) ### PayU Integration - Route Transactions Based on Transaction Type With this release, Vindicia identifies Transactions based on Transaction type data and routes it to different PayU Merchant Accounts. For example, verification and real-time Transactions are sent to one merchant account, and recurring Transactions are sent to another merchant account.​ Vindicia classifies Transactions as one of the following type values: * Credit Card Verification Transactions * Real-time Transactions * Recurring Transactions To enable, contact Vindicia Client Technical Support. (VIN-22923) ### WorldPay Integration - Tokenized Payments For Recurring Transactions With this release, Vindicia integrated with WorldPay's Tokenization API for recurring Transactions replacing the deprecated WorldPay's PayAsOrder API. With this new API, Vindicia creates a token for all recurring Transactions, including existing subscriptions. No change is required from merchants. (VIN-22257) ### Expanded Braintree Integration - Support for New PayPal Payment Method With this release, Vindicia's Braintree integration has been enhanced to support PayPal as a new payment method. PayPal via Braintree offers enhanced payment flows, including PayPal One Touch. Merchants who wish to accept Paypal payment method from their customers using PayPal through Braintree are required to use the Braintree Python SDK in their PayPal payment flow. For more details, see [Braintree PayPal](https://docs.vindicia.com/bundle/Subscribe_REST_API_Guide/page/topics/braintreePayPal_r.html) in the Subscribe REST API Guide. (BIMS-186) ## Bug Fixes The following issues were solved in this release: | Ticket | Title | Description | | - | - | - | | PORT-3011 | Subscribe Merchant Portal 2.0 - Email Note in Activity History Panel | An issue caused the text of the Activity History note to not appear in the pop-up for the Email Type in the Activity History paneof the Account Page. This issue has been fixed. | | PORT-3032 | Subscribe Merchant Portal 2.0 - Account Page Subscription Status and Billing State Not Displayed for Spanish Locale | When the Español (ES) Locale was selected in My Settings, the Subscription Status and Billing State values did not appear on the Account page. This issue has been fixed. | | PORT-3190 | Subscribe Merchant Portal 2.0 - Improved Display of Multiple Products in Subscription Items Panel | When a subscription included multiple products, more than one product could appear on the same line, making it difficult to identify products. This issue has been fixed. When a subscription has multiple products, each product now begins on a new line. | | PORT-3153 | Subscribe Merchant Portal 2.0 - Chargeback Received Date Not Appearing | The Received Date value did not appear in the Chargeback panel on the Transactions Detail page. This issue has been fixed. | | PORT-3309 | Subscribe Merchant Portal 2.0 - Transaction Search Results Unavailable for Same Day | When users searched for Transactions that occurred during the current day, no results were returned. This issue has been fixed. | | PORT-3356 | Duplicate "Attempt Succeeded" Push Notifications | Two "Attempt Succeeded" push notifications were received for the same transaction. This issue has been fixed. | | VIN-24000 | Incorrect Push Notification For Subscription Cancellation | An incorrect push notification when cancelling a subscription was received. This issue has been fixed. | | VIN-24107 | Fixed Date & Time fields incorrect formatting to ISO 8601 format | Subscriptions sometimes remained in a state of Processing due to incorrect parsing of their subscription IDs into ISO 8601 date format while generating push notifications. This issue was fixed. A new Name/Value Pair was created, do\_not\_reformat\_datetime, with a default of 0, to always convert any datetime fields in ISO 8601 in Push notifications. | | VIN-24217 | Global Collect Integration - Initial Scheme Transaction ID | The initial scheme transaction ID was not consistently sent to Global Collect to comply with the Stored Credentials framework. This issue has been fixed. | | VIN-25440 | dLocal Integration - 404 Response in Automatic Chargeback Feed via Vindicia Webhooks | A dLocal payment provider issue caused 404 responses in the Automatic Chargeback Feed via Vindicia webhooks. This issue has been fixed. | | VIN-26046 | Unintentional Cancellation When Resuming Paused Subscriptions | An issue caused subscriptions to expire and trigger unwanted cancellations when paused subscriptions were resumed and caused unintended cancellations of add-to-bundle PAIs. This issue has been fixed. | | VIN-26326 | Stripe Integration - Credit Card Validation Issue | For merchants using Stripe, when two validation transactions were performed for the same credit card, the second validation caused a disconnect between the Stripe Customer Identifier and the Stripe Card Identifier stored in Subscribe. 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.