COMMERCE_ENABLED; visitor payment creation additionally requires COMMERCE_PUBLIC_CHECKOUT_ENABLED, payment readiness, and the existing merchant policy checks. Memberships require the workspace’s Pro or Lifetime entitlement. Documentation does not enable payments or change fees.
Build the page
- Create a digital product or service in Products. Set its description, category, comma-separated tags, price, stock or slots, and delivery resources. Paid files and delivery links stay behind the signed receipt.
- Add an optional Member Price to a fixed-price product. It applies only after the customer signs in through the emailed member link and has current paid membership access in the same workspace. The checkout email must match that verified identity; typing an email never grants a discount.
- Create membership tiers with a monthly price and a list of benefits. Private member content and selected downloads are available through the member portal.
- For recurring donations, create a plan with Monthly Support enabled. Its price is the minimum; visitors choose their monthly amount and explicitly confirm recurring billing. Monthly support and a regular membership can coexist. Existing subscriptions keep their accepted price and payment destination.
- Select an active Products/Support App in Storefront for one-time support. Its configured cash amounts, custom amount, payment readiness, and merchant policies apply to the page as well as the Widget.
- Enable Show Recent Supporters if desired. Only successful, non-private payments whose supporter explicitly chose public sharing appear. Older gifts are never made public retroactively. The optional supporter email remains private and does not grant account access.
/shop/{workspace_id}; embedding the Products App retains its existing Widget layout.
Messages, ratings, and posts
Products → Community shows top supporters, supporter messages, post activity, and pending comments. Open a support purchase to write or replace the creator reply. Replies appear publicly only when the original gift is eligible for the public wall; they do not send email or change payment state. Top supporters are grouped using supplied customer email, within one workspace and currency. Names never merge people, and gifts without an email remain separate. This is payment attribution, not verified identity or a cross-workspace customer profile. A paid product receipt offers a one-to-five-star rating and optional feedback. The signed receipt is a purchase capability: anyone holding it can update that order’s single rating. Only currently paid orders contribute to the public average; refunded orders stop contributing. Feedback text is not automatically published. In the Post editor, select eligible membership tiers to restrict the body to signed-in customers with current paid access to one of those tiers. Leave the selection empty for a public post. Access changes take effect on publication. A locked post exposes its published title and excerpt as a teaser; keep those fields suitable for public viewing. Private bodies are excluded from public knowledge and Agent retrieval through workspace visibility. Member-only posts use web publication; share the sign-in link instead of emailing the body to a general audience. The Post editor also has an optional community switch. Views count once per browser session per day; likes count once per session. These are approximate engagement measurements, not unique people or historical backfills. New comments wait for owner review. Text is escaped on public rendering. Disabling community hides comments and stops new measurements.REST and MCP
The authenticated Workspace MCP adds eight commerce tools. All requireworkspace_id, an active workspace grant, and COMMERCE_ENABLED. They are absent from the public Page and Agent tool catalogs.
API keys also need
workspaces:read to enter MCP. MCP OAuth tokens are audience-bound to MCP and cannot authenticate REST calls. Registered OAuth clients use browser consent and PKCE; dynamic registration remains disabled.
Collection reads return data plus meta.page, per_page, total, and next_page. Use limit (1–100, default 25) and page (default 1). Additional applicable filters:
- Payments and supporter totals:
type(support,product,membership),status,from, andto(YYYY-MM-DD). Support rows include their message, privacy flag, and reply for authorized operators. - Products:
status,category, andtag. Responses include current price, optional member price, tags, units sold, remaining stock, and verified purchase rating totals, without delivery files or paid links. - Membership subscriptions:
statusandplan_id; responses include the frozen price, cancellation state, and paid-through timestamp. - Plans:
status; responses include perks, monthly-support mode, and active member counts. - Published posts:
tagandvisibility; responses contain metadata, eligible plan IDs, and optional metrics, without private bodies or delivery audiences. Google-derived knowledge remains excluded.
{ "reply": "Thank you for helping this happen." }; MCP additionally takes support_id. Only a successful support payment with a message can receive a reply. REST supports the normal Idempotency-Key middleware; MCP replies replace the stored reply and do not use the setup-tool receipt contract.