Invoice vs payment link vs bank transfer: what should you use?

A customer asks how to pay. Should you send an invoice, a payment link, or your bank details?

The answer can be more than one of those things because they do different jobs.

An invoice documents a payment request. A payment link gives the customer a web-based payment experience. Bank-transfer details tell the customer where and how to send a transfer. An invoice can contain both a link and bank instructions, while a payment link can lead to several different payment methods.

Once you separate the document, the interface, and the underlying method, the choice becomes much clearer. This guide explains how the pieces work, which combinations suit different sales, and what to consider about cost, records, refunds, disputes, and security.

The difference at a glance

Tool	Main purpose	What it does not establish by itself
Invoice	Describe the goods or services, amount due, and payment terms	That a transfer has been made or received
Payment link	Bring the customer to a page for payment or payment instructions	That every payment method is available or the payment is complete
Receiving details	Specify the destination and instructions for a transfer	The commercial terms or the identity of the invoice being paid

A useful example is a consultant billing a business for a completed milestone. The business may need a formal invoice for approval, then pay by bank transfer using the receiving details printed on it. No card checkout is necessarily required.

An online seller offering a fixed-price workshop may prefer a hosted payment page so buyers can complete a purchase immediately. Whether a separate invoice must be issued depends on the transaction and applicable requirements; a convenient checkout does not decide that question.

The tools can support each other. Choosing a payment link does not mean abandoning invoices, and issuing an invoice does not require the customer to pay by bank transfer.

What an invoice does

An invoice creates a structured commercial record of a request for payment. It identifies the supplier and customer, the goods or services, the amount and currency, and relevant dates and terms.

It also gives the customer’s finance team something to approve and a reference to use in its own records. A purchase-order number, project description, or billing period can connect the invoice to the buyer’s internal process.

Common invoice fields include a unique invoice number, issue date, seller and buyer details, a description, item amounts, relevant tax information, the total, and the agreed due date. Statutory requirements differ. For example, GOV.UK’s invoice guidance sets out fields required under UK rules; it is not a universal global checklist.

An invoice is not a receipt

An unpaid invoice is a request. A receipt or verified payment record provides evidence of payment. A system may mark an invoice paid automatically, or someone may manually update it after an external bank transfer.

That distinction is visible in Stripe’s invoice documentation, which allows externally paid invoices to be marked as paid outside its payment processing. The status of the commercial record and the underlying financial transaction therefore need to be understood together. Stripe: How invoicing works.

For your own workflow, decide which evidence is required before marking an invoice paid. A client’s statement that it has “gone to finance” should not close the invoice.

What a payment link does

A payment link is a URL that takes a customer to a payment page or a page containing payment instructions. What happens there depends on the provider and configuration.

A link might open a checkout for a fixed product, a customer-specific invoice, a subscription, or a bank-transfer instruction page. Some links can be reused; others represent one particular payment request.

For example, Stripe distinguishes reusable Payment Links from invoices addressed to specific customers in its own product documentation. That is an example of how one provider separates the tools, not a rule that every service follows. Stripe: Payment Links.

Before using any link product, determine whether the customer can change the amount or quantity, whether the link expires, whether it can be paid more than once, and how the resulting payment connects to your records.

The link is an interface, not a payment rail

A URL can present a card payment, bank payment, digital wallet, or another supported method. The route’s processing, fees, and dispute rules come from that underlying method and provider arrangement.

This explains why “pay by link” is not enough information for a cost comparison. You need to know how the customer will actually pay through it and what happens after the payment is accepted.

For the same reason, a link can show bank instructions without providing an immediate online transfer. Opening the page is not proof that the customer has submitted a payment.

What bank-transfer receiving details do

Receiving details specify how to send a payment to an account or receiving service. Depending on the route, they may include a beneficiary name, account number or IBAN, bank identifier, currency, transfer method, and mandatory reference.

The payer normally submits the transfer through its own bank or payment service. The recipient then needs to identify the incoming payment and connect it to the commercial request.

Some services provide virtual account identifiers to help distinguish incoming payments. Others rely on a required reference. Stripe’s bank-transfer documentation, for example, describes using virtual account numbers to support reconciliation. The implementation is provider-specific. Stripe: Bank transfer payments.

Do not assume that an account number supports every rail or currency. Use the exact instructions issued for the intended route. Our guide to sending bank details internationally explains the fields and includes a client email template.

How the three tools fit into a payment workflow

A complete workflow connects the commercial request with the actual money movement:

1. Agree the product or service, amount, and payment terms.
2. Issue the appropriate invoice or order record.
3. Present one or more supported ways to pay.
4. Receive evidence of the payment’s financial status.
5. Match the payment to the invoice or order.
6. Confirm the result to the customer and retain the records.

In a hosted checkout, software may connect several of these steps automatically. In a bank-transfer workflow, the business may perform more of the matching itself. Neither arrangement removes the need to understand which payment settled which obligation.

For a fictional design project, the invoice might be USD 1,500, with both a bank-transfer option and an eligible card checkout. The client should pay once using its chosen method. If it starts one method and then switches, check whether the first attempt can still complete before treating it as abandoned.

Avoid sending several independent payment requests for the same obligation without a way to reconcile them. The problem is not offering choice; it is failing to connect the choices to one commercial record.

Choose a combination for the type of sale

One client, a custom project

An invoice usually provides the detail needed for approval: the project, milestone, purchase order, agreed amount, and due date. Add compatible bank instructions or a customer-specific payment option.

A reusable generic checkout may be less useful if it cannot carry the client’s exact invoice information or prevent an incorrect amount. Evaluate the tool against the sales process rather than its visual simplicity.

Many customers, a standard product

A hosted payment page can make a fixed-price purchase easier to complete without a custom invoice conversation for each buyer. The business still needs reliable order records, the required customer documents, and a refund process.

Check how the system identifies each purchase if everyone uses the same link. A reusable link is not a unique transaction identifier.

A monthly retainer

Recurring invoices and automatic collection are separate capabilities. A recurring invoice can remind a customer to make a fresh bank transfer each month. Automatic collection requires the appropriate payment method, consent, and provider support.

Do not describe a monthly invoice email as an automatic debit unless the actual arrangement authorises and performs one.

A large business customer

Start with the buyer’s accounts-payable requirements. It may need a supplier record, purchase order, formal invoice, and bank-transfer instructions. A link that works perfectly for a consumer purchase may not fit that process.

An international customer

Add currency and route compatibility to the decision. The currency shown on a checkout, the currency charged to the customer, and the currency paid out to the seller can differ. Confirm all three, including who handles conversion.

Compare costs using the underlying payment method

Invoices and links may have software charges, but the largest transaction-dependent costs often relate to processing, conversion, and payout. Obtain the actual provider quote instead of assuming that an invoice is free or a link has one standard fee.

Here is a simplified fictional comparison for a USD 2,000 invoice. The rates are teaching examples, not quotes or market averages. Both options assume no FX and no additional charges.

Method	Illustrative charge	Net amount
Bank-transfer collection	USD 8 fixed charge	USD 1,992.00
Card payment through a link	2.5% plus USD 0.30	USD 1,949.70

The difference is USD 42.30. That is useful information, but it does not establish the best commercial choice on its own.

Perhaps the customer can complete the card checkout immediately but needs a supplier setup to send a bank transfer. Perhaps the sale value is much lower and the fixed charge matters more. Perhaps the business already pays for an invoicing tool whose bank reconciliation saves administrative time.

Compare the same transaction and include relevant software costs, foreign exchange, payout charges, and the effort required to handle exceptions. Convenience has value, but it should be evaluated explicitly rather than treated as free.

Design reconciliation before you start collecting

Reconciliation connects the invoice or order to the amount actually received. It becomes harder when the payment request, processor, bank, and accounting record all use different identifiers.

For each sale, preserve the invoice or order number, customer, expected amount and currency, payment identifier, received amount, fees, and refund or adjustment history.

A processor may pay out several transactions in one bank deposit. Matching the deposit to a single invoice will then be wrong. You need the settlement or payout report that explains which payments and deductions make up the deposit.

With direct bank transfers, common exceptions include two clients sending identical amounts, one client paying several invoices together, and a customer making a partial payment. An invoice number in remittance advice can help, but mandatory receiving references must still be preserved.

For a detailed worked approach, see payment references and reconciliation.

Distinguish refunds, returns, and disputes

These events can affect the same sale but follow different processes.

A refund is generally a merchant-initiated repayment through an available process. Depending on the method, it may take time to reach the customer and may not reverse all original fees.

A bank return or recall process concerns the transfer itself. The available options depend on the rail, institutions, reason, and stage. A request to recall money is not equivalent to a guaranteed cancellation.

A card dispute is raised through the cardholder’s issuing institution and follows the relevant network and provider process. Stripe’s documentation explains that a formal dispute can remove the disputed funds from a merchant’s balance while the case is considered. Stripe: How disputes work.

This distinction matters when comparing methods. A successful checkout is not a promise that the payment can never be disputed. Conversely, using a bank transfer does not make every completed transaction immune from fraud claims, returns, or other applicable processes.

Keep evidence of the order, customer communication, agreed terms, and delivery. Use the provider’s stated process rather than issuing an unrelated transfer that might duplicate a refund or conflict with an open dispute.

Make the customer experience clear

The customer should be able to answer five questions without asking you:

• Who am I paying?
• What am I paying for?
• What amount and currency will I pay?
• Which payment methods can I use?
• How will I know the payment was received?

A page with many payment logos can still fail these questions. A plain invoice with one clear, compatible method can answer them well.

For a payment link, check the page title, business identity, product description, amount, currency, and confirmation message. Test the experience on a phone. If a method takes time to complete, make sure the result distinguishes a pending payment from a completed one.

For bank details, keep the instructions together and copyable. If you offer both a link and bank transfer, say that they are alternatives for the same invoice and make the process for identifying the selected payment clear.

A short cover message can do much of that work:

Protect the payment instructions and the customer’s data

Use the hosted provider’s intended payment flow for sensitive payment information. Do not ask a customer to email card details or send you a banking password to complete a purchase.

For links, make the destination recognisable. Avoid unnecessary URL shorteners that hide where the customer is going. A familiar brand name in a message is not enough; the customer should be able to verify the actual domain and business identity.

For invoices, control who can edit the payment instructions. Store the approved version and use a verification process for bank-detail changes. The FBI recommends independent verification of changes to payment procedures as a defence against business email compromise. FBI guidance.

Collect only the customer information needed for the sale, applicable requirements, and support. A broadly reusable public payment link should not expose another customer’s private invoice details.

Common mistakes to avoid

Treating the link as the receipt. A URL proves that a payment opportunity exists, not that someone paid. Check the actual payment record.

Assuming all links accept cards. Some lead to bank-transfer instructions or other methods. Confirm the provider’s capabilities and the customer’s available options.

Using a generic link for a variable invoice amount. Check whether the amount and reference can be tied reliably to the specific customer obligation.

Marking the invoice paid on a screenshot alone. Reconcile the financial evidence through your own receiving records.

Sending changed bank details without verification. Treat the update as a controlled change, especially for recurring clients with saved supplier records.

Choosing on the collection fee alone. Include payout costs, FX, recordkeeping, refund handling, and the operational needs of your customers.

Frequently asked questions

Can a payment link replace an invoice?

It can replace some of the payment-request conversation, but it does not automatically replace the commercial or statutory document the sale requires. Some providers generate an invoice alongside the checkout; verify what yours actually does.

Can an invoice include a payment link?

Yes, where your tools support it. The invoice documents the request and the link presents a way to pay. Keep the amount, currency, customer, and invoice identity consistent between them.

Are bank transfers always cheaper than card payments?

No universal rule applies. Fixed fees, payment size, FX, provider pricing, and destination costs can change the comparison. Compare the final amount and operational effort for your actual sales.

Is a payment link safe to share publicly?

A provider may design a reusable product link for public sharing. A customer-specific invoice link can expose private information or enable unintended actions. Understand the link type and its access controls before publishing it.

What should a freelancer start with?

Start with the client’s approval requirements and a payment method both parties can use. For custom business work, that often means a clear invoice plus complete payment instructions, with a hosted option where it is useful and supported. The broader international client payments guide helps plan the full process.

Choose the documents and payment tools together. The most effective setup lets the customer pay correctly and leaves you with a clear record of what that payment settled.