NoxPos User Guide

What is NoxPos?

A non-custodial stablecoin checkout stack for stores and online sellers — wallets you control, rails you pick.

NoxPos helps merchants accept USDC and USDT without becoming a crypto bank. Customers pay on-chain to receiving addresses you configure. Settlement funds never sit in a NoxPos custody wallet.

The platform spans an in-store Cashier POS and online integrations (WooCommerce, Shopify, Hosted Pay Page, Pay Button SDK). One merchant identity, shared wallets and fee account patterns — different surfaces for different businesses.

This User guide explains audiences, design intent, and fit. Detailed how-to for Cashier lives in the Cashier Usage Guide; plugin install manuals live under each product’s docs.

Design principles

Every NoxPos product follows the same settlement story so finance and ops can reason once, then pick the surface that matches their stack.

• Non-custodial by default — customer → chain → your wallet; NoxPos does not hold store settlement.
• Exact locked amounts — reduce underpay / overpay disputes at the counter and online.
• Platform fees off-chain — service fees settle from your fee account, not skimmed from the customer’s transfer.
• One merchant identity — wallets, Integration API keys, and fee mode reuse across Cashier and plugins.
• Surface fit over one-size UI — POS for brick-and-mortar; cart plugins for CMS stores; Hosted Pay / SDK when you own the page.

Who it’s for

NoxPos is built for teams that already sell goods or services and want stablecoin rails without rebuilding their stack — or without trusting a third party with settlement funds.

• Brick-and-mortar stores that need a counter POS, staff roles, and table / Store QR — start with Cashier.
• WordPress shops already on WooCommerce Blocks or classic checkout — WooCommerce Gateway.
• Shopify-native brands waiting for wallet checkout inside Admin — Shopify App (coming soon).
• Sellers without Woo/Shopify — invoices, landings, games, media, knowledge pay — Hosted Pay Page.
• Builders embedding checkout in SaaS, bots, or custom apps — Pay Button SDK.

If you are unsure, use “Choose the right product” below — then open the matching product page or usage docs for setup steps.

Settlement philosophy

NoxPos separates two money flows on purpose: customer settlement and platform service fees.

Customer settlement is always wallet-to-wallet on Solana, Base, or TRON (depending on what you enable). Your receiving addresses are configured under Profile → Plugin configuration.

Platform fees (Cashier tiers or the flat online plugin rate) bill from your prepaid or monthly fee account. That keeps the customer’s on-chain amount equal to what the merchant is owed for the goods.

• Cashier product: /products/cashier
• After login, configure wallets and fee mode under Profile → Plugin configuration / Fees.

Choose the right product

Pick by where checkout already lives — not by which crypto you prefer.

• In-store counter, staff, receipts, Store QR → Cashier.
• WordPress + WooCommerce cart → WooCommerce Gateway.
• Shopify Online Store / Admin → Shopify App (preview today; install when listed).
• Need a redirect pay URL only (no cart CMS) → Hosted Pay Page.
• Own HTML/SaaS/bot UI and want an embedded button or QR → Pay Button SDK.
• Hybrid is normal — e.g. Cashier in the café + Hosted Pay for online booking deposits.

NoxPos POS (in-store)

Browser POS for brick-and-mortar — catalog, keypad, Store QR, staff controls.

Cashier solves the counter problem: staff need a fast, permissioned way to lock an amount and show a QR (or push to a table terminal) while funds settle to the store wallet.

It is aimed at cafés, restaurants, retail, and service desks that already think in tickets, shifts, and printers — not at rebuilding an online cart.

• Audience: floor staff + store owners who need roles, shift sign-off, and ledgers.
• Scenarios: dine-in QR, counter scan, quick charge keypad, multi-device Store QR.
• Problems solved: custody risk, messy underpay disputes, shared-login chaos across staff.
• Design intent: feel like a familiar POS, settle like crypto wallets.
• How-to (usage): /docs/cashier
• Product page: /products/cashier

WooCommerce Gateway

Native crypto method inside WordPress / WooCommerce checkout.

For merchants whose storefront and ops already live in Woo. Shoppers pick NoxPos Crypto at checkout; payment goes to your configured wallets; order status updates after reconcile.

Best when you do not want a second cart — keep Blocks or classic shortcode checkout, add a stablecoin rail beside cards.

• Audience: indie and DTC Woo stores, digital goods, memberships, booking shops on WordPress.
• Scenarios: cross-border USDT/USDC buyers, crypto-native customers, card-FX fatigue.
• Problems solved: no Woo theme rewrite; no custody of order funds; fee transparency off-chain.
• Design intent: behave like a Woo payment gateway, settle like NoxPos everywhere else.
• Docs: /docs/woocommerce
• Product: /?module=plugins&group=store&plugin=woocommerce

Shopify App

Same non-custodial model, tuned for Shopify Admin and themes — coming soon.

Aimed at brands that refuse to leave Shopify for a custom cart. When the app ships, checkout stays Shopify-native while settlement follows the NoxPos wallet story.

Today you can preview scenarios and fee framing; install from Admin when the listing goes live. Woo and Pay Button SDK cover shipping now.

• Audience: DTC brands, Markets/cross-border shops, subscription and wholesale patterns on Shopify.
• Scenarios: stablecoin buyers beside cards; finance that needs NoxPos fee + Shopify third-party fee clarity.
• Problems solved: keep Online Store ops; avoid building a parallel checkout stack.
• Design intent: Shopify-first UX, NoxPos settlement underneath.
• Docs: /docs/shopify-app
• Product: /?module=plugins&group=store&plugin=shopify

Hosted Pay Page

Redirect checkout when you only need a pay URL — no Woo or Shopify required.

Hosted Pay is for platforms and creators whose product is not a classic cart: games, casinos, media, knowledge consults, invoices, and campaign landings.

You create a session, send the buyer to NoxPos-hosted checkout, then unlock goods or access when status flips paid. Entitlement always stays on your side.

• Audience: non-CMS sellers, agencies/ISVs, channel operators, knowledge and media platforms.
• Scenarios: VIP Telegram/Discord, livestream tickets, outdoor vlogs, legal/business consults, chapter unlocks.
• Problems solved: no cart CMS install; works from email, bio links, and in-app WebViews.
• Design intent: one redirect rail, many vertical playbooks under Solutions → Hosted Pay.
• Docs: /docs/hosted-pay
• Product: /?module=plugins&group=store&plugin=hosted

Pay Button SDK

Embed button / QR checkout in your own site, SaaS, or bot UI.

For builders who own the page. Drop the SDK where billing already happens — credits top-up, invoice portals, tip jars, mint gates — without sending users through WordPress or Shopify.

Prefer Hosted Pay when you only have a redirect URL; prefer the SDK when the pay UI must stay on your domain.

• Audience: SaaS founders, bot/CLI authors, hackathon and custom-storefront builders.
• Scenarios: API credits, invoices, tip jars, gated downloads, internal tools.
• Problems solved: embeddable checkout without a full CMS plugin; same fee and wallet model as other online products.
• Design intent: geek-friendly surface, merchant-grade settlement.
• Docs: /docs/pay-button-sdk
• Product: /?module=plugins&group=sdk

Where to go next

Use this page to pick a fit. Then open the matching how-to or product surface — we keep usage manuals separate so this guide stays about intent and audiences.

• Cashier how-to: /docs/cashier
• WooCommerce docs: /docs/woocommerce
• Shopify docs: /docs/shopify-app
• Hosted Pay docs: /docs/hosted-pay
• Pay Button SDK docs: /docs/pay-button-sdk
• Solutions industry pages: /?module=plugins

How to submit a ticket

Website tickets are for account and product issues. Ideas and cooperation inquiries use a separate form on the same Contact page.

Open About → Contact us (or /contact). Choose Ticket, sign in with your merchant account, then pick a category: Malfunction, Platform fees, Cashier, WooCommerce, Hosted Pay, Pay Button SDK, or Shopify.

Write a short subject, describe what failed and what you already tried, then submit. Support replies appear on Contact us → Ticket → View replies; keep the same ticket for follow-ups instead of opening duplicates.

Use Ideas & cooperation on the Contact page for platform suggestions or business collaboration — those do not need a merchant login. Do not put account outages or failed payments there.

Cashier also has an in-app help / ticket path for counter issues. Website and Cashier tickets are separate queues — say which surface you used when you write.

1. 1

   Pick the right surface

   Broken checkout, wallets, fees, or plugins → Ticket. Product ideas or cooperation → Ideas & cooperation. How-to questions → product docs first (links below).

2. 2

   Sign in and choose a category

   Ticket requires your merchant login. Category routes the request (Cashier vs a specific plugin vs a general malfunction).

3. 3

   Attach identifiers

   Order / session ID, on-chain TxID, shop login ID, network, and token matter more than long screenshots alone. See the checklist in the next section.

Deep Cashier counter steps live in the Cashier Usage Guide → Troubleshooting. Plugin install steps live under each product’s docs.

What to include by category

A few precise fields usually unblock support faster than a long narrative. Always include your shop name or login ID.

Start every ticket with: shop name or login ID, approximate time (with timezone), and whether the issue is Cashier or a named plugin. Then add the fields for your category.

• Malfunction — what you clicked, exact error text, browser or device, and whether it still fails after refresh / re-login. Screenshots of the error help.
• Cashier — order ID, terminal or staff account if relevant, network + token on the pay screen, TxID if the customer paid, and whether Cashier showed pending / paid / failed.
• Platform fees — fee account mode, invoice or top-up reference, billed amount shown on screen, treasury TxID, and whether the fee account or VIP status looks wrong after confirm.
• WooCommerce — Woo order number, WordPress / plugin version if known, gateway status on the order, session or payment reference from NoxPos, network + TxID if the buyer paid.
• Hosted Pay — Hosted Pay session / pay-link ID, expected amount, redirect URL you used, webhook or status you expected, network + TxID if paid.
• Pay Button SDK — Integration API key environment (not the secret itself), session id from create-session, page URL where the button embeds, network + TxID if paid.
• Shopify — Shopify order name/number, app install shop domain, payment status in Shopify vs NoxPos, session reference, network + TxID if paid.
• Wrong-network or stuck pending — always include the intended network from the pay screen, the network the wallet actually used, full TxID, and amount sent.

Never paste private keys, seed phrases, or full Integration API secrets into a ticket. Login ID, order IDs, and TxIDs are enough.

Common problems & fixes

Try these before opening a ticket. If it still fails, open Contact → Ticket with the checklist fields above.

1. 1

   Customer paid but order stays pending

   Confirm they paid the exact locked amount on the network shown on the pay screen. Wait about a minute for confirmation, then refresh status. If the TxID is on a different chain or amount, automatic match will not complete — open a ticket with order ID + TxID.

2. 2

   Wrong network or wrong token

   Stablecoin on the wrong chain (or USDT vs USDC mix-up) usually cannot be auto-reconciled and may be unrecoverable. Always point customers to the network and token on the pay UI. Ticket with TxID for guidance only — do not promise a refund path that the chain cannot reverse.

3. 3

   Fee account paused new NoxPos POS orders

   Platform fees settle from the fee account, not from the customer’s transfer. Top up prepay or settle the unpaid monthly bill under Profile → Platform fee account. Wallets stay bound while checkout is paused.

4. 4

   VIP or fee top-up paid on-chain but status unchanged

   Treasury payments also use an exact amount suffix for matching. Pay the QR amount exactly, wait for confirm, then refresh Profile. Ticket with the treasury TxID and the amount shown on screen if status stays wrong.

5. 5

   Plugin order paid but store still unpaid

   Check webhook / callback delivery, that the Integration API key matches the shop, and that the session id on your side matches NoxPos. Include Woo/Shopify/Hosted session and TxID in the ticket.

6. 6

   Cannot sign in on the website

   Use the same merchant login ID or email as Cashier. Confirm the email if registration required verification. Password reset / support ticket needs the login ID you registered with.

7. 7

   Wallet bind or receive address rejected

   Use an address for the network you selected (Solana, Base, or TRON). Double-check copy-paste length and that you are binding under the owner account, not a cashier staff role.

• Cashier Usage Guide troubleshooting: /docs/cashier
• Contact / Ticket: /contact
• User guide (this page) checklist: scroll to “What to include by category” above