Log in to your CoinTracker account to give feedback

Bugs

Report
bugs
to our support team to ensure they’re documented and quickly addressed. Use this board to track the status of issues as they progress through our resolution process.
Failing to sync Bitstamp exchange
Users may experience: Users are reporting failed syncs when importing their Bitstamp exchange. These failed syncs result in new transactions missing and in some cases no transaction history imported at all. Users may see the below state when reviewing their Bitstamp exchange in CoinTracker. As a user when I add or have added my Bitstamp exchange via the API integration on CoinTracker, I expect all of my transactions to be imported into CoinTracker. Users are reporting missing transactions upon sync and ongoing syncs, the behavior is not consistent with a specific currency. The behavior appears to be a result of the type of buy transaction within Bitstamp. Some examples include: Instant, Market and normal buys. Expected behavior: CoinTracker should be importing all transactions from Bitstamp exchange. As a user, what should I do? To reconcile these missing transactions and are identifying the missing transactions pro-actively, users can add those transactions manually, here is a support article on how to add transactions manually. If you believe that you are missing transactions but are not sure which transactions are missing, you can export your transaction history from your exchange via CSV, additionally, you can export your transaction history from CoinTracker for the same exchange ( support article ). Alternatively, users can import their transaction history instead. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Bitstamp, failed sync, missing transactions
·

submitted

Exchange rate for non-USD fiat is based on UTC and not tax optimized
Users may experience: As a user, I am not US based. I have set my account currency to my respective region. I expect that when I import my portfolio into CoinTracker to calculate my taxes that the exchange rates in my calculations respect the time zone I am in. Currently CoinTracker fetches our exchange rate for the date MM/DD/YYYY + X:XX UTC. This means that users in regions with earlier timezones may be fetching outdated or non-ideal rates for their respective markets. As an example, if CoinTracker fetches exchange rates for 09/28/2023 07:30UTC and a user is located in New Zealand, the timestamp in that region would be 09/28/2023 19:30 NZST. The exchange rates that CoinTracker users are fixed meaning we use the same rate for the entire day. As a user, I would expect these rates to be optimized or dynamic to account for the shifting fiat rates. As a user, what should I do? This report is being submitted as a bug to represent exchange rate optimization. Please see add an upvote to this feature request to support custom exchange rates. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: exchange rate, fiat
·

submitted

Crypto to crypto trade transactions are not being imported on Kucoin exchange
Users may experience: As a user who trades and manages my crypto portfolio on Kucoin I expect CoinTracker to import all of my transaction history. Users report seeing their Buys, Sells, Transfers and in some cases their crypto to USDT trades being successfully imported into CoinTracker via their API integration sync for the Kucoin exchange. Users are reporting crypto to crypto trades not importing into CoinTracker causing balance discrepancies and incomplete transaction histories. Crypto to crypto trades include trading non-fiat tokens for other non-fiat tokens. An example of this would be: Trading BTC for ETH, SOL for ETH, ETH for XRP etc. As a user, what should I do? Currently, users will need to manually add missing transactions. Alternatively, if you are a user that is missing a lot of transactions we recommend that you transition your Kucoin exchange to a CSV import instead of the our API integration. Users can format their Kucoin transaction history CSV per this guide and import the CSV into CoinTracker as next step while we improve this integration. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Kucoin, trades, missing transactions
·

submitted

Gain / Loss changes when making a manual edit on a transaction for Coinbase API integration / FTX US CSV import
Users may experience: Users may see their capital gains / loss change slightly when adding a comment to a transaction in Coinbase / FTX US CSV import. This only applies to integrations that support spot pricing which currently only include Coinbase and FTX US CSV import The original gains values a user sees in CoinTracker used the spot pricing we received from Coinbase via our API integration & FTX US CSV import. When a manual change is made, that is any change that would result in a manual tag - in this case a comment, we do not transfer the spot price value of ETH over automatically we infer the price of the asset based on the price history in our (CoinTrackers) database. Expected behavior: Users expect their cost basis to be pulled in based on their exchange price. As a user, what should I do? As a workaround, a user can either, set a custom proceed to attain the expected gain per their CB spot price or avoid adding comments to Coinbase / FTX US CSV import. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: FTX, Coinbase, Spot price, manual edit
·

submitted

Load More