> ## 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.09 Release

Production Release Date: September 27, 2022

**Parent topic:**[Vindicia MarketONE Subscribe - 2022.09 Release Notes](2022.09_tp_subscribeReleaseNotes)

## Subscribe Features

### External User Authentication - Integration with Connect (ULM) IdP

From this release, it is possible to integrate with Connect (ULM) in order to authenticate users there along with setting of complex passwords and multi-factor authentication.

For details, see the [wiki page](https://wiki.corp.aws.vindicia.com/x/vQEpBg) and [user journey slides](https://wiki.corp.aws.vindicia.com/x/XRApBg).

(VIN-16516)

### PUSH 2.0 - Event Timestamp Configuration

The event timestamp is part of the push message header and serves to show the time the event occurred and was sent.

In recent releases, for Push 2.0 we enabled push messages event timestamp to be displayed in the following format - "event\_timestamp":"2022-09-09 17:18:04.561936" where the timestamp displays the date and time including milliseconds.

```
date-fullyear"-"date-month"-"date-mday" "time-hour":"time-minute":"time-second"."time-secfrac"-"time-numoffset
```

Merchants that use Push 1.0 would be using the following timestamp format instead: "event\_timestamp":"2022-09-09T17:09:41.000000+0000

```
date-fullyear"-"date-month"-"date-mday" "time-hour":"time-minute":"time-second".000000-"time-numoffset
```

From this release, we support both timestamp formats, as configured in the merchant configuration files.

To enable the newer Push 2 Millisecond format, the following Name-Value Pair should be added and enabled (1) in the merchant config:

```
push_timestamp_milliseconds
```

Merchants that are not configured with this NVP, will continue to use the older event timestamp version as was used in Push 1.0

(VIN-17949)

## Payment Features

### Braintree and Card-on-File Support

From this release, the following are supported:

* Recurring and One time transactions (including void and refund)
* Supports credit cards and Venmo payment method
* Supports Card-on-File
* Retain support - Full auth and capture (level one)

Details of the Integration and configuration of the feature are available in the Implementation guide in the [wiki](https://wiki.corp.aws.vindicia.com/pages/viewpage.action?pageId=3735572\&preview=/3735572/103354476/Braintree_Venmo_implementation_guide_v0.1.docx)

**Note:** The integration uses Payments Service as a microservice. Merchants must be configured accordingly.

(VIN-15949)

### Ingenico Connect Integration Supports Hosted Pages Paypal Payment Method

Starting 2022.05 release, Vindicia integrated with Ingenico Connect Payment Provider. In this release support for Hosted pages Boleto Bancario was added.

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

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). I

**Note:** The integration uses Payments Service as a microservice. Merchants must be configured accordingly.

(BIMS-464)

## Retain Features

### Merchant-Specific Retain Dashboards

In this release new Retain Dashboards, providing valuable Merchant-Specific information, are available in the Retain Merchant Portal. [Watch the video for the new capabilities offered](https://vimeo.com/744006680/90c7f72014).

Retain Dashboards provide crucial data and analytics of your failed Transactions and uncover insights how these failed Transactions were healed and captured. They show actionable trends and provide the conversion business data of failed Transactions as well show the implication of the lost revenue recovery and customer retention to your business over time.To enable, contact Vindicia Client Technical Support .

(VIN-17770)

## Internal Fixes

The following issues were solved in this release:

| Ticket | Description |
| - | - |
| VIN-9147 | Transaction revenue recognition report will not include deleted transactionswhere if we are correcting transactions manually by deleting them, they will not be present in the report |
| VIN-14187 | Subscribe Pprtal 1.0 Invoice support and list MAP Merchant Accepted Payment Payment Method only |
| VIN-17218 | Refund stuck in processing status The issue in this bug was not reproducible. However, we have improved logging of the issue so when the next error occurs, it will be easier to debug |
| VIN-17532 | Merchant termination extract modificationThe merchant termination extract was modified to include 3DS data |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.