JAVASCRIPT SDKv0.3.38

Choose your language.

Try it first

Choose an installable supported package#

You need Your target runtime and package manager.

Check the published version and platform support below.
Install that exact package in a small sample project.
Run one documented test request before adding it to the game.

Check your result The package resolves and your runtime can run the supported API.

JavaScript handles browser wallets. Server packages and HTTP handle verification and backend work.

Published packages#

Package	Version / public availability
JavaScript / TypeScript	@playmos/sdk 0.3.38; browser and Node. Node 22 is supported.
C# / .NET	Playmos.Sdk 0.1.1-preview; server REST, no browser wallet signing.
Python	playmos 0.1.0a1; server REST.
Go	No public Playmos package; use direct server HTTP.
Engine bridges	See the engine support matrix; no public Unity UPM.

Pinned installsTerminal

npm install @playmos/sdk@0.3.38
dotnet add package Playmos.Sdk --version 0.1.1-preview
pip install playmos==0.1.0a1

Registry versions were checked on October 7, 2026. Preview/alpha clients do not necessarily expose every field available through JavaScript or HTTP. Check the response before relying on a chain-provenance field or a feature beyond the package’s public methods.

Verify over HTTP#

On your server, read GET /v1/payments/:id with the secret belonging to the studio that created that purchase. Require a successful HTTP response and matching ID, player, SKU, canonical amount, status === 'confirmed' and verifiedVia === 'chain'.

Server receipt readTerminal

curl --fail-with-body "https://api.sandbox.playmos.io/v1/payments/$PAYMENT_ID" \
  -H "Authorization: Bearer $PLAYMOS_SECRET"

Python server verification#

Server HTTP verificationPython

import json, os
from urllib.request import Request, urlopen
from urllib.parse import quote
 
def verify_purchase(payment_id, expected):
    req = Request(
        "https://api.sandbox.playmos.io/v1/payments/" + quote(payment_id, safe=""),
        headers={"Authorization": "Bearer " + os.environ["PLAYMOS_SECRET"]},
    )
    with urlopen(req, timeout=15) as response:
        receipt = json.load(response)
    ready = (receipt.get("id") == payment_id
        and receipt.get("status") == "confirmed"
        and receipt.get("verifiedVia") == "chain"
        and all(receipt.get(k) == expected[k]
                for k in ("playerId", "sku", "amount")))
    return ready, receipt
# Only grant once in your database transaction after ready is true.

C# and Go#

For .NET, PlaymosClient.VerifyAsync(id) is the published server method. Treat IsConfirmed as one status check, not complete purchase validation. If your package’s model omits provenance, use the HTTP response directly. For Go, build a request with a context/deadline, require a 2xx status, decode JSON and apply the same matching rules before a durable grant.

If it did not work#

A source candidate or planned language binding is not an available registry release; use supported REST or the browser host path.

Try one variation Compare the installed version with this guide’s example version. Identify unsupported calls before using them.

Continue with the next guide →

import { Playmos } from '@playmos/sdk';
export async function verifyOnYourServer(
secretKey: string, paymentId: string,
expected: { playerId: string; sku: string; amount: string },
) {
if (!/^sk_(test|live)_\S+$/.test(secretKey)) {
throw new Error('Use your server-only secret key.');
}
const server = new Playmos({ apiKey: secretKey }); // sk_… stays on your server.
const result = await server.verify(paymentId);
if (result.status !== 'confirmed' || result.verifiedVia !== 'chain'
|| result.id !== paymentId || result.playerId !== expected.playerId
|| result.sku !== expected.sku || result.amount !== expected.amount) {
return { readyToGrant: false, result };
}
// Use canonical decimal strings for expected amounts.
// Atomically record a single grant for this payment ID in your database.
return { readyToGrant: true, result };
}