AML Screening

AML screening is an optional verification step that checks the verified person against politically exposed persons (PEP), sanctions, and criminal/watchlists, and optionally against adverse media. It is configured per environment on Settings → AML in the dashboard.

Settings

All switches are per environment (Live / Sandbox), so you can try them in Sandbox without affecting your live flow.

Pricing

• PEP, sanctions, and watchlist screening is included in the standard price of a completed verification (€0.99). There is no extra charge.
• Adverse media is a paid add-on: +€0.15 per completed verification where it ran.
• Ongoing monitoring is €0.25 per monitored person per month. A person counts for a month if monitoring was active for any part of it.
• AML screening is off by default. Nothing is charged until you turn it on.

How it works

• Screening runs once per verification, and only when the verification would otherwise be approved (no failed checks).
• Matches are made by our screening providers. Hits whose date of birth does not match the verified person are filtered out.
• Any likely sanctions, PEP, criminal, or watchlist match moves the verification to manual_review. Your team reviews the matches in the dashboard (Clear or Confirm match) and then approves or rejects the verification.
• Approve is blocked while a match is undecided. The dashboard (and the approve endpoint) answers with a clear message until every match is cleared. A confirmed match cannot be approved at all: reject the verification instead.
• Adverse media is informational. Articles are reported in aml and shown in the dashboard, but they do not by themselves hold a verification and do not block approval.
• If screening cannot run (for example, the provider is unavailable), the verification also goes to manual_review, with aml.status set to error. An error does not block approval, so your team can check by hand, and the screening can be run again from the dashboard. A finished screening is never re-run.
• The end user is never told the reason; they see the standard manual-review screen.

Ongoing monitoring

Screening at verification time only tells you who someone was on that day. With ongoing monitoring on, Flonk keeps watching the people you have verified and tells you when one of them appears on a sanctions, PEP, or watchlist later.

How to enable it. Open Settings → AML, make sure AML screening is on, and turn on Ongoing monitoring. Monitoring starts for people whose verification completes after that; it is not applied to past verifications.

What happens on a new match.

• The verification stays completed. Its status does not change and the end user is not affected.

• You receive a verification.aml_alert webhook with the updated aml summary and the alert details.

• In the dashboard, the verification shows the new match with a New — found by monitoring badge and a reminder to review it. Open the verification and Clear or Confirm match, the same way as for a match found at verification time.

• The aml summary (matched_hits, categories, confirmed_hits, …) is updated to include the new match.

• If a changed record for a person you already reviewed shows up again (an update to a match you had cleared), the match is reopened as undecided and you get a new alert.

Stopping. Open the verification in the dashboard and press Stop monitoring. Monitoring also stops on its own when the verification is deleted or erased, rejected, or no longer completed. The current month is still charged. Turning Ongoing monitoring or AML screening off in Settings → AML stops monitoring for everyone currently monitored in that environment (Live or Sandbox); the dashboard asks you to confirm first.

Good to know.

• Monitoring does not run for test-mode sessions, and test mode is not charged.
• Trial verifications are monitored and billed like any other.
• If monitoring could not start for someone, the dashboard shows Could not start — not monitored. That person is not charged.

Pricing. €0.25 per monitored person per month; see Pricing.

Hit details are visible only in the dashboard. Webhooks carry the summary and the alert metadata, never names or list details.

aml object

The aml object describes the screening result. It is additive: no API version change is needed. In the verification.completed webhook it is present only when screening ran; in the REST response it is always present and is null when screening did not run.

{
  "aml": {
    "status": "hit",
    "provider": "dilisense",
    "checked_at": "2026-10-05T12:04:30.000Z",
    "total_hits": 3,
    "matched_hits": 1,
    "cleared_hits": 1,
    "confirmed_hits": 0,
    "categories": ["PEP"]
  }
}

The object is included in the verification.completed webhook (the manual_review verification.status_changed event does not carry it), and in GET /v1/verifications/{sessionId} as verification.aml (null when screening did not run). See Direct API.

Hit details (names, lists, articles) are visible only in the dashboard, not through the API or webhooks.

Common questions

Does screening run again after approval? Only if you turn on Ongoing monitoring (€0.25 per person per month). Without it, screening runs once per verification.

Does a monitoring alert change the verification status? No. The verification stays completed. You get a verification.aml_alert webhook and review the new match in the dashboard.

Why did a verification go to manual review? Open it in the dashboard: the AML section lists the matches. Your webhook only carries the summary in aml.

Does this change my webhook contract? No. aml is an optional, additive field.