JAVASCRIPT SDKv0.3.20

Set up your studio.

Move from the shared demo to your own test keys, payout wallet and studio-owned receipts.

Start with the public sandbox#

The public IAP key is enough for the first-payment guide. It belongs to the demo studio. A payment created with it is not visible to a different studio’s secret key.

1. Issue your test keys#

Create test studio keysTerminal

curl --fail-with-body -X POST https://api.sandbox.playmos.io/v1/keys \
  -H 'Content-Type: application/json' \
  -d '{"label":"your-studio","payoutAddress":"0xYOUR_STUDIO_WALLET"}'

Replace the wallet placeholder with your studio’s actual address. Store keys.secret as PLAYMOS_SECRET on your backend. Only the publishable key belongs in a browser. Do not commit the response, paste secrets into the playground, or expose them in logs.

2. Set your payout wallet#

If you minted without payoutAddress, configure it with the server API before creating studio IAP payments. There is no SDK setter for this address.

Set the studio payout walletTerminal

curl --fail-with-body -X POST https://api.sandbox.playmos.io/v1/studio/payout \
  -H "Authorization: Bearer $PLAYMOS_SECRET" \
  -H 'Content-Type: application/json' \
  -d '{"address":"0xYOUR_STUDIO_WALLET"}'

3. Keep payment and verification in the same studio#

Create a new payment using your publishable test key, then verify that ID with your matching server secret. The service maps the game_sandbox_iap catalog alias to the studio’s own demo game on this setup path. Keep the returned resource IDs; do not assume aliases are the final IDs.

What belongs where#

You configure	Where
Items, prices, purchase keys	Your game / backend; arguments to pay().
Fulfillment and scores	Your trusted backend and database.
Publisher drafts and release review	Playmos portal publisher workspace.
API keys and payment records	Playmos SDK service, scoped to your studio.
Own-pool signing keys	Your local admin / operator signing environment.
Entry price, clock and split	An immutable series on your own registered pool.

Taking IAP payments is a complete integration. Add contests and economies when your game needs them.

Manage sandbox access in the Hub#

Approved Hub publishers can use the Developer Portal in the local preview to create a test key pair, save their studio payout wallet, revoke keys, and register webhook endpoints. Save secrets when shown; the portal never reads them back into a list. Hub drafts and SDK game IDs are separate.

Keep buildingYour first payment