Features
What Nowgate does, and what comes next
Nowgate is in development. Built features work in the engine today, tested end to end on simulated chains; real networks connect before launch. Coming soon features are planned.
Payments
A deposit address per payment
Create a payment for any of the 19 network–asset pairs and get an address that belongs to it alone (on Stellar, an address and a memo).
Clear statuses
waiting, confirming, partially_paid, finished, expired, failed and refunded, recomputed from the facts on-chain every time something changes.
Under-, over- and late payments
A short payment can be topped up until it expires; an overpayment is credited and flagged; money that arrives after expiry is credited with a late flag.
Confirmations you can trust
Bitcoin waits for more confirmations as amounts grow; the other networks wait for their finalized block, and Base for its safe head. Splitting a payment into small transfers can't lower the bar.
Prices in USD and EUR
Price a payment in a currency and Nowgate quotes the crypto amount from its own rate engine: Chainlink and Pyth feeds and exchange pools, each read checked by a second operator, with a rate only when two independent sources agree. The amount holds until the payment expires; money that arrives later is valued again at the rate of that moment.
Fees, markups and estimates
Let the payer cover the fee, so you receive the whole price, or add a markup. An estimate returns exactly the amount a payment created then would ask for, and the rates endpoint shows every rate and why one is missing.
Checkout
Payment links and hosted checkout
Reusable links that never expire, priced in a currency or an asset, each attempt its own payment. Every payment has a hosted page in ten languages, with a payment-URI QR code and its live status; a link's pages carry your branding and email the payer a receipt.
Donations
Open amounts with up to six presets and an amount of the donor's own within your bounds, a name and a message if they like, or none at all: an anonymous donor's name is never stored.
A widget, buttons and badges
Embed checkout in your page, open it in a 2 KB overlay that tells your page the payment's status, or link a button. The badges come light and dark, their text drawn as outlines.
A sandbox that plays the payer
Make up a payment, an underpayment, an overpayment, a repeat, the wrong asset, a late payment or an expiry, and watch the real rules handle it. Simulated money stays in the sandbox's own books, and never reaches a wallet.
Subscriptions
Plans and free trials
Price a plan in a currency or in one coin, every few days, weeks, months or years, with a free trial if you like. Change a subscriber's plan from their next period.
Each period paid on-chain
Nowgate holds no subscriber's funds: each period is an invoice your subscriber pays like any payment, in the coin they choose, partly or at once, and its payments credit your balance as payments do.
Reminders, grace and dunning
Invoices are emailed ahead of time, with reminders before and after they are due. An unpaid subscription waits out a grace period, then dunning, before it is canceled, and paying brings it back.
A page for subscribers
Each subscriber gets a link to their subscription and invoices, in ten languages, where they pay, change the emails' language or cancel at the end of the period. The API, its webhooks and the sandbox cover it all.
Money out
Payouts, batches and schedules
Pay any asset you hold to your own wallets: one payout, a batch of up to 1,000 as JSON or CSV, all or nothing, or a payout scheduled up to 30 days ahead. The network fee is quoted in the payout's own asset, and you choose who pays it.
Destinations that wait
A new payout address waits 24 hours before it can be paid, at the engine and again at the signer, and you are told the moment one is added. A stolen key can't empty a balance into its thief's wallet.
Keys, limits and approvals
Payout keys only work from your allowlisted addresses. Limits per payout and per day hold each asset, the signer keeps its own, and an account can require a person to approve every payout: no API key can.
Refunds
Refund a payment in whole or in parts, in its own asset. Without the payer's address, send them a page in ten languages where they give it, once; the payment shows what was refunded.
Forwarding
Send each payment on to your wallet as it is credited, or your whole balance once a day at an hour you choose, with the network fee taken from what is forwarded.
Simulated in the sandbox
Sandbox payouts and refunds run every status and webhook without a chain, finished in seconds, and a call fails one or activates a destination at once.
Dashboard and team
One dashboard for the whole team
Payments with filters and CSV export, payment links, balances, payouts and refunds, API keys, and webhook deliveries with replay, all in one place. The sandbox has a dashboard of its own, with its own accounts.
Roles per section
Seven roles from owner to cashier, or permissions set member by member for each section. Nobody can grant what they don't hold, and approving payouts is a permission apart.
A second factor on every account
Every account has an authenticator app, a passkey or a security key, and moving money, adding keys or changing the team asks for it again. Passwords are hashed with argon2id, and guessing locks an account without ever saying it exists.
Approvals by one or two people
Require a person to approve every payout and refund, or a second person who didn't create it. A passkey signs exactly the payouts on the screen, and no API key can approve anything.
Stuck deposits, your call
Coin sent to one of your payments in the wrong asset, or after it failed, waits for you to accept it into your balance or return it to the payer.
An activity trail
Every change made by a member, an API key, a till or Nowgate's operators, with who made it, from which address and when. The team is emailed about new destinations, keys and members.
Point of sale
A till in the browser
Pair a phone or tablet with a one-time code and sell at the counter, with nothing to install. Prices are in USD or EUR, and the payer scans a QR code with their wallet.
Cashiers with PINs
Each cashier signs in with a six-digit PIN, the till locks after two idle minutes, and wrong guesses lock the cashier, then the till, until a manager unlocks it.
Receipts and reports
Print receipts on 58 or 80 mm paper or A4, or email them to the payer. Sales add up per till and per cashier, by day or shift, and export as CSV.
White label
Checkout on your own domain
Point a name such as pay.example.com at Nowgate. Once its DNS records check out, Nowgate obtains its certificate and serves your checkout pages there, with your brand alone, and your links use it.
Emails in your brand
Receipts and subscribers' emails carry your name, logo and accent color, and replies go to your support address. Your logo travels in the email itself, so it shows where remote images are blocked.
Referrals
An affiliate program
Share your referral link, and earn a share of Nowgate's fees on the payments of the businesses that sign up from it, for a year. Shares are recorded in the ledger and join your balance after a hold.
Your own codes
Add codes of your own to tell campaigns apart, and see each one's sign-ups. The businesses you refer are numbered, never named.
Webhooks
Signed events
HMAC-SHA256 over the timestamp and the exact body, with an event ID and type, so your server can verify and deduplicate every event.
Retries and replay
Failed deliveries are retried for about 72 hours, every attempt is logged, and any event can be sent again.
A URL per payment
Send one payment's events to a URL of its own, signed with your default endpoint's secret and checked by the same guard against private addresses. They never reach your other endpoints.
Ledger and API
A double-entry ledger
Balances change only through balanced transactions, and the database rejects anything that doesn't sum to zero or would go negative.
An API that is safe to retry
Idempotency keys on every POST, decimal-string amounts, RFC 9457 errors with stable codes, cursor pagination, and scoped API keys.
SDKs for TypeScript, Python and PHP
Generated from the API's own specification over a small core per language, with no dependencies: retries with idempotency keys, pagination, typed errors and webhook verification built in.
Custody
Keys in a separate signer
Seeds never leave the signer, a separate process that checks every transaction against its own policy before it signs and keeps a hash-chained log of what it signed.
Verified by a second operator
A deposit counts only once a node run by a different operator reports the same transfer and agrees its block is final.
Sweeps into the hot wallet
Deposits on every network (Ethereum, BNB Smart Chain, Polygon, Base, TRON, Bitcoin, Solana, Stellar and Bittensor) are swept to the hot wallet. Native coins pay their own fee, and on Solana the hot wallet pays; token sweeps elsewhere get gas or energy from a wallet the operator funds.
Coming soon
Everything a merchant expects from a crypto payment gateway, built on the same payment and ledger core.
Launch
- The mainnet launch, small limits firstComing soon
Building an integration? The documentation covers everything that is built today.