Purpose: Enable Insider to orchestrate journeys while Litecard powers the mobile wallet channel (Apple/Google Wallet).
1. What this integration actually does
Insider = brain (segmentation, journeys, triggers)
Litecard = channel (wallet passes + push notifications)
Together:
- Insider triggers → Litecard creates/updates wallet passes
- Litecard sends push notifications + renders offers in-wallet
- Customer actions flow back into CRM/CDP
This creates a new CRM channel outside email/SMS
2. High-level architecture
Flow:
- Customer enters Insider (event, segment, journey)
- Insider sends event → Litecard (API / webhook)
- Litecard:
- Creates pass OR updates existing pass
- Returns unique wallet link
- Link embedded into:
- SMS
- Web/app
- Customer downloads pass
- Litecard:
- Sends push notifications
- Updates offers / points / tiers dynamically
- Transactions sync back → CRM/CDP
This matches the lifecycle shown in the system diagram (page 7)
3. Core integration components
A. Identity mapping #
You need a shared identifier:
- email (recommended)
- customer_id
- phone (fallback)
Used to:
- prevent duplicate passes
- sync updates (points, offers)
B. Litecard API (core endpoints) #
- Create / update pass
- Input: customer data + offer/loyalty data
- Output: unique wallet link
- Update pass state
- Points
- Tier
- Voucher balance
- Expiry
- Send push notification
- Triggered by Insider journeys
C. Insider usage #
Inside Insider:
- Create custom actions / webhooks
- Trigger Litecard API calls within journeys
Typical triggers:
- signup
- purchase
- inactivity
- birthday
- tier change
4. Journey implementation (step-by-step)
Step 1 — Pass creation flow #
Trigger: signup / first purchase
Inside Insider:
- Webhook → Litecard (create pass)
- Receive wallet link
- Insert into:
- SMS
- onsite popup
Result:
→ customer downloads pass
Step 2 — Engagement flows #
Once pass is installed:
Use Insider to trigger:
- reward issued
- reward expiring
- points close to threshold
- store proximity
Litecard executes:
- push notification
- pass update (visual + data)
Examples (from deck page 9) :
- Birthday reward
- “Reward expiring in 48h”
- Points stretch campaigns
- Geo-triggered prompts
Step 3 — Transaction sync #
From:
- eCommerce
- POS
- Loyalty platform
Flow:
- Transaction → CRM/CDP
- Insider processes event
- Event → Litecard
- Litecard updates pass
Result:
→ real-time wallet updates (points, offers)
5. Data flow summary
Inbound to Litecard
- customer profile
- segmentation events
- loyalty data (points, tiers)
- campaign triggers
Outbound from Litecard
- pass link
- pass status (downloaded / active)
- engagement events (optional)
6. Key use cases
1. Voucher distribution #
- Insider sends campaign
- Litecard embeds voucher in wallet
- Push reminders drive redemption
2. Loyalty visibility #
- Points + tiers shown live in wallet
- Reduces login friction
3. Geo-targeting #
- Trigger notification near store
- Drive foot traffic
4. Lifecycle automation #
- onboarding → reward → reminder → expiry
7. Why this works (positioning)
- Email/SMS = crowded
- Wallet = high intent, persistent channel
Litecard enables:
- direct lockscreen presence
- no app install required
- real-time updates
Result:
- +25% orders
- +93% revenue per customer
- +23% purchase frequency
8. Minimal technical setup
What you need:
- Insider webhook capability
- Litecard API access
- CRM/CDP connection (optional but recommended)
Time to launch:
- Basic: 1–2 weeks
- Full journeys: 3–6 weeks
9. MVP setup (fastest path)
If you want speed:
- Upload customer list (CSV) → Litecard
- Generate wallet links
- Send via Insider email/SMS
- Trigger 2–3 campaigns:
- welcome offer
- reminder
- expiry
This proves ROI quickly.
10. What to avoid
- No identity mapping → duplicate passes
- Over-triggering notifications → fatigue
- Not syncing POS → stale wallet data
- Treating wallet like email → wrong UX
