QTC Pay Desk
Accept Quantus like a merchant: build invoices with exact planck amounts, hand the customer a QR payment request, run a point-of-sale screen, keep a register, and embed a tip button on your site. This desk never holds keys or funds — it only prepares and records payment requests. You confirm payment in your own wallet or an explorer, then mark it paid here.
Read this before you take anyone's QTC
- No custody, no settlement guarantee. Pay Desk creates payment requests and records what you report. A transaction only exists when you see it in your wallet or the chain explorer.
- Marking "paid" is your attestation, not chain truth. Always verify the tx yourself — search the amount and address in the Block Explorer — before you release goods or mark an invoice paid.
- There is no listed spot price yet. QTC's first announced venue is NEAR Intents; no listing date was confirmed as of 2026-10-01. The rate card below is a manual entry — set it from whatever price you and the customer agree on, and stamp the timestamp.
- Amounts are exact to the planck. QTC has 12 decimals (1 QTC = 1012 plancks, verified from on-chain block rewards). QR codes encode your address; the amount travels alongside as copyable text — there is no QTC payment-URI standard yet, so the QR never invents one.
Rate card
Set the QTC/USD rate you are quoting. It applies to every invoice until you change it — each invoice records the rate it was quoted at, so old invoices never silently re-price.
Manual entry only — no exchange, no oracle, no API. QTC has no listed spot market yet.
Invoice builder
Itemize the sale, pick your receiving address, and generate a payment request. Addresses are checksum-verified (SS58, prefix 189) before an invoice can be created.
Enter your wallet address — it is validated locally, never sent anywhere.
Line items (priced in USD)
| Description | Qty | Unit price (USD) | Line total |
|---|
Payment request
—
QR encodes the receiving address only. The amount below is copyable text — verify both with the customer.
———Invoice register
Your local record of every request. Statuses are yours to maintain — Pay Desk cannot see the chain, so mark paid only after you verify the payment in your wallet or the explorer.
| ID | Reference | QTC | USD | Rate | Created | Status |
|---|
No invoices yet — build one above.
Confirmation guidance
Quantus is proof-of-work: finality is probabilistic, not instant. Blocks land when they land (the Sept 30 chain snapshot averaged ~14 s between blocks; week-one mainnet was faster — times move with difficulty). Suggested confirmation counts by invoice value are merchant heuristics, not protocol guarantees.
Coffee-money. Fine for walk-up counter sales.
Typical retail. ~1–2 minutes at current pace.
High-ticket. Wait a few minutes before releasing goods.
Treasury-scale. Consider escrow or staged delivery.
- Watch the address, not just the amount. Confirm the receiving address in the explorer/wallet matches your invoice's address exactly — address poisoning is cheap and quiet. The Contact Vault desk explains the attack.
- Small amounts stay practical. On-chain fees on Quantus are low by design; still, don't accept dust below the 0.001 QTC existential deposit — an invoice total that can't keep an account alive is an accounting headache.
- Expiry is yours to enforce. If the rate moves before payment arrives, the expired request is void — generate a fresh invoice at the fresh rate.
Tip-button generator
An embeddable donate/tip button for your site — the same pattern this builder's own footers use. Fill your address, pick a style, copy the snippet. Everything runs client-side; no tracking, no scripts from us.
Validated locally with the same SS58 check as invoices.
Preview
Embed snippet
Enter a valid address — the snippet appears here.Merchant playbook
The operational habits that separate a smooth QTC checkout from a support ticket.
- One invoice, one receiving address. Reusing a single address across customers leaks your whole revenue history and invites poisoning. Generate a fresh address per invoice in your wallet (the Web Wallet derives addresses from your seed; Address Toolkit inspects them).
- Price in fiat, settle in QTC. Quote USD, convert at your stamped rate, lock the QTC amount on the invoice. Crypto-denominated pricing transfers volatility to the customer.
- Decide refunds before you need them. Publish your policy: refunds in QTC at the original invoice rate (not current) is the standard honest answer. Get a return address up front for large orders.
- Keep your keys off the counter. The device that builds invoices should be view-capable only. Signing keys live in the Web Wallet or Airgap Desk — never in the register, never in the browser tab the customer sees.
- Taxes are your accountant's job, not this page's. The Ledger Desk keeps a miner/holder tax ledger; export this register's CSV into it for your books. Nothing here is tax advice.
- Have an outage story. If your wallet or the explorer is unreachable, fall back to: invoice paid → customer shows you the tx in their wallet → you confirm the sending address and amount → goods on trust, settled later. Write it down before Friday night.
Sources & honest limits
- Quantus-Network read 2026-09-29
Upstream org. Chain is Substrate/Polkadot-SDK-based; SS58 prefix 189 (node/src/chain_spec.rs); account crypto Poseidon2 over Goldilocks, verified byte-for-byte in the Web Wallet. - Chain snapshot
data/live.json(repo, fetched 2026-10-01 from sqm.quantus.com/v1/graphql)
Block rewards 0.30–0.32 QTC → 12 decimals confirmed (1 QTC = 1012 plancks); ~14 s average block gap in the snapshot window. Snapshot data decays — re-check the Network Dashboard before quoting block times to customers. - Quantus weekly update — mainnet week 1 2026-09-16
NEAR Intents named as first announced exchange venue; no listing date confirmed as of 2026-10-01. Hence: no price feed, manual rate card.
Limits: Pay Desk cannot watch the chain, cannot convert to fiat, cannot hold funds, carries no price oracle, and cannot guarantee a payment. QR codes encode addresses only — there is no QTC payment-URI standard yet. Everything persists in your browser's localStorage; clearing site data wipes the register (export CSV first).