Payrano Solutions: non-custodial stablecoin acceptance on TRON

Payrano Solutions lets a merchant accept USDT on TRON (TRC20) without ever handing custody of funds to a third party. The system produces a payment request, hosts a checkout, and reconciles the resulting on-chain transfer against a unique reference. The transfer itself is a direct wallet-to-wallet payment from customer to merchant. Payrano earns revenue from a flat monthly subscription rather than a cut of each transaction, so the amount the customer sends is exactly the amount the merchant keeps.

Card rails price acceptance at 1.5–3.5% plus fixed fees, hold funds for days, and expose merchants to chargebacks. Most crypto gateways solve the speed problem but reintroduce the trust problem: they take custody, batch payouts, hold a percentage, and become a single point of failure for merchant funds. Merchants who simply want to be paid in a dollar-stable token are asked to accept counterparty risk they never wanted.

• Never hold funds. If the operator cannot move merchant money, the operator cannot lose it.
• One asset, one network. USDT on TRON keeps fees low, confirmation times in seconds, and the state machine small enough to reason about.
• Predictable pricing. A subscription is easier to budget than basis points, and it removes the incentive to skim payments.
• Transparent surface. Public pages read through server functions that expose only what a page requires.

The gateway is a full-stack React application with server functions for privileged logic and a Postgres database with row-level security. Four layers:

• Merchant plane — authenticated dashboard for payments, transactions, keys, integrations, billing, verification and settings.
• Public plane — hosted checkout, subscription mandate pages and reputation profiles, served without exposing database access to the browser.
• Integration plane — versioned REST endpoints under /api/public/v1 for payment creation, lookup and key verification, plus a WooCommerce plugin and scheduled hooks for reminders and recurring charges.
• Administration plane — KYB review, lead pipeline, revenue and platform settings, gated by a server-side role check.

Payrano also acts as the identity provider for the separate Payrano Wallet application, so a single account works across the merchant gateway and the consumer wallet.

Generating a fresh wallet per payment creates key-management and sweeping problems and costs gas. Instead, each merchant nominates their own TRC20 deposit address, and each payment carries a unique reference plus an exact expected amount and expiry window. An incoming transfer is matched on address, amount and time window, then bound to its reference. Exact-amount matching keeps collisions negligible in practice; a mismatch is surfaced as an underpayment or overpayment for the merchant to resolve rather than being silently adjusted.

Revenue is a flat monthly subscription banded by processed volume: Starter up to 25,000 USDT per month, Growth up to 50,000, Scale up to 100,000, and custom pricing above that. Transaction fees are zero. Network (TRON) fees are paid by whoever signs the transfer, normally the customer's wallet.

Future revenue lines are explicitly additive and opt-in rather than deductions from merchant settlement: sponsored-energy gasless checkout, swap spread when a payer chooses a non-USDT asset, and premium tooling. Any change to how money is charged is published in this section before it takes effect.

All tables enforce row-level security with explicit grants; anonymous database roles hold no privileges. Public data paths are server-mediated. API key secrets are shown once, stored hashed, and protected at column level. Administrative privileges live in a dedicated roles table evaluated by a security-definer function server-side — never in client storage. KYB documents are held in a private bucket restricted to the owning merchant and administrators. Settlement addresses are additionally PIN-gated in the interface to reduce shoulder-surfing and casual disclosure.

Payrano is a technology provider, not a money transmitter or custodian: it never possesses, controls or directs merchant funds. Access is nonetheless gated by manual know-your-business review — trading licence and company documentation are collected and approved before an account can create live payments — and accounts can be suspended for abuse.

• Wrong or compromised deposit address. Funds are irrecoverable. Mitigated by explicit address linking with PIN confirmation and a hidden vault, but the merchant remains responsible for the address.
• Stablecoin issuer risk. USDT depends on its issuer's reserves and freeze powers. Payrano cannot insulate merchants from that.
• Network dependency. TRON congestion or a chain indexing delay can slow confirmation; payments stay in a confirming state rather than being lost.
• No chargebacks, no reversals. Good for merchants, unforgiving for mistakes: refunds are a manual outbound transfer by the merchant.
• Alpha features. Labs features are labelled and opt-in; they may change or be withdrawn.

• Graduate gasless checkout and on-chain subscriptions from Labs to general release.
• Single sign-on and deep-link payment flow with the Payrano Wallet application.
• Broader commerce plugins beyond WooCommerce, and webhook signing improvements.
• Deeper reporting: settlement statements and accounting exports per period.

This document describes software, not an investment. There is no token, no token sale, no yield product and no promise of return. Payrano does not custody funds and cannot recover a transfer sent to a wrong address. Figures for volume bands reflect the tiers published on the pricing page; the operational detail behind every claim here is documented in the documentation.