[{"data":1,"prerenderedAt":833},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fstablecoin-card-and-payout-compliance-map":3,"resources-category-stablecoin-card-and-payout-compliance-map":674},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":644,"categoryType":6,"compare":6,"contributors":6,"date":645,"description":646,"extension":647,"faq":648,"howto":6,"isBlog":664,"isChangelog":664,"meta":665,"navigation":667,"path":668,"pillar":664,"products":6,"rawbody":669,"role":6,"seo":670,"seoTitle":671,"stem":672,"thumbnail":6,"updated":6,"__hash__":673},"content\u002Fresources\u002Fmore\u002Fstablecoin-card-and-payout-compliance-map.md","Stablecoin card and payout compliance map: who owns KYC, KYB, sanctions, and the Travel Rule",null,{"type":8,"value":9,"toc":629},"minimark",[10,14,28,31,37,56,61,64,67,99,102,106,109,233,236,240,243,258,266,269,287,291,294,297,311,324,328,331,339,353,365,369,372,387,448,456,460,463,466,480,483,487,490,535,539,542,555,558,562,565,579,587,591],[11,12,13],"p",{},"A program that runs stablecoin cards and stablecoin payouts has two compliance stacks, not one. The card leg follows card network and issuing bank rules. The payout leg follows money transmission, virtual asset, and Travel Rule rules. Each provider owns its leg, and your company owns the gaps between them, plus its own customer risk decisions.",[11,15,16,17,22,23,27],{},"This page is a map, not a checklist for one provider. It shows which duty sits where when a company spends from stablecoin balances on a card and also sends stablecoin-funded payouts to bank accounts. For the card side alone, read ",[18,19,21],"a",{"href":20},"\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance","stablecoin card issuing compliance",". For the basics of the product, start with ",[18,24,26],{"href":25},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing","what stablecoin card issuing is",".",[11,29,30],{},"This is general information, not legal advice. Confirm your obligations with counsel in each country where you operate.",[11,32,33],{},[34,35,36],"strong",{},"Key takeaways",[38,39,40,44,47,50,53],"ul",{},[41,42,43],"li",{},"A combined program has five control areas: onboarding (KYC and KYB), transaction monitoring, sanctions screening, the Travel Rule, and record keeping.",[41,45,46],{},"The issuing bank owns card compliance. The payout provider owns the compliance on the transfers it executes. Neither owns your customer relationship.",[41,48,49],{},"The Travel Rule applies to transfers between regulated providers, not to card authorizations. In the US the threshold is $3,000 under 31 CFR 1010.410.",[41,51,52],{},"Wallet screening is the control traditional card programs lack. Every stablecoin funding and payout address needs it.",[41,54,55],{},"The most common audit gap is records split across providers with no shared customer ID.",[57,58,60],"h2",{"id":59},"what-does-a-combined-card-and-payout-program-have-to-cover","What does a combined card and payout program have to cover?",[11,62,63],{},"It has to cover five control areas across two legs. The card leg covers cardholders and card transactions. The payout leg covers senders, recipients, wallets, and bank transfers.",[11,65,66],{},"Some quick definitions first:",[38,68,69,75,81,87,93],{},[41,70,71,74],{},[34,72,73],{},"Issuer (issuing bank):"," the licensed bank or e-money institution whose license the card runs under. It owns the card program's anti-money laundering program.",[41,76,77,80],{},[34,78,79],{},"Program manager:"," the company that runs the card program day to day under the issuer's policies.",[41,82,83,86],{},[34,84,85],{},"Payout provider:"," the company that converts stablecoins and pays local currency into bank accounts. It runs its own compliance program on those transfers.",[41,88,89,92],{},[34,90,91],{},"KYC and KYB:"," know your customer (verifying a person) and know your business (verifying a company and its owners).",[41,94,95,98],{},[34,96,97],{},"Travel Rule:"," the requirement that regulated providers pass sender and recipient information along with a transfer.",[11,100,101],{},"The two legs touch at the funding wallet. Stablecoins that sit behind the card balance are the same stablecoins a payout draws on, so a gap in one leg shows up in the other.",[57,103,105],{"id":104},"who-owns-each-compliance-duty","Who owns each compliance duty?",[11,107,108],{},"Each provider owns the duties for the transactions it executes, and your company owns everything about its own customers that neither provider sees. The table below is the usual split. Contracts can move duties around, so check yours.",[110,111,112,131],"table",{},[113,114,115],"thead",{},[116,117,118,122,125,128],"tr",{},[119,120,121],"th",{},"Duty",[119,123,124],{},"Issuing bank and program manager",[119,126,127],{},"Payout provider",[119,129,130],{},"Your company",[132,133,134,149,163,177,191,205,219],"tbody",{},[116,135,136,140,143,146],{},[137,138,139],"td",{},"KYC on individuals",[137,141,142],{},"Every cardholder, before the card is issued",[137,144,145],{},"Every individual sender it pays out for",[137,147,148],{},"Your own users, if you onboard them first",[116,150,151,154,157,160],{},[137,152,153],{},"KYB on businesses",[137,155,156],{},"Companies in a corporate card program",[137,158,159],{},"Companies that send payouts",[137,161,162],{},"Your business customers and their owners",[116,164,165,168,171,174],{},[137,166,167],{},"Transaction monitoring",[137,169,170],{},"Card authorizations, clearing, disputes",[137,172,173],{},"Payout and payin activity, wallet flows",[137,175,176],{},"Patterns across both, tied to your customer",[116,178,179,182,185,188],{},[137,180,181],{},"Sanctions screening",[137,183,184],{},"Cardholders, merchants per network rules",[137,186,187],{},"Senders, recipients, wallet addresses",[137,189,190],{},"Your customer base, on every list update",[116,192,193,196,199,202],{},[137,194,195],{},"Travel Rule",[137,197,198],{},"Not on card authorizations",[137,200,201],{},"Transfers above the local threshold",[137,203,204],{},"Correct sender and recipient data",[116,206,207,210,213,216],{},[137,208,209],{},"Record keeping",[137,211,212],{},"Card and cardholder records",[137,214,215],{},"Transfer, quote, and screening records",[137,217,218],{},"A single customer file linking both",[116,220,221,224,227,230],{},[137,222,223],{},"Reporting suspicious activity",[137,225,226],{},"Card activity, to its regulator",[137,228,229],{},"Payout activity, to its regulator",[137,231,232],{},"Escalating what you see to both",[11,234,235],{},"Read the last column carefully. Your company sits in the middle and is the only party that sees the whole customer.",[57,237,239],{"id":238},"how-does-kyc-and-kyb-work-across-both-legs","How does KYC and KYB work across both legs?",[11,241,242],{},"Each provider runs its own check, and you supply the data both times. A cardholder verified by the issuer is not automatically verified by the payout provider, unless your contracts set up a reliance arrangement.",[11,244,245,246,252,253,257],{},"On the card side, the issuer needs cardholder identification even when the wallet behind the card is permissionless. ",[18,247,251],{"href":248,"rel":249},"https:\u002F\u002Fwww.neobankbeat.com\u002Fblog\u002Fstablecoin-cards-explained",[250],"nofollow","neobankbeat's explainer"," puts it plainly: \"The wallet may be permissionless; the plastic isn't.\" ",[18,254,256],{"href":255},"\u002Fresources\u002Fmore\u002Fdo-stablecoin-cards-require-kyc","Do stablecoin cards require KYC?"," covers what cardholders are asked for.",[11,259,260,261,265],{},"On the payout side, the provider verifies whoever is sending money. For a company that means KYB: registration, business activity, ownership, and source of funds. ",[18,262,264],{"href":263},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","What is KYB"," lists the usual documents.",[11,267,268],{},"The practical step is to collect once and map twice:",[270,271,272,275,278,281,284],"ol",{},[41,273,274],{},"Collect identity and business data in your own onboarding flow.",[41,276,277],{},"Map the fields to each provider's schema, including country-specific ID numbers.",[41,279,280],{},"Submit to the issuer for cardholders and to the payout provider for senders.",[41,282,283],{},"Store both providers' verification IDs on your own customer record.",[41,285,286],{},"Re-verify on the schedule each provider sets, and when a customer's details change.",[57,288,290],{"id":289},"where-does-transaction-monitoring-sit","Where does transaction monitoring sit?",[11,292,293],{},"Each provider monitors its own leg, and only you can monitor across them. The card program sees spend at merchants. The payout provider sees transfers to bank accounts. A pattern that crosses both, such as a card loaded and then drained by payouts to many new recipients, is visible only in your data.",[11,295,296],{},"Useful cross-leg signals to watch:",[38,298,299,302,305,308],{},[41,300,301],{},"A new customer whose first activity is a large payout rather than card spend.",[41,303,304],{},"Card balances funded from many unrelated wallets.",[41,306,307],{},"Payouts to recipients in countries that do not match the customer's profile.",[41,309,310],{},"Repeated small payouts just under a threshold.",[11,312,313,314,318,319,323],{},"For the payout side, ",[18,315,317],{"href":316},"\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments","real-time transaction monitoring for stablecoin payments"," covers rule design, and ",[18,320,322],{"href":321},"\u002Fresources\u002Fmore\u002Ftransaction-monitoring-red-flags-stablecoin-payments","transaction monitoring red flags"," lists patterns worth alerting on.",[57,325,327],{"id":326},"how-should-sanctions-screening-work-for-cards-and-payouts","How should sanctions screening work for cards and payouts?",[11,329,330],{},"Screen people, companies, and wallet addresses, and screen again whenever lists change. Card programs screen cardholders by default. Stablecoin flows add a second target: the wallet address.",[11,332,333,338],{},[18,334,337],{"href":335,"rel":336},"https:\u002F\u002Fhome.treasury.gov\u002Fsystem\u002Ffiles\u002F126\u002Fvirtual_currency_guidance_brochure.pdf",[250],"OFAC's 2021 sanctions guidance for the virtual currency industry"," describes a risk-based program for companies in this space. In a combined program, that means:",[38,340,341,344,347,350],{},[41,342,343],{},"Screening every cardholder and every payout sender and recipient at onboarding.",[41,345,346],{},"Screening every wallet that funds a card balance or a payout.",[41,348,349],{},"Rescreening the whole customer base on each list update, not only at onboarding.",[41,351,352],{},"Blocking or holding the transaction, not only flagging it, when there is a true match.",[11,354,355,359,360,364],{},[18,356,358],{"href":357},"\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments","How wallet screening works"," explains the address side, and ",[18,361,363],{"href":362},"\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen","how often to rescreen"," covers ongoing screening.",[57,366,368],{"id":367},"when-does-the-travel-rule-apply","When does the Travel Rule apply?",[11,370,371],{},"The Travel Rule applies when funds or virtual assets move between regulated providers. It does not apply to a card authorization, which runs under card network rules instead.",[11,373,374,375,380,381,386],{},"In the US, the funds transfer recordkeeping and travel rule sits in ",[18,376,379],{"href":377,"rel":378},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.410",[250],"31 CFR 1010.410",", with a $3,000 threshold. Globally, ",[18,382,385],{"href":383,"rel":384},"https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002Fupdate-Recommendation-16-payment-transparency-june-2025.html",[250],"FATF updated Recommendation 16"," on payment transparency in June 2025. In a combined program, the moments that trigger it are:",[110,388,389,402],{},[113,390,391],{},[116,392,393,396,399],{},[119,394,395],{},"Event",[119,397,398],{},"Travel Rule in scope?",[119,400,401],{},"Who sends the data",[132,403,404,415,426,437],{},[116,405,406,409,412],{},[137,407,408],{},"Cardholder pays a merchant",[137,410,411],{},"No, card network rules apply",[137,413,414],{},"Issuer, under network rules",[116,416,417,420,423],{},[137,418,419],{},"Stablecoins move from an exchange to the card wallet",[137,421,422],{},"Often, between regulated providers",[137,424,425],{},"The sending provider",[116,427,428,431,434],{},[137,429,430],{},"Payout from stablecoins to a recipient's bank",[137,432,433],{},"Yes, above the local threshold",[137,435,436],{},"The payout provider, with your data",[116,438,439,442,445],{},[137,440,441],{},"Recipient sends funds back",[137,443,444],{},"Depends on the route",[137,446,447],{},"The provider that executes it",[11,449,450,451,455],{},"The data has to be right before the transfer starts. Wrong or missing originator details are the most common reason a payout gets held. ",[18,452,454],{"href":453},"\u002Fresources\u002Fmore\u002Ftravel-rule-workflow-hold-return-reject","Travel Rule holds, returns, and rejections"," walks through what happens next.",[57,457,459],{"id":458},"what-records-should-you-keep","What records should you keep?",[11,461,462],{},"Keep one customer file that links both legs. Each provider keeps its own records, but an examiner or a bank partner will ask you to reconstruct a customer's full activity, and that is hard when data sits in two dashboards.",[11,464,465],{},"At minimum, store:",[38,467,468,471,474,477],{},[41,469,470],{},"Onboarding data you collected and both providers' verification results.",[41,472,473],{},"Every card transaction ID and every payout and quote ID, tagged with your customer ID.",[41,475,476],{},"Screening results and the decision taken on each alert.",[41,478,479],{},"Notes on investigations and any reports filed.",[11,481,482],{},"Retention periods differ by country and record type. Ask counsel for the exact periods in each market.",[57,484,486],{"id":485},"how-does-the-regulatory-layer-differ-by-region","How does the regulatory layer differ by region?",[11,488,489],{},"The regulatory frame on top of these duties changes by market. The card leg is licensed where the card is issued. The stablecoin leg is often regulated where the customer lives. One program can sit under several regimes.",[38,491,492,508,524],{},[41,493,494,497,498,503,504,27],{},[34,495,496],{},"EU:"," ",[18,499,502],{"href":500,"rel":501},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2023\u002F1114\u002Foj\u002Feng",[250],"MiCA"," covers stablecoin issuers and crypto service providers. Read ",[18,505,507],{"href":506},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-europe-mica","stablecoin cards in Europe",[41,509,510,513,514,519,520,27],{},[34,511,512],{},"US:"," the ",[18,515,518],{"href":516,"rel":517},"https:\u002F\u002Fwww.govinfo.gov\u002Fcontent\u002Fpkg\u002FPLAW-119publ27\u002Fhtml\u002FPLAW-119publ27.htm",[250],"GENIUS Act",", signed July 18, 2025, sets the frame for payment stablecoin issuers, while card programs run through sponsor banks. Read ",[18,521,523],{"href":522},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-united-states-regulation","stablecoin cards in the United States",[41,525,526,529,530,534],{},[34,527,528],{},"Elsewhere:"," licensing for virtual asset services varies. ",[18,531,533],{"href":532},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi","Stablecoin payment licenses"," explains MSB, MTL, VASP, and EMI.",[57,536,538],{"id":537},"where-does-blindpay-fit-in-the-compliance-map","Where does BlindPay fit in the compliance map?",[11,540,541],{},"BlindPay runs the payout and collection leg, with KYC, KYB, and sanctions screening built into the same API flow. In the table above, it sits in the payout provider column, next to whichever issuer runs the card program.",[11,543,544,545,549,550,554],{},"From the ",[18,546,548],{"href":547},"\u002Fdocs\u002Fkb\u002Fkyc","BlindPay docs",", customers are verified through the API before they can send payouts, and businesses go through KYB with documents listed in the ",[18,551,553],{"href":552},"\u002Fdocs\u002Fkb\u002Fkyb-documents","KYB documents guide",". Payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on SWIFT. Each payout starts from a live quote, which gives you a quote ID to store on the customer file next to the card transaction IDs.",[11,556,557],{},"BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. That keeps the payout leg separate from the card balance in your records, which is what an examiner wants to see.",[57,559,561],{"id":560},"how-to-get-started","How to get started",[11,563,564],{},"Draw your own version of the who-owns-what table before you sign the second contract. Then:",[270,566,567,570,573,576],{},[41,568,569],{},"List every event in your flow, from onboarding to payout.",[41,571,572],{},"Mark which provider executes each one.",[41,574,575],{},"Find the events no provider owns, and assign them to a person on your team.",[41,577,578],{},"Agree a shared customer ID across both providers.",[11,580,581,582,586],{},"When the payout column is ready to fill in, run a test payout from a free development instance with the ",[18,583,585],{"href":584},"\u002Fdocs\u002Fquickstart-payout","payout quickstart",", and keep the quote and payout IDs it returns as your first record.",[57,588,590],{"id":589},"sources","Sources",[38,592,593,599,605,611,617,623],{},[41,594,595],{},[18,596,598],{"href":248,"rel":597},[250],"neobankbeat, Stablecoin cards explained (November 18, 2025)",[41,600,601],{},[18,602,604],{"href":335,"rel":603},[250],"OFAC, Sanctions compliance guidance for the virtual currency industry (October 2021)",[41,606,607],{},[18,608,610],{"href":377,"rel":609},[250],"31 CFR 1010.410, recordkeeping for funds transfers",[41,612,613],{},[18,614,616],{"href":383,"rel":615},[250],"FATF, Update to Recommendation 16 on payment transparency (June 2025)",[41,618,619],{},[18,620,622],{"href":500,"rel":621},[250],"Regulation (EU) 2023\u002F1114 (MiCA)",[41,624,625],{},[18,626,628],{"href":516,"rel":627},[250],"GENIUS Act, Public Law 119-27 (July 18, 2025)",{"title":630,"searchDepth":631,"depth":631,"links":632},"",2,[633,634,635,636,637,638,639,640,641,642,643],{"id":59,"depth":631,"text":60},{"id":104,"depth":631,"text":105},{"id":238,"depth":631,"text":239},{"id":289,"depth":631,"text":290},{"id":326,"depth":631,"text":327},{"id":367,"depth":631,"text":368},{"id":458,"depth":631,"text":459},{"id":485,"depth":631,"text":486},{"id":537,"depth":631,"text":538},{"id":560,"depth":631,"text":561},{"id":589,"depth":631,"text":590},"compliance","2026-10-10","A compliance map for programs that run stablecoin cards and payouts together: KYC, KYB, monitoring, sanctions, Travel Rule, and records, split by owner.","md",[649,652,655,658,661],{"q":650,"a":651},"Who is responsible for compliance in a stablecoin card program that also pays out to bank accounts?","Each provider owns the duties for the leg it runs. The issuing bank and program manager own cardholder KYC and card monitoring. The payout provider owns KYC or KYB on the sender, sanctions screening of wallets and recipients, and Travel Rule data on its transfers. Your company still owns its own customer risk decisions and records.",{"q":653,"a":654},"Does the Travel Rule apply to stablecoin card spending?","Not to the card authorization itself, which runs on card network rules. It applies when stablecoins or funds move between regulated providers, such as a stablecoin transfer to an exchange or a payout provider. In the US the funds transfer rule in 31 CFR 1010.410 sets a $3,000 threshold. FATF updated its Recommendation 16 on payment transparency in June 2025.",{"q":656,"a":657},"Do I need KYB if my company only funds employee stablecoin cards?","Yes, in practice. The issuer or program manager verifies the company before approving a corporate card program, and a payout provider verifies the company before it sends payments on its behalf. Expect to provide registration documents, ownership details for each major owner, a description of the business, and the expected source of funds.",{"q":659,"a":660},"What sanctions screening does a stablecoin payout need?","Two kinds. The people and companies involved are screened against sanctions lists, and the wallet addresses are screened for links to sanctioned or high-risk activity. OFAC's October 2021 guidance for the virtual currency industry describes a risk-based program that covers both, with ongoing rescreening whenever lists change.",{"q":662,"a":663},"How long should a stablecoin card and payout program keep records?","For the period the local rules set, which differs by country and by record type. Keep onboarding files, screening results, transaction records on both the card and payout side, and investigation notes in one place you can search by customer. Ask counsel for the exact retention periods in each country where you operate.",false,{"author":666},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fstablecoin-card-and-payout-compliance-map","---\ntitle: \"Stablecoin card and payout compliance map: who owns KYC, KYB, sanctions, and the Travel Rule\"\nseoTitle: \"Stablecoin card and payout compliance: who owns what\"\ndescription: \"A compliance map for programs that run stablecoin cards and payouts together: KYC, KYB, monitoring, sanctions, Travel Rule, and records, split by owner.\"\ndate: \"2026-10-10\"\ncategory: \"compliance\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Who is responsible for compliance in a stablecoin card program that also pays out to bank accounts?\"\n    a: \"Each provider owns the duties for the leg it runs. The issuing bank and program manager own cardholder KYC and card monitoring. The payout provider owns KYC or KYB on the sender, sanctions screening of wallets and recipients, and Travel Rule data on its transfers. Your company still owns its own customer risk decisions and records.\"\n  - q: \"Does the Travel Rule apply to stablecoin card spending?\"\n    a: \"Not to the card authorization itself, which runs on card network rules. It applies when stablecoins or funds move between regulated providers, such as a stablecoin transfer to an exchange or a payout provider. In the US the funds transfer rule in 31 CFR 1010.410 sets a $3,000 threshold. FATF updated its Recommendation 16 on payment transparency in June 2025.\"\n  - q: \"Do I need KYB if my company only funds employee stablecoin cards?\"\n    a: \"Yes, in practice. The issuer or program manager verifies the company before approving a corporate card program, and a payout provider verifies the company before it sends payments on its behalf. Expect to provide registration documents, ownership details for each major owner, a description of the business, and the expected source of funds.\"\n  - q: \"What sanctions screening does a stablecoin payout need?\"\n    a: \"Two kinds. The people and companies involved are screened against sanctions lists, and the wallet addresses are screened for links to sanctioned or high-risk activity. OFAC's October 2021 guidance for the virtual currency industry describes a risk-based program that covers both, with ongoing rescreening whenever lists change.\"\n  - q: \"How long should a stablecoin card and payout program keep records?\"\n    a: \"For the period the local rules set, which differs by country and by record type. Keep onboarding files, screening results, transaction records on both the card and payout side, and investigation notes in one place you can search by customer. Ask counsel for the exact retention periods in each country where you operate.\"\n---\n\nA program that runs stablecoin cards and stablecoin payouts has two compliance stacks, not one. The card leg follows card network and issuing bank rules. The payout leg follows money transmission, virtual asset, and Travel Rule rules. Each provider owns its leg, and your company owns the gaps between them, plus its own customer risk decisions.\n\nThis page is a map, not a checklist for one provider. It shows which duty sits where when a company spends from stablecoin balances on a card and also sends stablecoin-funded payouts to bank accounts. For the card side alone, read [stablecoin card issuing compliance](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance). For the basics of the product, start with [what stablecoin card issuing is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing).\n\nThis is general information, not legal advice. Confirm your obligations with counsel in each country where you operate.\n\n**Key takeaways**\n\n- A combined program has five control areas: onboarding (KYC and KYB), transaction monitoring, sanctions screening, the Travel Rule, and record keeping.\n- The issuing bank owns card compliance. The payout provider owns the compliance on the transfers it executes. Neither owns your customer relationship.\n- The Travel Rule applies to transfers between regulated providers, not to card authorizations. In the US the threshold is $3,000 under 31 CFR 1010.410.\n- Wallet screening is the control traditional card programs lack. Every stablecoin funding and payout address needs it.\n- The most common audit gap is records split across providers with no shared customer ID.\n\n## What does a combined card and payout program have to cover?\n\nIt has to cover five control areas across two legs. The card leg covers cardholders and card transactions. The payout leg covers senders, recipients, wallets, and bank transfers.\n\nSome quick definitions first:\n\n- **Issuer (issuing bank):** the licensed bank or e-money institution whose license the card runs under. It owns the card program's anti-money laundering program.\n- **Program manager:** the company that runs the card program day to day under the issuer's policies.\n- **Payout provider:** the company that converts stablecoins and pays local currency into bank accounts. It runs its own compliance program on those transfers.\n- **KYC and KYB:** know your customer (verifying a person) and know your business (verifying a company and its owners).\n- **Travel Rule:** the requirement that regulated providers pass sender and recipient information along with a transfer.\n\nThe two legs touch at the funding wallet. Stablecoins that sit behind the card balance are the same stablecoins a payout draws on, so a gap in one leg shows up in the other.\n\n## Who owns each compliance duty?\n\nEach provider owns the duties for the transactions it executes, and your company owns everything about its own customers that neither provider sees. The table below is the usual split. Contracts can move duties around, so check yours.\n\n| Duty | Issuing bank and program manager | Payout provider | Your company |\n| --- | --- | --- | --- |\n| KYC on individuals | Every cardholder, before the card is issued | Every individual sender it pays out for | Your own users, if you onboard them first |\n| KYB on businesses | Companies in a corporate card program | Companies that send payouts | Your business customers and their owners |\n| Transaction monitoring | Card authorizations, clearing, disputes | Payout and payin activity, wallet flows | Patterns across both, tied to your customer |\n| Sanctions screening | Cardholders, merchants per network rules | Senders, recipients, wallet addresses | Your customer base, on every list update |\n| Travel Rule | Not on card authorizations | Transfers above the local threshold | Correct sender and recipient data |\n| Record keeping | Card and cardholder records | Transfer, quote, and screening records | A single customer file linking both |\n| Reporting suspicious activity | Card activity, to its regulator | Payout activity, to its regulator | Escalating what you see to both |\n\nRead the last column carefully. Your company sits in the middle and is the only party that sees the whole customer.\n\n## How does KYC and KYB work across both legs?\n\nEach provider runs its own check, and you supply the data both times. A cardholder verified by the issuer is not automatically verified by the payout provider, unless your contracts set up a reliance arrangement.\n\nOn the card side, the issuer needs cardholder identification even when the wallet behind the card is permissionless. [neobankbeat's explainer](https:\u002F\u002Fwww.neobankbeat.com\u002Fblog\u002Fstablecoin-cards-explained) puts it plainly: \"The wallet may be permissionless; the plastic isn't.\" [Do stablecoin cards require KYC?](\u002Fresources\u002Fmore\u002Fdo-stablecoin-cards-require-kyc) covers what cardholders are asked for.\n\nOn the payout side, the provider verifies whoever is sending money. For a company that means KYB: registration, business activity, ownership, and source of funds. [What is KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) lists the usual documents.\n\nThe practical step is to collect once and map twice:\n\n1. Collect identity and business data in your own onboarding flow.\n2. Map the fields to each provider's schema, including country-specific ID numbers.\n3. Submit to the issuer for cardholders and to the payout provider for senders.\n4. Store both providers' verification IDs on your own customer record.\n5. Re-verify on the schedule each provider sets, and when a customer's details change.\n\n## Where does transaction monitoring sit?\n\nEach provider monitors its own leg, and only you can monitor across them. The card program sees spend at merchants. The payout provider sees transfers to bank accounts. A pattern that crosses both, such as a card loaded and then drained by payouts to many new recipients, is visible only in your data.\n\nUseful cross-leg signals to watch:\n\n- A new customer whose first activity is a large payout rather than card spend.\n- Card balances funded from many unrelated wallets.\n- Payouts to recipients in countries that do not match the customer's profile.\n- Repeated small payouts just under a threshold.\n\nFor the payout side, [real-time transaction monitoring for stablecoin payments](\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments) covers rule design, and [transaction monitoring red flags](\u002Fresources\u002Fmore\u002Ftransaction-monitoring-red-flags-stablecoin-payments) lists patterns worth alerting on.\n\n## How should sanctions screening work for cards and payouts?\n\nScreen people, companies, and wallet addresses, and screen again whenever lists change. Card programs screen cardholders by default. Stablecoin flows add a second target: the wallet address.\n\n[OFAC's 2021 sanctions guidance for the virtual currency industry](https:\u002F\u002Fhome.treasury.gov\u002Fsystem\u002Ffiles\u002F126\u002Fvirtual_currency_guidance_brochure.pdf) describes a risk-based program for companies in this space. In a combined program, that means:\n\n- Screening every cardholder and every payout sender and recipient at onboarding.\n- Screening every wallet that funds a card balance or a payout.\n- Rescreening the whole customer base on each list update, not only at onboarding.\n- Blocking or holding the transaction, not only flagging it, when there is a true match.\n\n[How wallet screening works](\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments) explains the address side, and [how often to rescreen](\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen) covers ongoing screening.\n\n## When does the Travel Rule apply?\n\nThe Travel Rule applies when funds or virtual assets move between regulated providers. It does not apply to a card authorization, which runs under card network rules instead.\n\nIn the US, the funds transfer recordkeeping and travel rule sits in [31 CFR 1010.410](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.410), with a $3,000 threshold. Globally, [FATF updated Recommendation 16](https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002Fupdate-Recommendation-16-payment-transparency-june-2025.html) on payment transparency in June 2025. In a combined program, the moments that trigger it are:\n\n| Event | Travel Rule in scope? | Who sends the data |\n| --- | --- | --- |\n| Cardholder pays a merchant | No, card network rules apply | Issuer, under network rules |\n| Stablecoins move from an exchange to the card wallet | Often, between regulated providers | The sending provider |\n| Payout from stablecoins to a recipient's bank | Yes, above the local threshold | The payout provider, with your data |\n| Recipient sends funds back | Depends on the route | The provider that executes it |\n\nThe data has to be right before the transfer starts. Wrong or missing originator details are the most common reason a payout gets held. [Travel Rule holds, returns, and rejections](\u002Fresources\u002Fmore\u002Ftravel-rule-workflow-hold-return-reject) walks through what happens next.\n\n## What records should you keep?\n\nKeep one customer file that links both legs. Each provider keeps its own records, but an examiner or a bank partner will ask you to reconstruct a customer's full activity, and that is hard when data sits in two dashboards.\n\nAt minimum, store:\n\n- Onboarding data you collected and both providers' verification results.\n- Every card transaction ID and every payout and quote ID, tagged with your customer ID.\n- Screening results and the decision taken on each alert.\n- Notes on investigations and any reports filed.\n\nRetention periods differ by country and record type. Ask counsel for the exact periods in each market.\n\n## How does the regulatory layer differ by region?\n\nThe regulatory frame on top of these duties changes by market. The card leg is licensed where the card is issued. The stablecoin leg is often regulated where the customer lives. One program can sit under several regimes.\n\n- **EU:** [MiCA](https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2023\u002F1114\u002Foj\u002Feng) covers stablecoin issuers and crypto service providers. Read [stablecoin cards in Europe](\u002Fresources\u002Fmore\u002Fstablecoin-cards-europe-mica).\n- **US:** the [GENIUS Act](https:\u002F\u002Fwww.govinfo.gov\u002Fcontent\u002Fpkg\u002FPLAW-119publ27\u002Fhtml\u002FPLAW-119publ27.htm), signed July 18, 2025, sets the frame for payment stablecoin issuers, while card programs run through sponsor banks. Read [stablecoin cards in the United States](\u002Fresources\u002Fmore\u002Fstablecoin-cards-united-states-regulation).\n- **Elsewhere:** licensing for virtual asset services varies. [Stablecoin payment licenses](\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi) explains MSB, MTL, VASP, and EMI.\n\n## Where does BlindPay fit in the compliance map?\n\nBlindPay runs the payout and collection leg, with KYC, KYB, and sanctions screening built into the same API flow. In the table above, it sits in the payout provider column, next to whichever issuer runs the card program.\n\nFrom the [BlindPay docs](\u002Fdocs\u002Fkb\u002Fkyc), customers are verified through the API before they can send payouts, and businesses go through KYB with documents listed in the [KYB documents guide](\u002Fdocs\u002Fkb\u002Fkyb-documents). Payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on SWIFT. Each payout starts from a live quote, which gives you a quote ID to store on the customer file next to the card transaction IDs.\n\nBlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. That keeps the payout leg separate from the card balance in your records, which is what an examiner wants to see.\n\n## How to get started\n\nDraw your own version of the who-owns-what table before you sign the second contract. Then:\n\n1. List every event in your flow, from onboarding to payout.\n2. Mark which provider executes each one.\n3. Find the events no provider owns, and assign them to a person on your team.\n4. Agree a shared customer ID across both providers.\n\nWhen the payout column is ready to fill in, run a test payout from a free development instance with the [payout quickstart](\u002Fdocs\u002Fquickstart-payout), and keep the quote and payout IDs it returns as your first record.\n\n## Sources\n\n- [neobankbeat, Stablecoin cards explained (November 18, 2025)](https:\u002F\u002Fwww.neobankbeat.com\u002Fblog\u002Fstablecoin-cards-explained)\n- [OFAC, Sanctions compliance guidance for the virtual currency industry (October 2021)](https:\u002F\u002Fhome.treasury.gov\u002Fsystem\u002Ffiles\u002F126\u002Fvirtual_currency_guidance_brochure.pdf)\n- [31 CFR 1010.410, recordkeeping for funds transfers](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.410)\n- [FATF, Update to Recommendation 16 on payment transparency (June 2025)](https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002Fupdate-Recommendation-16-payment-transparency-june-2025.html)\n- [Regulation (EU) 2023\u002F1114 (MiCA)](https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2023\u002F1114\u002Foj\u002Feng)\n- [GENIUS Act, Public Law 119-27 (July 18, 2025)](https:\u002F\u002Fwww.govinfo.gov\u002Fcontent\u002Fpkg\u002FPLAW-119publ27\u002Fhtml\u002FPLAW-119publ27.htm)\n",{"title":5,"description":646},"Stablecoin card and payout compliance: who owns what","resources\u002Fmore\u002Fstablecoin-card-and-payout-compliance-map","uy3jgPkXL-kZwJ9ZC0xwSNBCLnFf8lKpl7-6Msd8X0g",[675,679,683,687,691,695,699,703,707,711,715,719,723,726,730,734,738,742,745,748,752,755,759,762,763,766,769,772,776,780,784,787,790,794,798,802,806,809,813,817,821,825,829],{"path":676,"title":677,"description":678},"\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":680,"title":681,"description":682},"\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":684,"title":685,"description":686},"\u002Fresources\u002Fmore\u002Fare-stablecoin-card-purchases-taxable","Are stablecoin card purchases taxable? A country-by-country overview of disposals, gains, and records","Why a stablecoin card purchase can be a taxable disposal, how the US, UK, Germany, Spain, the Netherlands, and Brazil differ, and which records to keep.",{"path":688,"title":689,"description":690},"\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":692,"title":693,"description":694},"\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":696,"title":697,"description":698},"\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":700,"title":701,"description":702},"\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":704,"title":705,"description":706},"\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":708,"title":709,"description":710},"\u002Fresources\u002Fmore\u002Fcross-border-stablecoin-card-compliance-by-country","Compliance for cross-border stablecoin card programs: a country readiness template","A country readiness template for stablecoin card programs: onboarding rules, funding rails, and payout rails for the US, LatAm, and the EU.",{"path":712,"title":713,"description":714},"\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":716,"title":717,"description":718},"\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":720,"title":721,"description":722},"\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":255,"title":724,"description":725},"Do stablecoin cards require KYC? What to expect, what gets checked, and why \"no KYC\" cards fall short","Why stablecoin cards ask for ID even with a permissionless wallet, what KYC and KYB collect, why no-KYC cards fall short, and how to fix a rejection.",{"path":727,"title":728,"description":729},"\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":731,"title":732,"description":733},"\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":735,"title":736,"description":737},"\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":739,"title":740,"description":741},"\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":357,"title":743,"description":744},"How wallet screening works in stablecoin payments: exposure, risk scores, and frozen addresses","How wallet screening works: OFAC-listed addresses, direct and indirect exposure, risk scores, issuer freezes, and what to do when an address is flagged.",{"path":532,"title":746,"description":747},"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":749,"title":750,"description":751},"\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":362,"title":753,"description":754},"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":756,"title":757,"description":758},"\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":316,"title":760,"description":761},"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":668,"title":5,"description":646},{"path":20,"title":764,"description":765},"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":506,"title":767,"description":768},"Stablecoin cards in Europe: MiCA, euro stablecoins, and what licensing means for cardholders and card programs","How MiCA applies to stablecoin cards in Europe: who needs authorization, how to check a provider on the ESMA register, euro vs dollar stablecoins, SEPA.",{"path":522,"title":770,"description":771},"Stablecoin cards in the United States: the GENIUS Act, sponsor banks, and Visa USDC settlement","How US stablecoin cards are structured and regulated: sponsor bank, program manager, processor, the GENIUS Act, Visa USDC settlement, FDIC coverage, tax.",{"path":773,"title":774,"description":775},"\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":777,"title":778,"description":779},"\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":781,"title":782,"description":783},"\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":453,"title":785,"description":786},"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":321,"title":788,"description":789},"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":791,"title":792,"description":793},"\u002Fresources\u002Fmore\u002Fverification-of-payee-instant-payments","Verification of payee in instant payments: how rails check the recipient before money moves","How EU Verification of Payee, UK Confirmation of Payee, Pix, SPEI, and US payee name checks confirm the recipient before an instant payment becomes final.",{"path":795,"title":796,"description":797},"\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":799,"title":800,"description":801},"\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":803,"title":804,"description":805},"\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":263,"title":807,"description":808},"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":810,"title":811,"description":812},"\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":814,"title":815,"description":816},"\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":818,"title":819,"description":820},"\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":822,"title":823,"description":824},"\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":826,"title":827,"description":828},"\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":830,"title":831,"description":832},"\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.",1791908487679]