What's new: Periodic review

What’s new

In order to comply with our AML (LCB-FT) obligations, end users will be required, at regular intervals, to review their personal data and update it if any changes have occurred.

If the information is updated within the required timeframe, the accounts will remain fully operational.
However, if an end user fails to update their data, their account will be progressively restricted and may ultimately be closed.

This feature therefore introduces several new elements:

New actions are required from end users
Account impacts may occur in the absence of updates, ranging from temporary restrictions to full account closure

Why is this a breaking change?

This feature involves new developments and new user journeys on your side. When Xpollens notifies you of a review request, you will need to ask the end user to update their information and send the necessary reminders to prevent their account from being blocked. Any changes made by the end user must be transmitted to Xpollens.

Furthermore, this feature is closely tied to the implementation of a user relationship lifecycle, through which the user’s status at Xpollens will be reflected. Previously, only the account status evolved toward closure, whereas now the user status itself will be taken into account.

Impact

1- New API to confirm the review is complete: POST /users/appUserId/periodic-review

2- New webhook PeriodicReviewChanged to track periodic review requests, deadlines, and updates.

Prerequesites

Webhook UserCreatedOrUpdated for user relation status update

Webhook 45 for account status updates

Additional information

Additional information	Yes/No
Upsell	No