Skip to main content
Production Release Date: April 23, 2024 Parent topic:Vindicia Subscribe - 2024.04 Release Notes

​
Subscribe Features

​
End of Trial and Pre-notification Push Notification optionally include Subscription Object for M1 customers

As part of the M1 carrier billing modifications, the existing invoice push notification End of Trial and Pre-notification can be optionally configured to include the subscription object and not just its minimized form. A merchant level Name-Value pair was added ReturnFullObjectInPush define value as 1 to enable (default is 0 - disabled) Additionally minor naming changes for the fields in Subscribe Merchant Portal 2.0 were made to ensure clarity of the field relevance for both emails and notifications. (VIN-28317)

​
Payment Features

​
Stripe Integration - Seamless Migration Option from Stripe Charge API to Stripe Intent API

From this release, Vindicia offers a seamless migration path for merchants using Stripe Charge API to Stripe Intent API, allowing easy access to Stripe Intent. With this migration to Stripe Intent, merchants now can validate their payment details, which was not the case in Stripe Charge. With this feature we have added an option whether CVV validation is needed for all Stripe Intent merchants (existing and new) as a Name-Value Pair. If the NVP is enabled, all the PMT or validation call will go through CVC validation. If successfully passed, we return the Payment Method ID to the merchant. If it fails, we simply return an error to the merchant, which will not include payment method id. The Success/pass CVC check will also allow merchant to create further payment using same payment method id. A fail check for payment method/CC won’t allow submitting an additional transaction with it. If the NVP is disabled, all validation/PMT call is performed as usual without CVC check and the merchant can make payments using the payment method id created. Name: StripeIntent:doCvcValidate Value: 0 - disabled, 1 - enabled Note: This feature is still undergoing testing and will be available for use soon. (VIN-28622)

​
Vantiv Litle Integration - Support for Merchant Advice Codes and Network Response Codes

With this release, support will be provided for MasterCard Merchant Advice Codes and Network Response codes as additional authorization codes available for merchants using XML 12. Note: We use Visa Network Response Codes mapping to Visa Category codes (available from Visa) to determine whether a particular network response code is categorized as hard (R) or soft (D) failure in our network_response_codes table. To take advantage of this new capability, merchants would need to enroll with Worldpay’s Issuer Insights via their account manager. To set the retry response codes priority, use Litle:auth_response_priority where
  • M is used for MAC codes
  • P is used for the (payment provider) auth codes
  • N is used for Network Response codes
For more details, see Litle internal configuration page. (VIN-29048)

​
Orbital Stratus Integration - Support for Visa Category Codes for Authorization Response

This feature was enabled on April 24th With this release, support will be provided for Visa category codes as an additional authorization response for merchants using Orbital Stratus payment provider To support Visa Category codes, the DTD version in the header of the SDK has been updated from PTI80 to PTI95. No new merchant configuration is necessary to support this functionality. (VIN-28934)

​
Response Auth Code Additions for Edgil, Braintree, Stripe, and Adyen

In this release, the following response codes were added:

​
Internal Fixes

The are no internal fixes.

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