01
Official Partner · Merchant Payment Review
NOWPayments. Accept Crypto Payments With Invoice, Payment Link, Or API.
Choose NOWPayments when the business needs to turn a customer’s crypto payment into a trackable order, invoice, or API payment flow.
Direct verdict
Stop matching anonymous wallet transfers by hand.
- What is NOWPayments?
- NOWPayments is the approved A Crypto Box partner for merchant crypto payment gateway flows, including invoices, payment links, buttons, plugins, and API payments.
- When should a business choose it?
- Choose NOWPayments when the business needs to turn a customer’s crypto payment into a trackable order, invoice, or API payment flow.
- Can I start with a payment link?
- Yes. Payment links and invoices are direct-request formats when a full store checkout is not required yet.
- Does a gateway replace order management?
- No. The merchant still owns fulfilment, support, settlement records, and the decision to release goods or access.
Product Proof
Create a payment tool
These screens were captured while actively reviewing the product.
NOWPayments at a glance
What the partner setup is built to do.
- 01
Partner status
Approved A Crypto Box payment partner
- 02
Core job
Crypto payment gateway for merchant acceptance
- 03
Direct requests
Invoices and payment links
- 04
Store surfaces
Payment button and supported e-commerce plugins
- 05
Technical control
Payment API with payment and order identifiers
- 06
Extended flows
Recurring or subscription tools and mass payouts
Customer payment flow
Send the invoice. Let the customer pay in crypto. Track the payment against the order.
02
Customer pays in crypto
The customer completes the payment through the gateway flow.03
Track payment status
Match payment status to the order or invoice identifier.04
Settle and record
Route settlement to the merchant wallet flow and keep the order record.Payment surfaces
Invoice, link, button, plugin, and API.
Module
Invoice and payment-link flow
Send a defined payment request with an order reference the business can track.Module
Payment button
Place a crypto payment action where the customer already decides to buy.Module
E-commerce plugins
Connect a supported commerce system when the store already runs on a plugin-ready stack.Module
Payment API
Create payments, pass order identifiers, and manage status inside your product.Payment Order
Payment status and identifiers
Payment ID for the gateway. Order ID for the business.
- TrackPayment and order IDsKeep the payment identifier beside the business order so fulfilment is not based on anonymous wallet matching.
- TrackPayment statusUse the gateway status in the merchant flow before fulfilling the order.
- TrackWebhook mechanicsWhere webhooks are used, treat status updates as operational signals that still need reconciliation against the order record.
Subscriptions and payouts
Keep recurring collection separate from mass payouts.
- 01
Extended flow
Subscriptions and recurring payments
Review recurring tools when the business bills on a repeat schedule and needs payment status tied to each cycle. - 02
Extended flow
Mass payouts
Review mass payout tooling when the business needs outbound crypto distribution as a separate operations flow from customer collection. - 03
Extended flow
Settlement and payout wallet
Define where settled crypto should land and who controls the payout wallet credentials.
Best fit by business type
Match the surface to the selling model.
| Business type | Starting surface |
|---|---|
| Freelancer or agency | Invoice or payment link with an order reference |
| Online store | Payment button or supported plugin inside checkout |
| SaaS or platform | API, status handling, and subscription logic where relevant |
| Payout-heavy team | Separate collection flow from mass payout operations |
Use a simple wallet transfer instead when
A gateway is optional for rare manual transfers.
- Manual transfer
- You handle a rare one-off transfer you can reconcile yourself.
- Manual transfer
- The customer and business already share a trusted wallet destination.
- Manual transfer
- There is no repeating order, invoice, or status workflow to maintain.
What we looked at
Repository facts and merchant operating structure.
Review basis
- Official partner positioning in the A Crypto Box merchant cluster
- Payment request formats: invoices, links, buttons, plugins, and API
- Order and payment identifier structure for merchant operations
- Recurring and mass-payout flows as separate operating flows
- Record-keeping and security handoffs around merchant access
Not claimed here
- No unverified exact fee schedule
- No unverified settlement-time guarantee
- No fake merchant count, plugin count, or success rate
- No guaranteed approval or chargeback-free claim
Related merchant guides
Build the workflow around NOWPayments.
Final NOWPayments CTA
Create the payment request. Track the status. Keep the order record.
NOWPayments FAQ
What is NOWPayments used for?
NOWPayments is positioned as a crypto payment gateway for merchants that need invoices, payment links, payment buttons, plugins, or API-led payment flows with trackable payment and order identifiers.
Should I start with a payment link or an API?
Start with a payment link or invoice when speed and a defined customer request matter most. Choose the API when payment creation, status, and fulfilment must become part of the product.
Do plugins replace custom development?
A supported plugin can reduce custom work when the store already runs on a compatible commerce system. The merchant still needs to test order handling and payment status.
Are subscriptions and mass payouts the same flow?
No. Recurring collection and outbound mass payouts are separate operating flows. Review each against the business model before combining them in one process.
When is a plain wallet transfer enough?
A wallet address can work for a low-volume manual transfer you can reconcile yourself. Use a gateway when you need defined requests, order IDs, and repeatable status handling.