Skip to main content
Release: CX-Saturn (Preview)

CX-0149 Wallet Requirements v2.0.0

ABSTRACT​

A wallet is a service used for managing Verifiable Credentials. It is commonly associated with and identified by a Decentralized Identifier (DID). This standard describes requirements for Catena-X compliant wallets and how participants may obtain such a wallet.

FOR WHOM IS THE STANDARD DESIGNED​

This standard is relevant for CSPs who must offer participants the provisioning of a Catena-X compliant wallet. It is also relevant for anyone who may wish to implement, host, provide, or obtain a Catena-X compliant wallet.

1 INTRODUCTION​

1.1 AUDIENCE & SCOPE​

This section is non-normative

This standard describes minimum requirements a wallet must fulfil in order to be used in the Catena-X dataspace. It also describes how a participant may obtain such a wallet.

This standard is relevant for Core Service Providers, as they must provide each participant with a Catena-X compliant wallet. It is also relevant for anyone else wanting to host or provide a Catena-X compliant wallet.

1.2 CONTEXT AND ARCHITECTURE FIT​

This section is non-normative

The Catena-X dataspace uses Self-Sovereign Identity for verifying participants' identities and claims about the participants. Participants are identified by a Decentralized Identifier (DID) and claims about participants are issued, presented, and verified in the form of Verifiable Credentials. Both DIDs and Verifiable Credentials are managed through a wallet. During onboarding, the CSP issues both a BPN Credential and a Membership Credential to a participant, see CX-0050.

1.3 CONFORMANCE AND PROOF OF CONFORMITY​

This section is non-normative

Sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The keywords MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD and SHOULD NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

For a wallet to be Catena-X compliant, it must fulfil compliance criteria of the specifications required in 2.1 REQUIREMENTS FOR A CATENA-X-COMPLIANT WALLET.

The CSP MUST provide a wallet that is Catena-X compliant.

2 MAIN CONTENT​

This section is normative

Unless mentioned otherwise, in this section "wallet" refers to a Catena-X-compliant wallet. Any wallet used in the Catena-X dataspace MUST be a Catena-X-compliant wallet.

2.1 REQUIREMENTS FOR A CATENA-X-COMPLIANT WALLET​

Wallets MUST implement the Decentralized Claims Protocol (DCP) v1.0 with profile vc11-sl2021/jwt. Support for presentation definitions is not required, and they SHOULD NOT be used. The following scopes MUST be implemented.

org.eclipse.tractusx.vc.type:MembershipCredential:read
org.eclipse.tractusx.vc.type:DataExchangeGovernanceCredential:read
org.eclipse.tractusx.vc.type:BpnCredential:read

The above requirements also imply the requirement of VC Data Model v1.1, StatusList2021 and that all communication happen via HTTPS. For details, please see the DCP specification

The wallet MUST be associated with a Decentralized Identifier following the DID v1.0 specification and using the did:web method. The corresponding DID document MUST be compliant with CX-0049.

2.1.1 BACKWARDS COMPATIBILITY​

For backwards compatibility with the R24.09 Jupiter release, a wallet MUST support DCP presentation flow v0.8.1. This requirement is in addition to the requirement for full DCP v1.0 support, i.e. the wallet must support both v0.8.1 and v1.0 of the DCP presentation flow. This backwards compatibility requirement should be dropped with the R26.09 release or when compatibility with R24.09 is no longer required.

2.2 OBTAINING A WALLET INSTANCE​

Every participant MUST have their own wallet instance. There are two possible ways for a participant to obtain a wallet instance:

2.2.1 PROVISIONING PARTICIPANT WALLETS​

The CSP MUST offer every participant to provision a wallet instance for them.

2.2.2 USING PARTICIPANT-OWNED WALLETS​

A participant MAY reject this provisioned wallet instance and instead choose to use their own wallet instance. In this case, the CSP is not required to provide a wallet instance for this participant. The participant MUST provide the CSP with the DID of the wallet instance they wish to use. The wallet instance used by the participant MUST be a Catena-X-compliant wallet and MUST be available before the participant initiates the onboarding process.

3 REFERENCES​

3.1 NORMATIVE REFERENCES​

3.2 NON-NORMATIVE REFERENCES​

This section is non-normative

3.3 REFERENCE IMPLEMENTATIONS​

This section is non-normative

ANNEXES​

FIGURES​

This section is non-normative

N/A

TABLES​

This section is non-normative

N/A

Copyright © 2025 Catena-X Automotive Network e.V. All rights reserved. For more information, please visit here.