Handle an Adyen for Platforms periodic KYC data review request end-to-end, including the proactive-review trigger
domain: docs.adyen.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Listen for a balancePlatform.accountHolder.updated webhook carrying verification error code 3_10 ("Review of data is required") with a remediatingActions entry pointing at /legalEntities/{id}/confirmDataReview
Optionally trigger the review proactively with POST /legalEntities/{id}/requestPeriodicReview while the user is active in your platform, instead of waiting for Adyen's own schedule
Prompt the user to review and, if needed, update their legal entity/UBO/signatory data before the verificationDeadlines cutoff in the webhook — capabilities remain allowed:true during this window
Once the user confirms, call POST /legalEntities/{id}/confirmDataReview and read the returned dataReviewedAt timestamp
Confirm resolution via another balancePlatform.accountHolder.updated webhook (or GET /accountHolders/{id}) showing verificationStatus valid before considering the review closed
Known gotchas
requestPeriodicReview returns a 422 if called more than one year before the next scheduled deadline, or less than 180 days after the last completed review — don't call it on every login just in case
The review is only finalized once the user has both confirmed the data AND resolved any verification errors — calling confirmDataReview alone does not close a review that still has open verificationErrors
Proactive review requests require onboarding v3 or v4; the requestPeriodicReview endpoint is not available on older onboarding versions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?