On 10 November 2026 .NET 8 and 9 left support, Python 3.10 went on 1 October and PHP 8.2 follows on 31 December. A method for finding what you run, reading each policy, and acting with months to spare.
Open Banking Payment Statuses: A Guide for UK Businesses
Community contributionBy Jafar Sadhik · community contribution, published under the author's own name
When a payment is safe to fulfil, how pending payments should be handled, and what finance needs for reconciliation
About Open Banking Payment Statuses: A Guide for UK Businesses
Open Banking Payment Statuses: A Guide for UK Businesses
Disclosure: Jafar Sadhik works at Atoa, a UK payment provider. This article is provider-neutral and uses official open banking documentation.
An open banking payment status tells a business how far a bank payment has progressed. It may show that the customer still needs to approve the payment, that the bank has accepted it for processing, that money has left the payer’s account or that the receiving bank has applied the credit.
Those events can happen within seconds, but they are not interchangeable. A customer returning from their banking app does not, by itself, prove that the merchant has received the money. A timeout does not prove that the payment failed. A completed technical status does not mean finance has matched the money to the correct order or invoice.
For businesses accepting open banking payments, the status model controls three practical decisions: what the customer sees, when goods or services are released and when finance can close the transaction. This guide explains how to make those decisions without turning bank and API terminology into a confusing checkout experience.
What Is an Open Banking Payment Status?
An open banking payment status is a time-stamped update describing the current state of a payment consent or payment order. The bank provides status information to the payment initiation service provider, which maps it into a status that the merchant’s systems can use.
The UK Open Banking Standard describes a journey that can include consent creation, customer authorisation, payment submission, bank processing and payment execution. A status can change as the payment moves through those stages.
The wording displayed by a payment provider may differ from the terminology used by the bank. One provider might show “processing” while another uses “pending” for a similar point in the journey. The underlying meaning matters more than the label.
A useful status must answer two questions:
- What has been confirmed?
- What action is safe now?
If a status cannot answer both, the business needs either more information or an exception process.
Which Open Banking Payment Statuses Matter Most?
Businesses normally need a smaller internal status model than the full set of bank and ISO status codes. The provider can map detailed technical updates into a set of operational states that product, support and finance teams understand.
| Business status | What it means | Safe business action |
|---|---|---|
| Awaiting authorisation | The payment request exists, but the customer has not completed bank approval | Keep the order open briefly; do not fulfil |
| Authorised | The customer approved the instruction | Wait for payment submission or processing confirmation |
| Processing | The payment order was submitted, but the required final status is not yet available | Prevent an unnecessary retry and continue checking |
| Completed | The provider received the status defined as sufficient for the business action | Fulfil according to the documented policy |
| Rejected | The bank or payment system returned a definitive rejection | Explain the outcome and offer a safe retry or another method |
| Reconciled | The received payment was matched to the correct order, invoice or account | Close the finance record |
| Exception | The outcome is incomplete, contradictory or overdue | Send the payment to an operational review queue |
These are business states, not a claim that every bank returns the same codes. The Open Banking Standard includes more specific states such as Awaiting Authorisation, Pending, AcceptedSettlementInProcess, AcceptedSettlementCompleted, AcceptedWithoutPosting and AcceptedCreditSettlementCompleted. Availability can vary by payment type and bank implementation.
The merchant should keep the provider’s original status as evidence while also storing the internal business status. That preserves the detail needed for investigation without exposing customers or staff to an unexplained code.
Authorised, Executed, and Received Are Not the Same
An authorised payment means the customer approved the payment instruction. It does not necessarily mean the payment has completed.
An executed payment usually indicates that the payer’s bank has processed the instruction and the funds have progressed into the payment system. Receipt is a later and stronger signal: the receiving bank has received the payment, and in the most complete case has applied the credit to the beneficiary account.
The distinction is visible in the Open Banking Standard:
- Authorised relates to the customer’s approval of the consent.
- Pending indicates that a payment order has been created and further processing is taking place.
- AcceptedSettlementCompleted indicates that processing at the payer’s bank has completed and the payer’s account has been debited.
- AcceptedWithoutPosting indicates that the receiving bank has received the payment but has not yet credited the beneficiary account.
- AcceptedCreditSettlementCompleted indicates that the receiving bank has applied the credit to the beneficiary account.
A business should not assume that every integration will expose every stage. Its provider documentation should identify the success status available for each supported bank and payment type.
When Is an Open Banking Payment Safe to Fulfil?
An open banking payment is safe to fulfil when the merchant has received the status required by its written fulfilment policy. A browser redirect or successful customer authentication is not enough on its own.
The correct threshold depends on what the business is releasing and how costly an incorrect decision would be. Immediate access to a low-value digital service may justify a different rule from dispatching a high-value physical item. An invoice workflow may wait for the payment to be both completed and matched to the invoice reference.
A practical policy has four parts:
- The provider status that triggers fulfilment.
- The products or order values covered by the rule.
- The action taken if the status remains pending.
- The evidence support staff can see if a customer asks what happened.
The policy should come from finance, operations and risk owners rather than being inferred by a developer from the name of an API status.
The customer’s return to the merchant site is useful for resuming the checkout, but it is not the source of truth. The payment record should be updated from signed API responses, provider notifications or a fresh status request.
How Should a Pending Open Banking Payment Be Handled?
A pending open banking payment should remain open while the business checks for a definitive status. The customer should not be encouraged to pay again unless the first attempt is known to have failed or the business has a controlled duplicate-payment process.
Pending is a valid outcome, not a technical embarrassment. It can occur because the bank is still processing the instruction, a status notification is delayed or the merchant lost the response even though the payment continued.
The customer message should answer three questions:
- Has the customer completed their part?
- Should they try again?
- How will they receive the final result?
A useful message is: “We are checking your payment. You do not need to pay again. We will update this order automatically.”
Behind that message, the merchant can wait for a webhook, request the latest status through the provider’s API and move unusually old payments into an exception queue. It should retain the original payment identifier during every check.
A timeout must not automatically become a failed payment. If the merchant changes “unknown” to “failed”, the customer may retry while the first payment is still capable of completing.
How Do Payment Webhooks and Status APIs Work Together?
A payment webhook sends a status update to the merchant when the provider detects a change. A payment status API lets the merchant request the latest known status. Reliable integrations use both.
Webhooks support quick, event-driven updates, but delivery can be delayed or repeated. An event may also arrive before or after the customer returns to the merchant’s checkout. The webhook handler therefore needs to be idempotent: processing the same event twice must not create two orders, receipts or ledger entries.
A sound handler follows this sequence:
- Verify that the notification came from the expected provider.
- Identify the payment using the provider’s payment ID.
- Check whether the event or status was already processed.
- Confirm that the proposed state change is valid.
- Update the canonical payment record.
- Trigger the permitted business action once.
- Record the event and outcome for audit and support.
The status API provides recovery when a notification is missing or the merchant needs to verify a disputed state. Payments that remain processing beyond the expected period can be queried on a schedule rather than left unresolved.
Old events must not move a payment backwards. A completed payment should not return to pending because a delayed notification contains an earlier status.
How Should Open Banking Payment Reconciliation Work?
Open banking payment reconciliation means matching the payment record with the correct sale, order, invoice or customer account. A payment can be technically complete but still be operationally unresolved if finance cannot identify what it paid for.
Each payment record should retain:
- the merchant’s order or invoice reference;
- the provider’s unique payment ID;
- amount and currency;
- the original provider status;
- the merchant’s internal status;
- the time and source of every material update;
- the payer or bank reference supplied for matching;
- any refund, return or duplicate linked to the payment.
The provider payment ID and merchant reference serve different purposes. The provider ID identifies the payment in the payment system. The merchant reference identifies the commercial record. Store both rather than attempting to match on customer name and amount, which can repeat.
Reconciliation can then separate four outcomes:
| Reconciliation outcome | Meaning | Next action |
|---|---|---|
| Exact match | Reference, amount and currency match an open record | Close the record automatically |
| Duplicate payment | More than one completed payment relates to the same record | Review and decide whether to refund |
| Unallocated receipt | Money arrived without a usable commercial reference | Investigate rather than guessing |
| Amount mismatch | The reference matches but the value does not | Keep the balance open and review |
A daily control should compare completed payment records, bank or settlement data and accounting entries. Differences in either direction need investigation. A dashboard total is not enough if it cannot identify the individual transactions behind it.
What Should Customers See at Each Payment Stage?
Customers need plain-language outcomes, not bank status codes. The interface should reflect the merchant’s actual knowledge at that moment.
| Payment stage | Customer message | What the merchant should do |
|---|---|---|
| Awaiting authorisation | “Complete the payment in your banking app.” | Hold the checkout open |
| Processing | “We are checking your payment. Please do not pay again.” | Continue checking the original payment |
| Confirmed | “Your payment is confirmed.” | Fulfil according to policy |
| Rejected | “The payment was not completed.” | Offer a safe retry or another method |
| Exception | “We are checking this payment and will update you.” | Route the record for review |
The same underlying state should appear in customer support tools. If the customer sees “processing” while support sees “failed”, staff may give advice that creates a duplicate payment.
Messages should also explain how the final outcome will arrive. If the order page updates automatically, say so. If the business sends an email, tell the customer to expect it.
How Should Businesses Test Open Banking Payment Statuses?
A successful test payment proves only the simplest route. A useful test plan covers events that arrive late, repeat or appear in an unexpected order.
Test at least these scenarios:
- the customer returns before the final payment update;
- the webhook arrives before the browser redirect;
- the same webhook arrives twice;
- a webhook never arrives and the status API is used;
- the payment stays processing through several checks;
- the customer closes the browser after approving the payment;
- the first attempt is unresolved when the customer starts another;
- a completed payment cannot be matched to an order;
- an older event arrives after a newer status;
- a refund or returned payment requires a separate workflow.
For each scenario, verify five results: the customer message, internal status, fulfilment decision, support view and finance record. An API response can be technically correct while the overall customer or accounting outcome is wrong.
Keep the test evidence and rerun important cases when the provider adds a bank, payment type or API version. Status mappings are business rules and should be treated as maintained configuration, not a one-off coding decision.
What Should You Ask an Open Banking Payment Provider?
A provider should be able to explain its payment status model in operational language. Before integrating, ask:
- Which status should trigger fulfilment for each supported payment type?
- Does the success status differ between banks?
- Which statuses confirm payer debit, receiving-bank acceptance and beneficiary credit?
- How are pending payments resolved?
- Are webhooks retried, signed and uniquely identified?
- Can the merchant query the current status independently?
- How long is payment status history retained?
- Which identifiers support automated reconciliation?
- How are duplicate attempts, refunds and returned payments represented?
- How are changes to status definitions communicated?
The answers should appear in technical documentation and be testable in a sandbox. A sales demonstration of the happy path does not show how the integration behaves when the outcome is uncertain.
Frequently Asked Questions About Open Banking Payment Statuses
Is an Authorised Open Banking Payment the Same as a Paid Order?
No. Authorised means the customer approved the payment instruction. The business still needs the provider status that its fulfilment policy treats as complete.
How Long Can an Open Banking Payment Stay Pending?
There is no single duration that applies to every bank and payment type. The provider should document the expected processing window and the point at which the merchant should query the status or open an exception.
Does AcceptedSettlementCompleted Mean the Payee Has the Money?
Not necessarily. It indicates that settlement processing on the payer’s side has completed and the instruction has moved into execution. AcceptedCreditSettlementCompleted is the stronger signal that the receiving bank has applied the credit, when that status is available.
Can an Open Banking Payment Complete After a Checkout Timeout?
Yes. A timeout can mean that the merchant did not receive the response, not that the bank rejected the payment. The merchant should query the original payment before allowing an unrestricted retry.
What Status Should Mark an Invoice as Paid?
Use the completion status defined with the payment provider, then confirm that the amount, currency and reference match the invoice. Payment completion and invoice reconciliation are related but separate decisions.
Turn Every Payment Status into One Clear Action
The strongest open banking payment flow is not the one with the most status codes. It is the one in which every status leads to a clear and defensible action.
Customer approval should lead to waiting for payment evidence. A processing status should prevent a premature retry. A completion status should trigger the agreed fulfilment rule. Reconciliation should close the financial record. Anything that does not fit those routes should enter a visible exception queue.
When product, support and finance teams use the same status model, customers receive clearer answers and the business is less likely to fulfil too early, collect twice or leave valid payments unmatched.
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
We counted 22 recall records in our 104 car, autonomy and robotics reports: 8 are software or firmware faults, 4 of those name a dealer visit, 1 allows over the air as well, 3 do not say. And 76 of the 104 reports still carry our red note.
Before a person from a buying team reaches your website, a machine has often read it, summarised it and decided how to describe you. A practical look at what that changes for B2B companies, and an audit any team can run in an afternoon.
We classified our 198 security advisories from 22 September to 28 October. 64 described attacks already under way, edge devices led, half of KEV listings came within five days of a fix, and the CVSS score was a weak guide to which ones mattered.
We read our 30 autonomy reports for dated promises. Madrid has three operators naming start dates, most passenger launches are set for 2027, freight is further ahead, and 21 of the 30 reports rest on the company alone.
Microsoft has revised its notes on how Office extends ISO/IEC 29500 57 times since 2009; the core standard text dates from 2016. Why progress should not wait for ballots, and what buyers can ask.
From the UAE on 30 October to Spain in October 2027, 14 e-invoicing deadlines fall in nine countries within a year. Clearance, Peppol and post-audit models need different software; here is what to ask a provider.
A 50,000-token summary costs a quarter of a cent on the cheapest text model on our board and 60 cents on the dearest. We priced five tasks across 38 models, and list the launch prices and premiums that change the bill.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.