Skip to content

Identity Rulebook ​

Document FW-RB-0003 · Version 1.0.0 · Status Active · Updated 2026-11-16 · Licence CC BY 4.0 Official English translation of the Turkish source text; in case of conflict the Turkish text prevails.

The rulebook for the personal credentials issued by Tamga's identity service (branching from the Tamga RulebookA set of binding rules. The Tamga Rulebook holds the rules for all participants; each credential type has its own rulebook that branches from it., FW-RB-0001), in the section structure of the EU Attestation Rulebook template: the Tamga identity credential (urn:tamga:id:IdentityAttestation:1; SD-JWT VC + ISO/IEC 18013-5 mdoc), its ZK copy (urn:tamga:id:ShortLivedIdentityAttestation:1), the pseudonym seed (urn:tamga:id:PseudonymSeed:1) and the driving licence information (urn:tamga:id:DrivingLicenceAttestation:1; not an official driving licence). Attributes and metadata, legal category, encoding per format, usage, trust anchors, validity and revocationWithdrawing a credential before it expires; the issuer marks it in a status list that verifiers check., EU compliance. The identity credential is not a PID (Person Identification Data)The core identity data a state issues at the highest assurance level. Tamga does not take this role; its identity credential is not a PID.; it is a non-qualified EAA that uses the EU PID attribute names and encoding.

VersionDateDescription
1.0.02026-10-16Current text of Tamga ARF 1.0, in the section structure of the EU Attestation Rulebook template (version 1.5).

Scheme owner: Tamga Network (today the provisional operator). Feedback: https://github.com/tamga-network/tamga-network/issues

1. Introduction ​

1.1 Scope and purpose ​

This rulebook defines the four personal credential types issued by the Tamga Network identity service (id.tamga.network):

Typevct / docTypeFormatCatalogue
Tamga identity credentialurn:tamga:id:IdentityAttestation:1SD-JWT VC (Selective Disclosure JWT Verifiable Credential)The JSON-based credential format with selective disclosure, used for online presentation in the EUDI Wallet and in Tamga. + mdocThe ISO/IEC 18013-5 mobile document format, encoded in CBOR; used for in-person presentation and for the mobile driving licence. (namespace tamga.id.1)schemas.tamga.network/v1/id/IdentityAttestation/1.0.0
ZK copy (zero-knowledge presentation only)urn:tamga:id:ShortLivedIdentityAttestation:1mdoc only (namespace tamga.id.1)schemas.tamga.network/v1/id/ShortLivedIdentityAttestation/1.0.0 · ADR-0044
Pseudonym seed (never presented)urn:tamga:id:PseudonymSeed:1SD-JWT VC onlyschemas.tamga.network/v1/id/PseudonymSeed/1.0.0 · ADR-0031
Driving licence informationurn:tamga:id:DrivingLicenceAttestation:1SD-JWT VC onlyschemas.tamga.network/v1/id/DrivingLicenceAttestation/1.0.0 · ADR-0039

Purpose. While no PIDThe core identity data a state issues at the highest assurance level. Tamga does not take this role; its identity credential is not a PID. provider has been appointed by a state, a person's identity is verified remotely once and carried in the wallet as a selectively disclosable, device-bound credential: institutions match the person against their own records, websites ask for age or "is there a valid identity", and the person discloses only what is needed.

Status. The identity credential is not a PID: it is a non-qualified EAA (Electronic Attestation of Attributes)The eIDAS term for a credential that attests attributes of a person, such as a degree or a membership. that Tamga issues on a provisional basis (ADR-0011, ADR-0022); pid_providers[] in the trust listA signed list of a country's root certificates, issuers and registered relying parties. Today trust in Tamga rests on these lists; a shared ledger comes later. stays empty. When a state provider is appointed, no new credentials are issued and the registration is handed over to the successor (§4.7). The driving licence information is not an official driving licence and not an mDL (mobile Driving Licence)A driving licence held in a wallet in the mdoc format (ISO/IEC 18013-5). (§4.8).

The technical definition is in SPEC-ID-0003 §9 and in the schema catalogue; in case of conflict they prevail. This rulebook sets no new rules; it collects ADR-0011, ADR-0013, ADR-0039, ADR-0044, ADR-0045, SPEC-ID-0003 and the RB-AP-ID rules of the Tamga Rulebook (Annex B) in the order of the EU template.

1.2 Document structure ​

Chapter 2 defines the attributes and metadata independently of the format; Chapter 3 the encoding per format (ISO/IEC 18013-5, SD-JWT VC, W3C VCDM); Chapter 4 usage, issuance conditions and the verifier's obligations; Chapter 5 trust anchors; Chapter 6 validity and revocation; Chapter 7 EU compliance and open decisions.

1.3 Key words ​

MUST, MUST NOT, SHOULD and MAY have their RFC 2119 meaning (Tamga Rulebook §0). Lower-case "must" describes a requirement set by an external document.

1.4 Terminology ​

Terms are in Annex D; EU terms have their meaning in ARF Annex 1.

2. Attributes and metadata ​

2.0 EU requirements and where they are met ​

RequirementWhere
Indication that it is an EAA (ARB_12)§2.1 — no category is written; under ETSI TS 119 472-1 V1.2.1 EAA-5.2.2.1-01 the absence is the indication of a non-qualified EAA; the template's value eaa:eu:non-qualified is not used (ADR-0047 K6)
Identity of the issuer, Annex V b (ARB_15)iss (the issuer's address) and the x5c leaf certificate in the signature header (organisation name, country); issuer_id is the certificate fingerprint (§2.5, §5)
Identity of the subject, Annex V c (ARB_17)Identity credential: family_name, given_name, birthdate, personal_administrative_number. Driving licence information: family_name, given_name, birth_date. The ZK copy and the pseudonym seed deliberately carry no subject identity (§2.2)
Start and end of validity, Annex V e (ARB_19)SD-JWT VC iat, exp; mdoc validityInfo (validFrom, validUntil)
Location of the trust anchor, Annex V h (ARB_21)No separate attribute in the credential, and none is added; the location is the issuer's certificate chain and the Tamga trust lists (§5); the lists are the single source of trust anchors (ADR-0047 K7)

The identity credential uses the attribute names and encoding of the EU PID (Implementing Regulation (EU) 2026/1731; ADR-0045); the type and namespace are Tamga's. All personal attributes are selectively disclosable; there is no portrait, address, document image or assurance level (LoA (Level of Assurance)How much confidence can be placed in an identity or a credential; Tamga uses separate levels for proofing (T), issuer (I) and wallet (W).) attribute. The national identity number exists only in this type (RB-AP-ID-04, RB-SCH-04).

Legal category (category). The EU Attestation Rulebook template (1.5) and ETSI TS 119 472-1 define the category attribute for QEAAs and PuB-EAAs (urn:etsi:esi:eaa:eu:qualified, urn:etsi:esi:eaa:eu:pub; its former name in the ARF text is attestation_legal_category, ARB_25). Tamga uses this name with its own values (urn:tamga:eaa:qualified, urn:tamga:eaa:pub) only for issuers whose registered class is qualified or public (RB-AP-14). The identity service is in the non-qualified EAA / I2 class (ADR-0022); none of the four types in this rulebook carries category (MUST NOT, RB-AP-ID-04). ETSI TS 119 472-1 (EAA-5.2.2.1-01) requires category to be absent in a non-qualified, non-public EAA; that the credential is a non-qualified EAA follows from this absence and from the issuer's class in the trust list.

2.2 Mandatory attributes ​

Identity credential (IdentityAttestation)

Data identifierDefinitionData typeExample value
family_nameFamily namestring (1–150)Yılmaz
given_nameGiven namestring (1–150)Ayşe
birthdateDate of birthdate (YYYY-MM-DD)1990-04-12
nationalitiesNationalities; unknown QU, stateless QSarray of ISO 3166-1 alpha-2 (at least one)["TR"]
personal_administrative_numberNational identity number; only in this typestring (5–32)12345678901
document_typeType of the verified documentID_CARD | PASSPORT | RESIDENCE_PERMIT | DRIVING_LICENSEID_CARD
document_number_hashKeyed digest of the document number (HMAC-SHA256; the key stays in the identity service); the number itself is absent and cannot be recoveredsha256-…sha256-q1…
issuing_countryIn the EU PID sense, the country of the provider that issued the credential; today the value is the country that issued the scanned identity document (§4.6)ISO 3166-1 alpha-2TR
document_chip_verifiedWhether the chip path fully passed: passive authentication of the chip, the clone check and the match of the live face with the chip photo, together (a fact, not a level; ADR-0083)booleantrue
verification_methodHow identity was verified; review-demo only in the demo credential issued for app store reviewremote-document-liveness-face | remote-nfc-liveness-face | in-person | review-demoremote-document-liveness-face

ZK copy (ShortLivedIdentityAttestation)

Data identifierDefinitionData typeExample value
age_over_18Whether the person is over 18; the only element that can be proven with ZKbooleantrue
age_over_15Whether the person is over 15; an element that can only be proven with ZK (ADR-0064)booleantrue

Pseudonym seed (PseudonymSeed)

Data identifierDefinitionData typeExample value
pseudonym_seedSeed for deriving per-site pseudonyms; derived from the person's stable identity with a separate key, never stored (RB-AP-ID-07)base64url, 43 charactersQm9…

Driving licence information (DrivingLicenceAttestation)

Data identifierDefinitionData typeExample value
family_nameFamily namestring (1–200)Yılmaz
given_nameGiven namestring (1–200)Ayşe
issuing_countryCountry that issued the cardISO 3166-1 alpha-2TR
document_number_hashKeyed digest of the card numbersha256-…sha256-Zx…
driving_privilegesCategories: [{ category, issue_date?, expiry_date? }]; EU 2006/126 category codes, national additions as printed (1–32 items)array of objects[{"category":"B","issue_date":"2010-06-01"}]
licence_expiry_dateExpiry date of the carddate2034-06-01
verified_atDay the card was inspecteddate2026-10-11
verification_methodHow the card was inspectedremote-document-liveness-faceremote-document-liveness-face
not_official_licenceExplicit indication that this is not an official driving licence; always trueconstant truetrue

driving_privileges[].category is the driving licence category; it has nothing to do with the legal category in §2.1.

2.3 Optional attributes ​

TypeData identifierDefinitionData typeExample value
Identity credentialage_over_18Derived from the date of birth; in age verification only this attribute is disclosed. Not in the EU PID set; a Tamga attribute with the ISO/IEC 18013-5 name (ADR-0045 K3)booleantrue
Identity credentialage_over_15Derived from the date of birth with the same rule; ISO/IEC 18013-5 age_over_NN pattern. The identity credential's age thresholds are a closed set (15, 18); a new threshold is added only by ADR (ADR-0064 K2)booleantrue
Driving licence informationbirth_dateDate of birth if on the card (ISO/IEC 18013-5 mDL name)date1990-04-12
Driving licence informationlicence_issue_dateIssue date of the card (if present)date2024-06-01
Driving licence informationage_over_18Derivedbooleantrue

2.4 Conditional attributes ​

None.

2.5 Mandatory metadata ​

Data identifierDefinitionData typeExample value
issThe issuer's address (identity service)URIhttps://id.tamga.network
vctType (SD-JWT VC); the mdoc docType is the same valueURNurn:tamga:id:IdentityAttestation:1
vct#integrityDigest of the type definition in the catalogue (RB-SCH-01)sha256-…sha256-…
iatMoment of issuance; mdoc validityInfo.signedNumericDate1791763200
expEnd of validity; mdoc validityInfo.validUntil (§6.1)NumericDate1854835200
cnfThe wallet's device key (holder binding); mdoc deviceKeyInfoJWK—
statusStatus list reference status_list {idx, uri}; absent in the ZK copy and the pseudonym seed (§6.2)object{"status_list":{"idx":48213,"uri":"https://status.tamga.network/7f3a9c21"}}

The identity of the issuer (Annex V b) is in the signature header: x5c (leaf + intermediate certificate, root excluded).

2.6 Optional metadata ​

Data identifierDefinitionData typeExample value
nbfTechnical start of validity; in mdoc validityInfo.validFrom; the issuer writes it at issuance: the value is the same moment as iat (rounded down to the hour), or the moment validity starts for a future-dated credential. A credential whose start has not been reached is stored in the wallet as "not yet valid" and cannot be presented; a verifier rejects itNumericDate1791763200

2.7 Conditional metadata ​

category is absent in these types (§2.1).

3. Encoding ​

3.1 ISO/IEC 18013-5 (mdoc) ​

Proximity analysis (ARB_02). Identity may need to be shown in person and offline (an institution's registration desk, an age check at a door); the identity credential is therefore also issued as an ISO/IEC 18013-5 mdoc (ADR-0013). The driving licence information is not used in official checks and is not issued as an mdoc (ADR-0039); the pseudonym seed is never presented. The ZK copy is mdoc only.

TypedocTypeNamespace
Identity credentialurn:tamga:id:IdentityAttestation:1tamga.id.1
ZK copyurn:tamga:id:ShortLivedIdentityAttestation:1tamga.id.1

Encoding rules: tstr, uint, bool and full-date as in RFC 8610 / RFC 8943; full-date = #6.1004(tstr). tstr is UTF-8. Element values are the same as in the SD-JWT VC except for dates. The MSO carries digestAlgorithm SHA-256, validityInfo (signed, validFrom, validUntil; tdate, no fractional seconds, time zone Z), deviceKeyInfo and the status list reference status.status_list {idx, uri} (the same bit as the SD-JWT copy; the address is the CWT representation of the same list — application/statuslist+cwt, ADR-0048 K3, packages 0.6.0). The signature is ES256 (COSE); x5chain is the same issuer certificate.

Data identifierElement identifierEncodingNamespace
family_namefamily_nametstrtamga.id.1
given_namegiven_nametstrtamga.id.1
birthdatebirth_datefull-datetamga.id.1
nationalitiesnationality[+ tstr] (array of alpha-2)tamga.id.1
personal_administrative_numberpersonal_administrative_numbertstrtamga.id.1
document_typedocument_typetstrtamga.id.1
document_number_hashdocument_number_hashtstrtamga.id.1
issuing_countryissuing_countrytstrtamga.id.1
document_chip_verifieddocument_chip_verifiedbooltamga.id.1
verification_methodverification_methodtstrtamga.id.1
age_over_18age_over_18booltamga.id.1
age_over_15age_over_15booltamga.id.1

Names and encoding follow EU PID Table 6 (ADR-0045 K2); the name table is in the open packages (@tamga-network/core/pid). The namespace tamga.id.1 is a Tamga-specific namespace (ARB_10): the credential is not a PID, so eu.europa.ec.eudi.pid.1 is not used.

Example (identity credential, elements disclosed for age only):

text
docType: "urn:tamga:id:IdentityAttestation:1"
nameSpaces: { "tamga.id.1": [ { elementIdentifier: "age_over_18", elementValue: true } ] }
MSO.validityInfo: { signed: 2026-10-11T08:00:00Z, validFrom: 2026-10-11T08:00:00Z, validUntil: 2028-10-10T08:00:00Z }
MSO.status: { status_list: { idx: 48213, uri: "https://status.tamga.network/7f3a9c21" } }

3.2 SD-JWT VC ​

The credentials are issued as SD-JWT VCThe JSON-based credential format with selective disclosure, used for online presentation in the EUDI Wallet and in Tamga. following the SD-JWT VC profile of HAIP 1.0 (ARB_01b): header alg ES256, typdc+sd-jwt, x5c; _sd_alg sha-256; no decoy digests. vct is a URN (urn:tamga:<domain>:<Type>:<major>) and unique in the network (ARB_05); the type definition (Type Metadata) comes from the catalogue and vct#integrity is mandatory (ARB_31, RB-SCH-01).

The "Disclosable" column is the sd value in the Type Metadata: MUST = always, MAY = allowed, MUST NOT = never (ARB_30). Array elements are disclosed one by one (path: ["nationalities", null] for nationalities, RFC 9901 §4.2.2).

Identity credential — IANA-registered names

Data identifierClaim nameEncodingReferenceDisclosable
family_namefamily_namestringOpenID Connect Core §5.1MUST
given_namegiven_namestringOpenID Connect Core §5.1MUST
birthdatebirthdatestring, YYYY-MM-DDOpenID Connect Core §5.1MUST
nationalitiesnationalitiesarray of strings (alpha-2), each element separatelyOpenID Connect for Identity Assurance §4.1MUST (each element)

Identity credential — EU PID names and Tamga-specific names

Data identifierClaim nameEncodingNotesDisclosable
personal_administrative_numberpersonal_administrative_numberstringEU PID nameMUST
issuing_countryissuing_countrystring (alpha-2)EU PID name (§4.6)MUST
document_typedocument_typestring (set)Tamga-specificMUST
document_number_hashdocument_number_hashstring sha256-…Tamga-specificMUST
document_chip_verifieddocument_chip_verifiedbooleanTamga-specificMUST
verification_methodverification_methodstring (set)Tamga-specificMUST
age_over_18age_over_18booleanISO/IEC 18013-5 nameMUST
age_over_15age_over_15booleanISO/IEC 18013-5 name (ADR-0064)MUST
iss, vct, vct#integrity, iat, exp, cnf, statussame—transport profileMUST NOT

Pseudonym seed

Data identifierClaim nameEncodingNotesDisclosable
pseudonym_seedpseudonym_seedstring (base64url)Tamga-specific; never in any verifier's scopeMUST NOT (the credential is never presented)

Driving licence information

Data identifierClaim nameEncodingNotesDisclosable
family_name, given_namesamestringOpenID Connect Core §5.1MUST
birth_datebirth_datestring, YYYY-MM-DDISO/IEC 18013-5 mDL name (ADR-0045 K4)MUST
issuing_countryissuing_countrystring (alpha-2)ISO/IEC 18013-5 mDL nameMUST
document_number_hashsamestring sha256-…Tamga-specificMUST
driving_privilegessamearray of objectsISO/IEC 18013-5 mDL name; the official mDL namespace is not used (RB-AP-ID-08)MUST
licence_issue_date, licence_expiry_datesamestring, YYYY-MM-DDTamga-specificMUST
verification_method, age_over_18samestring / boolean—MUST
verified_atsamestring, YYYY-MM-DDTamga-specificMUST NOT
not_official_licencesameconstant trueTamga-specific; visible in every presentationMUST NOT

Example (identity credential; the JWT claim set with disclosures resolved):

json
{
  "iss": "https://id.tamga.network",
  "vct": "urn:tamga:id:IdentityAttestation:1",
  "vct#integrity": "sha256-…",
  "iat": 1791763200,
  "exp": 1854835200,
  "cnf": { "jwk": { "kty": "EC", "crv": "P-256", "x": "…", "y": "…" } },
  "status": { "status_list": { "idx": 48213, "uri": "https://status.tamga.network/7f3a9c21" } },
  "family_name": "Yılmaz",
  "given_name": "Ayşe",
  "birthdate": "1990-04-12",
  "nationalities": ["TR"],
  "personal_administrative_number": "12345678901",
  "document_type": "ID_CARD",
  "document_number_hash": "sha256-…",
  "issuing_country": "TR",
  "document_chip_verified": false,
  "verification_method": "remote-document-liveness-face",
  "age_over_18": true,
  "age_over_15": true
}

In the issued credential each personal attribute is a separate disclosure; each element of the nationalities array is a separate disclosure too. Encoded credentials and disclosure examples are in the conformance vectors (conformance/vectors/sd-jwt).

3.3 W3C VCDM ​

Not used: Tamga does not use a JSON-LD carrier.

4. Usage ​

4.1 Use cases and the attributes a verifier asks for ​

UseAttributes requestedRule
Age verificationage_over_18 or age_over_15 (one threshold)No other attribute is requested; the two thresholds are not requested together, as that reveals an age range (ADR-0064 K3); in the browser via mdoc, optionally a zero-knowledge proof with the ZK copy
Matching at an institution (before issuance)personal_administrative_number, birthdate, given_name, family_nameThe institution's issuance service receives them only within its registered scope and through the full verification pipeline; it does not store or log the matching keys (RB-RP-ID-01)
"Is there a valid Tamga identity"noneReference policy event-tamga-id
Sign-up and sign-in on a website ("Sign in with Tamga")at sign-up given_name, family_name; at sign-in noneThe account key is a per-site pseudonym; document_number_hash and the identity number are not requested (RB-RP-13)
High-risk transactionper its scopeIf face matching is needed it is the verifier's responsibility; the credential carries no portrait (RB-RP-11)
Driving licence categoriesdriving_privileges and what is neededNot used in official checks or official procedures; the screen says "does not replace an official driving licence" (§4.8)

Requesting a PID (ARB_27). A verifier that accepts these types does not need to request a PID as well. Accepting a state PID for matching, once one exists, is opened by a separate decision.

4.2 Issuance policy ​

RequirementIdentity credential, ZK copy, pseudonym seedDriving licence information
IssuerOnly the identity service (id.tamga.network); institutions cannot issue these typessame
Category · classIDENTITY · EAA · I2 (ADR-0022)same
Type authorisationOnly in the identity service's registration (allow-list)same
KeyThe identity service's credential signing key; the status list key is separate (RB-AP-03)same
PrerequisiteIdentity proofing (§4.3); the ZK copy and the seed only together with the identity credential or with its refresh tokenThe wallet presents an active Tamga identity credential (given name, family name, date of birth); the name and date of birth on the card must match it (RB-AP-ID-09)
CopiesIdentity credential: 10 copies, each bound to a separate device key; a separate copy per verifier (ARF method D). ZK copy in small batches (at most 3)10 copies
WalletBefore issuance the wallet instance attestation (WIA) and key attestation (KA) are verified against wallet_providers[] (RB-AP-10)same
App store reviewSeparate demo signer tamga-id-review (I1; verification_method: review-demo, at most 7 days); only with a single-use review code; passes no policy that requires I2—
Embedded disclosure policyNot carried (ADR-0046 K1)Not carried

4.3 Identity proofing before issuance ​

RouteLevelNote
Remote: document, liveness and face matchingT2 (ETSI TS 119 461 Substantial)verification_method: remote-document-liveness-face
Remote with NFC chipT2; document_chip_verified: trueTechnically high; legally T3 is a qualified electronic signature
In personT2in-person

Rules: identity proofing happens only in the identity service; institutional issuersThe institution that signs and issues credentials: a university, a professional body, a public institution or a company., wallets and verifiers do not talk to the remote identity proofing provider (RB-AP-ID-01); a wallet may only read the identity document chip and relay the raw data unchanged to the identity service, which does the verification (ADR-0083; the chip path opens after a legal opinion). Before proofing starts, the privacy notice is shown and explicit consent is obtained (RB-AP-ID-02). The provider's decision is always confirmed at the provider's decision endpoint; a notification (webhook) is only a trigger. A provider outage does not lower the level; issuance stops. The level is not written into the credential (RB-AP-14).

There is no age limit (ADR-0043): no minimum age is required for the identity credential; the requirement is identity proofing with a valid identity document. A parental consent flow for children is handled by a separate decision after legal review.

4.4 Data protection ​

  • Tamga is the data controller for this data.
  • Personal attributes are not kept after issuance; the only persistent record is an opaque subject_ref, the document number digest, the validity period and the status list positions. Document images, selfies, video and raw OCR data are never stored by Tamga (RB-AP-ID-03).
  • An erasure request revokes the credential.
  • No second active identity credential is issued for the same document number; re-verification revokes the old one (RB-AP-ID-05).

4.5 Presentation and the verifier's obligations ​

  • Presentation only with OpenID4VP (OpenID for Verifiable Presentations)The protocol a verifier uses to request a credential from a wallet and receive the presentation. and DCQL (Digital Credentials Query Language)The query language a verifier uses in OpenID4VP to say which credentials and which fields it needs., a signed request and an encrypted response (RB-RP-02); the verifier chooses the format with DCQL (for example, age verification in the browser asks for age_over_18 only, via mdoc). In proximity the ISO/IEC 18013-5 flow is used.
  • Verification goes through the canonical pipeline: freshness of the trust source, then signature, issuer, type authorisation, revocation and wallet binding (RB-RP-03). The issuer must appear in the trust list in the IDENTITY category and authorised for this type.
  • A verifier that asks for the identity number must have this attribute explicitly in its registration; the wallet warns about out-of-scope requests.
  • The result has three values; INDETERMINATE is not acceptance (RB-RP-05).
  • ZK copy: the proof binds the type, so the verifier sees the short lifetime and expects no revocation check (status: NOT_APPLICABLE, reason: short-lived). A ZK presentation without this type (unmarked) is accepted only if the policy explicitly allows it (RB-AP-ID-11, ADR-0044).
  • The pseudonymA stable account identifier the wallet derives separately for each website; two sites cannot link the same person. seed is in no verifier's scope; the wallet derives per-site pseudonyms from it (RB-AP-ID-07).
  • Transactional data (ARF Topic 20, payments) is not defined for these types.

4.6 Relation to the EU PID and mDL ​

Tamga verifiers recognise the EU person identification data (PID) and the ISO driving licence (mDLA driving licence held in a wallet in the mdoc format (ISO/IEC 18013-5).) as external types:

TypeFormat
urn:eudi:pid:1SD-JWT VC
eu.europa.ec.eudi.pid.1mdoc
org.iso.18013.5.1.mDLmdoc
  • Recognition condition. An external type is accepted only if its issuer is in scope of an external list that vouches for that type (Annex A §6.1). Today the list of lists contains no external list; each one is added by a separate decision.
  • Nested selective disclosureShowing only the fields a verifier asks for from a credential, and nothing else.. In the EU PID the address is an object and the nationalities are an array. The person can disclose only what is needed: for example only the city of the address, or one of the nationalities. The verifier's scope check applies to the attribute itself or to its parent.
  • Age. The EU PID has no age attribute; in the EU a separate age verification credential is used for age. The mDL has age elements such as age_over_18. The Tamga identity credential follows the same age_over_NN pattern; the threshold set is closed: 15 and 18 today (ADR-0064).
Tamga identity credential (SD-JWT VC)Tamga identity credential (mdoc, tamga.id.1)EU PID (SD-JWT VC)EU PID (mdoc)
given_namegiven_namegiven_namegiven_name
family_namefamily_namefamily_namefamily_name
birthdatebirth_date (full-date)birthdatebirth_date (full-date)
nationalities (array)nationality (array)nationalities (array)nationality (array)
personal_administrative_numberpersonal_administrative_numberpersonal_administrative_numberpersonal_administrative_number
issuing_country (country that issued the document)issuing_countryissuing_country (country of the PID provider)issuing_country
age_over_18age_over_18— (separate age verification credential)—
age_over_15age_over_15— (separate age verification credential)—
document_type, document_number_hash, document_chip_verified, verification_methodsameno equivalent (Tamga-specific)no equivalent
no equivalentno equivalentplace_of_birth (place of birth: country, region, locality; mandatory)place_of_birth
no equivalent (the issuer is known from iss and the x5c certificate)no equivalentissuing_authority (mandatory metadata)issuing_authority
date_of_expiry (administrative expiry; separate from the copy's technical exp)expiry_datedate_of_expiry (optional)expiry_date
no equivalentno equivalentdate_of_issuance (optional)issuance_date

issuing_country (2026-10-11, project management decision). The attribute has its EU PID meaning: the country of the identity provider that issued the credential (Implementing Regulation (EU) 2026/1731). Because today Tamga's identity service issues the credential itself on the basis of a scanned identity document, the value reflects the country that issued the scanned document. When a state PID provider issues PIDs, the attribute carries the EU meaning and the documents describe it with the EU definition. Code and schema do not change today. The difference in meaning, stated plainly: in the EU PID the value is the country of the state that issued the PID; in Tamga the issuer is the identity service (Tamga), so the value shows the state that issued the identity card or passport.

PID attributes with no equivalent (2026-11-16). place_of_birth and issuing_authority are mandatory in the EU PID; the Tamga identity credential does not carry them today. Adding the place of birth is a separate decision that depends on whether the identity verification provider supplies it reliably; issuing_authority is filled with the name of a state PID provider when one arrives (§4.7). A verifier therefore cannot use the Tamga identity credential in place of an EU PID. The administrative expiry is written as date_of_expiry (mdoc expiry_date), separate from the copy's technical exp (ADR-0089 K2); date_of_issuance is not written (§6.1).

4.7 Hand-over — state PID provider ​

When a state appoints a PID provider: the identity service's registration is handed over with successor_id and no new credentials are issued; credentials already issued remain valid until they expire (RB-AP-ID-06). Verifier policies are updated to prefer the state PID; this type becomes DEPRECATED but stays verifiable.

4.8 Driving licence information — additional rules ​

The person's physical driving licence card is inspected remotely (document + liveness + face matching) and the categories and dates on the card are issued as a credential (ADR-0039). It is not an official driving licence and not an mDL; it is not used in traffic checks or official procedures. The credential always says so, with the explicit not_official_licence attribute, its display name ("Driving licence information — does not replace an official driving licence") and its card; verifier screens show the same statement (RB-AP-ID-08).

TopicRule
MatchingIf the name and date of birth on the card do not match the identity credential, the card is not a driving licence, it has expired or the categories cannot be read, no credential is issued (RB-AP-ID-09)
AbsentNational identity number, restriction and health codes (field 12; not even a has_restrictions fact), photo, signature, address; the provider's note fields are not read
Data protectionTamga is the data controller; the privacy notice and explicit consent are specific to the driving licence; personal attributes are not kept after issuance; name and date of birth are not sent to the provider, matching is done in the identity service with a keyed digest
Competent authorityOnce a country's competent authority starts issuing digital driving licences, Tamga stops issuing this type for that country; the registration points to the official type with successor (RB-AP-ID-10)
LawLegal review before issuance to real people is opened; the sandbox does not wait for it

4.9 Device binding ​

All four types are device-bound (ARB_34): each copy is bound to a separate key in the wallet's secure hardware (cnf / deviceKeyInfo; RB-AP-09, RB-WP-01). The cryptographically_bound_to attribute is not used: the link between the driving licence information and the identity credential is established by the presentation at issuance and kept by revocation (§6.2); there is no cryptographic binding in the credential.

5. Trust anchors ​

These types are non-qualified EAAs; the trust anchor comes from Tamga's signed trust lists, not from the EU trusted list (ARB_26):

  1. The verifier fetches in advance the list of lists (https://trust.tamga.network/lotl.jws) and the national list (tl-tr.jws) and verifies their signatures against the root certificates. The root fingerprints are published with the same values on the tamga.network/trust-anchor page, in keys/root-fingerprints.json and in the Trust Framework (RB-OP-06).
  2. The credential's x5c chain (x5chain in mdoc) chains to the national root; issuer_id is derived from the fingerprint of the leaf certificate, not from iss (RB-AP-01, RB-RP-04).
  3. The tl-tr › issuers[] entry gives the issuer, its category (IDENTITY), its class and its time-windowed authorisation for this type; the check uses the moment of issuance (iat) (RB-RP-03).
  4. The type is verified with the lotl › schemas[] entry and the content_hash in the catalogue (= vct#integrity).

At issuance the wallet checks against the same entry that the issuer is authorised to issue this type. The trust anchor of external types (§4.6) comes only from the external list.

6. Validity and revocation ​

6.1 Validity policy ​

TypeValidity
Identity credentialexp = moment of issuance + 730 days (at most 2 years); re-verification when it expires
ZK copyAt most 24 hours and never beyond the main credential's expiry (RB-AP-ID-11)
Pseudonym seed730 days; renewed together with the identity credential
Driving licence informationexp = the earlier of the card's expiry and 1 year after the inspection; automatic renewal does not extend it (RB-AP-ID-09)
Demo credential (review-demo)At most 7 days

Technical and administrative validity are separate: the identity credential's administrative expiry is in date_of_expiry (mdoc expiry_date); a copy's exp is its technical validity and may be shorter (ADR-0089 K2; §4.6).

6.2 Revocation ​

TypeRevocableMechanism
Identity credentialYes, mandatoryToken Status List (the EU Attestation Status List); the mdoc and SD-JWT copies carry the same bit (the mdoc copy reads the CWT representation of the list)
ZK copyNo — the short lifetime replaces revocation (ARF VCR_01); if the main credential is revoked no new copy is issued, and revocation takes effect for ZK presentations within 24 hours at most—
Pseudonym seedNo status list; never presented—
Driving licence informationYes, mandatoryToken Status List
  • Status list address (ARB_24a): status.status_list.uri in each credential; the identity service's lists are under https://status.tamga.network/. The address is opaque and encodes no institution, year or group (RB-AP-18).
  • Publication: at a fixed interval (today 2 minutes), even without changes; a list is valid for 6 hours; there is no out-of-cycle publication (RB-AP-17, SPEC-CRED-0003 §5). Revocation takes effect within minutes (RB-GEN-10).
  • Values: bits = 1 — valid or revoked. The identity service's types have no suspension, and revocation is permanent (the EU PID rule; RB-AP-ID-13, ADR-0048 K1). Until release 0.6.0 of the packages the lists are published as bits = 2, but no suspension value is written.
  • Revocation conditions: in the Revocation Policy (FW-POL-0001 §3). For the identity credential: the person's erasure request, re-verification with the same document, a report that the document was lost or stolen, an incorrect credential, withdrawal of consent. For the driving licence information in addition: re-verification with the same card, revocation of the wallet unit, and revocation, re-issuance or deletion of the linked identity credential (chained; RB-AP-ID-10).
  • Attestation Revocation List (the EU's second mechanism) is not published today (§7.2).

7. Compliance ​

7.1 Relation to the EU framework ​

  • This rulebook follows the section structure of the EU Attestation Rulebook template (1.5) (ARB_29). The mapping of the template to the Topic 12 requirements is in Tamga Rulebook §11.
  • The identity credential uses the attribute names and encoding of the EU PID (Implementing Regulation (EU) 2026/1731; ADR-0045) but is not a PID; the PID Rulebook's requirements specific to PID providers (type eu.europa.ec.eudi.pid.1, the urn:eudi:pid: namespace, portrait) do not apply.
  • The driving licence information is outside the scope of the EU mDL Rulebook: an official mDL is issued only with ISO/IEC 18013-5 and the official namespace; Tamga does not use that namespace (RB-AP-ID-08).
  • These types inherit all rules of the Tamga Rulebook; the type-specific rules are RB-AP-ID-01…13 and RB-RP-ID-01.

7.2 Known differences and open decisions ​

TopicStatus
Indication of a non-qualified EAA (ARB_12)Decision (2026-10-12, ADR-0047 K6): the EU template suggests the category value eaa:eu:non-qualified; ETSI TS 119 472-1 V1.2.1 EAA-5.2.2.1-01 requires category to be absent in a non-qualified EAA. Tamga follows ETSI; the template's value is not used
Trust anchor location in the credential (ARB_21)Decision (2026-10-12, ADR-0047 K7): no location attribute is added; the location is the lists in §5. A location in the credential would be the issuer's own claim; a verifier takes the anchor only from a list it chose itself, with a pinned signature
nbf (ETSI TS 119 472-1 technical start of validity)The issuer writes it at issuance (§2.6); a credential whose start has not been reached is stored in the wallet and not presented
Attestation Revocation ListTamga issuers publish the Status List (one is enough under EU VCR_11); the verifier and the wallet core also verify the identifier list (packages 0.5.0; FW-POL-0001 §8)

8. References ​

The EU Attestation Rulebook template and the PID and mDL rulebooks (the EU attestation rulebooks catalogue), ARF Annex 2 Topics 7, 10 and 12, Implementing Regulation (EU) 2026/1731, ETSI TS 119 472-1, ISO/IEC 18013-5, SD-JWT VC, HAIP 1.0, IETF Token Status List. The Tamga decisions and specifications this document rests on are listed in Annex E.

Status ​

Active — version 1.0.0 (16 October 2026).

Tamga ARF 1.0 · CC BY 4.0 · The Turkish text is the source; this is its official translation