QR code payments: choose and verify a method

Choose a supported QR payment route for your store. Check the destination, amount and customer flow, then verify the provider’s actual receipt.

QR code payments let customers scan a code to open a checkout or authorise a payment in a supported app. Choose the payment provider and customer flow first. The same-looking square can contain a web address or payment data that only a compatible app understands.

For an Australian store, a hosted card checkout suits customers who want to pay through their browser. PayPal’s seller code suits customers using PayPal. A wallet-specific route suits customers who already use that wallet. In every case, fulfil the order only after you match the provider’s confirmed payment to it.

Choose the underlying QR payment route

Choose a QR payment route by where you sell and what your customers can use to pay.

RouteCustomer requirementFunding and receiptSuitable context
Hosted checkout URLCamera and browser for a card checkoutPayment methods enabled on the hosted page; provider pays out to your nominated accountA counter sign or remote request leading to an online checkout
PayPal seller QR codePayPal payment flow and appCustomer selects an available PayPal payment method; payment reaches your PayPal accountIn-person sales to PayPal users
WeChat Pay through StripeEligible customer’s WeChat appCustomer authorises the wallet payment; Stripe uses its standard payout scheduleOnline sales to customers who use WeChat Pay

Stripe Payment Links creates a hosted payment page and can turn its URL into a code. Customers paying by card don’t need a custom app. The code doesn’t turn an online transaction into a terminal card payment.

PayPal’s Australian business QR flow lets the customer scan your seller code and enter the total. It pays your PayPal account, so receipt there and withdrawal to your bank are separate events.

Stripe’s WeChat Pay documentation lists Australia as an eligible merchant location for its online acceptance route. Customers authenticate in WeChat, using their wallet’s supported funding. That route requires an operational business website and account eligibility. Don’t copy a procedure for paying merchants in China and assume it enables your Australian shop.

A scheme-specific code contains structured payment data. EMVCo’s QR specifications standardise that data format. The payment provider handles the subsequent transaction. Encoding the data yourself doesn’t enrol your store or establish acceptance.

Configure the merchant request

Set up the provider’s supported merchant account before creating a payment code. For PayPal retail sales, use the commercial seller QR route intended for goods and services.

  1. Confirm the account’s merchant identity and where receipts will arrive. Finish the provider’s account verification before displaying a code.
  2. Set the amount in the supported payment request, or decide who enters it. PayPal’s reusable seller code asks the customer to enter the total.
  3. Record the order reference in the payment request where supported. Otherwise, keep a till record that connects the order to its eventual transaction ID.
  4. Generate the provider’s code or encode the approved checkout URL. Keep a copy of the intended destination with your display record.

A static code keeps the same encoded content. It can lead to a reusable checkout or seller account. A transaction-specific code belongs to a particular request, with its own amount or expiry. A reusable sign is convenient, but staff must still match each receipt to an order.

A URL QR code generator encodes an existing address. It cannot open a merchant account, set up a wallet scheme or verify payment. Use the payment links guide when you need to create the hosted request behind the code.

Test the scan and customer checkout

Test the displayed code on a second device before customers use it. Start from the printed sign or checkout screen customers will actually scan.

For a hypothetical $48 order, record reference Q482 and the intended merchant. Scan the code and inspect the destination before opening it. Confirm that the checkout names your store and shows $48, or requires the customer to enter $48. Check that any required app opens and that the customer can review the payment before authorising it.

PayPal’s QR payment instructions describe scanning in its app, entering the amount and selecting the payment method. A browser card checkout follows a different procedure. Keep those instructions beside the relevant code so customers know which flow to expect.

Use the provider’s test environment where it supports the chosen route. A successful scan confirms readability and routing. Complete the payment check separately before treating the setup as ready for sales.

Verify receipt before fulfilment

Verify payment in your own provider account and match its transaction details to the order. A scan count, submitted request or customer screenshot doesn’t establish receipt.

For the hypothetical Q482 order, find the provider transaction for $48. Match the payer or available order reference and save its transaction ID against Q482. If the provider doesn’t carry your reference, reconcile it with the till record before releasing the goods.

PayPal defines a Completed payment as successful, with money in the recipient’s account. A Pending money request remains unpaid. Review a payment’s separate hold or review status before fulfilment, and follow any provider instructions attached to it.

Enable the provider’s payment notifications, then open the transaction itself when a notification arrives. If checkout fails or confirmation is delayed, inspect the existing attempt before asking the customer to pay again. When two completed payments exist for one order, keep both transaction IDs and refund the duplicate through its original transaction.

For PayPal, open Activity, select the payment and choose Issue a refund. Its refund instructions allow full or partial refunds within 180 days. Record the refund against the order and confirm its status. A refund request and money returned to the customer are separate checkpoints.

Keep a displayed code accurate

Replace a displayed code when its destination or payment request no longer matches the sale. Inspect signs for stickers placed over the original code and remove damaged copies from use.

Re-scan the actual display after changing an account, checkout or redirect. Confirm the merchant and total again. A readable code can still point to the wrong account or an expired request.

Stripe’s payment-link sharing instructions explain that its QR image doesn’t expire, but deactivating the underlying link sends customers to an expiration page. A transaction-specific provider request can have a different lifetime. Generate a fresh request when that route expires, then replace every copy customers can still scan.

Restrict staff access to payment settings and keep the provider’s account protections enabled. Display an alternative payment option, such as your staffed card checkout, for customers who can’t use the required app. Before opening trade, scan the code you display and confirm that staff can recognise the matching completed transaction.

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.

See it in actionFree trial · Simple setup