Get paid in crypto with a payment link — no website needed
Not every seller has a shop with a cart. A freelancer sends one invoice a month, a tutor sells lessons over chat, a streamer takes tips, a small brand sells through Instagram. For all of them the simplest way to accept crypto is a payment link: a checkout page you share as a URL or a QR code. This post explains how links work in easyway, the three kinds, what the person paying sees, and where the money ends up.
What a payment link is
You create a link once in Dashboard → Payment links and get an address of the form easyway.cash/pay/link/pl_…. Every time someone opens it and continues, a fresh invoice is created in the background, exactly like an invoice made through the API. The payer chooses a coin and a network, gets an amount and a deposit address, and pays from any wallet or exchange. Because it is a normal invoice, everything else works the same: the exchange rate is locked for the life of the invoice (60 minutes by default, adjustable from 5 minutes to 24 hours in Settings), short payments are handled, and your webhooks fire if you have any.
The price of a link is always set in US dollars. The payer can settle it in any of the 44 coins on 12 networks you accept; the checkout converts the dollar amount at the moment the coin is chosen.
Three kinds of link
A payment link suits invoices, deposits, services and top-ups; a donation link tips, creators and causes; a product link digital goods such as files, licence keys and gift codes.
| Kind | Price | What the payer adds |
|---|---|---|
| Payment | Fixed, or open (min. and max.) | Nothing |
| Donation | Open amount | Optional name (40 characters) and message (200) |
| Product | Fixed | E-mail address (required) |
With an open amount the payer types the price. Unless you set your own bounds, it must be between 1 and 100,000 USD; a tighter range is one field each in the link form. A fixed-price link ignores any amount the browser sends.
A donation link keeps the donor's name and message with the payment and can drive an on-screen alert in OBS while you stream; the setup is on the crypto donations page.
A product link delivers after payment. You write a delivery text (a download link, instructions; up to 5,000 characters) and, if you sell codes, upload a stock of them. Once the invoice is paid the buyer sees the text and one unused code, and gets them by e-mail too. A code is held for the buyer while they pay, so two people can never pay for the last one; when the stock runs out the link shows as sold out. More on this on the sell digital products page.
Sharing it
Each link in the dashboard has a copy button and a QR button. The QR dialog also downloads a print-ready 1024-pixel PNG, for a flyer, a menu or a shop counter. Paste the URL into a chat, an e-mail signature, a social profile or a bio. You can add an optional success URL to send the payer back to your page after paying, and switch a link off at any time without deleting its history.
Where the money goes
A confirmed payment lands on your easyway balance, in the coin the payer used, minus the flat 0.5% platform fee: a 120 USD payment leaves 119.4 USD worth of that coin. easyway keeps the balance until you withdraw it, and live withdrawals only go to wallet addresses you have whitelisted with two-factor authentication (see security). Fees and withdrawal minimums per coin are on the pricing page. The payments list in the dashboard can be filtered by source, so link sales are easy to separate from API invoices.
Try it before sharing
Links have a test mode like everything else. Create one in test mode and open it: that makes a test invoice, and the dashboard can simulate a full, partial or late payment for it, which runs the same crediting code and webhooks as a real one. The steps are in the sandbox guide. When it behaves the way you want, create the live version and share that.
When you outgrow links
A link is one price for everyone. When you need a different amount per order, your own order id in the invoice or automatic fulfilment from your backend, create invoices with the API instead: one request, then a redirect to the same hosted checkout. The documentation covers both, and accepting crypto on a website walks through the API route.