What is a payment? Methods and transaction states

A payment transfers value from a payer to a payee. See how payment methods, authorisation and settlement differ when you take an online order.

A payment transfers value from a payer to a payee to meet an obligation or buy something. In an online store, the customer’s payment instruction starts a process. The provider’s transaction result tells staff whether that process has succeeded. The order record then connects the purchase to fulfilment.

A payment method describes how the customer pays. A transaction state describes what has happened to a particular attempt. Choose a method guide in the directory below for its setup, processing time and cancellation rules, including the record that confirms receipt.

What a payment means

A payment moves value between the person paying and the person receiving it. The payer is the customer in an ordinary retail sale. The retailer is the payee. The Reserve Bank of Australia’s payments system explanation distinguishes the instruments people use from the arrangements that move funds between institutions.

Consider a fictional order, RET-204, with a total of $120. The order records what the customer wants to buy and the amount owed. Selecting Pay sends an instruction to the payment system. A successful transaction pays the order, while a declined attempt leaves the store without a successful payment for that attempt.

Keep the order number and payment reference together. The amount owed is a sales record. The payment instruction is a request. Receipt of funds requires the receiving account or provider’s payment record. An order confirmation alone cannot establish all of those events.

Payment methods and the systems behind them

A card, a bank transfer and a digital wallet describe different ways a customer can initiate payment. Behind them sit banks, payment networks and service providers. The payment gateway carries the checkout request into the provider’s processing flow. Its presence on a store does not make every method available.

For a card purchase, the card issuer decides whether to authorise the request. A card-funded wallet supplies payment credentials through its supported checkout. The underlying card still has an issuer and network. NAB’s digital wallet explanation describes using a payment token in place of the card number.

An Australian bank transfer can use the New Payments Platform (NPP), the infrastructure behind services such as Osko. PayID identifies an eligible account through a registered identifier, such as an email address. The NPP carries the payment. Australian Payments Plus explains how the NPP and its addressing work.

BPAY uses a biller code and customer reference number in the customer’s online banking. PayTo uses an agreement that the customer authorises through their bank. A quick response (QR) code can direct a customer to a payment request. Scanning the code starts the relevant flow without proving payment.

Use the method’s own guide to establish its acceptance and receipt rules. A card’s dispute process does not establish the recovery rules for a bank transfer. Store availability and processing times depend on the actual method and provider.

Authorisation, capture and settlement

An ordinary card payment passes through authorisation and capture before funds reach the retailer’s bank account. These stages answer different questions.

  1. The customer submits the payment request through checkout. The store or its provider records an attempt and a reference.
  2. The issuer authorises or declines the request. An authorisation can reserve the amount against the customer’s card. A reserved amount is still awaiting capture.
  3. Capture submits the authorised amount for collection. Some integrations capture automatically, while others let the retailer capture an authorised amount later.
  4. Settlement completes the financial obligations between the institutions involved. The RBA’s settlement explanation describes the accounts and systems that settle Australian interbank obligations.
  5. The provider pays the retailer from the available merchant balance under its payout arrangement. Match that payout to the receiving bank account.

Stripe documents separate authorisation and capture for eligible methods. Its provider record can show that an authorised payment still requires capture. That is different from a completed payment.

The issuer can explain the customer’s card hold. The merchant’s provider can confirm the capture and payment state in its records. The receiving bank can confirm the payout credit. Stripe’s payout guidance separates funds becoming available from their transfer to the merchant’s bank account.

A pending card entry, a paid order and a settled institutional obligation describe different records. Ask which record a status belongs to before using it to explain where the money is.

What changes for an online payment

Online checkout collects payment details through the configured provider’s payment surface. That can be a hosted checkout page or payment fields embedded in the store. The customer enters credentials or approves the payment there. The store records the provider’s reference and transaction result against its own order.

The customer can lose their connection after submitting payment. Closing a page does not establish whether the request failed. Stripe’s fulfilment guidance explains why the store must receive payment results independently of the customer reaching its confirmation page.

shoppa is an AI shopping agent that helps customers find, compare and buy products using the retailer’s catalogue and documents. Customers can complete a purchase in the chat on the retailer’s site. For a checkout reached through that conversation, use the configured payment flow and its recorded result to confirm payment. A natural-language answer saying that an order is paid does not replace the provider’s transaction record.

Keep the payment reference available to staff handling an order question. It connects what the customer saw in checkout with the transaction the provider can investigate.

Read payment and order states together

Compare the provider’s transaction state with the store’s order state before deciding whether to retry or fulfil an order. The following cases use fictional orders and the documented Stripe payment lifecycle.

Successful payment

For order RET-204, the provider records the $120 payment as succeeded and the store marks the matching order paid. Confirm the amount and currency against the order. Staff can proceed under the store’s fulfilment rules while the provider’s payout follows its separate schedule.

Declined request

For order RET-205, the card request is declined. Stripe’s payment record returns to a state requiring a payment method after a failed attempt. Staff can explain that this attempt has not succeeded. Let the customer correct the payment method through checkout instead of manually marking the order paid.

Interrupted checkout

For order RET-206, the customer sees an error, but the provider records a successful payment. Search by the existing payment reference and match the amount to the order. Correct the store’s order record through its supported reconciliation process. Asking the customer to pay again before that check can create a second payment.

If the provider still records processing, retain the order’s pending-payment state until the provider confirms the outcome. Stripe’s payment lifecycle distinguishes processing from succeeded and explains the state following a failed attempt.

When the records disagree, give the responsible provider the payment reference and amount, with the recorded state and order number. Tell the customer which result is confirmed and which record still needs investigation. Do not infer payment failure from a missing confirmation page.

Refunds, reversals and repeat payments

A refund returns all or part of a completed payment through the provider’s supported refund process. Record the refund reference against the original transaction. A refund request and the customer’s receipt of that refund are separate events. Stripe’s refund guidance describes pending and failed refund outcomes as well as successful refunds.

Reversing or cancelling an uncaptured authorisation releases the hold under the issuer’s process. It does not refund a captured sale. A card dispute begins when the account holder contests the payment through their bank. Stripe explains the dispute process and the bank’s role in deciding its outcome.

A scheduled repeat payment is a future instruction or collection under agreed terms. Each collection still needs its own transaction outcome. Authorising a PayTo agreement allows payments under its terms, as Australian Payments Plus explains. It does not establish that every later collection succeeds.

Staff can report that a refund was requested or that an authorisation was cancelled when the provider’s record confirms it. Report a completed refund only when its state supports that statement. Send unresolved refund or card-hold questions to the provider or issuer responsible for that stage, using the original transaction and refund references. The record does not justify a universal arrival-time promise.

Read proof, advice and settled funds

A payer’s transfer confirmation records what their bank says happened to the instruction. A remittance advice describes the payment and the invoices it is intended to cover. Xero’s remittance advice explanation distinguishes that notice from a bank payment record.

Neither a screenshot nor an advice creates a credit in the retailer’s account. For a bank transfer, match the incoming credit to the expected amount, receiving account and reference. For a provider-collected payment, match the confirmed transaction to its merchant balance and subsequent payout records.

If an advice arrives without the money, leave the invoice awaiting receipt. Ask the payer for the bank’s transaction reference and recorded status. The sending bank investigates the instruction, while the receiving bank or provider checks the incoming record. Confirm the result before releasing goods or asking the customer to send another payment.

Explore this topic

6 guides