# UNTP Digital Conformity Credentials for Textile Transaction Certificates

## Executive Summary

UNTP DCC transforms textile Transaction Certificates from static files into machine-verifiable credentials.  
Reeco exports TC verification results as UNTP DCC `0.6.1`, including cryptographic JWT signing.

## What a DCC Is

A DCC (Digital Conformity Credential) is a W3C Verifiable Credential describing conformity evidence.  
In textile use cases, it represents third-party certification evidence (for example GRS, RCS, OCS, GOTS).

## Reeco DCC Export Flow

### Step-by-Step

1. Verify TC data and issuer coherence.
2. Map verified fields into UNTP DCC structure.
3. Attach scheme metadata and assessed product details.
4. Optionally sign as JWT with `did:web` identity.

### Core API Endpoints

| Endpoint | Purpose |
|---|---|
| `POST /api/v1/dpp/export/dcc` | Build UNTP DCC JSON-LD |
| `POST /api/v1/dpp/export/dcc/jwt` | Build and sign DCC as JWT VC |
| `GET /.well-known/did.json` | Publish public key for independent verification |

## Why It Matters

| Value Area | Benefit |
|---|---|
| Interoperability | Credential format aligned with UNTP |
| Auditability | Structured fields and evidence links |
| Trust | Cryptographic verification with `did:web` |
| Portability | Reusable by external verifiers and partners |

## Supported Schemes

- GRS
- RCS
- OCS
- GOTS

## Competitive Positioning

Most textile solutions stop at certificate storage or PDF exchange.  
DCC export creates a higher-trust, machine-readable compliance layer suitable for ecosystem-level verification.

## FAQ

### Is DCC the same as a PDF certificate?

No. DCC is structured, machine-readable, and can be cryptographically verifiable.

### Why sign DCC as JWT?

To allow integrity checks and issuer authentication by external systems.

### Can DCC be linked to DPP and DTE?

Yes. That is the basis for end-to-end linked compliance evidence.