Use Plaid's /identity_verification/retry endpoint to reset specific failed steps for a user without creating a duplicate identity verification record
domain: plaid.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Plaid webhook verification — the full failure-mode walkthrough related to plaid.com, checked against official docs, with linked verified routes.
Steps
Identify which specific steps failed (e.g., document upload, selfie) using the prior session's step-level status rather than retrying the whole flow blindly
Call /identity_verification/retry with the client_user_id, template_id, and the strategy specifying which steps to reset
Confirm that PII from the reset steps is cleared server-side, since a retry wipes prior data for the included steps rather than layering a new attempt on top
Note that the retry generates a new identity verification ID sharing the same client_user_id and template_id, and update your reconciliation logic to follow the new ID
For already-successful verifications, use a liveness retry to request a fresh selfie comparison against the original photo rather than a full re-verification
Cap retries at a low number (Plaid recommends starting around two) since higher retry allowances correlate with increased fraud attempts
Known gotchas
A retry is not additive — it clears the included steps' prior data, so partial-progress state from the original attempt is lost for those steps
Document capture already auto-retries up to three times within a single session for likely user-error failures, which is separate from and prior to an explicit /retry API call
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?