> ## 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 2022.05 Release Production Release Date: May 31, 2022 **Parent topic:**[Vindicia MarketONE Subscribe - 2022.05 Release Notes](2022.05_tp_subscribeReleaseNotes) ## Payment Features ### Ingenico Connect Integration Starting this release, Vindicia is integrated with Ingenico Connect Payment Provider. Ingenico Connect operates in many countries and supports different currencies. For details, see the [Ingenico Connect list](https://epayments.developer-ingenico.com/payment-methods/view-by-country/). **Note:** This is a new integration with Ingenico Connect. It is currently provided in addition to Vindicia's Ingenico Global Collect Integration. Ingenico Global Collect are planning to deprecate the Global Collect API in the future and merchants will be required to move to the Ingenico Connect interface. The supported features are listed in the [2022.05 external release note](2022.05_tp_subscribeReleaseNotes). Details of the Integration and configuration of the feature are available in the Implementation guide and slide deliverables in the [Ingenico Connect wiki](https://wiki.corp.aws.vindicia.com/x/aJBSBQ). Ingenico Daily reports, providing the final status of the Transactions, is also explained there. **Note:** The integration uses Payments Service as a microservice. Merchants must be configured accordingly. (BIMS-176) ### Upgrade of the Braintree Integration Including Venmo Payment Method Support From this release, Vindicia has integrated with the updated Braintree Payment Provider interface. As part of the integration, support for the Venmo payment method has been added. Merchants using this Braintree Integration can now accept payment directly from their customers' Venmo accounts. **Note:** The integration uses Payments Service as a microservice. Merchants must be configured accordingly. (BIMS-164,BIMS-162) ### Response Codes Updates The following changes were made to different Payment Providers response codes: * Cybersource response codes '201', '208' '231' were changed from D (soft fail) to R (hard fail). VIN-14872 (Fix was removed from 2022.05 release- these codes are still soft fail in 2022.05 release) * Payment Provider Decline (soft fail) response codes that were associated with a **fix** action have been updated. Now the action has been renamed to **Resend**. Merchant error messages will state that the Transaction can be sent back anytime. VIN- 14873 * Global Collect 480023 response code was added to the database as response type R (hard fail). VIN-15246 * Global Collect 430025 response code was added to the database as response type D (soft fail) with name AUTHORIZATION FAILED - SCA IS REQUIRED and resend action type. VIN-16001 * Global Collect 300 response code was changed to S (success) instead of D (soft fail). VIN-15852 (VIN-14869) ### External Billing Configuration Controlling Inclusion of Zero Currency Transactions in Charge Files In this release, a configuration option has been added for External Billing payment provider that allows merchants to choose whether the Transaction charges upload includes zero currency Transactions or excludes them. The configuration option is included in Vindicia's External Billing configuration ( Portal 1.0) the field is called **Exclude Zero Transaction** and is set to 0 (includes zero currency Transactions) Change to 1 to exclude these transactions. (VIN-14234) ### Adyen Integration- Providing Custom Data Fields Enhancement Vindicia's Adyen integration was previously released. In this release, Vindicia is providing additional support for merchant data via using custom data fields. Additionally, the Adyen card-on-file (CIT/MIT) IDs returned on a Transaction response can be returned as custom data (Name-Value pair). Additionally, the Adyen card-on-file (CIT/MIT) IDs returned on a Transaction response can be returned as custom data (Name-Value pair). The generic implementation allows merchants to use the fields they define in their Adyen instance using the structure **adyen:merchantDefinedData:\ = \** The following names will be sent to Adyen: * sap\_order * store\_order * partnerSolutionID (VIN-13170, VIN-15014, VIN-15013) ### Bank of America Integration Code and database changes have been made and incorporated for Bank of America payment provider integration. The feature itself will be released in future releases. (VIN-13344) ## Internal Fixes This release has the following fix input: | Ticket | Description | | - | - | | VIN-15819 | There are several currencies that do not support decimals. In those cases, Subscribe was passing the amount to the processor with additional digits. Adyen processes these type of currencies differently. The issue was fixed according to the Adyen approach.The following currencies were addressed: - CLP' => '0' - 'GNF' => '0' - 'HUF' => '0' - 'IDR' => '0' - 'ISK' => '0' - 'JPY' => '0' - 'KPW' => '0' - 'PYG' => '0' - 'XAF' => '0' - 'XOF' => '0' - 'XPF' => '0' | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.