[{"data":1,"prerenderedAt":1214},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fcross-border-stablecoin-payments-risk-register":3,"resources-category-cross-border-stablecoin-payments-risk-register":1002},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":560,"categoryType":6,"compare":6,"contributors":6,"date":973,"description":974,"extension":975,"faq":976,"howto":6,"isBlog":992,"isChangelog":992,"meta":993,"navigation":995,"path":996,"pillar":992,"products":6,"rawbody":997,"role":6,"seo":998,"seoTitle":999,"stem":1000,"thumbnail":6,"updated":973,"__hash__":1001},"content\u002Fresources\u002Fmore\u002Fcross-border-stablecoin-payments-risk-register.md","Cross-border stablecoin payments risk register: a fill-in template with 16 risks, scores, and owners",null,{"type":8,"value":9,"toc":955},"minimark",[10,14,23,29,48,53,61,65,68,168,172,175,247,257,261,264,269,348,362,366,464,472,476,550,558,561,656,671,675,794,807,811,882,896,900,903,913,917,948,952],[11,12,13],"p",{},"A cross-border stablecoin payments risk register lists every risk in your payout flow with its cause, a likelihood and impact score, the control that reduces it, an early-warning indicator, and a named owner. Use the template below: 16 starter risks in six categories, scored on a 5x5 scale before and after controls.",[11,15,16,17,22],{},"If you are new to the flow itself, read ",[18,19,21],"a",{"href":20},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-sandwich","what a stablecoin sandwich is"," first: each layer of the sandwich adds its own risks.",[11,24,25],{},[26,27,28],"strong",{},"Key takeaways",[30,31,32,36,39,42,45],"ul",{},[33,34,35],"li",{},"Score every risk twice: inherent (no controls) and residual (with controls). The gap is what your controls are worth.",[33,37,38],{},"Most residual risk in stablecoin payouts sits in operations and compliance, not in the blockchain.",[33,40,41],{},"Every row needs an indicator you can measure weekly, or the register can't warn you of anything.",[33,43,44],{},"One owner per risk, by name. Shared ownership means nobody checks.",[33,46,47],{},"Review quarterly and after every incident, new corridor, or rule change.",[49,50,52],"h2",{"id":51},"how-is-this-different-from-an-incident-playbook","How is this different from an incident playbook?",[11,54,55,56,60],{},"A risk register is written before anything breaks; a playbook is used while something is breaking. The ",[18,57,59],{"href":58},"\u002Fresources\u002Fmore\u002Fblockchain-payment-incident-playbook","blockchain payment incident playbook"," covers the six steps once a payment goes wrong, with a short register of its own. This page adds scoring, indicators, and a starter set you can paste into a spreadsheet.",[49,62,64],{"id":63},"what-columns-should-the-register-have","What columns should the register have?",[11,66,67],{},"Ten columns. Fewer and auditors find gaps; more and nobody keeps it current.",[69,70,71,84],"table",{},[72,73,74],"thead",{},[75,76,77,81],"tr",{},[78,79,80],"th",{},"Column",[78,82,83],{},"What goes in it",[85,86,87,96,104,112,120,128,136,144,152,160],"tbody",{},[75,88,89,93],{},[90,91,92],"td",{},"ID",[90,94,95],{},"Short code, for example SC-01",[75,97,98,101],{},[90,99,100],{},"Category",[90,102,103],{},"One of the six categories below",[75,105,106,109],{},[90,107,108],{},"Risk",[90,110,111],{},"What could happen, in one sentence",[75,113,114,117],{},[90,115,116],{},"Cause",[90,118,119],{},"Why it would happen",[75,121,122,125],{},[90,123,124],{},"Inherent score",[90,126,127],{},"Likelihood x impact with no controls (1 to 25)",[75,129,130,133],{},[90,131,132],{},"Controls",[90,134,135],{},"What you do to reduce it",[75,137,138,141],{},[90,139,140],{},"Residual score",[90,142,143],{},"Likelihood x impact with controls in place",[75,145,146,149],{},[90,147,148],{},"Key risk indicator",[90,150,151],{},"A number you can measure that rises before the risk hits",[75,153,154,157],{},[90,155,156],{},"Owner",[90,158,159],{},"One named person",[75,161,162,165],{},[90,163,164],{},"Last reviewed",[90,166,167],{},"Date and reviewer",[49,169,171],{"id":170},"how-do-you-score-likelihood-and-impact","How do you score likelihood and impact?",[11,173,174],{},"Use a 1 to 5 scale for each and multiply. Define the scale in your own numbers before you score anything.",[69,176,177,190],{},[72,178,179],{},[75,180,181,184,187],{},[78,182,183],{},"Score",[78,185,186],{},"Likelihood",[78,188,189],{},"Impact (example definitions, set your own)",[85,191,192,203,214,225,236],{},[75,193,194,197,200],{},[90,195,196],{},"1",[90,198,199],{},"Less than once in 5 years",[90,201,202],{},"Loss under a small set amount; no customer affected",[75,204,205,208,211],{},[90,206,207],{},"2",[90,209,210],{},"Once in 2 to 5 years",[90,212,213],{},"Small loss; a few payouts delayed by a day",[75,215,216,219,222],{},[90,217,218],{},"3",[90,220,221],{},"Once a year",[90,223,224],{},"Moderate loss; a corridor paused for a day",[75,226,227,230,233],{},[90,228,229],{},"4",[90,231,232],{},"Several times a year",[90,234,235],{},"Large loss; many customers affected; regulator notification possible",[75,237,238,241,244],{},[90,239,240],{},"5",[90,242,243],{},"Monthly or more",[90,245,246],{},"Loss that threatens the program; license or banking relationship at risk",[11,248,249,250,256],{},"Scores of 15 and above need a control plan and a sponsor sign-off. Scores of 8 to 14 need an owner and an indicator. Below 8, record the risk and review it quarterly. This tiering follows the logic of enterprise risk frameworks such as ",[18,251,255],{"href":252,"rel":253},"https:\u002F\u002Fwww.coso.org\u002Fenterprise-risk-management",[254],"nofollow","COSO's enterprise risk management guidance",": tie risk appetite to what the business can absorb, then act on what exceeds it.",[49,258,260],{"id":259},"what-are-the-16-starter-risks","What are the 16 starter risks?",[11,262,263],{},"Copy these rows, then rescore them for your volumes and corridors. The scores below are illustrative, for a mid-size payout program, not a benchmark.",[265,266,268],"h3",{"id":267},"stablecoin-and-issuer","Stablecoin and issuer",[69,270,271,294],{},[72,272,273],{},[75,274,275,277,279,281,284,286,289,292],{},[78,276,92],{},[78,278,108],{},[78,280,116],{},[78,282,283],{},"Inherent",[78,285,132],{},[78,287,288],{},"Residual",[78,290,291],{},"Indicator",[78,293,156],{},[85,295,296,322],{},[75,297,298,301,304,307,310,313,316,319],{},[90,299,300],{},"SC-01",[90,302,303],{},"Stablecoin trades below one dollar while you hold it",[90,305,306],{},"Reserve problem at the issuer",[90,308,309],{},"3x4 = 12",[90,311,312],{},"Hold for minutes, not days; cap holdings per token; execute only against locked quotes",[90,314,315],{},"2x2 = 4",[90,317,318],{},"Market price of each token you hold; hours of holdings",[90,320,321],{},"Treasury",[75,323,324,327,330,333,336,339,342,345],{},[90,325,326],{},"SC-02",[90,328,329],{},"Issuer freezes a token at an address you pay from or to",[90,331,332],{},"Address linked to illicit activity",[90,334,335],{},"2x4 = 8",[90,337,338],{},"Wallet screening before sending; registered wallets only",[90,340,341],{},"1x3 = 3",[90,343,344],{},"Screening alerts per month",[90,346,347],{},"Compliance",[11,349,350,351,356,357,361],{},"The depeg row is not theoretical. When Silicon Valley Bank failed in March 2023, USDC traded as low as 86 cents, per a ",[18,352,355],{"href":353,"rel":354},"https:\u002F\u002Fwww.federalreserve.gov\u002Feconres\u002Fnotes\u002Ffeds-notes\u002Fin-the-shadow-of-bank-run-lessons-from-the-silicon-valley-bank-failure-and-its-impact-on-stablecoins-20251217.html",[254],"December 2025 Federal Reserve note",". It recovered within days. A payment flow that converts within minutes is far less exposed than a treasury that holds for weeks, which is why holding time is the indicator. ",[18,358,360],{"href":359},"\u002Fresources\u002Fmore\u002Fstablecoin-depeg-risk-payments","Stablecoin depeg risk for payment companies"," covers the limits in detail.",[265,363,365],{"id":364},"fx-and-liquidity","FX and liquidity",[69,367,368,388],{},[72,369,370],{},[75,371,372,374,376,378,380,382,384,386],{},[78,373,92],{},[78,375,108],{},[78,377,116],{},[78,379,283],{},[78,381,132],{},[78,383,288],{},[78,385,291],{},[78,387,156],{},[85,389,390,414,438],{},[75,391,392,395,398,401,404,407,409,412],{},[90,393,394],{},"FX-01",[90,396,397],{},"Rate moves between approval and execution",[90,399,400],{},"Slow approvals; quote expiry",[90,402,403],{},"4x2 = 8",[90,405,406],{},"Approve intent, then execute within the quote window; re-quote tolerance in the FX policy",[90,408,315],{},[90,410,411],{},"Quote expiry rate; re-quote delta",[90,413,321],{},[75,415,416,419,422,425,428,431,433,436],{},[90,417,418],{},"FX-02",[90,420,421],{},"Thin local-currency liquidity on a large payout",[90,423,424],{},"Payout size above what the corridor absorbs at a good price",[90,426,427],{},"3x3 = 9",[90,429,430],{},"Split large payouts; test depth with quotes at several sizes",[90,432,315],{},[90,434,435],{},"Spread versus mid-market by payout size",[90,437,321],{},[75,439,440,443,446,449,452,455,458,461],{},[90,441,442],{},"FX-03",[90,444,445],{},"Funds stuck on the wrong chain for the corridor",[90,447,448],{},"Treasury holds USDC on a network the payout doesn't take",[90,450,451],{},"3x2 = 6",[90,453,454],{},"Map each corridor to supported networks; rebalance ahead of payout runs",[90,456,457],{},"1x2 = 2",[90,459,460],{},"Payouts blocked by network mismatch",[90,462,463],{},"Engineering",[11,465,466,467,471],{},"Measure FX-01 before you set a tolerance. ",[18,468,470],{"href":469},"\u002Fresources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate","Payout quality metrics"," defines quote expiry rate and re-quote delta.",[265,473,475],{"id":474},"counterparty-and-custody","Counterparty and custody",[69,477,478,498],{},[72,479,480],{},[75,481,482,484,486,488,490,492,494,496],{},[78,483,92],{},[78,485,108],{},[78,487,116],{},[78,489,283],{},[78,491,132],{},[78,493,288],{},[78,495,291],{},[78,497,156],{},[85,499,500,526],{},[75,501,502,505,508,511,514,517,520,523],{},[90,503,504],{},"CP-01",[90,506,507],{},"Payout provider fails or freezes operations",[90,509,510],{},"Insolvency, license loss, banking partner loss",[90,512,513],{},"2x5 = 10",[90,515,516],{},"Know who holds funds at each step; avoid idle balances at the provider; second provider for top corridor",[90,518,519],{},"1x4 = 4",[90,521,522],{},"Idle balance at provider; provider status page incidents",[90,524,525],{},"Finance",[75,527,528,531,534,537,539,542,544,547],{},[90,529,530],{},"CP-02",[90,532,533],{},"Payout fails after the stablecoins were collected",[90,535,536],{},"Recipient bank rejects; review times out",[90,538,427],{},[90,540,541],{},"Written refund rules per rail; status webhooks into your ledger; refund wallet set on each quote",[90,543,315],{},[90,545,546],{},"Payouts in failed or refunded per week; days to refund",[90,548,549],{},"Operations",[11,551,552,553,557],{},"For CP-01, map the failure modes in ",[18,554,556],{"href":555},"\u002Fresources\u002Fmore\u002Fwhat-happens-if-a-stablecoin-payment-provider-fails","what happens if a stablecoin payment provider fails"," before you sign.",[265,559,347],{"id":560},"compliance",[69,562,563,583],{},[72,564,565],{},[75,566,567,569,571,573,575,577,579,581],{},[78,568,92],{},[78,570,108],{},[78,572,116],{},[78,574,283],{},[78,576,132],{},[78,578,288],{},[78,580,291],{},[78,582,156],{},[85,584,585,609,632],{},[75,586,587,590,593,596,598,601,604,607],{},[90,588,589],{},"CO-01",[90,591,592],{},"Payment to a sanctioned person or address",[90,594,595],{},"Recipient or wallet on a sanctions list",[90,597,513],{},[90,599,600],{},"Screen recipients and wallets before the first payout and on list updates",[90,602,603],{},"1x5 = 5",[90,605,606],{},"Screening hits; time since last rescreen",[90,608,347],{},[75,610,611,614,617,620,622,625,627,630],{},[90,612,613],{},"CO-02",[90,615,616],{},"Travel Rule data missing on a transfer",[90,618,619],{},"Counterparty provider asks for originator or beneficiary data you didn't collect",[90,621,427],{},[90,623,624],{},"Collect originator and beneficiary data at onboarding",[90,626,315],{},[90,628,629],{},"Transfers held for missing data",[90,631,347],{},[75,633,634,637,640,643,645,648,651,654],{},[90,635,636],{},"CO-03",[90,638,639],{},"Customer or payout held for a request for information",[90,641,642],{},"Incomplete KYC or KYB, unusual activity",[90,644,403],{},[90,646,647],{},"Answer within days, not weeks; keep invoices and source-of-funds documents ready",[90,649,650],{},"3x1 = 3",[90,652,653],{},"Open information requests and their age",[90,655,347],{},[11,657,658,659,664,665,670],{},"Sanctions screening on wallets needs analytics, not just a list check: ",[18,660,663],{"href":661,"rel":662},"https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F562",[254],"OFAC FAQ 562"," says listed digital currency addresses are not likely to be exhaustive. For CO-02, FATF adopted a ",[18,666,669],{"href":667,"rel":668},"https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002Fupdate-Recommendation-16-payment-transparency-june-2025.html",[254],"revised Recommendation 16"," on payment transparency in June 2025, with implementation expected by the end of 2030, so expect data requests to grow.",[265,672,674],{"id":673},"operations-and-technology","Operations and technology",[69,676,677,697],{},[72,678,679],{},[75,680,681,683,685,687,689,691,693,695],{},[78,682,92],{},[78,684,108],{},[78,686,116],{},[78,688,283],{},[78,690,132],{},[78,692,288],{},[78,694,291],{},[78,696,156],{},[85,698,699,723,746,769],{},[75,700,701,704,707,710,712,715,718,721],{},[90,702,703],{},"OP-01",[90,705,706],{},"Payout sent to wrong bank account",[90,708,709],{},"Manual entry; recipient changed details",[90,711,309],{},[90,713,714],{},"Validate details before the first payout; re-approval on changes; small first payout",[90,716,717],{},"2x3 = 6",[90,719,720],{},"Bank returns; detail changes per month",[90,722,549],{},[75,724,725,728,731,734,736,739,741,744],{},[90,726,727],{},"OP-02",[90,729,730],{},"Same obligation paid twice",[90,732,733],{},"Retry after a timeout",[90,735,427],{},[90,737,738],{},"Idempotency key on every create call; one internal ID per obligation",[90,740,341],{},[90,742,743],{},"Duplicate payouts found in reconciliation",[90,745,463],{},[75,747,748,751,754,757,759,762,764,767],{},[90,749,750],{},"OP-03",[90,752,753],{},"Tokens sent on the wrong network",[90,755,756],{},"Address or network mismatch",[90,758,335],{},[90,760,761],{},"Network and token fixed by the quote; allowlisted addresses",[90,763,341],{},[90,765,766],{},"Funding transactions rejected",[90,768,463],{},[75,770,771,774,777,780,783,786,789,792],{},[90,772,773],{},"OP-04",[90,775,776],{},"Payout lands after a rail's cut-off",[90,778,779],{},"Weekend, holiday, batch timing",[90,781,782],{},"4x1 = 4",[90,784,785],{},"Rail calendar in the payout scheduler; tell recipients the expected date",[90,787,788],{},"2x1 = 2",[90,790,791],{},"Payouts credited later than promised",[90,793,549],{},[11,795,796,797,801,802,806],{},"OP-02 is the cheapest to remove. A retried create call with the same ",[798,799,800],"code",{},"Idempotency-Key"," header replays the original response instead of creating a second payout (",[18,803,805],{"href":804},"\u002Fdocs\u002Flearn\u002Fidempotency","idempotency",").",[265,808,810],{"id":809},"legal-and-regulatory","Legal and regulatory",[69,812,813,833],{},[72,814,815],{},[75,816,817,819,821,823,825,827,829,831],{},[78,818,92],{},[78,820,108],{},[78,822,116],{},[78,824,283],{},[78,826,132],{},[78,828,288],{},[78,830,291],{},[78,832,156],{},[85,834,835,858],{},[75,836,837,840,843,846,848,851,853,856],{},[90,838,839],{},"LR-01",[90,841,842],{},"Rules change in a corridor you pay into",[90,844,845],{},"New stablecoin, FX, or VASP rules",[90,847,309],{},[90,849,850],{},"Dated legal sign-off per corridor; quarterly regulatory review",[90,852,717],{},[90,854,855],{},"Days since last corridor review",[90,857,347],{},[75,859,860,863,866,869,871,874,876,879],{},[90,861,862],{},"LR-02",[90,864,865],{},"Your own flow needs a license you don't hold",[90,867,868],{},"Holding customer funds or transmitting on their behalf",[90,870,513],{},[90,872,873],{},"Legal opinion on the flow before launch; licensed provider for the regulated steps",[90,875,519],{},[90,877,878],{},"Flow changes since the last opinion",[90,880,881],{},"Legal",[11,883,884,885,890,891,895],{},"US rules are moving on a schedule. The ",[18,886,889],{"href":887,"rel":888},"https:\u002F\u002Fwww.congress.gov\u002F119\u002Fbills\u002Fs1582\u002FBILLS-119s1582enr.htm",[254],"GENIUS Act",", signed in July 2025, sets deadlines measured from its enactment and effective dates, so LR-01 belongs on a calendar, not only in a table. The ",[18,892,894],{"href":893},"\u002Fresources\u002Fmore\u002Fgenius-act-timeline-key-dates","GENIUS Act timeline"," lists the dates.",[49,897,899],{"id":898},"what-do-auditors-and-banking-partners-look-for","What do auditors and banking partners look for?",[11,901,902],{},"Three things: that each risk has an owner, that indicators are measured, and that reviews happened. Rows whose score doesn't move between inherent and residual are controls that exist on paper only, so expect questions there. Keep the review log next to the register:",[904,905,911],"pre",{"className":906,"code":908,"language":909,"meta":910},[907],"language-text","REVIEW LOG\nDate        Trigger              Attendees           Changes made\n[date]      Quarterly review     [names]             [rows rescored, controls added]\n[date]      New corridor: [X]    [names]             [new rows FX-04, LR-03]\n[date]      Incident [ID]        [names]             [OP-01 residual raised to 3x3]\n","text","",[798,912,908],{"__ignoreMap":910},[49,914,916],{"id":915},"how-does-blindpay-handle-the-risks-it-owns","How does BlindPay handle the risks it owns?",[11,918,919,920,924,925,928,929,928,932,928,935,938,939,942,943,947],{},"Several controls in this register map to the provider's side of the flow. On BlindPay, each payout quote locks the rate and fees for 5 minutes (",[18,921,923],{"href":922},"\u002Fdocs\u002Fpayout-quotes","payout quotes","), KYC and KYB run in the same API, and payouts report ",[798,926,927],{},"processing",", ",[798,930,931],{},"on_hold",[798,933,934],{},"completed",[798,936,937],{},"failed",", or ",[798,940,941],{},"refunded"," through webhooks (",[18,944,946],{"href":945},"\u002Fdocs\u002Fpayouts","payouts","). 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. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.",[49,949,951],{"id":950},"what-to-do-next","What to do next",[11,953,954],{},"Paste the 16 rows into a spreadsheet, put a name in every owner cell, and rescore each row with your own volumes. Then book the first quarterly review before you send the first live payout.",{"title":910,"searchDepth":956,"depth":956,"links":957},2,[958,959,960,961,970,971,972],{"id":51,"depth":956,"text":52},{"id":63,"depth":956,"text":64},{"id":170,"depth":956,"text":171},{"id":259,"depth":956,"text":260,"children":962},[963,965,966,967,968,969],{"id":267,"depth":964,"text":268},3,{"id":364,"depth":964,"text":365},{"id":474,"depth":964,"text":475},{"id":560,"depth":964,"text":347},{"id":673,"depth":964,"text":674},{"id":809,"depth":964,"text":810},{"id":898,"depth":956,"text":899},{"id":915,"depth":956,"text":916},{"id":950,"depth":956,"text":951},"2026-10-16","A copyable risk register for cross-border stablecoin payouts: 16 risks across six categories, a 5x5 scoring method, controls, indicators, and owners.","md",[977,980,983,986,989],{"q":978,"a":979},"What is a risk register for stablecoin payments?","It is a table that lists each risk in your cross-border stablecoin payment flow, its cause, how likely it is, how much damage it would do, the control that reduces it, the indicator that warns you early, and the person who owns it. Auditors, banks, and boards ask for it because it proves risks were thought through before money moved.",{"q":981,"a":982},"Which risks belong in a cross-border stablecoin payments risk register?","Group them in six categories: stablecoin and issuer, FX and liquidity, counterparty and custody, compliance, operations and technology, and legal and regulatory. A starting register usually holds 12 to 20 rows. Depeg, wrong network, expired quotes, sanctions exposure, provider failure, bank-detail errors, and corridor rule changes appear in almost every one.",{"q":984,"a":985},"How do you score risks in the register?","Score likelihood and impact from 1 to 5 each and multiply them, so every risk lands between 1 and 25. Score twice: inherent risk before controls and residual risk after them. Write down what each number means in your business, for example impact 5 as a loss above a set amount, so two people scoring the same risk get the same result.",{"q":987,"a":988},"How often should the risk register be reviewed?","Review it quarterly, and also after any incident, any new corridor or rail, any change of provider, and any regulatory change in a corridor you pay into. Record the review date and who attended. A register with no review history reads to an auditor as a document written once for approval and then forgotten.",{"q":990,"a":991},"Who should own risks in a stablecoin payment flow?","A named person, not a team. Treasury usually owns depeg and liquidity, compliance owns sanctions, Travel Rule, and information requests, engineering owns network, quote, and duplicate-payment risks, operations owns bank details and returns, and finance owns provider and counterparty risk. The owner reports on the control and its indicator at each review.",false,{"author":994},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fcross-border-stablecoin-payments-risk-register","---\ntitle: \"Cross-border stablecoin payments risk register: a fill-in template with 16 risks, scores, and owners\"\nseoTitle: \"Cross-border stablecoin payments risk register template\"\ndescription: \"A copyable risk register for cross-border stablecoin payouts: 16 risks across six categories, a 5x5 scoring method, controls, indicators, and owners.\"\ndate: \"2026-10-16\"\nupdated: \"2026-10-16\"\ncategory: \"compliance\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a risk register for stablecoin payments?\"\n    a: \"It is a table that lists each risk in your cross-border stablecoin payment flow, its cause, how likely it is, how much damage it would do, the control that reduces it, the indicator that warns you early, and the person who owns it. Auditors, banks, and boards ask for it because it proves risks were thought through before money moved.\"\n  - q: \"Which risks belong in a cross-border stablecoin payments risk register?\"\n    a: \"Group them in six categories: stablecoin and issuer, FX and liquidity, counterparty and custody, compliance, operations and technology, and legal and regulatory. A starting register usually holds 12 to 20 rows. Depeg, wrong network, expired quotes, sanctions exposure, provider failure, bank-detail errors, and corridor rule changes appear in almost every one.\"\n  - q: \"How do you score risks in the register?\"\n    a: \"Score likelihood and impact from 1 to 5 each and multiply them, so every risk lands between 1 and 25. Score twice: inherent risk before controls and residual risk after them. Write down what each number means in your business, for example impact 5 as a loss above a set amount, so two people scoring the same risk get the same result.\"\n  - q: \"How often should the risk register be reviewed?\"\n    a: \"Review it quarterly, and also after any incident, any new corridor or rail, any change of provider, and any regulatory change in a corridor you pay into. Record the review date and who attended. A register with no review history reads to an auditor as a document written once for approval and then forgotten.\"\n  - q: \"Who should own risks in a stablecoin payment flow?\"\n    a: \"A named person, not a team. Treasury usually owns depeg and liquidity, compliance owns sanctions, Travel Rule, and information requests, engineering owns network, quote, and duplicate-payment risks, operations owns bank details and returns, and finance owns provider and counterparty risk. The owner reports on the control and its indicator at each review.\"\n---\n\nA cross-border stablecoin payments risk register lists every risk in your payout flow with its cause, a likelihood and impact score, the control that reduces it, an early-warning indicator, and a named owner. Use the template below: 16 starter risks in six categories, scored on a 5x5 scale before and after controls.\n\nIf you are new to the flow itself, read [what a stablecoin sandwich is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-sandwich) first: each layer of the sandwich adds its own risks.\n\n**Key takeaways**\n\n- Score every risk twice: inherent (no controls) and residual (with controls). The gap is what your controls are worth.\n- Most residual risk in stablecoin payouts sits in operations and compliance, not in the blockchain.\n- Every row needs an indicator you can measure weekly, or the register can't warn you of anything.\n- One owner per risk, by name. Shared ownership means nobody checks.\n- Review quarterly and after every incident, new corridor, or rule change.\n\n## How is this different from an incident playbook?\n\nA risk register is written before anything breaks; a playbook is used while something is breaking. The [blockchain payment incident playbook](\u002Fresources\u002Fmore\u002Fblockchain-payment-incident-playbook) covers the six steps once a payment goes wrong, with a short register of its own. This page adds scoring, indicators, and a starter set you can paste into a spreadsheet.\n\n## What columns should the register have?\n\nTen columns. Fewer and auditors find gaps; more and nobody keeps it current.\n\n| Column | What goes in it |\n| --- | --- |\n| ID | Short code, for example SC-01 |\n| Category | One of the six categories below |\n| Risk | What could happen, in one sentence |\n| Cause | Why it would happen |\n| Inherent score | Likelihood x impact with no controls (1 to 25) |\n| Controls | What you do to reduce it |\n| Residual score | Likelihood x impact with controls in place |\n| Key risk indicator | A number you can measure that rises before the risk hits |\n| Owner | One named person |\n| Last reviewed | Date and reviewer |\n\n## How do you score likelihood and impact?\n\nUse a 1 to 5 scale for each and multiply. Define the scale in your own numbers before you score anything.\n\n| Score | Likelihood | Impact (example definitions, set your own) |\n| --- | --- | --- |\n| 1 | Less than once in 5 years | Loss under a small set amount; no customer affected |\n| 2 | Once in 2 to 5 years | Small loss; a few payouts delayed by a day |\n| 3 | Once a year | Moderate loss; a corridor paused for a day |\n| 4 | Several times a year | Large loss; many customers affected; regulator notification possible |\n| 5 | Monthly or more | Loss that threatens the program; license or banking relationship at risk |\n\nScores of 15 and above need a control plan and a sponsor sign-off. Scores of 8 to 14 need an owner and an indicator. Below 8, record the risk and review it quarterly. This tiering follows the logic of enterprise risk frameworks such as [COSO's enterprise risk management guidance](https:\u002F\u002Fwww.coso.org\u002Fenterprise-risk-management): tie risk appetite to what the business can absorb, then act on what exceeds it.\n\n## What are the 16 starter risks?\n\nCopy these rows, then rescore them for your volumes and corridors. The scores below are illustrative, for a mid-size payout program, not a benchmark.\n\n### Stablecoin and issuer\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| SC-01 | Stablecoin trades below one dollar while you hold it | Reserve problem at the issuer | 3x4 = 12 | Hold for minutes, not days; cap holdings per token; execute only against locked quotes | 2x2 = 4 | Market price of each token you hold; hours of holdings | Treasury |\n| SC-02 | Issuer freezes a token at an address you pay from or to | Address linked to illicit activity | 2x4 = 8 | Wallet screening before sending; registered wallets only | 1x3 = 3 | Screening alerts per month | Compliance |\n\nThe depeg row is not theoretical. When Silicon Valley Bank failed in March 2023, USDC traded as low as 86 cents, per a [December 2025 Federal Reserve note](https:\u002F\u002Fwww.federalreserve.gov\u002Feconres\u002Fnotes\u002Ffeds-notes\u002Fin-the-shadow-of-bank-run-lessons-from-the-silicon-valley-bank-failure-and-its-impact-on-stablecoins-20251217.html). It recovered within days. A payment flow that converts within minutes is far less exposed than a treasury that holds for weeks, which is why holding time is the indicator. [Stablecoin depeg risk for payment companies](\u002Fresources\u002Fmore\u002Fstablecoin-depeg-risk-payments) covers the limits in detail.\n\n### FX and liquidity\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| FX-01 | Rate moves between approval and execution | Slow approvals; quote expiry | 4x2 = 8 | Approve intent, then execute within the quote window; re-quote tolerance in the FX policy | 2x2 = 4 | Quote expiry rate; re-quote delta | Treasury |\n| FX-02 | Thin local-currency liquidity on a large payout | Payout size above what the corridor absorbs at a good price | 3x3 = 9 | Split large payouts; test depth with quotes at several sizes | 2x2 = 4 | Spread versus mid-market by payout size | Treasury |\n| FX-03 | Funds stuck on the wrong chain for the corridor | Treasury holds USDC on a network the payout doesn't take | 3x2 = 6 | Map each corridor to supported networks; rebalance ahead of payout runs | 1x2 = 2 | Payouts blocked by network mismatch | Engineering |\n\nMeasure FX-01 before you set a tolerance. [Payout quality metrics](\u002Fresources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate) defines quote expiry rate and re-quote delta.\n\n### Counterparty and custody\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| CP-01 | Payout provider fails or freezes operations | Insolvency, license loss, banking partner loss | 2x5 = 10 | Know who holds funds at each step; avoid idle balances at the provider; second provider for top corridor | 1x4 = 4 | Idle balance at provider; provider status page incidents | Finance |\n| CP-02 | Payout fails after the stablecoins were collected | Recipient bank rejects; review times out | 3x3 = 9 | Written refund rules per rail; status webhooks into your ledger; refund wallet set on each quote | 2x2 = 4 | Payouts in failed or refunded per week; days to refund | Operations |\n\nFor CP-01, map the failure modes in [what happens if a stablecoin payment provider fails](\u002Fresources\u002Fmore\u002Fwhat-happens-if-a-stablecoin-payment-provider-fails) before you sign.\n\n### Compliance\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| CO-01 | Payment to a sanctioned person or address | Recipient or wallet on a sanctions list | 2x5 = 10 | Screen recipients and wallets before the first payout and on list updates | 1x5 = 5 | Screening hits; time since last rescreen | Compliance |\n| CO-02 | Travel Rule data missing on a transfer | Counterparty provider asks for originator or beneficiary data you didn't collect | 3x3 = 9 | Collect originator and beneficiary data at onboarding | 2x2 = 4 | Transfers held for missing data | Compliance |\n| CO-03 | Customer or payout held for a request for information | Incomplete KYC or KYB, unusual activity | 4x2 = 8 | Answer within days, not weeks; keep invoices and source-of-funds documents ready | 3x1 = 3 | Open information requests and their age | Compliance |\n\nSanctions screening on wallets needs analytics, not just a list check: [OFAC FAQ 562](https:\u002F\u002Fofac.treasury.gov\u002Ffaqs\u002F562) says listed digital currency addresses are not likely to be exhaustive. For CO-02, FATF adopted a [revised 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, with implementation expected by the end of 2030, so expect data requests to grow.\n\n### Operations and technology\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| OP-01 | Payout sent to wrong bank account | Manual entry; recipient changed details | 3x4 = 12 | Validate details before the first payout; re-approval on changes; small first payout | 2x3 = 6 | Bank returns; detail changes per month | Operations |\n| OP-02 | Same obligation paid twice | Retry after a timeout | 3x3 = 9 | Idempotency key on every create call; one internal ID per obligation | 1x3 = 3 | Duplicate payouts found in reconciliation | Engineering |\n| OP-03 | Tokens sent on the wrong network | Address or network mismatch | 2x4 = 8 | Network and token fixed by the quote; allowlisted addresses | 1x3 = 3 | Funding transactions rejected | Engineering |\n| OP-04 | Payout lands after a rail's cut-off | Weekend, holiday, batch timing | 4x1 = 4 | Rail calendar in the payout scheduler; tell recipients the expected date | 2x1 = 2 | Payouts credited later than promised | Operations |\n\nOP-02 is the cheapest to remove. A retried create call with the same `Idempotency-Key` header replays the original response instead of creating a second payout ([idempotency](\u002Fdocs\u002Flearn\u002Fidempotency)).\n\n### Legal and regulatory\n\n| ID | Risk | Cause | Inherent | Controls | Residual | Indicator | Owner |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| LR-01 | Rules change in a corridor you pay into | New stablecoin, FX, or VASP rules | 3x4 = 12 | Dated legal sign-off per corridor; quarterly regulatory review | 2x3 = 6 | Days since last corridor review | Compliance |\n| LR-02 | Your own flow needs a license you don't hold | Holding customer funds or transmitting on their behalf | 2x5 = 10 | Legal opinion on the flow before launch; licensed provider for the regulated steps | 1x4 = 4 | Flow changes since the last opinion | Legal |\n\nUS rules are moving on a schedule. The [GENIUS Act](https:\u002F\u002Fwww.congress.gov\u002F119\u002Fbills\u002Fs1582\u002FBILLS-119s1582enr.htm), signed in July 2025, sets deadlines measured from its enactment and effective dates, so LR-01 belongs on a calendar, not only in a table. The [GENIUS Act timeline](\u002Fresources\u002Fmore\u002Fgenius-act-timeline-key-dates) lists the dates.\n\n## What do auditors and banking partners look for?\n\nThree things: that each risk has an owner, that indicators are measured, and that reviews happened. Rows whose score doesn't move between inherent and residual are controls that exist on paper only, so expect questions there. Keep the review log next to the register:\n\n```text\nREVIEW LOG\nDate        Trigger              Attendees           Changes made\n[date]      Quarterly review     [names]             [rows rescored, controls added]\n[date]      New corridor: [X]    [names]             [new rows FX-04, LR-03]\n[date]      Incident [ID]        [names]             [OP-01 residual raised to 3x3]\n```\n\n## How does BlindPay handle the risks it owns?\n\nSeveral controls in this register map to the provider's side of the flow. On BlindPay, each payout quote locks the rate and fees for 5 minutes ([payout quotes](\u002Fdocs\u002Fpayout-quotes)), KYC and KYB run in the same API, and payouts report `processing`, `on_hold`, `completed`, `failed`, or `refunded` through webhooks ([payouts](\u002Fdocs\u002Fpayouts)). 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. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.\n\n## What to do next\n\nPaste the 16 rows into a spreadsheet, put a name in every owner cell, and rescore each row with your own volumes. Then book the first quarterly review before you send the first live payout.\n",{"title":5,"description":974},"Cross-border stablecoin payments risk register template","resources\u002Fmore\u002Fcross-border-stablecoin-payments-risk-register","vkz9MvKgHdDmH-XPwQheZFpkOmDk4nb8jKpiCWUkHNw",[1003,1007,1011,1015,1019,1023,1027,1031,1035,1039,1043,1044,1048,1052,1056,1060,1064,1067,1071,1075,1079,1083,1087,1091,1095,1099,1103,1107,1111,1115,1119,1123,1127,1131,1135,1139,1143,1147,1151,1155,1159,1163,1167,1171,1175,1178,1182,1186,1190,1194,1198,1202,1206,1210],{"path":1004,"title":1005,"description":1006},"\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":1008,"title":1009,"description":1010},"\u002Fresources\u002Fmore\u002Fneobank-remittance-feature-us-rules","Adding remittances to a US neobank: the Remittance Transfer Rule, disclosures, and pricing","How to add a low-fee remittance feature to a US neobank: when the Remittance Transfer Rule applies, disclosures, 30-minute cancellation, and pricing.",{"path":1012,"title":1013,"description":1014},"\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":1016,"title":1017,"description":1018},"\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":1020,"title":1021,"description":1022},"\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":1024,"title":1025,"description":1026},"\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":1028,"title":1029,"description":1030},"\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":1032,"title":1033,"description":1034},"\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":1036,"title":1037,"description":1038},"\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":1040,"title":1041,"description":1042},"\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":996,"title":5,"description":974},{"path":1045,"title":1046,"description":1047},"\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":1049,"title":1050,"description":1051},"\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":1053,"title":1054,"description":1055},"\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":1057,"title":1058,"description":1059},"\u002Fresources\u002Fmore\u002Fdo-stablecoin-cards-require-kyc","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":1061,"title":1062,"description":1063},"\u002Fresources\u002Fmore\u002Fdo-you-need-a-banking-license-for-a-neobank","Do you need a banking license to launch a neobank? Four routes compared","Most neobanks launch without a bank charter. Compare the four routes, from own charter to embedded providers, in the US, Brazil, Mexico, and the EU.",{"path":893,"title":1065,"description":1066},"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":1068,"title":1069,"description":1070},"\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":1072,"title":1073,"description":1074},"\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":1076,"title":1077,"description":1078},"\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":1080,"title":1081,"description":1082},"\u002Fresources\u002Fmore\u002Fhow-to-verify-non-custodial-payment-provider","How to verify a payment provider is really non-custodial: 8 checks you can run yourself","Eight checks that prove whether a blockchain payment provider ever holds your funds: on-chain approvals, stored balances, terms of title, failure tests.",{"path":1084,"title":1085,"description":1086},"\u002Fresources\u002Fmore\u002Fhow-wallet-screening-works-stablecoin-payments","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":1088,"title":1089,"description":1090},"\u002Fresources\u002Fmore\u002Fkyc-vs-kyb-vs-kyt","KYC vs KYB vs KYT: what each check covers in blockchain payments","KYC verifies people, KYB verifies businesses and their owners, and KYT watches transactions and wallets. What each covers, when it runs, and who owns it.",{"path":1092,"title":1093,"description":1094},"\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":1096,"title":1097,"description":1098},"\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":1100,"title":1101,"description":1102},"\u002Fresources\u002Fmore\u002Fneobank-kyc-kyb-onboarding-flow","Neobank KYC and KYB onboarding: screen order, tiered limits, and fewer drop-offs","How to design neobank KYC and KYB onboarding: screen order, which checks run when, tiered limits, rejections, RFIs, and what to log for audits.",{"path":1104,"title":1105,"description":1106},"\u002Fresources\u002Fmore\u002Fneobank-compliance-checklist-stablecoin-rails","Neobank compliance checklist for stablecoin rails: 20 items, owners, and evidence","A 20-item compliance checklist for neobanks on stablecoin rails: AML program, KYC, sanctions, Travel Rule, records, licensing, and evidence to keep.",{"path":1108,"title":1109,"description":1110},"\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen","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":1112,"title":1113,"description":1114},"\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":1116,"title":1117,"description":1118},"\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":1120,"title":1121,"description":1122},"\u002Fresources\u002Fmore\u002Fblockchain-payment-provider-red-flags","Red flags when choosing a blockchain payments provider: 10 warning signs and what to ask","Ten warning signs to catch before you sign with a blockchain payments provider, how each shows up in a sales call or sandbox, and the question to ask.",{"path":1124,"title":1125,"description":1126},"\u002Fresources\u002Fmore\u002Fstablecoin-card-and-payout-compliance-map","Stablecoin card and payout compliance map: who owns KYC, KYB, sanctions, and the Travel Rule","A compliance map for programs that run stablecoin cards and payouts together: KYC, KYB, monitoring, sanctions, Travel Rule, and records, split by owner.",{"path":1128,"title":1129,"description":1130},"\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":1132,"title":1133,"description":1134},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-europe-mica","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":1136,"title":1137,"description":1138},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-united-states-regulation","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":1140,"title":1141,"description":1142},"\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":1144,"title":1145,"description":1146},"\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":1148,"title":1149,"description":1150},"\u002Fresources\u002Fmore\u002Fstablecoin-regulation-uk-singapore-hong-kong","Stablecoin regulation in the UK, Singapore, and Hong Kong: where each regime stands in 2026","UK rules start 25 October 2027, Singapore is consulting on its stablecoin law, and Hong Kong licensed its first issuers in April 2026.",{"path":1152,"title":1153,"description":1154},"\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":1156,"title":1157,"description":1158},"\u002Fresources\u002Fmore\u002Ftravel-rule-workflow-hold-return-reject","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":1160,"title":1161,"description":1162},"\u002Fresources\u002Fmore\u002Ftransaction-monitoring-red-flags-stablecoin-payments","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":1164,"title":1165,"description":1166},"\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":1168,"title":1169,"description":1170},"\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":1172,"title":1173,"description":1174},"\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":555,"title":1176,"description":1177},"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":1179,"title":1180,"description":1181},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","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":1183,"title":1184,"description":1185},"\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":1187,"title":1188,"description":1189},"\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":1191,"title":1192,"description":1193},"\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":1195,"title":1196,"description":1197},"\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":1199,"title":1200,"description":1201},"\u002Fresources\u002Fmore\u002Fwhere-neobanks-hold-customer-funds","Where does a neobank hold customer funds? FBO accounts, custodial wallets, and non-custodial flows","Pooled FBO bank accounts, custodial stablecoin wallets, or customer-controlled wallets: who holds the money, who reconciles it, and what fails.",{"path":1203,"title":1204,"description":1205},"\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":1207,"title":1208,"description":1209},"\u002Fresources\u002Fmore\u002Fcross-border-payout-rfi-how-to-answer","Why did my cross-border payout get an RFI? What compliance asks, and how to answer fast","A request for information pauses a customer or holds a payout until compliance gets answers. The three RFI types, their deadlines, and how to answer.",{"path":1211,"title":1212,"description":1213},"\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.",1793136747666]