For a closer look at the topic, consider help api alongside the options and criteria discussed below.
Integrating cryptocurrency payments into an existing platform requires more than slapping a checkout button on a webpage. You need a reliable infrastructure that handles currency conversion, transaction tracking, and payout routing without manual intervention. The help API from NOWPayments provides exactly that — a programmatic interface for building crypto payment flows directly into your application, store, or service. If you are looking for detailed documentation on these endpoints, the help api resource at https://nowpayments.io covers every command and parameter you will need.
This guide walks through what the API does, how it works under the hood, and what you can build with it.
What the API Handles
At its core, the API is a set of RESTful endpoints that let your backend create payments, check their status, query supported currencies, and receive real-time notifications when transactions change state. Everything runs through a single API key that you generate inside your account dashboard — no complex onboarding, no separate credentials for different endpoints.
The main capabilities break down into several areas:
| Capability | What It Does |
|---|---|
| Payment creation | Generate a unique payment address for each order |
| Status checking | Query whether a payment is pending, confirmed, or failed |
| Currency listing | Get the full list of supported cryptocurrencies |
| Price estimation | Calculate how much you will receive after conversion |
| Minimum amount checks | Verify the smallest acceptable payment per currency pair |
| Instant Payment Notifications | Webhook callbacks pushed to your server on status changes |
You do not need to run your own exchange or maintain hot wallets. When a customer pays in a cryptocurrency you do not hold, the processor swaps it automatically and routes the outcome to your designated wallet.
Getting Started
Setting up the API involves three steps: creating an account, configuring your payout wallet, and generating your API key. The key is a long random string with no predictable pattern, which makes brute-force attacks impractical. Store it in your environment variables — not in source code — and pass it in the request headers for every endpoint call.
Once the key is active, your system can start issuing payment creation requests. Each request returns a payment ID, a deposit address, an amount, and an expiration window. Your frontend displays the payment details to the customer while your backend monitors the transaction through status queries or IPN webhooks.
Customizing Payment Behavior
Several options let you adjust how payments behave once they are created:
- Outcome currency: Choose which cryptocurrency the customer receives as the final destination. Pay in ETH, get paid in BTC — the conversion happens behind the scenes.
- Fixed price: Lock the fiat value of the order so the customer sees a stable amount regardless of market volatility.
- Multiple payments per order: Allow a single order to be split across different cryptocurrencies, useful for large purchases where no single coin holds sufficient liquidity.
- Callback URL: Point Instant Payment Notifications to your server endpoint so your system updates order status automatically.
Core API Commands
The API exposes a small but focused set of commands. Each one maps to a specific HTTP method and endpoint.
| Command | Method | Purpose |
|---|---|---|
| GET API status | GET | Verify the API is operational |
| GET available currencies | GET | List all supported cryptocurrencies and networks |
| GET estimated price | GET | Calculate expected payout after conversion |
| POST create payment | POST | Generate a new payment with address and amount |
| GET payment status | GET | Check current state of an existing payment |
| GET minimum payment amount | GET | Retrieve the lowest acceptable amount for a currency pair |
The POST create payment endpoint is the most frequently used. You send the order amount, the currency you want to accept, and optionally your callback URL. The response contains everything needed to display payment instructions to the customer.
The GET estimated price endpoint is particularly useful for dynamic pricing scenarios. Instead of hardcoding exchange rates, your system calls this endpoint just before presenting the checkout page to show the customer exactly how much they need to pay in their chosen cryptocurrency.
Instant Payment Notifications
Relying solely on polling for payment status wastes resources and introduces delays. The IPN system pushes notifications to your server whenever a payment moves from one state to another — pending, confirming, completed, or failed. Your webhook handler should validate the request signature, update the order in your database, and trigger fulfillment logic such as shipping or digital delivery.
IPNs include the payment ID, the new status, the currency, and the transaction hash. Use this data to reconcile orders against your ledger and to surface accurate information to customers who ask about their payment progress.
Minimum Payment Amounts
Every cryptocurrency pair has a minimum payment threshold that fluctuates based on network fees and market conditions. For major coins like Bitcoin, Ethereum, Litecoin, and Tron, the minimum typically sits around $2 in half-conversion terms. Other tokens range between $3 and $5. If your business model involves microtransactions or low-value orders, query the minimum amount endpoint in real time rather than assuming a static floor. This prevents orders from being rejected at the blockchain level due to insufficient fees.
Specialized Integrations
Beyond standard e-commerce, the API supports tailored workflows for specific industries.
Mass payouts let you distribute funds to multiple recipients in a single batch operation. This is useful for affiliate programs, payroll systems, or marketplace settlements where you need to send crypto to many addresses efficiently.
Casino and gambling platforms benefit from the API’s ability to handle high-volume, low-latency deposits. The specialized integration includes features designed for gaming environments where instant confirmation matters and player funds must move quickly between accounts.
Both of these use cases share the same authentication mechanism and follow the same request-response patterns as the standard payment flow, making it straightforward to extend a basic integration into a more complex system.
Security Considerations
API keys provide the first layer of protection — they are randomly generated, extremely long, and impossible to guess through brute force. Beyond that, always enforce HTTPS for webhook endpoints, validate incoming request signatures, and restrict outbound API calls to whitelisted IP addresses if your hosting provider supports that feature. Never log API keys in plaintext, and rotate them immediately if you suspect exposure.
When to Use the API Versus Plugins
If you run a Shopify, WooCommerce, or similar storefront, plugins offer a faster path to accepting crypto. They require zero coding and connect through the platform’s extension system. The API is the right choice when you need custom checkout flows, integrate payments into a non-standard platform, build a mobile app, or require programmatic control over every step of the payment lifecycle.
The API gives you full visibility into each transaction and lets you build exactly the experience your users need — without being constrained by what a plugin developer decided to expose.