iDIN is an identification method run by the Dutch banks. You log in with your own bank, your bank confirms who you are to the other party, and the check is done. No money moves and the operator gets no view of your account; what is passed on is confirmed personal details, not your banking environment.
A licensed Dutch gambling operator must know who you are before you can play, and iDIN is the route used most often in practice for that step. Below is how the check runs, which data is involved, what your bank sees on its side, and what to do if iDIN does not work for you — a situation that comes up more often than the smooth flow suggests, particularly if you bank outside the Netherlands.
What iDIN does, and what it is not
iDIN relies on the fact that your bank already identified you when you became a customer. Instead of sending a copy of your identity document to a third party, that party asks your bank to confirm what it already knows. You give permission for that each time.
What iDIN is not: not a payment method, not a government login, and not a standing link. After confirmation, no ongoing connection remains between the operator and your bank account. Confusing it with iDEAL means expecting a debit that never comes; confusing it with DigiD means looking for a government login that is not what is happening here.
Why a licensed operator cannot skip this step
A licence holder may not let you play before it has reliably established your identity and age. That is not a house rule but a licence condition, and it connects to two other duties: the legal age limit cannot be enforced without identification, and the exclusion register cannot be queried for someone whose identity is not established.
The law does not prescribe that this has to be done with iDIN. It prescribes the outcome. Operators choose iDIN because it is fast and because a bank's confirmation carries more weight than a form filled in by the player. What other duties attach to a licence is covered on the Remote Gambling Act.
How the check runs, step by step
- At the operator, you choose identification through iDIN and select your bank from the list of participants.
- You are redirected to your bank's own trusted environment and log in with the method you already use there.
- Your bank shows which details the operator is requesting. This is the step worth reading, because it states exactly what is being passed on.
- You confirm, or you cancel. If you do not confirm, the operator receives nothing.
- You return to the operator, which receives the confirmed details and continues the registration.
The whole route runs through your bank, not through the operator. Your login details never reach the operator — that is the point of the design.
Which data actually gets passed on
iDIN works with separate attributes: an operator requests confirmation of specific details, not a full file. The confirmation step shows exactly which ones apply in your case. We do not list a fixed set here, since what is requested can differ by operator, and setting out a list would only encourage skipping the step where it is actually shown.
What is never included is access to your account. No balance, no transaction history, no record of where you have paid before. The operator receives confirmation of details, not a key to your banking environment.
What your bank sees as a result
This is the side of the arrangement rarely mentioned: your bank sees that you identified yourself with this operator through iDIN. That is part of the design — the bank has to carry out the check — and it cannot be avoided within iDIN.
What your bank does not see is what you do with the operator afterward. It is one confirmation at one moment, not ongoing visibility. If you would rather avoid even that one record, ask the operator for a different identification route; that one should exist, but which it is varies by operator and is not something we can state in general.
iDIN, iDEAL and DigiD are three different things
The names look alike; the functions do not. iDIN confirms who you are. iDEAL moves money. DigiD is the government's login method and, in this context, comes up mainly at the exclusion register CRUKS.
The difference is not only terminology. Registering with CRUKS is arranged with DigiD, with the government, not through an operator; identifying with iDIN is arranged with an operator, not with the government. Mixing the two up means looking for the wrong facility in the wrong place — and it matters directly for an expat: no DigiD blocks CRUKS self-registration, but does not by itself block opening a player account through iDIN.
If iDIN does not work for you
Three situations stop the route. Your bank does not participate in iDIN — which banks do participate is listed on idin.nl, not on this page, because that list changes. You have no Dutch bank account, the ordinary situation for anyone who has only recently moved to the Netherlands. Or the details your bank confirms differ from what you gave the operator, for instance after a name change or a shortened first name.
In all three cases the conclusion is the same: the identification duty does not disappear, only this route does. The operator then has to offer you another way to establish your identity. If you are stuck, ask customer support which route they have for that — not yourself which details you might enter differently, since a mismatch between your entry and the bank confirmation is exactly what the check is meant to catch.
Frequently asked questions
Do I have to do iDIN again every time I log in?
Does iDIN cost me anything?
Can I send a copy of my ID instead of using iDIN?
I live in the Netherlands but bank with a foreign bank. What now?
Does a successful iDIN check mean I can play immediately?
Can my bank refuse to cooperate?
Sources
- iDIN — the Dutch banks' identification scheme, with the current list of participants
- Kansspelautoriteit — regulator that checks licence holders' identification duty
- Wet op de kansspelen — consolidated legal text including the Remote Gambling Act
- CRUKS — the exclusion register queried after identification

