Security & compliance

Built so every payment can be trusted

How NodeGate keeps your money safe, makes sure a paid order stays paid, and keeps bad actors off the network.

Funds

Your money settles to wallets you control

Each payment goes to its own address, derived from a wallet whose recovery words never touch our servers.

  • Public keys only on the payment server. Addresses are created from an extended public key (xpub). The API can watch them but can't spend from them.
  • Optional automatic collection, isolated. If you switch on auto-collect, one isolated worker holds an encrypted key (AES-256-GCM) for one network and can send only to your treasury and your own hot wallet. Switch it off and keys stay offline.
  • Treasury changes are delayed. Changing where money goes takes effect after 24 hours, with an alert and a cancel button, so a stolen login can't redirect funds at once.
  • Small hot wallet, hard limits. Automatic withdrawals use a separate wallet with a small float and a maximum balance; anything above your limits waits for a person.
Payments

A paid order stays paid. A payout is never sent twice.

Finality, not just confirmations

A payment counts only when it is deep enough and the chain marks its block irreversible. Chain reorganisations are detected and handled.

One address per order

No guessing who paid by matching amounts. Every transfer is recorded, including under- and overpayments, so nothing is lost silently.

No double spending

Every outgoing transaction is recorded before it is sent. An unclear one is resolved by its hash and never re-signed automatically.

Signed, reliable notifications

Webhooks are signed with HMAC-SHA256, written in the same database transaction as the payment, and retried until your server confirms.

Idempotent by design

Order IDs and withdrawal references are unique, so a retried request can never create a second invoice or payout.

Withdrawals with approval

Every withdrawal is a request. It's approved by you or your platform, within limits that stop a stolen API key from draining funds.

Platform

Platform and account security

Sign-inPassword plus mandatory two-factor authentication (TOTP); lockout after repeated failures; rate-limited by IP
SessionsSecure, HttpOnly, SameSite=Strict cookies with idle and absolute timeouts; CSRF protection on every change
SecretsKeys and tokens encrypted at rest (AES-256-GCM); API keys shown once and stored only as hashes
TransportHTTPS everywhere; strict Content-Security-Policy on the dashboard and checkout
Audit trailEvery sign-in and every change is logged with who did it and when
EnvironmentsThe sandbox and live gateways are separate deployments with separate databases and keys
MonitoringAlerts for stuck or failed transfers, low gas, held withdrawals and unusual payments
BackupsDaily database backups [describe retention and off-site storage]
Compliance

Only verified businesses accept live payments

Our AML & KYC policy applies to every merchant. Questions from partners and authorities: compliance@nodegate.space.

  • Business verification (KYB). Company registration, proof of business address, and the ID and address of a director or owner, reviewed by a person before live access.
  • Prohibited businesses. We don't serve the activities on our prohibited list, and we close accounts that break it.
  • Sanctions and risk screening. [Describe the sanctions lists and address-screening provider you use]
  • Monitoring and reporting. Unusual activity is reviewed, and reported where the law requires.
  • Record keeping and privacy. Verification records are kept as required by law and protected as described in our privacy policy.

Found a security issue?

Please tell us privately at security@nodegate.space with steps to reproduce. We'll acknowledge it within 3 business days and keep you updated. Please don't access other people's data or disrupt the service while testing.

Ready to get paid your way?

Open a free sandbox account in a minute. Go live once your business is verified.