Jumio ID verification
Use Jumio as an ID verification (KYC) provider in Hanzo IAM.
Jumio verifies government-issued IDs and supports KYC flows. Configure it as an ID Verification provider in Hanzo IAM.
Prerequisites
You need:
- A Jumio account with API access
- API credentials (Client ID and Client Secret)
- Your Jumio API endpoint URL
If you don't have a Jumio account, visit jumio.com to sign up.
Configuration
Get Jumio credentials
In the Jumio dashboard, open the API credentials section. Note your API Token (Client ID), API Secret (Client Secret), and API endpoint URL (e.g. https://api.jumio.com).
Create the provider in Hanzo IAM
Providers → Add. Set Category to ID Verification, Type to Jumio, and fill in:
- Client ID — Jumio API Token
- Client Secret — Jumio API Secret
- Endpoint — Jumio API URL
Save the provider.
Add to your application
Edit the application, add the Jumio provider in the Providers section, and save.
How Verification Works
When a user initiates identity verification:
- Hanzo IAM calls the Jumio API with the user's ID information
- Jumio initiates a verification transaction and returns a transaction reference
- The user completes the verification workflow (in production scenarios, this involves document upload and selfie capture)
- Jumio validates the submitted documents against the provided information
- Upon successful verification, the user's account is marked as verified in Hanzo IAM
Testing the Provider
You can test your Jumio configuration from the provider edit page:
- Ensure you have ID card information and real name filled in your user profile
- Navigate to the provider edit page
- Use the test functionality to verify that the provider is properly configured
- Check the response to confirm successful API communication
Important Notes
- Verification is a one-time process per user. Once verified, users cannot modify their identity information
- The current implementation initiates the verification workflow through Jumio's API v4
- For production deployments, ensure your Jumio account has sufficient API call quotas
- All verification attempts are logged for audit purposes
How is this guide?
Last updated on