Identification

Authentication, Identity verification, Verification, Login verification, User identification, Identity proof, Authentication
Identification is the process of establishing who a person or organization is before access is granted. Crucial to security, privacy and legal compliance.

What is identification?

Identification is the process of determining and verifying who someone is before granting access to systems, data, or services. For online services, this is usually done through a combination of data such as an email address, password, phone number, or official documents. For small and medium-sized businesses, identification is an essential component of security, privacy protection, and legal compliance under the GDPR.

How identification works in practice

An identification process consists of several layers. The first layer is often a username or email address: you claim an identity. The second layer is verification: you prove that you are actually that person, for example through a password, PIN or two-factor authentication. For sensitive transactions or services, a third layer sometimes follows: validation using official documents such as an ID proof or Chamber of Commerce statement. This structure is also called the difference between identification (who are you), authentication (can you prove it) and authorization (what are you allowed to do). In practice, these concepts get mixed up, but the distinction helps when setting up secure systems.

Why identification is required by law in more and more situations

Since the introduction of the General Data Protection Regulation in 2018, as an organization you are obliged to know with whom you communicate and whose data you process. Identification is the starting point here: you can only process personal data if you have a legitimate basis, and that basis presupposes that you know who the data belongs to. Identification also plays a role outside the AVG: consider the Money Laundering and Terrorist Financing (Prevention) Act for financial services, or age verification for online sales of alcohol or tobacco. For ecommerce stores and platforms with user accounts, a clear identification process is therefore not a nice-to-have but a legal requirement.

What identification brings to your business

A well-designed identification process protects your company from fraud, data breaches and reputational damage. You know who has access to which data, you can detect abuse faster and you comply with your AVG obligations. At the same time, you build trust with customers: they know their account and data are safe. In our projects on web development and API integrations, we see that SMEs often think about identification too late. It only becomes urgent after a security incident or complaint. By including identification in your web design and user flows from the start, you avoid costly retrofitting and create a solid foundation for growth.

Applications of identification

Identification plays a role in virtually every digital process that involves personal data or access. Here are four specific situations in which SMBs deploy identification, plus a consideration of when it is or is not necessary.

User accounts in ecommerce stores and platforms.

If you run an ecommerce store or online platform, you want customers to be able to view their order history, download invoices and save their preferences. To do that, you need an account, and that account starts with identification: email address and password, sometimes supplemented by a verification email. With B2B ecommerce stores, you often see an extra step: verification of the Chamber of Commerce number or VAT number to show business discounts or net prices. A common mistake is that companies have too few requirements for passwords, so accounts are easily taken over. Provide at least eight characters, a mix of letters and numbers, and consider two-factor authentication for customers with high order values or sensitive data.

Access management to internal systems and CRM

Identification applies not only to clients but also to your own team. Who is allowed access to the CRM, who has access to financial data, and who can modify products in the ecommerce store’s backend? With a team of five employees, this is straightforward, but once you have ten or more people, you need structure. In practice, we see that small and medium-sized businesses often use a single shared password for tools like WordPress or WooCommerce. This is risky: in the event of an employee leaving or a security breach, you won’t know who did what. By linking individual accounts with unique login credentials to roles and permissions, you maintain control and comply with GDPR Article 32 regarding appropriate security measures. Tools like two-factor authentication and single sign-on make this process user-friendly.

Age verification and compliance in sensitive products

Do you sell products with an age limit, such as alcohol, tobacco or certain supplements? Then you are required by law to verify the age of the buyer. Online, this is done through identification: a copy of an ID proof, a DigiD check or a third-party verification service. In the United States, this obligation has become stricter since 2021. An ecommerce store with 500 orders per month could face hefty fines if it turns out that minors can order without verification. The challenge is to set up identification in such a way that it does not block conversion: customers must feel that they are being helped, not thwarted. A clear explanation up front and a quick verification step after the first order work better than a lengthy form at every checkout.

API links and data exchange between systems

If you allow systems to communicate with each other via APIs, for example between your ecommerce store and an accounting system, that link must also be identified. Not just any API call may retrieve or modify data. Identification here is done via API keys, OAuth tokens or certificates. For SMEs with multiple integrations, we often see that API keys are used too broadly: one key for all connections, with no limitation in rights or duration. This increases the risk in the event of a data breach. By using a unique key per integration with limited rights and an expiration date, you limit the impact of abuse. In projects involving AI automation and API integrations, we build this in as standard.

When identification is the right choice and when it is not

Identification is needed as soon as you process personal data, provide access to private content or are legally required to know someone's identity. It is not necessary if you only inform anonymous visitors without storing data, such as on a standard information website. A common mistake is making identification mandatory where it is not required, such as a mandatory account to request a quote. That raises the threshold and lowers conversion. Conversely, omitting identification where it is required, such as in an order process involving personal data, creates AVG problems. The rule of thumb: identify only when you have a legitimate basis and the data is actually needed for the purpose.

Want to apply this to your business? Monkey Vision helps SME entrepreneurs with web design, SEO and smart digital solutions. Schedule a no-obligation meeting and find out what's possible for you.

Schedule an introduction

Frequently Asked Questions

No, identification and authentication are two sequential steps. Identification is the moment when you claim who you are, such as by entering a username or email address. Authentication is the proof that you are actually that person, usually through a password, PIN or biometric attribute. In practice, the terms are used interchangeably, but the distinction helps in designing secure systems. Identification says "I am Jan," authentication says "and here is the proof. Both are necessary for a complete login process, and both are covered by the security obligations of the AVG.

It depends on customer type, data sensitivity and legal requirements. For a standard B2C ecommerce store with consumer items, email address plus password is often sufficient, possibly supplemented by a verification email. For B2B customers or high order values, two-factor authentication is wise. If you sell age-related products or financial services, identification via ID or DigiD is required by law. A good rule of thumb: the more sensitive the data or transaction, the stronger the identification. Do pay attention to ease of use: too many steps cost conversion. In our ecommerce store projects, we always seek the balance between security and user experience.

The three most common mistakes: too-weak password requirements, shared logins for multiple employees and no logging of who did what when. Weak passwords make accounts vulnerable to brute-force attacks. Shared accounts make it impossible to track responsibility in the event of an incident, creating an AVG violation. And without logging, in the event of a data breach, you can't prove who had access, which makes you liable. A fourth mistake: making identification mandatory where it is not required, such as in a newsletter subscription. That raises the threshold unnecessarily. Identify only when you have a legitimate basis and the data is really needed.

The best approach starts with a clear inventory: what processes require identification, what data do you process and what are the legal requirements? Then choose the identification method that fits the risk level, and test it with real users. Want to know which identification solution suits your situation? Schedule a free 30-minute development and integration scan. We'll walk through your current systems, identify vulnerabilities and provide three concrete areas for improvement that you can pick up this month. No sales pitch, just practical advice tailored to your business.

About the author

Monkey Vision

Monkey Vision is a full-service digital agency at Nijmegen, specializing in web design, SEO, and AI automation for small and medium-sized businesses. The knowledge base has been compiled by our team of online strategists and is continuously updated based on current insights.

Publication date: 26-04-2026
Last update: 26-04-2026