> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Handling Single Name Applicants

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

Depending on the requirements and cultural appropriateness, you can store a single name in your system using one of the following approaches:

1. `GivenName `**Field**
   * Store the single name in the `GivenName` field to reflect it as the primary identifying name for the applicant.
   * This approach provides the most straightforward and intuitive handling for systems where a single name is supported.
2. `FamilyName `**Field (Preferred)**
   * Alternatively, store the single name in the `FamilyName` field if this aligns better with cultural or regulatory practices.
   * Ensure that any system rules that differentiate between given and family names are appropriately configured to accept a single name in this context.
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.

<Info>
  ##### 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.
</Info>

## 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.
* **Choose Appropriate Fields**: Select the field that best suits both your internal requirements and the cultural context of the applicant.
* **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](/docs/v1/api/kyc-api-endpoints/reference/status/status-check) which includes full descriptions and examples for the `PersonalNameObject`.