Payment links
How to Get Paid with a Payment Link
Use payment links for service invoices and agreed deposits. Learn how reusable links create individual checkouts and how to confirm payment.
The short answer
A payment link gives your client a clear way to pay an agreed amount through hosted checkout. Use a separate invoice for a negotiated job, a reusable link for a repeatable service, or a signed order session for integrated variable amounts. Confirm verified payment before starting the next step.
Turn an agreed price into a clear next step
You have agreed the scope, the customer has accepted the price, and the next email needs a way to pay. A payment link puts that next step in one place: the customer opens checkout and follows the instructions for the requested payment.
For consultants, agencies, and other service businesses, this can fit an existing sales process. You can share a checkout link alongside your proposal or invoice without first building an online store. Keep the service agreement, cancellation terms, and payment request consistent.
Know the difference between a link and an invoice
A reusable payment link is an entry point for collecting a configured payment. When a customer continues through the payment flow, Ulasend creates an individual invoice and checkout for that payment attempt. The reusable link and the resulting invoice are different records; keep the invoice tied to the customer and order.
For a unique job with a negotiated price, a direct invoice may be the clearest choice. For a repeatable service with the same price, a reusable link can reduce setup work. A dynamic link can support different amounts through a suitable integration. Explore payment links.
Set up the collection before sending the message
Your business must have an approved, active receiving setup before collecting live payments. Choose a supported asset and network, set the requested amount, and include an order reference where appropriate. Tell the client what the payment covers, then share the current checkout link. Review account setup.
The customer should use the exact amount and instructions displayed in checkout. If they need another asset or network, arrange a new request with an available route. An issued live invoice does not switch source simply because the customer chooses another network in their wallet. See the checkout guide.
Use a separate request for an agreed deposit
Imagine a design studio agrees a $1,000 project with a $300 deposit. It can request the agreed $300 as its own payment, label that purpose in its business records, and later issue a separate request for the $700 balance. The two requests keep the deposit and remaining balance clear in the studio's records.
Keep the deposit terms in your service agreement. Two separate payment requests do not create an automatic installment plan, a recurring subscription, or an escrow arrangement. Your team remains responsible for tracking the work, the outstanding balance, and any customer refund obligation.
Protect variable order amounts
If each order has a different total, a developer can create a signed checkout session from a reusable crypto payment link. That session binds the order reference and amount to an expiring URL. This requires a server-side integration; it is different from changing a visible amount in a browser link. Read the dynamic checkout workflow.
For a small number of negotiated jobs, creating a separate invoice may be simpler. Choose the workflow your team can reconcile reliably instead of adding automation before you need it.
Confirm the payment before starting the next step
Check the invoice's verified paid status and actual amount before releasing the order or treating the deposit as collected. A screenshot or a return to your website is not proof of payment. Automated fulfillment needs a verified webhook matched to the saved order. Review payment confirmation.
Then acknowledge receipt in your normal client communication and record the invoice against the job. The best payment-link workflow leaves both parties knowing what was paid, what it covered, and what happens next.