SDKs and libraries
Every script, API and tool for building on Paysum, and when to use each.
| Tool | Use it to | Runs |
|---|---|---|
Checkout embed (embed.js) | Open Paysum checkout in a modal from a button on any website | In the buyer's browser |
Checkout Elements (elements.js) | Build checkout into your own page: cart, email, payment methods and pay button as separate pieces | In the buyer's browser |
| Storefront runtime | Add the cart, product page, search and sign-in to a Liquid theme with data-os-* attributes | On Paysum storefronts, loaded for you |
| Liquid themes | Design your whole storefront | On Paysum's servers |
| Store API | Read and change products, orders, customers, coupons and theme files | On your server |
| Hosted checkout | Create a checkout session on your server and send the buyer to it | On your server |
| Webhooks | Get signed checkout and withdrawal events | On your server |
| Dynamic delivery | Deliver each order from your own server | On your server |
| MCP server | Let an AI assistant manage your store | In your AI client |
| Theme CLI | Edit theme files locally with a live preview | On your machine |
Try the checkout embed live at checkout.paysum.io/demo. Every button there opens a demo checkout, and nothing is charged.
Which one do I need?
- I have my own website and want a Buy button. Use the checkout embed. One script tag and one attribute per button.
- I want checkout inside my page, styled like my site. Use Checkout Elements.
- I want my Paysum store to look different. Start with the visual builder. For full control, edit the Liquid theme.
- I run a server and want to sell or sync data. Use the Store API with an API key.
- My product is made per order. Use dynamic delivery.
Keys and security
Browser scripts (embed, Elements, storefront runtime) never need an API key. Server tools use a store API key. Keep it on your server. See Authentication.
Paysum