Selling from your own app: Skalp's checkout API, webhooks and SDKs
Skalp is also an API. Your code can create checkouts, read orders, manage products and subscriptions, and check licenses, while Skalp stays the merchant of record. Every event reaches your server as a signed webhook.
API keys with scopes
Create a key in the dashboard and tick only the scopes it needs, for example checkout:read and checkout:write. Checkout keys are bound to one store when you create them. Skalp stores only a hash, so the key is shown once.
SDKs
- Node and edge runtimes: the
@skalpgg/sdk package on npm. One package for checkout, subscriptions, webhooks and license checks, with types for every response.
- Go: the module
skalp.gg/go.
Webhooks
Skalp sends a signed POST to your URL when an order is paid, refunded or disputed, when a subscription changes, and on product changes, support queries and feedback. The signature is HMAC-SHA256 in the Skalp-Signature header. You can limit a webhook to the products you pick.
Common setups
- A desktop app checks its license key on start. License keys.
- A website or launcher opens Skalp checkout for the logged-in user and unlocks features on the paid webhook.
- A game server picks up purchases itself and delivers them in game. Server stores.
Questions people ask
Who appears on the buyer's card statement?
Skalp. On API sales Skalp is the seller of record, so the charge carries Skalp's name, not your store's.
Can I pass my own data through checkout?
Yes. Custom checkout fields come back in webhooks and API v1.