Integration
Four things to wire up to go live with Bluecom eSIM Shop.
Four things to wire up:
- Authentication — the path-based referral link and optional HMAC signing for SSO.
- Embedding — open the Shop in an iframe, WebView, or Telegram Mini App.
- Session lifecycle — how the two token layers behave and what to do on expiry.
- Payment return — notify your app when the user finishes (or abandons) checkout. Contract TBD.
Mental model
Bluecom issues you a provider
slug. You open a path-based referral link (/<slug>/<sale_channel>). To pre-authenticate a user (SSO), your backend signs a short-lived identity tail; skip signing and they enter as a guest. The Shop mints a channel session, issues cookies, and renders.
The Shop is self-contained inside the iframe/WebView. You do not call any Bluecom API directly during normal operation — events come back via tracking events and (eventually) the payment webhook.