Skip to main content

Understanding Workflows

Workflows define the verification checks performed on an individual. Different workflows have different data requirements and query different data sources depending on regulatory and risk needs.
Use GET /v2/workflowsto see which workflows are enabled for your account.

Workflow Requirements Matrix

Workflow PatternDocumentAddressDOBName
*-IDOnly
*-TwoPlus
*-TwoPlusID
*-OnePlusOne
*-AddressVerify
*-AgeVerify
Submitting insufficient data for a workflow will result in a 400 Bad Request error or BAD_DATA issues in the verification result.For example if you use an *-IDOnly workflow such as AUS-Basic1V-IDOnly and do not provide a government ID you will get a 400 Bad Request error.

Australia Workflows

Essential Tier

Description: Single government ID verification via DVSRequirements:
  • Name (given + family)
  • Date of birth
  • Identity document (passport, driver’s license, or national ID)
Data Sources:
  • Australian Document Verification Service (DVS)
{
  "documents": {
    "IDENTITY": [{
      "type": "PASSPORT",
      "country": "AUS",
      "primaryIdentifier": "PA1234567"
    }]
  }
}
Description: Two or more data source verification (no ID required)Requirements:
  • Name (given + family)
  • Date of birth
  • Residential address
Data Sources:
  • Credit bureaus
  • Electoral rolls
  • Public records
Description: Two+ data sources plus ID verificationRequirements:
  • Name (given + family)
  • Date of birth
  • Residential address
  • Identity document
Data Sources:
  • DVS
  • Credit bureaus
  • Electoral rolls
Description: Three data source verificationRequirements:
  • Name (given + family)
  • Date of birth
  • Residential address
Description: Three data sources with explicit age verificationRequirements:
  • Name (given + family)
  • Date of birth (age verified)
  • Residential address

Enhanced Tier

Description: Enhanced ID verification with additional compliance checksRequirements:
  • Name (given + family)
  • Date of birth
  • Identity document
Additional Checks:
  • AML screening
  • PEP screening
  • Sanctions lists
Description: Comprehensive verification with three sources plus IDRequirements:
  • Name (given + family)
  • Date of birth
  • Residential address
  • Identity document

Risk-Based Tier

Description: Customer Due Diligence with contact risk assessmentRequirements:
  • Name (given + family)
  • Date of birth
  • Email address
  • Phone number
Fraud Signals:
  • Email risk scoring
  • Phone risk indicators
Description: Full risk assessment including device and network intelligenceRequirements:
  • All CDD requirements
  • Device fingerprint (via OneSDK)
  • IP address
Fraud Signals:
  • Email risk
  • Phone risk
  • Device risk
  • IP geolocation

New Zealand Workflows

Description: One primary plus one secondary source verificationRequirements:
  • Name (given + family)
  • Date of birth
  • Identity document (NZ passport or driver’s license)

United States Workflows

Description: Basic US identity verificationRequirements:
  • Name (given + family)
  • Date of birth
  • US address
  • SSN (optional, improves match rate)
Description: Express electronic identity verificationRequirements:
  • Name (given + family)
  • Date of birth

Global Workflows

Description: International verification using country-specific data sourcesRequirements:
  • Name (given + family)
  • Date of birth
  • Country of residence
Coverage: Contact FrankieOne for supported countries and data sources.
Description: AML screening only (no identity verification)Requirements:
  • Name (given + family)
  • Date of birth
Checks:
  • PEP screening
  • Sanctions lists
  • Watchlists
Description: AML screening with adverse media monitoringRequirements:
  • Name (given + family)
  • Date of birth
Checks:
  • PEP screening
  • Sanctions lists
  • Adverse media

Global Address Verification (Ruleset-Based)

Description:
Verifies a residential address using country-specific data sources and fuzzy matching rules, without requiring full identity verification.
Typical Crypto Use Cases:
  • Wallet creation
  • Tiered onboarding (Tier 0 / Tier 1)
  • Jurisdiction eligibility checks
  • Proof-of-address prior to higher transaction limits
Requirements:
  • Residential address
  • Country of residence
Supported Address Fields:
  • Street number
  • Street name
  • Locality / city
  • Subdivision / state (where applicable)
  • Postal code
  • Country
Verification Capabilities:
  • Address normalization
  • Partial and fuzzy matching across providers
  • Country-specific address formats
  • Multiple provider corroboration
Does NOT require:
  • Government ID
  • Name matching
  • Date of birth verification
Optional Add-ons:
  • AML screening via GLB-AMLBasic or GLB-AMLMedia
  • Risk-based escalation to identity verification if required
{
  "addresses": [
    {
      "type": "RESIDENTIAL",
      "typeDescription": "Home Address",
      "format": "standard",
      "streetNumber": "1200",
      "streetName": "SW Orleans",
      "locality": "Topeka",
      "district": "",
      "subdivision": "KS",
      "country": "USA",
      "postalCode": "66604",
      "status": "CURRENT"
    }
  ]
}

Global Age Verification (DOB Only)

Description:
Standalone date-of-birth verification against trusted data sources.
This workflow verifies age only and does not perform full identity verification.
Use cases:
  • Age-gated products (gaming, content platforms)
  • Lightweight eligibility checks
  • Pre-KYC or step-up verification flows
  • Jurisdictional age compliance without ID collection
Requirements:
  • Given name
  • Family name
  • Date of birth
  • Country of residence
Verification Behavior:
  • DOB is checked against two or more independent data sources
  • No document upload required
  • No biometric or identity matching performed
  • Returns age confidence only (not identity confidence)
Typical Outcomes:
  • PASS — Date of birth confidently verified
  • REVIEW — Partial match or insufficient confidence
  • FAIL — Date of birth could not be verified
Risk Factors Evaluated:
  • Entity Age
  • Jurisdiction Risk
  • Data Consistency Across Sources
Limitations:
  • Does not verify identity
  • Does not satisfy KYC or AML requirements on its own
  • Should be paired with a KYC workflow if identity assurance is required
Recommended Pairings:
  • Identity verification: GLB-IntlOnePlus
  • Fraud signals (optional): Device and IP risk checks
{
  "individual": {
    "name": {
        "familyName": "YOUNGTEN",
        "middleName": "J",
        "givenName": "Oliver"
    },
    "dateOfBirth": {
        "day": "15",
        "month": "06",
        "year": "2015"
    },
    "addresses": [
      {
        "type": "RESIDENTIAL",
        "country": "AUS"
      }
    ]
  },
  "serviceName": "KYC",
  "workflowName": "GLB-DOBVerify"
}

Choosing the Right Workflow

1

Determine regulatory requirements

Understand the verification level required in your jurisdiction.
2

Assess available user data

Choose workflows that match the data you can reliably collect.
3

Balance UX and security

More checks increase assurance but add user friction.
4

Apply risk-based escalation

Use enhanced workflows for higher-risk users.
Use CaseRecommended Workflow
Low-risk onboardingAUS-Basic1V-IDOnly
Regulated financial servicesAUS-Basic2V-TwoPlusID
High-value accountsAUS-Advanced3V-TwoPlusID
Fraud-prone industriesAUS-Risk-CDD-Email-Phone-Device-IP
AML screening onlyGLB-AMLBasic