Our Support Status for Binance Japan

This page introduces the trade types that can be obtained via Binance Japan file and API.

1．Our Support Status for Binance Japan

*1　Regarding the Conversion History of Some Tokens to USDC  

Sufficient information about which coins were converted to USDC is not provided via API transactions. Therefore, these conversions are not reflected through API integration. Please upload the swap history using a custom file. Please note that any conversions to USDC are not reflected via the API. The dates below are provided as examples. 

・April 21, 2024, 00:00 (UTC) – October 15, 2024, 23:59 (UTC)
・September 2, 2024, 00:00 (UTC) – March 1, 2025, 23:59 (UTC) 
・October 29, 2024, 08:00 (GMT+8) – April 29, 2025, 07:59 (GMT+8) 

*2 Since February 28, 2025, Auto invest (Recurring) have been provided via the "Convert History (Exchange)" API. However, we have confirmed cases where these transactions are not reflected via the API for some customers. If this occurs, please upload the automatic purchase history using the exchange’s file instead. (For details about migration from Auto-Invest to Convert Recurring, please refer to this external site)

*3 Transfers between your own accounts (deposits and withdrawals) do not affect your profit and loss, so they are not needed for the calculation. For this reason, "Import asset transfers (deposits/withdrawals)" in the ledger settings is turned off by default (on by default for users who migrated from Gtax). Turn this setting on only if you want deposits and withdrawals to be reflected in the transaction list (Settings: Import Asset Transfers (Deposits/Withdrawals)). Send fees (crypto withdrawal fees and fiat deposit/withdrawal fees) are reflected regardless of the setting. Fiat (JPY) deposits and withdrawals cannot be retrieved via the API, so please upload the files.

*4 If you have been using the Binance API integration since before 2026/10/08, click "Edit" on the API connection screen, tick the "Binance Pay" endpoint, click "Submit", and then click "Sync" (you do not need to delete and re-register the API key). For the steps, see How to add an additional endpoint to an existing API sync. Due to the exchange API specifications, only roughly the last 18 months of history can be retrieved via the API. Please add earlier history with a custom file as 2.8 Received coins by bonus, campaign, or AirDrop/hard fork.

Transaction Records File:

• We confirmed that the PHB token migration is recorded in the Binance transaction records file. However, since the file does not include information about the new coins received from the migration, it cannot be processed automatically. Therefore, these transactions will not be reflected in cryptact even if the file is uploaded. Please add them manually using a custom file. Redenomination, reverse token split
• For “Buy Crypto with Fiat” transactions, the file does not include price information, so cryptact references its own price data. As a result, the price may not match the actual transaction price. Please edit the price in the transaction history if necessary. Alternatively, these transactions can be imported using the Binance / Buy Crypto History file.

2．Transactions Not Automatically Reflected via API or File

If you can identify the details of your transactions—such as by checking them on the exchange’s interface—please create a Custom File and enter the transactions yourself before uploading it. 
Custom File for any other trades
How to upload a Custom File 

【Related Articles】

How to get an API key for Binance Japan
How to download trade history from Binance Japan