Accept Payments from the Dashboard
Introduction
This guide is for merchants who collect payments through the Fluxis Dashboard—no API or code required. You will learn how to create payment requests from your POS terminal, use a static QR at your cashier, and track payments as they complete.
First time here? Complete Sign Up and open your default POS from Your Dashboard & Default POS.
Two ways to receive payments
| Method | Best for | How it works |
|---|---|---|
| One-off payment request | A specific sale with a known amount | Enter amount in the POS terminal → customer scans QR or opens payment link |
| Static QR at the cashier | Open-amount payments at a fixed location | Print or display the POS static QR → customer scans and enters the amount in their wallet |
Both methods use your default Point of Sale. Learn more about the underlying concept in Payment Request.
Create a payment request from the POS terminal
Use this flow when you know the exact amount to charge (for example, a single checkout).
- Sign in to the dashboard and go to Points of Sale.
- Review your POS settings — here you can configure which UAIs (asset/network combinations) the terminal will accept.
- Select your reference currency by clicking on it, then enter a test amount (for example,
1.00). - Click Charge to generate the payment request.
- Show the QR code on screen to the customer, or click Send a payment link to share the payment link.
- Check the generated payment request in the table on the left, along with its current status.
The customer pays with their crypto wallet. Fluxis detects the on-chain payment and updates the request status automatically.
Payment requests expire after about 8 minutes if no payment is received. Create a new request if the customer needs more time.
What the customer sees
The QR or link encodes a NASPIP token — a signed payment instruction that tells the wallet exactly where and how much to pay. You do not need to understand the token format to use the dashboard; Fluxis handles encoding and validation.
Print your static QR for the cashier
For a physical store, many merchants display a static QR at the register so customers can pay without staff entering each amount in the terminal.
- Open your POS terminal (Points of Sale → Enter →).
- Locate the static QR option for this POS (representing the terminal itself, not a fixed amount).
- Print or display the QR where customers can scan it (counter, receipt holder, signage).
- When a customer scans, their wallet prompts them to enter the payment amount.
The static QR is tied to your Point of Sale, not to a single transaction. Each scan can start a new payment with the amount the customer chooses. Track completed payments under Payments in the dashboard sidebar.
Track payments and statuses
All activity appears under Payments in the dashboard sidebar. Filter by account, date range, or search to find specific transactions.
Payment requests move through these states:
| State | Meaning | What to do in the dashboard |
|---|---|---|
pending | Checkout created; payer has not chosen asset yet | Wait or show hosted checkout if applicable |
created | Address assigned; awaiting payment (~8 min expiry) | Keep QR/link visible; wait for customer to pay |
confirmed | On-chain payment confirmed; settlement processing | Wait for completed before treating as fully settled |
processing | Payment detected; awaiting blockchain confirmations | Inform customer payment is in progress |
completed | Payment received and confirmed | Order fulfilled; payment appears in volume stats |
expired | No payment in time | Create a new payment request for the customer |
underpaid | Customer sent less than expected | Contact [email protected] |
overpaid | Customer sent more than expected | Contact [email protected] |
failed | Unexpected error during processing | Contact support; may need a new request |
Edge cases
Unusual amounts (underpaid, overpaid) and processing failures may need support coordination. See Payment Flows — Edge Cases for background.
Payment flow (dashboard perspective)
Code
Need to integrate via API instead?
If you want to embed Fluxis in your website, mobile app, or backend—and receive automated notifications when payments complete—follow the developer path:
That guide covers API keys, authentication, creating payment requests via POST /v1/pos/:posID/payment-request, and monitoring via webhooks or polling.
Need help?
Contact us at [email protected].