---
name: playmos-integrate
description: Integrate the Playmos SDK into a web, engine or backend project for in-app purchases and stablecoin commerce.
---
# Integrate Playmos

Read the [SDK quickstart](https://test.playmos.io/docs/quickstart.md) and inspect the project's existing purchase flow before choosing an integration seam. Default to Base Sepolia for a new integration. Use the package version in the [SDK reference](https://test.playmos.io/docs/reference.md); do not infer method signatures from package names.

## Choose the stack

- Browser or JavaScript: [browser integration](https://test.playmos.io/docs/browser.md).
- Unity, Unreal or Godot: [engine integration](https://test.playmos.io/docs/engines.md).
- Python, Go or C#: [server languages](https://test.playmos.io/docs/languages.md).
- Studio-owned keys and payout configuration: [studio setup](https://test.playmos.io/docs/studio-setup.md).

Reuse the existing client, backend and package manager. Public keys belong in clients; server secrets belong in backend configuration. Never put a secret or wallet private key in client code, logs or a handback.

For purchases, implement pay → backend verification → durable grant once. Persist an idempotency key and expected player, SKU and integer micro-USDC amount before sending. Keep the returned payment ID so a timeout can reconcile the same purchase. Read [payment verification](https://test.playmos.io/docs/payments.md) before implementing fulfillment.

If the task involves leaderboard entries and prizes, follow [contests](https://test.playmos.io/docs/contests.md) instead of treating a purchase receipt as contest admission.

Verify local behavior and report what was actually exercised. Wallet signing, funded spending and production publication require developer authority; missing studio details must not be invented.