Who Veriff is
Veriff is an identity verification company founded in Estonia in 2015 and based in Tallinn. Its platform verifies identity documents and faces, re-checks returning users with a selfie, verifies proof of address and estimates age.
It also screens people against PEP, sanctions and adverse media lists. Financial services, e-commerce, gaming and HR platforms are among the businesses it serves, which 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 an ID document and a liveness selfie, and adds PEP, sanctions and adverse media screening where your licence asks for it. Veriff's decision, with its reason, lands in the module's review queue.
How the connection works
The KYC / AML module creates verification sessions through Veriff's API and receives Veriff's decisions by webhook. Your app only gets the session URL for the customer in front of it, never Veriff's keys.
A session is created
When a customer signs up, the module creates a Veriff session with their details and gets back a session URL that belongs to this customer only.
The flow opens
Your app opens Veriff's flow with that URL: the web SDK in the browser, the native SDKs on iOS and Android, and Veriff's Flutter plugin in our Flutter apps.
Document and selfie
Guided by Veriff's screens, the customer photographs the document and takes a selfie, and Veriff checks both.
The decision arrives
Veriff posts its decision as soon as it is made, signed with your integration's shared secret, and the module checks the signature before reading it.
Screening results
Where screening is part of the check, a separate watchlist screening webhook brings the PEP and sanctions results to the module.
Your team decides
Approved customers go ahead and declined ones stop. Anything else, such as a possible screening match, waits in your team's review queue in the backoffice.
Next to other providers
Veriff can run next to other verification providers in the module. Customers can be routed by country or risk to the provider that covers them best, with another one as a fallback if a provider is unavailable.
Your onboarding screens, your review queue and your audit trail stay in the module whichever provider runs the check. Adding a provider next to Veriff, or moving away from it later, does not change your app, and past decisions stay linked to the provider that made them.
When Veriff fits best
A strong fit when
- You want identity checks and AML screening from one provider, inside your own app.
- Your customers sign up on the web and on mobile, and you want the provider's own SDK on both, Flutter included.
- You run financial services, gaming or e-commerce, industries Veriff serves.
Also worth a look
- A provider with deeper coverage in a market that matters to you, routed next to Veriff for those customers.
- A dedicated screening provider, if your compliance team wants its own source of sanctions and PEP data.
How we get you live
The contract
We help you get your Veriff account and contract in place, set up for your markets and your licence.
The checks
We configure your Veriff integration with you: which documents are accepted, whether screening runs, and which webhooks the module receives.
The keys
The API key and the shared secret go into your platform's secrets and nowhere else, so every decision is proven to come from Veriff.
A full test run
The whole flow runs on a Veriff test integration, from sign-up to the review queue, before your first real customer.
