Custodial crypto payment gateway
Zenq Pay collects each payment at its own deposit address, confirms it on-chain and settles it automatically to the payout wallet you set, for a flat fee from $0.10 per paid invoice. No percentage of the sale.
Custodial collection: we hold funds from payment until settlement. Accounts start in test mode; live payments need platform approval.
Order total75.00 USDPay with USDT
on BNB Smart Chain
Payment confirmed
+ 75.00 USDT
Settling to your payout wallet
Illustration only. No payment address.
Supported networks are unavailable right now
No network currently has an asset that can take a payment. Nothing is listed here rather than a list that might be out of date. The payment page always shows the assets and networks a specific checkout accepts.
No live network is enabled on this deployment yet, so payments run on test networks only. A successful test payment never authorises real funds. Networks marked not enabled are switched off and cannot take a payment; do not send funds to them. Read from the platform’s own network configuration when this page was rendered; checkout is the authoritative instruction for any individual payment.
Express invoices
An Express invoice is created for one specific stablecoin on one specific network, and its deposit address exists as soon as the invoice does. Use it for balance top-ups, or whenever you show your own payment screen.
Call POST /v1/express/invoices with the asset, the amount in token units and your order reference. Leave the amount out for an open top-up. An Idempotency-Key is required, so a retry returns the same invoice.
The response already carries the deposit address, the token and the network. Show them on your own payment screen, or send the customer to the hosted checkout URL that comes with it.
The invoice is credited only after the network confirms the payment. Fulfil from the signed invoice.paid webhook; settlement to your payout wallet follows once policy permits.
Express accepts USDT and USDC tokens only. Money that arrives after an invoice expires goes to review and is never credited automatically.
What you pay, and where the money goes
A plain comparison with a typical card processor. The Zenq Pay column is this platform’s own configuration and policy, custody included.
| Entry | A typical card processor | Zenq Pay |
|---|---|---|
| Fee on a sale | A percentage of every sale, usually plus a fixed amount | A flat fee per paid invoice, from $0.10 |
| Share of the amount | Grows with the size of the sale | None. The fee does not change with the amount |
| Recurring charges | Depends on the provider and the plan | None. Paid plans are one-time purchases |
| After the customer pays | The cardholder can dispute the charge later | Credited once the network confirms it. Refunds are a reviewed, manual step |
| Where your money lands | Paid out to a bank account on the processor's schedule | Settles on-chain to your own payout wallet, automatically, once settlement policy permits |
| Who holds it in between | The processor | Zenq Pay does. Collection is custodial until settlement |
Security and custody
What is implemented today, without claims about audits or certifications that have not happened.
Zenq Pay is a custodial collection service. Each payment gets a unique deposit address whose key is held by our signing service. We control the funds until settlement policy permits the transfer to the payout wallet you configured.
The public API and the dashboard never hold signing keys. Signing runs in a separate service with no public network surface. During the pilot the keys are held in software on our own server; they are not held in a hardware security module (HSM) or by an MPC custody provider.
A payment is credited only after network finality, exactly once, and a double-entry ledger is reconciled against on-chain balances. If credited chain history changes, the payment goes on hold until the original transfer passes verification again.
Every event is signed with HMAC-SHA256 over the exact bytes, with a timestamp. Endpoint URLs cannot point at private or metadata addresses, and they are checked again at send time.
Passwords are hashed with Argon2id, and sessions are server-side and revocable. Changing a payout wallet requires two-factor authentication, every owner is emailed, and a policy delay can apply before the new wallet takes effect.
An internal security review of the platform was completed in October 2026. An independent, third-party review is planned but has not yet taken place. No audits or certifications are claimed, and no uptime commitment is made.
Supported tokens. On BNB Smart Chain, the USDT and USDC accepted are the Binance-Peg USDT and Binance-Peg USDC tokens: representations issued on BNB Smart Chain by Binance, not tokens issued there by Tether or Circle themselves. On Ethereum, USDT and USDC are the issuers’ own contracts. Checkout always names the exact token and network to use.
For developers
nxp_test_…) from your server only, never from a browser.POST /v1/invoices takes a decimal-string amount. An Idempotency-Key makes a retried request return the same invoice.X-NexusPay-Signature: an HMAC-SHA256 over the raw body and a timestamp. Reject anything older than 300 seconds.invoice.paid should credit an order. Deliveries are at-least-once, so deduplicate on the event id.Every account starts in test mode with its own keys. Test-network tokens have no value.
# Create an invoice in test mode
curl -X POST https://<api-host>/v1/invoices \
-H "Authorization: Bearer nxp_test_…" \
-H "Idempotency-Key: order-1001" \
-H "Content-Type: application/json" \
-d '{"amount":"75.00","currency":"USD","merchant_order_id":"1001"}'
# 201 { "public_id": "chk_…", "status": "pending",
# "checkout_url": "https://…/pay/chk_…" }Works with the platform you run
Zenq Pay fits the store you have today. Install the DHRU Fusion module, or connect any backend through the REST API. Either way the order is credited from a signed webhook, and collection stays custodial until the funds settle to your wallet.
IMEI / unlock services: add funds with crypto
Upload the module, activate Zenq Pay under Payment Gateways, then paste your store API key and webhook secret. Your customers add funds in USDT or USDC on the hosted checkout, and the DHRU invoice is credited once, from the signed webhook only.
Available
Your own backend: create invoices, receive signed events
The path for any custom platform. Create an invoice from your server, send the customer to the hosted checkout or show the Express address yourself, and fulfil the order when the signed invoice.paid event arrives.
Available
Create a hosted checkout from the merchant workspace and share the link or its QR code. There is no payment form to build, and each link has its own status and timeline in the workspace.
Install the module, or create an API key and register a webhook endpoint. Every account starts in test mode with its own keys.
They choose one of the coins and networks your checkout offers and send from their own wallet. The payment page shows the exact amount and address.
Once the network confirms the payment, the signed event credits the order on your side. Settlement to your payout wallet follows automatically once settlement policy permits.
Every setup guide is in the developer docs.
Pricing
Start without buying a plan, or buy one once: paid plans are lifetime purchases with no monthly renewal. The fee is charged once when an invoice is paid, never as a percentage of the amount. These figures are read from the platform, not typed into this page.
$0.50 per paid invoice
$0Start without a plan purchase
No plan purchase required
$0.25 per paid invoice
$199One-time purchase
Lifetime plan / no monthly renewal
$0.10 per paid invoice
$499One-time purchase
Lifetime plan / no monthly renewal
Read from the platform’s own configuration (version 1) when this page was rendered. Applies to future invoices and purchases only. A one-time plan purchase and the fee per paid invoice are separate amounts. The fee shown is the standard rate; it depends on the network the customer pays on, and the pricing page lists it by network.
The fee is charged once when an invoice is paid, and it follows the network the customer actually paid on. The amount on each plan card is the standard fee, charged on any network this table does not list.
| Networks | Free | Pro | Elite |
|---|---|---|---|
| BNB Smart Chain, Polygon, Arbitrum, Base, Optimism, TRON, Binance Pay | $0.50 | $0.25 | $0.10 |
| Ethereum, Bitcoin | $1.90 | $1.65 | $1.50 |
Fees apply where the network is available: a network listed here is not necessarily enabled, and only networks currently enabled on the platform accept payments. Checkout shows the networks a customer can pay on. Each invoice keeps the fee schedule in force when it was created.
Draft. Pricing and legal disclosures remain draft. Live purchases require activation. Read the full pricing details.
Your next step is a small one
Explore the complete flow with test-network tokens before you go live. Live payments need platform review and activation.
Start in test mode