QU is Qubic's own currency, the way dollars are the US's - prices you set are converted to QU automatically at the current rate.
Revenue trend
Key metrics
Invoice status
Top customers
Revenue by period
Revenue figures are accounting input data, not a tax filing product -
they report what happened (cash-basis: an invoice counts the period it
was paid in, a refund reduces the period it was refunded
in), for you or your accountant to use as a source. Channel (payment
channel) revenue only reflects voucher redemptions from tonight onward -
see the code comment in channelStore.js for why older channel spend has
no historical breakdown to draw from.
These cover your full history, not just the most recent invoices shown
on the Invoices tab. Conversion rate only counts payment links that
reached a final outcome - paid or expired; one still sitting open
hasn't failed yet, so it isn't held against you. "Repeat customer"
means the same wallet address paid more than once - a genuine
returning customer using a different wallet each time won't be
detected as one, there's no other identity to key on here.
Quick charge
Enter an amount, hand the screen to your customer to scan, and it clears automatically the moment payment lands - built for in-person sales at a counter or table.
Products
Build a catalog once, then charge from it at the register instead of typing a price every time - useful if QPAY is your only point of sale.
Bulk import
Upload a CSV with columns name, price (or priceQu), sku, description - a header row is required, column order doesn't matter.
All products
Reports
Pick a date range (or leave both blank for all time), then export or print - built for handing to yourself or an accountant, not for tracking growth like the Analytics tab.
Same cash-basis accounting rules as everywhere else in this dashboard
(an invoice counts in the period it was paid, a refund reduces the
period it was refunded) - this is accounting input data, not a tax
filing product. Print produces a clean, unstyled copy suitable for
handing to someone else.
"Est. processing fee" is informational only and is never deducted from
anything - QPAY is self-hosted and non-custodial, so payments go
straight to your own wallet with no platform operator in between to
collect a cut. It's a reference figure (1% of the sale, or 1000 QU,
whichever is greater, per transaction) so you can see roughly what a
typical card or crypto payment processor would have charged instead.
Not offered here: a Balance Sheet or Cash Flow Statement. Both need
data this system doesn't have - a balance sheet needs your other
assets/liabilities/equity (bank balance, loans, owner's equity), and
a cash flow statement's operating section would just duplicate the
P&L above (every sale here already is a cash receipt - there's no
accrual/AR timing gap to reconcile). Use this data as one input to
real accounting software for those.
Invoices
A payment link for one specific sale, at a price you set. Share it once; once it's paid, it's done - for a link that keeps working for repeat sales, use a tip jar instead.
Refunds are signed by your connected wallet, right here - no separate
app, no copy-pasting a transaction id. Reconnect at any time if your
wallet session ends; a wallet prompt only appears when it's actually
needed to sign something.
Tip jars
A reusable link that never runs out - good for tips, donations, or "pay what you want." Selling something at a fixed price instead? Use an invoice - simpler, and it tracks per-order.
A tip jar is a stable, reusable link - unlike an invoice, it never runs
out. Every visit mints a fresh, ordinary one-time payment behind the
scenes, so each tip goes through the exact same pipeline as any other
invoice (including a webhook, if one's set). Pause a jar to stop new
tips without deleting its history.
Payment channels
A channel is a prepaid balance a caller deposits once, then draws down
per request with an instant, locally-signed voucher - built for
high-frequency/agent traffic, not one-off purchases. Channels are
opened and spent by your API's callers directly (see Integrations for
the client snippet); there's nothing to create here.
Integrations & docs
Selling something specific? You don't need any of this - create a
payment link from the Invoices
or Tip jars tab and share
the link, the same as a Stripe payment link. Everything below is for
connecting Qubic x402 to your own website's code, an existing store
platform, or an automated system - it assumes you (or someone you've
hired) is comfortable writing code.
Preferences
Appearance
Deployment settings
These reflect this server's actual configuration (its .env) - read-only
here by design; change them by editing .env and restarting the process.