Skip to main content
Release Date: June 2, 2021

​
Announcements

This release includes the following announcements:

​
Subscribe Reports 1.0 Upcoming Deprecation Announcement

In July 2021, Vindicia plans to deprecate Reports 1.0 solution for both Subscribe Merchant Portal versions. From that point, the majority of the Subscribe Reports will be available exclusively from Report 2.0. Report 1.0 will then be deprecated.

​
Coming in June 2021 - REST API Enhancement to Compress Response in GZIP format

Effective for June 2021 release, Subscribe REST API will start honoring merchants header compression requests (Accept-Encoding). The response’s header will indicate content-encoding:gzip and the response body will be compressed in gzip compression format. Please prepare to implement unzipping for the incoming response.

​
Payment Features

This release includes the following new payment features and support:

​
Card on File Support

Starting this release, Vindicia has extended CIT/MIT parameters support for the following:
  • Ingenico GlobalCollect Processor Card-On-File Support (VIN-1606)

​
Visa Response Codes

Visa has re-allocated its response codes to four different categories as announced in the previous release. The end-purpose of this change is to maximize the efficiency of the retry process by defining clear response codes and behaviors. For more information, see Visa’s best practices guide. The following categories, each defining the retry policy, were defined:
  • Category 1: Issuer will never approve transaction (reattempt not allowed)
  • Category 2: Issuer cannot approve the transaction at this time (reattempt allowed)
  • Category 3: Data Quality concern (re-validate data prior to reattempt)
  • Category 4: Generic response code (reattempt allowed) In addition, when re-attempt is allowed, there is a limitation of 15 attempts over 30 days.
Merchants must revise their current retry policy to ensure that the 15 retries within 30 days limitation is avoided. A fine of 10c/transaction is expected. Vindicia has updated the system behavior to enforce these changes by doing the following:
  • Vindicia has updated the retry logic of the Visa error codes for all corresponding payment processor codes, and mapped soft or hard failures in accordance with these new definitions. This is expected to improve authorization and capture rates.
  • Vindicia has reviewed merchant configurations and updated where previously hard failures codes were re-mapped to soft failures.
(VIN-9274)

​
Purchase Return (Refund) Authorization Mandate

Visa and Mastercard have issued mandate directives requiring merchants to request authorization for every cardholder refund or return transaction. New response codes have been added by the card issuers to support this initiative. Payment Processors handle this change by providing their own response codes to indicate the refund state. Vindicia is enforcing this change in its system behavior by displaying the response codes according to the received responses and proceeding in the authorization flow accordingly. (VIN-9767)

​
Subscribe Features

This release includes the following new Subscribe features:

​
REST API - Metadata (custom data) Name-Value Pairs Enhancement

Name-Value pairs are metadata fields that hold customized merchant-specific data. The following Subscribe objects have been updated to support up to 1024 characters for the Value field of the Name-Value pairs in the Subscribe REST API. The Name field continues to support up to 256 characters:
  • Account
  • Billing Plans
  • Chargebacks
  • Events
  • Invoices
  • Payment Methods
  • Products
  • Rate Plans
  • Refunds
  • Season Sets
  • Subscriptions
  • Transactions
Subscribe Merchant Portal 2.0 support for the feature will be available in future releases. (VIN-9960)

​
Scheduling Reports Support in Reports 2.0​

From this release, it is possible to schedule reports through Subscribe Merchant Portal 1.0 using Report 2.0 functionality. Existing schedules (of Reports 1.0) were not migrated to enable merchants to test this feature. Starting July 2021, with Reports 1.0 deprecation (as announced above), Vindicia will stop supporting schedules that existed for Report 1.0. For seamless reporting continuity, Vindicia recommends scheduling the required reports using the Reports 2.0 functionality.​ (VIN-8413)

​
Bug Fixes

​
Known Issues

This release includes the following known issues:
  • Portal 2.0 - If a Portal session times out when multiple browser tabs are open, only one tab refreshes with the new log in. Other open tabs do not automatically refresh and their menu items are not displayed. While this issue is being addressed, manual refresh of the open tabs is required as a workaround.
  • Large data reports fail to display in Reports 2.0. There is a timeout issue when generating and fetching large reports. As a temporary workaround, please schedule large sized reports rather than running them on demand and set SFTP as the delivery method.