Minting

Exports & Print Jobs

Overview

Once a mint batch reaches minted status, you can generate export packs containing token data for printing, labelling, or integration with downstream systems. Exports are available from the Exports / Print Jobs tab on the Minting Dashboard.

Export Format

Each export pack is a CSV manifest containing:

  • Token identifier
  • Resolver URL
  • Serial number (if applicable)
  • GTIN (if applicable)
  • Token status
  • Creation timestamp

Multi-Pack Generation

For batches exceeding 10,000 units, the system automatically generates multiple sequential packs:

Batch SizePacks Generated
1–10,0001 pack
10,001–20,0002 packs
100,00010 packs
1,000,000100 packs

Packs are generated sequentially and each pack covers a deterministic slice of the batch’s tokens.

Resumable Generation

Export generation is designed to be resilient:

  • If generation is interrupted (e.g., browser closed, network timeout), clicking Export / Download again resumes from the last completed pack.
  • Previously completed packs are not regenerated.
  • A 10-minute concurrency lock prevents duplicate generation for the same batch.

Downloading Packs

Once a pack is ready:

  • A signed download URL is generated with a 5-minute TTL.
  • The download starts automatically when the pack completes.
  • For multi-pack exports, each pack triggers its own download as it becomes available.

Status Values

StatusDescription
pendingPack has been requested but generation has not started.
generatingPack is actively being generated.
completedPack is ready for download.
failedPack generation encountered an error.

QR Code Manifests

You can generate a QR manifest for any completed batch using the Reprint QR codes action in the Batches tab. This produces a qr_manifest.csv file containing resolver URLs and token identifiers for use by printing or variable data printing (VDP) software to generate QR codes downstream. No server-side QR image generation is performed — the manifest provides the data needed for your print workflow to produce QR codes.

Each row includes:

ColumnDescription
mint_batch_idThe batch identifier
mint_unit_idThe individual token identifier
serialSerial number (if applicable)
gtinGS1 Global Trade Item Number (if assigned)
resolver_urlThe token’s resolver URL (to be encoded in a QR code)
created_atToken creation timestamp

QR manifests follow the same multi-pack and resumable generation behaviour as standard CSV exports.

NFC Encoding Manifests

Generate an NFC encoding manifest for any completed batch using the NFC Encoding Manifest action in the Batches tab. This produces an nfc_manifest.csv file containing resolver URLs and token identifiers for use by NFC tag encoding hardware and software.

Each row includes:

ColumnDescription
mint_batch_idThe batch identifier
mint_unit_idThe individual token identifier
serialSerial number (if applicable)
gtinGS1 Global Trade Item Number (if assigned)
resolver_urlThe token’s resolver URL (to be written to the NFC tag)
created_atToken creation timestamp

NFC manifests follow the same multi-pack and resumable generation behaviour as standard CSV exports.

RFID Encoding Manifests

Generate an RFID encoding manifest for any completed batch using the RFID Encoding Manifest action in the Batches tab. This produces an rfid_manifest.csv file containing resolver URLs and token identifiers for use by RFID tag encoding workflows.

Each row includes:

ColumnDescription
mint_batch_idThe batch identifier
mint_unit_idThe individual token identifier
serialSerial number (if applicable)
gtinGS1 Global Trade Item Number (if assigned)
resolver_urlThe token’s resolver URL (to be written to the RFID tag)
created_atToken creation timestamp

RFID manifests follow the same multi-pack and resumable generation behaviour as standard CSV exports.

QR Bundle (SVG ZIP)

You can generate a ZIP archive of QR code SVG files for any completed batch using the QR Bundle (SVG ZIP) export option. This is ideal for print shops and label production workflows that require individual QR code files.

Each bundle contains:

  • A qr/ folder with one SVG file per physical unit to be printed
  • An index.csv file mapping identifiers, resolver URLs, and filenames

Serialized batches

For serialized (unit-level) batches, each SVG encodes a unique resolver URL for that unit. The index file contains serial, gtin, resolver_url, and filename columns.

Batch-token (lot-level) batches

For batch-token batches, each lot’s shared resolver URL is repeated across the number of physical units specified by the lot’s print quantity. For example, a lot with a print quantity of 5,000 produces 5,000 identical SVG files. The index file contains lot_code, gtin, resolver_url, and filename columns.

Logo embedding

If your brand has a logo uploaded and the Allow logo in QR bundles setting is enabled, QR codes will be generated with the logo embedded in the centre using high error correction (ECC Level H). Without a logo, standard error correction (ECC Level M) is used.

Limits

QR bundles are limited to 10,000 codes per pack. For larger batches, the system automatically generates multiple packs. Each pack covers a deterministic slice of the batch’s tokens or lots.

Generation

QR bundles are generated asynchronously. After requesting a bundle, you can monitor its status in the Exports tab:

  • Queued — bundle request received
  • Generating — bundle is being created
  • Ready — bundle is available for download
  • Failed — generation encountered an error

Export File Retention

Export files are retained for 30 days from the time they are generated. After this period:

  • The export file is automatically removed and can no longer be downloaded.
  • Your export history remains visible in the Exports tab — you can see when exports were generated and their status.
  • If you need the data again, you can regenerate the export from the batch, which will produce a new file with a fresh 30-day retention window.

This applies to all export types: CSV manifests, QR manifests, NFC encoding manifests, RFID encoding manifests, and QR bundles.