itsme

The itsme identification service lets a customer approve the sharing of verified identity data with a participating business. The company receives the requested information through the integration, while the person sees and confirms the identity exchange in the app.

For financial onboarding, the useful question is which attributes the institution receives and how they match its application record. A reusable identity can reduce repeated capture, but the bank still determines whether the evidence meets its identification requirements and which other due diligence steps remain necessary.

The authentication service provides passwordless access for customers returning to a participating online service. This differs from creating an identity at onboarding, because the business needs to recognize an existing account and decide which access rights belong to that customer.

A financial application should define how the itsme identity links to its own customer identifier and what happens after an interrupted login. Account recovery, changes to customer details and authorization for sensitive functions need their own policies, even when several interactions use the same familiar identity app.

The itsme confirmation service records explicit approval for a particular action, with a separate purpose from a routine account login. Its payment use case presents transaction information, including the amount and recipient, so the person can confirm the action they intend to authorize.

That distinction matters when designing strong customer authentication for financial transactions and other sensitive changes. Product teams should specify which details the confirmation binds, how the result reaches the payment system and how canceled or expired requests are handled before enabling the journey for customers.

The itsme signature service enables qualified electronic signatures through supported document and signature platforms. A financial business can therefore assess identification and contract execution within the same customer journey while keeping the signature operation distinct from account login or payment confirmation.

The service supports signatures by natural persons, and itsme states that electronic seals for legal entities are not supported. Buyers should confirm the available platform integration, signer eligibility, document evidence and required signature level for each agreement instead of assuming every financial contract needs the same signing process.

The official itsme coverage register lists supported countries and the documents accepted for establishing an identity. Eligibility varies by issuing country and document type, while available identity attributes can also differ between the Belgian service and other European coverage.

A cross-border lender should test the actual applicant population against that matrix before estimating usable coverage. Country availability alone does not mean every resident has an eligible identity document, and a commercial rollout needs a defined alternative route for applicants who cannot use the selected method.

The official itsme technical documentation describes OpenID Connect integrations for identification, authentication and confirmation. Integration work also includes matching returned identities, validating responses and connecting outcomes with the institutional processes that decide whether an account, payment or agreement can proceed.

A broader identity orchestration strategy can coordinate this method with other accepted routes. A team evaluating IDnow should compare its identification methods against the same requirements, while the separate WebID profile provides context for that provider without treating different verification approaches as interchangeable.

The platform has Belgian origins and publishes a wider European country and document coverage matrix. A financial business should check that current register for its target customers, because the supported documents and returned identity attributes vary between markets and services.

An itsme identification can supply verified identity information within a financial onboarding process. The institution still defines its remaining due diligence obligations, and reusable KYC requires explicit decisions about evidence acceptance, ongoing updates and responsibility across organizations.