What you need
| Field | What it does |
|---|---|
| Your Zano server address | Your server's public address-minting route. We call it to get a fresh address for each order. Not secret. |
| Shared secret | A shared secret your server signs with and we verify. It can never touch your wallet. Secret. |
Self-hosting means running the blockchain yourself. You run the Zano wallet app, a wallet helper, a ready-made server, and a public address tool on your computer. This guide walks through it on a Mac.
Money flow
Money
Buyer
Taps your Coin Moebius Buy Button and pays from their own wallet.
Your product page
Your Coin Moebius Buy Button asks Coin Moebius to start a checkout.
Coin Moebius Messages only
Gets a fresh address from your server and shows it to the buyer.
Blockchain
Carries the coins from the buyer straight to you.
Your wallet
Receives the coins.
Your server
Sees the payment land in your wallet and tells Coin Moebius the sale is paid. Your keys and balance never leave your server.
Coin Moebius dashboardSale shows as paid.
No buyer data
Card numbers never reach us. Buyer names, addresses and contact details are stripped before a sale is saved.
Where our bill comes in
The payment goes to you. Our bill comes separately. On Flex, that bill is based on the sales you’ve made, at 2% + 20¢ each. Pro starts at $24 a month with 500 sales included, then a few cents for each extra sale. Business is $99 a month for unlimited sales. Your provider’s fees are separate from ours.
Why we ask for each field
Your Zano server address
When a buyer clicks Buy, we ask your server for a fresh address to show them. That request goes to this one public route. It hands back an address; your wallet stays private behind it.
Shared secret
Your server sends us a signed message whenever the chain tells it something new about an order. Paid is only one of the things it can say. It also reports money that has arrived and is still settling, an amount that came up short, and an order that expired with nothing sent. This shared secret lets us confirm the message really came from your server, so nobody can forge one. It can read nothing and move nothing.
Set up
- Get the Zano app and Node.js
Two free downloads. Get both now.
- The Zano Full Wallet, from zano.org/wallets. This is where you make your wallet. The same download also gives you the two command-line programs you need later, zanod and simplewallet. Installing Zano does not put them on your PATH, so the commands below use their full path. On a Mac they sit inside the app itself, at /Applications/Zano.app/Contents/MacOS/. On Windows they sit next to Zano.exe in the install folder, which the installer defaults to C:\Program Files\Zano.
- Node.js (the green LTS button at nodejs.org). This runs the small server that hands out addresses.
Download the Zano Full Wallet Your computer may block these programs the first time. Step 6 shows how to allow them on Mac and Windows.
- Make your wallet
Open the Zano app and create a new wallet. Then save your words and set a password.
- Choose Create a new wallet.
- Give it a name and note the folder path it shows. You need that path in step 3.
- Write your recovery words on paper, in order, and keep them safe. They are the only key to your money.
- Set a password and write it down too.
- When the wallet opens, copy your receive address. It starts with Zx.
Choose Create a new wallet Write down your recovery words Your new wallet is ready - Make a look-but-do-not-spend copy
Zano can make a second copy of your wallet that sees every payment and hands out addresses, but cannot send a coin anywhere. Zano calls it a watch-only wallet. That copy is the one your server uses, so the program facing the internet never holds a key that can spend. These run at two different prompts, so copy them one at a time. The second one goes to the wallet rather than to Terminal, which matters: the wallet takes full paths only.
1. In Terminal, open your wallet
/Applications/Zano.app/Contents/MacOS/simplewallet --wallet-file 'YOUR-WALLET-PATH'It asks for your wallet password. After that you are typing to the wallet, not to Terminal. Use the plain path from Copy as Pathname, because dragging the file into Terminal adds a backslash that breaks the path.
2. At the wallet prompt, save the copy
save_watch_only /Users/YOUR-NAME/Desktop/shop-watch.walletWrite the full path, starting from the drive or from /Users. The wallet does not understand ~ or %USERPROFILE%. It then asks for a password for the copy, so write that one down too.
3. Leave the wallet
exitFor a first test on your own laptop you can skip this and point step 6 at your real wallet. For real money, do not skip it.
- Make your two secret codes
Zano needs two, because Zano will not open its wallet to other programs without a code of its own. Run the command below twice and keep both. Label them as you go, because they look identical.
openssl rand -hex 32Secret What it does Wallet access code The code programs must show before your wallet answers them. It goes on the wallet helper command in step 6, and into the server in step 7. It never touches the dashboard. Webhook secret Signs every message your server sends us about an order, so we know each one really came from you. It goes into the server in step 7 and into the dashboard in step 9, and it has to be the same in both. You can click Generate in the dashboard for the webhook secret instead. On Windows, run this in Git Bash.
- Make your store and copy the id
Sign in to the dashboard, make a store, and open Store settings. Copy the Store id. It starts with proj_, and the server calls it your project id. You use it when you start the server.
Copy your Store id - Start the wallet helper
This program opens the watch-only copy from step 3 and answers the server. It asks for the password you set for that copy, hidden, so the password never shows on screen and never lands in your command history. Replace YOUR-WALLET-PATH with the path of the copy, and YOUR-WALLET-ACCESS-CODE with the wallet access code from step 4. In Finder, right-click the shop-watch.wallet file and choose Copy as Pathname. Paste it exactly as given, spaces and all, because the quotes already protect them. Do not drag the file into Terminal, which adds a backslash before each space and makes the wallet look for a name that does not exist.
/Applications/Zano.app/Contents/MacOS/simplewallet \ --wallet-file 'YOUR-WALLET-PATH' \ --daemon-address 37.27.100.59:10500 \ --rpc-bind-ip 127.0.0.1 --rpc-bind-port 11212 \ --jwt-secret 'YOUR-WALLET-ACCESS-CODE'The wallet helper is running This uses Zano's own public node, so you skip a 20 GB download. If the wallet cannot connect, that node may be down. If your Mac blocks the program, open System Settings, Privacy & Security, click Allow Anyway, and run it again. On Windows, choose More info, then Run anyway. Leave this window open.
Prefer to run your own node? (advanced)
To use no outside computer at all, run your own node first and wait for it to catch up. The first start downloads the ledger and takes a few hours.
/Applications/Zano.app/Contents/MacOS/zanod --data-dir ~/zano-data --rpc-bind-ip 127.0.0.1 --rpc-bind-port 11211 --no-console --disable-upnpThen in the command above, swap --daemon-address 37.27.100.59:10500 for --daemon-address 127.0.0.1:11211.
- Download and start the server
A ready-made server hands out an address for each sale and watches for the money. You do not edit it. Run these one at a time, in the same Terminal window.
1. Make a folder for it
mkdir ~/Desktop/coinmoebius-zano2. Go into that folder
cd ~/Desktop/coinmoebius-zanoEverything after this runs inside that folder, so keep using this same window.
3. Download the server
curl -fsSL https://www.coinmoebius.com/tools/zano-server.mjs -o zano-server.mjs4. Start a package file
npm init -y5. Install the two packages
npm install @aquarian-metals/coin-moebius-zano @aquarian-metals/coin-moebius-serverThis one takes a few seconds and prints a line about how many packages it added.
6. Start the server
node zano-server.mjsThe first run asks three questions: project id, webhook secret, and wallet access code. It saves them next to the file and never asks again. To change one later, edit coin-moebius-zano.json, or delete it to start over.
Get the ready-made server It asks three questions, then runs Need a different port, or pointing it somewhere else?
The server listens on 8787 and reports payments to coinmoebius.com. Two settings change that, and you put them in front of the start command. Set either one on its own, or both together.
Listen on a different port
PORT=9100 node zano-server.mjsUse this when something else already has 8787. Point ngrok at the same number you choose, so ngrok http 9100 for this example.
Report to a different Coin Moebius
COIN_MOEBIUS_API=http://127.0.0.1:8787 node zano-server.mjsOnly if you run Coin Moebius yourself.
Both at once
PORT=8788 COIN_MOEBIUS_API=http://127.0.0.1:8787 node zano-server.mjsThis is the usual shape when you run Coin Moebius locally, because a local Coin Moebius already holds 8787.
The server prints its port and the address it will report to every time it starts, so you can see at a glance which settings took.
- Put your server online
Your server needs a public web address so we can reach it. A free tool called ngrok makes one.
- Make a free account at ngrok.com.
- Install it. On a Mac, brew install ngrok is the quickest. On Windows, choco install ngrok, or download it from ngrok.com and unzip it.
- Add your authtoken (ngrok shows the exact line on its setup page).
- Run the command below, then copy the https address it shows next to Forwarding.
ngrok http 8787Copy the ngrok Forwarding address If you downloaded ngrok into a folder, run it from there as ./ngrok http 8787. Your free ngrok address stays the same every time you start it.
- Connect in the dashboard
Open Providers, click Connect a provider, choose Be your own provider, then Zano. Paste two things and save.
- Your Zano server address: your ngrok address with /coin-moebius/zano/mint added to the end.
- Shared secret: the webhook secret from step 4.
Connect a provider, Be your own provider Search and pick Zano Paste the address and the secret When you save, we quietly check that we can reach your server. Your wallet helper, server, and ngrok all need to be running.
- Add the buy button to your page
Make a product in the dashboard, then copy its buy button code onto your page. These two pieces go in two different places, so they are separate.
Near the bottom of the page, just before the closing body tag
<script src="https://sdk.coinmoebius.com/v3.3.7/sdk.global.js" integrity="sha384-cojsaUZyZ/LprY5umW55XCXezNxmxlP57mt+OtLHwuWiEtpNoGvPuiV2xCWWTOek" crossorigin="anonymous" defer></script>One line, once per page, no matter how many buttons that page has.
Wherever you want the button to appear
<coin-moebius-buy project-id="proj_yourprojectid" product-id="your-product" amount="59.99" currency="USD" label="Buy now"> </coin-moebius-buy>Swap in your own Store id and Product reference from the dashboard.
- Take your first payment
There is no sandbox for a self-hosted setup, so a small real payment is the test. Keep all three windows running (wallet helper, server, ngrok).
- Open your page, click Buy, and pick Zano. The window shows an address, a QR code, and the amount.
- Send that exact amount from any Zano wallet.
- Wait for confirmations. Zano makes a new block about once a minute and we wait for ten, so give it around ten minutes. The window keeps checking the whole time.
- When it shows the payment is complete, your whole setup is working end to end.
The buy window shows the address The payment is complete
After you connect
Your first real payment is the test, and the step above walks through it. Here is what to check while it settles. Keep all three windows running: the wallet helper, the server, and ngrok.
- After you pay, the buy window keeps checking on its own. Your buyer never has to refresh.
- Zano takes about ten minutes to fully confirm.
- Open the Transactions tab in the dashboard. When the new row reaches Paid, your whole setup is working end to end.
Troubleshooting
Checkout fails right away.
We could not reach your server. Make sure all three windows are running, and that the Zano server address in the dashboard is your ngrok address with /coin-moebius/zano/mint on the end.
The wallet helper will not start.
Zano refuses to run the wallet helper without an access code. Check that --jwt-secret is on the command and that the same value went into the server when it asked its three questions.
The wallet helper cannot reach a node.
The public Zano node is busy or down. Try again, or run your own node and point --daemon-address at 127.0.0.1:11211 instead.
The buyer paid but the order still says Awaiting.
That is normal while the payment confirms. Once the money is on the chain the buy window says the payment was received and is waiting on the network, and it turns into paid at ten blocks, about ten minutes after it lands.
It still says Awaiting after twenty minutes.
Either the server is not running, or its secret does not match. Confirm the server is up and that the webhook secret you typed matches the one in the dashboard.
The buyer paid in the wrong coin.
Zano and Freedom Dollar are separate on the same network, and only the one the order asked for counts toward the amount. A payment in the other one leaves the order at Awaiting, and your server window prints a warning about it.
Good to know
Zano and Freedom Dollar. Freedom Dollar (fUSD) is a coin on Zano that stays at one US dollar. Your buyer picks which of the two to pay with in the buy window. A price in US dollars charges the same number of Freedom Dollars. A buyer who picks ZANO pays at the ZANO rate your server gets from CoinGecko when checkout starts, and the buy window holds that amount for 15 minutes.
Run it on a computer that stays on. The test runs on your own computer. For an everyday store, run the same parts on a computer that stays on all the time, with a fixed web address.
Short downtime is cheap. The server catches up after a short outage and reports the payments it missed. It looks back about half an hour. A payment that landed earlier than that is not reported, and its order stays at Awaiting.
Keep a watch-only wallet for real money. Step 3 makes a copy that can see payments but not send them. Use that copy on the computer that faces the internet and keep your real wallet somewhere else.
Rotating the secret. Make a new webhook secret anytime, then use it in both the server and the dashboard. The server saved the old one, so open coin-moebius-zano.json, change hmacSecret to the new value, and start the server again. The old secret keeps working for 24 hours, so there is no rush.
Questions? Join our Discord