Travel Rule Gap and Sub-Threshold Virtual Asset Transfers
BitNow Korea, an FIU-registered virtual asset service provider, receives an incoming transfer of 4.2 BTC (about KRW 380 million) from a Singapore-based exchange for a customer, Mr. Jung. The transfer message includes only the sender's name 'Jung' and the Singapore exchange's name; the beneficiary wallet address is a BitNow-hosted wallet, but the sender's wallet address is missing. BitNow's Travel Rule policy says it must obtain and screen originator and beneficiary information for transfers of KRW 1 million or more, and may reject transfers with missing required data. Mr. Jung has made 14 incoming transfers in the past 30 days, each between KRW 850,000 and KRW 990,000, from three different overseas exchanges, and has withdrawn most funds to two unhosted wallets. He says he is an 'early investor' and the transfers are from 'friends'. His account was opened six months ago with a verified Korean ID; occupation: office worker; declared annual income: KRW 45 million. The compliance officer must decide whether to credit the 4.2 BTC, what to report, and whether to keep the customer.
1. Should BitNow credit the 4.2 BTC transfer? Apply the Travel Rule and the firm's policy.
Read the worked answer
BitNow should not credit the transfer yet. The transfer is about KRW 380 million, well above the KRW 1 million Travel Rule threshold, and the originator wallet address is missing. Under Korea's virtual asset Travel Rule, the VASP must obtain, screen, and retain originator and beneficiary information; a sender name and exchange name alone are not sufficient. BitNow should contact the Singapore exchange to obtain the missing originator data, verify that the exchange is a registered or regulated counterparty, and screen the names and wallet addresses against sanctions and internal risk lists. If the counterparty cannot or will not provide the required information, BitNow should reject or return the transfer under its policy and record the decision. Crediting first and investigating later would weaken the control and could expose BitNow to sanctions and AML breaches. The customer's explanation should be obtained separately, but the Travel Rule decision should be based on the missing data.
2. What suspicious-transaction and customer-risk issues arise from Mr. Jung's 14 sub-threshold transfers and unhosted-wallet withdrawals?
Read the worked answer
The pattern is suspicious. Fourteen transfers just below the KRW 1 million Travel Rule threshold, from three overseas exchanges, followed by withdrawals to unhosted wallets, looks like structuring to avoid information requirements. Mr. Jung's declared income of KRW 45 million does not explain roughly KRW 12–14 million in monthly incoming virtual assets, and his explanation that the funds are from 'friends' is vague. The bank should file an STR with the Korean FIU without delay, covering both the 4.2 BTC transfer and the sub-threshold pattern, and should not tell Mr. Jung that a report was filed. It should also reassess his risk rating as high, obtain source-of-funds and source-of-wealth evidence, identify the unhosted wallets and their owners, and consider whether the accounts are being used as a transit point. Enhanced monitoring should include wallet analytics and counterparty VASP checks.
3. Can BitNow keep Mr. Jung as a customer? What conditions, if any, should apply?
Read the worked answer
BitNow can keep Mr. Jung only if it can complete enhanced due diligence and satisfy itself that the activity is legitimate. The compliance officer should require a credible explanation of the source of the virtual assets, evidence of the 'friends' and their wallet ownership, identification of the unhosted wallets, and confirmation that the overseas exchanges are registered or regulated. If Mr. Jung refuses or gives inconsistent information, BitNow should exit the relationship and consider whether to block further transfers. If he cooperates, BitNow may continue with a high-risk rating, tighter transaction limits, pre-approval for transfers to unhosted wallets, and periodic refresh of his profile. The decision and rationale should be documented and approved by senior compliance. The STR should be filed regardless of whether the customer stays, and no tipping-off should occur.