iDIN is a Dutch online identification scheme run by the Dutch Payments Association (Betaalvereniging Nederland) on behalf of the country's banks. It lets people prove their identity online using the login they already have for their own bank, rather than uploading a document. The banks have already verified these customers, so iDIN reuses that trusted relationship to share confirmed personal details with other organisations.
iDIN is a Dutch online identification scheme run by the Dutch Payments Association (Betaalvereniging Nederland) on behalf of the country's banks. It lets people prove their identity online using the login they already have for their own bank, rather than uploading a document. The banks have already verified these customers, so iDIN reuses that trusted relationship to share confirmed personal details with other organisations.
To verify, the person chooses their bank, authenticates inside that bank's usual online or mobile banking flow, and consents to share a defined set of identity attributes. Only the data the requesting organisation has asked for, and that the person has agreed to, is released. iDIN supports different request types such as full identification and age verification, so a service can ask for just what it needs.
The verified attributes and a record of the consented result flow back into your Zenoo case, so the identity check sits alongside the rest of the onboarding decision with an audit trail.
The customer chooses their own bank and is taken into that bank's familiar online or mobile banking authentication flow.
The person confirms their identity with the bank and consents to release only the attributes your service has requested, such as name, date of birth, and address.
The verified attributes and a full audit record of the consented result flow straight into your Zenoo case.
Chain these into one Zenoo Studio flow so a single journey handles identity, screening, and fraud.
iDIN is one scheme in Zenoo's global coverage. Add a neighbouring register or a document fallback without changing your integration.
The person selects their bank, authenticates inside that bank's own online or mobile banking flow, and consents to share their identity attributes. Zenoo then returns the verified data, such as name, date of birth, and address, with a full audit trail.
iDIN returns verified identity attributes that the bank already holds and the person has consented to share, such as name, date of birth, gender, and address. Only the fields the requesting organisation asks for are released.
No. iDIN is run by the Dutch Payments Association on behalf of the banks and reuses the customer's existing bank login. It is a bank-based identification scheme rather than a compulsory government identity document.
It runs as a pre-built connector. The person authenticates with their bank through iDIN and consents to share their data, and Zenoo returns a verified result with a full audit record into your case.
