Who Jumio is
Jumio is an identity verification company founded in 2010 and based in Sunnyvale, California. The Jumio Platform checks ID documents against a selfie with liveness detection, re-checks returning users, verifies proof of address and screens customers against sanctions, PEP and adverse media lists.
A rules engine and orchestration decide which checks run for whom. Financial services, gaming and crypto companies are among its customers, which is why it is one of the providers our KYC / AML module connects to.
What it does in your platform
KYC / AML
Checks each new customer's ID document against a selfie with liveness detection, through the Jumio workflow you chose for their country or risk. The result reaches the module's review queue with the rest of the customer's checks.
How the connection works
The KYC / AML module starts Jumio workflows through its REST API and reads the results from its retrieval API. Jumio's API credentials stay in your platform's secrets; your app only gets a token for one transaction.
An account is created
When a customer signs up, the module creates a Jumio account with the workflow you chose, and Jumio returns an authorisation token for this transaction, with a lifetime the module sets.
The SDK starts
Your app starts Jumio's SDK with the token and your data centre: the web SDK in the browser, the native SDKs on iOS and Android, and Jumio's Flutter plugin in our Flutter apps.
ID and selfie
The customer captures the document and a selfie, and Jumio runs the checks the workflow defines.
Jumio calls back
When the workflow finishes, Jumio sends a callback to the module from addresses the platform allowlists. It says the transaction is done; the details come next.
The result is retrieved
The module fetches the full result from Jumio's retrieval API and applies your rules. Clear cases pass, and the rest wait in your team's review queue.
Next to other providers
Jumio is one of several verification providers the module connects to. You can route customers by country or risk between Jumio and another provider, and fall back to the other one when a provider is down.
Whichever provider checks a customer, the onboarding screens, the review queue and the audit trail stay the same. Adding a provider next to Jumio, or leaving it later, does not change your apps, and past results stay in your records.
When Jumio fits best
A strong fit when
- You want the checks to follow a workflow chosen per country or risk, with liveness detection on every selfie.
- You want your customers verified in one data centre: Jumio's SDKs connect to one in the US, the EU or Singapore.
- You build on the web and in Flutter or React Native, and want the provider's own plugin for each.
Also worth a look
- A provider with deeper coverage in a market that matters to you, routed next to Jumio 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 Jumio account and contract in place, in the data centre and for the markets your licence covers.
The workflows
We choose the Jumio workflows with you: which checks run for which customers, and when a case goes to a person.
The keys
Jumio's API credentials go into your platform's secrets and nowhere else, and only Jumio's callback addresses can reach the callback endpoint.
A full test run
The whole flow runs end to end with test identities, from sign-up to the review queue, before your first real customer.
