Working with Addresses
How to create and manage addresses using the FrankieOne KYC v2 API.
Overview of Addresses
Addresses are a key part of the KYC process, used to verify the identity of an entity and ensure authenticity. This guide provides an overview of how to create and manage addresses using the FrankieOne KYC v2 API.
Don't forget the Address ID
When updating an address, include the addressId
field. This is provided in the response message when you first add the address. You can retrieve the addressId
(and other IDs) by calling the GET /v2/{entityType}/{entityId}
API.
Country is Mandatory
The country
field is required and must be one of the ISO-3166-alpha-3 codes.
See here: List of ISO 3166 country codes
Address Types
Addresses can have various types. While optional, specifying the type is recommended for better processing and validation. The following types are commonly used:
RESIDENTIAL
: The primary address used to determine the country of residence and current address.
Note: The use ofRESIDENTIAL
for this purpose will be deprecated in the next major API version.POSTAL
: A mailing address, also used as the current residential address if noRESIDENTIAL
type is provided.
Street Address and the streetName
Field
Breaking down an address into its constituent parts is ideal, but the streetName
field is flexible. You can combine streetNumber
, streetName
, and streetType
into the streetName
field if necessary.
Break Down Address Fields
While combining fields is supported, breaking the address into individual fields yields the best matching results.
Structured Addresses
Using structured addresses is recommended for accuracy. Map the following fields 1-to-1: