AWS Software / SaaS global

Jumio

Fraud Detection

Jumio needed to verify online identities accurately across thousands of document types and jurisdictions while detecting fraud, deepfakes, and screen attacks that are becoming more advanced as AI capabilities spread.

over 200 countries and territories
over 5,000 ID types
over 50 ML models involved in the IDV process

Reported impact

Business outcome

Jumio supports identity verification for more than 5,000 ID types across over 200 countries and territories and uses over 50 ML models to keep verification friction low for legitimate users while improving fraud defenses against deepfakes and other attacks.

  • Compliance
  • Customer Experience
  • Risk Reduction
  • Scalability

Solution

Jumio uses AWS to operate a global identity-verification platform that must distinguish legitimate users from fraud, deepfakes, and screen attacks across many document types and jurisdictions. Amazon SageMaker supports the machine-learning lifecycle for more than 50 models involved in Jumio’s verification pipeline, while Amazon Rekognition provides image-analysis capabilities used in secure, frictionless identity checks. Submitted identity documents and biometric evidence are evaluated through these AI and ML services so Jumio can assess liveness, detect manipulation, and return verification results that support customer onboarding, age checks, and other regulated transactions. Running the stack on AWS gives Jumio a scalable foundation for global data-sovereignty requirements and helps the company continuously adapt its fraud controls as generative AI makes attacks more sophisticated.

Data flow

Identity documents and user imagery are submitted into Jumio's verification workflow, analyzed by Amazon Rekognition and the ML models managed on Amazon SageMaker, and returned as identity-verification and anti-fraud decisions for customer transactions.

Solution architecture

2 components · 1 layer
  1. Compute
    • Amazon SageMaker Supports the more than 50 machine-learning models Jumio uses in its identity-verification pipeline.
    • Amazon Rekognition Provides image-analysis capabilities used in Jumio's identity verification experience.

Architecture clues

  • Combines liveness detection and anti-deepfake checks in the identity workflow.
  • Designed for regulated digital onboarding and transaction scenarios.
  • Supports data sovereignty compliance across more than 200 geographies.

Evidence from the source

In total, we work with over 5,000 ID types in over 200 countries and territories.
Learn how Jumio is using Amazon SageMaker and Amazon Rekognition to deliver a seamless and secure identity verification experience.
Our goal is to deliver solutions that convert as many legitimate customers as possible while identifying as much fraud as possible.
We have over 50 ML models involved in the IDV process, determining whether the people on-screen are live humans or some type of deepfake or screen attack.
Transparency Evidence & methodology 90/100 reference value · 90% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence90%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    Jumio customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/jumio-case-study/
    Source type
    Vendor-published customer story
    Published
    Feb 7, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. LeadIQ

    Jumio Corporation Employee Directory, Headcount & Staff | LeadIQ

    Independent secondary
    https://leadiq.com/c/jumio-corporation/5a1d8747240000240061537a/employee-directory

    The profile says, "Browse Jumio Corporation's employee directory of 617 employees.", which maps to Mid-market.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.