> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/changelog/2024/15-may-identity-fraud-check-and-eid-capabilities.md).

# 15 May: Identity Fraud & eID

Identity Fraud Check and eID Capabilities. Product updates for identity fraud checks, Norway BankID, active NFC authentication, AML coverage, and portal integration tooling.

This release introduced a new fraud-focused check and expanded electronic ID verification options, while improving coverage across our services.

### **New features**

* [Identity Fraud Check](/documentation/product-guides/identity-verification/identity-fraud-check.md) was added, verifying customer details against multiple authoritative sources and analyzing activity and fraud patterns within the UK to better detect fraudulent behavior.
* [eID Check](/documentation/product-guides/identity-verification/eid-check.md) for Norway BankID was made available as an invitation-only feature, enabling verification directly through BankID for onboarding.
* [Active authentication](/documentation/product-guides/identity-verification/document-check/nfc-chip-verification.md) was introduced for NFC-enabled ID documents in the Mobile SDKs, complementing passive checks and enhancing security by detecting cloned or tampered chips.

### **Improvements**

* [AML Screening coverage](/documentation/product-guides/watchlist-pep-and-adverse-media/aml-screening-check/lists-included.md) was expanded with additional sanctions, watchlists, and enforcement sources across South America and Asia.
* [Multi-Bureau Checks coverage](/documentation/product-guides/identity-verification/multi-bureau-check/service-coverage.md) expanded to include Austria, Ghana, and Switzerland.
* The [Integration Assistant](https://portal.complycube.com/developers) on the Web Portal was enhanced to include an advanced option for pure API integrations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/changelog/2024/15-may-identity-fraud-check-and-eid-capabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.