Single Name Handling

Overview

In many cultures, it is common for an individual to have only a single name (a mononym). The FrankieOne platform supports these cases, but correct data mapping is crucial as requirements vary significantly between different types of verification checks.

This guide will walk you through the correct API implementation for handling single-name applicants to ensure successful verification and global compliance.

General API Implementation

The recommended approach for submitting a single name via the API is to populate the familyName and use a placeholder for the givenName.

Why this approach? Many downstream data sources have a mandatory requirement for a familyName or “Last Name” field. Placing the single name here ensures the highest compatibility across our network of data sources.

{
  "individual": {
    "name": {
      "givenName": "-",
      "familyName": "Sukarno"
    }
  }
}

While the API can also accept the single name in givenName and a hyphen in familyName, the critical factor is ensuring the format meets the requirements of the specific end data source you are checking against.

Verification Compatibility

Support for single-name verification is not universal. It depends entirely on the rules of the end data source. Submitting a single name to an unsupported service will result in a “No Match” or an error.

Verification Type	Single Name Support	Notes
Credit Bureau Checks	⚠️ Partial	Support for single names varies. While some checks will succeed, others require both a first and last name and will fail.
Government ID Checks (DVS)	✅ Yes (Conditional)	Support depends on the document type. See the detailed DVS table below for specific formatting rules.
Australian Electoral Roll Checks	❌ No	This service requires both a first and last name and will not process a single-name entry.
Superannuation & Payroll Checks	❌ No	These services have mandatory first and last name fields with no available workaround.
Other KYC & AML Checks	Varies	Compatibility depends on the specific check and region. We recommend following the standard `familyName` + hyphenated `givenName` format.

​Overview

​General API Implementation

​Verification Compatibility

Overview

General API Implementation

Verification Compatibility