> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vindicia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vindicia Retain - 2025.11 Release Notes

***

Production Release Date: November 18, 2025

## What's New with Retain?

Vindicia Retain leverages Vindicia's proven payment recovery and smart retry functionality along with additional touch points that make it easier and faster to use.

What's coming bulletins and Release notes for Vindicia Retain will be provided monthly in the [Vindicia Knowledge Center](/portal/retainReleaseNotes/retainReleaseNotes) listing new features, functionality, and enhancements that will be made available.

## Retain REST APIs

No Retain REST API changes for this release.

## Payment Features

### Scope parameter support in OAuth 2.0 Token for push notifications

Vindicia Retain now supports obtaining OAuth 2.0 access tokens for secure delivery of push notifications to merchant systems.

When configured, Retain will:

1. **Request an OAuth 2.0 access token** from the merchant's authorization server using the `client_credentials` grant type.
2. **Include a configurable**`**scope**`**parameter** in the token request if required by the merchant's security policy.
3. **Use the returned access token** in the `Authorization: Bearer <token>` header when sending push notifications to the merchant's callback endpoint (for example, transaction status or retry updates).

This enhancement allows merchants who secure their callback APIs behind OAuth 2.0 to receive Retain notifications without relaxing their authentication requirements. If a `scope` is not configured, Retain will continue to perform token requests and push notifications as before.

## Announcements

### Moving Day to Vindicia IDP 2.0

Exciting news! In the coming weeks we will be upgrading our remaining merchants who are not using Multi-Factor Authorization to **Vindicia IDP 2.0**, our advanced Identity Provider experience for secure user authentication and login to **Retain Hub**.

After this change, Retain portal users will gain:

* Log in with advanced security measures such as **complex passwords**, **Multi-Factor Authentication**, and the **use of unique passwords**.
* User management self-enablement, allowing your Retain Super Users to add additional users to the Retain Portal.
* Merchant users can create their own passwords, and use authentication Apps or their email for Multi-Factor Authentication.
* Easy setup and access

**Note:** API access is not impacted and will not change.

Merchants will receive scheduling information via email.


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