NOWPayments review

NOWPayments is a hosted crypto payment gateway: a business connects its payment flow to a vendor-operated service rather than installing a self-hosted payment server. It sits between a merchant’s checkout and crypto payment processing, with a personal account for managing transaction history. The homepage promotes acceptance of Bitcoin, stablecoins and 300+ other cryptocurrencies, alongside fiat-to-crypto and crypto-to-fiat conversion.

The service is aimed at businesses adding crypto payments without building coin-by-coin payment handling themselves. NOWPayments also advertises automatic coin conversion and batch processing of up to 1,000 transactions at a time. That makes it relevant to commerce, SaaS and marketplace payment flows, though the exact settlement and custody model should be confirmed with the vendor before connecting it to order fulfillment. This is a payment service, not a local library or CLI.

The homepage’s integration call to action is “Integrate NOW,” alongside ready-made payment solutions and a personal account for managing transaction history. It does not identify an API protocol, SDK, programming language, CLI, webhook format or named plugin. The vendor doesn’t publish those integration specifics on the homepage, so confirm the supported API surface and SDKs in NOWPayments’ developer docs before choosing an implementation.

For an application team, the key questions are how checkout sessions are created, how payment status reaches the order system, and how retries, refunds and expired payment windows are handled. Confirm authentication, webhook signatures, idempotency, test-mode behavior and supported frameworks with the vendor. The homepage includes a warning that its displayed environment is a test environment and says not to send actual funds. Do not treat that notice as proof that a separate sandbox or particular API features are available.

The pricing page lists a 1% starting service fee, with loyalty discounts and enterprise pricing available on request. The homepage says the quoted service commissions exclude blockchain network fees, so the headline rate is not the full cost of every payment. At the 1% starting rate, $1,000 in fee-assessed payment volume corresponds to $10 in service fees before network charges; the final rate may differ if a discount or enterprise arrangement applies.

The pricing page lists no monthly or annual subscription billing and no free plan. It does not publish a free-trial offer. The service fee is the main listed cost that scales with payment activity; ask the vendor how its rate applies across currencies, conversion, refunds and failed or expired payments. Loyalty discount thresholds and enterprise rates are not published, so teams with material volume should request a written quote and clarify any additional costs before estimating production margins.

NOWPayments is presented as a hosted payment service with a vendor-managed personal account. The vendor doesn’t publish an open-source licence or self-hosting option on its homepage, so teams should not assume they can run the gateway in their own infrastructure. Ask whether any integration components are open source and what licence applies before building dependencies around them.

The homepage also does not explain data-export formats or how to migrate transaction records. Before launch, confirm whether you can export payment and customer records, how long the vendor retains them, and whether exports include the fields your finance and support systems need. Replacing a gateway would require changing the payment integration and reconciling in-flight payments; the effort depends on the API and export options the vendor confirms.

The homepage advertises batch processing of up to 1,000 transactions at a time, 24/7 support, AML measures, two-factor authentication, role-based access control and withdrawal whitelisting. It does not publish rate limits or uptime figures on the homepage. Confirm API limits, payment-expiry rules, confirmation handling, escalation paths and what happens when an asset or network is removed before routing live orders through the service.

Reddit reports are mixed. One commenter said a payment window closed after 10 minutes and alleged that a late confirmation left funds unresolved; another user said a payment worked flawlessly. A separate comment described a high volume of support tickets. In a Nano community thread, users objected to the delisting, while a NOWPayments representative cited technical capabilities and resources. These are user reports, not verified service-wide outcomes, but they highlight the need for clear reconciliation and asset-support procedures.