Put a purchase button in your game.

Keep your game and the backend you already use. Choose who processes the payment and who delivers the item, then use the matching SDK integration.

1. Choose your setup#

Your game’s hosting location does not decide its payment provider. Configure only what you use in Game setup. The onboarding guide is optional and can be dismissed.

2. Add the purchase action#

npm install @playmos/sdk@0.3.38

Inside Playmos Hub

Use the SDK communication bridge. The trusted Hub connects the wallet and keeps checkout over the running game. Your game sends an item ID, not a client-defined price.

import {createCheckoutBridge} from '@playmos/sdk/checkout';
 
const bridge = createCheckoutBridge({hubOrigin: 'https://test.playmos.io'});
export async function buyItem(sku, savedRequestId) {
  const capabilities = await bridge.detect();
  if (!capabilities.services.purchase) {
    throw new Error('Purchases are not configured for this game.');
  }
  return bridge.checkout({
    kind: 'purchase', itemId: sku, requestId: savedRequestId,
  });
}
// Call buyItem from your shop button. Persist and reuse the request ID
// for this authenticated player's order after interruption.
// Refresh inventory from your server; wallet approval is not a grant.
 

The host must register the game’s purchase capability and trusted fulfillment adapter first. An uploaded ZIP or shared preview does not automatically enable paid checkout. See bridge configuration and the complete checkout workflow.

Outside Playmos Hub

Use the provided checkout interface or your own in-game UI. Start with the runnable example that matches your backend:

• Playmos payments + your game server
• Your existing checkout and processor
• Order endpoints, callbacks and recovery contract

3. Connect trusted delivery#

Your server authenticates the player, saves the order and verifies payment before granting the item once. Use one grant ledger for callbacks and manual completion. Playmos Managed IAP keeps the payment catalogue; your game keeps item behavior and inventory. Privy supplies wallet signing, not delivery.

Manual backend walkthrough · All IAP variables in one place · Callback verification

4. Buy one item, then test recovery#

1. Open your running game and buy one item on Base Sepolia.
2. Cancel before signing: no item is delivered.
3. Reload a pending checkout: check the same saved payment.
4. Repeat its callback: the backend grants exactly once.
5. Reject an incorrect player, SKU, game, amount or network.

Using an agent?#

Give your agent this guide as Markdown or the IAP integration skill. Public MCP exposes playmos_get_iap_guide and playmos://guides/in-app-purchases without signing in. Start with your existing purchase flow and identify the ownership model before creating a catalogue.

For Apple and Google releases, keep provider-specific SKU mappings and implement native billing, receipt verification, notifications and restore as separate integrations. See the configuration reference.