Ongoing AML monitoring

YeboVerify re-screens people, companies and directors after successful source refreshes. Workers drain pending checks in bounded batches; the console Monitoring page shows pending work, incomplete coverage and source health.

Use GET /v1/monitoring from your backend with your business API key. Live and sandbox records remain separate.

A changed AML result or coverage failure arrives through the existing signed verification.completed webhook. Read the aml result together with monitoring.lastSuccessfulScreenAt, monitoring.lastAttemptedAt and monitoring.error. Verify the webhook signature and deduplicate its event ID. There is no aml.match event.

A failed re-screen is incomplete coverage, never a fresh clearance. Recovery clears the coverage error but does not approve an identity that still needs review. Your system owns account restrictions and any banking action.

Source refreshes run daily, with monitoring workers scheduled every five minutes. Book size and retries affect completion time; pending counts and timestamps show actual progress.