IDfier Developers

Scopes

The customer fields you can receive, and the scope each one needs.

Your business client's scopes decide which fields you receive. IDfier sets them up, for example fullname,email,ageOver18,authLevel. A login session uses all of them; a verification link can ask for fewer.

Every field except id is sent only if it is in your scopes and IDfier has it for the customer. Treat a missing field as unknown.

The id field

Always included. id is a stable identifier for the customer within your business: the same customer always gets the same id from you, and a different id from every other business. Use it to recognise returning customers. It is not IDfier's internal user id and can't be used to match customers across businesses.

Identity

FieldTypeScope
fullnamestringfullname
handlestringhandle
emailstringemail
personalNostringpersonalNo

Age and birth

FieldTypeScope
agenumberage: whole years today, computed from the verified date of birth
dateOfBirthstringdateOfBirth
ageOver13, ageOver16, ageOver18, ageOver21, ageOver65booleanThe same name
ageBetween{min}And{max}booleanThe same name, e.g. ageBetween18And25

The age checks answer yes or no without revealing the date of birth or age; see Age verification.

Document and location

FieldTypeScope
documentTypestringdocumentType
genderstringgender
nationalitystringnationality
countrystringcountry

How the customer was verified

FieldTypeScope
authLevelstringauthLevel
authLevelVerified with
GoldID document with its chip read (NFC), or an IDfier profile created from an EU Digital Identity Wallet
SilverBankID
BronzeID document scan without the chip
EU WalletShared directly from an EU Digital Identity Wallet
UnknownNone of the above

For customers sharing from an EU wallet, see which fields the wallet provides in EU Digital Identity Wallet.

On this page