A payment link is a URL that is an invoice: open it and the payment surface is there, amount and assets preconfigured, ready to pay and shareable anywhere a link goes. No site, no integration, no code.
Links are how payments ride communication channels: paste in a chat, QR on a counter, link in an email campaign. Each carries its own confirmation state, so the merchant sees which conversation became a payment.
A payment link is a hosted checkout at a URL: create the link with an amount, a description, and accepted assets, and anyone who opens it can pay. No website, no cart, no code. The link renders the same payment surface an embed would, standalone.
Links carry state. A fixed-amount link presents one price; a flexible link lets the payer choose, which is the tips and donations shape. Links can be single-purpose and archived after use, or reusable as a standing payment point. Each payment against the link becomes its own record with reference, payer-visible status, and webhook delivery.
The pattern suits everywhere a conversation is the storefront: chat, social, email invoices, a QR code on a physical counter. The link is the checkout, whatever surface carries the URL.
A consultant sends a link in chat: 250 in the client's currency, description reading the milestone name. The client opens it, pays from any configured asset, and both sides watch the same confirmation page while the webhook closes the loop. The same link rendered as a QR on a market stall's card works identically: the buyer scans, the checkout opens on their phone, payment flows to the standing configuration, and the stall's close-of-day report aggregates every scan's takings with references intact.
U.CASH Pay-Now links carry any enabled rail, track their own payment state, and settle non-custodial; the receive platform gives every account a public, linkable payment page.
Payment links are the zero-infrastructure tier of taking money: live in the time it takes to fill a form, shareable anywhere a sentence fits, and fully compatible with the rest of the platform when the business grows into stores and embeds. U.CASH links inherit the same asset list and settlement as every other checkout surface. For teams scaling link use: generate links programmatically per invoice from the API rather than by hand, keep the description field meaningful since payers see it, and archive spent links so the standing list stays legible. The link tier grows into the API tier without rework.
Every term behind the rails, the assets, and the settlement.