> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Minting FAQ

> Answers to common minting questions: request ceilings, background processing, retries, idempotent resubmission, and localised passport content.

#### What is a Digital Product Passport?

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. When localised through Market Packs, it also includes market-specific recycling guidance, disclaimers, and multilingual content.

#### How many tokens can I mint in a single request?

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

#### How long does minting take?

Typical observed throughput:

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

Performance scales linearly with job size.

#### Can I mint without a GTIN?

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

#### What happens after minting?

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, rendered with the brand's theme and any linked Market Pack content. The Minting
Dashboard includes a token preview panel where you can inspect individual token details.

#### Do I need to stay on the page during minting?

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.

#### What happens if a mint job fails?

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, so partial
progress is never lost.

#### Can I run multiple mint jobs at the same time?

Yes. The system supports concurrent mint jobs. Each job is processed independently with no risk of
duplicate tokens or serial number conflicts.

#### How do exports work for large batches?

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.

#### Is there a QR code feature?

Yes. The token preview panel displays a scannable QR code (ISO/IEC 18004, SVG) encoding the
token's resolver URL. You can also generate QR bundles (ZIP archives of individual SVG files) for
print production workflows.

#### Is it safe to retry a failed submission?

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.

#### Do minted passports include localised content?

Yes. When a passport has a linked Market Pack, the rendered passport includes the market-specific recycling guidance, disclaimers, and locale-appropriate formatting defined in that pack. The localised content is additive: it supplements the base passport without altering it.

## Related Docs

* [Minting Overview](/minting/overview)
* [Minting Lifecycle](/minting/lifecycle)
* [Limits and Performance](/minting/limits-performance)
* [Exports and Print Jobs](/minting/exports-print-jobs)