The CMS becomes a marketplace primitive when you wire it to a payment plan withDocumentation Index
Fetch the complete documentation index at: https://kardow.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
purpose: 'cms_item'. The fulfillment pipeline runs automatically:
once the buyer pays, the item is created (or queued for review) without
any custom webhook code.
1. Create the plan
From the dashboard, create apayment_plan and set:
| Field | Value |
|---|---|
purpose | cms_item |
fulfillment | { "collection": "sponsors", "duration_days": 30, "moderation": "auto" } |
provider | stripe (embedded checkout) or invoice (custom redirect link) |
2. Show a checkout button on your site
3. What happens behind the scenes
- The buyerโs form data is stashed in
cms_pending_submissions. - They are sent to checkout (Stripe embedded or custom redirect).
- On payment success, the Stripe webhook calls the unified fulfillment
dispatcher, which:
- reads the pending submission,
- validates it against the collection schema,
- inserts a
cms_itemwithsource = 'payment'andexpires_atbased onduration_days, - emits a
purchase.fulfilledevent.
moderation is set to manual, the new item is created with
status = 'pending_review' and a dashboard notification fires. Otherwise it
goes live immediately.