[{"data":1,"prerenderedAt":1048},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api":3,"resources-category-on-ramp-widget-vs-api":692},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":659,"categoryType":6,"compare":6,"contributors":6,"date":660,"description":661,"extension":662,"faq":663,"howto":6,"isBlog":682,"isChangelog":682,"meta":683,"navigation":685,"path":686,"pillar":682,"products":6,"rawbody":687,"role":6,"seo":688,"seoTitle":689,"stem":690,"thumbnail":6,"updated":660,"__hash__":691},"content\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api.md","On-ramp widget vs API: which integration fits your product?",null,{"type":8,"value":9,"toc":646},"minimark",[10,14,17,23,42,51,56,59,62,80,88,103,107,110,113,130,138,142,145,298,301,312,318,322,325,328,336,345,354,358,361,440,444,447,491,500,504,507,512,529,534,548,552,555,571,574,631,634,638],[11,12,13],"p",{},"An on-ramp widget is a hosted page the provider runs inside your app. It shows quotes, collects KYC, and owns most screens, so you launch fast with little control. An API-first on-ramp gives you endpoints and webhooks: you build the screens, own the user experience and data flow, and take on more engineering work.",[11,15,16],{},"Both convert fiat into stablecoins. The difference is who owns each step between \"user taps buy\" and \"USDC lands in a wallet.\" That split decides your launch date, your conversion rate, and what your compliance team signs.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"Widgets trade control for speed. The provider owns the screens, the copy, and usually the KYC flow.",[27,31,32],{},"APIs trade speed for control. You own the UX, the quote display, and the data, and you build more.",[27,34,35],{},"KYC is the deciding factor. If you already verify users in your onboarding, an API avoids asking twice.",[27,37,38],{},"Businesses funding by bank transfer lean API-first. Consumer card purchases lean widget.",[27,40,41],{},"Hybrids are normal: an API for the money flow plus one hosted step the provider must own.",[11,43,44,45,50],{},"New to the stack? ",[46,47,49],"a",{"href":48},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure","What is stablecoin infrastructure"," maps the layers, and this page zooms into how the on-ramp layer plugs into your product.",[52,53,55],"h2",{"id":54},"what-is-a-hosted-on-ramp-widget","What is a hosted on-ramp widget?",[11,57,58],{},"A hosted on-ramp widget is a provider-built purchase flow embedded in your product through an iframe, a redirect, or an SDK that opens a modal. Your app passes a few parameters (amount, currency, destination wallet) and the provider handles the rest.",[11,60,61],{},"Inside the widget, the provider typically:",[63,64,65,68,71,74,77],"ol",{},[27,66,67],{},"Shows a quote with the price, fees, and network.",[27,69,70],{},"Collects identity data, ID photos, and a selfie.",[27,72,73],{},"Takes payment, often by card or a local method.",[27,75,76],{},"Sends stablecoins to the wallet address you passed in.",[27,78,79],{},"Redirects the user back, sometimes with a status callback.",[11,81,82,83,87],{},"Widgets were built for consumer wallets: one person buying a small amount, often by card. ",[46,84,86],{"href":85},"\u002Fresources\u002Fmore\u002Fbusiness-vs-consumer-crypto-on-ramps","Business vs consumer on-ramps"," covers why that market looks so different from company funding flows.",[11,89,90,91,95,96,102],{},"One technical note. If the widget loads in an iframe, the provider controls which sites may frame it through the Content-Security-Policy ",[92,93,94],"code",{},"frame-ancestors"," directive (",[46,97,101],{"href":98,"rel":99},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FReference\u002FHeaders\u002FContent-Security-Policy\u002Fframe-ancestors",[100],"nofollow","MDN reference","). Expect an allowlisting step, and expect some providers to force a redirect or popup instead.",[52,104,106],{"id":105},"what-is-an-api-first-on-ramp","What is an API-first on-ramp?",[11,108,109],{},"An API-first on-ramp exposes the conversion as REST endpoints plus webhooks. Your product creates the customer, requests a quote, creates the deposit, shows the payment instructions in your own UI, and listens for status events.",[11,111,112],{},"The typical call sequence:",[63,114,115,118,121,124,127],{},[27,116,117],{},"Create a customer and submit KYC or KYB data.",[27,119,120],{},"Register the destination wallet.",[27,122,123],{},"Request a quote for amount, currency, and rail.",[27,125,126],{},"Create the payin and render the deposit instructions (bank details, a Pix code, a CLABE).",[27,128,129],{},"Receive webhooks as the deposit arrives and the stablecoins are delivered.",[11,131,132,133,137],{},"The full walkthrough, with edge cases and testing, is in ",[46,134,136],{"href":135},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api","how to integrate a crypto on-ramp API",".",[52,139,141],{"id":140},"what-changes-between-a-widget-and-an-api","What changes between a widget and an API?",[11,143,144],{},"Almost everything except the conversion itself. The table below compares the two on the decisions that matter after launch.",[146,147,148,164],"table",{},[149,150,151],"thead",{},[152,153,154,158,161],"tr",{},[155,156,157],"th",{},"Dimension",[155,159,160],{},"Hosted widget",[155,162,163],{},"API-first ramp",[165,166,167,179,190,201,210,221,232,243,254,265,276,287],"tbody",{},[152,168,169,173,176],{},[170,171,172],"td",{},"Who builds the screens",[170,174,175],{},"Provider",[170,177,178],{},"You",[152,180,181,184,187],{},[170,182,183],{},"Branding",[170,185,186],{},"Logo and colors, provider layout",[170,188,189],{},"Fully yours",[152,191,192,195,198],{},[170,193,194],{},"KYC capture",[170,196,197],{},"Provider screens, provider customer relationship",[170,199,200],{},"Your onboarding, data sent to provider",[152,202,203,206,208],{},[170,204,205],{},"KYC decision",[170,207,175],{},[170,209,175],{},[152,211,212,215,218],{},[170,213,214],{},"Quote display",[170,216,217],{},"Provider shows it; you may not see the breakdown",[170,219,220],{},"You get fees, rate, and expiry as fields",[152,222,223,226,229],{},[170,224,225],{},"Deposit instructions",[170,227,228],{},"Shown inside the widget",[170,230,231],{},"Returned as data; you render them",[152,233,234,237,240],{},[170,235,236],{},"Status updates",[170,238,239],{},"Redirect or callback, varies",[170,241,242],{},"Webhooks for each state change",[152,244,245,248,251],{},[170,246,247],{},"Reconciliation",[170,249,250],{},"Per-session data, often limited",[170,252,253],{},"IDs and references you store in your ledger",[152,255,256,259,262],{},[170,257,258],{},"Typical funding",[170,260,261],{},"Cards, mobile wallets, some local methods",[170,263,264],{},"Bank transfers: ACH, wire, Pix, SPEI",[152,266,267,270,273],{},[170,268,269],{},"Time to first launch",[170,271,272],{},"Days to a few weeks",[170,274,275],{},"Weeks",[152,277,278,281,284],{},[170,279,280],{},"Engineering after launch",[170,282,283],{},"Low",[170,285,286],{},"Ongoing: webhooks, retries, UI states",[152,288,289,292,295],{},[170,290,291],{},"Who the user sees",[170,293,294],{},"The provider's name",[170,296,297],{},"Your product",[11,299,300],{},"Two rows deserve a closer look.",[11,302,303,306,307,311],{},[20,304,305],{},"Quote display."," A widget usually shows one all-in price. An API returns the pieces: rate, fees, amount received, and how long the quote stays valid. If your treasury team needs to explain every basis point, you need those fields. ",[46,308,310],{"href":309},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","Live quotes and slippage"," explains why the expiry window matters.",[11,313,314,317],{},[20,315,316],{},"Reconciliation."," Widgets are built around a session. APIs are built around objects with IDs. If deposits need to match invoices or customer accounts, object IDs win.",[52,319,321],{"id":320},"who-owns-kyc-and-compliance-in-each-model","Who owns KYC and compliance in each model?",[11,323,324],{},"The ramp provider always makes the verification decision. The question is who collects the data and who owns the customer relationship.",[11,326,327],{},"With a widget, the provider usually collects documents in its own screens and treats the user as its own customer. That's simpler for your compliance team. It's also friction for a user who already passed your onboarding and now sees a second ID check.",[11,329,330,331,335],{},"With an API, you collect the data once and submit it. Your compliance team now has to think about data handling and about which party screens what. ",[46,332,334],{"href":333},"\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-compliance-who-owns-what","On-ramp compliance: who owns what"," breaks down that split line by line.",[11,337,338,339,344],{},"Business customers raise the bar. Under FinCEN's customer due diligence rule, covered US financial institutions identify beneficial owners of legal entity customers (",[46,340,343],{"href":341,"rel":342},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.230",[100],"31 CFR 1010.230","). Expect a business on-ramp to ask for owners and control persons, whichever integration you pick.",[11,346,347,348,353],{},"The money transmission question doesn't disappear with a widget either. FinCEN's 2019 guidance on convertible virtual currency business models (",[46,349,352],{"href":350,"rel":351},"https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-certain-business-models",[100],"FIN-2019-G001",") looks at what each party actually does with the value, not at whose screen it happens on. This article is for information only and is not legal advice.",[52,355,357],{"id":356},"which-integration-fits-which-product","Which integration fits which product?",[11,359,360],{},"Pick by funding method, by who the user is, and by whether you already run KYC. The table gives a starting point.",[146,362,363,376],{},[149,364,365],{},[152,366,367,370,373],{},[155,368,369],{},"Product",[155,371,372],{},"Better fit",[155,374,375],{},"Why",[165,377,378,389,400,410,420,430],{},[152,379,380,383,386],{},[170,381,382],{},"Consumer self-custody wallet, card buys",[170,384,385],{},"Widget",[170,387,388],{},"Card coverage and KYC in minutes, built for you",[152,390,391,394,397],{},[170,392,393],{},"Neobank or fintech with USD accounts",[170,395,396],{},"API",[170,398,399],{},"Deposit details inside your account screen, KYC reused",[152,401,402,405,407],{},[170,403,404],{},"B2B treasury or payroll funding",[170,406,396],{},[170,408,409],{},"Bank transfers, IDs for reconciliation, webhooks to ledger",[152,411,412,415,417],{},[170,413,414],{},"Marketplace collecting from buyers",[170,416,396],{},[170,418,419],{},"Deposits matched to orders and sellers",[152,421,422,425,427],{},[170,423,424],{},"Prototype or MVP to test demand",[170,426,385],{},[170,428,429],{},"Launch in days, learn before you build",[152,431,432,435,437],{},[170,433,434],{},"Regulated fintech with its own KYC program",[170,436,396],{},[170,438,439],{},"One verification, your audit trail",[52,441,443],{"id":442},"how-do-you-decide-step-by-step","How do you decide, step by step?",[11,445,446],{},"Use these steps in order. Most teams have their answer by step 4.",[63,448,449,455,461,467,473,479,485],{},[27,450,451,454],{},[20,452,453],{},"Name the funding method."," Card buys point to a widget. Bank transfers point to an API.",[27,456,457,460],{},[20,458,459],{},"Check your onboarding."," If users already pass KYC or KYB with you, an API saves them a second check.",[27,462,463,466],{},[20,464,465],{},"Decide who the user should see."," If the brand on the payment screen must be yours, you need an API.",[27,468,469,472],{},[20,470,471],{},"List what finance needs."," Fee breakdowns, quote IDs, and deposit references require API data.",[27,474,475,478],{},[20,476,477],{},"Count your engineering weeks."," If you can't staff webhooks, retries, and UI states this quarter, start with a widget.",[27,480,481,484],{},[20,482,483],{},"Ask about hosted steps."," Even API-first providers may host one step, such as terms acceptance. Know which ones.",[27,486,487,490],{},[20,488,489],{},"Plan the exit."," If you start on a widget, confirm you can move to the provider's API later without re-verifying every user.",[11,492,493,494,499],{},"Whichever you pick, document it for your bank partners. US bank regulators' 2023 interagency guidance on third-party relationships (",[46,495,498],{"href":496,"rel":497},"https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html",[100],"OCC Bulletin 2023-17",") expects banks to understand the vendors in a flow, and your ramp is one of them.",[52,501,503],{"id":502},"what-are-the-limits-of-each-approach","What are the limits of each approach?",[11,505,506],{},"Neither model is free of trade-offs, and each has cases where it is the wrong pick.",[11,508,509],{},[20,510,511],{},"Widget limitations:",[24,513,514,517,520,523,526],{},[27,515,516],{},"Your users see a different company's name at the moment they pay.",[27,518,519],{},"You often can't show the fee breakdown or control the quote expiry.",[27,521,522],{},"Iframe embedding can break on strict mobile webviews or framing rules.",[27,524,525],{},"Data access is limited to what the provider sends back.",[27,527,528],{},"Conversion depends on screens you can't A\u002FB test.",[11,530,531],{},[20,532,533],{},"API limitations:",[24,535,536,539,542,545],{},[27,537,538],{},"More engineering, before and after launch.",[27,540,541],{},"You own every UI state, including errors and holds.",[27,543,544],{},"Your compliance team owns data collection and its handling.",[27,546,547],{},"Bank-transfer funding is slower than a card buy, so it suits planned deposits more than impulse purchases.",[52,549,551],{"id":550},"how-does-blindpay-fit","How does BlindPay fit?",[11,553,554],{},"BlindPay is an API-first on-ramp for businesses. There's no consumer card widget. Your product creates customers, quotes, and payins through the API, renders the deposit instructions itself, and follows each deposit through webhooks.",[11,556,557,558,562,563,566,567,570],{},"One step is hosted on purpose: ",[46,559,561],{"href":560},"\u002Fdocs\u002Flearn\u002Fterms-of-service","terms of service acceptance",". Each customer accepts BlindPay's terms on a page at app.blindpay.com that shows your instance's logo, name, and accent color, then returns to your ",[92,564,565],{},"redirect_url"," with a ",[92,568,569],{},"tos_id"," you pass when creating the customer. Everything else stays in your UI.",[11,572,573],{},"What the API gives you:",[24,575,576,587,593,603,625],{},[27,577,578,581,582,586],{},[20,579,580],{},"KYC and KYB through the API."," You submit customer data and documents; BlindPay runs the review. ",[46,583,585],{"href":584},"\u002Fdocs\u002Fkb\u002Fkyc","KYC requirements"," lists the fields per level.",[27,588,589,592],{},[20,590,591],{},"Quotes as data."," A payin quote locks the payment method, amount, and fees for 5 minutes, so you can show exact numbers before the user commits.",[27,594,595,598,599,602],{},[20,596,597],{},"Deposit instructions as fields."," ACH and wire return bank details and a memo code, Pix returns a ",[92,600,601],{},"pix_code",", SPEI returns a CLABE. Customers with an approved virtual account get dedicated US bank details instead.",[27,604,605,608,609,612,613,616,617,620,621,624],{},[20,606,607],{},"Webhooks for every step."," ",[92,610,611],{},"payin.new",", ",[92,614,615],{},"payin.update",", and ",[92,618,619],{},"payin.complete",", plus ",[92,622,623],{},"tos.accept"," and customer updates.",[27,626,627,630],{},[20,628,629],{},"Delivery to any supported chain."," USDC or USDT to Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, or Tron, depending on token.",[11,632,633],{},"If your users never see a wallet address, the Abstracted docs flavor treats payins as plain deposits. Payouts run the other direction over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO).",[52,635,637],{"id":636},"what-to-do-next","What to do next",[11,639,640,641,645],{},"Write down your funding method and whether you already run KYC. If the answers are \"bank transfer\" and \"yes,\" start with the ",[46,642,644],{"href":643},"\u002Fdocs\u002Fquickstart-payin","payin quickstart"," on a free development instance and render your first deposit instructions today.",{"title":647,"searchDepth":648,"depth":648,"links":649},"",2,[650,651,652,653,654,655,656,657,658],{"id":54,"depth":648,"text":55},{"id":105,"depth":648,"text":106},{"id":140,"depth":648,"text":141},{"id":320,"depth":648,"text":321},{"id":356,"depth":648,"text":357},{"id":442,"depth":648,"text":443},{"id":502,"depth":648,"text":503},{"id":550,"depth":648,"text":551},{"id":636,"depth":648,"text":637},"payments","2026-09-29","Hosted on-ramp widget or API-first ramp? Compare who owns the UX, KYC, quotes, webhooks, branding, and compliance, plus a decision table and checklist.","md",[664,667,670,673,676,679],{"q":665,"a":666},"What is the difference between an on-ramp widget and an on-ramp API?","A hosted on-ramp widget is a page or iframe the provider runs inside your app: the provider shows the quote, collects KYC, and owns most of the screens. An API-first on-ramp gives you endpoints and webhooks, so your product builds every screen, sends customer data to the provider, and decides how quotes and deposit instructions look. The conversion is the same. Control and effort differ.",{"q":668,"a":669},"Is an on-ramp widget faster to launch than an API?","Usually, yes, for the first version. A widget can go live in days because the provider already built KYC capture, quote display, and payment screens. An API integration takes longer because you build those screens and handle webhooks yourself. The gap narrows if you already run KYC in your own onboarding, since the API can reuse that data instead of asking users twice.",{"q":671,"a":672},"Who does KYC in an on-ramp widget?","In most widgets, the ramp provider collects ID documents and selfies inside its own screens and keeps the customer relationship. With an API-first ramp, you usually collect the data in your onboarding and submit it to the provider, which still runs the verification and makes the decision. Either way, the ramp provider screens the person or business before any money moves.",{"q":674,"a":675},"Can I brand a hosted on-ramp widget?","Partly. Most widgets let you set a logo, colors, and sometimes default currency or network, but the layout, the copy, and the KYC steps stay the provider's. If your product needs its own flow, such as showing deposit details inside an existing account screen, an API is the only way to control every pixel and every word the user reads.",{"q":677,"a":678},"Which on-ramp integration do businesses use?","Business on-ramps tend to be API-first because companies fund with bank transfers like ACH, wire, Pix, or SPEI, need deposits matched to invoices or accounts, and want webhooks feeding a ledger. Hosted widgets are more common in consumer wallets where one person buys a small amount by card and conversion speed matters more than reconciliation.",{"q":680,"a":681},"Can you mix a widget and an API in one product?","Yes. A common pattern is an API for the money flow and one hosted step for something the provider must collect directly, such as a terms of service acceptance or a document upload. The rule is simple: the more of the flow the provider hosts, the less you control, and the more your user sees the provider's name.",false,{"author":684},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api","---\ntitle: \"On-ramp widget vs API: which integration fits your product?\"\nseoTitle: \"On-ramp widget vs API: which one to integrate\"\ndescription: \"Hosted on-ramp widget or API-first ramp? Compare who owns the UX, KYC, quotes, webhooks, branding, and compliance, plus a decision table and checklist.\"\ndate: \"2026-09-29\"\nupdated: \"2026-09-29\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the difference between an on-ramp widget and an on-ramp API?\"\n    a: \"A hosted on-ramp widget is a page or iframe the provider runs inside your app: the provider shows the quote, collects KYC, and owns most of the screens. An API-first on-ramp gives you endpoints and webhooks, so your product builds every screen, sends customer data to the provider, and decides how quotes and deposit instructions look. The conversion is the same. Control and effort differ.\"\n  - q: \"Is an on-ramp widget faster to launch than an API?\"\n    a: \"Usually, yes, for the first version. A widget can go live in days because the provider already built KYC capture, quote display, and payment screens. An API integration takes longer because you build those screens and handle webhooks yourself. The gap narrows if you already run KYC in your own onboarding, since the API can reuse that data instead of asking users twice.\"\n  - q: \"Who does KYC in an on-ramp widget?\"\n    a: \"In most widgets, the ramp provider collects ID documents and selfies inside its own screens and keeps the customer relationship. With an API-first ramp, you usually collect the data in your onboarding and submit it to the provider, which still runs the verification and makes the decision. Either way, the ramp provider screens the person or business before any money moves.\"\n  - q: \"Can I brand a hosted on-ramp widget?\"\n    a: \"Partly. Most widgets let you set a logo, colors, and sometimes default currency or network, but the layout, the copy, and the KYC steps stay the provider's. If your product needs its own flow, such as showing deposit details inside an existing account screen, an API is the only way to control every pixel and every word the user reads.\"\n  - q: \"Which on-ramp integration do businesses use?\"\n    a: \"Business on-ramps tend to be API-first because companies fund with bank transfers like ACH, wire, Pix, or SPEI, need deposits matched to invoices or accounts, and want webhooks feeding a ledger. Hosted widgets are more common in consumer wallets where one person buys a small amount by card and conversion speed matters more than reconciliation.\"\n  - q: \"Can you mix a widget and an API in one product?\"\n    a: \"Yes. A common pattern is an API for the money flow and one hosted step for something the provider must collect directly, such as a terms of service acceptance or a document upload. The rule is simple: the more of the flow the provider hosts, the less you control, and the more your user sees the provider's name.\"\n---\n\nAn on-ramp widget is a hosted page the provider runs inside your app. It shows quotes, collects KYC, and owns most screens, so you launch fast with little control. An API-first on-ramp gives you endpoints and webhooks: you build the screens, own the user experience and data flow, and take on more engineering work.\n\nBoth convert fiat into stablecoins. The difference is who owns each step between \"user taps buy\" and \"USDC lands in a wallet.\" That split decides your launch date, your conversion rate, and what your compliance team signs.\n\n**Key takeaways**\n\n- Widgets trade control for speed. The provider owns the screens, the copy, and usually the KYC flow.\n- APIs trade speed for control. You own the UX, the quote display, and the data, and you build more.\n- KYC is the deciding factor. If you already verify users in your onboarding, an API avoids asking twice.\n- Businesses funding by bank transfer lean API-first. Consumer card purchases lean widget.\n- Hybrids are normal: an API for the money flow plus one hosted step the provider must own.\n\nNew to the stack? [What is stablecoin infrastructure](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure) maps the layers, and this page zooms into how the on-ramp layer plugs into your product.\n\n## What is a hosted on-ramp widget?\n\nA hosted on-ramp widget is a provider-built purchase flow embedded in your product through an iframe, a redirect, or an SDK that opens a modal. Your app passes a few parameters (amount, currency, destination wallet) and the provider handles the rest.\n\nInside the widget, the provider typically:\n\n1. Shows a quote with the price, fees, and network.\n2. Collects identity data, ID photos, and a selfie.\n3. Takes payment, often by card or a local method.\n4. Sends stablecoins to the wallet address you passed in.\n5. Redirects the user back, sometimes with a status callback.\n\nWidgets were built for consumer wallets: one person buying a small amount, often by card. [Business vs consumer on-ramps](\u002Fresources\u002Fmore\u002Fbusiness-vs-consumer-crypto-on-ramps) covers why that market looks so different from company funding flows.\n\nOne technical note. If the widget loads in an iframe, the provider controls which sites may frame it through the Content-Security-Policy `frame-ancestors` directive ([MDN reference](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FReference\u002FHeaders\u002FContent-Security-Policy\u002Fframe-ancestors)). Expect an allowlisting step, and expect some providers to force a redirect or popup instead.\n\n## What is an API-first on-ramp?\n\nAn API-first on-ramp exposes the conversion as REST endpoints plus webhooks. Your product creates the customer, requests a quote, creates the deposit, shows the payment instructions in your own UI, and listens for status events.\n\nThe typical call sequence:\n\n1. Create a customer and submit KYC or KYB data.\n2. Register the destination wallet.\n3. Request a quote for amount, currency, and rail.\n4. Create the payin and render the deposit instructions (bank details, a Pix code, a CLABE).\n5. Receive webhooks as the deposit arrives and the stablecoins are delivered.\n\nThe full walkthrough, with edge cases and testing, is in [how to integrate a crypto on-ramp API](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api).\n\n## What changes between a widget and an API?\n\nAlmost everything except the conversion itself. The table below compares the two on the decisions that matter after launch.\n\n| Dimension | Hosted widget | API-first ramp |\n| --- | --- | --- |\n| Who builds the screens | Provider | You |\n| Branding | Logo and colors, provider layout | Fully yours |\n| KYC capture | Provider screens, provider customer relationship | Your onboarding, data sent to provider |\n| KYC decision | Provider | Provider |\n| Quote display | Provider shows it; you may not see the breakdown | You get fees, rate, and expiry as fields |\n| Deposit instructions | Shown inside the widget | Returned as data; you render them |\n| Status updates | Redirect or callback, varies | Webhooks for each state change |\n| Reconciliation | Per-session data, often limited | IDs and references you store in your ledger |\n| Typical funding | Cards, mobile wallets, some local methods | Bank transfers: ACH, wire, Pix, SPEI |\n| Time to first launch | Days to a few weeks | Weeks |\n| Engineering after launch | Low | Ongoing: webhooks, retries, UI states |\n| Who the user sees | The provider's name | Your product |\n\nTwo rows deserve a closer look.\n\n**Quote display.** A widget usually shows one all-in price. An API returns the pieces: rate, fees, amount received, and how long the quote stays valid. If your treasury team needs to explain every basis point, you need those fields. [Live quotes and slippage](\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes) explains why the expiry window matters.\n\n**Reconciliation.** Widgets are built around a session. APIs are built around objects with IDs. If deposits need to match invoices or customer accounts, object IDs win.\n\n## Who owns KYC and compliance in each model?\n\nThe ramp provider always makes the verification decision. The question is who collects the data and who owns the customer relationship.\n\nWith a widget, the provider usually collects documents in its own screens and treats the user as its own customer. That's simpler for your compliance team. It's also friction for a user who already passed your onboarding and now sees a second ID check.\n\nWith an API, you collect the data once and submit it. Your compliance team now has to think about data handling and about which party screens what. [On-ramp compliance: who owns what](\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-compliance-who-owns-what) breaks down that split line by line.\n\nBusiness customers raise the bar. Under FinCEN's customer due diligence rule, covered US financial institutions identify beneficial owners of legal entity customers ([31 CFR 1010.230](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F31\u002F1010.230)). Expect a business on-ramp to ask for owners and control persons, whichever integration you pick.\n\nThe money transmission question doesn't disappear with a widget either. FinCEN's 2019 guidance on convertible virtual currency business models ([FIN-2019-G001](https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-certain-business-models)) looks at what each party actually does with the value, not at whose screen it happens on. This article is for information only and is not legal advice.\n\n## Which integration fits which product?\n\nPick by funding method, by who the user is, and by whether you already run KYC. The table gives a starting point.\n\n| Product | Better fit | Why |\n| --- | --- | --- |\n| Consumer self-custody wallet, card buys | Widget | Card coverage and KYC in minutes, built for you |\n| Neobank or fintech with USD accounts | API | Deposit details inside your account screen, KYC reused |\n| B2B treasury or payroll funding | API | Bank transfers, IDs for reconciliation, webhooks to ledger |\n| Marketplace collecting from buyers | API | Deposits matched to orders and sellers |\n| Prototype or MVP to test demand | Widget | Launch in days, learn before you build |\n| Regulated fintech with its own KYC program | API | One verification, your audit trail |\n\n## How do you decide, step by step?\n\nUse these steps in order. Most teams have their answer by step 4.\n\n1. **Name the funding method.** Card buys point to a widget. Bank transfers point to an API.\n2. **Check your onboarding.** If users already pass KYC or KYB with you, an API saves them a second check.\n3. **Decide who the user should see.** If the brand on the payment screen must be yours, you need an API.\n4. **List what finance needs.** Fee breakdowns, quote IDs, and deposit references require API data.\n5. **Count your engineering weeks.** If you can't staff webhooks, retries, and UI states this quarter, start with a widget.\n6. **Ask about hosted steps.** Even API-first providers may host one step, such as terms acceptance. Know which ones.\n7. **Plan the exit.** If you start on a widget, confirm you can move to the provider's API later without re-verifying every user.\n\nWhichever you pick, document it for your bank partners. US bank regulators' 2023 interagency guidance on third-party relationships ([OCC Bulletin 2023-17](https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html)) expects banks to understand the vendors in a flow, and your ramp is one of them.\n\n## What are the limits of each approach?\n\nNeither model is free of trade-offs, and each has cases where it is the wrong pick.\n\n**Widget limitations:**\n\n- Your users see a different company's name at the moment they pay.\n- You often can't show the fee breakdown or control the quote expiry.\n- Iframe embedding can break on strict mobile webviews or framing rules.\n- Data access is limited to what the provider sends back.\n- Conversion depends on screens you can't A\u002FB test.\n\n**API limitations:**\n\n- More engineering, before and after launch.\n- You own every UI state, including errors and holds.\n- Your compliance team owns data collection and its handling.\n- Bank-transfer funding is slower than a card buy, so it suits planned deposits more than impulse purchases.\n\n## How does BlindPay fit?\n\nBlindPay is an API-first on-ramp for businesses. There's no consumer card widget. Your product creates customers, quotes, and payins through the API, renders the deposit instructions itself, and follows each deposit through webhooks.\n\nOne step is hosted on purpose: [terms of service acceptance](\u002Fdocs\u002Flearn\u002Fterms-of-service). Each customer accepts BlindPay's terms on a page at app.blindpay.com that shows your instance's logo, name, and accent color, then returns to your `redirect_url` with a `tos_id` you pass when creating the customer. Everything else stays in your UI.\n\nWhat the API gives you:\n\n- **KYC and KYB through the API.** You submit customer data and documents; BlindPay runs the review. [KYC requirements](\u002Fdocs\u002Fkb\u002Fkyc) lists the fields per level.\n- **Quotes as data.** A payin quote locks the payment method, amount, and fees for 5 minutes, so you can show exact numbers before the user commits.\n- **Deposit instructions as fields.** ACH and wire return bank details and a memo code, Pix returns a `pix_code`, SPEI returns a CLABE. Customers with an approved virtual account get dedicated US bank details instead.\n- **Webhooks for every step.** `payin.new`, `payin.update`, and `payin.complete`, plus `tos.accept` and customer updates.\n- **Delivery to any supported chain.** USDC or USDT to Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, or Tron, depending on token.\n\nIf your users never see a wallet address, the Abstracted docs flavor treats payins as plain deposits. Payouts run the other direction over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO).\n\n## What to do next\n\nWrite down your funding method and whether you already run KYC. If the answers are \"bank transfer\" and \"yes,\" start with the [payin quickstart](\u002Fdocs\u002Fquickstart-payin) on a free development instance and render your first deposit instructions today.\n",{"title":5,"description":661},"On-ramp widget vs API: which one to integrate","resources\u002Fmore\u002Fon-ramp-widget-vs-api","jEgaU14q57-xd4zKdPgHqAsthp5e_Q8mnxsAOmfI1CA",[693,697,701,705,709,713,717,721,725,729,733,737,741,745,749,753,757,761,765,769,773,777,781,785,789,793,797,800,804,808,812,816,820,824,828,832,836,840,844,848,852,856,860,861,865,869,873,877,881,885,889,893,897,901,905,909,913,916,920,924,928,932,936,940,944,948,952,956,960,964,968,972,976,980,984,988,992,996,1000,1004,1008,1012,1016,1020,1024,1028,1032,1036,1040,1044],{"path":694,"title":695,"description":696},"\u002Fresources\u002Fmore\u002Fblockchain-payment-use-cases","7 real-world blockchain payment use cases: payroll, remittances, B2B, and more","Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24\u002F7 treasury, bill pay, and PSP payouts.",{"path":698,"title":699,"description":700},"\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared","AP2 vs ACP vs x402: agent payment protocols compared","AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.",{"path":702,"title":703,"description":704},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026","Best stablecoin payment platforms for fintech in 2026: a US comparison","Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.",{"path":706,"title":707,"description":708},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","Best stablecoin payment providers in 2026: how to choose","How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.",{"path":710,"title":711,"description":712},"\u002Fresources\u002Fmore\u002Fwhat-are-blockchain-payments","Blockchain payments explained: how stablecoins move money without correspondent banks","Blockchain payments move a stablecoin on a public ledger instead of messages between banks. How they work, what they cost, and how they compare with SWIFT.",{"path":714,"title":715,"description":716},"\u002Fresources\u002Fmore\u002Fblockchain-payments-glossary","Blockchain payments glossary: 34 terms explained in plain English","Stablecoin, on-ramp, off-ramp, finality, gas, non-custodial, travel rule. The 34 terms of blockchain payments, each defined in one or two lines.",{"path":718,"title":719,"description":720},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","Build vs buy: should you build stablecoin payouts in-house or use an API?","Building stablecoin payouts in-house means wallets, liquidity, banking partners, licenses, and a compliance program. When building makes sense.",{"path":722,"title":723,"description":724},"\u002Fresources\u002Fmore\u002Fcan-a-virtual-account-replace-a-bank-account","Can a virtual account replace a business bank account? What each one does for cross-border companies","Usually not. A virtual account collects and settles payments; a bank account runs payroll, taxes, and credit. A job-by-job guide for cross-border teams.",{"path":726,"title":727,"description":728},"\u002Fresources\u002Fmore\u002Flatam-payout-liquidity-partner-pix-spei","Choosing a liquidity partner for LatAm payouts: Pix, SPEI, and beyond","How to choose a liquidity partner for payouts into Latin America: how Pix and SPEI work, how a stablecoin liquidity layer replaces local bank accounts, and a checklist for coverage, pricing, and compliance.",{"path":730,"title":731,"description":732},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes","Common stablecoin payout mistakes: wrong network, expired quotes, and bad bank details","The mistakes that make stablecoin payouts fail or stall: wrong network or token, expired quotes, deposits below minimums, bad bank details, and cut-offs.",{"path":734,"title":735,"description":736},"\u002Fresources\u002Fmore\u002Fcorrespondent-banking-vs-stablecoin-liquidity","Correspondent banking vs stablecoin liquidity: why pre-funding traps your capital","Correspondent banking keeps cross-border payouts liquid by parking cash in nostro accounts in every country. What that trapped capital costs a treasury team, and what stablecoin liquidity changes.",{"path":738,"title":739,"description":740},"\u002Fresources\u002Fmore\u002Fcrypto-payment-processor-for-businesses","Crypto payment processor for businesses: what to compare before you choose","Compare crypto payment processors on six criteria: settlement speed, stablecoins, compliance, dev effort, payout coverage, and pricing. Scorecard inside.",{"path":742,"title":743,"description":744},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps","Custodial vs non-custodial off-ramps: who holds the money, and what happens if the provider fails","A custodial off-ramp holds your stablecoins; a non-custodial one pulls them only at payout. What changes in insolvency, de-banking, and failed payouts.",{"path":746,"title":747,"description":748},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets","Custodial vs non-custodial vs MPC wallets: how to choose","Custodial, non-custodial, and MPC wallets differ in who holds the keys. Compare control, recovery, risk, and regulation, with product examples for each.",{"path":750,"title":751,"description":752},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-cut-off-times-weekends-holidays","Do stablecoin payouts work on weekends and holidays? Cut-offs and bank calendars by rail","The stablecoin leg runs 24\u002F7, and so do Pix, SPEI, and RTP. ACH, wire, SEPA, TED, and SWIFT wait for a business day. Cut-offs and calendars by rail.",{"path":754,"title":755,"description":756},"\u002Fresources\u002Fmore\u002Fstablecoin-cross-border-payments-savings","How businesses use stablecoins for cross-border payments (and where the savings come from)","Correspondent hops, FX markup, and pre-funding: what stablecoin settlement does to each cost of a cross-border payment, with a $50,000 example to Brazil.",{"path":758,"title":759,"description":760},"\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works","How does a stablecoin payment move? From bank deposit to local payout, step by step","A stablecoin payment moves in legs: fiat collected, stablecoin settled, fiat paid out. What happens at each step, where delays hide, what recipients see.",{"path":762,"title":763,"description":764},"\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding","How global merchants get paid across borders with stablecoins, no pre-funding required","Pre-funding means parking local currency in every market before money moves. Stablecoin virtual accounts remove it. A worked example across 4 countries.",{"path":766,"title":767,"description":768},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times","How long does a stablecoin payout take? Settlement times by country and rail","Stablecoin payouts settle in minutes on Pix, SPEI, RTP, and Transfers 3.0, and in 1 to 5 business days on ACH, SEPA, and SWIFT. Full table by rail.",{"path":770,"title":771,"description":772},"\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-fees-explained","How much does a crypto on-ramp cost? Fees, spreads, and how to read a quote","A crypto on-ramp charges through the rate spread, a service fee, the payment rail, and sometimes the network. How each works, and how to read the quote.",{"path":774,"title":775,"description":776},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-fees-explained","How much does a stablecoin off-ramp cost? Fees per transaction vs a bank wire","What a stablecoin off-ramp costs per transaction: network fee, FX spread, percentage and flat fees, worked at $200, $2,000, and $20,000 vs a bank wire.",{"path":778,"title":779,"description":780},"\u002Fresources\u002Fmore\u002Fhow-to-add-stablecoin-payments-to-your-wallet-integration","How to add stablecoin payments to your wallet integration","Connect the wallets you already run to bank deposits and local payouts: register addresses, open virtual accounts, quote, authorize, and track webhooks.",{"path":782,"title":783,"description":784},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-virtual-account-provider","How to choose a virtual account provider: a 12-point checklist for developers and finance teams","Twelve criteria for evaluating a virtual account API, from rails and naming to custody, webhooks, and pricing, plus red flags and a scorecard to copy.",{"path":786,"title":787,"description":788},"\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","How to choose the best on\u002Foff ramp provider for your fintech app","Six criteria for evaluating a crypto on\u002Foff ramp provider: corridor coverage, live quotes, fiat settlement speed, licensing, API quality, and liquidity depth. Each with concrete tests to run, a comparison table, and a scoring framework.",{"path":790,"title":791,"description":792},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","How to evaluate a payment orchestration platform for cross-border payments","Six criteria that decide whether an orchestration platform works for cross-border money: rail coverage, compliance per corridor, developer experience, settlement speed, FX transparency, and pricing.",{"path":794,"title":795,"description":796},"\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan","How to evaluate a stablecoin API in 30 days: a week-by-week plan","A 30-day plan to evaluate a stablecoin API: shortlist, sandbox tests, compliance review, and a live pilot, plus where costs hide and a worked cost model.",{"path":135,"title":798,"description":799},"How to integrate a crypto on-ramp API: payin quotes, deposit instructions, and webhooks","The on-ramp API flow step by step: verify the customer, pick the wallet, quote, create the payin, show deposit instructions, and handle webhooks.",{"path":801,"title":802,"description":803},"\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","How to issue stablecoin-funded cards through an API: a developer's guide","Build vs. buy for stablecoin card issuing, the objects a card issuing API must expose, a step-by-step integration flow, and where KYC and KYB sit in it.",{"path":805,"title":806,"description":807},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-us-bank-account","How to off-ramp USDC to a US bank account: ACH, RTP, or wire","Cashing out USDC or USDT to a US bank account: when ACH, Same Day ACH, RTP, and wire pay out, the cut-offs in ET, the fields you need, and what delays it.",{"path":809,"title":810,"description":811},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-euros-sepa","How to off-ramp USDC to euros over SEPA: networks, IBAN details, and timing","Converting USDC to EUR in a SEPA bank account: which networks work, the IBAN details you need, SEPA vs SEPA Instant timing, limits, and what MiCA changes.",{"path":813,"title":814,"description":815},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdt-latin-america","How to off-ramp USDT to local currency in Latin America","Converting USDT to BRL, MXN, ARS, or COP: which networks work, the payout rail in each country, weekend timing, fees, and the documents a business needs.",{"path":817,"title":818,"description":819},"\u002Fresources\u002Fmore\u002Fhow-to-on-ramp-local-currency-latin-america","How to on-ramp BRL, MXN, ARS, and COP into stablecoins: Pix, SPEI, Transfers 3.0, and PSE","How Latin American bank payments become USDC or USDT: what each rail shows the payer, the payer data it needs, how fast it lands, and the traps by country.",{"path":821,"title":822,"description":823},"\u002Fresources\u002Fmore\u002Fhow-to-pay-invoices-with-stablecoins-api","How to pay invoices, boletos, and Pix codes with stablecoins through an API","Register the bill, quote it, pay it from USDC or USDT, and track two webhook streams. A developer guide to stablecoin bill pay, boleto gotchas included.",{"path":825,"title":826,"description":827},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","How to send USDC to a bank account in Brazil","Step-by-step: convert USDC to Brazilian reais and deliver them to a bank account over Pix using a stablecoin payout API. Quote, verify, send, settle in minutes.",{"path":829,"title":830,"description":831},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI","Send USDC to a Mexican bank account: verify the recipient, quote in pesos, fund from a wallet, and confirm on SPEI. Recipient data, statuses, and failures.",{"path":833,"title":834,"description":835},"\u002Fresources\u002Fmore\u002Fhow-to-test-virtual-accounts-sandbox","How to test a virtual accounts API integration before going live","The integration sequence for a virtual accounts API, what a sandbox simulates and what it can't, and a test plan with the statuses and webhooks to expect.",{"path":837,"title":838,"description":839},"\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation","How virtual accounts automate payment reconciliation (with a worked example)","Virtual accounts match each deposit to a customer by account number, not a free-text reference. A worked example with partial payments and micro-deposits.",{"path":841,"title":842,"description":843},"\u002Fresources\u002Fmore\u002Fstablecoin-api-idempotency-keys","Idempotency keys in a stablecoin API: how to never send the same payout twice","A timeout on a payout call is the most common way to pay someone twice. How idempotency keys prevent it, what replays, what conflicts, and how to retry.",{"path":845,"title":846,"description":847},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api","Integrating a stablecoin API: a developer's guide to cross-border payments with BlindPay","Step-by-step integration of a stablecoin API: authenticate, onboard a customer, create a virtual USD account, quote and send a cross-border payout, and handle signed webhooks. Endpoints, statuses, and SDKs for BlindPay.",{"path":849,"title":850,"description":851},"\u002Fresources\u002Fmore\u002Fliquidity-risk-global-payouts","Managing liquidity risk in global payouts: a practical guide for fintechs and PSPs","Liquidity risk in payouts is the chance funds aren't available at the right rate, in the right currency, when a payout settles. Its four sources and a six-step framework to manage them.",{"path":853,"title":854,"description":855},"\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","Marketplace payouts in Latin America: stablecoin rails for sellers in Brazil, Mexico, Colombia, and Argentina","How marketplaces pay sellers, creators, and vendors across Latin America with stablecoin settlement: supported rails (Pix, SPEI, PSE, Argentine transfers), the end-to-end payout workflow, API integration, and what changes for speed, minimums, and FX cost.",{"path":857,"title":858,"description":859},"\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained","Non-custodial payments: what they are and why they reduce risk for businesses","A non-custodial payment provider moves your money without holding it between payments. Who controls the funds, who carries the risk, and what to ask.",{"path":686,"title":5,"description":661},{"path":862,"title":863,"description":864},"\u002Fresources\u002Fmore\u002Fon-ramp-or-off-ramp-which-does-your-product-need","On-ramp, off-ramp, or both? How to tell which stablecoin API your product needs","Match your use case to the direction money moves: on-ramp, off-ramp, or both. Covers payroll, remittance, marketplaces, treasury, and 10 questions to ask.",{"path":866,"title":867,"description":868},"\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","On\u002Foff ramp liquidity with live quotes: how it works and why it matters","What on\u002Foff ramp liquidity with live quotes means for developers: live quote vs batch rate, the quote ID flow in an API, what happens on expiry, how liquidity depth changes spread by transaction size, rate windows and UX, and a checklist for evaluating a live quote API.",{"path":870,"title":871,"description":872},"\u002Fresources\u002Fmore\u002Fonchain-settlement-vs-bank-settlement","Onchain settlement vs bank settlement: RTGS, ACH, cards, and blockchain finality compared","How onchain settlement compares with Fedwire, Pix, ACH, and card settlement: settlement asset, hours, finality, reversibility, and where payout risk sits.",{"path":874,"title":875,"description":876},"\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained","POBO vs COBO: SWIFT payments and collections on behalf of, explained","POBO sends a SWIFT payment for a customer, COBO collects one for them. Whose name shows, how UETR tracking works, and where stablecoin settlement fits.",{"path":878,"title":879,"description":880},"\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","Payment orchestration vs payment gateway: what's the difference?","A gateway connects you to one processor. An orchestration platform connects to many rails and picks the best path per transaction. The table, the triggers, and a worked USD to BRL example.",{"path":882,"title":883,"description":884},"\u002Fresources\u002Fmore\u002Fpix-vs-spei","Pix vs SPEI: how Brazil's and Mexico's instant payment rails compare","Pix vs SPEI side by side: who runs each rail, how recipients are identified, hours, settlement, returns, and proof of payment for stablecoin payouts.",{"path":886,"title":887,"description":888},"\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template","Stablecoin API RFP template: sections, scoring, and a vendor scorecard","How to write an RFP for a stablecoin API: the eight sections to include, pass or fail gates, 1 to 3 weighted scoring, a copyable scorecard, and a timeline.",{"path":890,"title":891,"description":892},"\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks","Stablecoin API SDKs: how one OpenAPI spec keeps five languages in sync","BlindPay's stablecoin API is described by one OpenAPI 3.1 spec that drives validation, docs, SDKs for Node, Python, Go, PHP, and Swift, and the MCP server.",{"path":894,"title":895,"description":896},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","Stablecoin API SLAs and settlement finality explained","Stablecoin API uptime numbers cluster near 99.9% for a reason: most providers measure API acceptance instead of the point where money becomes final and spendable.",{"path":898,"title":899,"description":900},"\u002Fresources\u002Fmore\u002Fstablecoin-api-objects-explained","Stablecoin API objects explained: customers, bank accounts, wallets, quotes, payouts, and webhooks","The core objects behind a stablecoin API, how they relate, which IDs to store in your ledger, and 8 data-model mistakes that break payout integrations.",{"path":902,"title":903,"description":904},"\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained","Stablecoin API quotes explained: expiry, fee direction, and minor units","A stablecoin API quote locks the rate, fees, and amounts for a few minutes. How expiry works, which side pays the fee, and the field that flips meaning.",{"path":906,"title":907,"description":908},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Stablecoin API sandbox vs production: what testing misses","Most stablecoin API sandboxes pass every integration test and still leave a team unprepared for production, because webhook delivery and idempotent retries are exactly what sandboxes fake or skip.",{"path":910,"title":911,"description":912},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","Stablecoin API webhooks: signature checks, duplicate events, and reconciliation","How to handle stablecoin API webhooks in production: verify signatures on raw bytes, dedupe retries, never regress a final status, reconcile daily.",{"path":309,"title":914,"description":915},"Stablecoin FX slippage: how live quotes turn the quoted rate into the rate you get","FX slippage is the gap between the rate a stablecoin on-ramp or off-ramp shows and the rate that settles. Why quote freshness is a liquidity signal, and how to check a quote-then-execute flow.",{"path":917,"title":918,"description":919},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america","Stablecoin cards in Latin America: how they work in Brazil, Mexico, Argentina, and Colombia","How USD stablecoin cards work in Brazil, Mexico, Argentina, and Colombia: local card and crypto rules, costs at the point of sale, and when a Pix or SPEI payout fits better.",{"path":921,"title":922,"description":923},"\u002Fresources\u002Fmore\u002Fstablecoin-liquidity-provider-vs-fx-desk","Stablecoin liquidity providers vs traditional FX desks: what finance teams should know","A bank FX desk prices cross-border payouts by relationship. A stablecoin liquidity provider prices them by API. How the two compare on cost, speed, minimums, coverage, and compliance.",{"path":925,"title":926,"description":927},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees","Stablecoin payment fees vs credit card processing fees: what merchants actually pay","Cards cost merchants 1.5% to 3.5% plus cross-border, FX, and chargeback fees. Stablecoin payments cost cents on-chain plus a sub-percent conversion spread.",{"path":929,"title":930,"description":931},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide","Stablecoin payments explained: a guide for businesses","Stablecoin payments move dollar-pegged tokens between parties and settle in minutes, 24\u002F7. How they work, what they cost, and how businesses accept and send them.",{"path":933,"title":934,"description":935},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained","Stablecoin payout statuses explained: processing, on hold, completed, failed, and refunded","What each stablecoin payout status means, which are final, why an on-chain confirmation isn't a completed payout, and how to test every failure.",{"path":937,"title":938,"description":939},"\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","Stablecoin payroll for LATAM contractors: how it actually works in 2026","How US companies pay contractors in Argentina, Brazil, Mexico, and Colombia with stablecoins in 2026: USDC vs USDT, the step-by-step payout flow, US tax reporting, a platform comparison, and how to start.",{"path":941,"title":942,"description":943},"\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants","Stablecoin settlement explained: how merchants get paid faster than card networks","Stablecoin payments settle in seconds to minutes, final and 24\u002F7. Cards take 1 to 3 business days and wires up to 5. How it works and how to cash out.",{"path":945,"title":946,"description":947},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","Stablecoin virtual accounts explained: from bank transfer to wallet balance","A stablecoin virtual account is a bank account in your customer's name whose deposits convert to USDC or USDT. How approval, deposits, and fees work.",{"path":949,"title":950,"description":951},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","Stablecoin-funded virtual cards vs. traditional virtual cards for cross-border payouts","Stablecoin-funded vs. bank-funded virtual cards for paying contractors and vendors abroad: funding speed, pre-funding, FX cost, settlement finality, and a Brazil walkthrough.",{"path":953,"title":954,"description":955},"\u002Fresources\u002Fmore\u002Fstablecoins-local-rails-latin-america","Stablecoins plus local rails: how cross-border payments actually land in Latin America","A stablecoin crosses the border in seconds, but the payment lands over Pix, SPEI, or another local rail. How that last mile works in Brazil and Mexico.",{"path":957,"title":958,"description":959},"\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","Stablecoins vs SWIFT for B2B cross-border payments: a real comparison","Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes for business payments in 2026.",{"path":961,"title":962,"description":963},"\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026","USDC to ARS in 2026: routes, fees, and rules compared","Four ways to convert USDC to Argentine pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Transfers 3.0. Fees, speed, KYC, and Argentina's PSAV rules compared.",{"path":965,"title":966,"description":967},"\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026","USDC to BRL in 2026: routes, fees, and rules compared","Four ways to convert USDC to Brazilian reais in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Pix. Fees, speed, KYC, and Brazil's VASP rules compared.",{"path":969,"title":970,"description":971},"\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026","USDC to COP in 2026: routes, fees, and rules compared","Four ways to convert USDC to Colombian pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with PSE. Fees, speed, KYC, and Colombia's VASP rules compared.",{"path":973,"title":974,"description":975},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN in 2026: routes, fees, and rules compared","Four ways to convert USDC to Mexican pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with SPEI. Fees, speed, KYC, and Mexico's rules compared.",{"path":977,"title":978,"description":979},"\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received","Virtual account deposit not received? Why deposits get delayed, held, or returned","Why a virtual account deposit is late, on hold, or returned: arrival windows, payin statuses, RFIs, wrong rails, and how to trace a wire or SWIFT payment.",{"path":981,"title":982,"description":983},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-virtual-iban","Virtual account vs virtual IBAN vs real bank account: what's the difference?","A real account holds funds for one holder. A virtual account routes deposits into a master account. A virtual IBAN is the IBAN version. When to use each.",{"path":985,"title":986,"description":987},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link","Virtual account vs wallet address vs payment link: how to collect in stablecoins","Three ways to collect money that ends in stablecoins: a virtual account, a deposit wallet address, or a payment link. Compare rails, refunds, KYC, and fit.",{"path":989,"title":990,"description":991},"\u002Fresources\u002Fmore\u002Fvirtual-accounts-cross-border-payments","Virtual accounts for cross-border payments: use cases, payment rails, and costs","How virtual accounts let payers abroad pay a local-style account, which rails collect and pay out, what drives the cost, and five questions to ask.",{"path":993,"title":994,"description":995},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","Virtual accounts vs one-time deposit instructions: how to collect bank transfers as stablecoins","One-time deposit instructions suit occasional payers and local rails. Virtual accounts suit repeat US payers. How each matches deposits and when to switch.",{"path":997,"title":998,"description":999},"\u002Fresources\u002Fmore\u002Fpix-key-cpf-clabe-payout-details","What details do you need to pay someone in Brazil or Mexico? Pix keys, CPF, and CLABE","What a payout to Brazil or Mexico needs from the recipient: Pix key types, CPF and CNPJ formats, the 18-digit CLABE, and the checks that stop a bad payout.",{"path":1001,"title":1002,"description":1003},"\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","What does \"no pre-funding\" mean in a stablecoin API?","No pre-funding means each payout is funded when you send it, not from a balance parked in advance. The three funding models, the math, and what to ask.",{"path":1005,"title":1006,"description":1007},"\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","What is a crypto on-ramp and off-ramp? A guide for fintech builders","A crypto on-ramp converts fiat into stablecoins or crypto; an off-ramp converts them back into fiat in a bank account. How each works step by step, how they differ, which payment methods on-ramps support, and who they are built for.",{"path":1009,"title":1010,"description":1011},"\u002Fresources\u002Fmore\u002Fwhat-is-a-liquidity-market-cross-border-payments","What is a liquidity market in cross-border payments? And why stablecoin liquidity is changing it","A liquidity market in cross-border payments is where the currency to settle a transfer gets sourced. How correspondent banks pre-fund it, and how stablecoin liquidity changes the model.",{"path":1013,"title":1014,"description":1015},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","What is a stablecoin off-ramp? How crypto becomes cash","A stablecoin off-ramp converts stablecoins like USDC or USDT back into fiat currency in a bank account. How the conversion works and who regulates it.",{"path":1017,"title":1018,"description":1019},"\u002Fresources\u002Fmore\u002Fwhat-is-a-virtual-account","What is a virtual account? A plain-English guide for fintech teams","A virtual account is a unique set of bank details that routes incoming payments to one customer or purpose. How it works, who uses it, and where it fits.",{"path":1021,"title":1022,"description":1023},"\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration","What is payment orchestration? The routing layer, explained","Payment orchestration is the routing layer between your app and every processor, bank, and rail you use. The five layers, how stablecoin settlement fits, and how it differs from a gateway.",{"path":1025,"title":1026,"description":1027},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","What to ask a stablecoin payments provider: 30 due diligence questions","The questions to ask a stablecoin payments vendor before you sign: licensing, custody, pricing, rails, compliance, failure handling, security, and exit.",{"path":1029,"title":1030,"description":1031},"\u002Fresources\u002Fmore\u002Fwhen-not-to-use-blockchain-payments","When not to use blockchain payments: 7 cases where a bank rail wins","Blockchain payments beat wires on many corridors, not all of them. Seven cases where a domestic rail, a card, or a plain wire is still the better choice.",{"path":1033,"title":1034,"description":1035},"\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout","Where is my off-ramp payout? How to track it rail by rail, and what to tell the recipient","Track an off-ramp payout from transaction hash to bank: the reference each rail gives you (Pix E2E ID, SPEI key, ACH trace, UETR) and status copy.",{"path":1037,"title":1038,"description":1039},"\u002Fresources\u002Fmore\u002Fwho-pays-gas-fees-stablecoin-payments","Who pays gas fees in stablecoin payments?","Who pays network fees in each stablecoin payment flow, how gas works on Ethereum, Solana, Tron, Stellar, and Arc, and how to compare it across providers.",{"path":1041,"title":1042,"description":1043},"\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow","Why are cross-border payments slow? Where the days go in an international wire","Most SWIFT payments reach the destination bank within an hour. The days go to cut-offs, correspondent hops, compliance checks, and local crediting.",{"path":1045,"title":1046,"description":1047},"\u002Fresources\u002Fmore\u002Fwhy-crypto-on-ramp-deposits-fail","Why crypto on-ramp deposits fail: missing references, late transfers, holds, and refunds","Most failed on-ramps fail on the fiat side: a missing reference, the wrong payer, a late transfer, a hold. What happens to the money in each case.",1791469669362]