# Why a wire for a crypto purchase gets flagged or delayed Why banks flag or delay wires tied to crypto purchases, what triggers the review, and how onchain settlement sidesteps the friction. --- ## Why a wire for a crypto purchase gets flagged or delayed Every OTC broker, dealer's rep, or closing advisor who has structured a crypto purchase with fiat funding has run into this: the wire goes out, and then nothing happens. Or worse — something happens, but that something is a compliance hold, a request for documentation from a bank you've never dealt with, or a flat rejection with a reason code that tells you nothing useful. The deal is paused, your counterparty is waiting, and the clock is running. This is not a rare edge case. It is the predictable consequence of sending fiat down rails that were not built to accommodate a destination the bank's risk system classifies as inherently suspicious. This article breaks down exactly why it happens, where in the chain it happens, and what it means for your workflow as the person responsible for getting funds to the right place when a deal closes. ## The bank's core problem with crypto-linked transfers To understand the flags, you need to understand how a bank's compliance infrastructure reads the transaction. The underlying issue is not crypto itself. It is how crypto-linked value enters the traditional banking system and how that movement is interpreted by modern compliance infrastructure. A bank's automated systems are built around pattern recognition. They compare each transaction against what is "normal" for that account, for that transaction type, and for the stated purpose. When the destination — or even the stated purpose on the wire instructions — signals a crypto exchange or OTC desk, several of those pattern-recognition rules trigger simultaneously. Banks have become far more cautious about transfers involving cryptocurrency platforms. Many institutions treat these transactions as high-risk because of the volume of fraud tied to crypto investment scams. The compliance officer at the originating bank is not evaluating whether your specific deal is legitimate. They are running the transaction through a framework built on population-level statistics, and that population includes a disproportionate share of fraud cases, pig-butchering schemes, and money-laundering attempts. Your clean, documented OTC purchase lands in the same queue. Banks now rely heavily on automated risk scoring systems. These systems analyze transaction patterns, payment rails, counterparties, jurisdictions, and intermediary exposure. When crypto funds move into the banking system without a clearly defined structure, those systems default to caution. The key phrase there is "clearly defined structure." What triggers a hold is not usually the dollar amount alone — it is the absence of a recognizable structural narrative in the transaction metadata. A wire with a memo field that reads "purchase of digital assets" or "crypto acquisition" gives the system exactly what it needs to escalate. Most crypto-related bank freezes are structural rather than punitive. They are triggered when a transaction cannot be clearly categorized or explained within standard banking logic. Understanding this reframes the entire problem. The bank is not accusing your client of wrongdoing. It is surfacing the transaction for human review because its automated systems cannot categorize it cleanly enough to pass it through. The result looks identical from where you're standing — a delayed or blocked wire — but the remediation path is different depending on where in the chain the hold occurred. ## Where the wire actually gets stopped There are at least three distinct points where a crypto-related wire can be held or rejected, and each one requires a different response. ### The originating bank This is the most common point of failure. The client's own bank either blocks the transfer outright at the point of initiation, or flags it for internal review before releasing the funds. Some banks block certain crypto-related transfers entirely. If you're funding a crypto account, expect slower movement of money. Some major retail banks have standing policies that restrict transfers to known cryptocurrency businesses; their systems have the beneficiary institution's routing details mapped against a list of crypto-adjacent counterparties, and the block fires automatically regardless of the transaction amount or the client's account history. The more nuanced version is the behavioral flag. A client who has never wired seven figures out of their account before presents an anomalous transaction regardless of the destination. There are a variety of legitimate transactions that could raise a red flag simply because they are inconsistent with an accountholder's normal account activity. For example, a real estate investment, the receipt of an inheritance, or a gift, may cause an account to have a significant credit or debit that would be inconsistent with typical account activity. Replace "real estate investment" with "crypto OTC purchase" and you have the exact scenario your clients face. The amount is unusual, the destination is unusual, and together those two signals are enough to route the transaction to the fraud or compliance desk for a manual call. What the bank will ask for at this stage: source of funds documentation, a clear statement of purpose, identification of the beneficiary institution, and often a callback to the account holder to confirm intent. If your client is traveling, unresponsive, or simply doesn't understand why their bank is asking these questions, the wire sits. Transactions flagged for review won't process until the review is complete, which may take up to 72 hours. In a deal where the OTC desk's quote is time-locked, 72 hours is a deal-breaker. ### The correspondent banking chain For international wires, the problem compounds. Many crypto-to-fiat solutions rely on international SWIFT transfers. These transfers often pass through multiple correspondent banks before reaching the final recipient. Each correspondent bank applies its own compliance rules and risk appetite. SWIFT itself does not move money; it moves messages. A wire from a US bank to a Vietnamese bank typically passes through 1 to 4 correspondent banks, each of which holds nostro and vostro accounts at the next bank in the chain. Each hop adds a fee, often $15 to $25, and a delay of hours to a full business day. Now add the crypto context. Each intermediary bank can independently flag or delay the transfer. Crypto-related transactions face inconsistent interpretation across jurisdictions, and the sender has no visibility into where or why a transfer is stopped. Even if the originating bank approves the transaction, a correspondent bank may still block it. This is one of the most common and least understood causes of frozen crypto-related transfers. This is the scenario that produces the most confusion in practice. Your client's bank approved the wire. The funds left the account. The OTC desk hasn't confirmed receipt. There is no error message — just silence. What's actually happening is that the wire is sitting in a correspondent bank's compliance queue, and neither the sender's bank nor the beneficiary's bank has visibility into exactly when or whether it will clear. Complex beneficiary ownership or purpose: if the payment lacks clear commercial purpose or the beneficiary is a corporate structure, compliance teams may request supporting documents and hold funds until satisfied. And because every correspondent bank has its own AML framework, a wire that cleared the first hop can still be held at the second. Manual compliance reviews or interbank negotiations can take 3–10 or more business days, sometimes longer for complex sanctions or cross-jurisdictional approvals. For deals structured around a specific settlement date, that window can collapse the entire transaction. ### The beneficiary bank If the wire survives the originating bank and the correspondent chain, it can still be held at the receiving end. Regulated OTC desks bank at institutions that have specifically onboarded them as customers and have established compliance protocols for incoming crypto-related wires. But those protocols are not automatic clearance — they are a process, and that process takes time when the incoming wire lacks the documentation the receiving bank expects. A regulated OTC desk produces compliance documentation that correspondent banks and receiving institutions will accept. Without that, large fiat settlements face a real risk of being flagged regardless of how smoothly the trade is executed. The implication for you as the professional managing the deal: the source of the wire matters to the receiving institution, not just the amount. Proceeds arriving from an unverified, informal, or unregulated counterparty are treated very differently than proceeds arriving from a documented, licensed desk. ## What the bank's compliance system is actually looking for The AML infrastructure at any regulated financial institution operates on a combination of rules-based triggers and behavioral modeling. Many banks use anti-money laundering (AML) software that employs rules-based and machine learning algorithms to flag unusual activities. These systems help compliance teams identify potential SAR cases. A Suspicious Activity Report, or SAR, is the formal mechanism by which banks report to regulators — and the filing threshold shapes how banks approach crypto-linked transactions. When transactions or behavior raise red flags, businesses must file suspicious activity reports (SARs) with the relevant authorities. In the US, crypto businesses classified as MSBs must file SARs for transactions involving $2,000 or more where there is reason to suspect illicit activity. For banks, the threshold is $5,000. Because the consequences of failing to file a required SAR are significant — regulatory penalties, reputational harm, and fines — bank compliance teams are structured to err on the side of review. The cost of a false positive (briefly inconveniencing a legitimate customer) is far lower than the cost of a missed filing. Someone transfers large amounts of cryptocurrency to an exchange, immediately converts it to fiat, and withdraws it, repeating the pattern with different accounts — this pattern is treated as indicative of layering in a money-laundering scheme. The problem is that a legitimate OTC purchase, executed cleanly and documented properly, can produce a transaction record that looks superficially similar: a large wire from an account with no prior crypto activity, moving to a financial institution that handles digital assets, for a transaction that will produce an onchain event. The pattern-recognition system doesn't know your client's intention. It knows what the transaction looks like. The FATF Travel Rule adds another layer. The Travel Rule requires VASPs to collect and transmit originator and beneficiary information when processing transfers above designated thresholds. Many countries enforce a Crypto Travel Rule, which requires platforms to attach sender and receiver information for transactions above defined thresholds, typically $1,000–$3,000. Where that information is missing, incomplete, or formatted in a way the receiving institution's system doesn't parse correctly, the transaction gets flagged for manual reconciliation. And manual reconciliation takes days, not hours. ## The regulatory status of the OTC desk changes everything One variable that professionals frequently underestimate is how much the counterparty's regulatory status affects whether the wire lands cleanly. This isn't theoretical — it is the practical difference between a wire that clears the same day and a wire that sits in a compliance queue for a week. Fiat proceeds arriving at a bank from an unregulated or lightly regulated OTC desk carry substantially higher compliance risk than proceeds from a supervised intermediary with a documented compliance process. Banks distinguish between these two scenarios, and the difference often determines whether the incoming wire is accepted or rejected. A licensed desk runs full KYC, AML, and source-of-funds checks, which produces the documentation your bank will demand. Proceeds from an unregulated desk arrive at the bank with no compliance trail and are far more likely to be rejected. This is the argument for steering clients toward regulated counterparties even when the unregulated desk is offering a marginally better quote. If the wire gets held for ten days, the spread advantage evaporates immediately — and you are the professional fielding the calls. The license is not a formality. It is the single factor that decides whether the bank receiving your fiat accepts the proceeds or freezes them. When you are setting up the payment structure for a deal, verifying the regulatory standing of the counterparty is part of your due diligence, not an afterthought. ## Why the buyer's banking profile matters more than most advisors acknowledge A significant source of wire delays doesn't come from the OTC desk or the wire instructions — it comes from the buyer's own account history and the stated purpose on the wire memo field. A lack of proof of legal, commercial practice, or even any commercial activities by many of the parties to the transaction can be flagged. For example, a bank might use AML solutions to flag a transaction as suspicious if it is made between two individuals who do not have any apparent business relationship. For a buyer who has held a savings or investment account with no history of large outgoing wires, the sudden appearance of a transfer in the hundreds of thousands or millions of dollars to a crypto-adjacent institution is exactly the kind of anomaly that trips every behavioral rule in the bank's system. It doesn't matter that the client has been with that bank for twenty years. The system isn't looking at the relationship — it's looking at the deviation. Preparing the buyer before the wire is initiated is not optional. The practical steps: notify the bank in advance of a large wire to a specific destination; provide a clear written description of the transaction; have source-of-funds documentation ready to submit on request; and make sure the account holder is available to take a verification call, because bigger transfers — whether through Zelle, a wire, or an internal bank-to-bank move — often trigger extra verification, and some banks require a phone call with the fraud department before releasing the funds. Missing that call means the wire doesn't move until the bank reaches the client, which may not be until the next business day. ## The problem with the wire memo field It is worth addressing this directly because it causes more holds than almost any other single factor. The purpose description on a wire — the memo field — is read by the originating bank's compliance system before the wire is released. "Crypto purchase," "Bitcoin," "digital asset acquisition," and any variation of these phrases flag the transaction. What you write in that field shapes how the wire is classified in transit. If the payment lacks clear commercial purpose or the beneficiary is a corporate structure, compliance teams may request supporting documents and hold funds until satisfied. The memo field is the bank's first indicator of commercial purpose. A description that is too vague invites a documentation request. A description that explicitly mentions cryptocurrency routes the wire into the high-risk category before a human has even looked at it. The right approach depends on the specific bank and the counterparty's instructions — which is exactly why experienced OTC desks provide detailed wire instructions that include recommended memo language. Those instructions exist because the desk has learned, through operational experience, what triggers holds at the major correspondent banks they work with. Ignoring those instructions and substituting your own language in the memo field is a reliable way to add days to the settlement timeline. ## What actually breaks the pattern — and what doesn't A common misconception is that re-sending the wire with a different amount or splitting the transaction into multiple smaller wires will resolve the problem. It won't. Sending several smaller payments in a row — especially to the same person — can trigger a fraud review. While this isn't "structuring" in the legal sense, banks' fraud systems may interpret rapid, repeated transfers as an attempt to bypass limits or as a sign your account has been compromised. In many cases, all the payments will be paused until the bank confirms they're legitimate. Structuring — the practice of breaking transactions into sub-threshold amounts specifically to avoid reporting — is itself a federal offense, and even the appearance of it will extend, not resolve, the hold. What actually breaks the pattern is documentation and communication, submitted proactively, before the compliance team asks. That means a letter or secure message to the bank's compliance or fraud department explaining the transaction purpose, the counterparty, the legal basis for the transfer, and the client's relationship to the funds. It means having corporate documents, trade confirmations, or prior transaction records ready to transmit. Prepare a compliance pack — invoice, contract, client details, and purpose code — and submit proactively for first-time or large payments. Reactive compliance is always slower than proactive compliance. ## The onchain alternative — and where it actually fits The fiat wire problem is structural, not incidental. It persists because the compliance infrastructure that governs wire transfers was built for a world where digital asset transactions didn't exist, and layered onto a correspondent banking system that adds compliance checkpoints at every hop. No amount of better memo-field language fully resolves the underlying mismatch between what SWIFT was built to handle and what a crypto OTC purchase looks like to an automated risk-scoring system. For deals where the counterparty is receiving on-chain — where the buyer is acquiring an asset that settles directly to a wallet — the payment structure can be built differently from the start. Instead of routing fiat through multiple correspondent banks toward a destination that every bank in the chain will scrutinize, the settlement leg can happen entirely on-chain: the funds move to the designated wallets in a single transaction, split automatically at the agreed percentages, without touching the correspondent banking system at all. Shaka is built for exactly this moment — the professional sets the recipient wallets and the split structure, and when the deal closes, every counterparty receives their allocation in one settlement, directly and with finality. That's not a workaround for every deal. There are transactions where fiat delivery is required and where the wire must be navigated, documented, and cleared through the banking system. In those cases, the workflow described above — proactive bank preparation, correct memo language, regulated counterparties, compliance documentation — is the only path. But for deals where the economics land in a stablecoin or in the native asset, replacing the wire leg with an onchain payment eliminates the correspondent banking problem entirely. The question banks can't stop asking — "what is the crypto-linked purpose of this wire?" — simply doesn't get asked. ## The documentation framework that actually moves wires For deals where fiat wires are unavoidable, the professional's job is to pre-empt every compliance question before the bank asks it. In practice, that means five things. First, the counterparty documentation package needs to be assembled before the wire is sent, not after the hold is placed. This means the OTC desk's licensing information, any trade confirmation or term sheet, and — for large transactions — source-of-funds documentation for the buyer. The desk must provide trade confirmations, wire records, and compliance reporting in a format that can be submitted directly to a bank's compliance team. Second, the buyer needs to have a prior conversation with their bank. This doesn't need to be a formal process — a brief call or secure message to the bank's private banking or wire department, explaining that a large wire will be initiated to a specific licensed institution for the purchase of digital assets, substantially reduces the probability of an automatic hold. The bank's system may still flag the wire, but a flagged wire with advance notification clears faster than a flagged wire that arrives without context. Third, the memo field should follow the OTC desk's specific instructions. Those instructions exist because the desk has operational data on what language reduces holds at the institutions their clients use. Fourth, for international wires, confirm the full correspondent banking route before initiating the transfer. A wire from a US bank to a Vietnamese bank typically passes through 1 to 4 correspondent banks. Each of those correspondent banks is a potential hold point. Knowing the route means knowing which correspondent bank's compliance standards apply in transit — and whether a direct relationship or an alternative rail is available. Fifth, preserve the deal timeline with a realistic buffer that accounts for potential holds. Deals that are structured with exactly zero days of settlement float will fail when a wire takes four days instead of one. The most experienced OTC professionals build a minimum three-business-day buffer into any transaction that involves a fiat wire to a crypto counterparty — not because they expect a hold, but because the cost of being wrong is too high when the alternative is a lost deal. The wire-flags-crypto problem will not be legislated away quickly, because the banks' risk frameworks respond to population-level fraud data, and that data won't change until the fraud patterns change. What changes in the short term is how well you, as the professional structuring the deal, understand the compliance infrastructure your clients' money is traveling through — and how much of that friction you can pre-empt before it stops the clock on a transaction you've spent weeks building.