Stripe
Overview
Coassemble Embed does not include a direct, customer-facing Stripe integration or a hosted storefront. If you want to charge learners for access, the recommended model is to run payments in your own product/website/portal, then use your backend to gate access and request per-user secure course links from the Coassemble API.
What Embed Supports (and Does Not Support)
- Embed supports: Delivering Coassemble courses inside your website/app via a secure, per-user link generated by your backend using the Coassemble API.
- Embed does not support:
- A hosted storefront for selling courses
- Taking payments on your behalf
- Automatically gating course access based on Stripe payment status
In this model, Stripe handles payments, your backend enforces entitlements, and Embed delivers the course.
Recommended Architecture: Stripe Checkout + Backend Gating + Embed
Use this pattern when you want paid access:
- Host your own site/app/portal
- Your site/app is where learners browse and purchase.
- You implement Stripe Checkout (or your preferred Stripe payment flow).
- Take payment via Stripe
- The learner pays on your site using Stripe.
- Confirm payment and assign access in your backend
- After Stripe confirms payment (for example, via a successful checkout session and/or webhook confirmation), your backend:
- Creates/updates the user in your system
- Marks the user as entitled to the course
- After Stripe confirms payment (for example, via a successful checkout session and/or webhook confirmation), your backend:
- Request a per-user secure course link from Coassemble
- When an entitled user loads the course page, your backend calls the Coassemble API to generate a secure link for that specific user.
- Embed the course in your page
- Render the secure link inside your site/app.
- Only users who have successfully paid (and are entitled in your system) should ever receive a link.
Key Concept
Your application is the gatekeeper:
- Stripe: money movement and payment confirmation
- Your backend: identity + entitlement checks + API call to generate the secure link
- Coassemble Embed: course delivery within your product
Coassemble does not handle payments in this setup.
Additional Information
- Ensure your backend only requests/generates Embed links for users who are authenticated and entitled.
- Use Stripe’s payment confirmation mechanisms (such as webhooks) to reliably grant access after successful payment.
This article is maintained in our help centre. View the original ↗