Sort Code Checker Transparency FAQ

We aim to use reliable public and operational data sources appropriate to each data type.

• Branch-linked data: public Open Banking / Open Data branch endpoints where available.
• Validation support: modulus validation resources used for structural checks.
• Institution-level overlays: public payment-system participant lists where relevant.
• Regulatory evidence: FCA Register evidence where a reliable institution-level match is available.
• Operational metadata: our own sync timestamps, source health checks, and freshness diagnostics.

We do not describe this as a full central industry directory unless we actually license and integrate that data.

The FCA says the Financial Services Register is the official public record of firms and other bodies that are or have been authorised or registered by the FCA or PRA, and the FCA provides API access through its developer portal.

This website helps users research sort-code-related branch and institution information from the sources we currently support. It may display bank or brand names, branch names, city/location details, freshness metadata, and confidence labels that explain how strongly a record is supported by public data.

Some institutions are published through a branchless model when branch evidence is not available. Those pages focus on institution identity and non-branch evidence instead of branch counts.

Some institutions operate without public branch directories or do not publish branch-linked sort-code evidence. When we can verify the institution through regulatory, overlay, validation, or service-point evidence, we publish them through a branchless model.

Branchless listings are deliberate and do not imply missing data. They simply use a different evidence model where branch counts do not apply.

• It does not verify that a specific bank account exists or is active.
• It does not confirm account ownership.
• It does not guarantee that a payment will succeed.
• It does not provide regulated financial advice.
• It does not claim complete UK sort-code coverage unless that is explicitly stated and supported.

Where applicable, we may label records using clear internal confidence categories such as:

• Branch-linked: tied to a branch-level public record.
• Institution-linked: tied to an institution, but not a confirmed branch-level record.
• Branchless: institution-level evidence exists without branch rows, so branch counts do not apply.
• Validation-only: supported only by structural validation logic, with limited descriptive metadata.
• Unknown / insufficient public data: we do not have enough trustworthy public information to say more.

Branch presence means we have branch or location records for an institution in the current dataset.

Audited branch-linked sort codes mean the provider data explicitly exposes a safe, verifiable path from those branch records to specific sort codes.

We do not invent that linkage when the provider payload does not supply it. If linkage is incomplete, the site will say so directly.

Common reasons include:

• the provider branch payload omits explicit sort-code fields;
• linkage fields exist but are not public-safe or auditable;
• the provider endpoint is restricted or temporarily unavailable; or
• the linkage model is still under audit.

This does not necessarily mean the institution has no sort codes. It means we do not yet have audited branch-to-sort-code linkage from the provider.

When this site 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 final permission advice. You should review the permissions and legal entity directly on the FCA Financial Services Register before relying on it for a financial decision.

Registered with the FCA is not the same thing as Authorised by the FCA. Registration can apply to some regulated or supervised activities without meaning the firm has the same permissions as an authorised firm.

That is why this site keeps those labels separate and tells users to review permissions directly on the FCA Register when it matters.

Sometimes. This site may show FCA Register evidence for institutions where a reliable regulatory match is available, but it does not claim that every bank or institution page is already FCA-linked.

FCA status here is a regulatory trust signal, not a substitute for independent verification.

Common reasons include:

• no confident FCA match has been linked yet;
• the public brand name and the legal entity name differ;
• another evidence layer is available before the regulatory layer is complete; or
• the FCA linkage still needs manual review.

A missing site label is not the same thing as a regulatory warning.

Use the FCA Financial Services Register for direct checking.

The FCA also explains when to use the Register and when to use Firm Checker in its consumer checking guidance.

That depends on how the site is configured. A production site may process sort-code lookups in server logs, analytics, cache layers, or security tooling as part of normal website operations. It may also process entered values temporarily to return results. The definitive statement for your site should be in the Privacy Policy.

If you keep logs or analytics, state the retention period and purpose clearly in your Privacy Policy.

Yes, typical categories can include:

• technical data such as browser type, and device metadata,
• usage data such as page views, clicks, and lookup interactions,
• contact data if someone fills in a contact form or emails you directly.

We may refresh source data on a scheduled basis and record operational timestamps such as the last successful sync. However, a sync timestamp does not mean every external source is complete, current, or available at all times.

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.

Use freshness as a risk signal, not as a guarantee. If the payment is sensitive or time-critical, confirm directly with the bank or payee before acting.

Escalate to direct verification when:

• the result is partial, limited, unknown, or missing key fields;
• the payment is high-value, urgent, or operationally critical;
• details conflict with what the payee provided; or
• freshness/status labels indicate stale, blocked, or partial coverage.

No. This site is an information and research tool. If you are making an important payment decision, opening an account, updating mandate details, or resolving a payment issue, you should confirm critical details directly with the relevant bank, PSP, or official service provider.

This website is operated by TechneKaizen. You should also provide easy access to:

Please use the Contact page and include the sort code, the page URL, and what appears to be incorrect. If possible, include a source you believe is more accurate.