Register and choose
The customer creates an account, sees the plans published by the operator, and selects the duration and supported payment method.
The customer path
From account creation to a connected device
The portal keeps the steps in one account, while the backend remains authoritative for prices, entitlements, device limits, and configuration output.
Pay and activate
Flirexa creates a provider invoice. Access is granted only after the provider reports a matching settled amount and currency, not merely because the browser returned.
Connect a device
A device slot receives a server and protocol configuration. The customer downloads a file, scans a QR code, or uses an official application where available.
Built for recurring operations
Fewer manual messages between customer and operator
- publish plans with exact cent pricing and device allowances
- offer configured card, local, or cryptocurrency providers
- show subscription status, expiration, traffic, and device slots
- regenerate or remove a device without exposing another customer's record
- deliver WireGuard and AmneziaWG configuration files and QR codes
- let customers choose an available DNS protection mode per device
- keep support tickets attached to the authenticated customer account
AuthenticationShort-lived HttpOnly browser cookies, rotating hash-only refresh families, and CSRF protection
PaymentsThe backend recalculates the authoritative price and waits for verified settlement
DevicesEvery slot is independent, with its own assignment and configuration lifecycle
BrandEnterprise applies the operator's product identity, colors, domain, email identity, and legal links
Payment choices
Use the providers your account and region support
Flirexa integrates the checkout and settlement workflow. It does not override a payment provider's regional, currency, business-category, or account eligibility rules.
| Capability | How it works | Plan boundary |
|---|---|---|
| NOWPayments | Cryptocurrency checkout with provider-confirmed settlement | FREE and above |
| Commercial provider suite | Stripe, PayPal, PayLio, CryptoPay, Mollie, Razorpay, Payme, and supported provider-specific methods | Business and Enterprise |
| Promo codes | Discount or time-extension rules validated by the backend | Starter and above |
| Prepaid customer credit | Exact-cent top-ups, append-only ledger, atomic subscription purchase, and audited operator adjustment | Business and Enterprise |
| Automatic end-customer renewal | Temporarily unavailable while rebuilt around one new verified settlement per extension | Manual renewal remains supported |
Account credit
A balance is accounting, not a number painted in the interface
Credit after settlement
A top-up changes the balance only after the configured provider confirms payment. Repeated webhooks cannot credit the same invoice twice.
Atomic purchases
The server locks the customer balance, recalculates the plan price, debits exact integer cents, and activates the subscription in one transaction. Insufficient credit rolls the operation back.
Immutable history
Every top-up, subscription purchase, and operator adjustment writes a ledger entry with the resulting balance.
Controlled adjustments
An administrator must enter a reason. Debits that would make the balance negative are rejected and the admin action is audited.
Questions
What customers and operators should expect
Can the portal be linked from my existing website?
Yes. Your public website can send customers to the portal on its configured domain. Enterprise provides the built-in domain and white-label controls for a branded handoff.
Can one account use several devices?
The operator decides the device allowance in each plan. Every slot receives its own client record and configuration, so removing one device does not silently reuse another device's identity.
What happens when a payment provider is unavailable?
The portal reports a readable provider error and does not activate the subscription. The operator can offer another configured provider or investigate the provider account and connectivity.
Does the customer portal expose Flirexa upgrade prompts?
No. Operator licence gates use neutral customer-facing wording in the portal. A customer is not redirected to the vendor's licence checkout.