> ## Documentation Index
> Fetch the complete documentation index at: https://tfh-soam-docs3-qa2-7-newsletter.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# NFC Credential

> A unique government-issued document, such as a passport or eID.

| Property         | Value                                                                                                                             |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Issued by        | [Tools for Humanity](https://www.toolsforhumanity.com) (verified issuer)                                                          |
| Status           | Active                                                                                                                            |
| ID               | `9303`                                                                                                                            |
| Sybil resistance | Yes — each document can only be used with one World ID; duplicate enrollments for the same document are rejected.                 |
| Validity period  | Document expiry, max 10 years (the default duration of the credential; generally the maximum recommended sybil resistance window) |
| SDK Reference    | Coming soon                                                                                                                       |

## Introduction

The NFC Credential represents a unique government-issued document. It supports passports and eIDs. Availability varies by country and continues to expand over time. An NFC Credential is **guaranteed to be issued to a single World ID per unique document**. In addition to ICAO-9303 compliant documents (such as passports or eIDs), the Japanese [My Number Card](https://en.wikipedia.org/wiki/My_Number_Card) (MNC) is also supported. The MNC flow uses different enrollment handling internally, but it issues the same credential.

## Use Cases

Use the NFC Credential when you need proof of a unique government document. This is useful for applications that need document-level Sybil resistance without requiring a proof of a unique human.

## Credential Structure

This credential implements the following attributes beyond the defaults in the [Credential](https://docs.rs/world-id-primitives/latest/world_id_primitives/credential/struct.Credential.html).

<table>
  <thead>
    <tr>
      <th className="whitespace-nowrap">Attribute</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td className="whitespace-nowrap">
        <code>genesis\_issued\_at</code>
      </td>

      <td>The timestamp of when the unique document was first verified.</td>
    </tr>

    <tr>
      <td className="whitespace-nowrap">
        <code>expires\_at</code>
      </td>

      <td>The expiration of the document with a maximum of 10 years.</td>
    </tr>

    <tr>
      <td className="whitespace-nowrap">
        <code>associated\_data\_commitment</code>
      </td>

      <td>
        A commitment to the user's Associated Data (see{" "}

        <a href="/world-id/reference/nfc-issuer#associated-data">
          NFC Issuer implementation notes
        </a>

        ).
      </td>
    </tr>
  </tbody>
</table>

In addition, the credential implements the following claims:

### Claim 0 - Authentication Claim

Identifies the type of authentication performed when enrolling a document. This helps determine the state of the document at enrollment time. For example, documents that only undergo Passive Authentication have no guarantee that the data isn't cloned from an original document. Please note that not all authentications are supported for all documents, and it usually varies per country. The strongest authentication available is always selected.

| Value | Claim                 | Description                                                                                        |
| ----- | --------------------- | -------------------------------------------------------------------------------------------------- |
| `1`   | None                  | Passive authentication only (document signature verification).                                     |
| `2`   | Chip Authentication   | Document passed Chip Authentication (CA) per ICAO 9303. Proves the chip is genuine and not cloned. |
| `3`   | Active Authentication | Document passed Active Authentication (AA) per ICAO 9303. Proves the chip holds a private key.     |
| `4`   | MNC Authentication    | Document was verified via the MNC (My Number Card) SD-JWT flow.                                    |

### Claim 1 - SOD Signature

Contains a hash of the document's signature from the issuing authority. For passports and other ICAO-9303 compliant documents, the signature is retrieved from `SignedData.SignerInfos[0].Signature` in the `EF.SOD` (Security Object Document) (see [Section 4.6.2.1 from ICAO-9303 Part 10](https://www.icao.int/sites/default/files/publications/DocSeries/9303_p10_cons_en.pdf)). The raw signature bytes are then hashed with blake3 and converted to a field element with modulo reduction. Please note that this claim is not set for credentials from My Number Cards.

## Credential Renewal

Renewal is not supported for this credential. A document can only be enrolled once. From a user standpoint, they will generally obtain a new document from their issuing authority (e.g. a new passport) and register it as a new credential.

## Technical Reference

For issuer endpoints, migration payloads, and implementation-specific details, see the [NFC Issuer reference](/world-id/reference/nfc-issuer).