"viban_purchase" Transactions Not Importing from the Crypto.com csv
complete
What is the issue?
When importing Crypto.com CSV files, transactions labeled as "viban_purchase" are not being recognized or imported. This causes incorrect balances and cost basis calculations for affected users.
Who is affected?
Users who purchased crypto using fiat on Crypto.com and are relying on CSV imports.
What is the workaround?
Users may need to manually enter these transactions or change the CSV to reflect another supported purchase type.
Keywords: Crypto.com, viban_purchase, CSV import issue, missing transactions, cost basis error
Log In
Sarah T. - CoinTracker
marked this post as
complete
This issue has been resolved.
You can now upload a fresh CSV with viban-purchase type transactions. Please be cautious not to duplicate existing CSVs.
If you are still noticing the reported behavior,
reach out to the CoinTracker support team directly
.Support Ops Tools
marked this post as
acknowledged