Working with Names

At FrankieOne, we understand that names vary significantly across different cultures and regions. We continuously work to support diverse naming conventions and cultural nuances. If you have specific requirements not covered here, please contact us.

Name Structure

The Name object consists of the following fields:

Required (at least one)
  • Family name (Surname)
  • Given/First name
Optional
  • Other names (Middle name(s))
  • Display Name - Honorific

For complete technical specifications, refer to the PersonalNameObject in our API Reference.

  • FrankieOne supports UTF-8 characters by default
  • Handles names with diacritics (accents, umlauts)
  • Supports multiple character sets (ASCII, local characters)

Handling Multiple Character Sets (e.g., Chinese or Thai)

For names with both ASCII and local characters, support is contingent on the service providers being used to verify your customer’s details. There are two approaches to storing these names:

Name FieldsDisplayName Field (what’s seen in Portal)
Option 1English versionLocal version
Option 2Local versionEnglish version

For document-specific requirements, see Requirements & Additional Fields for ID Documents.

Many cultures use single names. You can:

  • Store in GivenName field (preferred)
  • Or store in FamilyName field if culturally appropriate
  • Use DisplayName for alternative renderings

Australian DVS Checks

For Australian Document Verification Service:

  • Use a hyphen (-) as first name
  • Put the single name in FamilyName
  • A full stop (.) can be used instead of hyphen when running through providers

Middle Name Matching (Australian Data Sources)

Pass Conditions
  • No middle name provided & none in database
  • Middle name provided & matches database
  • Driver’s License checks are more flexible
Fail Conditions
  • Middle name mismatch
  • Middle name provided but none in database
  • Database has middle name but none provided

For specific guidance on name handling or verification requirements, please contact our developer support team.

Built with