Table of contents
A Pay by Bank journey can look almost instant: choose a bank, approve the payment and return to the business. Several separate events sit behind that short experience.
The distinction matters. A customer authenticating is not the same as authorising a payment. An authorised instruction is not automatically a completed payment. A status notification is evidence about the payment's state, while reconciliation is the business matching that result to the right sale.
Step 1: the business creates a payment request
The business or its payment provider prepares the amount, payee and reference. The customer should be able to review those details before approving anything. The request may be opened from an online checkout, payment link or QR code.
Step 2: the customer selects their bank
The provider identifies a supported bank and starts the bank-controlled journey. Coverage varies by provider, bank, account type and payment product, so it should be checked against the intended customers.
Step 3: the bank authenticates the customer
The customer proves their identity to their bank, often with the bank's app, passcode or biometric process. Strong Customer Authentication rules can apply when a payer initiates an electronic payment. The bank controls the credentials. The payment initiation provider should not receive the customer's banking password or biometric data.
Step 4: the customer authorises the payment
The customer reviews the amount and payee and chooses whether to proceed. Authentication answered who the bank is dealing with. Authorisation records the customer's decision about this payment.
The consent can still be awaiting authorisation, authorised or rejected. A cancellation, failed authentication or insufficient funds can stop the journey before a payment is executed.
Step 5: the payment is initiated
After valid authorisation, the payment initiation service submits the instruction to the bank. The bank applies its own checks and processing. Pay by Bank describes the initiation journey. The underlying movement of money uses the relevant bank payment infrastructure.
Step 6: payment status is returned
Status information can distinguish processing from execution and failure. The Open Banking Standard includes granular states and reasons so providers can report what is known at each stage. For example, an authorised consent and a status confirming that the payee bank has received the payment are not interchangeable.
The message shown to staff should be tied to the status received. If the provider only knows that the customer authorised the instruction, it should not describe that event as final receipt.
Step 7: funds become available
Many UK account-to-account payments use Faster Payments, which operates around the clock. Pay.UK says payments are usually available almost immediately, although some can take longer. Bank checks, processing exceptions or a receiving-bank issue can affect timing.
Funds availability is different from a provider displaying an earlier success screen. Businesses should understand the provider's exact operational meaning for each confirmation.
Step 8: the business reconciles the result
Reconciliation matches the payment record, amount and reference to the correct order or invoice. It may happen quickly, but it is still an operational step after the payment journey. Good references and system integrations reduce manual work.
What a small business should ask
- Which banks and payment types are supported?
- What exact event changes an order from pending to paid?
- How are delayed, rejected or incomplete payments shown?
- Can staff distinguish customer authorisation from executed payment status?
- How are references passed into bookkeeping or order systems?
Use our guide to Pay by Bank settlement and funds availability for the timing question, or the small-business decision guide for the broader trade-offs.
