Crest guide

Payment links for invoices: what they are and how to use them

Last reviewed: 10 July 2026

A payment link is a shareable URL that opens a page where a client can review and complete a payment. You create the link with a payment provider, then place it on the invoice or send it with the invoice. For sole proprietors and freelancers, the useful choice is usually an invoice-specific request for one client, a reusable checkout link for repeated services, or a stable payment profile link.

The link does not replace the invoice. Your invoice still needs the correct seller and client details, description, dates, total, currency, tax treatment, payment terms, and any other fields required for the transaction. The provider page handles only the payment flow that the provider makes available for your account, market, and client.

This article is general information. It does not determine whether a provider is available or suitable for your business, whether a particular payment is protected, or what legal, tax, accounting, refund, dispute, or record-keeping rules apply. Check the provider's current local documentation and pricing before sending a link.

Quick comparison

The phrase payment link covers several different tools. Start by identifying what the URL actually represents.

Link or detailWhat it isBest fitImportant boundary
Hosted checkout linkA URL to a provider-hosted checkout pageRepeated services, products, deposits, or open-price requestsIt can be fixed or open amount, one-off or reusable, and expiring or not; those are separate settings or product properties.
Payment request linkA link tied to a specific requestOne client, invoice, balance, or milestoneDo not assume it expires or accepts only one payment unless the named provider variant says so.
Payment profile link or handleA stable recipient identity such as PayPal.Me, Revolut.Me, or WisetagA reusable way for clients to find the recipientIt is not automatically tied to an invoice, amount, or commercial checkout.
Invoice payment linkA link tied to a particular invoiceClear matching between a request and the invoicePutting a generic reusable link on an invoice does not make the link invoice-specific.
Bank transfer detailsAccount and rail-specific information for a transferDirect bank paymentThese details are not a payment link, although a provider may display them behind one.
Payment QR codeA scannable carrier for a URL, profile, or structured payment dataPrinted invoices or a second way to open the same destinationA QR code is not automatically a payment method or a distinct payment request.

You may also encounter payment address. It is ambiguous search language: it can mean a profile link, payment handle, wallet address, bank detail, or another identifier. Define what it means in the provider you use, then call it by the precise name. A payout or send link points in the opposite direction—the creator sends money to a claimant—so do not use one when you intend to collect an invoice.

Choosing the right kind of link

Choose the link by the job it must do, not by the provider logo.

Use an invoice-specific request when you want the destination to reflect one client, amount, currency, invoice number, or milestone. It can reduce ambiguity when you later match the provider record to your invoice. Confirm whether the amount can be edited, whether the request can be paid more than once, and whether it expires.

Use a reusable hosted checkout link when you sell a repeated service, standard package, consultation, deposit, or product. It is easier to reuse, but the invoice and provider record may need a clear reference so you can identify which client paid. A reusable link can still have a fixed amount; an open-amount link can still be limited in other ways.

Use a payment profile link or handle when the main purpose is to identify the recipient. It is convenient for clients already using the same provider, but it may ask the payer to enter the amount or sign in. Put the invoice total, currency, and reference next to the link because the profile itself may not contain them.

Use bank transfer details when the client wants to initiate a bank payment directly and the required account information is appropriate for the payment rail. Do not label bank details as a link. If a provider offers both bank details and a hosted request, decide which route the client should use and avoid presenting two routes as if they were the same transaction.

Before choosing, check four independent attributes:

  • Amount: fixed by you, entered by the client, or configurable.
  • Use count: one payment, multiple payments, or configurable.
  • Time: expiring, non-expiring, or not documented.
  • Payer access: account required, guest access possible, app required, or dependent on the route.

Avoid inferring one attribute from another. A provider's “one-time payment” label may describe charge frequency rather than whether the URL stops working after one payer uses it.

What the client sees

Most hosted payment links open a provider-controlled page, not a page inside your invoicing tool. Depending on the provider variant and local setup, the client may see your business or profile name, a description, amount, currency, enabled payment methods, and a confirmation step. A profile handle may instead open a recipient profile and ask the client to enter an amount.

The experience can change by merchant account, payer location, currency, browser, device, eligibility, and provider configuration. A method visible to you in a dashboard is not necessarily available to every payer. Guest access may exist for one market or flow but not another. Check the exact link in a signed-out browser before relying on it.

The provider page also does not prove that its amount matches your invoice. Compare the amount and currency yourself, retain the invoice reference in your records, and use the provider's own transaction record when reviewing what happened.

How to create payment links with common providers

The steps below are bounded to the named variants and the official pages reviewed on 10 July 2026. Interfaces and eligibility can change. If your dashboard differs, use the provider's current localized help centre rather than forcing these steps onto another product or account type.

Stripe Payment Links

In Stripe Dashboard, open Payment Links, choose New, select or add a product or use the customer-chosen-price option where available, configure the page, and create the link. Stripe documents the current flow in Create a payment link; check the Payment Links product page for current local pricing and availability.

Stripe Payment Links are hosted checkout links. The reviewed documentation supports fixed product or subscription pricing and customer-chosen amounts, and says the same link can be shared with multiple customers. Additional controls can bound use, but do not call an ordinary reusable Payment Link invoice-specific unless you have created and recorded it for that invoice. Available methods depend on the merchant, payer, currency, browser, and device.

PayPal Business Payment Links

For PayPal's US Business Payment Links flow, sign in to a Business account, add the product or service details and pricing, build the page, then share the generated URL or QR code. See PayPal Business Payment Links and the US business fees page.

This is a reusable hosted checkout product, distinct from PayPal.Me and PayPal's mobile request-link flow. The seller can use an exact price or allow a customer-entered price depending on configuration. Merchant availability, guest access, methods, and pricing vary, so follow the local PayPal page for the account that will receive the payment.

PayPal.Me

Visit PayPal.Me, sign in or create an account, choose the available handle, and share the resulting profile link. The reviewed US help says an amount and currency can be appended to the URL. See the PayPal.Me frequently asked questions and PayPal's localized business pricing.

PayPal.Me is a reusable payment profile link, not an invoice-specific request. A payer may need a PayPal account during the flow, and local availability and funding routes vary. If you use it on an invoice, keep the invoice amount, currency, and reference visible outside the profile link.

PayPal request links

PayPal's reviewed US mobile-app help describes opening Send/Request, choosing the link flow, entering the amount, optional note, and currency, selecting Request, creating the link, and sharing it. See How to create and use PayPal links and the US business fees page.

This is a fixed-amount request link for one payment, distinct from PayPal Business Payment Links and PayPal.Me. The reviewed source documents a dated expiry for the US flow, but that high-volatility duration should be checked on the official page when you create the request. The recipient uses a PayPal account on the web or in the app.

Revolut Personal payment request links

The reviewed UK Personal help flow is Payments, New, Link, Request money, set the amount, then share. See Revolut's requesting money help and local Standard fees.

This is a fixed request flow. Do not carry assumptions from Revolut.Me, Pro, or Business into it. Availability, non-Revolut payer routes, methods, limits, commercial suitability, and expiry vary or are not settled by the reviewed source, so verify them in the local help centre.

Revolut.Me

The reviewed Italy-English help describes opening Payments, creating a payment link, choosing the request-money route, and sharing the generic Revolut.Me link. See Revolut.Me help and local Standard fees.

Revolut.Me is a reusable payment profile link with an amount entered by the sender. It is not automatically an invoice-specific or commercial checkout link. Payer routes, card eligibility, lifecycle controls, limits, and commercial use depend on local rules; verify them before placing this variant on a business invoice.

Revolut Pro Payment Links

Revolut's reviewed Belgium-English Pro help supports creating a payment link or QR code from the Pro sale flow, setting the seller's amount, and sharing it by message, email, invoice, or another channel. Use Revolut Pro Payment Links help for both the current flow and localized pricing details.

This is a Pro hosted checkout variant, not Personal or Business. The reviewed source supports reusable links or a usage limit, but eligibility, exact interface path, expiry, and payer methods can vary across localized documentation. Use the local Pro page for the receiving account.

Revolut Business Payment Links

For the reviewed Business flow, open Merchant, choose Get paid, then Payment link, add the page details and fixed amount, optionally set a payment-count limit, create the link, and share it. See Revolut Business Payment Links help and Business accept-payments pricing.

This hosted checkout requires an eligible Business and Merchant account. The link is reusable unless a supported payment-count limit completes it. The reviewed help and pricing pages use different locales, so recheck seller eligibility, payer methods, expiry, and same-locale pricing. Do not confuse this receiving link with a payout link under Transfers.

Wise Business Payment Links

Wise Business documents starting from Home or a currency balance and choosing Request, or opening Payments and choosing a single-use or reusable link. Enter the amount, currency, and description, choose from the methods enabled for the route, create the link, and share it. See Getting paid by Wise Business Payment Link and UK receive-money pricing.

Single-use and reusable Wise Business links have different lifecycles: the reviewed source says the former accepts one payment and expires, while the latter accepts multiple payments until closed. Exact expiry, local eligibility, and enabled payment methods remain route-dependent, so do not generalize them.

Wisetag

In Wise, open Payments, Payment Tools, and Wisetag, enable discoverability, then copy or share the link or QR code. See What is a Wisetag? and UK receive-money pricing.

Wisetag is a reusable profile handle with an amount entered by the sender, mainly for another Wise customer. It is distinct from Wise Business Payment Links and is not an invoice-specific hosted checkout. Keep the invoice amount, currency, and reference alongside it.

Venmo Business Profile and QR

In the reviewed US flow, switch to the Business Profile, choose Charge, QR Code, then Venmo Me; optionally set an amount, and share or print the result. See QR codes for Venmo Business Profiles and Business Profile transaction pricing.

Treat this as a US app, business-profile, and QR flow rather than a general web hosted-checkout link. The amount can be open or prefilled, and the payer can edit a prefilled amount. The payer uses the Venmo app and account. Do not infer a general external URL lifecycle from the QR flow.

Square Payment Links

In the reviewed US Square Dashboard, open Payments and orders, Payment links, choose Create link, select the link type, add the title, amount or frequency, configure the available options, save, and share. See Get started with Square Payment Links and the US Payment Links product page.

Square supports seller-set or buyer-entered amounts depending on link type. The reviewed source says links remain active until deactivated or deleted, and ordinary hosted checkout does not require a special Square app. A “one-time payment” setting describes charge frequency; it does not by itself prove that the URL accepts only one use.

SumUp Payment Links

The reviewed UK flow is Profile, Payment Links, Create payment link; choose a fixed or open amount, add the description, choose one-off or reusable, create the link, then copy it or show its QR code. See Send Payment Links with SumUp and the UK Payment Links product page.

This is a provider-hosted web flow. The official pages support fixed or open amount and one-off or reusable variants, but not a general time-expiry claim. Account eligibility, methods, and pricing are market-specific, so use the local SumUp pages rather than treating the UK flow as universal.

Where to put a payment link on an invoice

Put the link in a clearly labelled payment section near the total, currency, due date, and payment terms. Name the provider and tell the client what the link does—for example, “Pay this invoice with [provider]”—without implying that the invoice tool processes the payment.

Keep the visible invoice number or payment reference close to the link. If the provider allows a description or note, use the same reference there. For an open-amount or profile link, repeat the exact amount and currency on the invoice and ask the client to check them before submitting.

Use one primary route when possible. If you also show bank transfer details or another link, label each route separately so the client does not pay twice. Long raw URLs may wrap poorly in PDFs, so include a short descriptive label while retaining enough destination information for the client to inspect it. For the rest of the document, use the invoice requirements guide and freelancer invoice template.

Before you send the invoice

Check the invoice and link together:

  • Open the exact URL in a signed-out browser and, where relevant, on a phone.
  • Confirm the destination hostname belongs to the provider you intended to use.
  • Confirm the recipient identity or business name shown by the provider.
  • Compare the amount and currency with the invoice; check whether the payer can edit them.
  • Record whether the link is request-specific, reusable, usage-limited, or expiring.
  • Add the invoice number or another unambiguous reference where the provider allows it.
  • Confirm what the payer must use: account, app, guest flow, or another route.
  • Check the provider's current localized pricing and business eligibility.
  • Keep a copy of the invoice and the provider transaction record for your normal records.

Do not send a dashboard preview URL, a payout link, or a link copied from an unexpected message. If the provider offers a test or preview state, make sure the final client URL is the live receiving route intended for this invoice.

Safety and phishing

A familiar logo is not enough. Inspect the destination hostname before sending, and encourage the client to do the same. Avoid URL shorteners when they hide the provider domain. Do not publish an intended-recipient request link on a public page unless the provider designed that variant for public reuse.

If a payment request is unexpected, the safer response is to open the provider independently, sign in through the known app or site, and inspect the request there. Do not enter credentials or payment information after following a link whose sender, hostname, or purpose you cannot confirm.

A hosted link does not by itself establish that the underlying invoice is legitimate, that services were delivered, that funds settled, or that a payment qualifies for a refund, dispute process, or buyer or seller protection. Those questions depend on the transaction and the provider's current terms. Keep your own invoice, correspondence, delivery evidence, and provider records.

Using the link in payment reminders

When an invoice is still due, resend the invoice and the same request-specific link where appropriate. Check that the link remains active before every reminder, especially if it can expire, close after one payment, or reach a usage limit. If you replace it, update the invoice or clearly tell the client which link supersedes the old one.

Keep the reminder factual: identify the invoice, original due date, amount, currency, and current payment route. Do not create urgency by making unsupported claims about provider deadlines or settlement. See the payment reminder email guide for a practical sequence and templates.

Use your existing payment link on a Crest invoice

Add your provider's payment link to a Crest invoice. Crest presents the external URL in the PDF and live invoice and keeps payment status manual. Crest does not process, verify, or reconcile the payment.

Create an invoice

Frequently asked questions

Are payment links safe?

They can be a normal way to reach a provider-hosted payment flow, but the format alone does not establish that a request is legitimate. Check the sender, invoice, destination hostname, amount, currency, and provider account. For an unexpected request, open the provider independently rather than relying on the message link.

Does a payment link prove that an invoice was paid?

No. The URL is a route into a payment flow. Review the provider's transaction record and your receiving account, then update the invoice status using your normal process. A client opening a link or reporting payment is not the same as your confirmation that funds arrived.

Can one payment link be reused?

Sometimes. Reuse is variant-specific. Stripe and PayPal Business describe reusable hosted links; Wise Business and SumUp expose distinct lifecycle choices; some request links accept one payment; profile links are generally stable identities. Check use count separately from amount and expiry.

Is a QR code a payment link?

Not necessarily. A QR code is a transport format. It may encode a payment-link URL, a profile handle, or structured payment data. Describe the destination or data it carries rather than treating “QR” as a separate payment method.

What is a payment address?

It is an ambiguous term. A provider may use it for a profile link, handle, wallet address, bank detail, or another identifier. For invoices, use the precise term—hosted checkout link, payment request link, profile handle, bank transfer details, or payment QR code—and explain what the client must do.

Can a payment link replace the required invoice fields?

No. The invoice and payment route do different jobs. Keep the seller and client details, invoice number, dates, description, amount, currency, tax treatment, due date, and other required information on the invoice. The payment link simply gives the client a route to a provider flow.

Should I put more than one payment route on an invoice?

Only when it helps the client and you can label the alternatives clearly. State that the client should choose one route, and keep the provider name, amount, currency, and reference visible. Multiple poorly distinguished routes increase the chance of confusion or duplicate payment.

Sources and update policy

The provider claims in this guide were reviewed against official product, help, and localized pricing pages on 10 July 2026. Crest maintains an internal evidence ledger and review contract for this guide.

Provider interfaces, availability, pricing, payer methods, expiry, limits, refunds, disputes, protection, and generated URL patterns can change. Recheck the exact official and localized provider pages before publication and before relying on a high-volatility claim. The full provider ledger should be reviewed at least every 90 days; high-volatility claims should be rechecked within 30 days of publication or omitted.

Official provider references: