Deposit & split
API-created addresses, automatic distribution to merchant / platform / affiliates.
Deposit wallets, payment splits, and utility NFTs — one REST API. Register, get keys, integrate.
Give each payment or customer a deposit address. Funds settle on-chain to your rules.
Ephemeral wallets for one-shot checkouts, or client wallets reused per user. Native splits to merchant, platform, and affiliates.
Memberships, licenses, and order receipts — mint from your backend or import a mint already on-chain.
Self-serve collections under your API keys. Mode A: NxtGateW mints after you confirm payment. Mode B: index an external on-chain mint. Same webhook: nft.minted.
Background workers handle mint confirmation, splits, and lifecycle txs.
You call the API once; workers broadcast, wait for confirmations, and notify you.
Know when a deposit lands, a split finishes, or an NFT is minted.
Typical merchant path — payment confirmed, then wallet settle and/or NFT.
Register on the platform, create API keys, then ship wallets and NFTs without running your own chain ops.
Everything is available after self-serve signup — docs, console, and OpenAPI included.
API-created addresses, automatic distribution to merchant / platform / affiliates.
You confirm payment; NxtGateW mints on-chain and notifies you.
Something already minted on your contract? Import the tx — no double mint.
Register, get keys, open the console — no custom onboarding required to start.
Polygon and Ethereum for NFTs; wallet networks per your account config.
NxtGateW stays the infrastructure layer. Customers stay on your product.
Create, fund detection, and split lifecycle via REST.
Collections, Mode A mint, Mode B import, metadata, lifecycle.
Workers confirm mints and run splits in the background.
Guide, OpenAPI, console, HMAC, idempotency.
Credentials, encryption, signatures, and queue monitoring are part of the product — see the developer guide and NFT modes.
Private keys encrypted at rest when stored by the platform; export when your model requires it.
Optional request signing with timestamp and nonce; reused nonces rejected as replay.
Outbound events verified with platform signatures and IPN tokens.
On-chain mints against configured contract addresses with confirmation waits.
Merchant, PSP, and admin roles with API credentials scoped to your account.
Operations history, webhook delivery status, and admin requeue for failed jobs.
Wallet API · NFT Mode A/B · Webhooks · OpenAPI · Console
Create an account for API keys, or message us if you need a walkthrough.
Docs: https://nxtgatew.com/docs
Console: API console
Create deposit wallets with on-chain splits, and issue utility NFTs (membership, license, order receipt) through one API — either platform mint (Mode A) or import an existing on-chain mint (Mode B).
No. Register on the platform, create API keys, open the docs and console. Collections and wallets are scoped to your merchant account.
Mode A: after payment, call POST /nft/nfts — NxtGateW mints. Mode B: if a third party already minted on your contract, call POST /nft/nfts/import with the tx_hash. Never do both for the same purchase.
Create a deposit wallet with merchant (and optional affiliate) payout addresses. When crypto arrives, workers split on-chain according to the snapshot stored on that wallet.
NFT module: Polygon, Amoy (sandbox), Ethereum. Deposit wallets: networks enabled on your account (typically Polygon / Ethereum).
Open /docs/merchant-api, save your keys in sessionStorage, then use Wallet or NFT (Mode A mint / Mode B import).