Frequently asked questions

Reway lets you pay with a supported asset while the recipient receives a supported asset and network they prefer. It coordinates the route so you do not have to arrange the required swaps and cross-chain steps yourself. Read how Reway works.

Reway is designed to work with user-controlled wallets. Use the compatible connection options offered in the app. See wallets and identity.

The intended architecture is non-custodial. Users authorize payment actions through their wallets or supported accounts, while Reway coordinates routing and settlement. Read security and control for what this means.

Relay supplies the underlying cross-chain routing and execution in Reway's current architecture. Reway supplies the payment experience, identity, payment information, and activity tracking above it.

No, provided a supported route exists between the two sides. The sender chooses an available funding asset and the recipient has a supported receiving preference.

The route can be simpler. Token conversion and cross-chain movement are only needed when the payment requires them.

That depends on the flow. Planned direct sends to supported external wallets may not require the recipient to actively use the interface. Identity, requests, and other Reway account features can require a Reway-aware experience.

Check the quote for the specific payment. Costs depend on the assets, networks, and route. These docs do not publish a fixed fee or a guaranteed settlement time. Read fees and gas.

No universal gasless guarantee is made. Gas abstraction is a planned capability that depends on the wallet, chain, and transaction. Only rely on it where the app explicitly shows that it applies.

Only supported assets with an available route can fund the payment. Reway starts with curated coverage and can expand it over time. See assets and networks.

A link is shareable. A directed payment request is intended for a specific payer and can carry its own request status. Requests are part of the planned payment extensions.

Not necessarily. A cross-chain route can continue after its source transaction confirms. Check the final payment status and destination details in activity.

First check whether the original transaction was submitted and what its current status is. A second attempt could create a duplicate payment. Follow the pending payment checks.

API and SDK access is planned. The developer page explains the intended scope; production endpoint references and access instructions are not published in these docs yet.

Non-custodial payments can still be visible on public blockchains. Private Payments are under research, and the privacy architecture is not final. See security and control.

Crypto-to-Fiat Settlement is a future direction that would depend on off-ramp partners and coverage. It is not part of the core launch baseline.

The product roadmap groups the launch baseline, planned workflows, and research directions. Inclusion there does not establish a launch date or current availability.