Connect MemberKit for delivery
MemberKit is a common external members area for courses and digital products. AtomicPay can create buyer access in MemberKit after an approved sale when you configure external members delivery correctly.
Use this guide when your product delivers content in MemberKit rather than inside AtomicPay. For the broader delivery model, start with configure delivery and member access. For callback mechanics, see external members callback URLs.
What MemberKit delivery controls
| Area | Purpose |
|---|---|
| External members area | Tells AtomicPay to provision access outside the platform after payment. |
| MemberKit platform selection | Connects the product to MemberKit instead of another delivery model. |
| Callback URL | Gives AtomicPay the endpoint MemberKit expects for access creation. |
| Product-to-course mapping | Determines which MemberKit area or course the buyer should enter. |
| Post-purchase access timing | Depends on approved sale status, not merely checkout initiation. |
Before you start
- The product exists and is ready for delivery setup.
- Product approval readiness is far enough along for a real buyer test.
- Your MemberKit account is active and the course or members area exists.
- You have the callback or integration URL from MemberKit.
- The plan and offer buyers will purchase are already connected to checkout.
- Support knows how MemberKit access differs from ebook or link delivery workflows.
Connect MemberKit to AtomicPay
- Confirm you are in the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the product in AtomicPay.
[Screenshot: Products list — target product opened.]
- Go to delivery or members area settings.
[Screenshot: Product delivery tab — members area settings visible.]
- Choose External members area.
[Screenshot: Delivery method — External members area selected.]
- Select MemberKit as the platform.
[Screenshot: Platform dropdown — MemberKit selected.]
- Paste the MemberKit callback URL in the required field.
- Example format:
https://memberkit.com.br/callbacks/...
- Example format:
[Screenshot: Callback URL field — MemberKit URL pasted exactly as provided.]
- Save the product settings.
[Screenshot: Product saved — delivery settings persisted.]
- Confirm the checkout link and checkout page are published.
[Screenshot: Checkout Published — link copied and ready for test.]
- Complete a test purchase through the real buyer path.
[Screenshot: Test checkout — payment submitted on live checkout link.]
- Confirm the buyer appears in MemberKit with the correct access.
[Screenshot: MemberKit dashboard — test buyer enrolled in correct course.]
- Verify the sale in Sales and delivery in buyer access troubleshooting if needed.
[Screenshot: Sales detail — approved sale with buyer email matching MemberKit account.]
What to verify before launch
| Check | Why it matters |
|---|---|
| Callback URL matches the right MemberKit workspace | Wrong mapping creates access in the wrong course. |
| Checkout copy mentions MemberKit access | Reduces support confusion after payment. |
| Access is tested after approved sale | PIX pending should not trigger delivery. |
| Webhooks fire on the right event | Automations should not use abandoned or pending events alone. |
| Support can find the sale in Sales | Access issues are faster to resolve with sale evidence. |
Best practices
- Configure MemberKit before sending launch traffic.
- Test with the same payment method your buyers will use.
- Document which MemberKit course maps to which AtomicPay product.
- Align checkout promise with delivery settings.
- Include MemberKit delivery in before-launch checklists.
Common mistakes
- Launching checkout before callback delivery is tested.
- Using different callback URLs between test and production products.
- Granting access when PIX was only generated.
- Confusing MemberKit setup with MemberKit-style promises in checkout but no callback configured.
- Escalating access issues without checking sale status and buyer email in Sales.
FAQ
Is MemberKit the only external members area option?
No. AtomicPay supports other external delivery models too. Use MemberKit when that is where your course content lives. See delivery and member access.
Should I configure delivery before checkout launch?
Yes. Buyers should never reach a live checkout before MemberKit delivery is tested end to end. Follow complete your first-sale workflow.
What if the buyer paid but has no MemberKit access?
Start with buyer access troubleshooting, then verify callback URL, sale approval status, and MemberKit course mapping.
Does MemberKit work with subscriptions?
Yes, but support should understand subscription status and renewal timing separately from initial access creation.