Regional bank API and digital partnership route in Japan
ConfidenceLikelyUpdated2026-07-29Review by2026-10-27Sources7Machine-translatedOriginal (JA)
On this page
Overview
Regional-bank digital partnership in Japan is not just “a bank app.” It is split into electronic payment agency API contracts, shared API platforms, bank-owned apps, accounting / treasury integrations, BaaS-style bank partnerships, and account-direct payment rails.
Use this page with bank API route, bank API incident controls, BaaS Japan landscape, regional bank consolidation, account-to-account payments, and legal / financial licenses.
Route Map
| Route | Bank-side actor | Partner type | API / service function | Regulatory hook |
|---|---|---|---|---|
| Registered electronic payment agency API | Regional bank | Accounting, PFM, treasury, payment, cash-management app | Balance, transaction history, transfer instruction depending on scope. | FSA electronic payment agency registration and bank API contract disclosure. |
| Shared regional API platform | Regional-bank alliance / system subsidiary | Common API platform and system vendor | Same-spec or shared connection layer for multiple banks. | JBA open API contract / principles plus individual bank policy. |
| Official regional-bank app | Regional bank and app operator | Bank app, group fintech subsidiary, regional-service platform | Account view, transfers, points, debit, savings, local-commerce features. | Bank license, outsourcing, electronic payment agency / bank agency route if applicable. |
| BaaS / embedded service | Bank or digital-bank partner | Non-bank platform or fintech | Account / payment / identity / balance UX embedded in another service. | Bank license plus API / agency / intermediary contracts. |
| Account-direct payment | Regional bank plus payment network | Bank Pay / J-Debit / account-direct merchant route | Merchant payment from bank account. | A2A route and merchant acquiring controls. |
Sources: the route labels synthesize the FSA electronic-payment-agency register, JBA Open API materials, and bank-specific disclosures. A route name does not prove that every participant holds the same registration or supports the same API scope. ^[Sources: https://www.fsa.go.jp/menkyo/menkyoj/dendai.pdf; https://www.zenginkyo.or.jp/abstract/council/openapi/; https://www.boy.co.jp/renkei/api.html.]
Regional Examples
| Example | Public relevance |
|---|---|
| Yokohama Bank API disclosure | Publicly lists electronic payment agency API contract route and user-compensation language. |
| TSUBASA FinTech common platform | Shows regional-bank alliance approach to shared API / digital-service platform infrastructure. |
| Chiba Bank / TSUBASA participants | Illustrates how regional banks can pool technology while remaining separate banking entities. |
| Fukuoka FG / iBank style route | Shows regional bank group app / platform strategy beyond a plain account-view app. |
| freee and Money Forward | Common accounting / PFM integration anchors for regional bank API analysis. |
Control Questions
| Question | Public relevance |
|---|---|
| Who has electronic payment agency registration? | API access is not only a bank’s technical choice; it is a registered-actor route. |
| Is the API read-only or instruction-capable? | Account-information and payment-instruction risks differ. |
| Is the connection direct to one bank or via a shared platform? | Operational concentration and vendor dependency differ. |
| Does the bank outsource API system operation? | Outsourcing and incident responsibility matter. |
| Is the app bank-owned, bank-partnered, or third-party? | Legal entity and user-compensation path can differ from UX branding. |
| Does the flow create wallet balance or only bank-account movement? | Payment Services Act classification can change. |
Sources: these are control questions. Registration is checked in the current FSA registry; API scope and responsibility are checked in the relevant bank/partner contract disclosure. ^[Sources: https://www.fsa.go.jp/menkyo/menkyoj/dendai.pdf; https://www.zenginkyo.or.jp/fileadmin/res/abstract/council/openapi/openapi_text_1.pdf.]
JapanFG Relevance
- Yokohama Bank, Chiba Bank, Chugoku Bank, Tsukuba Bank, and TSUBASA-linked regional banks are useful API-platform anchors.
- Fukuoka FG and Minna Bank BaaS model show a more platform-native regional-bank direction.
- freee and Money Forward is cross-linked when account data / accounting integration is the core use case.
- Bank API incident controls be used before treating bank API integration as a low-risk convenience feature.
Research Checklist
- Identify the bank, partner, API function, and service brand.
- Check the FSA electronic payment agency registry and the bank’s API disclosure page.
- Distinguish read-only information APIs from update / transfer-instruction APIs.
- Check whether the system is a bank-specific API or shared alliance / vendor platform.
- Link payment functions to A2A payment route and wallet functions to funds transfer vs prepaid boundary.
Related
- INDEX
- japan-bank-api-payment-agency-route
- japan-bank-api-incident-and-fraud-control
- baas-japan-landscape
- minna-bank-baas-model
- regional-bank-consolidation-pattern
- account-to-account-payment-japan
- INDEX
- yokohama-bank
- chiba-bank
- FinWiki index
Sources
- FSA: electronic payment agency registry.
- Japanese Bankers Association: Open API council and model API contract.
- Bank of Yokohama: API / electronic payment agency collaboration disclosure.
- Bank of Japan workshop material referencing TSUBASA FinTech common platform.
- Tsukuba Bank: TSUBASA FinTech common platform / app renewal release.
#banking#regional-bank#bank-api#digital-partnership#electronic-payment-agency#fintech
Discovery
Keep reading
Read next
- Japan rokin bank registryThis registry index captures the FSA public license list for Japan's labor-bank system: Rokinren plus 13 licensed rokin banks. It maps the labor-union / worker-finance lane of cooperative ba...
- Japan shinkin bank registryThis registry index captures the FSA public license list for Japan's shinkin-bank system: Shinkin Central Bank plus 254 licensed shinkin banks. It is a registry route, not a plan to create h...
- Sony Bank operating profile (ソニー銀行)Sources: the identity, ownership route, and license category are supported by Sony Bank's company profile, Sony's official partial-spin-off record, and the FSA workbook. The spin-off changed...
Links here
- GMO Aozora Net Bank operating profile (GMO あおぞらネット銀行)GMO あおぞらネット銀行 (GMO Aozora Net Bank, Ltd.) is a joint venture of Aozora Bank and the GMO group with a stated technology-bank and corporate-service focus. Its official company outline records...
- Japan BaaS operating modelsJapan BaaS can be described by customer ownership, deposit-contract holder, UI controller, API provider, KYC / AML / fraud-monitoring responsibility, and license stack. A partner-branded app...
- Japan net bank competition mapJapan net-bank competition includes several public operating models: ecosystem retail banks, full-banking BaaS / white-label banks, SME / corporate API banks, securities / asset-formation ba...
- Japan net bank deposit & feature matrix 2026Japan's online-bank market is not one homogeneous category. Operators differ by group ownership, direct-versus-partner distribution, product scope, and public disclosure format. This page th...
- Japan regional bank M&A consolidation family-tree matrixPost-1990 regional-bank consolidation in Japan has produced a layered map of bank holding companies, each combining one or more first-regional ("地銀") and/or second-regional ("第二地銀") predeces...