Buying an app, theme, extension, skill, tool, prompt or MCP server is a
Stripe Checkout away. You do not need an organization: orders are
account-scoped, under /account/orders.
At checkout
Stripe Tax is enabled (automatic_tax), so VAT or sales tax is computed
for your location and added at checkout rather than surprising you on
the invoice.
Two modes exist:
- One-time — a single payment, one
Order. - Subscription — a monthly Stripe subscription.
What a subscription actually bills
Each paid month produces its own order. Not the first month only: every month.
This matters more than it sounds. A subscription listing charges you monthly, so every month has to reach the seller, and every month opens its own 14-day dispute window counted from that month's payment. A problem in month seven is disputable in month seven.
The idempotency is enforced in Postgres on the Stripe invoice id, not in application code: Stripe replays a webhook delivery for up to three days, and a duplicate row here would be a second real transfer to a seller.
What is missing, stated plainly: there is no surface for you to cancel a marketplace subscription yourself yet. The Stripe portal in your organization's billing page carries the organization's Stripe customer, not the one Checkout creates for a marketplace purchase. Contact support to cancel until that ships.
Your money is not released immediately
The seller is not paid at checkout. Funds sit in escrow for 14 days after payment, and the payout cron releases them only once that window closes. That window is your dispute window: see Disputes.
Hiring rather than buying
Agencies and freelancers are not bought, they are contacted: the listing carries a hire flow that opens a lead, and the conversation continues off-platform. Nothing is charged by BoostEcom for a hire.