Operating a crypto exchange or payments business in Japan without a functioning correspondent banking relationship is not a compliance gap – it is an existential one. The Financial Services Agency (FSA) regulates crypto-asset exchange service providers under the Payment Services Act, and the Japan Virtual and Crypto Asset Exchange Association (JVCEA) functions as the designated self-regulatory body. Together, they set the conditions under which a licensed operator can access fiat rails. When those rails fail – because a correspondent bank exits the relationship or refuses onboarding entirely – the business stops moving money, and revenue collapses within days. With VASP supervision tightening across the major hubs and Japanese regulators increasing expectations around AML and the Travel Rule (the obligation to pass originator and beneficiary data with a transfer), the window for improvised banking arrangements is closing fast.
This page explains the regulatory basis for correspondent banking access in Japan, the FSA/JVCEA compliance conditions a bank will interrogate before onboarding a crypto entity, the practical process an inbound operator must work through, and the cross-border structuring decisions that determine whether fiat rails remain stable over the long term.
What is the regulated basis for crypto-banking access in Japan?
Correspondent banking access for a crypto entity in Japan depends, first and foremost, on holding the right FSA registration and meeting JVCEA membership conditions. The Payment Services Act establishes the crypto-asset exchange service provider (CAESP) registration requirement. Without that registration, a domestic bank has no regulatory basis on which to onboard the business as a crypto operator – and every major Japanese correspondent bank will ask for the registration certificate before opening an account for crypto-related activity.
The JVCEA sits alongside the FSA as the self-regulatory layer. JVCEA membership is a near-mandatory practical step for any operator seeking banking relationships with Japanese institutions: banks treat JVCEA membership as a proxy for AML/CFT program quality. A registered CAESP that has not yet completed JVCEA onboarding will find correspondent access materially harder to obtain, even if its regulatory status is technically valid.
Under the applicable regime, registered operators are subject to detailed rules on asset segregation, customer asset protection, cybersecurity, and AML/CFT procedures aligned with FATF Recommendation 15 and the Travel Rule. Banks conducting their own due diligence on a prospective crypto client will cross-reference those obligations against the operator's actual policies, procedures and audit history. A mismatch between the licensed perimeter and the operational reality is one of the most common reasons a bank declines or exits a relationship in our cross-border practice.
Why do Japanese correspondent banks exit crypto relationships?
Japanese correspondent banks exit crypto-company relationships primarily because the compliance cost of maintaining them – under FSA supervisory expectations and global AML/CTF guidance – is perceived to outweigh the commercial return. This is not a Japan-specific phenomenon, but the FSA's supervisory posture makes it more acute here than in some other jurisdictions.
The FSA expects banks to conduct enhanced due diligence on financial-institution customers with significant crypto exposure. In practice, that means a bank must understand the crypto operator's customer base, its Travel Rule implementation, its transaction-monitoring stack, and the jurisdictions its users sit in. For a correspondent bank that processes modest crypto volumes, the compliance overhead is substantial.
Several risk factors trigger exits in our experience. The first is a failure to demonstrate Travel Rule compliance – particularly for transfers to or from counterparties outside Japan, where the sunrise problem (the gap between jurisdictions that have implemented the rule and those that have not) creates residual risk that the bank's own compliance team cannot close. The second is concentration: where a significant share of a crypto operator's transaction volume flows through counterparties in higher-risk jurisdictions, the bank's correspondent risk appetite is tested. The third is regulatory uncertainty about the operator's product scope – a CAESP that has added staking, lending or DeFi-adjacent services without a corresponding regulatory analysis presents an ambiguous risk profile.
Operators that address these three vectors proactively – Travel Rule tooling, counterparty due diligence, and a clear regulatory boundary around each product – retain banking relationships at materially higher rates than those that present a bank with a thick PDF and a hope.
What is the process for an inbound operator seeking banking access in Japan?
An inbound operator – a non-Japanese entity seeking either a domestic CAESP registration or a correspondent banking relationship in Japan for a Japan-facing operation – faces a structured sequence of steps. No step can be safely skipped, and the sequencing matters.
The first step is a regulatory perimeter analysis. Before approaching any bank, the operator must establish which activities require FSA registration, which are ancillary, and whether any product requires a separate licence – for example, a type I or type II financial instruments business registration if the operator deals in securities-classified tokens. The FSA's classification framework does not always map cleanly to how operators describe their own products. In our practice, a significant proportion of inbound operators discover at this stage that their product scope is wider than their proposed registration category.
The second step is JVCEA engagement. New CAESP applicants are expected to engage with the JVCEA as part of the application process. The JVCEA's review covers the operator's AML program, its cybersecurity controls, and its customer asset-protection arrangements. The timeline for JVCEA review varies by the completeness of the submission and the complexity of the operator's product set.
The third step – which can begin in parallel with JVCEA engagement but must not precede the regulatory perimeter analysis – is bank outreach. The operative question in any bank meeting is not "will you open an account" but "here is our FSA registration, JVCEA status, AML program, Travel Rule implementation and transaction-monitoring infrastructure – what additional information does your financial-crime team require." A bank that receives a structured compliance package at first contact is far more likely to proceed than one that receives a commercial pitch.
In a recent matter, a Southeast Asian exchange seeking Japan market access approached us after two Japanese banks had declined its account application. The operator held a home-country registration but had not completed JVCEA onboarding and had not documented its Travel Rule implementation for Japan-domiciled counterparties. We restructured the compliance package, coordinated JVCEA engagement, and the operator obtained a banking relationship with a regional Japanese institution within the following quarter. The fiat rail then enabled the operator to pass the FSA's supervisory interview for full CAESP registration.
For CTA purposes: The process above describes the standard path. Your facts – the entity structure, the user base, the existing home-country licences and the banking history – change the analysis significantly. Map your options with a OBOLUS assessment before committing to a Japan entry structure.
How does Travel Rule compliance affect banking access in Japan?
Travel Rule compliance is the single most consequential factor in a Japanese bank's decision to onboard or retain a crypto operator, and the FSA has signalled clearly that enforcement of the applicable provisions is a supervisory priority. Japan was among the first jurisdictions to implement the FATF Travel Rule domestically, and the JVCEA has published detailed guidance on the data-exchange obligations that apply to member firms.
The practical problem for an operator with an international user base is the sunrise problem: a transfer to a VASP domiciled in a jurisdiction that has not yet implemented the Travel Rule cannot be completed with full data exchange, even if the Japanese side is fully compliant. The FSA's current posture treats this as a risk to be managed, not a blanket prohibition, but it expects operators to have a documented approach – including counterparty due diligence on the receiving VASP, a record of the data attempted to be transmitted, and an escalation policy for high-value transfers to non-compliant counterparties.
A bank conducting enhanced due diligence on a CAESP will ask to see that documented approach. If it does not exist, or if it exists on paper but is not operationally embedded in the operator's transaction workflow, the bank's financial-crime team will typically ask for remediation before proceeding. In our experience, operators that implement Travel Rule tooling through a recognised vendor and maintain a counterparty risk register for their top transfer destinations move through bank due diligence significantly faster than those that rely on a policy document alone.
Cross-border complexity intensifies this. A Japan-registered operator whose parent or affiliate entity sits in a jurisdiction with a different Travel Rule implementation standard faces the additional task of demonstrating that the group's data-flow architecture does not create a gap in the Japanese entity's compliance obligations. This is a common structural issue for inbound operators who have tried to apply a single global policy to a Japan-specific regulatory requirement.
What are the asset-segregation and safeguarding requirements that banks assess?
Asset segregation is a foundational requirement under the FSA's CAESP regime, and banks treat compliance with it as a precondition for onboarding – not a tick-box. The Payment Services Act and the associated FSA rules require registered operators to hold customer crypto assets and fiat separately from their own assets, and to maintain records that permit reconciliation on a daily basis.
For fiat, the segregation requirement means that customer funds must be held in a designated trust or deposit account structure that is legally separated from the operator's operating capital. The specific structure – whether a trust bank account, a designated beneficiary account, or another approved form – depends on the operator's registration category and the FSA's current supervisory guidance. A bank asked to hold segregated customer fiat for a CAESP will conduct its own analysis of whether the proposed account structure satisfies this requirement. If the operator cannot explain the structure clearly, the bank will not proceed.
A common mistake in our practice: operators assume that a generic "client money" account opened with a foreign EMI satisfies the FSA's segregation requirement for Japan-domiciled customer funds. It does not. The FSA expects the segregation structure to be visible and auditable within Japan, and a Japanese correspondent bank will confirm this expectation during its own due diligence. Structuring the fiat-rail arrangement around a non-Japanese EMI, without a clear legal analysis of how that structure maps to the FSA's requirements, is one of the fastest ways to lose a banking relationship in Japan.
How does the cross-border tax and banking interaction affect Japan market access?
For a non-Japanese parent group with a Japan-registered operating subsidiary, the tax and banking interaction is a two-sided problem. On one side, the Japan subsidiary must demonstrate to a Japanese bank that its intra-group flows – management fees, technology licensing, intercompany lending – are priced on arm's-length terms and documented in a transfer-pricing study. A bank's financial-crime team will treat unexplained intra-group flows as a potential AML concern if they are large relative to the Japan entity's own-account revenue.
On the other side, the parent entity's jurisdiction affects the Japanese bank's correspondent-bank risk assessment. A parent incorporated in a jurisdiction on the FATF grey list, or one that has recently exited it, will trigger enhanced due diligence that extends to the Japan subsidiary's account application. This is not a disqualifying factor, but it adds process time and requires the operator to provide a detailed group structure chart, beneficial-ownership documentation, and an explanation of why the parent is domiciled where it is.
Consumption tax treatment of crypto-asset transactions in Japan is a separate, complex question that has evolved as the FSA's registration regime matured. The National Tax Agency's current guidance treats the sale of crypto assets as subject to consumption tax in certain circumstances, but the application of those rules to B2B payment flows, stablecoin transactions, and cross-border settlement arrangements requires a jurisdiction-specific analysis. A banking application that does not address the tax treatment of the operator's revenue model can raise questions a bank does not feel equipped to answer, leading to a delay or a referral to a specialist team.
In our cross-border structuring work, we consistently find that operators who address the tax layer as part of their banking preparation – rather than treating it as a separate, later question – move through bank onboarding materially faster. The bank wants to understand the business, not the compliance program in isolation.
If your Japan entry structure raises questions across the banking, tax and licence layers simultaneously, a consolidated analysis is the most efficient path. Map your options and let us identify where the exposure sits before you commit capital.
Which operator profile is best positioned for Japan correspondent banking access?
Not every operator is equally positioned for Japan market access, and the decision to pursue a CAESP registration – and the corresponding banking relationship – should be calibrated to the operator's profile, not the theoretical attractiveness of the market.
Profile A is the established exchange with a home-country FSA-equivalent registration, a mature AML/CFT program, Travel Rule tooling already deployed, and a Japan user base that justifies a dedicated local entity. This operator's path to correspondent banking access is the most predictable: the JVCEA review will be substantive but manageable, and a Japanese regional bank or trust bank is the likely counterparty. The principal risk is timeline – JVCEA and FSA review cycles can extend across many months, and the operator should plan for that.
Profile B is the inbound payments or EMI operator that wants to use a Japan-registered entity as the settlement layer for a broader Asia-Pacific product. This profile is more complex. The operator must demonstrate that the Japan entity's activity is genuinely independent from the group's broader payment flows, that the segregation requirements are met within Japan, and that the Travel Rule implementation extends to the Japan entity's specific counterparty set. The banking relationship is harder to obtain and harder to maintain if the group's structure is not clearly documented.
Profile C is the DeFi or tokenisation platform that has not previously operated under a traditional AML/CFT regime and is seeking Japan market access as part of an institutional-grade expansion. This profile faces the longest path. The FSA's expectations around institutional governance, product classification, and customer asset protection are not easily met by an operator whose prior architecture was designed around permissionless protocols. The JVCEA review will be intensive, and a Japanese bank will want to see a period of stable, auditable operating history before committing to a correspondent relationship.
Across all three profiles, the cross-border reality is the same: Japan market access is not a single licence decision. It is a stack – FSA registration, JVCEA membership, Travel Rule tooling, fiat-rail structure, and a tax and transfer-pricing analysis for any intra-group flows. Operators who plan that stack in advance of their first bank meeting succeed. Operators who approach the bank first and then work backwards through the compliance requirements consistently find the process longer and more expensive.
A common assumption: does one offshore licence cover Japan operations?
A common assumption among operators expanding into Japan is that a registration in a favourable offshore jurisdiction – whether the BVI, Cayman Islands or a MiCA-compliant EU member state – is sufficient to serve Japanese users without a local FSA registration. This assumption is incorrect, and acting on it carries material regulatory and banking risk.
The Payment Services Act applies on the basis of where services are provided and where customers are located, not where the operator is incorporated. An operator actively soliciting or serving Japanese users is within the FSA's supervisory perimeter regardless of its place of incorporation. The FSA has taken action against unregistered operators providing services to Japanese users, and Japanese banks are well aware of this – any account application from a foreign entity that appears to be targeting Japanese users without an FSA registration will be declined, or reported.
The cross-border corollary is equally important. A MiCA-passported CASP operating in the EU has no passport into Japan. Passporting under MiCA extends across the EU/EEA; it has no legal effect in Japan's domestic regulatory perimeter. An operator that has invested in a CASP authorisation in Lithuania or Malta and then assumes it can serve Japan on the basis of that authorisation is compounding a compliance error with a banking risk: any Japanese correspondent bank that identifies the mismatch will exit the relationship.
The correct structure is a Japan-specific analysis: determine whether the operator's activity requires FSA registration, obtain that registration, achieve JVCEA membership, and then approach banking with a compliant local entity. In our practice, we map this against the operator's existing licence stack across other jurisdictions so that the Japan entry does not inadvertently create regulatory conflict in markets the operator already serves.
Related at OBOLUS
- Banking, payments and EMI onboarding – the full practice overview for fiat-rail access across 70+ jurisdictions
- Correspondent banking access in Bermuda – how the Bermuda regime compares for operators structuring Atlantic-facing operations
- EMI licence for crypto firms in Lithuania – the EU gateway option for operators seeking MiCA-compatible fiat rails
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily because the compliance cost of maintaining the relationship – under FSA supervisory expectations, FATF guidance and the bank's own AML policies – exceeds the perceived commercial return. Specific triggers include inadequate Travel Rule documentation, transaction flows to higher-risk jurisdictions, product-scope ambiguity, and a mismatch between the operator's stated business model and its actual transaction patterns. Proactive disclosure and a well-documented compliance program are the most effective retention tools available to an operator.
How can a VASP onboard with an EMI?
A VASP (virtual asset service provider) seeking EMI onboarding must first establish that its home-country registration satisfies the EMI's own regulatory and compliance requirements. Most EMIs active in the crypto sector will require evidence of registration, an AML/CFT policy, Travel Rule tooling documentation, beneficial-ownership disclosure, and an explanation of the operator's user base and transaction profile. Where the VASP operates across multiple jurisdictions, the EMI will also assess whether the group structure creates regulatory gaps that its own compliance team cannot accept.
What does client-money safeguarding require?
Client-money safeguarding requires a licensed operator to hold customer funds in a legally segregated account – typically a designated trust account or a ring-fenced beneficiary structure – that is clearly separated from the operator's own capital. In Japan, the FSA's requirements under the Payment Services Act specify the form that segregation must take for CAESP-registered entities. The operator must maintain daily reconciliation records and be able to demonstrate segregation to both the regulator and any correspondent bank that holds the account.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. We map the licence stack across operating, custody and payment layers before you commit – so that banking, FSA registration and JVCEA onboarding are planned as an integrated sequence, not discovered sequentially as obstacles. Digital assets are the whole of our practice. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in FSA/JVCEA licensing conditions, VASP registration requirements and the compliance conditions for correspondent banking access in Japan and across the Asia-Pacific region.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.