> ## 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 Internal Notes for 2024.04 Release Production Release Date: April 23, 2024 **Parent topic:**[Vindicia Subscribe - 2024.04 Release Notes](2024.04_tp_subscribeReleaseNotes) ## 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](https://docs.vindicia.com/bundle/b_retainMerchantConfiguration/page/topics/vantivConfiguration_r.html) 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: | Payment Provider | Response Code | Categorization | Description | Action | | - | - | - | - | - | | Edgil (1048) | 5012 | D (soft fail) | The transaction was declined. More information may be in the processor return code | Resend | | 5017 | D (soft fail) | An unexpected error from the processor was received. See the processor return code for more information. | Resend | | | 5029 | D (soft fail) | An account token is not allowed based on the account input type specified | Customer | | | 5032 | D (soft fail) | The transaction type specified was invalid | Resend | | | 5035 | D (soft fail) | The account number failed to pass the LUHN algorithm and is invalid | Resend | | | 5037 | D (soft fail) | The expiration date is invalid.,Resend,2,2, | Resend | | | BrainTree (1041) | 2105 | D (soft fail) | Cannot Authorize at this time (Life cycle) | Resend | | 2106 | D (soft fail) | Cannot Authorize at this time (policy) | Resend | | | 2107 | R (hard fail) | Card Not Activated | Fix | | | 2108 | R (hard fail) | Closed Card | Fix | | | 915200 | R (hard fail) | Failed to refund transaction | Fix | | | 915201 | D (soft fail) | Failed to refund transaction. Please try again at a later time | Resend | | | Paysafe (1055) | 3057 | R (hard fail) | Please tell cardholder to call the issuer – do not retry transaction | Fix | | 3073 | R (hard fail) | Your request has been declined due to closed customer account | Fix | | | 3074 | D (soft fail) | Issuer cannot approve at this time. Retry later, up to 10 times over 30 days | Resend | | | 3075 | D (soft fail) | Re-validate payment information prior to reattempt. Retry later, up to 10 times over 30 days | Resend | | | 3076 | D (soft fail) | Issuer cannot approve at this time. Please retry after 1 hour | Resend | | | 3077 | D (soft fail) | Issuer cannot approve at this time. Please retry after 24 hours. | Resend | | | 3078 | D (soft fail) | Issuer cannot approve at this time. Please retry after 2 days | Resend | | | 3079 | D (soft fail) | Issuer cannot approve at this time. Please retry after 4 days | Resend | | | 3080 | D (soft fail) | Issuer cannot approve at this time. Please retry after 6 days | Resend | | | 3081 | D (soft fail) | Issuer cannot approve at this time. Please retry after 8 days | Resend | | | 3082 | D (soft fail) | Issuer cannot approve at this time. Please retry after 10 days | Resend | | | 3087 | D (soft fail) | The transaction was not approved for an exemption. Please resubmit with Strong Customer Authentication present | Resend | | | 3088 | D (soft fail) | Transaction was not approved for an exemption, due to an amount limit. Please resubmit using Strong Customer Authentication or lower amount | Resend | | | 3089 | D (soft fail) | Exemptions can not be applied to this transaction type. Please re-submit your transaction without the exemption indicator. | Resend | | | 3090 | D (soft fail) | Your request has been declined because only one type of travel addendum data can be present | Resend | | | 3091 | D (soft fail) | Your request has been declined due to inability to verify PIN | Resend | | | 3092 | D (soft fail) | Your request has been declined due to no financial impact - original transaction already declined. | Resend | | | Stripe (1067) | card\_not\_supported | R (hard fail) | The card does not support this type of purchase | Fix | | invalid\_amount | D (soft fail) | The payment amount is invalid, or exceeds the amount that’s allowed | Resend | | | invalid\_request\_error | R (hard fail) | Invalid request. See message field for more information. | Fix | | | try\_again\_later | D (soft fail) | The card was declined for an unknown reason | Resend | | ## 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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.