confirmOnZimpler

Instead of forcing a user to manually type out their legal details (which often leads to typos and failed verification later), the platform extracts this verified identity data directly from a third-party provider. It can be used in regions below - Denmark, Estonia, Finland, Sweden, Brazil.

Documentation

Try it now

Request parameters:

Name	Description	Type	Values	Default	Source

token	This is the unique transaction identifier, session ID, or authorization token generated when the Zimpler order was first created.	string	-	-	MethodgetZimplerAccessToken Key from response`id`

This method is usually used with these methods:

getZimplerAccessToken

Call example:
JavaScriptReact HookFlutter

confirmOnZimpler({
  token: 'asdasdas132123123'
})

Response examples:
SuccessError

{
  Region: 'Yerevan',
  FirstName: 'Bell',
  LastName: 'Beith',
  BirthDate: '1980-08-23',
  Address: 'address_line',
  PersonalId: '2345928345'
}

Response parameters:

Name	Description	Type	Values

Region	The administrative division, state, or province of the user's residence.	string	-
FirstName	The legal given name of the individual.	string	-
LastName	The legal family name/surname of the individual.	string	-
BirthDate	The user's date of birth, formatted in standard ISO 8601 (YYYY-MM-DD)	string	-
Address	The physical street address or location line of the user.	string	-
PersonalId	A unique national identification number, passport number, or national registry code.	string	-