Kemicard ships on a regular release cadence — eight releases over the past twelve months, most recently v2.29 on 3 September 2026. Upgrades install as new managed package versions from the AppExchange; we proactively notify customers affected by fixes.
- Kemicard Connect — plan and send targeted push-notification campaigns to pass holders at scale.
- Bulk processing — generate and update thousands of passes reliably in a single operation.
An anti-fraud release. A static QR code keeps working for as long as someone has a photo of it, and a pass that can be forwarded freely can do the work of two memberships. Three new Google Wallet controls close that gap, and the Kemicard Scanner gets a faster check-in flow at the door.
- Rotating barcode (Google Wallet) — replaces the static QR code with one that refreshes on an interval you set (5–600 seconds, default 20) at a length you choose (6–8 digits, default 6). Each pass carries its own secret and the scanner validates the live code, so a screenshot goes stale within seconds. Enabled per template in Kemicard Studio under Settings → Barcodes. Set it up.
- Pass sharing controls — decide which wallets a pass is allowed to reach, set separately per platform. Apple Wallet gets an on/off switch that removes the Share button. Google Wallet gets four levels: Fully Shareable, Single User (Multiple Devices), Single User (Single Device), and Sharing Prohibited. Compare the levels.
- Private Image type (Google Wallet) — shows a member photo on a standard pass, private to the pass holder but with no screen-lock prompt. Secure Private Image remains available where device-unlock verification is wanted. Choose a type.
- Kemicard Scanner — pick camera or an external handheld/gun scanner once and Kemicard remembers it; results appear immediately and can carry a profile photo, extra images and clickable links for visual identity checks. Scanner guide.
- Self-service upgrade steps — the Upgrades area of the Kemicard Console now carries a Pending badge when post-install metadata steps are outstanding, and an admin runs them with one click under their own session. No support case, and no guessing whether the org is fully upgraded. How to run them.
Two boundaries worth knowing before you enable these. Rotating barcodes apply to the Google Wallet version only — the Apple pass keeps its standard barcode, so door staff must scan the Google pass for the anti-fraud coverage to apply. And Google only permits the sharing level to change before a member has saved the pass; once it is in a wallet the level is locked, so choose it before you distribute.
- Secure private images for Google Wallet — among the first Google Wallet partners to implement; optional per template.
- URL-based thumbnail images — Google thumbnail support with API control.
- Smoother geolocation-triggered passes — geofencing reliability improvements.
- Faster, safer package upgrades — plus Google rendering fixes.
- Geofencing with Google Maps integration — addresses or coordinates, multiple locations per template.
- Streamlined feature enablement and refined permissions for standard users.
- Campaign reporting improvements and reliability hardening.
- Template import/export between orgs — the standard sandbox-to-production promotion path.
- Template clone — one-click variants preserving configuration and structure.
- Real-time pass event processing — new event pipeline for instant updates.
- Enhanced barcode text configuration, WhatId support in email templates, and notification-ordering fixes.
- New Overview & Getting Started guides.
- Loyalty Pass support for Apple & Google Wallet — points balances and rewards status on the card.
- Dynamic thumbnail images on passes.
- Guided wizard for template creation and centralized logging in the Kemicard Console.
- Fixes: attach-pass-to-email, editable Apple notification titles, inactive-template install counting, and back-field validation over 255 characters.
Stay current. Some fixes (accurate install counts, Google thumbnails, rendering) require recent versions — if you're more than one version behind, ask support to run your upgrade.
