Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix/ETD-1130 - added LedgerType SALE for tx - spend and received #4824

Conversation

martinkyov
Copy link
Contributor

https://support.kraken.com/hc/en-us/articles/360001169383-How-to-interpret-Ledger-history-fields

"sale" = this shows only as a filter option when viewing your Ledger history while signed in to your account, it is not shown in history exports. "Sale" is a filter that brings up all "Spend" and "Receive" entries from orders placed via the new Kraken app or Buy Crypto button.

https://support.kraken.com/hc/en-us/articles/360001169383-How-to-interpret-Ledger-history-fields

"sale" = this shows only as a filter option when viewing your Ledger history while signed in to your account, it is not shown in history exports. "Sale" is a filter that brings up all "Spend" and "Receive" entries from orders placed via the new Kraken app or Buy Crypto button.
https://support.kraken.com/hc/en-us/articles/360001169383-How-to-interpret-Ledger-history-fields

spend" = shown for transactions made via the Buy Crypto button or new Kraken app, this indicates the amount of the asset being debited from the account
"receive" = shown for transactions made via the Buy Crypto button or new Kraken app, this indicates the amount of the asset being credited to the account.
@timmolter timmolter merged commit d84d219 into knowm:develop Apr 20, 2024
1 check passed
duplessisc pushed a commit to duplessisc/XChange that referenced this pull request May 29, 2024
…ors-kraken-api-misident

bugfix/ETD-1130 - added LedgerType SALE for tx - spend and received
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants