Skip to main content

Quick Reference Card


1. Complete Endpoint Reference

Individual Management

Workflow Operations

System


2. Field Enumerations (Complete)

Document Types

Document Classes

Address Types

Full address type options, note some are for KYB such as OFFICE_LOCALITY Available options: OTHER, RESIDENTIAL, BUSINESS, POSTAL, REGISTERED_OFFICE, PLACE_OF_BUSINESS, OFFICIAL_CORRESPONDANCE, PLACE_OF_BIRTH, OFFICE_LOCALITY, AUTHORITATIVE_RESIDENTIAL

Address Status

Phone Types

Email Types

Gender Values

Name Types (for alternateNames)


3. Workflow Response Enumerations

Workflow Execution State

Workflow Status (Overall Result)

Service Profile State

Risk Levels


4. Issue Categories & Severities

Issue Categories

Issue Severities

Common Issue Codes

Full category and issue code mapping with severity and meaning

Risk Factors

FrankieOne calculates an overall risk assessment by evaluating multiple risk factors across identity, AML, fraud, behavior, and workflow integrity. Each factor contributes to the final risk level (LOW, MEDIUM, HIGH, UNACCEPTABLE) returned in workflow results.
All risk factors, weightings, thresholds, and scoring are configurable per customer. The examples below illustrate typical categories and signals, not fixed scoring rules.

Core Risk Factors (Overview)

For full risk view, see:
Assessing Risk

Risk Categories & Signals

Entity Profile Risk


AML & Screening Risk


Identity Verification (IDV) Risk

These factors influence confidence in document authenticity and biometric matching.

Onboarding Fraud Risk


Behavioral & Integrity Risk


Workflow Logic Risk


Custom Risk Factors

Custom attributes allow customers to inject domain-specific risk signals into workflows.

How Risk Is Used

  • Risk factors are evaluated during workflow execution
  • Results contribute to:
    • riskLevel
    • riskScore
    • Issue categories and severities
  • Outcomes may trigger:
    • Step-up verification
    • Manual review
    • Workflow termination
Risk scoring models vary by jurisdiction, industry, and customer configuration. Always validate behavior in UAT before production rollout.

6. OneSDK Events (Complete)

Lifecycle Events

Result Events

Form Events

Document Events

Biometric Events

Error Events

Catch-All


7. Error Codes

Authentication Errors (AUTH-*)

Validation Errors (API-*)

System Errors (SYS-*)

Workflow Errors (WF-*)


8. Workflow Requirements Matrix

Document Requirements by Workflow Type

IDOnly Workflows:
TwoPlus Workflows: Address line 1 can be provided in street name

9. Complete Request/Response Examples

Create Individual + Execute Workflow

Request:
Response (201 Created):

Execute Workflow

Request:
Response:

Get Results

Request:
Response (workflow completed):

10. Webhook Payload Schemas

WorkflowComplete Event

EntityRiskChanged Event


11. Australian Document Identifiers

Driver’s License Format by State

Licence Number Formats Card Number Formats

Passport Format

  • Australian: 2 letters + 7 digits (e.g., PA1234567)
  • International: Varies by country

Medicare Card

  • 10 digits + IRN (1 digit)
  • Format: XXXX XXXXX X/X

12. Testing in UAT

Test Data Behavior

  • UAT environment connects to test data sources
  • Fake document numbers will return NOT_FOUND or BAD_DATA_ID
  • Use FrankieOne-provided test credentials for realistic responses

Expected Test Results


13. Rate Limiting

Headers (when rate limited)

Best Practices

  1. Implement exponential backoff
  2. Cache workflow list (changes infrequently)
  3. Batch operations where possible
  4. Use webhooks instead of polling

14. SDK Installation

NPM

CDN

Initialization

OpenAPI & Swagger Specification

The OpenAPI specifications are published as separate resources.
Use the KYC v2 spec for individual, workflow, document, and results APIs.
Use the Core v2 spec for shared operations such as workflow discovery and audit access.

Remaining Gaps (Contact Support)