Send and requests
Direct transfers and requests for a specific payer, built around receiving preferences.
Planned capability. Availability and final details will depend on the release.
Reway Send and Payment Requests extend the same payment engine into direct interactions. They are part of the product's planned payment workflows, beyond the initial payment-link baseline.
Reway Send
Send is designed for paying another Reway user or a supported external wallet. The sender chooses the recipient, amount, and asset to spend. The recipient's supported output can use a different token or network.
For example, Alice could fund a payment with USDT on Arbitrum while Bob receives USDC on Base, if that route is offered. Alice would review the quote and authorize the required wallet actions.
Receiving at an external wallet may not require the recipient to use the Reway interface. The exact requirements depend on the released flow.
Payment Requests
A request is directed at a particular payer. It can include an amount, receiving asset and network, description, expiry where supported, and payment status.
For a freelancer with a repeat client, this could keep the request and its payment outcome together. The client would still choose a supported asset to pay with.
Which workflow fits?
| Workflow | Who starts it? | Best suited to |
|---|---|---|
| Payment link | The recipient | Sharing payment details with a client or another payer. |
| Send | The sender | Starting a direct transfer to a user or supported wallet. |
| Payment request | The recipient | Asking a specific payer for a specific payment. |