Cryptomus review

Cryptomus is a hosted crypto-services platform, not a library, CLI or self-hosted server. It combines a cryptocurrency payment gateway, a trading platform and tools for earning passive income. The homepage describes a unified API, with a dedicated API for each tool, and says it is fully documented.

For a business, the payment gateway sits between a checkout or billing system and crypto payment processing. The trading and staking products sit alongside it as hosted services for managing crypto activity. Cryptomus says it supports more than 100 cryptocurrencies; its trading interface is powered by TradingView. The homepage advertises payment fees as low as 0.4% and trading fees as low as 0.04%, while the detailed spot schedule lists tiered maker and taker rates.

This is a vendor-dependent architecture: your application integrates with Cryptomus rather than running the payment service itself. Confirm which tools expose APIs, how transactions and account state are represented, and what happens to funds during withdrawals or service interruptions.

The homepage describes a unified API for the ecosystem and a dedicated API for every tool. It calls the API simple, fast and fully documented. That is the available integration surface to evaluate if you want to connect payment processing or other Cryptomus tools to an application.

The homepage does not name an API protocol, SDK, programming language, CLI or plugin. Before implementation, confirm the API style and endpoints in Cryptomus documentation, along with authentication, payment-status updates, retries, idempotency and error handling. Ask specifically whether the service supports webhooks and whether official SDKs exist for your language; do not assume those features from the phrase “unified API.”

For a production integration, also confirm sandbox access, API versioning and backward-compatibility policy. Those details affect whether Cryptomus can fit an existing billing or order-management flow without custom polling and maintenance work. The stated documentation coverage is a useful starting point, but the homepage alone does not establish integration depth.

The pricing page lists no monthly or annual subscription and no free plan. Payment Gateway (Merchant) charges 0.4%–2% per incoming payment. Auto-Convert is free, as are internal Personal-to-Business wallet transfers. The headline “as low as 0.4%” is therefore the bottom of a range, not a guaranteed rate for every transaction.

Spot Exchange - Lvl 1 lists 0.08% maker and 0.1% taker fees at the $0 monthly-turnover tier. Lvl 2 lists 0.06% maker and 0.095% taker at the $100,001 tier; Lvl 3 lists 0.055% and 0.085% at $250,001; Lvl 4 lists 0.05% and 0.075% at $500,001. The homepage separately advertises trading fees as low as 0.04%, so confirm which product and conditions that rate applies to.

Virtual card issuance is $4, and top-ups cost 3.2%. Network withdrawal fees vary by cryptocurrency and blockchain. Model fees against incoming payment volume, trade mix and withdrawals; ask Cryptomus for the applicable merchant rate before forecasting production costs.

Cryptomus presents its products as hosted services accessed through dedicated APIs. The vendor does not publish an open-source licence or source-availability terms on the homepage, and it does not describe a self-hosting option. Treat it as a hosted dependency unless Cryptomus confirms otherwise in its contract and technical documentation.

The vendor also does not publish data-export or migration details on the homepage. Before storing business-critical payment records or balances, ask what transaction and account data you can export, in which formats, and whether exports remain available after account closure. Confirm how to reconcile pending payments and retrieve historical records if you leave.

Migration effort depends on how much of your payment flow relies on Cryptomus-specific APIs and account behavior. Keep your internal order and ledger records independent of the provider, and avoid making the provider's account view the only record of a transaction. Confirm withdrawal procedures and any restrictions before moving meaningful volume.

The homepage and pricing details do not publish API rate limits, uptime commitments or service-level terms. Confirm those limits, along with authentication controls, incident communication, withdrawal rules and compliance requirements, before making Cryptomus part of a checkout or treasury workflow. Ask how payment status is recovered after timeouts and how account reviews affect access to funds.

Reddit discussions include a user who said they could not access funds and had contacted support for weeks. Other commenters speculated about an account freeze; that explanation is unverified. Separate older threads contain allegations about an ICO and token listings. Those posts are not proof of current payment-gateway behavior, but the fund-access report makes withdrawal and escalation procedures worth checking directly.

Do not treat a hosted payment account as long-term cold storage. Keep independent transaction records, test support and withdrawal processes with limited exposure, and document a fallback payment path. Ask Cryptomus for current security and compliance documentation rather than inferring safeguards from the product range.