WebID

The WebID product range distinguishes VideoID for live identification, AutoID for automated checks and VisualID for a process involving agent review. Electronic identity options include eID using an identity card and PIN, alongside ePassID using NFC. Those alternatives differ in the credentials and interaction required from the customer.

Selection should begin with the countries, documents and customer groups the institution intends to support. A workflow that assumes a particular card, bank account or language can exclude otherwise eligible applicants. Buyers should test alternative routes and accessible handling of failed checks before deciding how a video identification process fits into their service.

WebID AccountID combines identity document and selfie checks with an online banking login and reference transfer. The process compares bank account information with the identity data collected during identification. The documented workflow therefore evaluates the reference transfer together with the other identity checks.

For a payment provider, useful acceptance cases include an unsupported account, mismatched account holder data and a transfer that does not complete. The institution should establish what each result means and which evidence returns to its onboarding system. This account identification flow serves a different purpose from Verification of Payee when a payment recipient is checked.

WebID CorporateID addresses business verification with information and documents about companies and their beneficial owners. Its documented process includes German transparency register data within Know Your Business checks. A financial institution should confirm which jurisdictions, legal forms and ownership structures its proposed service actually covers.

Business onboarding also needs a clear relationship between the legal entity, its representatives and the people entitled to act. Buyers should test incomplete ownership information, outdated records and cases requiring manual review. An extracted company record and successful personal identification should remain distinguishable evidence within the customer due diligence process.

WebID SignID supports qualified electronic signatures for digital agreements, including financing contracts. The identification step can use a WebID method or an external identification provider within the supported process. Teams should confirm the required identity evidence and signature setup for their intended agreement.

A qualified electronic signature adds signature evidence alongside the other required checks in the onboarding process. The implementation needs rules for document delivery, completed signature files and unsuccessful attempts. Operations teams should know whether a case failed at identification, signing or the transfer back into the contracting system.

The WebID EUDI Wallet connector is described with integration work in progress, alongside testing in national environments. Procurement discussions should distinguish test coverage from production availability for the wallets and countries relevant to the institution. A connector announcement alone does not establish that every intended customer can already use it.

The financial institution retains its role as the relying party when accepting wallet credentials, while WebID supplies the technical intermediary. Requirements for requesting attributes, assessing evidence and retaining records therefore need explicit ownership. EUDI Wallet use in finance connects wallet acceptance to those operational decisions and the wider onboarding process.

A provider offering several methods still needs defined routing rules within the financial institution. Identity orchestration in finance brings method selection, additional checks and exception handling into one managed workflow. Teams should establish how retries, changed methods and manual decisions remain attached to the original customer application.

Vendor review should cover supported markets, evidence exports, retention, access control and operational escalation. Acceptance testing should include rejected identification, interrupted sessions and technical failure as well as successful applications. A general compliance claim needs checking against the exact contracted service and its current documentation for each financial use case.

The documented AccountID process combines document and selfie checks with bank login and a reference transfer. Buyers should evaluate the complete workflow and returned evidence for their own onboarding requirements.

The financial institution remains the relying party while using WebID as a technical intermediary for wallet connections. The service agreement should clearly assign technical tasks and operational responsibilities between the organizations.

Company records, beneficial ownership and personal identity establish different facts during business customer onboarding. The institution should define how those results combine before a representative can open or operate an account.