Japan Financial Licenses & Registrations (FSA)

Japan's officially licensed financial institutions — banks, securities firms, crypto-asset exchanges, moneylenders, insurers and more — as English-schema JSON with corporate numbers for KYC/KYB matching.

This Actor delivers the Financial Services Agency's (金融庁) official licensee lists (免許・許可・登録等を受けている業者一覧) — the Japanese counterpart of the UK FCA register. Ten license categories, each with registration number, registration date, supervising finance bureau, published head-office address and phone, and the 13-digit corporate number that lets you join records against gBizINFO, the corporate registry, or your own KYC data.

Unofficial tool. Not affiliated with or endorsed by the Financial Services Agency or the Government of Japan. Records are edited/processed data from the FSA licensee lists (出典：金融庁ウェブサイトの「免許・許可・登録等を受けている業者一覧」を編集・加工して作成). fsa.go.jp content is published under 公共データ利用規約（第1.0版）(PDL 1.0), which permits commercial reuse with attribution and a processed-data notice — both embedded in every record.

---

Quick start — verified input

Copy-paste this into the Actor's input (JSON tab) or pass it via API — it was run successfully on 2026-09-02 (every registered crypto-asset exchange in Japan, ~10 seconds):

{
  "licenseCategory": "crypto_exchanges",
  "maxItems": 1000
}

Common input mistakes

Wrong	Right	Why
"licenseCategory": "Banks" / "bank" in the UI	choose banks in the dropdown	Slugs are lower-case; via API bank, crypto, trust, 銀行 … are mapped for you.
"licenseCategory": "all" with the default budget	"licenseCategory": "all", "maxApiRequests": 15	all needs 11 requests; the run stops immediately and tells you the required budget.
"prefecture": "東京都" or "13" (via API)	"prefecture": "Tokyo"	The platform checks the dropdown values (47 English names or empty) before the run starts.
"prefecture": "Osaka-shi"	"prefecture": "Osaka"	Cities are not prefectures; the run stops with a hint.
"maxItems": "500"	"maxItems": 500	Numbers are numbers in JSON — the platform rejects a numeric string before the run starts.

Every invalid value stops the run immediately (before any upstream request) with a message that names the field and lists the valid values. Fields with a fixed list of values are validated by the Apify platform before the run even starts.

Empty results?

A run that finishes with items: 0 and complete: true is not an error. Typical causes: a prefecture where no company of that category has its head office (e.g. trust_companies outside Tokyo), or a category whose registrants are all listed without an address (name withheld as possibly-individual) while a prefecture filter is active. Drop the prefecture filter and re-run.

---

Who is this for?

• KYC / KYB and compliance teams — verify that a Japanese counterparty actually holds the license it claims, by register, number, and date, with a corporate number for entity resolution.
• Fintech and crypto analysts — the crypto-asset exchange register includes each exchange's list of handled crypto assets; monitor listings and new registrants.
• Market entry & partnerships — map who is licensed for what (funds transfer, prepaid instruments, trust business, insurance) before picking partners or competitors to study.

Supported categories

One FSA register per run (or "all"): crypto_exchanges (default) · banks · securities · moneylenders · funds_transfer · electronic_payment_instruments · prepaid_third_party · life_insurance · nonlife_insurance · trust_companies.

Sample output (dataset item)

{
  "category": "crypto_exchanges",
  "categoryJa": "暗号資産交換業者",
  "licenseKind": "registration",
  "name": "○○株式会社",
  "nameWithheld": false,
  "corporateNumber": "1234567890123",
  "registrationNo": "関東財務局長 第00000号",
  "registrationDate": "2019-01-11",
  "authority": "関東財務局",
  "postalCode": "100-0004",
  "address": "東京都千代田区大手町…",
  "prefecture": "東京都",
  "prefectureCode": "13",
  "prefectureEn": "Tokyo",
  "cryptoAssetsHandled": ["BTC", "ETH", "XRP"],
  "asOfDate": "2026-08-21",
  "sourceFileUrl": "https://www.fsa.go.jp/menkyo/menkyoj/kasoutuka.xlsx",
  "source": "金融庁ウェブサイト",
  "sourceUrl": "https://www.fsa.go.jp/menkyo/menkyo.html",
  "license": "公共データ利用規約（第1.0版）PDL1.0 — 編集・加工して作成",
  "retrievedAt": "2026-08-25T09:12:44Z"
}

Upstream quirks are normalized honestly: registration dates arrive as both Excel serials and wareki strings (令和8年3月26日) and become ISO dates; postal codes that lost their leading zero as spreadsheet numbers get it back.

Input reference

{
  "licenseCategory": "securities",
  "prefecture": "Tokyo",
  "maxItems": 500
}

licenseCategory is one of the dropdown slugs (crypto_exchanges, banks, securities, moneylenders, funds_transfer, electronic_payment_instruments, prepaid_third_party, life_insurance, nonlife_insurance, trust_companies) or all — all fetches every supported register (11 polite requests — raise maxApiRequests to 11+; the Actor pre-checks the budget and tells you before spending anything). prefecture is one of the 47 English names (dropdown) or empty for the whole country.

Pricing

Pay per result — see the pricing tab. Most registers are small (the crypto register is a few dozen firms; securities ~2,000), so full-category pulls cost cents.

FAQ

Where does the data come from? From the XLSX licensee lists published on fsa.go.jp (menkyo.html), refreshed roughly monthly per category. Each record carries asOfDate (the register's own reference date) and sourceFileUrl (the exact file it came from).

Is this an official government service? No. Unofficial, independently built and maintained, using officially published PDL 1.0 data with the required attribution embedded in every record.

Why are a few names withheld? Some FSA registers list sole proprietors — private individuals registered, for example, as investment advisers, with what are effectively home addresses and personal phone numbers. This Actor withholds any name it cannot positively identify as a legal entity (name: null, nameWithheld: true) and withholds the contact fields with it. On the live registers at capture time this affected 12 records — all genuine individuals. We accept occasionally over-redacting an unusual foreign entity name; we do not accept publishing a person's home address. Each run's summary reports the withheld count, so nothing is filtered silently.

Is every Japanese moneylender in here? No — the FSA lists cover finance-bureau-registered moneylenders. Moneylenders registered with prefectural governors are not in this register (the FSA page says so itself). Same principle across categories: this Actor returns what the FSA files contain, no more.

What if the FSA changes a file's layout? The parser detects columns by header name and fails loudly with a clear error rather than guessing — you get a stopped run, never silently mis-mapped data.

What about server load? 1 + one request per selected category, ≥1.5 s apart, exponential backoff on 429/5xx, hard request budget, no rate-limit evasion.

Search terms this Actor answers

Japan FSA register · Japan financial license lookup · Japan crypto exchange list · licensed securities firms Japan · Japan moneylender register · KYC Japan financial institutions · FCA register Japan equivalent · Japan banking license data

More Japan public-data Actors by the same developer

• Japan Government Tenders & Awards — tender notices and award results from the kkj.go.jp portal.
• Japan Medical Facilities — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
• Japan Care Facilities — long-term care providers across 35 service types (MHLW open data, CC BY).
• Japan Government Subsidies & Grants — open subsidy calls from the official jGrants API.
• Japan Renewable Energy FIT/FIP Facilities — METI-certified renewable installations, privacy-safe schema.
• Japan Construction & Real-Estate Licenses — licensed contractors and brokers from MLIT's register.
• Japan Trade Statistics — monthly import/export flows by HS code and partner country, from Japan Customs.

---

Data source: 金融庁ウェブサイト（https://www.fsa.go.jp/menkyo/menkyo.html）— PDL 1.0; attribution and processing notice embedded in every record.