A Cryptomus alternative
blockwallets uses the same API as Cryptomus (same endpoints, parameters, signature and webhook format); the difference is pricing: blockwallets publishes its rate, 1% per payment dropping automatically to 0.5% with volume, while Cryptomus charges new users 2% and negotiates lower rates. Switching from Cryptomus means changing the base URL and keys.
Data checked 2026-11-03 · Markdown
Side by side
blockwallets and Cryptomus, point by point.
Their figures come from their own website and official docs, linked at the bottom of the page. Prices change; their site is authoritative.
| blockwallets | Cryptomus |
| Fee per payment | 1% per payment, lowered automatically by last month’s volume down to 0.5% (a public tier table, nothing to negotiate); no monthly or setup fee, free withdrawals | 2% for new users; lower rates down to 0.4% by agreement, depending on business type, monthly turnover and integration type |
| Coins and networks | 17 coins (USDT, USDC, USD1, FDUSD, DAI, BTC, LTC, DOGE, BCH, TRX, BNB, ETH, POL, AVAX, OKB, SOL and TON) on 15 networks; USDT, USDC and other stablecoins are credited 1:1 in US dollars | The website gives no total; the API docs’ example lists coins we don’t support, such as XMR |
| Where the money sits | Payments are credited in US dollars to your blockwallets balance; you request withdrawals to your own wallet whenever you like, or set them to be requested automatically (minimum $10.00; each is reviewed by a person, and a new payout address waits 24 hours before its first payout). Online servers hold only a read-only public key (xpub); the keys that move funds are used only in a signing environment isolated from the online services. Sweeps only go to fixed cold-wallet addresses; payouts to merchants are approved by a person and only go to the merchant’s registered withdrawal address | Payments go to your business wallet balance at Cryptomus; the API docs state payouts “are made only from your business wallets balances” |
| Switching cost | Replace https://api.cryptomus.com with https://blockwallets.io and use the new merchant and API key; the rest of the code stays | — |
| Testing | Separate test credentials on public testnets; the payment page has a “simulate payment” button, so the whole flow costs nothing | Test-webhook endpoints send simulated webhooks to your callback URL; the docs describe no separate testnet environment |
| Webhooks | Same signature and webhook format as Cryptomus; failed deliveries are retried for about two and a half days | sign = md5(base64(body) + API key) |
Which to pick
Who each one suits.
Pick blockwallets if
- You want a public rate with nothing to negotiate: 1%, dropping automatically to 0.5% as volume grows
- You already integrate Cryptomus and want an API-compatible backup, or to move over entirely
- You mostly take USDT and USDC and want dollar accounting with withdrawals to your own wallet
- You care that the keys able to move funds never sit on an internet-facing server
Cryptomus suits you better if
- You need coins we don’t support (we have 17; no XMR, for example)
- You rely on API payouts or conversion: our Cryptomus-compatible layer covers receiving only
- You need to go live today: we are in private beta and onboard merchants by request
Switching
Switch over in five steps.
- Request access; once approved, generate a merchant and API key under “Developers › Integration & keys” in the dashboard (one set each for test and live)
- Replace
https://api.cryptomus.com with https://blockwallets.io in your code and use the new merchant and API key - Add your domains under “Website domains”:
url_callback, url_return and url_success only accept these - Run it once on testnets with the test credentials: create a bill, press “simulate payment” on the payment page, check that the webhook signature verifies
- Switch to the live credentials
Compatible endpoints: /v1/payment, /v1/payment/info, /v1/payment/list, /v1/payment/services, /v1/payment/resend, /v1/wallet, /v1/test-webhook/payment and /v1/test-webhook/wallet. Bills are priced in USD, USDT or USDC only. Details in the integration docs.
blockwallets has compatible APIs for Cryptomus, NOWPayments and Coinbase Commerce, plus a native REST API and no-code payment links: every way to integrate.
Can blockwallets replace Cryptomus?
Yes. Endpoints, parameters, the sign signature and the webhook format match Cryptomus, so an existing Cryptomus integration works after changing the base URL and keys.
Do I need to change code to switch from Cryptomus?
Not for receiving payments: change the base URL, merchant and API key. We don’t offer Cryptomus’s payout or conversion endpoints; if you use them, you’ll need another route for those.
How do the fees compare?
blockwallets charges 1% per payment, lowered by last month’s volume to 0.9% from $50,000, 0.8% from $100,000, 0.7% from $250,000, 0.6% from $500,000 and 0.5% from $1,000,000, with the same table for every merchant. Cryptomus lists 2% for new users and down to 0.4% by agreement (checked 2026-11-03).
Is money safe with blockwallets?
Online servers hold only a read-only public key: they can create receiving addresses and read balances but can’t send funds. The keys that move money are used only in a signing environment isolated from the online services. Sweeps only go to fixed cold-wallet addresses; payouts to merchants are approved by a person and only go to the merchant’s registered withdrawal address. You can request a withdrawal to your own wallet at any time, or set up automatic requests; each is reviewed by a person.
Can I try it before deciding?
Yes. Test mode has its own credentials on public testnets, and the payment page has a “simulate payment” button. It costs nothing.
Sources
Where the Cryptomus figures come from
Checked on 2026-11-03 against their website and official docs. Our figures are the defaults in blockwallets’ code (the published fee tiers and network list).
Try it on testnets first.
Test mode is free, with one-click simulated payments.