Cryptomus Pricing Overview

I like Cryptomus as a consolidated crypto stack that covers merchant processing, personal and business wallets, P2P and spot trading, and mobile access in one ecosystem, reducing the number of vendors I have to evaluate and maintain across the payment flow, payout, and treasury workflows . I see mature building blocks in the business-facing API, invoicing, modules, and webhooks, and a pragmatic emphasis on operational features such as auto-conversion and recurring billing that are actually useful in a live checkout context.

✅ Merchant payments stack with clear API surface

The business API exposes the essentials I expect for a crypto gateway: create invoices, generate static wallets, payment status lifecycle, refunds, payment history, service discovery, signature verification, and webhook resend/testing. Authentication uses userId plus a signature derived from base64-encoded payload with the API key, which is documented with concrete examples and REST semantics using JSON bodies. This is straightforward to implement in a typical server environment and friendly to standard HTTP tooling and SDK scaffolding.

✅ Invoicing flows and payment link/QR mechanics

From the dashboard flow, I can quickly raise an invoice or payment-by-link, choose who bears the fee, set payment expiration windows, select the settlement currency, and distribute the URL or QR code. Status transitions include active, paid, partially paid, and expired, with post-expiry reconciliation when blockchain confirmations land, which helps with edge cases around network latency and invoice TTLs.

✅ Auto-conversion and recurring payments
Auto-conversion stands out in practice: customers can pay in one asset while I settle to a preferred stablecoin to reduce exposure to volatility. Recurring payments support subscription-type models without having to custom-build logic. These are the kinds of features that reduce operational noise at scale and align well with common e-commerce payment scenarios.

✅ Supported assets and networks across mobile and web

The app store listing and FAQs point to broad asset coverage, including BTC, ETH, USDT and USDC across multiple networks like TRON, Ethereum, BSC, Polygon, Solana, TON, Arbitrum, and more. The mobile wallet lists mainstream assets such as BTC, ETH, SOL, TRX, BNB, DOGE, LTC, LINK, BCH, XMR, SHIB, AVAX, and others, which maps well to real-world payer preferences and reduces conversion friction at checkout. Having both the mobile wallet and the merchant suite under one umbrella simplifies operations for teams that need to test end-to-end flows from a phone as well as the web dashboard.

✅ Trading and exchange features integrated into the same stack

For teams that also need to re-balance or convert proceeds, the platform includes spot trading capabilities with a dedicated trading API, plus referral and market maker programs for those who care about liquidity-side incentives. Even if I don’t lean heavily on the exchange layer, having conversions and simple orders natively available helps treasury flows after payment settlement.

✅ Developer documentation that covers payment, payout, and reference data

The docs include not only payments but also payout endpoints, statuses, webhooks, and an SDK/modules area that references CMS integrations like WooCommerce, PrestaShop, WHMCS, and OpenCart. The presence of both personal and business API sections, along with reference endpoints for currencies and networks, is helpful to keep implementation clean and typed on my side. The request signing examples, REST patterns, and webhook verification specifics reduce guesswork during integration reviews and security assessments .

✅ KYC/AML posture and security controls

The platform positions itself as KYC/AML-compliant, with a fairly standard identity verification flow for account tiers and monitoring of suspicious activity. On the account security side, the stack includes 2FA, PIN, address whitelisting, session controls, and multi-channel notifications, which aligns with baseline controls I expect in a payments environment. Several third-party articles outline these measures and the compliance stance in accessible language, which can help internal risk and compliance teams during vendor evaluation . Review collected by and hosted on G2.com.

Pricing and fee clarity could be consolidated in one canonical, easy-to-find page with examples across scenarios, including auto-conversion, cross-network receipt, and payout behavior under different configurations. Review collected by and hosted on G2.com.