People validating payment details
Built for people checking payee details before sending a transfer, approving payroll, or confirming a saved payment record.
Sort Code Checker
Validate branch context, institution match, and payment-scheme states against the latest published dataset before you act.
Built for people checking payee details before sending a transfer, approving payroll, or confirming a saved payment record.
See the current branch match, institution, location context, and payment scheme states without digging through directories first.
The checker surfaces what the dataset can confirm and labels unknown or limited states clearly instead of guessing.
Jump to value, outcomes, how it works, proof notes, FAQ, and continuation paths.
Why this matters
One wrong digit or one outdated assumption about a branch can turn a routine payment into a delay, a rejection, or a decision you no longer trust.
A sort code can reveal more than a bank name. The current record can also show whether branch metadata is limited and whether payment scheme support is explicitly known or still unknown.
Use the checker when you need fast clarity before you act, then escalate to the bank or payee when the result looks incomplete, unfamiliar, or inconsistent.
Run a check
Enter the code exactly as shown to reveal the current branch record, institution, and payment scheme states.
If the result looks incomplete or unfamiliar, pause and confirm the details with the payee or bank before you continue.
Enter a sort code to reveal the current branch record, bank name, payment scheme states, and source context. Branchless institutions will show without branch counts.
Coverage Map
Hover, focus, or tap a highlighted city to preview the current public coverage here. Open the city hub when you want the full branch, institution, and linked sort code context for that location.
Loading the latest public city coverage snapshot...
Interactive
Enter a UK sort code to preview the normalized format, a live status chip, and the next step for a full lookup.
UK Bank Lookup
Enter a UK sort code
Outcomes
The same sort code can show up in very different contexts. Use the checker with the right expectation for what you are trying to confirm.
Run the lookup first, then compare the result with the payee-supplied bank details. Stop if the institution, branch context, or support state looks wrong or incomplete.
Use the checker when reviewing payroll, finance software, or stored supplier details so copied digits and stale assumptions do not slip through unnoticed.
A limited match, unknown state, or no-result response is a signal to verify directly with the bank or payee rather than forcing confidence from incomplete data.
How it works
The first job is immediate clarity. The second job is helping you decide whether you have enough confidence to move forward or whether you need manual confirmation.
A valid match can show the branch record, bank name, location context, source provider, and payment scheme states from the current dataset.
Proof
The checker is designed to reduce guesswork, not to overstate certainty. The trust boundary below mirrors how result cards are interpreted.
A successful lookup can confirm how the current published dataset maps a sort code to institution, branch metadata, and scheme-state fields when those values are available.
Partial, limited, or unknown means the current source record does not provide enough reliable data for that field. Branch presence without audited linkage is shown as incomplete rather than guessed. It is a trust boundary, not a hidden guess.
Latest successful sync: March 20, 2026, 2:46 pm. This confirms when this site last refreshed its published dataset; it does not guarantee every upstream source changed at that exact time.
Always verify directly with the bank or payee when a payment is high-value, time-sensitive, operationally critical, or when the lookup returns missing, limited, or conflicting details.
Use methodology, FAQ, and support routes when you need deeper evidence, issue reporting, or governance details.
How sort codes are structured
Sort codes are usually written as three pairs of digits. That structure makes it easier to read the number carefully and reduce simple copy mistakes before you rely on the lookup.
The opening digits help identify the institution group or routing family the branch belongs to.
The middle digits narrow the code toward a branch or operational cluster within the bank.
The last digits complete the branch-level identifier used in UK payment routing systems.
FAQ
These answers match the FAQ structured data on this page and are here so the page stays transparent about what the checker does and does not do.
A UK sort code is a six-digit number used by British banks to identify the specific branch or routing record associated with an account. It works alongside the account number rather than replacing it.
The checker shows the latest successful dataset sync available to the site. The current visible timestamp on this page is March 20, 2026, 2:46 pm.
Treat limited, unknown, or missing results as a prompt to verify directly with the payee or bank before you send money. The checker is a validation aid, not final payment authorisation proof.
When the checker shows Authorised by the FCA, it means the current institution record is linked to FCA Register evidence that indicates authorisation rather than only registration.
That is still a trust signal, not permission advice. Review permissions directly on the FCA Register before relying on it for a financial decision.
No. The FCA distinguishes authorised from registered, so this site keeps those labels separate and does not collapse them into a generic approved label.
Final step
Use the checker for this decision, then keep repeat validation habits for future payments that carry risk.
After a successful lookup, use the local save action in the result card to keep a browser-only shortlist of codes you revisit.
Use the sync timestamp to decide when it is worth rerunning a lookup, especially if the previous result was limited or the payment is sensitive.
Use the related pages below when you need broader context than one sort code, including location hubs and institution-level directories.