Product roadmap
The launch baseline, planned extensions, and longer-term research in one place.
Product direction. This page describes the baseline, plans, and research.
Reway's product direction starts with a focused payment engine and adds workflows around it. This page separates the launch baseline, planned extensions, and research. It is not a release calendar or a guarantee of availability.
The launch baseline
The V1 launch baseline focuses on four areas:
| Area | Purpose |
|---|---|
| Universal Cross-Chain Payments | Let a sender fund a payment with a supported asset while the recipient receives their preferred supported output. |
| Payment Links | Put receiving details into a shareable payment flow. |
| Reway Identity | Make payment recipients easier to recognize. |
| Dashboard and Activity | Track sent, received, pending, and completed payments. |
Initial coverage is intended to focus on a curated set of networks and liquid assets. Check the app for the features and routes currently enabled.
Everyday payment improvements
Planned extensions include Reway Send, Payment Requests, Payment Link Customization, Smart Invoices, and Saved Payment Templates. Their purpose is to make common payment tasks easier to start and repeat.
Gasless Payments are also a planned direction, subject to support from the chain, wallet, and transaction type. Broader ERC-20 and SPL support and additional networks are coverage improvements that depend on route quality.
See Send and requests, invoices, and fees and gas.
Business and developer tools
Reway Checkout, White-label Checkout, the Developer API / SDK, Batch Pay / Payroll, and Split Payments are planned ways for businesses and applications to use the payment engine.
These features need release-specific integration and transaction-handling documentation before teams build production processes around them. Read the business overview and developer overview for the intended scope.
Creator and community tools
Reway Page, Reway Unlock, Paid Community Access, a Telegram Bot, Social Payments, and Reway Avatars are proposed ways to connect payments with identity, content, and communities.
They are grouped in creator and community tools, where you can see what each is intended to do.
Research and longer-term directions
Private Payments
Privacy is under research. The current direction is to retain Relay for routing and evaluate specialized privacy infrastructure for supported flows. The guide discusses Hinkal as one possible provider, not a confirmed production integration.
Address privacy, shielded balances, and private transfers have different properties. The architecture and its chain and token coverage still need technical validation.
Universal Swap
A future swap interface could expose the conversion and cross-chain routing used underneath payments. It would let a user request a supported asset on another network directly. This remains secondary to the payment experience.
Crypto-to-Fiat Settlement
Future fiat settlement could route a crypto payment through an off-ramp provider to a recipient's bank or payout rail. Availability would depend on partner support, country coverage, and applicable requirements. It is outside the core launch baseline.
Reway Everywhere
A proposed browser extension could recognize supported payment contexts, links, or wallet addresses and open a Reway payment flow. It depends on the underlying payment APIs and identity system becoming stable.
Spending at normal stores
The longer-term idea is to use external payment or card infrastructure so a user can spend crypto at merchants that have not integrated Reway. Provider relationships and payment-rail coverage would be necessary; no released card product is specified here.
AI Agent Payments
Future software payment flows could let an agent pay for services using supported assets, with proposed controls such as spending limits, approved services, approval thresholds, and payment records. Standards such as x402 are an area to explore, not a published Reway implementation.
How to read future updates
Look for released behavior, supported routes, and operating limits before relying on a new capability. This roadmap does not assign dates, pricing, or production guarantees to the planned features.