Kraken Source of Funds Request:
how to respond

Kraken's Source of Funds process is part of its Customer Due Diligence (CDD) and Enhanced Due Diligence (EDD) programs — which Kraken documents publicly in detail on its support pages at support.kraken.com. Unlike exchanges that hide behind vague "compliance review" language, Kraken actually tells you what program triggered your hold. The notifications you will see include:

• Withdrawal hold notice: "Withdrawal hold — your withdrawal is currently on hold as part of our security review." — Kraken places a hold on withdrawals (not the entire account) while conducting the review. Trading and deposits may still function, but you cannot withdraw until the review is complete.
• Chatbot "I can't withdraw" response: When you contact Kraken support about the hold, the chatbot responds with "I can't withdraw" — a known phrase in the Kraken support system that triggers a compliance workflow. The chatbot cannot resolve SoF issues; it routes you to the support ticket system.
• CDD/EDD email request: An email from Kraken support requesting Source of Funds or Source of Wealth documentation. Kraken's emails are more specific than most exchanges — they typically reference the specific program (CDD or EDD) and may indicate the general reason for the review (e.g., "transaction volume threshold," "high-risk jurisdiction," "sanctions screening match").
• Account tier restriction: Kraken's features are tied to verification tiers (Starter, Express, Intermediate, Pro). A SoF review may downgrade your effective tier, removing access to specific features (e.g., fiat deposits/withdrawals at the Intermediate level) until the review is complete.

Kraken's compliance triggers are documented on its support pages and include: incomplete verification at your current tier level, withdrawal holds triggered by security patterns (first-time purchases, password changes, ACH deposits, new withdrawal addresses), suspicious activity detected through ongoing monitoring, sanctions screening matches (OFAC SDN list, PEPs, watchlists), and high-risk jurisdiction or industry associations. Kraken's CIP and ongoing monitoring programs run continuously — a review can be triggered months or years after account opening if new activity crosses a threshold.

Kraken operates through two primary entities: Payward Global (US and non-EU operations) and Payward Europe (EU operations, regulated by the Central Bank of Ireland as a Virtual Asset Service Provider). For EU users, Kraken is subject to: the Central Bank of Ireland's VASP regulations, EU AMLD6, MiCA, and FATF Travel Rule obligations. For US users, Kraken is subject to FinCEN MSB regulations, state money transmitter licenses, and OFAC sanctions compliance.

Kraken's AML-CFT Program is publicly documented and includes specific sections on: Customer Identification Program (CIP), Customer Due Diligence (CDD), Enhanced Due Diligence (EDD), ongoing monitoring, sanctions screening, and suspicious activity reporting. The EDD section is particularly relevant to Source of Funds cases — it is triggered for higher-risk customers, larger transaction volumes, customers from high-risk jurisdictions, and complex or unusual transaction patterns. When EDD is triggered, Kraken requires both Source of Funds (where did the specific funds come from) and Source of Wealth (how did you accumulate your total wealth) documentation.

Kraken's documented hold periods are a significant advantage over other exchanges — you know the maximum wait time in most cases. However, for compliance-related freezes (as opposed to security holds), Kraken does not publish a timeline, and these cases can extend beyond the standard hold periods. We use the documented framework as a baseline and escalate when Kraken exceeds its own published standards.

Kraken's documentation requirements are publicly documented and more structured than most exchanges. Based on the support pages and our case experience:

• Valid government-issued ID: Passport (preferred), national ID card, or driver's license. Kraken's verification is tiered — Starter requires basic ID, Intermediate requires full ID verification, Pro requires proof of address and potentially additional documentation. A SoF review may require upgrading your tier or re-verifying at your current tier.
• Proof of address statement: Bank statement, utility bill, or government letter showing your name and address. Kraken specifies "statement" — it wants an actual periodic statement (monthly or quarterly), not a one-time letter. Must be dated within the last 3 months.
• Source of Wealth documentation (EDD): When Kraken triggers Enhanced Due Diligence, it requests Source of Wealth — not just Source of Funds. SoW documentation includes:
  
  • Tax returns (2-3 years) showing declared income
  • Business financials if you own or are employed by a business
  • Investment portfolio statements
  • Real estate ownership documentation
  • Inheritance or gift documentation for wealth not from employment
  • A personal financial statement summarizing your assets and liabilities
• Source of Funds documentation (transaction-specific): Documentation proving where the specific funds deposited to Kraken came from:
  
  • Bank deposits: Bank statements showing the source of funds transferred to Kraken, traced back to their origin (salary, investment sale, etc.)
  • Crypto deposits: Withdrawal records from the source exchange showing the date, amount, and destination address matching your Kraken deposit
  • Large deposits: For deposits above Kraken's internal thresholds (which vary by jurisdiction), Kraken may trace funds back through multiple hops — if money moved through several accounts before reaching Kraken, each hop may need documentation
• Sanctions screening documentation: If the SoF review was triggered by a sanctions screening match (false positive on OFAC SDN list, PEP designation, or watchlist match), Kraken requires documentation proving you are not the sanctioned individual — this may include additional ID, proof of residence in a non-sanctioned jurisdiction, or a sworn declaration of identity.

Kraken is unique among major exchanges in publishing specific hold periods for different types of restrictions. These are documented on support.kraken.com:

• Standard verification (tier upgrade): Less than 30 minutes for automated verification. Manual verification of additional documents takes longer.
• First-time card purchase hold: 72 hours. Kraken places a hold on withdrawals after the first card purchase to prevent fraud. This is a security hold, not a compliance review, and lifts automatically.
• ACH Plaid purchases hold: 7 days. After an ACH deposit via Plaid, withdrawals are held for 7 days to ensure the transaction clears.
• PayPal purchases hold: 72 hours.
• Password change hold: 24 hours for new withdrawal addresses. After a password change, withdrawals to new addresses are held for 24 hours as a security measure.
• Compliance freeze (CDD/EDD review): No published timeline. This is the hold relevant to Source of Funds reviews. Unlike the security holds above, a compliance freeze does not auto-resolve — it remains until Kraken's compliance team makes a determination. Based on our experience, standard CDD reviews take 5-10 business days after document submission, and EDD reviews take 2-4 weeks. Complex cases (sanctions screening, cross-border, high volume) can extend to 6-8 weeks.

If Kraken's compliance review exceeds these timelines significantly, we escalate through the Central Bank of Ireland (for EU users) or FinCEN (for US users), referencing Kraken's own published AML-CFT program standards to argue that the review is exceeding reasonable bounds.

Specific mistakes we see with Kraken Source of Funds cases:

• Confusing security holds with compliance freezes: Kraken has multiple hold types — the 72-hour card purchase hold, 7-day ACH hold, and 24-hour password change hold are all security measures that auto-resolve. A compliance freeze from CDD/EDD does not auto-resolve. If you wait 72 hours expecting a compliance freeze to lift, you have wasted 72 hours. We can identify which type of hold you are under based on the notification language.
• Using the chatbot for compliance issues: Kraken's chatbot is designed for basic support queries and will respond with "I can't withdraw" for any withdrawal-related question. It cannot resolve compliance freezes, cannot access your compliance case, and cannot escalate. All compliance communication must go through the support ticket system at support.kraken.com.
• Submitting Source of Funds when Source of Wealth was requested: Kraken distinguishes between SoF (where did these specific funds come from) and SoW (how did you accumulate your total wealth). If Kraken requested SoW under EDD and you submit only SoF documentation, the review will not resolve — Kraken will keep the freeze and request the missing SoW. We ensure the correct type of documentation is submitted from the start.
• Not checking the Compliance Hub references: Kraken's support pages reference specific Compliance Hub articles that detail the requirements. Many users miss these references and submit generic documentation that does not meet Kraken's specific standards. We always reference the relevant Compliance Hub article in our submissions.
• Assuming EU regulations don't apply because Kraken is "American": For EU users, Kraken operates through Payward Europe (Central Bank of Ireland regulated). EU law — AMLD6, MiCA, GDPR — applies to your account, not US law. This matters for data access rights (GDPR Article 15), complaint procedures (Central Bank of Ireland), and the legal basis for Kraken's actions. We leverage EU regulatory rights in our Kraken cases for EU-based users.