​

Wallet Passes

​

What you see on the page

• Pass type — loyalty card, coupon, or ticket
• Contact ID or External ref — who carries the pass, or your own order or ticket id
• Title and optional Subtitle — what the holder reads first
• Organization name and Description — your brand on the pass
• Barcode message — the scanned value at your counter, for example the member code

​

Who can read and who can act

​

Worked examples

​

Issue a loyalty card to a member

1. Choose Issue pass.
2. Set the pass type to loyalty card, the member’s Contact ID, your Organization name, and the member’s code as Barcode message.
3. Confirm, then deliver the pass link over any channel you already use. The pass installs into the holder’s wallet.

​

Bump the generation counter

1. Find the member’s active pass and choose Update.
2. Change what moved — a new tier in the title, a refreshed barcode, a corrected description.
3. Save. The row’s Generation goes up by one, and every device holding that pass refreshes its content without the member re-saving anything. That is the whole refresh contract: content change plus generation bump.

​

Void a pass when the membership ends

1. Choose Void on the row. The console asks for confirmation, since the action cannot be undone.
2. The status leaves active, and Update and Void disable on the row, on the dashboard and in the API alike.

​

API pairing

curl -X POST https://api.orbit.devotel.io/api/v1/wallet-passes/issue \
  -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "loyalty_card",
    "contact_id": "cnt_member_9x2",
    "title": "Club Card",
    "organization_name": "Your Brand",
    "barcode_message": "ORBIT-CNT-9X2",
    "barcode_format": "QR_CODE",
    "background_color": "#1A1A2E",
    "fields": [
      { "key": "points", "label": "Points", "value": "0" }
    ],
    "idempotency_key": "issue-cnt_member_9x2"
  }'

​

Tenant-owned controls