Developers
Cherum inside your product.
A widget, an SDK or an API — three ways in. The widget and SDK ship Exchange today; the API covers Payments, and payout endpoints are switched on per account on request. Your users stay on your site, your brand stays on the screen, and you earn a share of what flows through.
Three routes
Pick the one that matches how deep you want to go.
Widget
A card you drop on your page — iframe or script tag. Themed to your site, no dependency to install.
EXCHANGE
SDK
A React component from npm, with props instead of a URL. For teams who want it inside their own layout.
EXCHANGE
API
REST endpoints and signed webhooks, for flows that never touch our UI at all. Payments are self-serve from the dashboard; payout endpoints exist and we enable them per account — mail [email protected] and we turn them on.
PAYMENTS TODAY · PAYOUTS ON REQUEST
Three lines to embed
Script tag, a div, one call.
The same card that runs on cherum.io. Put your wallet in integrator, set your cut with integratorBps, and match your site with theme, accent and radius.
<script src="https://cdn.cherum.io/widget.js"></script>
<div id="cherum-widget"></div>
Cherum.mount('#cherum-widget', {
integrator: '0xYourWallet', // your share lands here
integratorBps: 20, // your cut, in basis points
theme: 'dark',
accent: '#8B6FE6'
});Revenue share
You earn on what you send
Your wallet goes in the snippet and your share is attributed on‑chain. EVM volume settles to you directly; everything else accrues in the dashboard and we pay it out on request. You set your own non-EVM rate in the dashboard, up to 1%, and change it yourself.
What you don’t inherit
No custody, no support queue
Your users sign from their own wallets and the contract does the rest, so embedding us does not make you a custodian. A failed leg’s money can go back only to the sender’s wallet — it does not arrive in your inbox.