
Company Passport European Business Wallet Have Your Say Submitted
Since 2021, the Company Passport initiative has been working on providing the necessary foundation for the introduction of Organizational/Business Wallets, acknowledging that the introduction of such wallets will have a significant impact in many different scenarios. Our primary use case is centred around the foundation and ‘onboarding’ of companies (more specifically the Dutch Private limited Company), including the KYC/KYB process. At this stage Company Passport has provided a harmonised taxonomy, several credential schemes and an eIDAS 2 based architectural framework, grounded in the ARF. The current focus of the use case is on the process as used in the Dutch context. All this information can be accessed on our website www.companypassport.eu and in our Github here.
Please find videos of May 6th session in the links below. We are still arranging English sub-titles of the actual presentation films. The aftermovie has recently been published on LinkedIn.
CP Partner Event Aftermovie (already with english subtitles)
Videos per presentor (only in Dutch at the moment)
More specifically we would like to make some observations regarding the use of business wallets
Scope Expansion of the Business Wallet Beyond Legal Person (LP) Definition
We propose broadening the scope of the Business Wallet, from the narrow EIDAS2 focus on Legal Persons only.
1. Business wallets should not only be offered to Legal Persons but also Natural Persons with their own business, who make up most business registrations. For example, in the Netherlands, 90% of registrations are sole proprietorships, partnerships and associations that do not fall under the Legal Person definition. Many types of relying parties (for instance banks), distinguish between sole proprietaries of Natural Persons and their Natural Person acting as a citizen's normal household.
2. Business wallets should also accommodate those who hold no registration in an EU business register but are still registered by another body to confirm their existence. In the Netherlands, there is a category of entities that does not need to be registered in a Business Register. Potentially that would require a different type of register to be set up (or such entities would need to be added to the Dutch Chamber of Commerce holder register).
Deployment of Organisational EUDIW
It is anticipated that, in the vast majority of cases, the Organisational European Digital Identity Wallet (EUDIW) will be deployed as a cloud-based solution. While it is technically feasible for very small enterprises to "host" the organisational wallet on a local device, this will likely be the exception rather than the norm. In such scenarios, the organisational wallet would resemble the Natural Person (NP) EUDIW, mainly focussed on "2) Requesting, holding, and presenting capabilities" mentioned below. The main difference then is the presence of an "LPID" or indeed an "Organisational PID" as the case may be.
In the current ARF communication protocols we found no base that a mobile device-bound organisational wallet could completely function as an issuer or relying party.
In terms of "Issuance" a device bound wallet could of course "issue" something with appropriate seal and/or digital signature, but we have no confirmation if this procedure meets all conditions to be considered as "issuance" under eIDAS - ARF.
Preferred Architecture: Modular Cloud-Based Capabilities
In practice, organisational digital identity functionality will more commonly be realised through a modular architecture comprising three distinct, cloud-based capabilities:
1. Issuing capability
2. Requesting, holding, and presenting capability
3. Relying party capability
In such an architecture, both the (1) issuing component and the (3) relying party capability are typically integrated in the organisation’s internal legacy systems (e.g., via APIs). In the context of banking institutions, this refers specifically to integration with Know Your Customer (KYC) systems and the static data repositories of product platforms. The same type of connection to more corporate oriented legal systems may apply to the (2) requesting/holding/presenting component, yet this could just as well remain stand-alone with no connection to legacy systems.
Value creation
Note that as part of our explorations Company Passport has found that successful uptake and value creation is expected in general B2B engagement (i.e. entering safer, securer, non-refutable fraud resistant and machine readable B2B engagements), rather than “just” engagements with obliged entities. Noteworthy in this respect is the fact that the firm (or NP) has selective disclosure rights and can therefore decide which data-points the firm/NP wishes to consent being shared.
Furthermore, for relying parties in a broad spectrum of economic transactions, sets of verifiable credentials can function as trust anchors that via search actions on credential listings or via M2M system integrations instantly can be verified. This enhances trust and actively prevents fraud.
As a result of experiments we have performed in our Sandbox environment, we conclude the Business Wallet needs additional features such as system-to-system sharing of data, inbox functionality, delivering data in the wallet without human intervention and a flexible permission and trust system. We see great potential in granular authorisations and power of attorney.
Trust services ecosystem
Company Passport has already had in depth engagements with Center of Excellence Datasharing & Cloud, iShare & de Dutch eHerkenning providers (QTSPs). Trust you will find our initial conclusions helpful (see attachment which demonstrates engagement organisational wallets in Datasharing and Dataspaces)
Perhaps more noteworthy for Natural Person EUDIWs, yet just as helpful for situations where a NP represents a business, it can be important to reconfirm the binding of the actual natural person to the device. Company Passport has engaged with Partnership Cyber Security Innovation “Digital Deltaworks” to provide options to make this more robust. ARF 1.5 has since provided allowances for this.
There are a lot of other identifiers in different contexts and processes in use, for example in the field of intellectual property, the taxation, customs, and excise domain, in education, in health, in automotive. We suggest considering how trust can be enhanced, for example by using organisation wallets and credentials to verify if conditions are (still) in place and how to issue and verify commonly used identifiers in a more cost and process efficient way to develop a more robust and competitive internal European market.
Attachments
General Presentation on Company Passport and its partners
Whitepaper Scheme aggregator (in Dutch):
• Samenwerking en governance voor interoperabiliteit in grensoverschrijdende digitale transacties
CP Taxonomy Working Group (SKOS, Ontology, Datamodels, Schema’s & Rulebooks)
Coe Datasharing & Cloud / iShare / eHerkenning partnership with company passport