Enrolling members

Every enrollment ends up in the same place: an application row, a customer record in DK, and a wallet pass. How the application is created is up to you.

At the till (operator)

Open Enroll a member, pick a program, and fill in the customer's name, kennitala, email, and phone. If the program is open, the pass is issued immediately and the email goes out within seconds. If it requires approval, the application sits in the queue.

Kiosk / public form

Programs with the public form enabled have a URL of the form /enroll/{tenant-slug}/{program-slug}. Open that URL on a kiosk iPad or share it with the customer to fill out themselves. The form is tenant-branded, requires no Stokk login, and runs the same enrollment pipeline.

Bulk import (CSV)

For migrating from another wallet vendor, use Bulk import. Paste a CSV (or TSV) with columns kennitala, name, email, phone. The header row is required; column order doesn't matter.

DK customer creation

Most enrollees aren't in DK yet. Stokk creates the DK customer first, mirrors it locally, then issues the pass. Returning customers (kennitala already in DK) are reused — no duplicate records.

What the customer sees

  1. An email from your verified sender domain titled “Your [program] card is ready.”
  2. A button that opens a tenant-branded landing page on their phone.
  3. The landing page detects iOS or Android and offers Add to Apple Wallet or Add to Google Wallet.
  4. The card lives in their wallet from then on. Customer data updates push to the device automatically.