One link, many payments
A payment link is a reusable slug — orbchain.io/l/your-slug. Every time someone opens it, a fresh payment is minted behind the scenes and the visitor lands on the hosted checkout: coin choice, address, QR, live status. Reusable is the operative word: the same link serves your next hundred customers, each getting their own tracked payment. Your part is pasting a URL.
Three decisions at creation, all in the dashboard:
- Amount: fixed or open. A fixed-amount link is a price tag — and the buyer can't tamper with it, because the link's amount wins over anything in the URL. An open link lets the payer enter the amount: consulting invoices, pay-what-you-want, top-ups.
- Priced in fiat, if you want. Set
$50instead of a coin amount and each payment locks the coin equivalent at open time — the same volatility-free pricing invoices get, without touching the API. - Settle in your coin. Attach a settlement coin and every payment through the link auto-settles — buyers pay whatever they hold, your balance accrues in USDT.
Links are still real payments
No-code doesn't mean no-plumbing — it means the plumbing is already connected. Every payment minted through a link is a first-class payment: it shows up in the dashboard and exports, fires your signed webhooks if you have them configured, gets an Ed25519 settlement receipt when paid, and counts toward the same balance you pay out or auto-settle from. A freelancer can ignore all of that today and turn on webhooks the day they automate — the link doesn't change.
Links are also managed objects: toggle one off when a sale ends (the URL starts declining politely), watch its use count, keep separate links per product or per client so revenue attribution is just "which link".
The embeddable button
Each link ships with a copy-paste HTML snippet — a styled donate/pay button for static sites, blogs, and documentation pages. It's still zero-integration (the button just opens the link), which makes it the fastest path from "static site" to "accepts crypto" that exists: paste, publish, done.
Where links stop and invoices start
The honest boundary: a link doesn't know what was bought. If you need order IDs flowing back into an order system, per-purchase metadata, or programmatic creation, that's the invoice API — same checkout, same rails, plus the integration surface. And if what you're really doing is collecting tips rather than selling, the donation page is purpose-built for that. The progression most solo sellers actually follow: link in a DM today, invoice API when the store ships, payouts when there's a team to pay — one account, no migration, each step optional.