{"title":"Periodic data reviews","category":"default","creationDate":1689926280,"content":"

Adyen occasionally requires your users to review and confirm that their data is up-to-date. You also can choose to proactively request the data review<\/a> for your user. You may want to do this if your user does not engage with your platform on a regular basis.<\/p>\n

After a data review is triggered, Adyen immediately runs verification checks on the existing data of the user. This data includes information about their legal entity\/legal arrangement and all entities associated with it, such as their ultimate beneficial owners (UBOs) and signatories. Adyen informs you through webhooks the review requirements for the user:<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

In both scenarios, Adyen provides a verification deadline in the webhook<\/a>. While the deadline is active, the user can continue using their capabilities that were allowed prior to the review request. If the user does not confirm the data and resolve any verification errors, their capabilities will be disallowed. The review is only considered finalized when the user has confirmed the data and<\/strong> resolved all verification errors.<\/p>\n

Step 1: Get updates when a review is required<\/h2>\n

Adyen informs you if a user data review is required through a balancePlatform.accountHolder.updated<\/a> webhook. The webhook contains the following information:<\/p>\n\n\n\n\n\n\n\n\n\n
Field<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
verificationStatus<\/a><\/td>\nSet to invalid<\/code><\/td>\n<\/tr>\n
allowed<\/a><\/td>\nRemains set to true<\/code><\/td>\n<\/tr>\n
verificationErrors<\/a><\/td>\nContains the verification error 3_10<\/strong> and message \"Review of data is required\".<\/td>\n<\/tr>\n
verificationDeadlines<\/a><\/td>\nThe date when the capability will be disallowed if the verification error is not resolved.<\/td>\n<\/tr>\n
remediatingActions<\/a><\/td>\nContains the remediating action 3_100<\/strong> and message \"Use \/legalEntities\/{id}\/confirmDataReview<\/code> to indicate that the data is confirmed\".<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

Note that the webhook contains the capabilities that will be disallowed if the user does not confirm that they have reviewed and updated their data.<\/p>\n<\/div>\n

\n <\/code-sample>\n<\/div>\n

Step 2 (optional): Proactively request a data review for your user<\/h2>\n
\n

This feature is only available if you are using onboarding v3 or v4.<\/p>\n<\/div>\n

To streamline the process, we recommend that you request the data review during a time when your user is active in your platform.<\/p>\n

Note that we may also require a data review outside of the scheduled period if there is a significant change to the user's information or risk level.<\/p>\n

If you request a data review when the user is not eligible, for example when:<\/p>\n