Skip to main content
There are cultures and regions that use single names for individuals, also known as mononyms. When handling data entry and verification for applicants with single names, it’s crucial to follow a consistent and culturally sensitive approach. Below are the guidelines you should follow as part of your integration with FrankieOne.

​
Name Storage for Single Names

Store a single name in the FamilyName field. FamilyName is the only name field FrankieOne requires — GivenName is optional — and most downstream data sources also mandate a family name or “Last Name”, so this approach keeps the profile valid and gives the widest verification coverage.
  1. FamilyName Field (Preferred)
    • Store the single name in the FamilyName field, and use a hyphen (-) as the GivenName placeholder.
    • Ensure that any system rules that differentiate between given and family names are appropriately configured to accept a single name in this context.
  2. GivenName Field
    • Only use the GivenName field where a specific data source requires it, and keep FamilyName populated — a single name stored in GivenName with an empty FamilyName will be rejected.
  3. DisplayName for Renderings
    • Utilize the DisplayName field to reflect culturally appropriate renderings of the name. This is particularly important for systems that output names for display where a single name might be used differently than conventional given-family name structures.
Special Cases: Australian Document Verification Service (DVS)
  • Use a hyphen (-) as the first name placeholder.
  • Enter the single name into the FamilyName field.
  • A full stop (.) can be used as an alternative to a hyphen if preferred by the service providers during verification processes.

​
Tips for Implementation

  • Consistent Application: Ensure your application’s data entry and storage processes consistently apply these rules to prevent errors or discrepancies in user data.
  • Default to FamilyName: Store the single name in FamilyName unless a specific data source requires otherwise, and never leave FamilyName empty.
  • Configured Displays: Adjust how names are displayed in your application. Use DisplayName for areas where users or clients view a person’s name, ensuring natural or preferred readings.
If you require further assistance or need specific guidance on handling single names, do not hesitate to reach out to our developer support team.
For detailed technical specifications, please refer to our API Reference which includes full descriptions and examples for the individual name object. For the API-side implementation, including the Australian DVS formatting rules and which check types support single names, see Single Name Handling.