You send 0.15 BTC from a European exchange to your bitFlyer account, the transaction confirms on-chain in under an hour, and then nothing happens for three days. No error message, no rejection — just a "pending review" label and a support ticket you didn't expect to open.
That gap between on-chain confirmation and account credit is the part most guides skip. Sending crypto to a Japan exchange means routing funds to a platform licensed by the Financial Services Agency (FSA), and licensed platforms carry obligations that offshore exchanges simply don't. Understanding those obligations before you broadcast a transaction is the difference between a same-day credit and a week of back-and-forth.
What Japanese Licensing Actually Requires
Japan treats crypto exchange operation as a licensed financial business. The practical consequence for depositors is that the exchange cannot credit whatever lands in its wallet — it has to know who sent it.
Under Japan's implementation of the FATF travel rule, transfers between exchanges are expected to carry originator information: who sent the funds and on whose behalf. Some platforms transmit this automatically through shared messaging protocols. Others don't, and when the data doesn't arrive, the receiving exchange flags the deposit for manual review rather than crediting it.
bitFlyer, as one of the larger FSA-licensed exchanges in Japan, applies these checks consistently. That isn't the exchange being obstructive — it's the exchange complying with rules it can't opt out of.
Self-custody wallets are the harder case
When you send from a wallet you control, there's no counterparty exchange to attach sender data, so there's nothing for the travel rule to carry. Many Japanese exchanges handle this by requiring you to pre-register the wallet address, or by asking for a written explanation of the funds' origin and your relationship to them.
Do that work before you send. Once the transaction is broadcast, you can't retroactively attach information to it — you can only open a ticket and wait.
The Two Deposit Paths, Compared
| Source | Typical friction | What helps |
|---|---|---|
| Another exchange | Travel-rule data may or may not transmit | Send from a platform that shares originator info |
| Personal wallet | No sender data; address may need pre-registration | Register the address first, keep records of the source of funds |
If you have a choice, sending from a recognized exchange reduces the odds of manual review. If you don't — say the coins have been in cold storage for years — budget extra time and have your documentation ready before the deposit lands.
Network Mistakes Cause More Failed Deposits Than Compliance
Compliance review delays funds. Network errors can destroy them. Before you send anything, check four things:
- Chain, not just ticker. USDT exists on many chains. If the exchange credits one and you sent another, recovery is slow and sometimes impossible.
- Memo or destination tag. Some assets require one. Omit it and the exchange holds your coins with no way to attribute them to your account.
- Minimum deposit thresholds. A small test send can fall below the credited minimum. Check the threshold before you test with a tiny amount.
- Address freshness. Old deposit addresses may still work, but always pull a current one from the interface while logged in.
Before You Hit Send
Verify the receiving details at the source
Copy the deposit address directly from the exchange interface in your logged-in session. Don't reuse an address from a chat history, a note, or a previous transaction. Networks get deprecated and addresses get retired.
Build the paper trail in advance
Screenshot the withdrawal confirmation. Record the sending platform, the amount, the timestamp, and the transaction hash. If a compliance team asks, you'll answer in minutes instead of scrambling through email archives.
Test the route with a small amount
A small first transfer tells you whether the path credits cleanly. Once it does, send the rest. The extra network fee is cheap compared to a stuck deposit.
Frequently asked questions
Can I send crypto to a Japanese exchange from any wallet?
Technically yes, but the deposit may not credit automatically. Japanese exchanges are required to identify the source of incoming funds, so transfers from self-custody or unverified wallets often go to manual review. Pre-registering your wallet address, where the exchange offers that option, speeds things up considerably.
How long does a deposit usually take to credit?
On-chain confirmation is often the fast part — minutes for most networks. The compliance review adds the rest. A clean transfer from a recognized exchange might credit the same day, while one needing manual checks can take several business days.
What happens if I send on the wrong network?
It depends on whether the exchange controls a wallet on that other chain. Sometimes funds can be recovered with a fee and a support request. Often they can't. Verify the network and asset combination before broadcasting, every time.
Do I need to report the transfer for tax purposes?
In Japan, crypto gains are generally taxable, and moving assets between your own accounts isn't itself a disposal — but selling or trading is. Keep records. Consult a Japanese tax professional for your situation rather than relying on forum advice.
Pull a fresh deposit address from bitFlyer now, confirm the network matches the asset you're sending, and make your first transfer a small one. If it credits cleanly, the route works — and the rest can follow.