Mist Network
Follow channel
Support

Trust and security

This page explains how mistKET protects money, accounts and integrations. It describes how the system works today.

1. How funds move

The customer pays to a mistKET address assigned to the invoice. Once the payment reaches the confirmations the network requires, the invoice is marked paid and the amount, minus the fee, is credited to your store balance.

This is a custodial model: your balance stays in mistKET wallets until you withdraw it.

  • No private keys are stored on the server. Payment addresses come only from watch-only wallet addresses; private keys are never entered into the system.
  • Every balance change writes a ledger entry. Balances can be rebuilt from the ledger when needed, and manual adjustments also leave a ledger trail.
  • The same invoice cannot be credited twice.
  • Stores allowed to use an external address can receive USDT (TRC20) on their own address. The money then goes straight to the store; mistKET only watches the payment, does not credit a balance and takes no fee.

2. Payouts

  • You request a payout in the panel. The amount is reserved in your balance and the address is checked against the network you chose.
  • An administrator on our team reviews and approves every payout. After sending, the transaction hash is saved on the payout.
  • You can cancel a payout until it is approved. The amount of a cancelled or rejected payout returns to your balance.
  • An approved payout is being sent and cannot be cancelled.

3. Account security

  • Two-step verification: turn it on in Settings with an authenticator app (TOTP). When it is on, sign-in asks for a 6-digit code; a code cannot be reused, and 5 wrong attempts lock sign-in for 5 minutes.
  • Recovery code: use it if you forget your password or lose access to your authenticator app. You can view, download and renew it in Settings. A used code is renewed automatically.
  • You can sign out of sessions on other devices in Settings.
  • Sign-in, sign-up and password reset attempts are rate limited.
  • Signing in to the admin panel requires a one-time code sent over Telegram in addition to the password.

4. API security

  • Every API request is signed with HMAC-SHA256 using your API secret. Requests with a timestamp more than 5 minutes old or ahead are rejected.
  • Signature version 2 also signs the method, path and a one-time nonce; the same nonce is never accepted twice.
  • IP allowlist: you can limit the API to addresses you list (IPv4, IPv6 or CIDR, up to 20). An empty list means no restriction.
  • You can revoke API keys in the panel. A project that is not approved or has been closed cannot create invoices through the API.

5. Webhooks

  • Every webhook is signed with HMAC-SHA256 using your webhook secret (X-Mistket-Signature and X-Mistket-Timestamp headers). You can rotate the secret in the panel.
  • If your endpoint answers with anything other than 2xx, the webhook is retried after 10 s, 30 s, 2 min, 10 min, 30 min, 1 h, 2 h and 3 h. That is 9 attempts over about 7 hours. Retries run from a job that starts every minute, so the short gaps can stretch to a minute.
  • Webhooks are only sent to public addresses. Local and private network addresses are rejected, and the address is checked again at send time.
  • In the panel you can resend the latest webhook and send a test event.

6. Rates, under and over payments

  • The rate is locked when the customer picks a network. The crypto amount stays the same for the life of the invoice (30 minutes by default).
  • A store can set an underpayment tolerance (up to 10%). A payment within that margin counts as paid in full.
  • If an underpayment arrives while the invoice is open, the time is extended by 30 minutes (up to 3 times). The customer can send the rest to the same address.
  • If time runs out after a partial payment, the invoice stays under review. The store can accept it for the amount received; the fee is then charged on the amount received.
  • A payment more than 1% above the amount is marked overpaid and still counts as successful. The full amount received is credited to the balance.

7. Late payments

After an invoice expires, its address is watched for 10 more minutes. A payment that arrives in that window is still applied to the invoice.

A payment that arrives later, or does not match any invoice, is not credited automatically. Our team is alerted and reviews it by hand. If you sent such a payment, message us at @mistnetwork with the transaction hash.

A transaction dropped from the network (never confirmed and replaced by another one) is removed from the invoice, and the invoice waits for payment again.

8. Account review

mistKET has no separate mechanism for freezing part of a balance. Reviews use these steps:

  • New projects can accept payments only after an administrator approves them.
  • A project can be closed. A closed project cannot create invoices, use the API or request payouts; its balance stays in the ledger.
  • Because payouts are approved by hand, a suspicious payout can be rejected. The rejected amount returns to the balance.

9. Audit log

Important actions are recorded with who did them, when and from which IP address. These include sign-ins, two-step verification changes, password and recovery code actions, API keys, the IP allowlist, the webhook address, payout requests, approvals, rejections and sends, manual invoice confirmations and balance adjustments.

10. Reporting a security issue

If you found a vulnerability or see activity on your account you do not recognise, contact support at @mistnetwork or write to [email protected].

Please tell us before sharing details publicly. Never share your password, recovery code or API secret with anyone; our team will not ask for them.

Mist NetworkMist Network