Secure Trust Bank
Secure Trust Bank PLC is an award-winning UK specialist bank, founded in 1952 in the West Midlands and headquartered in Solihull, providing savings accounts and specialist lending to over a million retail and business customers. It is a publicly listed company (London Stock Exchange: STB) rather than a mutual or building society, operating across Retail Finance (V12), Vehicle Finance, Real Estate Finance, Commercial Finance and personal Savings. It is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the PRA (FRN 204550). As a UK ASPSP under PSD2 and the CMA Open Banking framework, its account offerings sit against the Open Banking Implementation Entity (OBIE) standards - a public, unauthenticated Open Data reference surface (ATMs, branches, products) and the FAPI-secured Read/Write APIs for Account and Transaction Information, Payment Initiation and Confirmation of Funds. Secure Trust Bank is a specialist lender and not one of the nine CMA9-mandated banks; as of this review it publishes no public developer portal or bank-branded Open Banking developer host, so the API surfaces below reference the shared OBIE standard specifications the bank's regulated products conform to, not proprietary Secure Trust Bank API contracts.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Secure Trust Bank the way a machine reads it — 39 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Secure Trust Bank scores 39.9/100 (developing), with a separate agent-readiness read of 38/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Secure Trust Bank's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/secure-trust-bank/"
title="Secure Trust Bank on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/secure-trust-bank.svg"
alt="Secure Trust Bank Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/secure-trust-bank/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/secure-trust-bank/"
title="Secure Trust Bank on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/secure-trust-bank/card.svg"
alt="Secure Trust Bank Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Secure Trust Bank
Each block below is one kind of artifact we hold for Secure Trust Bank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 34
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Secure Trust Bank Account Access Consents API
The Account Access Consents API from Secure Trust Bank — 2 operation(s) for account access consents.
Secure Trust Bank Accounts API
The Accounts API from Secure Trust Bank — 2 operation(s) for accounts.
Secure Trust Bank ATM API
Endpoint for getting ATM data
Secure Trust Bank Balances API
The Balances API from Secure Trust Bank — 2 operation(s) for balances.
Secure Trust Bank BCA API
Endpoint for getting Business Current Account data
Secure Trust Bank Beneficiaries API
The Beneficiaries API from Secure Trust Bank — 2 operation(s) for beneficiaries.
Secure Trust Bank Branch API
Endpoint for getting Branch data
Secure Trust Bank CCC API
Endpoint for getting Commercial Credit Card data
Secure Trust Bank Direct Debits API
The Direct Debits API from Secure Trust Bank — 2 operation(s) for direct debits.
Secure Trust Bank Domestic Payment Consents API
The Domestic Payment Consents API from Secure Trust Bank — 3 operation(s) for domestic payment consents.
Secure Trust Bank Domestic Payments API
The Domestic Payments API from Secure Trust Bank — 3 operation(s) for domestic payments.
Secure Trust Bank Domestic Scheduled Payment Consents API
The Domestic Scheduled Payment Consents API from Secure Trust Bank — 2 operation(s) for domestic scheduled payment consents.
Secure Trust Bank Domestic Scheduled Payments API
The Domestic Scheduled Payments API from Secure Trust Bank — 3 operation(s) for domestic scheduled payments.
Secure Trust Bank Domestic Standing Order Consents API
The Domestic Standing Order Consents API from Secure Trust Bank — 2 operation(s) for domestic standing order consents.
Secure Trust Bank Domestic Standing Orders API
The Domestic Standing Orders API from Secure Trust Bank — 3 operation(s) for domestic standing orders.
Secure Trust Bank File Payment Consents API
The File Payment Consents API from Secure Trust Bank — 3 operation(s) for file payment consents.
Secure Trust Bank File Payments API
The File Payments API from Secure Trust Bank — 4 operation(s) for file payments.
Secure Trust Bank Funds Confirmation Consents API
The Funds Confirmation Consents API from Secure Trust Bank — 2 operation(s) for funds confirmation consents.
Secure Trust Bank Funds Confirmations API
The Funds Confirmations API from Secure Trust Bank — 1 operation(s) for funds confirmations.
Secure Trust Bank International Payment Consents API
The International Payment Consents API from Secure Trust Bank — 3 operation(s) for international payment consents.
Secure Trust Bank International Payments API
The International Payments API from Secure Trust Bank — 3 operation(s) for international payments.
Secure Trust Bank International Scheduled Payments API
The International Scheduled Payments API from Secure Trust Bank — 3 operation(s) for international scheduled payments.
Secure Trust Bank International Scheduled Payments Consents API
The International Scheduled Payments Consents API from Secure Trust Bank — 3 operation(s) for international scheduled payments consents.
Secure Trust Bank International Standing Orders API
The International Standing Orders API from Secure Trust Bank — 3 operation(s) for international standing orders.
Secure Trust Bank International Standing Orders Consents API
The International Standing Orders Consents API from Secure Trust Bank — 2 operation(s) for international standing orders consents.
Secure Trust Bank Offers API
The Offers API from Secure Trust Bank — 2 operation(s) for offers.
Secure Trust Bank Parties API
The Parties API from Secure Trust Bank — 3 operation(s) for parties.
Secure Trust Bank PCA API
Endpoint for getting Personal Current Account data
Secure Trust Bank Products API
The Products API from Secure Trust Bank — 2 operation(s) for products.
Secure Trust Bank Scheduled Payments API
The Scheduled Payments API from Secure Trust Bank — 2 operation(s) for scheduled payments.
Secure Trust Bank SME API
Endpoint for getting Unsecured SME Loan data
Secure Trust Bank Standing Orders API
The Standing Orders API from Secure Trust Bank — 2 operation(s) for standing orders.
Secure Trust Bank Statements API
The Statements API from Secure Trust Bank — 5 operation(s) for statements.
Secure Trust Bank Transactions API
The Transactions API from Secure Trust Bank — 2 operation(s) for transactions.
Scroll within the panel for all 34 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Open Data API
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Secure Trust Bank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/secure-trust-bank · machine-readable index on apis.io
This is an independent, third-party profile of Secure Trust Bank, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.