Klaviyo already owns your email and SMS. A wallet pass is the third owned channel: it sits on the home screen, updates by push at no per-message cost, and you issue one automatically the moment a profile subscribes.
A few ways teams put Klaviyo and Passmint to work together.
One Zap links the two — live in a few minutes, no code involved.
In Zapier, add Passmint as a connected app and paste your API key when prompted. Zapier verifies it against your account immediately, so you'll know the connection works before building the rest of the Zap. Use a pmk_test… key while you're setting things up.
Create a new Zap and choose Klaviyo as the trigger app. Pick the trigger that fires when a profile is created, or when a profile subscribes to a list — the latter is usually what you want, so passes only go to people who've opted in. Send a test so Zapier can pull a sample profile and learn its property names (email, name, and any custom properties like vip_tier or a coupon code).
TODO(verify): Confirm Klaviyo's exact trigger labels — there's typically a 'new profile' trigger and a 'profile subscribed to a list' trigger — and whether each lets you scope to a specific list. Note whether subscription consent (email vs SMS) is exposed on the sample profile.
Add an action step, choose Passmint, and select Create Pass. Pick the template to issue from the dropdown — Zapier loads your templates automatically — choosing your coupon template for a signup offer or your loyalty template for a VIP card. Then map Holder Email and Holder Name from the Klaviyo profile's email and name properties.
In Field Values, map the Klaviyo profile data you want on the pass to your template's fields. The key on the left must exactly match a field name defined in your Passmint template (e.g. discount_code → the profile's coupon code, vip_tier → a tier property, clv_band → Klaviyo's predicted-CLV property bucketed into Bronze/Silver/Gold). The value on the right is the property from the triggering profile. Properties you don't map are simply left off the pass.
TODO(verify): Confirm which Klaviyo profile properties are available to map — especially predicted CLV / lifetime value and any per-profile coupon code, which may live under predictive analytics or a custom property rather than the core profile fields. Then confirm, on a real template, that the Field Values keys you reference exist as field names in that template; mismatched keys are silently ignored.
Add a second action — Klaviyo → update profile (or add a profile property) — and map Passmint's Pass URL output into a custom property such as wallet_pass_url. Now your welcome flow can drop a personalised "Add to Apple/Google Wallet" button into the very first email or SMS, using that property as the link. The pass becomes part of the onboarding you already run.
TODO(verify): Confirm Klaviyo's 'update profile' / 'add or update property' action exists in Zapier and that it can write a custom property keyed by the same email from the trigger. Check whether the property must be pre-created in Klaviyo before a flow can reference it.
Run the Zap with your test profile and check that a pass is created in Passmint, the URL comes back, and (if you added it) the property writes onto the Klaviyo profile. Open the pass on a phone to confirm the code and branding look right, then switch your API key to pmk_live…, turn the Zap on, and subscribe a test address to watch it work end to end.
The details teams check before switching the Zap on.
Hand every new Mailchimp subscriber a wallet coupon — the offer lives on the phone, not the inbox.
Issue a membership card when a contact is created and keep the tier in sync as they move through your funnel.
Hand every new contact a coupon or loyalty pass automatically.
Issue a membership or loyalty pass to every new contact.
Free for your first passes. No Apple or Google certificates to manage, no code to write.