Minting FAQ

A DPP is a structured data record that accompanies a product through its lifecycle. It can include composition, origin, compliance, and sustainability information as defined by your industry’s regulatory framework.

Up to 1,000,000 units per mint request. Large jobs are processed automatically in the background — you do not need to stay on the page.

Typical observed throughput:

  • 100,000 units: approximately 5–6 seconds
  • 1,000,000 units: approximately 60–90 seconds

Performance scales linearly with job size.

Whether a GTIN is required depends on your brand’s DPP schema configuration. The minting validation checks all required fields before allowing submission.

Minted tokens are associated with the product and batch. Each token’s resolver URL can be printed, embedded in a QR code, or programmed into an NFC tag. Scanning the URL routes to the product’s passport data. The Minting Dashboard includes a token preview panel where you can inspect individual token details.

No. After submitting a mint request, the system processes tokens in the background. You can navigate away and check progress on the Minting Dashboard at any time. In-progress jobs are automatically resumed to completion.

Failed processing cycles are automatically retried up to 3 times. If all retries are exhausted, the job is marked as failed. Tokens generated before the failure are preserved — partial progress is never lost.

Yes. The system supports concurrent mint jobs. Each job is processed independently with no risk of duplicate tokens or serial number conflicts. The platform has been tested with multiple overlapping 1,000,000-unit jobs.

Batches with more than 10,000 units are split into multiple sequential CSV packs. Each pack contains up to 10,000 units. Packs are generated one at a time and can be downloaded individually. If export is interrupted, it can be resumed without regenerating completed packs.

Yes. The token preview panel displays a scannable QR code (ISO/IEC 18004, SVG) encoding the token’s resolver URL. The QR code uses ECC Level M for reliable scanning and renders with a black foreground on a white background regardless of theme.

Yes. If you provide an idempotency key with your mint request, duplicate submissions will return the existing job rather than creating a new one. This makes retries completely safe.