Skip to content
Zenq Pay
Merchant sign in

Explore Zenq Pay

Sections of the home page, pricing and developer docs.

Sign in

Merchant dashboard

Going live

Live mode means real payments on main networks into deposit addresses that Zenq Pay controls. This page explains what has to happen first and how your money reaches you.

Custodial collection

Zenq Pay is a custodial collection service. Each payment goes to a deposit address created for that invoice; the key for that address is held by Zenq Pay's isolated signing service, not by you. Funds stay there until the settlement policy allows a transfer to the payout wallet you configured. During that window Zenq Pay controls the funds.

Settlement sends the amount received minus the platform fee and any outstanding refunds to your payout wallet. The fee is a flat amount per paid invoice, set by your plan and the network the customer paid on (see Fees), converted at the invoice's own quote rate and never more than was received. Amounts below the platform's settlement minimum wait until settling is worth the network fee, and amounts above its review threshold wait for an administrator's approval.

Fees

The platform fee is charged once per paid invoice. It is a flat amount, never a percentage of the payment, and it depends on two things: your plan, and the network the customer actually paid on. If a customer switches network at checkout, the fee follows the network the payment arrived on, not the one first shown.

Each invoice keeps the fee schedule in force when it was created, so a later price change does not alter it. Every invoice webhook carries the fee charged in data.fee_cents (integer US cents) and data.fee_usd (the same amount as a two-decimal US dollar string). Until the invoice is paid they may show the plan's standard fee rather than the network's.

Current amounts per plan and network are on the pricing page; the dashboard's Plans & billing page shows them for your plan. The legal terms are in the fee schedule.

1. Apply for live mode

Live mode is off for every new account. An account owner applies in the dashboard under Settings → Go live. The application asks for:

  • legal name, country, address and business category;
  • expected monthly volume;
  • beneficial owner name and email;
  • optionally a registration number and website;
  • your acceptance of the attestation.

Two-factor authentication must be enabled on your account before you can submit (403 mfa_required). An incomplete application is refused (incomplete), and live mode is offered only to businesses registered in the countries the platform currently serves (country_not_supported).

2. Platform review and approval

A platform administrator reviews the application, screens the business and its beneficial owner against sanctions lists, and may ask for more information: you are emailed the request, the application shows it under Settings → Go live, and you answer by updating and resubmitting it. Only a platform owner, signed in with a recent two-factor check, can approve it. Approval is also refused while the platform itself is not ready to accept live payments (for example, no main network ready yet). Account owners are emailed with the decision.

Before approval, creating a live store is refused with 403 live_not_enabled. Because an API key takes its store's environment, there is no way to get a nxp_live_… key until then.

3. Create a live store and key

After approval, create a store with the live environment, then an API key for it under Settings → API keys. Creating any API key requires a verified email. Register live webhook endpoints separately: test and live endpoints and secrets do not mix.

Switch your integration to the live key and live webhook secret. Nothing else changes: the same endpoints, payloads and signatures.

4. Add a payout wallet

Under Settings → Payout wallets an account owner adds the address that should receive settlements, per network. Because this decides where money goes, it is protected more strongly than anything else:

  • two-factor authentication must be enabled (403 mfa_required), and you confirm the change with a fresh two-factor check;
  • every account owner is emailed about the change, whatever their notification settings;
  • a new wallet only takes effect after a delay. On main networks the delay is at least 24 hours by default. Until then, settlements keep going to the previous wallet if there is one, or wait (destination_pending).

If you did not make a wallet change you were emailed about, disable that wallet from the dashboard immediately.

Checklist

  1. Your integration passes the test plan in test mode.
  2. Two-factor authentication is on for every owner.
  3. The live application is submitted and approved.
  4. A live store, live API key and live webhook endpoint exist, and the live secrets are stored on your server.
  5. A payout wallet is added and its change delay has passed.
  6. Make a small live payment and confirm invoice.paid fulfils the order once.