Developer platform

Every way to build on Paysum: REST API, theme CLI, MCP server, checkout embed and webhooks.

Everything you can do in the dashboard has a programmable route. Pick the one that fits what you are building; they all use the same store API keys, so one key system covers every tool.

Store API

REST endpoints for products, orders, customers, coupons and theme code.

Theme CLI

Edit your storefront in your own editor with a live preview, then publish.

MCP server

Let Cursor, Claude and other assistants work on your store with a scoped key.

Checkout

Hosted checkout sessions, a drop-in embed, or Elements for a checkout built into your own page.

Webhooks

Signed events when payments complete and withdrawals settle.

Authentication

Create keys, choose scopes and keep secrets safe.

Which one do I need? #

You want to	Use
Sync products from another system or export orders	Store API
Build a custom storefront theme with Git and your own editor	Theme CLI
Ask an AI assistant to add products, run a sale or restyle the theme	MCP server
Sell from your own website or app	Checkout embed or hosted checkout
Design your own checkout page and keep payment on Paysum	Checkout Elements
Deliver custom goods after payment	Webhooks

Keys and scopes #

Keys are created in Dashboard → Developers → API keys. Each key belongs to one store and carries scopes such as products:read or themes:write. A write scope includes the matching read scope. See Authentication for the full list.