Iframe Integration
Iframe Integration
Resell Osteocom courses by dropping a single <iframe> tag into any page. Osteocom hosts the storefront card and runs the checkout — no backend, SDK or payment integration on your side.
What you need to know before you start
- The integration is fully client-side. Your platform only embeds an iframe — Osteocom does the rest.
- Each customer must reach Osteocom with a stable, unique identifier (
partnerUserId) that your platform controls. - The partner domain(s) that will host the iframe must be whitelisted by Osteocom (CSP
frame-ancestors), otherwise browsers will block the embed. - The customer pays on Osteocom, not on your platform. After payment, Osteocom records the activation automatically.
How the flow works
text
┌──────────────────────┐ 1. Embed ┌─────────────────────────┐
│ Partner LMS page │ ───────────────────▶ │ Osteocom iframe │
│ (your platform) │ │ /embed/...?clientId=… │
└──────────────────────┘ └─────────────────────────┘
│
2. Validate │ + render card
▼
┌─────────────────────────┐
│ Card with title / price │
│ "Buy" or "Already │
│ purchased" CTA │
└─────────────────────────┘
│
3. Click "Buy" — exits iframe
▼
┌─────────────────────────┐
│ Osteocom checkout │
│ Customer pays Osteocom │
└─────────────────────────┘
│
4. Activation recorded
▼
┌─────────────────────────┐
│ Next iframe load shows │
│ "Already purchased" │
└─────────────────────────┘Where to go next
→SetupWhat you have to share with Osteocom and what we give back to you. Onboarding checklist.→EmbeddingCopy-paste HTML snippet, full parameter reference, and theming.→User FlowWhat the customer sees: card states, checkout journey, post-purchase behavior.→ReferenceStatus codes, rate limits, CSP rules.