pricingOps must publish launch prices before advertising
Pricing
Users should see the route cost before connecting. Suppliers should see how payout is calculated before selling capacity.
What users pay
A Torna session is funded from wallet balance. The product should show the selected route, expected price basis, and whether the route is automatic or operator-provided before the user starts.
- No hidden setup fee should be added at connect time.
- Auto-route prices come from the selected public pool and ready supplier inventory.
- Advanced routes can cost more if a brand or operator picked premium capacity.
Rial top-up
Rial payments are converted to an internal USDT-denominated balance. The exchange quote must lock when the payment instruction is created, and the user should see the reference code, expiry time, and expected credit.
Supplier payout
Supplier earnings are settlement-derived. A supplier listing can be fixed-price or usage-metered, but payout should only happen for verified, reachable, active capacity that actually serves traffic.
What is not final yet
- Launch price tables are not a product promise until ops signs them off.
- Cardholder fees, fraud reserve, and withdrawal costs still need live treasury drills.
- Advertising should wait until top-up, settlement, refund, and support flows have been tested with real operators.