With Kemicard installed and authorized, this walkthrough takes you from a Salesforce contact to a live membership pass on a phone — managing the contact, updating membership details, and sending the pass, step by step.
Part 1 · ~15 min
Send your first pass
Assign the page layout, create a contact, send the sample membership pass, and install it on a phone. Nothing to design — the template already exists.
Part 2 · ~30 min
Build your first template
Create a template in Kemicard Studio, bind it to a Salesforce object, choose a pass type, add images and a barcode, and watch the live preview.
Part 1 — Send your first pass
Eight steps, using the sample data installed with the package. At the end you will have a working membership pass in Apple Wallet and Google Wallet.
1. Assign the Kemicard Contact page layout
The installer deploys a Kemicard Contact page layout, but Salesforce does not assign it to anyone automatically. Until you assign it, the membership fields this walkthrough uses will not appear on the Contact record.
- Click the gear icon in the top right, then Setup.
- Open Object Manager, search for Contact, and click it.
- Click Page Layouts, then Page Layout Assignment.
- Click Edit Assignment, set the layout to Kemicard Contact for the profile you work in — System Administrator, typically — and Save.
2. Open Contacts in the Kemicard app
Open the App Launcher, search for Kemicard, and open the Kemicard app.
Then click the Contacts tab.
3. Create the contact and fill the membership fields
Create a contact — this walkthrough uses Phoebe Buffay to match the sample data, but in your own org it is any Contact you want to issue a pass for. Fill these fields, because the pass is built from them:
- Email — use your own address. This is where the enrollment email lands, so you see exactly what a member receives.
- Member Number and Member Name — the identifiers printed on the card.
- Member Since and Membership Expiration Date — these drive the dates shown on the pass and the wallet's expiry behaviour.
Further down the same record, Membership Pass Template selects which design the pass uses — the sample data ships Woofly Membership Pass. The Membership Pass, Apple Wallet Pass URL and Google Wallet Pass URL fields stay empty until you send the pass; you will watch them populate in step 5.
4. Send the membership pass
Click “Send Membership Pass” to initiate sending the pass to the contact via email.
5. Refresh and confirm the contact details
Wait a couple of seconds, refresh the page, and click the “Details” tab to ensure all contact information is accurate and up to date.
6. Confirm the pass is generated
Confirm the pass is generated by checking that “Membership Pass” is populated, and that both the Apple Wallet Pass URL and Google Wallet Pass URL fields are generated on the record.
7. Check your inbox
Once the pass is generated, you will receive an email with the pass's downloadable links — Add to Apple Wallet and Save to Google Wallet buttons, device-detected from one link.
8. Install on a phone
Open the email on a phone and tap the button for your device. Here is what the sample Woofly membership pass looks like installed on Google and iOS devices — including the back of the card with automatic updates and notification toggles:
Bonus: make a live update
Change a mapped field on the contact — for example the membership tier — and watch the installed pass refresh on the phone within seconds via the real-time event pipeline. Then send a push notification from the pass record and see it land on the lock screen. That loop — record change to pocket — is the heart of Kemicard.
Part 2 — Build your first template
Part 1 sent a pass from a template that already existed. This part builds the template itself, following a real configuration in a Salesforce org. The sequence is the same whichever object you build from — and once this template exists, Part 1 works against it exactly as it did against Woofly.
1. Create the template
From the App Launcher open Kemicard Studio, choose New Template, then fill in the Details step: a Template Pass Name, a Description and an Organization Name. The organization name is what a member sees on the card, so use the public-facing one.
2. Bind it to a Salesforce record
This is the step that makes the pass live rather than static. Metadata Configuration chooses the Kemicard Configuration record, which tells Kemicard which object and fields feed the pass.
Email Template on the same screen decides which enrolment email carries the add-to-wallet link. Kemicard ships templates alongside the standard Experience Cloud verification ones, and you can point at your own.
3. Pick a pass-type template
Apple and Google are separate stages in the left rail, and each asks the same question independently: which layout should this pass use? Every card shows a sample preview, so you are choosing a shape rather than a name.
On the Apple stage the options are Event Ticket (venue and event details to the front), Event Ticket (Thumbnail) (a hero image with the details beside it) and Loyalty Card (rewards and membership, with the most branding freedom).
The Google stage offers Generic Pass (Hero/Strip Image) for transit, coupons and access, and two thumbnail variants. The difference between them is a privacy decision, not a visual one: the Secure Lock variant hides the thumbnail behind device unlock — fingerprint or face — while the Private Image variant keeps the image visible without requiring it. Choose Secure Lock when the image identifies a person.
4. Add images — and mind the limits
In Studio, the image slots are on the preview itself: click the logo placeholder on the card, or the wide strip area beneath it, to open the upload dialog.
The upload dialog states the rules, and they are stricter than most people expect: under 100 KB, PNG for Apple, JPG, JPEG or PNG for Google, and a 150×150 px logo. Tick Apple, Google or both.
The strip image is a separate slot with its own dimensions, and it is the one most often left empty by mistake — an unset strip renders as a blank band across the middle of the card.
Uploaded images appear in the preview immediately, on both platforms, so you can check the logo against your background colour before saving anything.
5. Design the card and watch the preview
The Settings rail on the left changes what the Preview on the right renders — front, back and notification, for both platforms at once. Use it constantly; it is faster than reasoning about the layout.
6. Add a barcode
Under Barcodes, pick the symbology your scanners already read — QR Code, AZTEC, CODE_39, CODE_128, CODABAR, DATA_MATRIX, EAN and others are offered.
Then choose the Salesforce field it encodes. Here it is a Contact field, so every issued pass resolves straight back to its record on scan.
You're up and running
This concludes the installation and setup of Kemicard Digital Pass for Salesforce: you have successfully generated and sent a membership pass from Salesforce. To go deeper, continue with these documentation sets:
- Kemicard Studio guide — design your own templates: fields, colors, images, barcodes, tiers, cloning, and import/export.
- Events guide and loyalty template guide — purpose-built walkthroughs per use case.
- Update Template guide — change templates already live in the field.
- Flow integration — automate issuance with the five sample flows that ship with the package.
- Campaign Manager — generate passes and send messages for your whole base.
- Scanner user guide — check-in and verification at the door.
- Notifications & geofencing — the engagement patterns that make the card a channel.
