Test and live

• -Each has its own settings, categories, sellers, buyers, listings, orders, keys, webhook endpoints, and Stripe connection.
• -The key decides which one you reach: msk_test_ or msk_live_. An id from one is not found in the other.
• -Test mode takes Stripe test keys and live mode Stripe live keys, so a test payment can never move real money.
• -Reputation, events, and the request log are kept per marketplace too.

The switch at the top of every screen shows which marketplace you are working on. Live mode is amber, with a warning across the top, so nobody changes production by accident.

Test mode is free, with no time limit. The dashboard's going live screen shows each condition, met or not. Live keys become available as soon as your workspace meets the conditions for going live: a paid plan whose first payment succeeded, the acceptable use policy accepted by any member, and, when payments or seller verification is on, a working Stripe connection in live mode. Nobody reviews your application, and there is nothing to wait for.

If a condition stops being true, the live marketplace becomes read-only until it is true again: reads work, and changes get 403 marketplace_read_only. GET /v1/marketplace says why, in read_only. Nothing is deleted. A payment that fails gives you 14 days before this happens, and a new version of the acceptable use policy gives you 30. Test mode is never read-only for any of these. The one exception is a suspension by MarketSDK staff for breaking the acceptable use policy, which makes both modes read-only, with suspended as the reason, until it is lifted. It deletes nothing.

Nothing is copied from test to live. Set up live the way you set up test: settings, categories, a Stripe key, and webhook endpoints. Your code changes only its key.

the API reference →