How to Check Your Kraken Deposit History?

Accessing the Deposit History Interface

1. Log in to your Kraken account using verified credentials and two-factor authentication.

2. Navigate to the Funding section from the main navigation bar located at the top of the dashboard.

3. Select Deposit History from the dropdown or sidebar menu under Funding tools.

4. Ensure the page loads fully—deposit entries appear in chronological order with the most recent at the top.

5. Confirm that time filters, asset selectors, and status toggles are visible and functional before proceeding.

Understanding Deposit Status Indicators

1. Processing means Kraken has received the blockchain transaction but has not yet credited the funds to your account balance.

2. Confirmed indicates the deposit has met Kraken’s required network confirmations and is now reflected in your available balance.

3. Failed signals a mismatch in address, incorrect memo/tag, or unsupported network used during submission.

4. Cancelled appears when a deposit was manually withdrawn by the user before confirmation or invalidated due to timeout.

5. Pending Review denotes manual verification triggered by unusual volume, new deposit address usage, or KYC-related flags.

Filtering and Exporting Historical Records

1. Use the date range picker to narrow results between specific calendar dates—Kraken retains records for up to 90 days by default.

2. Apply asset filters to isolate deposits for BTC, ETH, XRP, USDT, or any other supported cryptocurrency.

3. Toggle status filters to view only confirmed or failed entries, aiding reconciliation with external wallets or ledgers.

4. Click the Export CSV button to download a timestamped file containing transaction ID, asset, amount, fee, status, and timestamp.

5. Verify exported data integrity by cross-checking at least three random entries against on-screen display values.

Common Deposit Address Misconfigurations

1. Submitting ETH to an ERC-20 deposit address while holding tokens on the BSC network leads to irreversible loss.

2. Omitting the memo field when depositing XRP or Stellar-based assets causes funds to remain uncredited indefinitely.

3. Using legacy Bitcoin addresses (starting with '1') instead of native SegWit (bc1q) addresses may incur higher fees and longer processing times.

4. Copying Kraken deposit addresses from screenshots rather than directly from the interface introduces invisible whitespace or encoding errors.

5. Reusing a single deposit address across multiple transactions violates Kraken’s privacy policy and may trigger automated account review.

Troubleshooting Delayed or Missing Deposits

1. Check the blockchain explorer using the transaction hash provided in your wallet—verify confirmations match Kraken’s stated minimums.

2. Confirm the destination address displayed in Kraken’s deposit history matches exactly what you sent to, including case sensitivity and character count.

3. Inspect whether the deposit occurred during scheduled maintenance windows announced in Kraken’s status blog or Twitter feed.

4. Review your account’s withdrawal/deposit limits—some newly verified tiers restrict incoming volume until additional documentation is submitted.

5. Contact Kraken Support only after validating all technical parameters; include transaction hash, timestamp, asset type, and screenshot of your wallet’s send confirmation.

Frequently Asked Questions

Q: Can I see deposits made before my current verification level was approved?A: Yes. All deposits tied to your account email are visible regardless of tier, though pre-KYC deposits may show limited metadata.

Q: Why does my deposit history show “N/A” for the transaction ID?A: This occurs when fiat deposits are processed via bank wire or SEPA transfer—no blockchain hash exists for such entries.

Q: Is there a way to search deposits by transaction ID directly?A: No. Kraken does not provide a search-by-hash field. Filtering must be done through date, asset, or status first.

Q: Do deposits to sub-accounts appear in the main account’s deposit history?A: No. Each sub-account maintains its own isolated funding history accessible only when logged into that specific sub-account session.