Payment Links: Getting Paid Without a Checkout

A payment link removes the step where getting paid requires the customer to decide and then act, and that timing effect is worth more than the card acceptance. Cutting days-to-payment from 38 to 16 on $44,800 of monthly billing releases about $32,853 of working capital. But at a $3,200 average invoice the bigger decision is which method the link offers first: card costs $15,641 a year against $2,520 for capped bank debit, which dwarfs everything else here.

What a payment link replaces

A payment link is a hosted page with an amount attached, sent by email, text, or embedded in an invoice. The customer clicks, pays, and the funds settle to you. There is no storefront, no checkout to build, and no integration.

It is worth being clear about what problem that solves, because it is not the obvious one:

• It is not primarily about accepting cards. You could accept cards by phone, per our virtual terminal analysis, and many businesses do.
• It is about removing the step where payment requires a decision and an action. An invoice with bank details requires the customer to initiate something. A link does not.
• It also removes you from handling card details, which per our compliance analysis is a meaningful reduction in what you are responsible for.

The second point is where the money is, and it is a timing effect rather than a fee effect.

What it is actually worth

Take a service business sending 14 invoices a month at $3,200, which is $44,800 of monthly billing.

If a link cuts average days to payment from 38 to 16, that is 22 days of receivables released:

• Working capital released: $44,800 × 22 ÷ 30 = $32,853, once
• Plus every month after: the shorter cycle persists, so the collection effort falls permanently

Price that against your cost of capital and the fee question looks different. If the released $32,853 would otherwise have been drawn on a facility at 14%, the annual saving is roughly $4,600, which is the correct figure to set the processing fees against. Per our receivables analysis, speed of collection is usually worth more to a small business than the percentage it pays to achieve it.

The fee arithmetic, and the one decision that matters

On the same 14 invoices at $3,200, the payment method dominates everything else:

The difference between card and capped bank debit is $13,121 a year on this volume, which dwarfs every other decision in this article. Per our b2b card analysis, at a $3,200 average ticket a percentage fee is a large absolute number, and the cap is what makes the method viable at that size.

So the design question is not whether to use links. It is which method the link offers first.

• Offer bank debit as the default and card as the alternative, rather than the reverse.
• Confirm the cap. An uncapped percentage on bank debit removes most of the advantage at this ticket size.
• Do not surcharge to steer without checking the rules, per our surcharging analysis, which vary and are restrictive.
• Accept that some customers will use the card anyway, and that per our b2b card analysis being paid now by card often beats being paid in 38 days by bank transfer.

The last point prevents over-optimizing. A customer who pays by card the day the link arrives has cost you $93 and saved you 22 days. That is a trade worth making, which is why the goal is to default the cheaper method rather than to block the expensive one.

Setting them up properly

1. Put the invoice number in the link's reference field. This single step is the difference between automatic reconciliation and manual matching, per our reconciliation analysis.
2. Lock the amount where it should be fixed and allow partial payment only where you intend to accept it.
3. Set an expiry. An indefinitely live link for a specific invoice is a payment that can arrive after the matter is settled, and per our accuracy analysis a payment with no matching open item is the common source of reconciliation breaks.
4. Send it in the invoice, not separately. A link arriving in its own email looks like a phishing attempt, and per our invoice fraud analysis customers have been trained to be suspicious of exactly this pattern.
5. Use your own domain or a recognizable hosted page. The same reason.
6. Automate the reminder sequence with the link included each time, since the reminder that contains no way to pay is a reminder to do something later.
7. Reconcile daily, not monthly, because links produce many small arrivals rather than a few batched ones.
8. Record the method used per customer, so you know which relationships are expensive and can address those specifically.

Item four is the one that costs businesses real money through no fault of their own. Payment request fraud works by sending a plausible payment link, so a legitimate link sent out of context is both less likely to be used and actively training your customer to trust the pattern a fraudster will exploit. Putting the link inside the invoice document and the invoice email is the whole mitigation.

Where links are the wrong tool

• Recurring billing. Per our recurring billing analysis, a subscription needs a stored mandate, not a link sent every period.
• Very small amounts. A fixed per-transaction component dominates a small ticket, and per our transaction cost analysis the arithmetic reverses entirely below a certain size.
• In-person sales. Per our channel analysis, card-present rates are lower and approval rates are higher, so a link at the counter costs more and converts worse.
• Where terms are the product. Per our terms analysis, if you compete by offering 60 days, a link that invites immediate payment is not the problem to solve.
• High-value one-off transactions with a new counterparty. A large payment from someone you have not dealt with before deserves a verified bank transfer and a conversation.

The fourth item is worth examining honestly before adopting links at all. A business whose customers chose it partly because it invoices on terms is not suffering a collection problem, it is delivering a feature. Speeding up collection in that situation is a repricing of the relationship, and per our pricing analysis it should be treated as one rather than introduced as an administrative improvement.

Frequently asked questions

This guide is educational and does not constitute legal, compliance, tax, or payments advice. All figures are stylized illustrations using assumed invoice volumes, values, fee rates, and payment timings, and do not describe any particular provider or merchant. Processing rates, fee caps, bank debit return rules and timelines, surcharging restrictions, and data security obligations vary by provider and by jurisdiction and change over time. Confirm current terms with your provider and applicable surcharging rules with qualified counsel.