Payment links
One shareable link with the details someone needs to pay you.
A payment link gives someone the information they need to pay you in one place. You define the payment and your receiving preferences, then share the link with the payer.
They can choose a supported asset they already hold. Reway finds the route to your preferred receiving asset and network.
What a link contains
| Detail | Purpose |
|---|---|
| Recipient | Identifies who should receive the payment. |
| Amount | Sets the amount being requested. |
| Receive asset | Specifies the token you want to receive. |
| Receive network | Specifies the network where you want to receive it. |
| Description | Gives the payer context, such as a project name or service. |
| Optional settings | Expiry or extra information, where the app supports them. |
A client payment example
You complete a design project and request $500, with USDC on Base as your receiving preference. Your client holds a different supported asset.
Instead of sending them a wallet address plus separate token and network instructions, you share the payment link. The client reviews the quote and pays from their wallet. The available route determines the amount they need to spend and its costs.
Choose your next step
- Create a link if you want to collect a payment.
- Pay a link if someone has sent you one.
- Check activity if you need to confirm whether a payment completed.
Links, requests, and customization
A link is designed to be shared. A payment request is intended for a particular payer and can have its own request status. Direct requests are part of the planned payment extensions described in Send and requests.
More link customization is also part of the product direction. Labels, identity information, and presentation can make a link easier to recognize. Use the settings actually offered in the app; customization options are not all part of the baseline.