How Payrano Solutions works

A merchant creates a payment for a fixed USDT amount. Payrano issues a unique payment reference and a hosted checkout page containing the amount, the merchant's TRC20 deposit address, a QR code and an expiry countdown. The customer sends USDT from any wallet or exchange. Once the TRON network confirms the transfer, the payment is matched to its reference and marked completed in the merchant dashboard.

Everything is denominated in USDT on TRON only. There is no fiat leg, no card processing, no trading, and no conversion — the amount your customer sends is the amount you keep.

Access is granted after a manual review. The path is:

1. Request access — submit business details on the waitlist form. This creates a lead record for our team.
2. Create an account — sign up with email and password. The account exists but cannot create live payments yet.
3. Complete KYB — under Verification upload your trading licence and company documents into a private, access-controlled storage bucket.
4. Manual approval — an administrator reviews the application and approves or rejects it. On approval, gateway features unlock and you receive a confirmation email.

Until KYB is approved, payment creation, API keys and integrations stay gated behind a verification notice.

Payrano ships with no pre-configured wallet. You add your own TRC20 (TRON) address in Settings, paste it, then confirm it with the Link action, which is protected by a 6-digit PIN you set locally. Saved addresses live in a collapsed vault that only expands after the PIN is entered, so a long list of settlement addresses is never on screen by default.

Payments cannot be created until at least one deposit address is linked — this prevents issuing a checkout that has nowhere to settle.

Every payment moves through a single predictable status flow:

• waiting — created, checkout live, nothing received yet.
• confirming — a transfer was detected and is awaiting TRON confirmations.
• completed — confirmed and reconciled against the reference.
• expired — the countdown elapsed with no matching transfer. Create a new payment rather than reusing an expired reference.

The reference is the reconciliation key: a single merchant deposit address is used with a unique reference per payment, which removes the need for per-payment wallet infrastructure.

Create Payment takes an amount and a description and produces a hosted checkout at /pay/<id>. The page shows the USDT amount, the deposit address with a copy action, a scannable QR code, the reference and a countdown. It is mobile-first and can be shared as a link, embedded in an invoice, or displayed on a till.

The merchant dashboard shows KPI cards with sparklines, a volume chart, a conversion funnel from created to completed, and live settlement toasts as payments confirm. Payments lists requests with status filters; Transactions is the read-only on-chain ledger. Both export to CSV for accounting.

Generate keys under API Keys. The secret is shown once at creation and is never readable again — store it in your own secret manager. Send it as the API key header on requests.

• POST /api/public/v1/payments — create a payment; returns the id, reference, deposit address and checkout URL.
• GET /api/public/v1/payments — list or look up payments for the key's merchant.
• GET|POST /api/public/v1/keys/verify — credential check used by integrations and POS terminals to validate a key pair before going live.

Requests are validated and scoped to the merchant that owns the key. Revoking a key takes effect immediately.

Integrations provides a downloadable WordPress/WooCommerce plugin. Install the ZIP, paste your API key pair, and USDT (TRC20) appears as a checkout method: orders create a Payrano payment, the customer pays on the hosted page, and the order is marked paid once the transfer is confirmed.

Payrano charges a flat monthly subscription based on processed volume, and takes 0% of each transaction — no fee is split out of your customer's payment.

• Starter — up to 25,000 USDT of monthly volume.
• Growth — up to 50,000 USDT.
• Scale — up to 100,000 USDT.
• Custom — above 100,000 USDT, priced per account.

Billing & Fees tracks month-to-date volume against your tier ceiling and warns you before you exceed it. See the pricing page for current amounts.

Labs holds features that are functional but still stabilising. They are opt-in per merchant and clearly labelled Alpha or Beta in the dashboard.

• Gasless checkout — sponsor TRX energy so a payer with no TRX can still complete a TRC20 transfer. Checkout shows a gasless badge when sponsorship applies.
• On-chain subscriptions — publish a plan, let a customer sign a spending mandate at /subscriptions/<planId>, and a daily scheduler raises the recurring charge automatically.
• Pay with anything — the payer picks another asset at checkout and it is auto-swapped so you still receive USDT.
• Payment-reputation receipts — a payer can claim a signed receipt for a completed payment, building a public payment history at /reputation/<address>. Receipt data is only served through server-side code, never read directly from the database by the browser.

Transactional email is sent from the verified domain notify.payranosolutions.com as Payrano Solutions. The pack covers account emails (welcome, sign-in, password reset, email change), KYB status and reminders for unfinished verification, payment confirmations, subscription renewals and volume warnings. Reminder emails run on a daily schedule.

Every table is protected by row-level security: a merchant can only read its own payments, transactions, keys and applications. Anonymous database access is revoked — public surfaces such as checkout, receipts and reputation go through server functions that return only what the page needs.

API key secrets are write-once and column-protected. Administrative roles live in a separate roles table checked server-side, never in browser storage. KYB documents sit in a private bucket readable only by the owning merchant and administrators. Transport is HTTPS-only with automatic certificates.

• USDT on TRON (TRC20) only — no other chains or assets for settlement.
• No fiat, cards, IBAN payouts or exchange/trading features.
• No custody. Payrano cannot hold, freeze, refund or move merchant funds — refunds are performed by the merchant from their own wallet.
• Underpayments and overpayments are reported, not auto-corrected.
• Expired references are not reusable.

• v1.4 — Documentation and white paper published.
• v1.3 — Alpha & Beta Labs: gasless checkout, on-chain subscriptions, pay-with-anything, reputation receipts.
• v1.2 — Full transactional email pack on notify.payranosolutions.com; key-verification endpoint for POS integrations.
• v1.1 — Subscription pricing replaces per-transaction fee splitting; merchant-owned settlement wallets with PIN-gated address vault; light, dark and system themes.
• v1.0 — Gateway MVP: hosted checkout, payment links, dashboard, API keys, WooCommerce plugin, KYB onboarding and admin console.

This changelog and the white paper are updated alongside the application, so the documentation always describes the version that is live.