Who iDenfy is
iDenfy is an identity verification company founded in 2017. It verifies documents and faces with liveness detection, screens people and companies against sanctions, PEP and adverse media lists, verifies businesses and their owners, and adds fraud signals such as proxy detection.
It serves fintech, crypto, gaming and e-commerce businesses, among others, and by default processes and stores the data on servers in the EU. That mix is why it is one of the providers our KYC / AML module connects to.
What it does in your platform
KYC / AML
Verifies customers at sign-up with a document check and a liveness check, and can screen them against sanctions, PEP and adverse media lists as soon as the check is done. The result lands in the module's review queue, next to the checks of any other provider.
How the connection works
The KYC / AML module creates iDenfy sessions through its API and receives results by signed webhook. Your app only ever holds a token for one session, never iDenfy's keys.
A session is created
When a customer signs up, the module asks iDenfy for a verification session and receives an auth token, with an expiry time the module sets.
The SDK starts
Your app starts iDenfy's SDK with the token: the native SDKs on iOS and Android, and iDenfy's Flutter wrapper in our Flutter apps. On the web, the same flow runs in an iframe.
Document and liveness
The customer captures the document and passes the liveness check, and iDenfy analyses both, with a person reviewing where needed.
A signed webhook
The app's own callback only says the customer finished. The result comes by webhook, with an HMAC-SHA256 signature the module checks before reading it.
The decision
Approved customers go ahead and denied ones stop. Suspected cases wait in your team's review queue in the backoffice.
Next to other providers
iDenfy can run next to other verification providers in the module. Customers are routed by country or risk to the provider that covers them best, with a fallback if one is unavailable.
Whichever provider runs the check, the onboarding screens, the review queue and the audit trail stay the same. Adding iDenfy, or leaving it later, does not change your apps, and past checks stay linked to the provider that made them.
When iDenfy fits best
A strong fit when
- You want identity checks, AML screening and business verification from one provider.
- You want your verification data processed and stored in the EU by default.
- Your apps run on Flutter or React Native, and you want the provider's own wrapper for each.
Also worth a look
- A provider with deeper coverage in a market that matters to you, routed next to iDenfy for those customers.
- A provider you already have a contract with: it becomes a connector too.
How we get you live
The contract
We help you get your iDenfy account and contract in place, set up for your markets and your licence.
The flow
We configure the verification flow with you in iDenfy's dashboard: accepted documents and countries, AML screening and the extra steps your policy needs.
The keys
The API key pair and the webhook signing key go into your platform's secrets and nowhere else, so every result is proven to come from iDenfy.
A full test run
The whole flow runs with iDenfy's sandbox keys, which return test results for approved, denied and suspected cases, before your first real customer.
