[{"data":1,"prerenderedAt":735},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments":3,"resources-category-how-wallet-screening-works-stablecoin-payments":597},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":564,"categoryType":6,"compare":6,"contributors":6,"date":565,"description":566,"extension":567,"faq":568,"howto":6,"isBlog":587,"isChangelog":587,"meta":588,"navigation":590,"path":591,"pillar":587,"products":6,"rawbody":592,"role":6,"seo":593,"seoTitle":594,"stem":595,"thumbnail":6,"updated":565,"__hash__":596},"content\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments.md","How wallet screening works in stablecoin payments: exposure, risk scores, and frozen addresses",null,{"type":8,"value":9,"toc":550},"minimark",[10,14,17,20,26,45,54,59,62,68,74,82,86,96,105,108,123,127,130,133,229,240,248,252,255,261,267,273,276,280,283,301,313,316,336,344,348,351,406,414,418,421,453,456,460,468,480,498,501,505,508,512],[11,12,13],"p",{},"Wallet screening checks a blockchain address against sanctions lists and blockchain analytics before funds go to it, and after funds arrive from it. The list check catches addresses regulators have published. The analytics check scores how close an address sits to sanctioned parties or illicit activity, which matters because published lists are incomplete.",[11,15,16],{},"A wallet address is a new kind of counterparty. It carries its own history, it can belong to someone other than your customer, and once tokens move to it they don't come back on request. Screening is how a payments team decides, before money moves, whether it should.",[11,18,19],{},"This article is for information only and is not legal advice.",[11,21,22],{},[23,24,25],"strong",{},"Key takeaways",[27,28,29,33,36,39,42],"ul",{},[30,31,32],"li",{},"Screen the address, not only the customer. A verified customer can still send to, or receive from, a sanctioned or high-risk address.",[30,34,35],{},"OFAC publishes some digital currency addresses on the SDN List, and says itself that those listings are not likely to be exhaustive.",[30,37,38],{},"Blockchain analytics fills the gap by scoring direct and indirect exposure to risky addresses. Hops and thresholds are a policy choice.",[30,40,41],{},"You can't refuse an inbound onchain transfer. Write the rule for what happens to funds that land from a flagged address before it happens.",[30,43,44],{},"USDC and USDT issuers can block addresses. A frozen balance stays stuck until the issuer lifts the block.",[11,46,47,48,53],{},"If you're mapping where screening fits in the wider payment system, start with ",[49,50,52],"a",{"href":51},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure","what stablecoin infrastructure is",". Wallet screening is one control inside its compliance layer.",[55,56,58],"h2",{"id":57},"what-is-wallet-screening","What is wallet screening?",[11,60,61],{},"Wallet screening is the check a payments team runs on a blockchain address before it sends funds to that address or accepts funds from it. It has two parts, and they answer different questions.",[11,63,64,67],{},[23,65,66],{},"List screening"," asks: is this exact address on a sanctions list? It's a lookup. Either the address appears in a published entry or it doesn't.",[11,69,70,73],{},[23,71,72],{},"Exposure screening"," asks: how close is this address to risky activity? It uses blockchain analytics, which clusters addresses that likely belong to the same entity and labels clusters by type (exchange, mixer, scam, darknet market, sanctioned entity). The tool then traces where an address's funds came from and went to, and returns a risk score.",[11,75,76,77,81],{},"Customer screening, covered in ",[49,78,80],{"href":79},"\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen","ongoing sanctions screening",", checks names. Wallet screening checks identifiers that names can't reach. Both feed the same alert queue.",[55,83,85],{"id":84},"which-wallet-addresses-appear-on-sanctions-lists","Which wallet addresses appear on sanctions lists?",[11,87,88,89,95],{},"The US Treasury's Office of Foreign Assets Control (OFAC) adds digital currency addresses to some entries on the Specially Designated Nationals (SDN) List. OFAC ",[49,90,94],{"href":91,"rel":92},"https:\u002F\u002Fofac.treasury.gov\u002Frecent-actions\u002F20181128",[93],"nofollow","first did this on November 28, 2018",", for two individuals tied to Iran.",[11,97,98,99,104],{},"The listings are useful and incomplete at the same time. OFAC's ",[49,100,103],{"href":101,"rel":102},"https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F562",[93],"FAQ 562"," says its digital currency address listings are \"not likely to be exhaustive.\" The same answer says that anyone who identifies an address they believe belongs to or is associated with an SDN, and who holds property in it, should block it and report it to OFAC.",[11,106,107],{},"Two practical consequences follow:",[109,110,111,117],"ol",{},[30,112,113,116],{},[23,114,115],{},"An address not on the list can still be prohibited."," If you know or have reason to know a wallet belongs to a listed person, the absence of the address from the SDN entry doesn't help you.",[30,118,119,122],{},[23,120,121],{},"One entity often controls many addresses."," A sanctioned party can open new addresses in seconds. List screening catches the ones already published; exposure screening is how the rest get caught.",[55,124,126],{"id":125},"how-does-blockchain-analytics-score-a-wallet","How does blockchain analytics score a wallet?",[11,128,129],{},"Blockchain analytics scores a wallet by tracing its transaction history and measuring how much of its activity touches labeled risky entities. The output is usually a score or a risk tier, plus the categories behind it.",[11,131,132],{},"The scoring rests on two kinds of exposure:",[134,135,136,155],"table",{},[137,138,139],"thead",{},[140,141,142,146,149,152],"tr",{},[143,144,145],"th",{},"Exposure type",[143,147,148],{},"What it means",[143,150,151],{},"Example",[143,153,154],{},"How strong a signal",[156,157,158,173,187,201,215],"tbody",{},[140,159,160,164,167,170],{},[161,162,163],"td",{},"Direct exposure",[161,165,166],{},"The address transacted with a risky address in one transfer",[161,168,169],{},"Received USDT straight from a sanctioned address",[161,171,172],{},"Strong. Usually triggers review or a block",[140,174,175,178,181,184],{},[161,176,177],{},"Indirect exposure, one hop",[161,179,180],{},"Funds passed through one intermediate address",[161,182,183],{},"Sanctioned address to an unlabeled wallet to your counterparty",[161,185,186],{},"Moderate. Depends on amount and timing",[140,188,189,192,195,198],{},[161,190,191],{},"Indirect exposure, several hops",[161,193,194],{},"Funds passed through two or more addresses",[161,196,197],{},"Mixer output routed through a chain of fresh wallets",[161,199,200],{},"Weaker with each hop, unless the pattern looks deliberate",[140,202,203,206,209,212],{},[161,204,205],{},"Ownership attribution",[161,207,208],{},"The address is clustered with an entity that is itself risky",[161,210,211],{},"An address controlled by a listed exchange",[161,213,214],{},"Strong. Treat like direct exposure",[140,216,217,220,223,226],{},[161,218,219],{},"No exposure found",[161,221,222],{},"No labeled risky activity in the traced history",[161,224,225],{},"New wallet, or one only used with regulated exchanges",[161,227,228],{},"Clean for now. Not a guarantee",[11,230,231,232,235,236,239],{},"Two settings decide how noisy this gets. The ",[23,233,234],{},"hop limit"," sets how far back the trace goes. The ",[23,237,238],{},"threshold"," sets what share or amount of exposure counts. Set them too wide and every wallet that ever touched an exchange looks risky. Set them too narrow and layering through a few fresh wallets walks right past you.",[11,241,242,243,247],{},"Neither setting has an industry standard number. Write down what you chose and why, and tune it the way you'd tune any monitoring rule. The ",[49,244,246],{"href":245},"\u002Fresources\u002Fmore\u002Ftransaction-monitoring-red-flags-stablecoin-payments","transaction monitoring red flags"," list shows how the same rule-tuning discipline works for amounts and velocity.",[55,249,251],{"id":250},"when-should-you-screen-before-or-after-the-transfer","When should you screen: before or after the transfer?",[11,253,254],{},"Screen outbound transfers before they're signed, and screen inbound transfers as soon as they land. The timing differs because blockchains let anyone send to any address, but nobody can pull a confirmed transfer back.",[11,256,257,260],{},[23,258,259],{},"Outbound (pre-transaction)."," You control the send. Screen the destination address, and the customer behind it, before the transaction is broadcast. A match stops the payment. Nothing has moved yet, so nothing needs unwinding.",[11,262,263,266],{},[23,264,265],{},"Inbound (post-transaction)."," You don't control the send. A stranger can push tokens to your deposit address at any time, including from a sanctioned wallet. Screening happens on arrival, and the decision is about the funds you now hold: credit them, hold them for review, return them, or block and report them.",[11,268,269,272],{},[23,270,271],{},"Stored addresses (periodic)."," A wallet that passed at registration can be listed later, or start receiving from risky sources. Rescreen saved addresses when lists or analytics data change, and before each outbound payment, not only once.",[11,274,275],{},"The inbound case is where programs get caught out. A small deposit from a listed address (sometimes called dusting) can land in a clean customer's wallet without their involvement. Your policy should say whether that triggers a block, a review, or just a note on file, and the answer can depend on amount and direct versus indirect exposure.",[55,277,279],{"id":278},"what-can-a-stablecoin-issuer-freeze","What can a stablecoin issuer freeze?",[11,281,282],{},"Stablecoin issuers can block addresses at the token contract level, which freezes every unit of their token held by that address. This is a separate control from your own screening, and it can hit you even when you did everything right.",[11,284,285,288,289,294,295,300],{},[23,286,287],{},"Circle (USDC)."," Circle's ",[49,290,293],{"href":291,"rel":292},"https:\u002F\u002F6778953.fs1.hubspotusercontent-na1.net\u002Fhubfs\u002F6778953\u002FBlog%20Posts\u002FCircle%20Stablecoin%20Access%20Denial%20Policy_pdf.pdf",[93],"Stablecoin Access Denial Policy"," says that when an address is denied access, it can no longer send or receive Circle's stablecoin, and all of the stablecoin it controls is blocked onchain. Circle says it blocks addresses to comply with a law, regulation, or legal order, may block in response to urgent law enforcement or sanctions-related government requests, and may reverse a block once the authority confirms the obligation has lifted. The ",[49,296,299],{"href":297,"rel":298},"https:\u002F\u002Fwww.circle.com\u002Flegal\u002Fusdc-terms",[93],"USDC terms"," reserve the same right.",[11,302,303,306,307,312],{},[23,304,305],{},"Tether (USDT)."," Tether's ",[49,308,311],{"href":309,"rel":310},"https:\u002F\u002Ftether.to\u002Fen\u002Flegal\u002F",[93],"terms of service"," reserve the right to blacklist any address holding Tether tokens for suspected prohibited uses, to freeze tokens, and to bar transactions to or from sanctioned persons.",[11,314,315],{},"What this means in a payment flow:",[27,317,318,324,330],{},[30,319,320,323],{},[23,321,322],{},"A frozen counterparty can't receive."," A payout to a blocked address fails onchain. Screening first saves you the failed transaction and the alert.",[30,325,326,329],{},[23,327,328],{},"Funds received from a soon-to-be-frozen address aren't affected by that freeze."," The block applies to the address, not to tokens that already left it. Your own screening still decides whether you accept them.",[30,331,332,335],{},[23,333,334],{},"Your own address can be frozen."," If an issuer blocks an address you control, the balance sits there until the block is reversed. Keep operating balances spread across addresses you can explain to an issuer, and keep records that show where funds came from.",[11,337,338,339,343],{},"How issuers decide is also part of the ",[49,340,342],{"href":341},"\u002Fresources\u002Fmore\u002Fstablecoin-depeg-risk-payments","depeg and issuer risk"," picture for any payment flow that holds stablecoins.",[55,345,347],{"id":346},"what-should-happen-when-an-address-is-flagged","What should happen when an address is flagged?",[11,349,350],{},"When an address is flagged, stop the money first and decide second. The workflow below works for both list matches and high exposure scores, with the outcome changing by severity.",[109,352,353,359,365,376,382,388,400],{},[30,354,355,358],{},[23,356,357],{},"Freeze the flow, not the customer."," Put the payout on hold before broadcast, or keep inbound funds uncredited. Don't tell the counterparty why.",[30,360,361,364],{},[23,362,363],{},"Confirm the match."," For a list hit, compare the exact address and network to the SDN entry. For an analytics score, open the trace and look at the actual hops and amounts.",[30,366,367,370,371,375],{},[23,368,369],{},"Check the customer side."," Is the address registered to a verified customer? Does the activity fit the customer's stated business? Pull the KYC or ",[49,372,374],{"href":373},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","KYB"," file.",[30,377,378,381],{},[23,379,380],{},"Ask, if the risk is indirect."," A request for information on the relationship and purpose of the payment often clears a one-hop exposure in a day.",[30,383,384,387],{},[23,385,386],{},"Decide and record it."," Clear, return, reject, or block. Write who decided, why, and what evidence they used.",[30,389,390,393,394,399],{},[23,391,392],{},"Block and report confirmed sanctions matches."," OFAC's ",[49,395,398],{"href":396,"rel":397},"https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F646",[93],"FAQ 646"," says a US person holding virtual currency that must be blocked has to deny all parties access to it, isn't required to convert it to fiat, and must report it to OFAC within 10 business days and annually after that.",[30,401,402,405],{},[23,403,404],{},"Feed the result back."," Add the address to an internal deny list, or note a cleared false positive so the same trace doesn't re-alert next week.",[11,407,408,409,413],{},"Steps 4 and 5 mirror how ",[49,410,412],{"href":411},"\u002Fresources\u002Fmore\u002Ftravel-rule-workflow-hold-return-reject","Travel Rule exceptions are handled",": hold, ask, then decide with a written reason.",[55,415,417],{"id":416},"what-are-the-limits-of-wallet-screening","What are the limits of wallet screening?",[11,419,420],{},"Wallet screening reduces risk. It doesn't remove it, and a few limits are worth stating plainly.",[27,422,423,429,435,441,447],{},[30,424,425,428],{},[23,426,427],{},"Lists lag."," An address is listed after the activity, not before. Screening on day one says nothing about day ninety.",[30,430,431,434],{},[23,432,433],{},"Attribution is probabilistic."," Clustering and labels are a vendor's model of who controls what. They can be wrong in both directions.",[30,436,437,440],{},[23,438,439],{},"Fresh wallets look clean."," A brand-new address has no history, so it scores low even when its owner is not. Customer due diligence carries that case.",[30,442,443,446],{},[23,444,445],{},"Cross-chain hops break traces."," Bridges and swaps can split a trail across networks, and not every tool follows every chain equally well.",[30,448,449,452],{},[23,450,451],{},"Unhosted wallets have no counterparty provider."," There's nobody to send Travel Rule data to or ask for records, so the customer relationship has to carry the evidence.",[11,454,455],{},"None of this is a reason to skip screening. It's a reason to pair it with identity checks, monitoring, and a clear hold-and-review process.",[55,457,459],{"id":458},"how-does-blindpay-handle-wallet-risk","How does BlindPay handle wallet risk?",[11,461,462,463,467],{},"BlindPay runs KYC, KYB, sanctions screening, and transaction monitoring inside the API flow, before money moves. Customers are verified before their first transaction, and entities or individuals on OFAC, EU, UN, or other sanctions lists are not supported, per the ",[49,464,466],{"href":465},"\u002Fdocs\u002Fkb\u002Fprohibited-activities","prohibited activities list",".",[11,469,470,471,475,476,467],{},"External wallets are registered per customer as ",[49,472,474],{"href":473},"\u002Fdocs\u002Fblockchain-wallets","blockchain wallets",". On EVM networks, the customer can sign a message and BlindPay recovers the address from the signature, so the address is proven to be under the customer's control instead of pasted in. These wallets are non-custodial: BlindPay never holds their keys and cannot access, freeze, or recover funds in them. For Brazilian customers, each external wallet is also declared as self-custodied or not, as explained in ",[49,477,479],{"href":478},"\u002Fdocs\u002Fkb\u002Fself-custody-wallets","self-custody wallets",[11,481,482,483,487,488,492,493,497],{},"A sanctions or watchlist screening match is one of the documented ",[49,484,486],{"href":485},"\u002Fdocs\u002Fkb\u002Fcut-off-times","compliance hold triggers",". The payin or payout moves to ",[489,490,491],"code",{},"on_hold",", and the compliance team reviews it. If the flag can't be cleared internally, BlindPay sends a request for information about the parties and the purpose of the payment, and an unanswered request may lead to a refund to the sender after 24 hours, as described in ",[49,494,496],{"href":495},"\u002Fdocs\u002Fkb\u002Fon-hold-transactions","on-hold transactions",". A hold can last up to 30 days; a timeout without a decision fails the transaction. If prohibited activity is identified, funds may be frozen pending investigation.",[11,499,500],{},"Payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) from USDC or USDT on supported networks, with these checks applied to each one.",[55,502,504],{"id":503},"what-to-do-next","What to do next",[11,506,507],{},"Write your inbound rule first: what happens to funds that arrive from a listed address, a high-score address, and a one-hop exposure. Then set your hop limit and threshold, and test both on a sample of real deposits before you turn on automatic blocks.",[55,509,511],{"id":510},"sources-and-further-reading","Sources and further reading",[27,513,514,520,526,532,538,544],{},[30,515,516],{},[49,517,519],{"href":91,"rel":518},[93],"OFAC recent actions, November 28, 2018: first digital currency addresses on the SDN List",[30,521,522],{},[49,523,525],{"href":101,"rel":524},[93],"OFAC FAQ 562: digital currency information on the SDN List",[30,527,528],{},[49,529,531],{"href":396,"rel":530},[93],"OFAC FAQ 646: how to block digital currency",[30,533,534],{},[49,535,537],{"href":291,"rel":536},[93],"Circle Stablecoin Access Denial Policy (PDF)",[30,539,540],{},[49,541,543],{"href":297,"rel":542},[93],"Circle USDC terms",[30,545,546],{},[49,547,549],{"href":309,"rel":548},[93],"Tether terms of service",{"title":551,"searchDepth":552,"depth":552,"links":553},"",2,[554,555,556,557,558,559,560,561,562,563],{"id":57,"depth":552,"text":58},{"id":84,"depth":552,"text":85},{"id":125,"depth":552,"text":126},{"id":250,"depth":552,"text":251},{"id":278,"depth":552,"text":279},{"id":346,"depth":552,"text":347},{"id":416,"depth":552,"text":417},{"id":458,"depth":552,"text":459},{"id":503,"depth":552,"text":504},{"id":510,"depth":552,"text":511},"compliance","2026-10-02","How wallet screening works: OFAC-listed addresses, direct and indirect exposure, risk scores, issuer freezes, and what to do when an address is flagged.","md",[569,572,575,578,581,584],{"q":570,"a":571},"What is wallet screening in stablecoin payments?","Wallet screening checks a blockchain address before or after funds move, against sanctions lists and against blockchain analytics data. The list check catches addresses that regulators have published. The analytics check scores how close the address sits to sanctioned parties, mixers, scams, or stolen funds in the transaction graph. Most programs run both, because published address lists are incomplete.",{"q":573,"a":574},"What is the difference between direct and indirect exposure?","Direct exposure means the address sent funds to, or received funds from, a risky address in a single transfer. Indirect exposure means the funds passed through one or more intermediate addresses on the way. Direct exposure to a sanctioned address is a strong signal. Indirect exposure weakens with each hop and with the share of funds involved, so most programs set thresholds for both.",{"q":576,"a":577},"Can you stop someone from sending stablecoins to your address?","No. Anyone can send tokens to any public address, so inbound screening happens after the transfer lands, not before. What a business controls is what it does next: whether it credits the funds, holds them for review, returns them, or blocks and reports them. That is why the inbound rule has to be written down before the first unexpected deposit arrives.",{"q":579,"a":580},"Can Circle or Tether freeze stablecoins in a wallet?","Yes. Circle's published access denial policy says a blocked address can no longer send or receive USDC, and the USDC it holds cannot move onchain. Circle blocks addresses to comply with laws, regulations, or legal orders. Tether's terms reserve the right to blacklist addresses holding USDT and to bar transactions involving sanctioned persons. A frozen balance stays frozen until the issuer reverses the block.",{"q":582,"a":583},"What should happen when a wallet address matches the OFAC list?","Stop the outbound payment, and do not release inbound funds. OFAC's guidance on blocking digital currency says a US person holding blocked virtual currency must deny all parties access to it and report it to OFAC within 10 business days, then annually. Escalate to the compliance officer, keep the full record, and get counsel involved before anyone touches the funds.",{"q":585,"a":586},"How often should wallet addresses be rescreened?","Screen every address before each outbound transfer, not only when it was first added. A wallet that was clean at registration can be listed, or receive funds from a listed address, later. Rescreen stored addresses when sanctions lists or analytics data change, and treat a new high-risk score on a saved address like a new alert, with a review and a decision on record.",false,{"author":589},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments","---\ntitle: \"How wallet screening works in stablecoin payments: exposure, risk scores, and frozen addresses\"\nseoTitle: \"How wallet screening works in stablecoin payments\"\ndescription: \"How wallet screening works: OFAC-listed addresses, direct and indirect exposure, risk scores, issuer freezes, and what to do when an address is flagged.\"\ndate: \"2026-10-02\"\nupdated: \"2026-10-02\"\ncategory: \"compliance\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is wallet screening in stablecoin payments?\"\n    a: \"Wallet screening checks a blockchain address before or after funds move, against sanctions lists and against blockchain analytics data. The list check catches addresses that regulators have published. The analytics check scores how close the address sits to sanctioned parties, mixers, scams, or stolen funds in the transaction graph. Most programs run both, because published address lists are incomplete.\"\n  - q: \"What is the difference between direct and indirect exposure?\"\n    a: \"Direct exposure means the address sent funds to, or received funds from, a risky address in a single transfer. Indirect exposure means the funds passed through one or more intermediate addresses on the way. Direct exposure to a sanctioned address is a strong signal. Indirect exposure weakens with each hop and with the share of funds involved, so most programs set thresholds for both.\"\n  - q: \"Can you stop someone from sending stablecoins to your address?\"\n    a: \"No. Anyone can send tokens to any public address, so inbound screening happens after the transfer lands, not before. What a business controls is what it does next: whether it credits the funds, holds them for review, returns them, or blocks and reports them. That is why the inbound rule has to be written down before the first unexpected deposit arrives.\"\n  - q: \"Can Circle or Tether freeze stablecoins in a wallet?\"\n    a: \"Yes. Circle's published access denial policy says a blocked address can no longer send or receive USDC, and the USDC it holds cannot move onchain. Circle blocks addresses to comply with laws, regulations, or legal orders. Tether's terms reserve the right to blacklist addresses holding USDT and to bar transactions involving sanctioned persons. A frozen balance stays frozen until the issuer reverses the block.\"\n  - q: \"What should happen when a wallet address matches the OFAC list?\"\n    a: \"Stop the outbound payment, and do not release inbound funds. OFAC's guidance on blocking digital currency says a US person holding blocked virtual currency must deny all parties access to it and report it to OFAC within 10 business days, then annually. Escalate to the compliance officer, keep the full record, and get counsel involved before anyone touches the funds.\"\n  - q: \"How often should wallet addresses be rescreened?\"\n    a: \"Screen every address before each outbound transfer, not only when it was first added. A wallet that was clean at registration can be listed, or receive funds from a listed address, later. Rescreen stored addresses when sanctions lists or analytics data change, and treat a new high-risk score on a saved address like a new alert, with a review and a decision on record.\"\n---\n\nWallet screening checks a blockchain address against sanctions lists and blockchain analytics before funds go to it, and after funds arrive from it. The list check catches addresses regulators have published. The analytics check scores how close an address sits to sanctioned parties or illicit activity, which matters because published lists are incomplete.\n\nA wallet address is a new kind of counterparty. It carries its own history, it can belong to someone other than your customer, and once tokens move to it they don't come back on request. Screening is how a payments team decides, before money moves, whether it should.\n\nThis article is for information only and is not legal advice.\n\n**Key takeaways**\n\n- Screen the address, not only the customer. A verified customer can still send to, or receive from, a sanctioned or high-risk address.\n- OFAC publishes some digital currency addresses on the SDN List, and says itself that those listings are not likely to be exhaustive.\n- Blockchain analytics fills the gap by scoring direct and indirect exposure to risky addresses. Hops and thresholds are a policy choice.\n- You can't refuse an inbound onchain transfer. Write the rule for what happens to funds that land from a flagged address before it happens.\n- USDC and USDT issuers can block addresses. A frozen balance stays stuck until the issuer lifts the block.\n\nIf you're mapping where screening fits in the wider payment system, start with [what stablecoin infrastructure is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure). Wallet screening is one control inside its compliance layer.\n\n## What is wallet screening?\n\nWallet screening is the check a payments team runs on a blockchain address before it sends funds to that address or accepts funds from it. It has two parts, and they answer different questions.\n\n**List screening** asks: is this exact address on a sanctions list? It's a lookup. Either the address appears in a published entry or it doesn't.\n\n**Exposure screening** asks: how close is this address to risky activity? It uses blockchain analytics, which clusters addresses that likely belong to the same entity and labels clusters by type (exchange, mixer, scam, darknet market, sanctioned entity). The tool then traces where an address's funds came from and went to, and returns a risk score.\n\nCustomer screening, covered in [ongoing sanctions screening](\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen), checks names. Wallet screening checks identifiers that names can't reach. Both feed the same alert queue.\n\n## Which wallet addresses appear on sanctions lists?\n\nThe US Treasury's Office of Foreign Assets Control (OFAC) adds digital currency addresses to some entries on the Specially Designated Nationals (SDN) List. OFAC [first did this on November 28, 2018](https:\u002F\u002Fofac.treasury.gov\u002Frecent-actions\u002F20181128), for two individuals tied to Iran.\n\nThe listings are useful and incomplete at the same time. OFAC's [FAQ 562](https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F562) says its digital currency address listings are \"not likely to be exhaustive.\" The same answer says that anyone who identifies an address they believe belongs to or is associated with an SDN, and who holds property in it, should block it and report it to OFAC.\n\nTwo practical consequences follow:\n\n1. **An address not on the list can still be prohibited.** If you know or have reason to know a wallet belongs to a listed person, the absence of the address from the SDN entry doesn't help you.\n2. **One entity often controls many addresses.** A sanctioned party can open new addresses in seconds. List screening catches the ones already published; exposure screening is how the rest get caught.\n\n## How does blockchain analytics score a wallet?\n\nBlockchain analytics scores a wallet by tracing its transaction history and measuring how much of its activity touches labeled risky entities. The output is usually a score or a risk tier, plus the categories behind it.\n\nThe scoring rests on two kinds of exposure:\n\n| Exposure type | What it means | Example | How strong a signal |\n| --- | --- | --- | --- |\n| Direct exposure | The address transacted with a risky address in one transfer | Received USDT straight from a sanctioned address | Strong. Usually triggers review or a block |\n| Indirect exposure, one hop | Funds passed through one intermediate address | Sanctioned address to an unlabeled wallet to your counterparty | Moderate. Depends on amount and timing |\n| Indirect exposure, several hops | Funds passed through two or more addresses | Mixer output routed through a chain of fresh wallets | Weaker with each hop, unless the pattern looks deliberate |\n| Ownership attribution | The address is clustered with an entity that is itself risky | An address controlled by a listed exchange | Strong. Treat like direct exposure |\n| No exposure found | No labeled risky activity in the traced history | New wallet, or one only used with regulated exchanges | Clean for now. Not a guarantee |\n\nTwo settings decide how noisy this gets. The **hop limit** sets how far back the trace goes. The **threshold** sets what share or amount of exposure counts. Set them too wide and every wallet that ever touched an exchange looks risky. Set them too narrow and layering through a few fresh wallets walks right past you.\n\nNeither setting has an industry standard number. Write down what you chose and why, and tune it the way you'd tune any monitoring rule. The [transaction monitoring red flags](\u002Fresources\u002Fmore\u002Ftransaction-monitoring-red-flags-stablecoin-payments) list shows how the same rule-tuning discipline works for amounts and velocity.\n\n## When should you screen: before or after the transfer?\n\nScreen outbound transfers before they're signed, and screen inbound transfers as soon as they land. The timing differs because blockchains let anyone send to any address, but nobody can pull a confirmed transfer back.\n\n**Outbound (pre-transaction).** You control the send. Screen the destination address, and the customer behind it, before the transaction is broadcast. A match stops the payment. Nothing has moved yet, so nothing needs unwinding.\n\n**Inbound (post-transaction).** You don't control the send. A stranger can push tokens to your deposit address at any time, including from a sanctioned wallet. Screening happens on arrival, and the decision is about the funds you now hold: credit them, hold them for review, return them, or block and report them.\n\n**Stored addresses (periodic).** A wallet that passed at registration can be listed later, or start receiving from risky sources. Rescreen saved addresses when lists or analytics data change, and before each outbound payment, not only once.\n\nThe inbound case is where programs get caught out. A small deposit from a listed address (sometimes called dusting) can land in a clean customer's wallet without their involvement. Your policy should say whether that triggers a block, a review, or just a note on file, and the answer can depend on amount and direct versus indirect exposure.\n\n## What can a stablecoin issuer freeze?\n\nStablecoin issuers can block addresses at the token contract level, which freezes every unit of their token held by that address. This is a separate control from your own screening, and it can hit you even when you did everything right.\n\n**Circle (USDC).** Circle's [Stablecoin Access Denial Policy](https:\u002F\u002F6778953.fs1.hubspotusercontent-na1.net\u002Fhubfs\u002F6778953\u002FBlog%20Posts\u002FCircle%20Stablecoin%20Access%20Denial%20Policy_pdf.pdf) says that when an address is denied access, it can no longer send or receive Circle's stablecoin, and all of the stablecoin it controls is blocked onchain. Circle says it blocks addresses to comply with a law, regulation, or legal order, may block in response to urgent law enforcement or sanctions-related government requests, and may reverse a block once the authority confirms the obligation has lifted. The [USDC terms](https:\u002F\u002Fwww.circle.com\u002Flegal\u002Fusdc-terms) reserve the same right.\n\n**Tether (USDT).** Tether's [terms of service](https:\u002F\u002Ftether.to\u002Fen\u002Flegal\u002F) reserve the right to blacklist any address holding Tether tokens for suspected prohibited uses, to freeze tokens, and to bar transactions to or from sanctioned persons.\n\nWhat this means in a payment flow:\n\n- **A frozen counterparty can't receive.** A payout to a blocked address fails onchain. Screening first saves you the failed transaction and the alert.\n- **Funds received from a soon-to-be-frozen address aren't affected by that freeze.** The block applies to the address, not to tokens that already left it. Your own screening still decides whether you accept them.\n- **Your own address can be frozen.** If an issuer blocks an address you control, the balance sits there until the block is reversed. Keep operating balances spread across addresses you can explain to an issuer, and keep records that show where funds came from.\n\nHow issuers decide is also part of the [depeg and issuer risk](\u002Fresources\u002Fmore\u002Fstablecoin-depeg-risk-payments) picture for any payment flow that holds stablecoins.\n\n## What should happen when an address is flagged?\n\nWhen an address is flagged, stop the money first and decide second. The workflow below works for both list matches and high exposure scores, with the outcome changing by severity.\n\n1. **Freeze the flow, not the customer.** Put the payout on hold before broadcast, or keep inbound funds uncredited. Don't tell the counterparty why.\n2. **Confirm the match.** For a list hit, compare the exact address and network to the SDN entry. For an analytics score, open the trace and look at the actual hops and amounts.\n3. **Check the customer side.** Is the address registered to a verified customer? Does the activity fit the customer's stated business? Pull the KYC or [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) file.\n4. **Ask, if the risk is indirect.** A request for information on the relationship and purpose of the payment often clears a one-hop exposure in a day.\n5. **Decide and record it.** Clear, return, reject, or block. Write who decided, why, and what evidence they used.\n6. **Block and report confirmed sanctions matches.** OFAC's [FAQ 646](https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F646) says a US person holding virtual currency that must be blocked has to deny all parties access to it, isn't required to convert it to fiat, and must report it to OFAC within 10 business days and annually after that.\n7. **Feed the result back.** Add the address to an internal deny list, or note a cleared false positive so the same trace doesn't re-alert next week.\n\nSteps 4 and 5 mirror how [Travel Rule exceptions are handled](\u002Fresources\u002Fmore\u002Ftravel-rule-workflow-hold-return-reject): hold, ask, then decide with a written reason.\n\n## What are the limits of wallet screening?\n\nWallet screening reduces risk. It doesn't remove it, and a few limits are worth stating plainly.\n\n- **Lists lag.** An address is listed after the activity, not before. Screening on day one says nothing about day ninety.\n- **Attribution is probabilistic.** Clustering and labels are a vendor's model of who controls what. They can be wrong in both directions.\n- **Fresh wallets look clean.** A brand-new address has no history, so it scores low even when its owner is not. Customer due diligence carries that case.\n- **Cross-chain hops break traces.** Bridges and swaps can split a trail across networks, and not every tool follows every chain equally well.\n- **Unhosted wallets have no counterparty provider.** There's nobody to send Travel Rule data to or ask for records, so the customer relationship has to carry the evidence.\n\nNone of this is a reason to skip screening. It's a reason to pair it with identity checks, monitoring, and a clear hold-and-review process.\n\n## How does BlindPay handle wallet risk?\n\nBlindPay runs KYC, KYB, sanctions screening, and transaction monitoring inside the API flow, before money moves. Customers are verified before their first transaction, and entities or individuals on OFAC, EU, UN, or other sanctions lists are not supported, per the [prohibited activities list](\u002Fdocs\u002Fkb\u002Fprohibited-activities).\n\nExternal wallets are registered per customer as [blockchain wallets](\u002Fdocs\u002Fblockchain-wallets). On EVM networks, the customer can sign a message and BlindPay recovers the address from the signature, so the address is proven to be under the customer's control instead of pasted in. These wallets are non-custodial: BlindPay never holds their keys and cannot access, freeze, or recover funds in them. For Brazilian customers, each external wallet is also declared as self-custodied or not, as explained in [self-custody wallets](\u002Fdocs\u002Fkb\u002Fself-custody-wallets).\n\nA sanctions or watchlist screening match is one of the documented [compliance hold triggers](\u002Fdocs\u002Fkb\u002Fcut-off-times). The payin or payout moves to `on_hold`, and the compliance team reviews it. If the flag can't be cleared internally, BlindPay sends a request for information about the parties and the purpose of the payment, and an unanswered request may lead to a refund to the sender after 24 hours, as described in [on-hold transactions](\u002Fdocs\u002Fkb\u002Fon-hold-transactions). A hold can last up to 30 days; a timeout without a decision fails the transaction. If prohibited activity is identified, funds may be frozen pending investigation.\n\nPayouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) from USDC or USDT on supported networks, with these checks applied to each one.\n\n## What to do next\n\nWrite your inbound rule first: what happens to funds that arrive from a listed address, a high-score address, and a one-hop exposure. Then set your hop limit and threshold, and test both on a sample of real deposits before you turn on automatic blocks.\n\n## Sources and further reading\n\n- [OFAC recent actions, November 28, 2018: first digital currency addresses on the SDN List](https:\u002F\u002Fofac.treasury.gov\u002Frecent-actions\u002F20181128)\n- [OFAC FAQ 562: digital currency information on the SDN List](https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F562)\n- [OFAC FAQ 646: how to block digital currency](https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F646)\n- [Circle Stablecoin Access Denial Policy (PDF)](https:\u002F\u002F6778953.fs1.hubspotusercontent-na1.net\u002Fhubfs\u002F6778953\u002FBlog%20Posts\u002FCircle%20Stablecoin%20Access%20Denial%20Policy_pdf.pdf)\n- [Circle USDC terms](https:\u002F\u002Fwww.circle.com\u002Flegal\u002Fusdc-terms)\n- [Tether terms of service](https:\u002F\u002Ftether.to\u002Fen\u002Flegal\u002F)\n",{"title":5,"description":566},"How wallet screening works in stablecoin payments","resources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments","C5Bn-hhb3SAJmZ6emyxJ0wDQZaw3X-WJd43Ss3VX_HA",[598,602,606,610,614,618,622,626,630,634,638,642,646,650,654,655,659,663,666,670,674,678,682,686,690,693,696,700,704,708,711,715,719,723,727,731],{"path":599,"title":600,"description":601},"\u002Fresources\u002Fmore\u002Faml-audit-readiness-risk-monitoring","AML audit readiness: what regulators ask for and how to prove your risk monitoring works","The evidence examiners expect from automated risk monitoring: a 10-item evidence table, good vs poor practice, SAR timelines, RFIs, and a 30-day plan.",{"path":603,"title":604,"description":605},"\u002Fresources\u002Fmore\u002Fare-blockchain-payments-legal","Are blockchain payments legal? Rules in the US, EU, UK, Brazil, and Mexico","Blockchain payments are legal for businesses in the US, EU, UK, Brazil, and Mexico, under different rules. What each country regulates, as of October 2026.",{"path":607,"title":608,"description":609},"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible","Are stablecoin payments reversible? Finality, custody, and fraud explained","Stablecoin transfers settle final in minutes and cannot be reversed. That finality proves custody at every step, but it also opens a fraud gap on the fiat side of the payment.",{"path":611,"title":612,"description":613},"\u002Fresources\u002Fmore\u002Fautomated-kyc-kyb-vs-manual-onboarding","Automated KYC\u002FKYB vs. manual onboarding: what actually changes","A side-by-side comparison of automated and manual KYC\u002FKYB for fintechs: onboarding time, false-positive rates, cost per verification, scaling across jurisdictions, and audit-trail quality, plus the cases where a human reviewer is still required.",{"path":615,"title":616,"description":617},"\u002Fresources\u002Fmore\u002Fbrazil-self-custody-wallet-declaration","Brazil's self-custody wallet rule: COAF reporting for transfers of US$10,000 or more","Since October 1, 2026, Brazil requires reports to COAF on transfers of US$10,000+ to or from self-custodied wallets. What counts, who reports, what to do.",{"path":619,"title":620,"description":621},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-automated-risk-monitoring","Build vs. buy automated risk monitoring: a decision framework and 15 provider questions","Build, buy point solutions, or use an integrated provider? Compare three ways to run automated risk monitoring, who stays responsible, and 15 questions.",{"path":623,"title":624,"description":625},"\u002Fresources\u002Fmore\u002Fcompliance-agents-cross-border-stablecoin-payments","Compliance agents for cross-border stablecoin payments: a global regulatory guide","How compliance agents apply FinCEN, MiCA, FCA, MAS, and Banco Central do Brasil rules to cross-border stablecoin payments: jurisdiction table, the FATF Travel Rule, multi-list sanctions screening, the four components of a compliant program, and questions to ask a compliance provider.",{"path":627,"title":628,"description":629},"\u002Fresources\u002Fmore\u002Fcrypto-wallet-compliance-checklist","Crypto wallet compliance checklist: KYC, KYT, and Travel Rule","The compliance that comes with crypto wallets and stablecoin payments: KYC and KYB, KYT, the Travel Rule, address screening, MSB rules, and 15 checks.",{"path":631,"title":632,"description":633},"\u002Fresources\u002Fmore\u002Fdirect-vs-indirect-stablecoin-exchange","Direct vs indirect stablecoin exchange: who holds the stablecoin, and who carries compliance","In direct exchange, both parties hold stablecoins and own compliance. In indirect exchange, a provider settles in stablecoins behind a normal bank payment.",{"path":635,"title":636,"description":637},"\u002Fresources\u002Fmore\u002Fdo-merchants-need-a-license-to-accept-stablecoins","Do merchants need a license to accept stablecoin payments? KYC, KYB, and compliance explained","Usually no: the license sits with the provider that moves the funds. What merchants still owe on KYB, sanctions, tax, and records in the US, EU, Brazil.",{"path":639,"title":640,"description":641},"\u002Fresources\u002Fmore\u002Fgenius-act-timeline-key-dates","GENIUS Act and MiCA timeline: the key dates for stablecoin payment teams","Every GENIUS Act and MiCA date that matters to a stablecoin payment flow, how the US effective date is calculated, and what to finish before each deadline.",{"path":643,"title":644,"description":645},"\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments","How to automate KYC and KYB for stablecoin payments","A developer guide to automated KYC and KYB for stablecoin payment flows: how verification runs inside a payment API, step-by-step workflows for individuals and businesses, jurisdiction requirements for the US, EU, UK, Singapore, and Brazil, and what to check before settlement.",{"path":647,"title":648,"description":649},"\u002Fresources\u002Fmore\u002Fhow-to-choose-automated-risk-monitoring-vendor","How to choose an automated risk monitoring vendor for a fintech startup","A buyer's guide to automated risk monitoring vendors for early-stage fintechs: the five criteria that matter (regulatory coverage, integration effort, false-positive rate, pricing model, audit output), the question to ask a vendor on each, a checklist table, and what it costs.",{"path":651,"title":652,"description":653},"\u002Fresources\u002Fmore\u002Freduce-false-positives-transaction-monitoring","How to reduce false positives in transaction monitoring without missing real risk","Cut AML alert noise without losing real cases: a 7-step tuning process, the levers that work, the metrics to watch, and what automation should never close.",{"path":591,"title":5,"description":566},{"path":656,"title":657,"description":658},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi","MSB vs money transmitter license vs VASP vs EMI: which license does a stablecoin payment flow need?","MSB registration, state money transmitter licenses, VASP, EMI, and PSAV compared: who needs each, what triggers it, and when your provider covers you.",{"path":660,"title":661,"description":662},"\u002Fresources\u002Fmore\u002Fmica-stablecoin-rules-explained","MiCA stablecoin rules explained for payment companies","What MiCA means if your business uses stablecoins in the EU: EMTs vs ARTs, issuer requirements, why USDC is compliant and USDT was delisted, and a practical checklist.",{"path":79,"title":664,"description":665},"Ongoing sanctions screening: how often to rescreen and what to screen","How often to rescreen customers against sanctions lists, what to screen beyond names, and a cadence that holds up under OFAC strict liability.",{"path":667,"title":668,"description":669},"\u002Fresources\u002Fmore\u002Fpsav-brazil-explained","PSAV in Brazil: the Central Bank's virtual asset license explained","PSAV is Brazil's authorization for virtual asset service providers, created by BCB Resolutions 519, 520, and 521 under Law 14.478\u002F2022. What it requires and who needs it.",{"path":671,"title":672,"description":673},"\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments","Real-time transaction monitoring for cross-border stablecoin payments","Why stablecoin cross-border flows need different monitoring than wires: the signals that get scored (wallet address risk, velocity, corridor risk, on\u002Foff-ramp counterparties), real-time vs. batch monitoring, and a worked example of a flagged pattern from alert to decision.",{"path":675,"title":676,"description":677},"\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance","Stablecoin card issuing compliance: KYC, KYB, and regulatory coverage explained","What compliance stablecoin card issuing requires: KYC vs. KYB, who is responsible for what, how rules differ in the US, EU, UK, and Latin America, and ongoing monitoring.",{"path":679,"title":680,"description":681},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-limits","Stablecoin off-ramp limits: per-transaction, daily, and monthly caps explained","Why off-ramps cap how much you can convert per transaction, day, and month, how the caps map to KYC and KYB tiers, and the documents that raise them.",{"path":683,"title":684,"description":685},"\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026","Stablecoin regulation in 2026: MiCA, the GENIUS Act, Brazil, and Japan","Where stablecoin regulation stands in 2026: MiCA in the EU, the GENIUS Act in the US, Brazil's VASP regime, and Japan's issuer rules, compared for payment businesses.",{"path":687,"title":688,"description":689},"\u002Fresources\u002Fmore\u002Fgenius-act-for-businesses","The GENIUS Act explained for businesses that use stablecoins","What the GENIUS Act means if your business sends, receives, or holds stablecoins: who it regulates, the dates that matter, and what to do before 2027.",{"path":411,"title":691,"description":692},"The Travel Rule in an automated workflow: what to collect, when to hold, when to return","How to automate Travel Rule compliance for stablecoin transfers: what data to collect, the checks before release, and when to hold, reject, or return.",{"path":245,"title":694,"description":695},"Transaction monitoring red flags for stablecoin payments: 12 rules to automate","The 12 red flags automated transaction monitoring should catch in stablecoin and cross-border payments, with rule logic, actions, and the data each needs.",{"path":697,"title":698,"description":699},"\u002Fresources\u002Fmore\u002Fvirtual-account-requirements-kyc-kyb","Virtual account requirements: KYC, KYB, and what the bank reviews before it says yes","What you need to open a virtual account: KYC or KYB, the extra fields and source of funds documents the bank reviews, who owns each step, and timelines.",{"path":701,"title":702,"description":703},"\u002Fresources\u002Fmore\u002Fwhat-are-compliance-agents-in-fintech","What are compliance agents in fintech? How they work and what they do for payments","Compliance agents are autonomous software components that run KYC, KYB, sanctions screening, and transaction monitoring inside a payment flow, then document every decision. How they work, what they do for payments, how they differ from traditional compliance software, and how BlindPay embeds them in its API.",{"path":705,"title":706,"description":707},"\u002Fresources\u002Fmore\u002Fwhat-happens-if-a-stablecoin-payment-provider-fails","What happens to your money if a stablecoin payment provider fails?","Issuer, provider, or bank: who fails decides what you get back. What the GENIUS Act and state law protect, where money sits mid-payment, and a runbook.",{"path":373,"title":709,"description":710},"What is KYB? Know Your Business verification explained","KYB verifies a company's legal existence, ownership, and control before it can transact. What it checks, who counts as a beneficial owner, and how it differs from KYC.",{"path":712,"title":713,"description":714},"\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp","What is a VASP? Virtual asset service provider explained","A VASP is any business that exchanges, transfers, or custodies virtual assets like stablecoins for customers. FATF's definition and what it requires in practice.",{"path":716,"title":717,"description":718},"\u002Fresources\u002Fmore\u002Fwhat-is-automated-risk-monitoring-fintech","What is automated risk monitoring in fintech?","A reference explainer on automated risk monitoring for fintechs: the four components (KYC\u002FKYB, transaction monitoring, sanctions and watchlist screening, compliance automation), what each one flags, a manual vs. automated comparison, and what FinCEN, FATF, and OFAC actually require.",{"path":720,"title":721,"description":722},"\u002Fresources\u002Fmore\u002Ftravel-rule-stablecoin-off-ramps","What is the travel rule for stablecoin off-ramps? Thresholds, data, and failed checks","The travel rule makes off-ramps pass sender and receiver data with transfers. Thresholds by country, required data, and what happens when checks fail.",{"path":724,"title":725,"description":726},"\u002Fresources\u002Fmore\u002Fgenius-act-usdt-foreign-stablecoin-issuers","What the GENIUS Act means for USDT and other foreign-issued stablecoins","Can USDT stay available in the US under the GENIUS Act? The foreign issuer path, the 2027 and 2028 deadlines, and what payment companies should ask now.",{"path":728,"title":729,"description":730},"\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-compliance-who-owns-what","Who owns compliance when you integrate a crypto on-ramp API? KYC, KYB, KYT, and holds","An on-ramp API splits compliance between the provider and you. Who runs KYC, KYB, KYT, sanctions, and the travel rule, and what stays on your side.",{"path":732,"title":733,"description":734},"\u002Fresources\u002Fmore\u002Fsource-of-funds-crypto-off-ramps","Why do crypto off-ramps ask for source of funds? Documents, triggers, and on-chain proof","Why off-ramps ask where your stablecoins came from, how source of funds differs from source of wealth, what triggers a request, and which documents pass.",1791469681887]