The Salesforce-Native Coupon Platform for Apple and Google Wallet
Create mobile wallet coupons from any Salesforce segment or Flow, then deliver them by email, SMS, QR, or WhatsApp. Kemicard reminds holders before expiry and logs every redemption to the record that earned it.
Think of it as a coupon wallet on every phone: digital coupons, mobile wallet-delivered — Apple Wallet coupons on iPhone, Google Wallet offers on Android. Redeemable mobile wallet offers report every redemption to Salesforce, and for eCommerce, wallet coupons close the loop between online campaigns and in-store scans.
Try on AppExchangeWhy Do Businesses Move to Digital Coupons in Apple Wallet and Google Wallet?
A coupon nobody sees earns nothing. Wallet offers stay visible until expiry, and every redemption gets counted.
Email fatigue
Promotional emails compete with everything else in the inbox. Most offers get filtered into the promotions tab and expire there unopened.
No attribution
One shared code goes to everyone. There is no way to tell who redeemed it or which campaign made it happen.
No urgency mechanism
No reminder before expiry. The customer forgets and the offer lapses. The spend behind it is wasted.
Businesses need offers customers see in time and redemptions they can measure. Mobile wallet coupons deliver both — the offer sits a swipe from the lock screen until it expires, and every redemption writes back to the Salesforce record that earned it.
Salesforce Native Mobile Wallet Coupons, Personal to Every Record
Salesforce native means coupons are created and tracked inside your CRM. Personal to every record means each customer gets their own offer and their own code.
Personal offer, unique code
Offers are personal by default. Each coupon is generated from a single Salesforce record, and the unique code links every scan back to it.
One template, both wallets
Design the coupon once. Logo, colors, barcode, and images render correctly in Apple Wallet and Google Wallet.
Extend, change, or end the offer anytime
A sent coupon stays editable. Push a new expiry date or a better offer, and every issued pass updates in the wallet.
Your next promotion could be in the wallet. Book a demo and find out — your branding on the pass, your data in the fields.
See the Coupon DemoIssue, Remind, Redeem, and Measure in One Salesforce Wallet Coupon App
Issue, remind, redeem, measure. All four stages run in Salesforce, and all four write to the same record.
No-code offer builder
Build the coupon in the Salesforce admin UI, with no code and no certificates to manage.
Issue from a segment or Flow
Any Salesforce list view or Flow can trigger issuance, so an offer goes out the moment a record qualifies.
Bulk issuance for a campaign
Send an offer to a whole segment in one queued run, with every coupon logged on its Contact.
Geo-triggered surfacing
The coupon surfaces on the holder's lock screen when they are near your store or venue.
Configurable redemption rules
You decide how each offer redeems, from a single use to a set number per holder, validated against the record at scan time.
Validate from a phone
Staff redeem through the Salesforce mobile app, so scanning a coupon needs no separate hardware.
Fraud and duplicate detection
Each code is checked at scan, so a copied or screenshotted coupon fails validation.
Inherited Salesforce security
Coupon configuration runs inside your org and respects your existing profiles and field-level security.
Full audit trail
Issuance, updates, reminders, and revocations are timestamped against the holder.
One Wallet Coupon Platform, Every Offer, All in Salesforce
Whatever you are promoting, the build is identical. A record meets a condition, the coupon issues, and it saves to Apple or Google Wallet. What moves is the offer and who gets it.
Welcome / first-purchase offer
Sends when a Lead or Contact is created, so new signups get a first-order code automatically. Example: a retailer sends a 15% welcome coupon the moment someone joins the list.
Post-purchase next-visit offer
Sent on a closed order or gift, driving the second transaction. Example: after a first purchase, the customer gets a “come back in 30 days” coupon connected to their order record.
Referral and advocacy offers
Each advocate gets a unique code, and redemption links the new customer back to the referrer. Example: a member shares their code, and every redemption logs to both records for the reward payout.
Milestone and tier rewards
Fires when a Salesforce field crosses a threshold, so the reward coupon issues on its own. Example: at 2,000 points, the member gets a free-item coupon in the wallet with no manual send.
Seasonal and flash sales
Scheduled go-live and expiry across a whole segment, with urgency from the expiry push. Example: a holiday code issues Friday, reminds Sunday, closes Monday.
Cross-sell and next-best-offer
A coupon for a complementary product, based on what the record already owns. Example: someone who bought the printer gets an ink discount in the wallet.
Partner and co-branded offers
A partner's offer delivered through your wallet program, with redemption tracked for shared ROI. Example: a sponsor's offer sits in the same wallet, and redemptions report back for co-marketing.
B2B and field-sales offers
A rep connects a negotiated discount to an Opportunity, and the buyer redeems it at order. Example: a rep issues a one-time account discount tied to the deal record.
Feedback and review incentive
A coupon issued in exchange for a survey or review, triggered when a case closes or a survey goes out. Example: after a support case wraps, the customer gets a thank-you code for leaving feedback.
A Promotion Channel That Lives on the Lock Screen
- Instant offer refresh — change the strip image and back-of-pass message to promote a sale, and installed passes update automatically.
- Geofenced reminders — the coupon surfaces when the customer is near your store or venue, up to 10 locations per template.
- Push announcements — new offers and expiry reminders as lock-screen notifications, with 80–90% visibility.
- Scan-to-redeem — QR redemption in-store; each scan triggers a Flow that records the redemption and can retire the coupon.
- Expiry built in — fixed or relative expiry dates; expired coupons move to the wallet's expired section on their own.
- Segmented offers — different coupon designs and values per Salesforce segment, driven by the data on the record.
Northside Outfitters
Bloom Garden Center
Offers That Remind Customers to Use Them
An offer nobody remembers is a discount that never converts. Push notifications give every coupon and voucher a voice — and expiry dates become conversion events.
- Expiry countdowns. A push three days before an offer lapses recovers redemptions email never reaches. The urgency is real, so it works.
- Activation moments. Flash-sale coupons flip active with a lock-screen announcement — every installed card, simultaneously.
- Balance updates. Gift cards push their remaining balance after each use, keeping the card top-of-mind until it's spent.
- Location triggers. Geofencing surfaces the coupon when the customer is near a store where it's valid.
Every message here is a template — sent automatically from a Salesforce Flow, a Bulk Action, or a single record, at no per-message cost.
884 Pine Ridge Road
Denver, CO 80211
Code: NS-20
The Back of the Offer: Terms Nobody Has to Ask About
Redemption steps, exclusions, and expiry — attached to the offer itself, so cashiers and customers see the same rules.
Every row is a back-of-pass field configured in Kemicard Studio — plain text, tappable links, and phone numbers, all mapped to Salesforce data. Extend an expiry date or add an exclusion and every issued voucher's back updates instantly — the fine print is never out of date.
Redemptions Reported Where Revenue Lives
Coupon installs, scans, and redemptions all land on the Salesforce record, so campaign ROI reports sit beside your opportunity and order data — no separate coupon platform to reconcile.
Redemption tracking
Every scan writes who, when, and where — reportable by campaign, segment, and location.
Conversion attribution
Trace purchases and sign-ups back to a coupon interaction through Campaign integration.
Fraud controls
Unique serials per coupon, duplicate-scan detection, sharing controls, and one-click retirement of abused offers.
Offers that redeem themselves
Paper coupons get lost, PDF vouchers get screenshot-shared, and email offers get buried. A wallet coupon is different: installed once, it sits in the customer's wallet with your branding, updates when the offer changes, and — critically — carries a unique, scannable identity that makes redemption controlled and measurable.
With Kemicard, each coupon is a Salesforce record. Issue a one-per-customer voucher via Flow or Bulk Actions; the unique QR code redeems exactly once, validated live at the point of sale by the Kemicard Scanner, with the redemption logged to the record. Sharing a screenshot achieves nothing — the code is already spent or flagged as duplicate on the second scan. For gift cards and store credit, the same pattern shows a live balance that decrements with each use.
Expiry does the marketing for you: a push notification three days before an offer lapses recovers redemptions that email never would, and geofencing surfaces the coupon when the customer is near a location where it's valid. When the campaign ends, retire the template and every outstanding pass visibly expires — no zombie discounts circulating. Measurement comes free: issued, installed, redeemed, and where, all in Salesforce reports.
An Offer You Cannot Close Is a Discount You Cannot Control
The failure mode of digital coupons is not distribution; it is redemption. An offer that is only looked at can be screenshotted, forwarded and used repeatedly, and the first sign of trouble is a margin that does not reconcile.
- Validate at the point of use. Single-use codes checked against a record fail on the second attempt, which is what makes the offer finite.
- Expiry that enforces itself. A pass past its date stops validating rather than relying on a cashier to check.
- Per-recipient issuance makes a forwarded offer traceable rather than anonymous.
- Redemption writes back, so you know which segment responded and what it cost.
Frequently Asked Questions
Yes, a build is possible, and it helps to know what it involves. A do-it-yourself Salesforce Apple Wallet integration means Apex, the Apple Wallet API, certificate renewals, and JWT signing to connect Salesforce to Google Wallet, plus a server to generate and update every pass. Kemicard ships that whole stack as a configured product, so your team maps fields instead of maintaining a Salesforce Google Wallet integration for years.
No. Kemicard provisions and rotates the Apple certificates and the Google issuer setup for you, so you generate an Apple Wallet coupon from Salesforce with no signing server and no file to build. Apple Wallet for Salesforce and Google Wallet for Salesforce run as a managed product here, not a raw API your team keeps alive.
Yes. Kemicard is an AppExchange wallet pass app, installed as a managed package like any other. You can test it in a sandbox first, then roll it to production, with nothing external to host.
Yes, and the reason is where the data sits. Because Kemicard runs inside your org, coupon records stay in your Salesforce environment and inherit its field-level security and access controls, inside Salesforce's SOC 2 Type II environment. There is no separate database for your security team to vet — see the Trust Center for the full posture.
Pricing is annual and based on the number of coupons you issue per year, not on user seats. A wallet pass app for Salesforce like this fits teams sending real volume — it is the right call when you run thousands of offers a year rather than a few hundred. Nonprofits get a discount. See pricing for the full table.
Yes. Beyond editing an offer yourself, any pass field bound to Salesforce refreshes through the real-time wallet updates Salesforce sends to Apple and Google, with no resend. Salesforce wallet pass automation keeps every issued coupon current the moment the record behind it changes.
Coupons & Vouchers — the brochure
A one-page summary for a conference table or an email, or the six-page version for the colleague who has to approve it. Both cover what you can issue, how it works, and the push and back-of-card examples for coupons and vouchers.
Further reading
From the blog
Stop Guessing Which Offer Worked. See Every Redemption in Salesforce.
Book 30 minutes with the Kemicard team. We will build a working coupon against your own fields on the call, and you will watch a redemption log back to the record that sent it.