EAASD-JWT VC

Attestation Rulebook for attestations of type Control

Category: non-qualified EAA

• Author(s):
• [Florin Coptil, Robert Bosch GmbH]
• [Stephan Fuchs, Deutsche Bank AG]
• Reviewer(s):
• [Baumgardt Michaela, Commerzbank]
• [Bastek-Margo Jenny, Commerzbank]
• [Fabrizio Notarnicola, Infocameere IT ]
• [Ricky Lamberty, Robert Bosch GmbH]
• [ , Bundesanzeiger ]
• [ Leone Riello , Infocert]
• Contact:
• Florin Coptil*
• Stephan Fuchs*
• Feedback:

Written against: ARF version 3.0.0, WE BUILD template version 1.0 (generic)

Feedback: GitHub issues

1 Introduction

This attestation addresses the following question:

Who exercises effective control over this legal entity?

A Controller is any natural person, legal entity, or legal arrangement that directly or indirectly exercises effective control over a legal entity.

1.1 Document scope and purpose

The Control Attestation records all natural persons, legal entities, and legal arrangements which have control, direct or indirect, in a legal entity, providing comprehensive transparency on control structures. This attestation is a critical component of both Know Your Customer (KYC) and Know Your Supplier (KYS) processes within the Wallet ecosystem, supporting effective risk management, regulatory compliance, and anti-money laundering (AML) obligations.

Design Decisions

This Control Attestation Rulebook is based on: - The EU Anti-Money Laundering Regulation (AMLR 2024/1624) as the primary regulatory driver for beneficial ownership and control transparency obligations - The EUDI Wallet ecosystem and eIDAS 2 framework as the digital identity infrastructure - The SD-JWT VC specification (draft-ietf-oauth-sd-jwt-vc-09) for verifiable credential encoding - ISO 3166-1 alpha-2 for country and jurisdiction codes - ISO 8601 for date formatting - ISO 17442 for Legal Entity Identifier (LEI) codes - Beneficial Ownership Data Standard (BODS) version 0.4

1.2 Document structure

This Rulebook follows the generic WE BUILD attestation rulebook template. Chapter 2 states how it complies with the ARF and the applicable Regulations. Chapters 3 and 4 define the attributes and metadata in an encoding-independent manner. Chapter 5 states the formats in which this attestation is issued. Chapters 6 to 9 cover protocols, issuance, revocation and presentation. Chapter 10 sets out the trust framework, and chapter 11 lists references.

1.3 Key words

This document uses the capitalised key words 'SHALL', 'SHOULD' and 'MAY' as specified in [RFC 2119], to indicate requirements, recommendations and options.

In addition, 'must' (non-capitalised) indicates an external constraint, a requirement not mandated by this document but by an external document. The word 'can' indicates a capability. Other words such as 'will', 'is' and 'are' are statements of fact.

1.4 Terminology

Additional terminology specific to this attestation:

2 Compliance

2.1 Compliance statement

This Rulebook complies with the applicable requirements of Topic 12, Attestation Rulebooks, in Annex 2 of the Architecture and Reference Framework, version 3.0.0. It uses the terminology of Annex 1 of the ARF.

2.2 Regulatory basis

This attestation is not a qualified electronic attestation of attributes. The data described in Annex V points b, c and e of Regulation (EU) 2024/1183 is addressed as required by EW-DM-12-018 and as recommended by EW-DM-12-020 and EW-DM-12-022. Where a recommendation is not followed, the reason is stated below.

Where the attestation is issued as a qualified electronic attestation of attributes, the trust model of chapter 10 applies in its qualified form and the legal category recorded in section 4.1 changes accordingly.

2.3 Traceability

Every applicable requirement mapped to the section that satisfies it. Requirements marked not applicable carry a stated reason.

3 Attestation attributes

The Control Attestation is designed to provide a complete, verifiable representation of an entity's control structure in a standardised digital format. This attestation supports transparency, compliance, and risk management by enabling automated verification of effective control across complex, multi-tiered corporate structures where control may be exercised through diverse mechanisms beyond simple shareholding.

Attributes are defined here in an encoding-independent manner (EW-DM-12-007). The encoding of each attribute is given in chapter 5.

3.1 Introduction

The Controller model supports three distinct controller types: natural persons (Person), legal entities (Entity with category = "legal_entity"), and legal arrangements (Entity with category = "legal_arrangement", e.g., trusts, foundations).

Controller type classification:

Controller entity category classification (applicable when type = "Entity"):

Data Model:

The Controller follows a hierarchical structure:

Controller [1..n]                               // The person or entity exercising control
├─ type (enum) (M)                              // "Person" | "Entity"
├─ jurisdiction (tstr) (M)                      // ISO 3166-1 alpha-2
├─ person (O, conditional on type="Person")
│   ├─ first_name (tstr) (M)
│   ├─ surname (tstr) (M)
│   └─ birth_date (date) (O)                    // ISO 8601 YYYY-MM-DD
├─ entity (O, conditional on type="Entity")
│   ├─ category (enum) (M)                      // "legal_entity" | "legal_arrangement"
│   ├─ name (tstr) (M)
│   ├─ identifier [1..n] (M)                    // At least one identifier required
│   │   ├─ type:euid (str) value(O)             // European Unique Identifier
│   │   ├─ type:lei (str) value(O)              // Legal Entity Identifier per ISO 17442
│   │   ├─ type:tax (str) value(O)              // National tax or registration number
│   │   └─ type:other (str) value(O)           // Any other applicable identifier 
│   ├─ jurisdiction (tstr) (M)                  // ISO 3166-1 alpha-2
│   ├─ legal_form (tstr) (M)                    
│   ├─ form (tstr) (M)                          // See Section 2.8.8 -> legal_form (see XLS from Finnland)
│   └─ subtype_info (object) (O)                // Mandatory when category = "legal_arrangement"
│       ├─ settlement (tstr) (M)                // Founding instrument or trust deed
│       ├─ purpose (tstr) (M)                   // Declared purpose of the arrangement
│       ├─ assets (tstr) (M)                    // Assets held within the arrangement
│       └─ reason_for_registration (tstr) (O)   // Optional reason for formal registration
├─ address (Address) (M)                        // Residential (Person) or registered (Entity)
│   ├─ street (tstr) (M)
│   ├─ house_number (tstr) (M)
│   ├─ locality (tstr) (M)
│   ├─ region (tstr) (M)
│   ├─ postal_code (tstr) (M)
│   └─ country (tstr) (M)                       // ISO 3166-1 alpha-2
├─ controls (M)                                 // How control is exercised
│   ├─ type [enum] [1..n] (M)                   // See Section 2.8.3
│   ├─ level (tstr) (M)                         // "direct" | "indirect" | "joint" | "unknown"
│   ├─ basis [enum] (M)                         // e.g., "corporate_position", "contractual"
│   ├─ voting_percentage (Decimal) (M)          // Percentage of voting rights (0–100)
│   ├─ appointment_rights (tstr) (O)            // Free text details on appointment rights
│   ├─ other_details (tstr) (O)                 // Free text for other control mechanisms
│   └─ rights [String] (M)                      // "dividend_rights" | "liquidation_rights"
├─ effective_date (date) (M)                    // ISO 8601 YYYY-MM-DD
└─ evidence [1..n] (M)                          // At least one evidence entry required
│   ├─ id (tstr) (M)                            // Unique identifier, URI, or URN
│   ├─ type (tstr) (M)                          // Evidence type, see Section 2.8.9
│   ├─ url (uri) (O)                            // URI to publicly accessible source document
│   └─ data (base64) (O)                        // Base64-encoded, required if url absent

Note: M - mandatory / O - optional.

Explanation: - The attestation SHALL contain at least one Controller entry of type = "Person" to comply with AML requirements mandating identification of the natural persons who ultimately exercise control over the entity. - The attestation MAY contain zero or more Controller entries of type = "Entity" representing intermediate legal entities or legal arrangements in the control chain. - Each Controller entry SHALL include: - type (mandatory enum: "Person" or "Entity") - jurisdiction (mandatory, ISO 3166-1 alpha-2) - address (mandatory, residential address for Person, registered address for Entity) - controls (mandatory, at least one record describing how control is exercised) - effective_date (mandatory, date when this control became effective) - evidence (mandatory, at least one piece of supporting evidence)

• For each Controller of type = "Person":
• The person object SHALL be present and the entity object SHALL be absent.
• first_name and surname SHALL be present.
• birth_date is OPTIONAL but SHOULD be included where available.

• At least one controls record SHALL be present, including:

  • type, SHALL use values from Section 4.4.3
  • level, SHALL use values from Section 4.4.2
  • basis, SHALL use values from Section 4.4.4
  • rights, SHALL use values from Section 4.4.5

• For each Controller of type = "Entity":

• The entity object SHALL be present and the person object SHALL be absent.
• category SHALL be present and SHALL be one of "legal_entity" or "legal_arrangement".
• name SHALL be present (complete official registered name).
• identifier SHALL contain at least one of: euid, lei, tax, or other.
• jurisdiction SHALL be present (ISO 3166-1 alpha-2).
• form SHALL be present and SHALL use a value from Section 4.4.6.

• At least one controls record SHALL be present.

• When entity.category = "legal_arrangement" OR entity.form = "trust", the subtype_info object SHALL be present and SHALL include:

• settlement, the instrument establishing the legal arrangement
• purpose, the declared purpose of the arrangement
• assets, description of assets held within the arrangement

• reason_for_registration is OPTIONAL

• Each Controller entry SHALL include at least one evidence entry. Each evidence entry SHALL include:

• id, unique identifier, URI, or URN of the source document
• type, SHALL use values from Section 4.4.9

• data, base64-encoded document, SHALL be provided if url is absent or not publicly accessible

• controls.type SHALL be an array allowing multiple concurrent control mechanism types to be declared for a single controller.

• controls.level SHALL use one of: "direct", "indirect", "joint", or "unknown" as defined in Section 4.4.2.
• controls.rights SHALL be an array and SHALL use values from Section 4.4.5.
• effective_date SHALL follow ISO 8601 YYYY-MM-DD format.

Attestation Classification:

This attestation type MAY be classified as: - EAA within the EUBW Wallet ecosystem, when self-issued by the legal entity subject to the control disclosure (i.e., the entity issues an attestation about its own control structure). - QEAA when issued by a qualified trust service provider (QTSP) or authorized competent body that can independently attest the control structure (e.g., based on official company register data, audited financial statements, or notarized documentation).

Terms primarily relevant to a Person controller:

Terms primarily relevant to an Entity controller (as legal_entity or legal_arrangement):

3.2 Mandatory attributes

Controller Top-Level Mandatory Attributes (applies to all Controller entries)

Person Controller Mandatory Attributes (present when type = "Person")

Entity Controller Mandatory Attributes (present when type = "Entity")

Entity Identifier Fields (at least one SHALL be present)

Legal Arrangement Additional Mandatory Attributes (present when entity.category = "legal_arrangement" or entity.form = "trust")

Address Mandatory Attributes (applies to all Controller entries)

Controls Mandatory Attributes (at least one record per Controller entry)

Evidence Mandatory Attributes (at least one entry per Controller entry)

3.3 Optional attributes

Person Controller Optional Attributes

Legal Arrangement Optional Attributes (when entity.category = "legal_arrangement")

Controls Optional Attributes

Evidence Optional Attributes

3.4 Conditional attributes

4 Metadata

Metadata describes the attestation rather than its subject.

4.1 Mandatory metadata

Note: Only the additional mandatory attributes are listed; the mandatory attributes defined by the protocol are not specified.

Legal category. This Rulebook retains the attestation_legal_category attribute. Section 4.1 of the generic template replaces it with the category attribute of [ETSI TS 119 472-1], whose value for this category is eaa:eu:non-qualified. EW-DM-12-029, legacy ARB_25, of ARF version 3.0.0 is a SHALL that still requires attestation_legal_category, so the template and the ARF disagree. The attribute is left as written and the deviation is recorded for the rulebook quality assurance group.

4.2 Optional metadata

4.3 Conditional metadata

No conditional metadata elements are defined for this attestation type.

4.4 Code lists

4.4.1 controller.type Values

4.4.2 controls.level Values

4.4.3 controls.type Values

Note: Multiple mechanism types MAY apply to a single controller. In such cases, controls.type SHALL be encoded as an array containing all applicable values.

4.4.4 controls.basis Values

4.4.5 controls.rights Values

4.4.6 entity.form Values

4.4.7 Country Codes

controller.jurisdiction, entity.jurisdiction, and address.country SHALL use ISO 3166-1 alpha-2 two-letter country codes.

4.4.8 Date Formats

All date attributes (e.g., effective_date, person.birth_date) SHALL follow the ISO 8601 YYYY-MM-DD format.

4.4.9 Evidence Type Values

4.5 Integrity rules

The following integrity rules SHALL be enforced during issuance and verification:

5 Formats

5.1 SD-JWT VC-based encoding

The Control Attestation uses the SD-JWT VC format to allow for selective disclosure of control structure attributes.

Selective Disclosure: Top-level claims (controller, evidence) SHALL be individually selectively disclosable, enabling a legal entity to disclose only the attributes requested by a Relying Party. The . notation is used to indicate the nesting of attributes.

Verifiable Credential Type (vct): eu.we-build:control:1

5.1.1 Attribute Encoding Table

Notes:

• MUST: The claim SHALL be selectively disclosable, the holder MAY choose to disclose or withhold this claim when presenting the credential to a Relying Party.
• MUST NOT: The claim SHALL NOT be selectively disclosable, it is always present in plain text in the JWT header/payload and cannot be withheld by the holder, as it is required for credential verification and trust establishment.
• MUST (conditional): The claim SHALL be selectively disclosable and SHALL be present when the specified condition is met.
• controller entries are indexed as [n] where n starts at 0; at least one controller SHALL be present, and at least one SHALL be of type = "Person".
• evidence entries within each controller are indexed as [m] where m starts at 0; at least one evidence entry SHALL be present per controller.
• iat, exp, and iss follow RFC 7519 standard JWT claim naming conventions.

5.1.2 Status Claim

For SD-JWT VC-compliant Control Attestations, the attestation MUST include a status claim if the technical validity period is greater than 24 hours. This claim enables Relying Parties to determine if a credential has been revoked via a status list mechanism, as specified in SD-JWT VC.

The status claim SHALL be a JSON object with the following members:

Example:

{
  "status": {
    "type": "status-list",
    "status_list_credential": "https://issuer.example.com/status/control/2025",
    "status_list_index": 456,
    "status_purpose": "revocation"
  }
}

3.2.3 Example Payload

The following is a non-normative example of a Control Attestation SD-JWT VC payload demonstrating a natural person controller, a legal entity controller, and a legal arrangement controller:

{
  "vct": "eu.we-build:control:1",
  "iss": "https://issuer.example.com",
  "iat": 1736935200,
  "exp": 1768471200,
  "attestation_legal_category": "EAA",
  "schema_version": "0.9.0",
  "trust_anchor_url": "https://trust.webuildconsortium.eu/anchors/eidas-tl",

  "controller": [
    {
      "type": "Person",
      "jurisdiction": "DE",
      "person": {
        "first_name": "Alice",
        "surname": "Smith",
        "birth_date": "1975-03-20"
      },
      "address": {
        "street": "Hauptstrasse",
        "house_number": "10",
        "locality": "Berlin",
        "region": "Berlin",
        "postal_code": "10115",
        "country": "DE"
      },
      "controls": {
        "type": ["voting_rights", "board"],
        "level": "direct",
        "basis": "shareholding",
        "voting_percentage": 60.0,
        "appointment_rights": "Right to appoint majority of supervisory board",
        "rights": ["dividend_rights", "liquidation_rights"]
      },
      "effective_date": "2020-01-15",
      "evidence": [
        {
          "id": "src-001",
          "type": "officialRegister",
          "url": "https://example.com/docs/shareholder-register-2024.pdf"
        }
      ]
    },
    {
      "type": "Entity",
      "jurisdiction": "DE",
      "entity": {
        "category": "legal_entity",
        "name": "HoldCo GmbH",
        "identifier": {
          "euid": "DE987654321",
          "lei": "529900T8BM49AURSDO55",
          "tax": "DE123456789"
        },
        "jurisdiction": "DE",
        "form": "private_company",
        "legal_form":"GmbH"
      },
      "address": {
        "street": "Musterstraße",
        "house_number": "45",
        "locality": "Frankfurt",
        "region": "Hessen",
        "postal_code": "60311",
        "country": "DE"
      },
      "controls": {
        "type": ["nominee", "voting_rights"],
        "level": "indirect",
        "basis": "shareholding",
        "voting_percentage": 40.0,
        "rights": ["dividend_rights"]
      },
      "effective_date": "2019-06-01",
      "evidence": [
        {
          "id": "src-002",
          "type": "governanceChart",
          "url": "https://example.com/docs/governance-chart-2024.pdf"
        }
      ]
    },
    {
      "type": "Entity",
      "jurisdiction": "LU",
      "entity": {
        "category": "legal_arrangement",
        "name": "Smith Family Trust",
        "identifier": {
          "lei": "549300ABCDEF12345678"
        },
        "jurisdiction": "LU",
        "form": "trust",
        "subtype_info": {
          "settlement": "Settled under Luxembourg trust law on 2015-03-01",
          "purpose": "Family wealth management and succession planning",
          "assets": "Real estate, securities portfolios, and cash holdings",
          "reason_for_registration": "Registered for tax transparency under CRS"
        }
      },
      "address": {
        "street": "Rue de la Forêt",
        "house_number": "7",
        "locality": "Luxembourg",
        "region": "Luxembourg",
        "postal_code": "L-1234",
        "country": "LU"
      },
      "controls": {
        "type": ["agreements", "other_means_of_control"],
        "level": "indirect",
        "basis": "trust_arrangement",
        "voting_percentage": 0.0,
        "other_details": "Control exercised through trustee appointment rights over beneficiary assets",
        "rights": ["dividend_rights", "liquidation_rights"]
      },
      "effective_date": "2015-03-01",
      "evidence": [
        {
          "id": "src-003",
          "type": "trustDeed",
          "url": "https://example.com/docs/trust-deed-2015.pdf"
        }
      ]
    }
  ],

  "status": {
    "type": "status-list",
    "status_list_credential": "https://issuer.example.com/status/control/2025",
    "status_list_index": 456,
    "status_purpose": "revocation"
  },

  "cnf": {
    "jwk": {
      "kty": "EC",
      "crv": "P-256",
      "x": "TCAER19Zvu3OHF4j4W4vfSVoHIP1ILilDls7vCeGemc",
      "y": "ZxjiWWbZMQGHVWKVQ4hbSIirsVfuecCE6t4jT9F2HZQ"
    }
  }
}

Sample payloads are provided under ../data-schemas/sd-jwt/sample-data/control-sd-jwt-sample.json

5.2 ISO/IEC 18013-5-compliant encoding

ISO/IEC 18013-5 (mdoc) is out of scope for this Rulebook, as offline proximity presentation is not a current requirement for the Control Attestation.

5.3 W3C Verifiable Credentials Data Model-based encoding

This Rulebook does not define a W3C Verifiable Credentials Data Model encoding for this attestation type.

6 Protocols

6.1 Issuance

This attestation is issued using OpenID for Verifiable Credential Issuance [OpenID4VCI], as profiled by [HAIP].

6.2 Presentation

This attestation is presented using OpenID for Verifiable Presentations [OpenID4VP]. Only remote presentation is in scope, consistent with chapter 5, which records the mdoc encoding as out of scope.

7 Issuance

7.1 Binding

7.2 Issuance Policy

For EAA (Self-Issued / Standard Issuance): - The issuer (i.e., the legal entity itself) issues the attestation based on the information and supporting documentation available at the time of issuance. - The issuer is responsible for ensuring that the attested information remains accurate and must immediately revoke the attestation if any change occurs that affects the validity or accuracy of the underlying data.

For QEAA (Qualified Issuance): - The issuer-either a Qualified Trust Service Provider (QTSP) or another authorized competent body-must issue and verify the attestation exclusively on the basis of authoritative sources, such as official company register data or audited financial statements. - The issuer is also responsible for maintaining a high level of assurance throughout the attestation's validity period by continuously monitoring the underlying information. If any change affecting the accuracy or validity of the attested data is detected, the issuer must promptly revoke the attestation.

The Issuer SHALL implement the base issuer obligation as defined in the Issuer Obligation specification: https://github.com/webuild-consortium/webuild-attestation-rulebooks-catalog/blob/main/rulebooks/rb-base/verifier-base-verification.md#41-issuer-obligations

7.3 Lifecycle management

The issuer sets the validity period of the attestation and reissues it when the underlying facts change, revoking the superseded attestation as described in chapter 8.

7.4 Embedded disclosure policy

This attestation defines no embedded disclosure policy.

8 Revocation

An attestation SHALL remain valid only while its underlying information is accurate, complete, and legally effective.

Revocation Mechanism - Token Status List: The issuer must maintain an active IETF Token Status List (aligned with the Attestation Status List mechanism specified by the EU Commission). - Credential Metadata: The metadata status_list must be populated in every issued CompanyInfo attestation, referencing the status list URI and the credential's specific index.

Authorized Authority: Only the authorized issuer (the QTSP/competent body for QEAA, or the self-issuing legal entity for EAA) may modify the status list entry.

Revocation Triggers & Business Rules - QEAA Trigger (Automatic): The QTSP/competent body must actively monitor official company register data and audited financial statements. Any detected discrepancy or change in the company registry must automatically trigger revocation of the QEAA. - EAA Trigger (Manual Obligation): The self-issuing legal entity is under strict obligation to immediately update or revoke its EAA if its available documents, financial thresholds, or ownership structures change.

Relying Party Action: A revoked or suspended attestation must be treated as invalid for credential-validity purposes by all RPs. The business interpretation is determined by the Relying Party's internal compliance policies.

9 Presentation

Base Verification Process

The Relying Party SHALL perform the base attestation verification process as defined in the Base Verification specification: https://github.com/webuild-consortium/webuild-attestation-rulebooks-catalog/blob/main/rulebooks/rb-base/verifier-base-verification.md#42-relying-party-obligations

9.1 Presentation Policy

To verify and validate a received presentation of an attestation of this type, the following steps SHALL be performed:

1. verify the signature over the attestation using a trust anchor obtained as described in chapter 10;
2. verify that the attestation is within its validity period;
3. check revocation status as described in chapter 8, unless the attestation is short-lived, or its remaining lifetime is below the revocation time threshold;
4. verify device binding where section 7.1 records the attestation as device-bound;
5. request only those attributes that are necessary for the stated purpose of the transaction, and, where the trust model for this attestation requires Relying Party registration, only those attributes it is registered and authorised to request.

Obligations specific to this attestation type, carried over from the Relying Party obligations of the previous version of this Rulebook:

When receiving and processing an attestation, the Relying Party SHALL perform the following verification obligations.

9.2 Presentation modes

Remote presentation is in scope. Proximity presentation is not in scope, consistent with chapter 5, which records the mdoc encoding as out of scope.

9.3 Transactional data

This Rulebook defines no transactional data.

10 Trust Framework

The trust anchor is obtained as described in the branch below that corresponds to the legal category under which the attestation was issued.

This chapter specifies the trust anchor mechanisms used by Relying Parties to establish trust in the issuer of an Electronic Attestation of Attributes (EAA) or a Qualified Electronic Attestation of Attributes (QEAA). The corresponding verification procedures are defined in Sections 4.2.2–4.2.4.

Qualified Electronic Attestations of Attributes (QEAAs)

For QEAAs, trust is established through the X.509 Public Key Infrastructure (PKI) and the applicable Trust List of Licensees (TLOL). The issuer's certificate chain, including the intermediate certificate contained in the QEAA header, SHALL be validated up to a trusted root certificate. This validation SHALL be performed using the applicable TLOL, taking into account the trust list state applicable at the time of issuance.

Successful certificate chain validation establishes that: - the issuer's certificate was recognized within the applicable trust framework; - the issuer's identity has been validated by the supervisory authority during inclusion in the TLOL; and - the issuer satisfies the trust requirements applicable to QEAAs.

In addition, the Relying Party MAY apply further authorization checks based on its internal policies, such as maintaining a whitelist of accepted QEAA providers.

Electronic Attestations of Attributes (EAAs)

For EAAs, trust is established through a cryptographic chain anchored in the Electronic Business Wallet Owner Identity Document (EBWOID). The EBWOID SHALL be included in the header of every EAA. During EBWOID issuance, the EBWOID provider verifies that the public key contained in the EBWOID is owned by the Electronic Business Wallet (EBW) owner.

The Relying Party SHALL verify the EBWOID in accordance with the verification procedure defined in this Rulebook. Upon successful verification, the Relying Party obtains: - assurance that the EBWOID was issued by an authorized provider and is not self-issued; - the verified identity of the issuer, including its name and EUID (or another globally unique EBW owner identifier); and - the public key authorized to verify the EAA signature.

Authorization of the issuer is subsequently determined in accordance with the Relying Party's internal policies. Such authorization MAY be based on locally maintained wallet configuration or on trusted jurisdiction- or domain-specific trust list services that identify issuers authorized for a particular type of EAA

Trust anchor location

The attribute or metadata carrying the trust anchor location contains at least the URL at which a machine-readable version can be found or looked up.

11 References