# Set up auto-swap Source: https://guide.crypto-now.io/auto-convert-deposits-to-stablecoins-auto-swap Create a per-account rule that automatically converts incoming crypto to the coin you want to hold, every time a wallet is topped up past a threshold. Auto-swap turns one currency into another automatically. You set a rule once — *when this wallet receives at least \$X, convert it from coin A to coin B and send it here* — and CryptoNow runs the conversion on every qualifying replenishment, with no manual step. It's how you keep your treasury in a stable coin without watching wallets. Rules are **per Account**, so set the **Account** toggle (top-right) to the account you want the rule on before you start. Go to **Settings** (the gear in the left nav) and scroll to the **Auto swap** card. Click **Create new**. Auto swap card with a Create new button Fill in the five fields, then click **Submit**: * **Name of rule** — a label for your own reference (e.g. *BTC to USDT (ERC20)*). * **You send** — the currency to convert. * **You get** — the currency to receive. * **Minimum amount in USD** — the threshold. When a top-up brings the sender wallet to at least this value, the swap fires. * **Sender's wallet** — the wallet that's watched; its incoming funds get converted. * **Destination wallet** — where the converted currency lands. Auto swap rule form with name, you send, you get, minimum USD, sender and destination wallets The saved rule appears in the Auto swap card, with edit and delete controls. It's now active and will run on the next qualifying replenishment. Saved auto swap rule listed with edit and delete icons Auto-swap relies on **auto-sign being enabled** (it's on by default). If auto-sign is off, the rule can't execute. See **Secure your account** for the auto-sign setting. Each auto-swap is a live exchange, so it carries the usual swap cost — the network (miner) fee plus the third-party exchange provider's fee, taken from the amount converted. Conversions run on mainnet. # Create your account Source: https://guide.crypto-now.io/create-your-account Register your CryptoNow account with email and get to your dashboard in a couple of minutes. ``` Paste the button (or iframe) snippet into your page. The button renders wherever you place it — here on a storefront's cart. Merchant storefront with a Pay with Crypto button The customer fills their cart and selects **Pay with Crypto**. The hosted widget opens with the order total. Cart with an item and the Pay with Crypto button enabled CryptoNow payment widget opening with the order total They choose a currency and network, then **Proceed to the payment**. Currency and network selection in the widget The widget shows the exact amount, a deposit address, and a QR code, with a countdown until the charge expires. Payment screen with amount, address and QR code Once the funds confirm, the widget shows success with the received amount and transaction hash. Payment received successfully screen with amount and hash The payment appears in **Transaction's → History** as a **Replenishment**, carrying your **clickId** and an **IncomingHash** that matches the widget's hash — so you can tie each on-chain payment back to the exact order. Transaction history showing the replenishment with clickId and incoming hash **Button vs iframe.** The **button** opens the widget in a popup or new tab. The **iframe** keeps the widget inline on your page so the customer visually stays on your site. Both run the same hosted checkout. **Settlement.** The funds land in your account wallet as a replenishment, net of the standard 0.5% replenishment fee, with your `clickId` echoed back on the transaction (`outsideOrderId` in the charge response). Match on `clickId` to reconcile against your store. The widget URL is `checkouts.crypto-now.io`. Set a **custom domain** on the checkout to white-label it as your own. # Permanent deposit addresses Source: https://guide.crypto-now.io/give-clients-a-permanent-deposit-address Give each customer a fixed deposit address — minted by the API when they start a deposit — so repeat deposits always credit, funds settle to your treasury, and a callback fires on every payment. For deposit-driven businesses (casinos, brokers, prop firms), each customer gets a **permanent** deposit address they reuse for every deposit. Your platform calls the API to mint that address the moment a customer starts a deposit, shows it natively in your own UI, and funds sweep into your account (treasury) wallet automatically — with a **callback** on every payment so you can credit the user. A returning customer reuses the **same address**, so repeat deposits are never lost. The deposit loop: picks a method and confirms. on-demand — the address is minted at this moment. natively, no redirect. they land at the address. you credit the user in your system. **Static client wallet vs checkout charge — critical.** A client wallet assigned to a customer is **permanent**: repeat deposits to the same address are **always credited**. A checkout charge mints a **single-use** wallet — re-sending to a previous charge address is **not tracked**. "Same address every time" applies to client wallets only. ## 1. Set the callback URL, then generate API keys Order matters: set the **Callback Url** *first*, Submit, and only **then** generate keys. In **Settings → Account Data**, enter your callback endpoint, Submit, then click **Generate new API keys** — you get a **Public key** and **Private key**. Account settings showing Public/Private API keys and the Callback Url field The **Private key** is server-side only — never ship it to the browser. Treat the keys and the passphrase below as secrets. ## 2. Get your account wallet's Wallet ID + passphrase Wallet operations (and withdrawals) need the **account wallet's Wallet ID + passphrase** for the network you settle on — here the **EVM / Ethereum** account wallet. In **Wallets → Account wallets**, open the wallet's menu → **Passphrase** → **Send code** (passes 2FA) → the **Wallet ID** and **Passphrase** are revealed. Merchant wallet menu with Passphrase tab and Send code button Revealed Wallet ID and Passphrase This is the **account** wallet's ID. You never fetch a client wallet's ID — client wallets are created **by the API**, on demand, in the next step. ## 3. The customer starts a deposit — and the wallet is minted In your platform's deposit screen, the customer picks the method and clicks **Confirm**. Platform deposit screen, USDT ERC20 method selected, Confirm button That **Confirm** is what triggers your backend to call the API. API base: `https://napi.crypto-now.io`. Authenticate with the keys, look up the `currencyId` for the network, then create the client wallet (`typeWallet: user`) — the response's `address` is what you display. ```bash theme={"system"} # 1. Authenticate → JWT curl -X POST https://napi.crypto-now.io/api/public/auth \ -H "Content-Type: application/json" \ -d '{ "publicKey": "", "privateKey": "" }' # → { "token": "" } ``` ```bash theme={"system"} # 2. Find the currencyId (e.g. USDT-ERC20) curl https://napi.crypto-now.io/api/public/currency \ -H "Authorization: Bearer " ``` ```bash theme={"system"} # 3. Create the user's client wallet → returns its address curl -X POST https://napi.crypto-now.io/api/public/wallet/ \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "typeWallet": "user" }' # → { "data": { "id": "", "address": "0x...", "passphrase": "..." } } ``` Your platform shows the returned **address + QR**: Deposit screen showing address and QR, status Waiting for money Store `user → { walletId, address }` and reuse it for that user. The wallet you just minted now appears in CryptoNow under **Client wallets** at `$0.00` — it didn't exist before the customer confirmed: Client wallets list showing the newly created EVM USDT wallet at $0.00 There's also a Node SDK — `crypto-now-node-api-sdk` (npm) — wrapping these calls. ## 4. Repeat deposits reuse the same address Because you stored and reuse the wallet, a returning customer gets the **same address**. Below, a second, separate deposit (different deposit ID) resolves to the identical address — so a customer who re-uses an old address is still credited. A second deposit request showing the same destination address ## 5. The customer pays Once the payment lands, your platform shows it as deposited: Deposit status Deposited ## 6. Receive the callback CryptoNow fires a callback to your URL on each client-wallet replenishment. The body is encrypted; the JWT carries the `walletId` and an encrypted `salt`, so the decrypt is self-contained (decrypt code for Node / PHP / Python is in the API docs). Decrypted, it carries the transaction details you use to credit the user. ```js theme={"system"} import CryptoJS from 'crypto-js'; const decrypt = (encrypted, salt) => CryptoJS.AES.decrypt(encrypted, salt).toString(CryptoJS.enc.Utf8); // req.headers.authorization = "Bearer "; req.body.data = encrypted payload const { id: walletId, salt } = decodeJwt(req.headers.authorization.slice(7)); const finalSalt = decrypt(salt, walletId); const payload = JSON.parse(decrypt(req.body.data, finalSalt)); // → { typeTransaction: "Replenishment", currency: "USDT", amount: "10", // wallet: { id }, payer, incomingTxHash, ... } ``` Confirm deliveries under **Settings → Outgoing Webhooks** — an `InitialReplenishmentDetect` then a `Replenishment`, both delivered (Status `True`): Outgoing Webhooks list with Replenishment entries and the JSON payload If you passed a `clickId` when creating the charge/wallet, it comes back as `outsideOrderId` — use it to map the payment to your order/user. ## 7. Settlement: throughput vs. actual balance The **client wallet** doesn't hold funds — it sweeps everything to your account wallet — so the figure it shows is **cumulative throughput**, not a live balance. Here it reads **10 USDT** (the amount that passed through): Client wallet showing 10 USDT throughput The **account wallet** holds the actual funds: **9.95 USDT** — the 10 USDT deposit minus the **0.5% system fee** (0.05 USDT) on replenishment. The swept replenishment transaction shows the client → account hop, the miner fee (paid in ETH from the account wallet) and the on-chain hashes. Account wallet balance 9.95 USDT with the replenishment transaction details This whole flow relies on **auto-sign being ON** (the default). It fronts gas for the sweep and lets the callback complete — disabling it breaks deposits. See **Secure your account**. # How wallet balances work Source: https://guide.crypto-now.io/how-wallet-balances-work Account wallets versus client wallets, and why the number on a client wallet is throughput — not a spendable balance. CryptoNow has two kinds of wallets, and the figure shown on each means something different. Getting this right matters: the number on a **client wallet** is not money you can spend — it's a running total of everything that has ever passed through. | | Account wallet | Client wallet | | -------------------- | ---------------------------------- | ------------------------------------------------------------- | | **What it is** | Your own treasury wallet | A deposit address assigned to one end-client, per network | | **Balance shown** | Your **actual, spendable** balance | **Cumulative throughput** — everything ever received | | **Permanent?** | Yes | Yes, for a static/API client wallet (same address every time) | | **You pay out from** | This one | Never — funds have already swept out of here | Find both under **Wallets** in the sidebar: **Account wallets** (your treasury) and **Client wallets** (per-client deposit addresses). ## Where the money actually sits When a client sends funds to their client wallet, those funds **auto-forward (sweep)** to your default **account wallet** as a **replenishment** — net of the standard **0.5% replenishment fee** — and a **callback** fires. So your spendable money lives in the account wallet, not the client wallet. The client wallet's "balance" is **cumulative throughput**, not a current or spendable balance. Don't read it as funds on hand and don't try to pay out against it. Always use the **account wallet's** real balance for payouts. ## Worked example A client sends **10 USDT** to their permanent deposit address: * The funds sweep to your account wallet, which credits **≈9.95 USDT** (10 − 0.5% replenishment fee). * A callback fires, carrying your `clickId` so you can attribute the deposit. * The **client wallet** figure goes up by the full 10 (throughput); the **account wallet** shows the real **≈9.95** you can actually use. **Permanent vs single-use.** A static client wallet keeps the **same address every time**, so repeat deposits are always credited — the right pattern for recurring depositors. A **checkout charge** mints a single-use address instead; re-sends to a past charge address are **not** tracked. The "same address every time" promise is the static client wallet, not a checkout link. Reconcile deposits against your own system by matching on **`clickId`** (it echoes back on the transaction as `outsideOrderId`). # Get started with CryptoNow Source: https://guide.crypto-now.io/index Accept crypto payments, pay people out, and manage your treasury — with your funds under your control the whole way through. Everything you need to accept crypto payments, pay people out, and manage your treasury — with your funds staying under your control the whole way through. Pick a track below, or use the sidebar to jump straight to any step. Create your account, switch on two-factor security, and find your way around the dashboard. Payment links, on-site checkout, WooCommerce, permanent deposit addresses, and subscriptions. Withdraw to any address, or pay many recipients at once with a single multisend. Swap between coins and auto-convert incoming deposits to the currency you want to hold. Understand what wallet balances really mean and decode every transaction status and type. Full API reference and integration guides for building directly on CryptoNow. # Make a withdrawal Source: https://guide.crypto-now.io/make-a-withdrawal Send crypto out of your CryptoNow account to any external address, another internal wallet, or a saved contact — with fees, gas priority, and two-factor security. When funds land in your account wallets, you withdraw them straight from the dashboard. CryptoNow estimates the network (miner) fee and the system fee, takes both **on top** of the amount you enter, and asks for two-factor confirmation before anything moves. **Fees are added on top — the recipient gets exactly what you type.** Your wallet is debited the amount **plus** the miner fee **plus** the 0.5% system fee. You never have to back the fees out of the amount yourself. ## Before you start * The wallet you're withdrawing from needs the **native gas coin** of that network. For an ERC-20 token like USDT, that means the account wallet must hold some **ETH** to pay the miner fee. (See [Set up your treasury & gas](/set-up-your-treasury-and-gas).) * Both 2FA factors must be active: an **email code** and **Google Authenticator**. (See [Secure your account](/secure-your-account).) ## Withdraw funds Go to **Transaction's → Withdraw** (or click **Send** on a funded wallet from Home). Your wallets that hold a balance appear here. CryptoNow Home showing a USDT account wallet with a 9.95 balance and recent replenishments In the **Withdraw** dialog: * **Currency** — the coin/token to send (only currencies with funds are listed). * **Wallet address** — the source account wallet. The line beneath it shows the native-gas balance available to pay the miner fee (e.g. `ETH: 0.0058… — $9.22`). * **Sent to** — choose **External wallet** (paste any address), **Internal wallet** (move between your own wallets), or **Address Book** (a saved contact). * **Amount** — type a figure or hit **MAX**. The **Minimum** is per-coin and small (here `$0.01`) — there is no flat minimum. * **Gas priority** — **Low / Normal / Fast**. Faster confirmation costs more miner fee. * **Exchange rate in USD** — a helper to size the amount in dollars. The dialog shows the running **Total** as *Amount + Miner Fee + System Fee*. CryptoNow Withdraw dialog with currency, source wallet, external destination, amount, gas priority, and a Total of amount plus miner fee plus system fee A **0.5% system fee** applies to withdrawals — the dialog states this directly. On a 2 USDT withdrawal that's 0.01 USDT. Press **Submit**. CryptoNow emails a one-time code — enter it and click **Confirm**. Enter 2FA dialog asking for the code from email CryptoNow 2FA email containing a confirmation code Then enter the current code from **Google Authenticator** and click **Confirm**. Withdrawals require **both** factors. Enter 2FA dialog asking for the Google Authenticator code You'll see a **Success** confirmation, and the **Withdrawal** appears in your transaction list with its hashes and the exact miner and system fees. The wallet balance drops by the amount plus the system fee; the miner fee is paid in the network's native coin. CryptoNow Home showing a completed withdrawal of 2 USDT, balance now 7.94, with miner and system fee detail ## Where the fees come from | Fee | Paid in | Taken from | | ----------------------- | ------------------------------------------ | ------------------------- | | **Miner (network) fee** | the network's native coin (ETH, BNB, TRX…) | the source account wallet | | **System fee (0.5%)** | the coin being withdrawn | the source account wallet | The **gas-payer toggle** in your account settings ("Miner Fee for withdrawal / replenishment pays…") governs **client-wallet** flows — replenishment sweeps and client-wallet withdrawals. An **account-wallet** send like this one always draws its miner fee from the account wallet itself, so keep a little native gas there. ## Worked example Withdrawing **2 USDT** from a 9.95 USDT wallet: * Recipient receives exactly **2 USDT**. * **System fee:** 0.01 USDT (0.5% of 2). * **Miner fee:** \~0.0000883 ETH, paid from the account wallet's ETH. * New USDT balance: **7.94** (9.95 − 2 − 0.01). # Pay many people at once Source: https://guide.crypto-now.io/pay-many-people-at-once-multisend Send the same coin or token to many addresses in a single multisend — one on-chain transaction covers up to 200 recipients. Multisend pays out to many addresses at once. You paste a list of addresses and amounts, the dashboard estimates the fees, and it settles in as few transactions as possible. One on-chain transaction covers up to **200 addresses**. Larger lists are split automatically — 1,000 recipients run as 5 transactions, for example. Go to **Payments → Multisend**. On the left, **Token multipayment** lists what each wallet holds — select the coin or token to send. Then choose the source wallet in the **Multisend** panel. Empty multisend page with token list and wallet selector In **Addresses with Amounts**, add one recipient per line as `address;amount` (address and amount separated by a semicolon). For long lists, use **Upload file** with a `.csv`. **Show examples** demonstrates the correct format. Three recipient addresses with amounts entered The footer states the System Fee directly: **\$0.10 per address**. Duplicate addresses can be merged or kept, depending on the option you pick. Select **Next**. To estimate the Miner Fee, the dashboard makes an external call that itself costs a small blockchain fee — confirm with **Continue**. Modal explaining the miner fee estimate requires an external call Check the recipient list and the **Summary**: total addresses, transactions needed, the approximate **Miner Fee** (network) and **System Fee** (\$0.10 per address), and your balance. Multisend review showing recipients, totals, miner fee and system fee Select **Confirm**. You'll see a confirmation that the transaction was processed. Success confirmation for the multisend The payout appears in **Transaction's → History** as a single **Multisend** entry, first **Pending** then **Done**. Expand it for the Payment ID, Miner Fee, System Fee, and hash; **Show multisend addresses** lists every recipient. Transactions list showing the multisend with miner fee, system fee and hash Both fees are paid from the sending wallet's **native coin** (ETH, BNB, etc.): a \$0.10 System Fee per address plus the network Miner Fee. Make sure the wallet holds enough native coin to cover gas and fees before you send. Sending an **ERC-20 token** (USDT, USDC) adds a one-time on-chain **approval** before the payout, so the contract can move that token on your behalf. Sending a **native coin** like ETH skips this step. **Worked example.** 3 Ethereum recipients settled in 1 transaction. Approximate Miner Fee ≈0.0000299 ETH; System Fee ≈0.000192 ETH ($0.30 = 3 × $0.10), both drawn from the sending wallet's ETH. # Recover a wrongly-sent token Source: https://guide.crypto-now.io/recover-a-wrongly-sent-token When someone sends an unsupported token to one of your client wallets, you can still get it out — by exporting that wallet's private key and moving the token from an external wallet you control. CryptoNow automatically credits and sweeps the tokens it supports. If a client sends a **token CryptoNow doesn't recognise** (an obscure ERC-20, an LP token, the wrong network's asset) to one of your static client wallets, it won't auto-credit — it simply sits at that address on-chain, untouched. Because **you hold the keys to every wallet**, nothing is lost. You export the client wallet's private key, import it into any self-custody wallet, and send the token wherever you want. Exporting a private key gives **full control of that wallet** to anyone who holds it. Treat this as a break-glass recovery: do it deliberately, never paste the key anywhere untrusted, and consider the wallet's key "spent" afterwards. **The wallet needs native gas to send the token out.** A client wallet usually keeps a little ETH/BNB/etc. from earlier sweeps. If it's empty, send a small amount of the network's native coin to the wallet address first. ## Recover the token Paste the client wallet address into a block explorer (Etherscan for EVM). You'll see the incoming token transfer that never got swept. Etherscan showing an unrecognised token transferred into a CryptoNow client wallet In CryptoNow, go to **Wallets → Client wallets**, search for the wallet by address, open the **⋮** menu and choose **Show private key**. CryptoNow client wallet row with the actions menu open on Show private key Enter the code from **Google Authenticator** and send it. (See [Secure your account](/secure-your-account) if 2FA isn't set up.) Your private key dialog asking for the Google Authenticator code The key is shown once — copy it. Your private key dialog with the key value and a copy prompt Open any self-custody EVM wallet — this example uses **Ctrl Wallet**; **MetaMask**, **Phantom**, etc. work too, depending on the token's network. Choose **Add → Import wallet or account → Import with Private Key**, pick the network, paste the key, and give it a name. External wallet import menu with Import with Private Key option External wallet Import Private Key screen with network, account name, and key field The imported wallet now shows the stuck token alongside any leftover native gas. External wallet showing the recovered token and ETH balance Send the token out — to the client's correct wallet, to your account wallet, or to an exchange. The network fee is paid from the native coin on the wallet. External wallet send screen with token amount and destination address External wallet confirm-send screen showing from, to, network, and estimated network fee ## Why this happens CryptoNow sweeps **supported** assets to your account wallets automatically. Anything outside that set — an LP token, a one-off ERC-20, a token sent on a network the wallet wasn't created for — lands at the address but isn't tracked. The static client wallet is a **real on-chain wallet you control**, so the funds are always reachable with its key; this recovery is simply how you reach them. Send the token to whichever wallet you want it in — typically the client's correct address or your own account wallet — and the recovery is complete. # Secure your account Source: https://guide.crypto-now.io/secure-your-account Confirm your email and switch on Email 2FA and Google Authenticator in CryptoNow. Both are required before you can view keys, withdraw, or move funds.