This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Chase UK is the digital retail bank operated in the United Kingdom by J.P. Morgan Europe Limited, a wholly owned subsidiary of JPMorgan Chase & Co. that launched the Chase consumer brand in the UK in September 2021. It is an app-only challenger bank with no physical branches or ATM estate, authorised and regulated by the FCA and PRA. As a UK account provider (ASPSP) it operates a dedicated Open Banking interface conformant to the OBIE Read/Write API Standard, exposing Account Information (AIS), Payment Initiation (PIS), and Confirmation of Funds (CBPII) services to FCA-authorised third-party providers.
APIs.json: https://raw.githubusercontent.com/api-evangelist/chase-uk/refs/heads/main/apis.yml
- Financial Services
- Banking
- Open Banking
- PSD2
- OBIE
- United Kingdom
- Payments
- Account Information
- Challenger Bank
- Fintech
- Created: 2026-07-23
- Modified: 2026-07-23
Chase UK's Account Information Service (AIS) dedicated interface, conformant to the OBIE Read/Write API Standard, letting FCA-authorised AISPs retrieve a consenting customer's account, balance, transaction, beneficiary, standing order, direct debit, and statement data. Access is gated behind developer onboarding and secured with FAPI OAuth2/OIDC, PSD2 SCA, and mutual-TLS.
- Account Information
- AISP
- Open Banking
- OpenAPI — shared OBIE Read/Write standard v4.0.1 (not a Chase-proprietary contract)
- Documentation
- Info for TPPs
- Developer Portal
Chase UK's Payment Initiation Service (PIS) dedicated interface, conformant to the OBIE Read/Write API Standard, enabling FCA-authorised PISPs to create single immediate payments, future-dated payments, and standing orders to UK accounts on behalf of a consenting customer. Access is gated behind developer onboarding and secured with FAPI OAuth2/OIDC, PSD2 SCA, and mutual-TLS.
- Payment Initiation
- PISP
- Payments
- OpenAPI — shared OBIE Read/Write standard v4.0.1 (not a Chase-proprietary contract)
- Documentation
- Info for TPPs
- Developer Portal
Chase UK's Confirmation of Funds (CBPII) dedicated interface, conformant to the OBIE Read/Write API Standard, allowing an FCA-authorised card-based payment instrument issuer to check whether a specified amount is available on a consenting customer's account. Access is gated behind developer onboarding and secured with FAPI OAuth2/OIDC, PSD2 SCA, and mutual-TLS.
- Confirmation of Funds
- CBPII
- Open Banking
- OpenAPI — shared OBIE Read/Write standard v4.0.1 (not a Chase-proprietary contract)
- Documentation
- Info for TPPs
- Developer Portal
- Website
- Developer Portal
- Documentation
- Getting Started (Info for TPPs)
- Support
- Terms of Service
- Privacy Policy
Chase UK is app-only with no branch or ATM estate, so it does not publish OBIE Open Data APIs (ATMs / Branches / Personal & Business Current Accounts). Its only public API posture is the FAPI-secured OBIE Read/Write dedicated interface, reachable through the sandbox developer portal after FCA-authorised onboarding. TPP enquiries: open.banking@chase.com.
FN: Kin Lane Email: kin@apievangelist.com