[{"data":1,"prerenderedAt":1005},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fneobank-kyc-kyb-onboarding-flow":3,"resources-category-neobank-kyc-kyb-onboarding-flow":796},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":748,"categoryType":6,"compare":6,"contributors":6,"date":749,"description":750,"extension":751,"faq":752,"howto":768,"isBlog":786,"isChangelog":786,"meta":787,"navigation":789,"path":790,"pillar":786,"products":6,"rawbody":791,"role":6,"seo":792,"seoTitle":793,"stem":794,"thumbnail":6,"updated":749,"__hash__":795},"content\u002Fresources\u002Fmore\u002Fneobank-kyc-kyb-onboarding-flow.md","Neobank KYC and KYB onboarding: screen order, tiered limits, and fewer drop-offs",null,{"type":8,"value":9,"toc":733},"minimark",[10,14,23,26,32,51,56,59,78,82,85,209,217,221,224,242,250,254,257,348,362,366,369,378,381,440,453,457,460,519,522,526,529,579,599,603,606,623,632,636,661,665,668,714,721,725],[11,12,13],"p",{},"Design neobank onboarding as a short funnel: consent, basic details, identity data and documents, an automated check, then a decision with limits that match the verification tier. Ask for more (source of funds, business ownership papers) only when the account needs it. BlindPay runs KYC and KYB inside its API, so the app owns the screens while BlindPay owns the checks for its payment flow.",[11,15,16,17,22],{},"Onboarding is where most neobanks lose users and where most audits start. This guide covers the screen order, which checks run when, how to handle rejections and requests for information, and what to keep for examiners. It is part of our ",[18,19,21],"a",{"href":20},"\u002Fresources\u002Fmore\u002Fhow-to-build-a-neobank","guide to building a neobank",".",[11,24,25],{},"This is educational content, not legal advice.",[11,27,28],{},[29,30,31],"strong",{},"Key takeaways",[33,34,35,39,42,45,48],"ul",{},[36,37,38],"li",{},"Ask for country first. It decides the tier, the documents, and whether review is automated.",[36,40,41],{},"Tiered limits let you approve fast on light data and ask for more only when activity grows.",[36,43,44],{},"Rejections need human-readable fixes. Requests for information should ask only for what's missing.",[36,46,47],{},"KYB is slower by design: ownership and control need a human review.",[36,49,50],{},"Log decisions and evidence, not just statuses.",[52,53,55],"h2",{"id":54},"what-is-the-difference-between-kyc-and-kyb-in-a-neobank","What is the difference between KYC and KYB in a neobank?",[11,57,58],{},"KYC verifies a person. KYB verifies a business and the people who own or control it.",[11,60,61,62,68,69,73,74,22],{},"For an individual, you collect identity data, check an ID document against a selfie, and screen the name against sanctions and PEP lists. For a business, you verify the company exists, then run KYC on its owners. Under the US ",[18,63,67],{"href":64,"rel":65},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.230",[66],"nofollow","beneficial ownership rule",", that means each person owning 25 percent or more of the equity, plus one individual with responsibility to control, manage, or direct the company. If you need definitions first, start with ",[18,70,72],{"href":71},"\u002Fresources\u002Fmore\u002Fkyc-vs-kyb-vs-kyt","KYC vs KYB vs KYT"," and ",[18,75,77],{"href":76},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","what KYB verifies",[52,79,81],{"id":80},"what-data-should-each-onboarding-step-collect","What data should each onboarding step collect?",[11,83,84],{},"Collect in the order that gets to a decision soonest. Here is a typical individual flow, with the check each step feeds.",[86,87,88,107],"table",{},[89,90,91],"thead",{},[92,93,94,98,101,104],"tr",{},[95,96,97],"th",{},"Step",[95,99,100],{},"Screen",[95,102,103],{},"Data",[95,105,106],{},"Check it feeds",[108,109,110,125,139,153,167,181,195],"tbody",{},[92,111,112,116,119,122],{},[113,114,115],"td",{},"1",[113,117,118],{},"Welcome",[113,120,121],{},"Terms of service, privacy notice, consent",[113,123,124],{},"Legal basis to process data",[92,126,127,130,133,136],{},[113,128,129],{},"2",[113,131,132],{},"About you",[113,134,135],{},"Name, email, country, date of birth",[113,137,138],{},"Tier selection, sanctions and PEP screening",[92,140,141,144,147,150],{},[113,142,143],{},"3",[113,145,146],{},"Identity details",[113,148,149],{},"Tax ID, phone, address",[113,151,152],{},"Identity match, address checks",[92,154,155,158,161,164],{},[113,156,157],{},"4",[113,159,160],{},"Document",[113,162,163],{},"ID type and country, front, back if needed",[113,165,166],{},"Document authenticity",[92,168,169,172,175,178],{},[113,170,171],{},"5",[113,173,174],{},"Selfie",[113,176,177],{},"Live photo",[113,179,180],{},"Face match against the document",[92,182,183,186,189,192],{},[113,184,185],{},"6",[113,187,188],{},"Review",[113,190,191],{},"Summary and submit",[113,193,194],{},"Automated decision or manual review",[92,196,197,200,203,206],{},[113,198,199],{},"Later",[113,201,202],{},"Limits",[113,204,205],{},"Source of funds, purpose of transactions",[113,207,208],{},"Enhanced review, higher limits",[11,210,211,212,216],{},"On BlindPay, the ",[18,213,215],{"href":214},"\u002Fdocs\u002Flearn\u002Fcustomers","customer data requirements"," follow this split. KYC Standard asks for the core identity fields, an ID document, and a selfie. KYC Enhanced adds a source of funds document and the purpose of transactions.",[52,218,220],{"id":219},"how-does-business-onboarding-kyb-work","How does business onboarding (KYB) work?",[11,222,223],{},"Business onboarding runs company checks first, then KYC on each owner.",[225,226,227,230,233,236,239],"ol",{},[36,228,229],{},"Collect legal name, tax ID, formation date, country, and address.",[36,231,232],{},"Upload the formation document and a proof of ownership document.",[36,234,235],{},"List beneficial owners above 25 percent and a control person, each with their own KYC data.",[36,237,238],{},"Screen the company and every owner.",[36,240,241],{},"Route to manual review and show a waiting state.",[11,243,244,245,249],{},"BlindPay's ",[18,246,248],{"href":247},"\u002Fdocs\u002Fkb\u002Fkyb-documents","KYB document list"," shows what reviewers expect. Plan for manual review on every business: on BlindPay, KYB Standard always goes to the compliance team for manual review.",[52,251,253],{"id":252},"which-checks-run-when","Which checks run when?",[11,255,256],{},"Some checks run once at signup, some on every transaction, some on a schedule.",[86,258,259,272],{},[89,260,261],{},[92,262,263,266,269],{},[95,264,265],{},"Check",[95,267,268],{},"When it runs",[95,270,271],{},"Who usually runs it",[108,273,274,285,294,305,315,326,337],{},[92,275,276,279,282],{},[113,277,278],{},"Identity verification",[113,280,281],{},"Signup",[113,283,284],{},"Verification provider",[92,286,287,290,292],{},[113,288,289],{},"Document and selfie match",[113,291,281],{},[113,293,284],{},[92,295,296,299,302],{},[113,297,298],{},"Sanctions and PEP screening",[113,300,301],{},"Signup, then on list updates",[113,303,304],{},"You and your payment provider",[92,306,307,310,312],{},[113,308,309],{},"Country risk tiering",[113,311,281],{},[113,313,314],{},"Your rules plus provider rules",[92,316,317,320,323],{},[113,318,319],{},"Transaction screening and Travel Rule",[113,321,322],{},"Each payin and payout",[113,324,325],{},"Payment provider",[92,327,328,331,334],{},[113,329,330],{},"Rescreening",[113,332,333],{},"When lists change or on a schedule",[113,335,336],{},"You and your provider",[92,338,339,342,345],{},[113,340,341],{},"Enhanced review",[113,343,344],{},"Higher risk or higher limits",[113,346,347],{},"Compliance team",[11,349,350,351,356,357,361],{},"Sanctions lists change often. The ",[18,352,355],{"href":353,"rel":354},"https:\u002F\u002Fsanctionssearch.ofac.treas.gov\u002F",[66],"OFAC sanctions list search"," is the public reference for US lists, and our guide on ",[18,358,360],{"href":359},"\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen","how often to rescreen"," covers ongoing screening.",[52,363,365],{"id":364},"how-do-tiered-limits-cut-drop-off","How do tiered limits cut drop-off?",[11,367,368],{},"Tiers let you approve on less data and ask for more only when the customer needs it.",[11,370,371,372,377],{},"Instead of asking every user for bank statements on day one, start with standard verification and default limits. When a user wants to send more, ask for source of funds then. The ",[18,373,376],{"href":374,"rel":375},"https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002FFatf-recommendations.html",[66],"FATF Recommendations"," describe this risk-based approach to customer due diligence.",[11,379,380],{},"BlindPay's default limits, measured on the stablecoin amount, show how this works in practice:",[86,382,383,399],{},[89,384,385],{},[92,386,387,390,393,396],{},[95,388,389],{},"Limit",[95,391,392],{},"KYC Standard",[95,394,395],{},"KYB Standard",[95,397,398],{},"KYC Enhanced",[108,400,401,415,427],{},[92,402,403,406,409,412],{},[113,404,405],{},"Per transaction",[113,407,408],{},"US$10,000",[113,410,411],{},"US$30,000",[113,413,414],{},"US$50,000",[92,416,417,420,422,425],{},[113,418,419],{},"Daily",[113,421,414],{},[113,423,424],{},"US$100,000",[113,426,424],{},[92,428,429,432,434,437],{},[113,430,431],{},"Monthly",[113,433,424],{},[113,435,436],{},"US$250,000",[113,438,439],{},"US$500,000",[11,441,442,443,447,448,452],{},"When a customer needs more, a ",[18,444,446],{"href":445},"\u002Fdocs\u002Flearn\u002Flimit-increase","limit increase request"," goes in with a supporting document, and compliance decides. Our guide to ",[18,449,451],{"href":450},"\u002Fresources\u002Fmore\u002Fsource-of-funds-crypto-off-ramps","source of funds requests"," covers which documents work.",[52,454,456],{"id":455},"worked-example-where-does-a-funnel-lose-users","Worked example: where does a funnel lose users?",[11,458,459],{},"Illustrative numbers, not data from any real app. A neobank starts 1,000 signups in a month.",[86,461,462,474],{},[89,463,464],{},[92,465,466,468,471],{},[95,467,97],{},[95,469,470],{},"Users who finish",[95,472,473],{},"Lost at this step",[108,475,476,487,497,508],{},[92,477,478,481,484],{},[113,479,480],{},"Basics",[113,482,483],{},"900",[113,485,486],{},"100",[92,488,489,491,494],{},[113,490,146],{},[113,492,493],{},"780",[113,495,496],{},"120",[92,498,499,502,505],{},[113,500,501],{},"Document and selfie",[113,503,504],{},"620",[113,506,507],{},"160",[92,509,510,513,516],{},[113,511,512],{},"Automated approval",[113,514,515],{},"560",[113,517,518],{},"60 (manual review or rejection)",[11,520,521],{},"The document step loses the most. Three fixes target it: use the camera with an on-screen frame, check blur and glare before upload, and let users resume on another device. If the team instead asked for a bank statement at signup, every user would hit a fourth upload. Deferring it to the limit increase moves that friction to the few who need it.",[52,523,525],{"id":524},"how-should-rejections-and-requests-for-information-work","How should rejections and requests for information work?",[11,527,528],{},"Treat them as product flows, not dead ends.",[33,530,531,546,569],{},[36,532,533,536,537,541,542,545],{},[29,534,535],{},"Rejection."," Show the reason in plain words and what to do next. On BlindPay, feedback arrives in ",[538,539,540],"code",{},"kyc_warnings"," or ",[538,543,544],{},"fraud_warnings",", and a retry means creating a new customer with corrected data.",[36,547,548,551,552,555,556,559,560,564,565,568],{},[29,549,550],{},"Request for information."," Compliance pauses the review and asks for specific items. On BlindPay, a ",[538,553,554],{},"customer.update"," webhook moves the customer to ",[538,557,558],{},"compliance_request",", you fetch the open ",[18,561,563],{"href":562},"\u002Fdocs\u002Flearn\u002Frfi","RFI",", collect only those fields in your UI, and submit them. The status returns to ",[538,566,567],{},"verifying"," while BlindPay re-reviews.",[36,570,571,574,575,578],{},[29,572,573],{},"Approved with an open RFI."," The customer can transact (",[538,576,577],{},"approved_rfi",") while the request stays open. Remind them before it becomes a block.",[11,580,581,582,584,585,584,588,584,591,584,594,596,597,22],{},"Statuses to map to screens: ",[538,583,567],{},", ",[538,586,587],{},"approved",[538,589,590],{},"rejected",[538,592,593],{},"pending_review",[538,595,558],{},", and ",[538,598,577],{},[52,600,602],{"id":601},"what-should-you-log-for-audits","What should you log for audits?",[11,604,605],{},"Log the decision path, not only the final status.",[33,607,608,611,614,617,620],{},[36,609,610],{},"Data and documents submitted, with timestamps and the tier.",[36,612,613],{},"Each check's result: identity, document, selfie, sanctions, PEP.",[36,615,616],{},"Manual reviewer, decision, and reason.",[36,618,619],{},"Requests for information, responses, and dates.",[36,621,622],{},"Limit changes and the documents behind them.",[11,624,625,626,631],{},"US BSA recordkeeping rules ",[18,627,630],{"href":628,"rel":629},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.430",[66],"require five-year retention"," for records kept under that chapter. Keep yours at least that long unless counsel says otherwise.",[52,633,635],{"id":634},"what-are-common-onboarding-mistakes","What are common onboarding mistakes?",[33,637,638,641,644,647,650,653],{},[36,639,640],{},"Asking for every document up front, including ones only high-limit users need.",[36,642,643],{},"Asking for country last, after the user has already uploaded a document the tier won't accept.",[36,645,646],{},"Showing a raw error code on rejection.",[36,648,649],{},"Letting users edit identity data after approval without re-verification.",[36,651,652],{},"Running sanctions screening once and never again.",[36,654,655,656,541,658,660],{},"Logging only ",[538,657,587],{},[538,659,590],{}," with no evidence.",[52,662,664],{"id":663},"how-does-blindpay-fit","How does BlindPay fit?",[11,666,667],{},"BlindPay puts KYC and KYB inside the payments API, so a neobank builds the screens and BlindPay runs the checks for its payins, payouts, and virtual accounts.",[33,669,670,685,696,702,708],{},[36,671,672,675,676,680,681,684],{},[29,673,674],{},"Consent first."," Each customer accepts BlindPay's ",[18,677,679],{"href":678},"\u002Fdocs\u002Flearn\u002Fterms-of-service","terms of service"," on a hosted page, which returns a ",[538,682,683],{},"tos_id"," you pass when creating the customer.",[36,686,687,690,691,695],{},[29,688,689],{},"Two KYC tiers."," KYC Standard is automated and typically completes in about 60 seconds. KYC Enhanced adds source of funds and purpose of transactions and is reviewed manually. Individuals from ",[18,692,694],{"href":693},"\u002Fdocs\u002Fkb\u002Fsupported-countries","high-risk countries"," must use Enhanced.",[36,697,698,701],{},[29,699,700],{},"KYB with ownership."," Owners above 25 percent are verified with their own KYC data.",[36,703,704,707],{},[29,705,706],{},"Statuses by webhook,"," so your app can show the right screen at each step.",[36,709,710,713],{},[29,711,712],{},"Default limits per tier"," with a documented increase path.",[11,715,716,717,22],{},"Your own obligations still apply to anything outside BlindPay's flow, such as balances you hold in your ledger. For the licensing side, see ",[18,718,720],{"href":719},"\u002Fresources\u002Fmore\u002Fdo-you-need-a-banking-license-for-a-neobank","do you need a banking license",[52,722,724],{"id":723},"what-to-do-next","What to do next",[11,726,727,728,732],{},"Sketch your onboarding screens against the table above, then create test customers on a development instance, where KYC is auto-approved, to wire every status to a screen. The ",[18,729,731],{"href":730},"\u002Fdocs\u002Fkb\u002Fkyc-basics","KYC basics guide"," lists the photo rules to put on your document screen.",{"title":734,"searchDepth":735,"depth":735,"links":736},"",2,[737,738,739,740,741,742,743,744,745,746,747],{"id":54,"depth":735,"text":55},{"id":80,"depth":735,"text":81},{"id":219,"depth":735,"text":220},{"id":252,"depth":735,"text":253},{"id":364,"depth":735,"text":365},{"id":455,"depth":735,"text":456},{"id":524,"depth":735,"text":525},{"id":601,"depth":735,"text":602},{"id":634,"depth":735,"text":635},{"id":663,"depth":735,"text":664},{"id":723,"depth":735,"text":724},"compliance","2026-10-08","How to design neobank KYC and KYB onboarding: screen order, which checks run when, tiered limits, rejections, RFIs, and what to log for audits.","md",[753,756,759,762,765],{"q":754,"a":755},"What is the difference between KYC and KYB onboarding in a neobank?","KYC verifies a person: identity, address, tax ID, and a selfie against an ID document, plus sanctions and PEP screening. KYB verifies a company: legal name, registration, formation documents, and the people behind it. In the US, beneficial owners are anyone owning 25 percent or more plus one person who controls or manages the company. Business onboarding takes longer because ownership documents usually need a human review.",{"q":757,"a":758},"How long does neobank KYC take?","Automated KYC can finish in about a minute when the document and selfie are clean. On BlindPay, KYC Standard is automated and typically completes in about 60 seconds. Enhanced KYC, required for individuals from high-risk countries, is reviewed manually and typically takes up to one business day. Business verification always goes through manual review, so plan a waiting state into the app.",{"q":760,"a":761},"How do neobanks reduce onboarding drop-off?","Ask for the minimum first and defer the rest. Collect country early so you know the tier, use the phone camera for documents, check photo quality before upload, save progress between sessions, and show a clear waiting state. Ask for source of funds only when a customer needs higher limits instead of on day one. Each extra field at signup costs completions.",{"q":763,"a":764},"What should a neobank do when KYC is rejected?","Tell the user what to fix in plain words, not a code. Common causes are blurry documents, a name or birth date that doesn't match the ID, and a screenshot instead of a photo. On BlindPay, rejection feedback arrives in warning fields on the customer, and a retry means creating a new customer with corrected data rather than editing the rejected one.",{"q":766,"a":767},"What should a neobank log for KYC audits?","Log who was verified, at which tier, with which data and documents, what each check returned, who reviewed manual cases, and when. Keep sanctions screening results and any requests for information with their responses. US BSA rules generally require records to be kept for five years. Store decisions, not just final statuses, so an examiner can follow the path.",{"name":769,"steps":770},"How to design KYC onboarding for a neobank",[771,774,777,780,783],{"name":772,"text":773},"Collect consent and the basics","Show the terms of service and privacy notice first, then ask for name, email, country, and date of birth. Country decides the verification tier, so ask for it early.",{"name":775,"text":776},"Capture identity data and documents","Collect tax ID, address, and an ID document with a selfie. Use the camera on mobile and check image quality before upload.",{"name":778,"text":779},"Submit and show a waiting state","Send the data to your verification provider and show a clear waiting screen. Automated checks often finish in about a minute; manual reviews take longer.",{"name":781,"text":782},"Handle the decision","On approval, open the account with the limits of that tier. On rejection, show what to fix. On a request for information, ask only for the missing items.",{"name":784,"text":785},"Raise limits when activity needs it","Start every customer on default limits and collect source of funds or other documents only when a customer needs more.",false,{"author":788},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fneobank-kyc-kyb-onboarding-flow","---\ntitle: \"Neobank KYC and KYB onboarding: screen order, tiered limits, and fewer drop-offs\"\nseoTitle: \"Neobank KYC and KYB onboarding: flow, checks, mistakes\"\ndescription: \"How to design neobank KYC and KYB onboarding: screen order, which checks run when, tiered limits, rejections, RFIs, and what to log for audits.\"\ndate: \"2026-10-08\"\nupdated: \"2026-10-08\"\ncategory: \"compliance\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to design KYC onboarding for a neobank\"\n  steps:\n    - name: \"Collect consent and the basics\"\n      text: \"Show the terms of service and privacy notice first, then ask for name, email, country, and date of birth. Country decides the verification tier, so ask for it early.\"\n    - name: \"Capture identity data and documents\"\n      text: \"Collect tax ID, address, and an ID document with a selfie. Use the camera on mobile and check image quality before upload.\"\n    - name: \"Submit and show a waiting state\"\n      text: \"Send the data to your verification provider and show a clear waiting screen. Automated checks often finish in about a minute; manual reviews take longer.\"\n    - name: \"Handle the decision\"\n      text: \"On approval, open the account with the limits of that tier. On rejection, show what to fix. On a request for information, ask only for the missing items.\"\n    - name: \"Raise limits when activity needs it\"\n      text: \"Start every customer on default limits and collect source of funds or other documents only when a customer needs more.\"\nfaq:\n  - q: \"What is the difference between KYC and KYB onboarding in a neobank?\"\n    a: \"KYC verifies a person: identity, address, tax ID, and a selfie against an ID document, plus sanctions and PEP screening. KYB verifies a company: legal name, registration, formation documents, and the people behind it. In the US, beneficial owners are anyone owning 25 percent or more plus one person who controls or manages the company. Business onboarding takes longer because ownership documents usually need a human review.\"\n  - q: \"How long does neobank KYC take?\"\n    a: \"Automated KYC can finish in about a minute when the document and selfie are clean. On BlindPay, KYC Standard is automated and typically completes in about 60 seconds. Enhanced KYC, required for individuals from high-risk countries, is reviewed manually and typically takes up to one business day. Business verification always goes through manual review, so plan a waiting state into the app.\"\n  - q: \"How do neobanks reduce onboarding drop-off?\"\n    a: \"Ask for the minimum first and defer the rest. Collect country early so you know the tier, use the phone camera for documents, check photo quality before upload, save progress between sessions, and show a clear waiting state. Ask for source of funds only when a customer needs higher limits instead of on day one. Each extra field at signup costs completions.\"\n  - q: \"What should a neobank do when KYC is rejected?\"\n    a: \"Tell the user what to fix in plain words, not a code. Common causes are blurry documents, a name or birth date that doesn't match the ID, and a screenshot instead of a photo. On BlindPay, rejection feedback arrives in warning fields on the customer, and a retry means creating a new customer with corrected data rather than editing the rejected one.\"\n  - q: \"What should a neobank log for KYC audits?\"\n    a: \"Log who was verified, at which tier, with which data and documents, what each check returned, who reviewed manual cases, and when. Keep sanctions screening results and any requests for information with their responses. US BSA rules generally require records to be kept for five years. Store decisions, not just final statuses, so an examiner can follow the path.\"\n---\n\nDesign neobank onboarding as a short funnel: consent, basic details, identity data and documents, an automated check, then a decision with limits that match the verification tier. Ask for more (source of funds, business ownership papers) only when the account needs it. BlindPay runs KYC and KYB inside its API, so the app owns the screens while BlindPay owns the checks for its payment flow.\n\nOnboarding is where most neobanks lose users and where most audits start. This guide covers the screen order, which checks run when, how to handle rejections and requests for information, and what to keep for examiners. It is part of our [guide to building a neobank](\u002Fresources\u002Fmore\u002Fhow-to-build-a-neobank).\n\nThis is educational content, not legal advice.\n\n**Key takeaways**\n\n- Ask for country first. It decides the tier, the documents, and whether review is automated.\n- Tiered limits let you approve fast on light data and ask for more only when activity grows.\n- Rejections need human-readable fixes. Requests for information should ask only for what's missing.\n- KYB is slower by design: ownership and control need a human review.\n- Log decisions and evidence, not just statuses.\n\n## What is the difference between KYC and KYB in a neobank?\n\nKYC verifies a person. KYB verifies a business and the people who own or control it.\n\nFor an individual, you collect identity data, check an ID document against a selfie, and screen the name against sanctions and PEP lists. For a business, you verify the company exists, then run KYC on its owners. Under the US [beneficial ownership rule](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.230), that means each person owning 25 percent or more of the equity, plus one individual with responsibility to control, manage, or direct the company. If you need definitions first, start with [KYC vs KYB vs KYT](\u002Fresources\u002Fmore\u002Fkyc-vs-kyb-vs-kyt) and [what KYB verifies](\u002Fresources\u002Fmore\u002Fwhat-is-kyb).\n\n## What data should each onboarding step collect?\n\nCollect in the order that gets to a decision soonest. Here is a typical individual flow, with the check each step feeds.\n\n| Step | Screen | Data | Check it feeds |\n| --- | --- | --- | --- |\n| 1 | Welcome | Terms of service, privacy notice, consent | Legal basis to process data |\n| 2 | About you | Name, email, country, date of birth | Tier selection, sanctions and PEP screening |\n| 3 | Identity details | Tax ID, phone, address | Identity match, address checks |\n| 4 | Document | ID type and country, front, back if needed | Document authenticity |\n| 5 | Selfie | Live photo | Face match against the document |\n| 6 | Review | Summary and submit | Automated decision or manual review |\n| Later | Limits | Source of funds, purpose of transactions | Enhanced review, higher limits |\n\nOn BlindPay, the [customer data requirements](\u002Fdocs\u002Flearn\u002Fcustomers) follow this split. KYC Standard asks for the core identity fields, an ID document, and a selfie. KYC Enhanced adds a source of funds document and the purpose of transactions.\n\n## How does business onboarding (KYB) work?\n\nBusiness onboarding runs company checks first, then KYC on each owner.\n\n1. Collect legal name, tax ID, formation date, country, and address.\n2. Upload the formation document and a proof of ownership document.\n3. List beneficial owners above 25 percent and a control person, each with their own KYC data.\n4. Screen the company and every owner.\n5. Route to manual review and show a waiting state.\n\nBlindPay's [KYB document list](\u002Fdocs\u002Fkb\u002Fkyb-documents) shows what reviewers expect. Plan for manual review on every business: on BlindPay, KYB Standard always goes to the compliance team for manual review.\n\n## Which checks run when?\n\nSome checks run once at signup, some on every transaction, some on a schedule.\n\n| Check | When it runs | Who usually runs it |\n| --- | --- | --- |\n| Identity verification | Signup | Verification provider |\n| Document and selfie match | Signup | Verification provider |\n| Sanctions and PEP screening | Signup, then on list updates | You and your payment provider |\n| Country risk tiering | Signup | Your rules plus provider rules |\n| Transaction screening and Travel Rule | Each payin and payout | Payment provider |\n| Rescreening | When lists change or on a schedule | You and your provider |\n| Enhanced review | Higher risk or higher limits | Compliance team |\n\nSanctions lists change often. The [OFAC sanctions list search](https:\u002F\u002Fsanctionssearch.ofac.treas.gov\u002F) is the public reference for US lists, and our guide on [how often to rescreen](\u002Fresources\u002Fmore\u002Fongoing-sanctions-screening-how-often-to-rescreen) covers ongoing screening.\n\n## How do tiered limits cut drop-off?\n\nTiers let you approve on less data and ask for more only when the customer needs it.\n\nInstead of asking every user for bank statements on day one, start with standard verification and default limits. When a user wants to send more, ask for source of funds then. The [FATF Recommendations](https:\u002F\u002Fwww.fatf-gafi.org\u002Fen\u002Fpublications\u002FFatfrecommendations\u002FFatf-recommendations.html) describe this risk-based approach to customer due diligence.\n\nBlindPay's default limits, measured on the stablecoin amount, show how this works in practice:\n\n| Limit | KYC Standard | KYB Standard | KYC Enhanced |\n| --- | --- | --- | --- |\n| Per transaction | US$10,000 | US$30,000 | US$50,000 |\n| Daily | US$50,000 | US$100,000 | US$100,000 |\n| Monthly | US$100,000 | US$250,000 | US$500,000 |\n\nWhen a customer needs more, a [limit increase request](\u002Fdocs\u002Flearn\u002Flimit-increase) goes in with a supporting document, and compliance decides. Our guide to [source of funds requests](\u002Fresources\u002Fmore\u002Fsource-of-funds-crypto-off-ramps) covers which documents work.\n\n## Worked example: where does a funnel lose users?\n\nIllustrative numbers, not data from any real app. A neobank starts 1,000 signups in a month.\n\n| Step | Users who finish | Lost at this step |\n| --- | --- | --- |\n| Basics | 900 | 100 |\n| Identity details | 780 | 120 |\n| Document and selfie | 620 | 160 |\n| Automated approval | 560 | 60 (manual review or rejection) |\n\nThe document step loses the most. Three fixes target it: use the camera with an on-screen frame, check blur and glare before upload, and let users resume on another device. If the team instead asked for a bank statement at signup, every user would hit a fourth upload. Deferring it to the limit increase moves that friction to the few who need it.\n\n## How should rejections and requests for information work?\n\nTreat them as product flows, not dead ends.\n\n- **Rejection.** Show the reason in plain words and what to do next. On BlindPay, feedback arrives in `kyc_warnings` or `fraud_warnings`, and a retry means creating a new customer with corrected data.\n- **Request for information.** Compliance pauses the review and asks for specific items. On BlindPay, a `customer.update` webhook moves the customer to `compliance_request`, you fetch the open [RFI](\u002Fdocs\u002Flearn\u002Frfi), collect only those fields in your UI, and submit them. The status returns to `verifying` while BlindPay re-reviews.\n- **Approved with an open RFI.** The customer can transact (`approved_rfi`) while the request stays open. Remind them before it becomes a block.\n\nStatuses to map to screens: `verifying`, `approved`, `rejected`, `pending_review`, `compliance_request`, and `approved_rfi`.\n\n## What should you log for audits?\n\nLog the decision path, not only the final status.\n\n- Data and documents submitted, with timestamps and the tier.\n- Each check's result: identity, document, selfie, sanctions, PEP.\n- Manual reviewer, decision, and reason.\n- Requests for information, responses, and dates.\n- Limit changes and the documents behind them.\n\nUS BSA recordkeeping rules [require five-year retention](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.430) for records kept under that chapter. Keep yours at least that long unless counsel says otherwise.\n\n## What are common onboarding mistakes?\n\n- Asking for every document up front, including ones only high-limit users need.\n- Asking for country last, after the user has already uploaded a document the tier won't accept.\n- Showing a raw error code on rejection.\n- Letting users edit identity data after approval without re-verification.\n- Running sanctions screening once and never again.\n- Logging only `approved` or `rejected` with no evidence.\n\n## How does BlindPay fit?\n\nBlindPay puts KYC and KYB inside the payments API, so a neobank builds the screens and BlindPay runs the checks for its payins, payouts, and virtual accounts.\n\n- **Consent first.** Each customer accepts BlindPay's [terms of service](\u002Fdocs\u002Flearn\u002Fterms-of-service) on a hosted page, which returns a `tos_id` you pass when creating the customer.\n- **Two KYC tiers.** KYC Standard is automated and typically completes in about 60 seconds. KYC Enhanced adds source of funds and purpose of transactions and is reviewed manually. Individuals from [high-risk countries](\u002Fdocs\u002Fkb\u002Fsupported-countries) must use Enhanced.\n- **KYB with ownership.** Owners above 25 percent are verified with their own KYC data.\n- **Statuses by webhook,** so your app can show the right screen at each step.\n- **Default limits per tier** with a documented increase path.\n\nYour own obligations still apply to anything outside BlindPay's flow, such as balances you hold in your ledger. For the licensing side, see [do you need a banking license](\u002Fresources\u002Fmore\u002Fdo-you-need-a-banking-license-for-a-neobank).\n\n## What to do next\n\nSketch your onboarding screens against the table above, then create test customers on a development instance, where KYC is auto-approved, to wire every status to a screen. The [KYC basics guide](\u002Fdocs\u002Fkb\u002Fkyc-basics) lists the photo rules to put on your document screen.\n",{"title":5,"description":750},"Neobank KYC and KYB onboarding: flow, checks, mistakes","resources\u002Fmore\u002Fneobank-kyc-kyb-onboarding-flow","em4b6KTPot_KRMSH08opAW9yR5jbnAfMIg9lzS2Vb6M",[797,801,805,809,813,817,821,825,829,833,837,841,845,849,853,857,860,864,868,872,876,880,884,887,891,895,896,900,903,907,911,915,919,923,927,931,935,939,943,947,951,955,959,963,967,971,974,978,982,986,990,994,998,1002],{"path":798,"title":799,"description":800},"\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":802,"title":803,"description":804},"\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":806,"title":807,"description":808},"\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":810,"title":811,"description":812},"\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":814,"title":815,"description":816},"\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":818,"title":819,"description":820},"\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":822,"title":823,"description":824},"\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":826,"title":827,"description":828},"\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":830,"title":831,"description":832},"\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":834,"title":835,"description":836},"\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":838,"title":839,"description":840},"\u002Fresources\u002Fmore\u002Fcross-border-stablecoin-payments-risk-register","Cross-border stablecoin payments risk register: a fill-in template with 16 risks, scores, and owners","A copyable risk register for cross-border stablecoin payouts: 16 risks across six categories, a 5x5 scoring method, controls, indicators, and owners.",{"path":842,"title":843,"description":844},"\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":846,"title":847,"description":848},"\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":850,"title":851,"description":852},"\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":854,"title":855,"description":856},"\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":719,"title":858,"description":859},"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":861,"title":862,"description":863},"\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":865,"title":866,"description":867},"\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":869,"title":870,"description":871},"\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":873,"title":874,"description":875},"\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":877,"title":878,"description":879},"\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":881,"title":882,"description":883},"\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":71,"title":885,"description":886},"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":888,"title":889,"description":890},"\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":892,"title":893,"description":894},"\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":790,"title":5,"description":750},{"path":897,"title":898,"description":899},"\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":359,"title":901,"description":902},"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":904,"title":905,"description":906},"\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":908,"title":909,"description":910},"\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":912,"title":913,"description":914},"\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":916,"title":917,"description":918},"\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":920,"title":921,"description":922},"\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":924,"title":925,"description":926},"\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":928,"title":929,"description":930},"\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":932,"title":933,"description":934},"\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":936,"title":937,"description":938},"\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":940,"title":941,"description":942},"\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":944,"title":945,"description":946},"\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":948,"title":949,"description":950},"\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":952,"title":953,"description":954},"\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":956,"title":957,"description":958},"\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":960,"title":961,"description":962},"\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":964,"title":965,"description":966},"\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":968,"title":969,"description":970},"\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":76,"title":972,"description":973},"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":975,"title":976,"description":977},"\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":979,"title":980,"description":981},"\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":983,"title":984,"description":985},"\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":987,"title":988,"description":989},"\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":991,"title":992,"description":993},"\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":995,"title":996,"description":997},"\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":999,"title":1000,"description":1001},"\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":450,"title":1003,"description":1004},"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.",1793136749181]