Workflows

Chip Initialization

Learn how to arm physical NFC anchors. This step rotates default factory keys into brand-specific deterministic AES-128 secrets and registers the hardware inside the V-Ledger repository.

The Mutual Auth Loop

The Toolbox App orchestrates this entire workflow. By using our proprietary key diversification strategy, every NTAG 424 DNA is completely distinct and shielded against manufacturer-level tampering.

  1. 01Authenticate mobile app using API Key to retrieve live diversification Master Keys.
  2. 02Physically tap NFC. Tooling establishes a mutually encrypted AES-128 APDU session.
  3. 03Rotate default keys, provision private URLs, and permanently set the SUN Lock Bit.
  4. 04
    Push registration data to backend cloud. (Required)

    Backend places the UID into global inventory in status 'INACTIVE'.

Mutual Auth Active

The Cloud Enrollment Hook

Triggers automatically in Toolbox after successful hardware lock.

POST/v1/dpp/enroll

Request Example

{
  "chipUid": "04A1B2C3D4E5F6",
  "productId": null
}

Response Example

{
  "success": true,
  "message": "Chip registered and ready.",
  "data": {
    "id": 8921,
    "status": "INACTIVE"
  }
}

System Fact: Chips are initialized into an `INACTIVE` pool state. This serves as raw inventory that cannot yet be resolved publicly until the final Minting Workflow (WF2) activates it with standard-compliant metadata.