Workflows - frankieone

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/workflows

to see which workflows are enabled for your account.

Workflow Requirements Matrix

Workflow Pattern	Document	Address	DOB	Name
`*-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

AUS-Basic1V-IDOnly

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"
    }]
  }
}

AUS-Basic2V-TwoPlus

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

AUS-Basic2V-TwoPlusID

Description: Two+ data sources plus ID verificationRequirements:

Name (given + family)
Date of birth
Residential address
Identity document

Data Sources:

DVS
Credit bureaus
Electoral rolls

AUS-Basic3V-TwoPlus

Description: Three data source verificationRequirements:

Name (given + family)
Date of birth
Residential address

AUS-Basic3V-TwoPlusAge

Description: Three data sources with explicit age verificationRequirements:

Name (given + family)
Date of birth (age verified)
Residential address

Enhanced Tier

AUS-Advanced1V-IDOnly

Description: Enhanced ID verification with additional compliance checksRequirements:

Name (given + family)
Date of birth
Identity document

Additional Checks:

AML screening
PEP screening
Sanctions lists

AUS-Advanced3V-TwoPlusID

Description: Comprehensive verification with three sources plus IDRequirements:

Name (given + family)
Date of birth
Residential address
Identity document

Risk-Based Tier

AUS-Risk-CDD-Email-Phone

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

AUS-Risk-CDD-Email-Phone-Device-IP

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

NZL-Basic1V-OnePlusOne

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

USA-Basic1V-OnePlus

Description: Basic US identity verificationRequirements:

Name (given + family)
Date of birth
US address
SSN (optional, improves match rate)

USA-eIDExpress

Description: Express electronic identity verificationRequirements:

Name (given + family)
Date of birth

Global Workflows

GLB-IntlOnePlus

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.

GLB-AMLBasic

Description: AML screening only (no identity verification)Requirements:

Name (given + family)
Date of birth

Checks:

PEP screening
Sanctions lists
Watchlists

GLB-AMLMedia

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)

Global Address Verification (KYC Ruleset)

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)

GLB-DOBVerify (two_plus_age)

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": "DEFAULT",
  "workflowName": "GLB-DOBVerify"
}

Choosing the Right Workflow

Determine regulatory requirements

Understand the verification level required in your jurisdiction.

Assess available user data

Choose workflows that match the data you can reliably collect.

Balance UX and security

More checks increase assurance but add user friction.

Apply risk-based escalation

Use enhanced workflows for higher-risk users.

Use Case	Recommended Workflow
Low-risk onboarding	`AUS-Basic1V-IDOnly`
Regulated financial services	`AUS-Basic2V-TwoPlusID`
High-value accounts	`AUS-Advanced3V-TwoPlusID`
Fraud-prone industries	`AUS-Risk-CDD-Email-Phone-Device-IP`
AML screening only	`GLB-AMLBasic`

KYC

Documentation Index

​Understanding Workflows

​Workflow Requirements Matrix

​Australia Workflows

​Essential Tier

​Enhanced Tier

​Risk-Based Tier

​New Zealand Workflows

​United States Workflows

​Global Workflows

​Global Address Verification (Ruleset-Based)

​Global Age Verification (DOB Only)

​Choosing the Right Workflow

Understanding Workflows

Workflow Requirements Matrix

Australia Workflows

Essential Tier

Enhanced Tier

Risk-Based Tier

New Zealand Workflows

United States Workflows

Global Workflows

Global Address Verification (Ruleset-Based)

Global Age Verification (DOB Only)

Choosing the Right Workflow