Payment links: request and verify a customer payment
Create a hosted payment link for an order or invoice, share it by message or QR code and verify the provider’s completed transaction before fulfilment.
- Published
- Last updated
Payment links take customers to a provider-hosted checkout where they can pay for an order or invoice. Create the request with an identifiable reference, then match the successful provider transaction to that order before sending the goods.
Link by Stripe is a separate digital wallet that saves payment details for later purchases. A payment link is the URL you share, and Link can be one payment option inside its checkout.
What a payment link does
A payment link connects a request for money to a hosted payment page. The provider collects the customer’s payment details and records the transaction in your merchant account.
In a fictional example, a homewares retailer agrees to sell a lamp for $180 under order LAMP-482. Staff create a fixed-price request describing the lamp and record LAMP-482 against it. The customer opens the URL on their phone and pays. Staff match the successful $180 payment to LAMP-482 before releasing the lamp.
A reusable product link can collect many separate payments. An invoice link identifies a particular bill. Neither the existence of the URL nor a customer opening it proves that the bill has been paid.
If someone asks about a “Link payment method”, identify the screen they mean. Stripe’s Link wallet retrieves saved payment details at participating checkouts. A message containing a hosted checkout URL is a payment request. The Stripe guide covers the wallet and its account controls.
A toll account is different again. Linkt manages toll-road accounts, so a toll notice belongs in the operator’s account service. It is unrelated to creating a retail payment request.
Choose a provider for the request
Use your existing provider when it can carry the order reference and show the final payment state. Choose an invoice workflow when you need a bill with a balance and due terms.
Australian request options
| Route | Methods and currency | Invoice or recurring use | Expiry and reconciliation |
|---|---|---|---|
| Stripe Payment Links | Cards and eligible local methods, with local-currency pricing options | One-off prices or subscriptions. Use Stripe Invoicing for a customer-specific bill | Reusable until deactivated, or limited by completed payments. Match payments in the Dashboard |
| Square Payment Links | Cards and supported wallets. An Australian account charges in its account currency | Reusable sales links and recurring subscriptions. Square Invoices is a separate bill workflow | Deactivate an unwanted link. View link sales and transactions in Square Dashboard |
| PayPal invoices | PayPal and eligible card checkout, with the invoice’s selected currency | Customer-specific invoices and recurring invoice schedules. A schedule sends bills and does not itself authorise automatic collection | Track paid and pending invoices. Cancel an incorrect unpaid invoice before replacing it |
| Westpac OnlinePay Pay by Link | Hosted payment choices enabled for the merchant account | Amount-only or itemised requests with a merchant reference. Use a separately agreed recurring-payment service for subscriptions | Dashboard links default to one day and can last up to 30 days. Track Paid, Not paid or Expired |
Stripe’s payment-link documentation explains its hosted checkout. Square’s Australian payment-link page describes its reusable links and supported methods. PayPal’s invoicing instructions cover bill creation and recurring schedules. Westpac documents its reference and expiry controls in Pay by Link.
For a one-off store order, Square suits a retailer already using Square’s sales records. Stripe suits a retailer collecting through Stripe, especially when the checkout needs currency options. For a specific invoice, use the provider’s invoice product so payments reduce the right bill.
For an international customer, choose the charge currency before sending the request and explain any conversion. Square supports international sales through payment links, but its Australian instructions exclude tax and shipping-fee settings for those sales. Add these costs to the agreed order through a supported workflow before requesting payment.
UK availability is a separate account question. Stripe publishes a UK Payment Links offering, but its UK pricing and account conditions do not set the terms for an Australian account. A customer paying from the UK does not turn your Australian merchant account into a UK account.
Compare processing charges and currency-conversion costs for the exact method you will accept. A card rate, an instalment rate and an international-payment rate can produce different deductions from the same order.
Create and send the request
Create the request inside your authorised merchant account, with payment collection enabled and the right staff permissions. Square requires payment-link permissions. Westpac OnlinePay requires the Merchant Supervisor role.
For a fixed-price Stripe request, follow this sequence from Stripe’s creation instructions:
- Open Payment Links in the Dashboard and create a new link. Select a product or create the product and price.
- Enter the agreed amount and currency. Use a description the customer recognises, such as “Lamp, order LAMP-482”. Confirm whether delivery and tax are already included.
- Add an order-reference custom field if the reference is not already tied to the request. A reusable link needs a way to identify each purchaser’s order.
- Choose the supported payment methods and required customer details. For one specific payment, enable “Limit the number of payments” and set the limit to one.
- Preview the hosted checkout. Confirm the merchant name, final amount and description, then create and copy the link.
- Open the copied destination in a separate browser window. Check that it shows the intended request before sending it to the customer.
For an invoice, create the invoice first and share its payment link. Adding a generic product link to a PDF invoice does not automatically connect the resulting payment to that invoice’s balance.
Send the URL by email, SMS or the messaging channel already used for the order. Include the reference and amount in the message so the customer knows what they are paying. Sending an SMS is a delivery method, not a separate payment system.
A QR code can contain the same URL. Stripe lets you download a QR image from the link’s details page. The code’s usefulness depends on the underlying request staying active.
Verify the payment and update the order
Verify the payment in the provider account before changing the order to paid. Search for the transaction and match the gross amount, currency and order reference. Record its transaction identifier against the order.
For the fictional lamp sale, a successful $180 transaction for LAMP-482 clears that order’s payment check. A pending transaction stays pending. A bank payout can combine several sales and deduct fees, so its net amount is a separate reconciliation task.
Stripe shows payments in the Dashboard and can send successful-payment emails when you enable notifications. Its post-payment instructions also explain receipts and refunds.
Automated fulfilment needs the provider’s server notification. Stripe sends a checkout completion event, but delayed payment methods need the later success state before goods are released. Stripe’s fulfilment documentation requires handling repeated notifications without fulfilling the same payment twice.
The customer can see a confirmation page or return to your site after checkout. That return page is useful for showing next steps, but it cannot prove payment by itself. A connection can fail after a successful charge, and a screenshot can show an incomplete or unrelated transaction.
Enable the provider’s payment receipt where appropriate. Keep your order confirmation separate so the customer can see both what they bought and that the provider accepted payment.
Handle QR codes, expiry and failed attempts
Test a payment QR code on another device and compare the destination with the original hosted URL. Confirm the merchant and amount on the loaded checkout. A QR code containing a checkout URL opens a web page. Native payment schemes can use different instructions, as the QR payment guide explains.
Stripe’s sharing instructions state that its QR image does not expire, but deactivating the underlying link takes the customer to an expiry page. Square lets staff deactivate links. Westpac’s dashboard shows when a request has expired.
| What you see | What to check | What to do |
|---|---|---|
| A customer asks for another link | Search the original transaction and reference | Resend the active request only if it remains unpaid |
| A request has expired | Check its amount and payment history | Re-enable it where supported or create a replacement after confirming the balance |
| The agreed amount has changed | Check whether the old request is still payable | Deactivate or cancel it, then send the corrected request |
| Checkout reports failure | Check for a successful or pending transaction | Let the customer retry only after resolving the original attempt’s state |
| Two payments match one order | Compare both transaction identifiers | Refund the duplicate through the provider and retain the refund record |
A refund changes a transaction, while deactivation stops future use of a link. Complete both actions when the situation requires them. The Square guide covers its link workflow in more detail.
Explain safe payment requests
A provider-hosted checkout keeps card entry on the provider’s page, but a convincing message can still contain the wrong destination. Customers must recognise the merchant and amount before paying. Staff must copy the URL from the merchant account and keep control of who can create requests.
Stripe documents encryption of card data and its payment security controls. Its hosted checkout handles the full card details. Your transaction record contains payment information such as the amount, status and masked card details, plus customer information you collected. That does not give staff access to the customer’s full card number or security code.
Keep a customer’s wallet settings and saved-payment actions in the provider’s own account interface. Never ask them to send a security code, password or full card details in a reply to the request.
If a customer questions a link, confirm the order through your existing contact channel and provide a fresh copy from the merchant account. Release the order only after its matching transaction shows successful payment.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.