QR Codes & Claiming
Share codes as QR
Every code has a scannable QR that deep-links recipients straight into the claim flow (via a web+cardano://claim/... URI plus the campaign's claim URL).
- Single code: click the QR button on a code row to view/print its QR.
- All codes: click Export QR Codes in the campaign toolbar to open the export dialog, then download a ZIP with one uniquely-coded QR per code — drop them on flyers, stickers, or event screens.
Export options
The export dialog lets you tailor the output to your printer and stock, with a live preview of a single sticker:
- Format — PDF (print-ready, prints cleanly on Windows; the default), PNG (raster image; available when the server has the GD extension), or SVG (vector, for design tools).
- Sticker size — 1", 1.5", 2", or a custom edge length (0.5"–4"), square.
- Resolution (DPI) — 203 (thermal-label default, e.g. Zebra ZP 450), 300, or custom. Drives the pixel dimensions of PNG output (
inches × DPI). - Error correction — L / M / Q / H. Higher levels tolerate more damage/smudging at the cost of a denser QR.
- Header / footer — optionally print the campaign expiration date above and the claim code below the QR (both off by default).
Every code gets its own QR, so a shared image can't be posted online to drain the campaign wallet.
The claim experience
From the recipient's side:
- They scan the QR (or open the claim link). The code is pre-filled from the QR.
- They enter their Cardano wallet address.
- They submit, and the reward is queued for delivery to their wallet.
Invalid codes, exhausted codes, and malformed addresses are rejected with a clear message. Per-wallet and per-IP rate limits protect the endpoint (see Configuration).
Delivery
Claims are processed asynchronously by the queue worker using the configured transaction backend. On the null backend the claim is recorded but nothing is sent — useful for rehearsing the flow before mainnet.
You can watch claim statuses and refresh them on demand from the campaign page — see Monitoring & performance.