[{"data":1,"prerenderedAt":1220},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template":3,"resources-category-stablecoin-api-rfp-template":866},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":815,"categoryType":6,"compare":6,"contributors":6,"date":816,"description":817,"extension":818,"faq":819,"howto":838,"isBlog":856,"isChangelog":856,"meta":857,"navigation":859,"path":860,"pillar":856,"products":6,"rawbody":861,"role":6,"seo":862,"seoTitle":863,"stem":864,"thumbnail":6,"updated":816,"__hash__":865},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template.md","Stablecoin API RFP template: sections, scoring, and a vendor scorecard",null,{"type":8,"value":9,"toc":801},"minimark",[10,14,17,23,42,56,61,64,67,71,74,212,220,224,227,271,274,278,281,331,334,337,351,355,358,364,565,568,576,580,583,586,628,632,635,643,658,662,665,725,728,732,735,761,765,772,794],[11,12,13],"p",{},"A stablecoin API RFP (request for proposal) is a written document that asks every vendor the same numbered questions about corridors, compliance, custody, integration, reliability, pricing, and contract terms. Score the replies in two passes: pass or fail gates first, then a weighted 1 to 3 score on every criterion, using weights you set before anyone replies.",[11,15,16],{},"Most fintechs skip the RFP and go straight to demos. That works until three vendors describe \"global coverage\" in three different ways and nobody can say which is better. A short, structured RFP fixes that.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"An RFP is useful because it fixes the questions and the answer format. Comparability is the whole point.",[27,31,32],{},"Set the pass or fail gates and the weights before sending. Changing them after replies arrive invites bias.",[27,34,35],{},"Gates come first: licensing, Travel Rule and sanctions controls, custody model, and live launch corridors.",[27,37,38],{},"Score 1 to 3. A 3 needs proof, such as a document, a public docs link, or a sandbox test.",[27,40,41],{},"Verify the top two vendors in a sandbox before signing. Written answers are claims until tested.",[11,43,44,45,50,51,55],{},"If you are still working out which part of the stack you are buying, read ",[46,47,49],"a",{"href":48},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure","what stablecoin infrastructure is"," first, then ",[46,52,54],{"href":53},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","the types of stablecoin APIs",". An RFP only works when every vendor on the list is solving the same problem.",[57,58,60],"h2",{"id":59},"what-is-a-stablecoin-api-rfp","What is a stablecoin API RFP?",[11,62,63],{},"A stablecoin API RFP is a document a buyer sends to several providers asking for written, structured answers about how the provider would handle the buyer's payment flow. It replaces open-ended sales calls with numbered questions, a response template, a deadline, and a list of required documents.",[11,65,66],{},"An RFP is different from a questionnaire. A questionnaire asks a vendor about itself. An RFP starts with your flow (corridors, volumes, users, custody needs) and asks how the vendor would serve it. That framing matters, because a stablecoin API that is strong for card issuing can be weak for local payouts, and only your flow tells you which one you need.",[57,68,70],{"id":69},"what-sections-should-a-stablecoin-api-rfp-include","What sections should a stablecoin API RFP include?",[11,72,73],{},"A stablecoin API RFP should include eight sections, each with numbered questions and a list of documents to attach. Put your own requirements first, so every answer that follows is about your flow.",[75,76,77,96],"table",{},[78,79,80],"thead",{},[81,82,83,87,90,93],"tr",{},[84,85,86],"th",{},"Section",[84,88,89],{},"What you write",[84,91,92],{},"What you ask the vendor",[84,94,95],{},"Documents to request",[97,98,99,114,128,142,156,170,184,198],"tbody",{},[81,100,101,105,108,111],{},[102,103,104],"td",{},"1. Requirements and flow",[102,106,107],{},"Corridors, direction, monthly volume range, payment size, tokens and networks, end-user types",[102,109,110],{},"Confirm which parts of the flow you would handle, and which you would not",[102,112,113],{},"None",[81,115,116,119,122,125],{},[102,117,118],{},"2. Corridors and rails",[102,120,121],{},"Countries, currencies, and rails you need at launch and in 12 months",[102,123,124],{},"Which rail and country pairs are live in production, in which direction, with what settlement window",[102,126,127],{},"Rails list from public docs",[81,129,130,133,136,139],{},[102,131,132],{},"3. Compliance and licensing",[102,134,135],{},"Your own licenses, if any, and who your end users are",[102,137,138],{},"Which licenses or registrations cover your flow; who runs KYC, KYB, sanctions screening, Travel Rule, and monitoring",[102,140,141],{},"License list, AML and sanctions policy statement",[81,143,144,147,150,153],{},[102,145,146],{},"4. Custody and flow of funds",[102,148,149],{},"Who must hold funds at each step",[102,151,152],{},"Who holds stablecoins, fiat, and keys at each step; what happens to funds in a payment that cannot complete",[102,154,155],{},"Flow-of-funds diagram",[81,157,158,161,164,167],{},[102,159,160],{},"5. Technical integration",[102,162,163],{},"Your stack, languages, and ledger model",[102,165,166],{},"API style, OpenAPI spec, SDKs, sandbox access, webhooks, idempotency, error model",[102,168,169],{},"Docs links, sandbox credentials",[81,171,172,175,178,181],{},[102,173,174],{},"6. Reliability and support",[102,176,177],{},"Your uptime and support needs",[102,179,180],{},"SLAs, status page, incident history, support hours and channels, escalation path",[102,182,183],{},"SLA document, incident summary",[81,185,186,189,192,195],{},[102,187,188],{},"7. Pricing",[102,190,191],{},"Volume range and payment size per corridor",[102,193,194],{},"Itemized sample quotes for your top corridors, monthly fees, minimums, pre-funding needs",[102,196,197],{},"Sample quotes, order form",[81,199,200,203,206,209],{},[102,201,202],{},"8. Contract",[102,204,205],{},"Your legal requirements",[102,207,208],{},"Term, termination, notice, data export on exit, liability, change-of-terms process",[102,210,211],{},"Standard contract",[11,213,214,215,219],{},"Keep the vendor questions to 40 or fewer across all eight sections. Long RFPs get long, vague answers. If you need a deeper question bank for a specific section, the ",[46,216,218],{"href":217},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","30 due diligence questions"," are organized by category and drop into sections 3, 4, 6, and 8.",[57,221,223],{"id":222},"which-requirements-should-be-pass-or-fail-gates","Which requirements should be pass or fail gates?",[11,225,226],{},"Gates are the requirements where a weak answer cannot be offset by a strong score somewhere else. Procurement frameworks for stablecoin payments usually treat licensing, Travel Rule compliance, and the custody model as hard minimums, and most buyers add live corridors.",[228,229,230,248,254,265],"ol",{},[27,231,232,235,236,242,243,247],{},[20,233,234],{},"Licensing for your flow."," The vendor holds the licenses or registrations needed for the role it plays in your flow, in the markets you pay into. In the US you can check federal money services business registration yourself in FinCEN's ",[46,237,241],{"href":238,"rel":239},"https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fmsb-state-selector",[240],"nofollow","MSB registrant search",". ",[46,244,246],{"href":245},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi","Which license a stablecoin payment flow needs"," explains the categories.",[27,249,250,253],{},[20,251,252],{},"Travel Rule and sanctions controls."," The vendor screens every counterparty and transaction it touches and exchanges originator and beneficiary data where the Travel Rule applies.",[27,255,256,259,260,264],{},[20,257,258],{},"A written custody model."," The vendor states in writing who holds stablecoins, fiat, and keys at every step, and what happens to funds in a payment that fails. ",[46,261,263],{"href":262},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps","Custodial vs non-custodial off-ramps"," covers why this matters in an insolvency.",[27,266,267,270],{},[20,268,269],{},"Launch corridors live in production."," Every corridor you need on day one is live today, in the direction you need. Roadmap items do not pass.",[11,272,273],{},"A vendor that fails one gate is out. Do not calculate its score. This keeps a cheap or well-documented vendor from winning on points while failing on the one thing that would stop your launch.",[57,275,277],{"id":276},"how-do-you-score-answers-on-a-1-to-3-scale","How do you score answers on a 1 to 3 scale?",[11,279,280],{},"Score each criterion 1, 2, or 3, multiply by its weight, and add up. The short scale forces a decision and makes evidence the difference between a 2 and a 3.",[75,282,283,296],{},[78,284,285],{},[81,286,287,290,293],{},[84,288,289],{},"Score",[84,291,292],{},"Meaning",[84,294,295],{},"Evidence needed",[97,297,298,309,320],{},[81,299,300,303,306],{},[102,301,302],{},"1",[102,304,305],{},"Weak, vague, or missing",[102,307,308],{},"None, or a sales claim only",[81,310,311,314,317],{},[102,312,313],{},"2",[102,315,316],{},"Meets the requirement",[102,318,319],{},"A clear written answer",[81,321,322,325,328],{},[102,323,324],{},"3",[102,326,327],{},"Strong and proven",[102,329,330],{},"A document, a public docs link, or a sandbox result that confirms the answer",[11,332,333],{},"Weights depend on your business. A payroll platform paying contractors in Latin America will weight corridors and settlement heavily. A regulated bank will weight licensing, security, and contract terms. Decide the weights before sending the RFP and write them into the scoring sheet, so nobody adjusts them after a favorite vendor replies.",[11,335,336],{},"Two rules keep scoring honest:",[24,338,339,345],{},[27,340,341,344],{},[20,342,343],{},"Score per criterion, not per vendor."," Score all vendors on criterion 1, then all on criterion 2. Reading one vendor end to end inflates its scores.",[27,346,347,350],{},[20,348,349],{},"Two scorers per section."," Engineering scores technical sections, compliance scores sections 3 and 4, finance scores pricing. Average the two, and discuss any gap of 2 points.",[57,352,354],{"id":353},"what-does-a-stablecoin-api-scorecard-look-like","What does a stablecoin API scorecard look like?",[11,356,357],{},"A scorecard lists every weighted criterion with blank score columns for each vendor, plus the gates above it. Copy the table below into a spreadsheet and adjust the weights to your flow. The weights shown are an example, not an industry standard.",[11,359,360,363],{},[20,361,362],{},"Gates (pass or fail for each vendor):"," licensing for your flow, Travel Rule and sanctions controls, written custody model, launch corridors live.",[75,365,366,385],{},[78,367,368],{},[81,369,370,373,376,379,382],{},[84,371,372],{},"Criterion",[84,374,375],{},"Example weight",[84,377,378],{},"Vendor A (1 to 3)",[84,380,381],{},"Vendor B (1 to 3)",[84,383,384],{},"Vendor C (1 to 3)",[97,386,387,401,415,428,442,455,469,482,495,508,521,534,547],{},[81,388,389,392,395,397,399],{},[102,390,391],{},"Corridors and rails beyond launch needs",[102,393,394],{},"12%",[102,396],{},[102,398],{},[102,400],{},[81,402,403,406,409,411,413],{},[102,404,405],{},"Settlement windows per rail, in writing",[102,407,408],{},"10%",[102,410],{},[102,412],{},[102,414],{},[81,416,417,420,422,424,426],{},[102,418,419],{},"Compliance split (KYC, KYB, screening, monitoring)",[102,421,408],{},[102,423],{},[102,425],{},[102,427],{},[81,429,430,433,436,438,440],{},[102,431,432],{},"Supported stablecoins and networks",[102,434,435],{},"6%",[102,437],{},[102,439],{},[102,441],{},[81,443,444,447,449,451,453],{},[102,445,446],{},"Quote and fee transparency",[102,448,394],{},[102,450],{},[102,452],{},[102,454],{},[81,456,457,460,463,465,467],{},[102,458,459],{},"Pre-funding requirement",[102,461,462],{},"8%",[102,464],{},[102,466],{},[102,468],{},[81,470,471,474,476,478,480],{},[102,472,473],{},"API design and OpenAPI spec",[102,475,462],{},[102,477],{},[102,479],{},[102,481],{},[81,483,484,487,489,491,493],{},[102,485,486],{},"SDKs and sandbox access",[102,488,435],{},[102,490],{},[102,492],{},[102,494],{},[81,496,497,500,502,504,506],{},[102,498,499],{},"Webhooks and event reliability",[102,501,462],{},[102,503],{},[102,505],{},[102,507],{},[81,509,510,513,515,517,519],{},[102,511,512],{},"Reconciliation and reporting",[102,514,435],{},[102,516],{},[102,518],{},[102,520],{},[81,522,523,526,528,530,532],{},[102,524,525],{},"SLAs, support, and refund handling",[102,527,462],{},[102,529],{},[102,531],{},[102,533],{},[81,535,536,539,541,543,545],{},[102,537,538],{},"Contract terms and exit",[102,540,435],{},[102,542],{},[102,544],{},[102,546],{},[81,548,549,554,559,561,563],{},[102,550,551],{},[20,552,553],{},"Weighted total (max 3.00)",[102,555,556],{},[20,557,558],{},"100%",[102,560],{},[102,562],{},[102,564],{},[11,566,567],{},"To get the weighted total, multiply each score by its weight and add the results. A vendor scoring 2 on everything totals 2.00. Anything above 2.50 means most answers came with proof.",[11,569,570,571,575],{},"For what a good and a bad answer look like on the six criteria that eliminate vendors fastest, see ",[46,572,574],{"href":573},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","how to choose a stablecoin API",".",[57,577,579],{"id":578},"what-questions-belong-in-the-technical-section","What questions belong in the technical section?",[11,581,582],{},"The technical section should ask how the API behaves when things go wrong, not only how a successful payment works. Every vendor can show a happy path in a demo.",[11,584,585],{},"Ask for:",[24,587,588,597,600,608,611,614,622,625],{},[27,589,590,591,596],{},"A link to the public API reference and an ",[46,592,595],{"href":593,"rel":594},"https:\u002F\u002Fspec.openapis.org\u002Foas\u002Flatest.html",[240],"OpenAPI"," description you can generate a client from.",[27,598,599],{},"The list of official SDKs and the languages your team uses.",[27,601,602,603,607],{},"Sandbox access without a sales call, and which production behaviors the sandbox does not reproduce. ",[46,604,606],{"href":605},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Sandbox vs production"," lists the usual gaps.",[27,609,610],{},"How to trigger a failed and a refunded payment in the sandbox.",[27,612,613],{},"How write requests stay safe to retry (idempotency keys, and for how long they are stored).",[27,615,616,617,621],{},"How webhooks are signed, retried, and replayed, and whether events can arrive out of order. ",[46,618,620],{"href":619},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","Webhooks and reconciliation"," covers the patterns.",[27,623,624],{},"The full list of payment statuses and which are terminal.",[27,626,627],{},"Rate limits per endpoint and what the error response looks like.",[57,629,631],{"id":630},"what-should-the-pricing-and-contract-sections-ask","What should the pricing and contract sections ask?",[11,633,634],{},"The pricing section should ask for itemized sample quotes on your real corridors and amounts, and the contract section should ask what happens at the edges: exit, failure, and change.",[11,636,637,638,642],{},"For pricing, give each vendor the same three payments (for example, your median and largest payment on your top two corridors) and ask for the fee, the exchange rate, the reference rate it was compared to, the network fee, and the amount the recipient receives. Ask separately about monthly fees, minimum volumes, and any balance you must keep with the vendor. ",[46,639,641],{"href":640},"\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained","Stablecoin API pricing explained"," shows where fees sit outside the quote.",[11,644,645,646,651,652,657],{},"For the contract, ask about term and termination notice, data export on exit, liability caps, how fee changes are announced, and support response times. If you work with a bank partner, it will likely ask how you chose and monitor the vendor. US bank regulators' ",[46,647,650],{"href":648,"rel":649},"https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html",[240],"2023 interagency guidance on third-party relationships"," describes third-party risk management as a life cycle and says not every third party carries the same risk, so a scored RFP file is useful evidence later. For security, a ",[46,653,656],{"href":654,"rel":655},"https:\u002F\u002Fwww.aicpa-cima.com\u002Ftopic\u002Faudit-assurance\u002Faudit-and-assurance-greater-than-soc-2",[240],"SOC 2"," report covers controls relevant to security, availability, processing integrity, confidentiality, or privacy, so ask which report the vendor has and for what period.",[57,659,661],{"id":660},"what-is-a-realistic-rfp-timeline","What is a realistic RFP timeline?",[11,663,664],{},"Plan four to six weeks from first draft to signed contract. The slow parts are vendor answers and compliance review, not scoring.",[75,666,667,680],{},[78,668,669],{},[81,670,671,674,677],{},[84,672,673],{},"Week",[84,675,676],{},"Activity",[84,678,679],{},"Output",[97,681,682,692,703,714],{},[81,683,684,686,689],{},[102,685,302],{},[102,687,688],{},"Write requirements, set gates and weights, pick 3 to 5 vendors",[102,690,691],{},"RFP document and scoring sheet",[81,693,694,697,700],{},[102,695,696],{},"2 to 3",[102,698,699],{},"Vendors answer in writing; you answer clarifying questions to all vendors at once",[102,701,702],{},"Written responses and documents",[81,704,705,708,711],{},[102,706,707],{},"4",[102,709,710],{},"Apply gates, score, send follow-up questions",[102,712,713],{},"Ranked shortlist of two",[81,715,716,719,722],{},[102,717,718],{},"5 to 6",[102,720,721],{},"Sandbox verification and contract review for the top two",[102,723,724],{},"Final scores and a decision memo",[11,726,727],{},"Share clarifying answers with every vendor, not only the one who asked. Otherwise vendors answer slightly different RFPs.",[57,729,731],{"id":730},"what-are-the-limits-of-an-rfp","What are the limits of an RFP?",[11,733,734],{},"An RFP measures what vendors say and what their documents show. It does not measure what happens in production, and it rewards vendors that write well.",[24,736,737,743,749,755],{},[27,738,739,742],{},[20,740,741],{},"Written answers are claims."," Settlement windows, failure handling, and support quality only become facts in a sandbox or a small live pilot.",[27,744,745,748],{},[20,746,747],{},"RFPs favor large vendors."," Big providers have teams that answer RFPs every week. A smaller provider with a better fit can lose on polish, so score content, not formatting.",[27,750,751,754],{},[20,752,753],{},"Weights are judgment."," No framework weighting is an industry standard. Two reasonable teams can weight the same criteria differently.",[27,756,757,760],{},[20,758,759],{},"An RFP does not replace a pilot."," Use it to pick two vendors, then test.",[57,762,764],{"id":763},"how-does-blindpay-answer-a-stablecoin-api-rfp","How does BlindPay answer a stablecoin API RFP?",[11,766,767,768,575],{},"BlindPay is a stablecoin payout and collection API: it converts USDC and USDT into local currency over Pix, PIX Safe, TED, SPEI, ACH Colombia, Transfers 3.0, ACH, domestic wire, RTP, SEPA, and SWIFT (POBO\u002FCOBO) with UETR tracking and MT103 confirmations, and runs KYC, KYB, and sanctions screening inside the payment flow. It is registered with FinCEN as a Money Services Business (NMLS #2745309), and the status of other licenses is on the ",[46,769,771],{"href":770},"\u002Flicenses","licenses page",[11,773,774,775,779,780,784,785,789,790,793],{},"For the technical and pricing sections, most answers are public: development instances are free, there is no setup fee or monthly minimum, and SDKs cover Node.js, Python, Go, PHP, and Swift, as listed in the ",[46,776,778],{"href":777},"\u002Fdocs\u002Fsdks","SDK reference",". Every payout quote returns the fee breakdown and the amount the recipient receives, and expires after 5 minutes. A ",[46,781,783],{"href":782},"\u002Fdocs\u002Flearn\u002Fbilling","fee schedule endpoint"," returns the flat and percentage fee per rail and network on your instance. In development, setting a payout's request amount to $666.00 or $777.00 forces a ",[786,787,788],"code",{},"failed"," or ",[786,791,792],{},"refunded"," result, so both failure paths are testable before scoring. A refunded payout returns the stablecoins; a failed payout does not refund automatically and goes to support.",[11,795,796,797,575],{},"To score BlindPay with evidence instead of claims, create a development instance and run the ",[46,798,800],{"href":799},"\u002Fdocs\u002Fquickstart-payout","payout quickstart",{"title":802,"searchDepth":803,"depth":803,"links":804},"",2,[805,806,807,808,809,810,811,812,813,814],{"id":59,"depth":803,"text":60},{"id":69,"depth":803,"text":70},{"id":222,"depth":803,"text":223},{"id":276,"depth":803,"text":277},{"id":353,"depth":803,"text":354},{"id":578,"depth":803,"text":579},{"id":630,"depth":803,"text":631},{"id":660,"depth":803,"text":661},{"id":730,"depth":803,"text":731},{"id":763,"depth":803,"text":764},"payments","2026-10-01","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.","md",[820,823,826,829,832,835],{"q":821,"a":822},"What should a stablecoin API RFP include?","Eight sections: your requirements and flow, corridors and rails, compliance and licensing, custody and flow of funds, technical integration, reliability and support, pricing, and contract terms. Each section should have numbered questions, a response format, and a list of documents to attach, so every vendor answers the same questions in the same shape and the answers can be scored side by side.",{"q":824,"a":825},"How do you score stablecoin API vendors?","Use gates first, then scores. Gates are pass or fail: licensing for your flow, Travel Rule and sanctions controls, a written custody model, and live launch corridors. Vendors that pass get a 1 to 3 score on each weighted criterion, where 3 means the answer is proven with a document, link, or sandbox test. Set the weights before any vendor replies.",{"q":827,"a":828},"What are the hard minimums when choosing a stablecoin API?","Most evaluation frameworks treat three things as pass or fail: the provider is licensed or registered for the role it plays in your flow, it runs Travel Rule and sanctions controls on the transactions it touches, and it can state in writing who holds funds and keys at every step. Add your launch corridors being live in production as a fourth gate.",{"q":830,"a":831},"Why use a 1 to 3 scale instead of 1 to 10?","A short scale forces a decision. On a 1 to 10 scale, reviewers cluster around 6 to 8 and real differences disappear in the noise. With 1 to 3, a score of 3 needs evidence, such as a document, a public docs link, or a sandbox result, so the scale rewards proof over confident answers in a sales deck.",{"q":833,"a":834},"How long should a stablecoin API RFP take?","About four to six weeks for most fintechs: one week to write the RFP and set gates, two weeks for vendors to answer, one week to score and ask follow-ups, and one to two weeks of sandbox checks on the top two. Compliance and contract review take the longest, so request those documents with the RFP, not after scoring.",{"q":836,"a":837},"Should you share your volumes in a stablecoin API RFP?","Yes, as ranges under a mutual NDA. Pricing, limits, and onboarding depend on monthly volume, payment size, and corridors, so a vendor that does not know them will quote a generic rate you cannot compare. Ranges such as $1 million to $3 million a month are enough. You do not need to share customer names or exact revenue.",{"name":839,"steps":840},"How to run an RFP for a stablecoin API",[841,844,847,850,853],{"name":842,"text":843},"Write the requirements section","Describe your flow on one page: corridors and direction, monthly volume and typical payment size, tokens and networks you hold, who your end users are, and who must hold funds at each step. Vendors answer this section, so make it specific enough that two vendors cannot read it differently.",{"name":845,"text":846},"Set the hard-minimum gates","Pick the pass or fail requirements before any vendor replies: licensing for your flow, Travel Rule and sanctions controls, a written custody model, and your launch corridors live in production. A vendor that fails one gate is out, and its scores are never calculated.",{"name":848,"text":849},"Send the RFP with a fixed answer format","Send the same document to every vendor with numbered questions, a response template, a deadline, and a list of documents to attach. Ask for written answers only. Calls are useful for follow-ups, but they produce answers you cannot compare side by side.",{"name":851,"text":852},"Score the answers on a 1 to 3 scale","Score each criterion 1 (weak or missing), 2 (meets the need), or 3 (strong and proven with a document, link, or sandbox test). Multiply by the weight you set before sending the RFP, and add up totals only for vendors that passed every gate.",{"name":854,"text":855},"Verify the top two in a sandbox","Take the two highest-scoring vendors into their sandboxes and test the claims that drove their scores: quotes, failed and refunded payouts, webhook replays, and duplicate requests. Change a score when the sandbox disagrees with the written answer.",false,{"author":858},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template","---\ntitle: \"Stablecoin API RFP template: sections, scoring, and a vendor scorecard\"\nseoTitle: \"Stablecoin API RFP template and vendor scorecard\"\ndescription: \"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.\"\ndate: \"2026-10-01\"\nupdated: \"2026-10-01\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to run an RFP for a stablecoin API\"\n  steps:\n    - name: \"Write the requirements section\"\n      text: \"Describe your flow on one page: corridors and direction, monthly volume and typical payment size, tokens and networks you hold, who your end users are, and who must hold funds at each step. Vendors answer this section, so make it specific enough that two vendors cannot read it differently.\"\n    - name: \"Set the hard-minimum gates\"\n      text: \"Pick the pass or fail requirements before any vendor replies: licensing for your flow, Travel Rule and sanctions controls, a written custody model, and your launch corridors live in production. A vendor that fails one gate is out, and its scores are never calculated.\"\n    - name: \"Send the RFP with a fixed answer format\"\n      text: \"Send the same document to every vendor with numbered questions, a response template, a deadline, and a list of documents to attach. Ask for written answers only. Calls are useful for follow-ups, but they produce answers you cannot compare side by side.\"\n    - name: \"Score the answers on a 1 to 3 scale\"\n      text: \"Score each criterion 1 (weak or missing), 2 (meets the need), or 3 (strong and proven with a document, link, or sandbox test). Multiply by the weight you set before sending the RFP, and add up totals only for vendors that passed every gate.\"\n    - name: \"Verify the top two in a sandbox\"\n      text: \"Take the two highest-scoring vendors into their sandboxes and test the claims that drove their scores: quotes, failed and refunded payouts, webhook replays, and duplicate requests. Change a score when the sandbox disagrees with the written answer.\"\nfaq:\n  - q: \"What should a stablecoin API RFP include?\"\n    a: \"Eight sections: your requirements and flow, corridors and rails, compliance and licensing, custody and flow of funds, technical integration, reliability and support, pricing, and contract terms. Each section should have numbered questions, a response format, and a list of documents to attach, so every vendor answers the same questions in the same shape and the answers can be scored side by side.\"\n  - q: \"How do you score stablecoin API vendors?\"\n    a: \"Use gates first, then scores. Gates are pass or fail: licensing for your flow, Travel Rule and sanctions controls, a written custody model, and live launch corridors. Vendors that pass get a 1 to 3 score on each weighted criterion, where 3 means the answer is proven with a document, link, or sandbox test. Set the weights before any vendor replies.\"\n  - q: \"What are the hard minimums when choosing a stablecoin API?\"\n    a: \"Most evaluation frameworks treat three things as pass or fail: the provider is licensed or registered for the role it plays in your flow, it runs Travel Rule and sanctions controls on the transactions it touches, and it can state in writing who holds funds and keys at every step. Add your launch corridors being live in production as a fourth gate.\"\n  - q: \"Why use a 1 to 3 scale instead of 1 to 10?\"\n    a: \"A short scale forces a decision. On a 1 to 10 scale, reviewers cluster around 6 to 8 and real differences disappear in the noise. With 1 to 3, a score of 3 needs evidence, such as a document, a public docs link, or a sandbox result, so the scale rewards proof over confident answers in a sales deck.\"\n  - q: \"How long should a stablecoin API RFP take?\"\n    a: \"About four to six weeks for most fintechs: one week to write the RFP and set gates, two weeks for vendors to answer, one week to score and ask follow-ups, and one to two weeks of sandbox checks on the top two. Compliance and contract review take the longest, so request those documents with the RFP, not after scoring.\"\n  - q: \"Should you share your volumes in a stablecoin API RFP?\"\n    a: \"Yes, as ranges under a mutual NDA. Pricing, limits, and onboarding depend on monthly volume, payment size, and corridors, so a vendor that does not know them will quote a generic rate you cannot compare. Ranges such as $1 million to $3 million a month are enough. You do not need to share customer names or exact revenue.\"\n---\n\nA stablecoin API RFP (request for proposal) is a written document that asks every vendor the same numbered questions about corridors, compliance, custody, integration, reliability, pricing, and contract terms. Score the replies in two passes: pass or fail gates first, then a weighted 1 to 3 score on every criterion, using weights you set before anyone replies.\n\nMost fintechs skip the RFP and go straight to demos. That works until three vendors describe \"global coverage\" in three different ways and nobody can say which is better. A short, structured RFP fixes that.\n\n**Key takeaways**\n\n- An RFP is useful because it fixes the questions and the answer format. Comparability is the whole point.\n- Set the pass or fail gates and the weights before sending. Changing them after replies arrive invites bias.\n- Gates come first: licensing, Travel Rule and sanctions controls, custody model, and live launch corridors.\n- Score 1 to 3. A 3 needs proof, such as a document, a public docs link, or a sandbox test.\n- Verify the top two vendors in a sandbox before signing. Written answers are claims until tested.\n\nIf you are still working out which part of the stack you are buying, read [what stablecoin infrastructure is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure) first, then [the types of stablecoin APIs](\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis). An RFP only works when every vendor on the list is solving the same problem.\n\n## What is a stablecoin API RFP?\n\nA stablecoin API RFP is a document a buyer sends to several providers asking for written, structured answers about how the provider would handle the buyer's payment flow. It replaces open-ended sales calls with numbered questions, a response template, a deadline, and a list of required documents.\n\nAn RFP is different from a questionnaire. A questionnaire asks a vendor about itself. An RFP starts with your flow (corridors, volumes, users, custody needs) and asks how the vendor would serve it. That framing matters, because a stablecoin API that is strong for card issuing can be weak for local payouts, and only your flow tells you which one you need.\n\n## What sections should a stablecoin API RFP include?\n\nA stablecoin API RFP should include eight sections, each with numbered questions and a list of documents to attach. Put your own requirements first, so every answer that follows is about your flow.\n\n| Section | What you write | What you ask the vendor | Documents to request |\n| --- | --- | --- | --- |\n| 1. Requirements and flow | Corridors, direction, monthly volume range, payment size, tokens and networks, end-user types | Confirm which parts of the flow you would handle, and which you would not | None |\n| 2. Corridors and rails | Countries, currencies, and rails you need at launch and in 12 months | Which rail and country pairs are live in production, in which direction, with what settlement window | Rails list from public docs |\n| 3. Compliance and licensing | Your own licenses, if any, and who your end users are | Which licenses or registrations cover your flow; who runs KYC, KYB, sanctions screening, Travel Rule, and monitoring | License list, AML and sanctions policy statement |\n| 4. Custody and flow of funds | Who must hold funds at each step | Who holds stablecoins, fiat, and keys at each step; what happens to funds in a payment that cannot complete | Flow-of-funds diagram |\n| 5. Technical integration | Your stack, languages, and ledger model | API style, OpenAPI spec, SDKs, sandbox access, webhooks, idempotency, error model | Docs links, sandbox credentials |\n| 6. Reliability and support | Your uptime and support needs | SLAs, status page, incident history, support hours and channels, escalation path | SLA document, incident summary |\n| 7. Pricing | Volume range and payment size per corridor | Itemized sample quotes for your top corridors, monthly fees, minimums, pre-funding needs | Sample quotes, order form |\n| 8. Contract | Your legal requirements | Term, termination, notice, data export on exit, liability, change-of-terms process | Standard contract |\n\nKeep the vendor questions to 40 or fewer across all eight sections. Long RFPs get long, vague answers. If you need a deeper question bank for a specific section, the [30 due diligence questions](\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence) are organized by category and drop into sections 3, 4, 6, and 8.\n\n## Which requirements should be pass or fail gates?\n\nGates are the requirements where a weak answer cannot be offset by a strong score somewhere else. Procurement frameworks for stablecoin payments usually treat licensing, Travel Rule compliance, and the custody model as hard minimums, and most buyers add live corridors.\n\n1. **Licensing for your flow.** The vendor holds the licenses or registrations needed for the role it plays in your flow, in the markets you pay into. In the US you can check federal money services business registration yourself in FinCEN's [MSB registrant search](https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fmsb-state-selector). [Which license a stablecoin payment flow needs](\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi) explains the categories.\n2. **Travel Rule and sanctions controls.** The vendor screens every counterparty and transaction it touches and exchanges originator and beneficiary data where the Travel Rule applies.\n3. **A written custody model.** The vendor states in writing who holds stablecoins, fiat, and keys at every step, and what happens to funds in a payment that fails. [Custodial vs non-custodial off-ramps](\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps) covers why this matters in an insolvency.\n4. **Launch corridors live in production.** Every corridor you need on day one is live today, in the direction you need. Roadmap items do not pass.\n\nA vendor that fails one gate is out. Do not calculate its score. This keeps a cheap or well-documented vendor from winning on points while failing on the one thing that would stop your launch.\n\n## How do you score answers on a 1 to 3 scale?\n\nScore each criterion 1, 2, or 3, multiply by its weight, and add up. The short scale forces a decision and makes evidence the difference between a 2 and a 3.\n\n| Score | Meaning | Evidence needed |\n| --- | --- | --- |\n| 1 | Weak, vague, or missing | None, or a sales claim only |\n| 2 | Meets the requirement | A clear written answer |\n| 3 | Strong and proven | A document, a public docs link, or a sandbox result that confirms the answer |\n\nWeights depend on your business. A payroll platform paying contractors in Latin America will weight corridors and settlement heavily. A regulated bank will weight licensing, security, and contract terms. Decide the weights before sending the RFP and write them into the scoring sheet, so nobody adjusts them after a favorite vendor replies.\n\nTwo rules keep scoring honest:\n\n- **Score per criterion, not per vendor.** Score all vendors on criterion 1, then all on criterion 2. Reading one vendor end to end inflates its scores.\n- **Two scorers per section.** Engineering scores technical sections, compliance scores sections 3 and 4, finance scores pricing. Average the two, and discuss any gap of 2 points.\n\n## What does a stablecoin API scorecard look like?\n\nA scorecard lists every weighted criterion with blank score columns for each vendor, plus the gates above it. Copy the table below into a spreadsheet and adjust the weights to your flow. The weights shown are an example, not an industry standard.\n\n**Gates (pass or fail for each vendor):** licensing for your flow, Travel Rule and sanctions controls, written custody model, launch corridors live.\n\n| Criterion | Example weight | Vendor A (1 to 3) | Vendor B (1 to 3) | Vendor C (1 to 3) |\n| --- | --- | --- | --- | --- |\n| Corridors and rails beyond launch needs | 12% |  |  |  |\n| Settlement windows per rail, in writing | 10% |  |  |  |\n| Compliance split (KYC, KYB, screening, monitoring) | 10% |  |  |  |\n| Supported stablecoins and networks | 6% |  |  |  |\n| Quote and fee transparency | 12% |  |  |  |\n| Pre-funding requirement | 8% |  |  |  |\n| API design and OpenAPI spec | 8% |  |  |  |\n| SDKs and sandbox access | 6% |  |  |  |\n| Webhooks and event reliability | 8% |  |  |  |\n| Reconciliation and reporting | 6% |  |  |  |\n| SLAs, support, and refund handling | 8% |  |  |  |\n| Contract terms and exit | 6% |  |  |  |\n| **Weighted total (max 3.00)** | **100%** |  |  |  |\n\nTo get the weighted total, multiply each score by its weight and add the results. A vendor scoring 2 on everything totals 2.00. Anything above 2.50 means most answers came with proof.\n\nFor what a good and a bad answer look like on the six criteria that eliminate vendors fastest, see [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api).\n\n## What questions belong in the technical section?\n\nThe technical section should ask how the API behaves when things go wrong, not only how a successful payment works. Every vendor can show a happy path in a demo.\n\nAsk for:\n\n- A link to the public API reference and an [OpenAPI](https:\u002F\u002Fspec.openapis.org\u002Foas\u002Flatest.html) description you can generate a client from.\n- The list of official SDKs and the languages your team uses.\n- Sandbox access without a sales call, and which production behaviors the sandbox does not reproduce. [Sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) lists the usual gaps.\n- How to trigger a failed and a refunded payment in the sandbox.\n- How write requests stay safe to retry (idempotency keys, and for how long they are stored).\n- How webhooks are signed, retried, and replayed, and whether events can arrive out of order. [Webhooks and reconciliation](\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation) covers the patterns.\n- The full list of payment statuses and which are terminal.\n- Rate limits per endpoint and what the error response looks like.\n\n## What should the pricing and contract sections ask?\n\nThe pricing section should ask for itemized sample quotes on your real corridors and amounts, and the contract section should ask what happens at the edges: exit, failure, and change.\n\nFor pricing, give each vendor the same three payments (for example, your median and largest payment on your top two corridors) and ask for the fee, the exchange rate, the reference rate it was compared to, the network fee, and the amount the recipient receives. Ask separately about monthly fees, minimum volumes, and any balance you must keep with the vendor. [Stablecoin API pricing explained](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) shows where fees sit outside the quote.\n\nFor the contract, ask about term and termination notice, data export on exit, liability caps, how fee changes are announced, and support response times. If you work with a bank partner, it will likely ask how you chose and monitor the vendor. US bank regulators' [2023 interagency guidance on third-party relationships](https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html) describes third-party risk management as a life cycle and says not every third party carries the same risk, so a scored RFP file is useful evidence later. For security, a [SOC 2](https:\u002F\u002Fwww.aicpa-cima.com\u002Ftopic\u002Faudit-assurance\u002Faudit-and-assurance-greater-than-soc-2) report covers controls relevant to security, availability, processing integrity, confidentiality, or privacy, so ask which report the vendor has and for what period.\n\n## What is a realistic RFP timeline?\n\nPlan four to six weeks from first draft to signed contract. The slow parts are vendor answers and compliance review, not scoring.\n\n| Week | Activity | Output |\n| --- | --- | --- |\n| 1 | Write requirements, set gates and weights, pick 3 to 5 vendors | RFP document and scoring sheet |\n| 2 to 3 | Vendors answer in writing; you answer clarifying questions to all vendors at once | Written responses and documents |\n| 4 | Apply gates, score, send follow-up questions | Ranked shortlist of two |\n| 5 to 6 | Sandbox verification and contract review for the top two | Final scores and a decision memo |\n\nShare clarifying answers with every vendor, not only the one who asked. Otherwise vendors answer slightly different RFPs.\n\n## What are the limits of an RFP?\n\nAn RFP measures what vendors say and what their documents show. It does not measure what happens in production, and it rewards vendors that write well.\n\n- **Written answers are claims.** Settlement windows, failure handling, and support quality only become facts in a sandbox or a small live pilot.\n- **RFPs favor large vendors.** Big providers have teams that answer RFPs every week. A smaller provider with a better fit can lose on polish, so score content, not formatting.\n- **Weights are judgment.** No framework weighting is an industry standard. Two reasonable teams can weight the same criteria differently.\n- **An RFP does not replace a pilot.** Use it to pick two vendors, then test.\n\n## How does BlindPay answer a stablecoin API RFP?\n\nBlindPay is a stablecoin payout and collection API: it converts USDC and USDT into local currency over Pix, PIX Safe, TED, SPEI, ACH Colombia, Transfers 3.0, ACH, domestic wire, RTP, SEPA, and SWIFT (POBO\u002FCOBO) with UETR tracking and MT103 confirmations, and runs KYC, KYB, and sanctions screening inside the payment flow. It is registered with FinCEN as a Money Services Business (NMLS #2745309), and the status of other licenses is on the [licenses page](\u002Flicenses).\n\nFor the technical and pricing sections, most answers are public: development instances are free, there is no setup fee or monthly minimum, and SDKs cover Node.js, Python, Go, PHP, and Swift, as listed in the [SDK reference](\u002Fdocs\u002Fsdks). Every payout quote returns the fee breakdown and the amount the recipient receives, and expires after 5 minutes. A [fee schedule endpoint](\u002Fdocs\u002Flearn\u002Fbilling) returns the flat and percentage fee per rail and network on your instance. In development, setting a payout's request amount to $666.00 or $777.00 forces a `failed` or `refunded` result, so both failure paths are testable before scoring. A refunded payout returns the stablecoins; a failed payout does not refund automatically and goes to support.\n\nTo score BlindPay with evidence instead of claims, create a development instance and run the [payout quickstart](\u002Fdocs\u002Fquickstart-payout).\n",{"title":5,"description":817},"Stablecoin API RFP template and vendor scorecard","resources\u002Fmore\u002Fstablecoin-api-rfp-template","RCM4ZlgwdNDiME1rqNZW8QNBIEZfaE5uRHSMeJne1Go",[867,871,875,879,883,887,891,895,899,903,907,911,915,918,922,926,930,934,938,942,946,950,954,958,962,966,970,974,978,982,986,990,994,998,1002,1006,1010,1014,1018,1022,1026,1030,1034,1038,1042,1046,1050,1054,1058,1062,1063,1067,1071,1075,1079,1082,1085,1089,1093,1097,1101,1105,1109,1113,1117,1121,1125,1129,1133,1137,1141,1145,1149,1153,1157,1161,1165,1169,1173,1177,1181,1185,1189,1193,1197,1200,1204,1208,1212,1216],{"path":868,"title":869,"description":870},"\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":872,"title":873,"description":874},"\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":876,"title":877,"description":878},"\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":880,"title":881,"description":882},"\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":884,"title":885,"description":886},"\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":888,"title":889,"description":890},"\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":892,"title":893,"description":894},"\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":896,"title":897,"description":898},"\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":900,"title":901,"description":902},"\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":904,"title":905,"description":906},"\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":908,"title":909,"description":910},"\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":912,"title":913,"description":914},"\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":262,"title":916,"description":917},"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":919,"title":920,"description":921},"\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":923,"title":924,"description":925},"\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":927,"title":928,"description":929},"\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":931,"title":932,"description":933},"\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":935,"title":936,"description":937},"\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":939,"title":940,"description":941},"\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":943,"title":944,"description":945},"\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":947,"title":948,"description":949},"\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":951,"title":952,"description":953},"\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":955,"title":956,"description":957},"\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":959,"title":960,"description":961},"\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":963,"title":964,"description":965},"\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":967,"title":968,"description":969},"\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":971,"title":972,"description":973},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api","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":975,"title":976,"description":977},"\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":979,"title":980,"description":981},"\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":983,"title":984,"description":985},"\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":987,"title":988,"description":989},"\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":991,"title":992,"description":993},"\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":995,"title":996,"description":997},"\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":999,"title":1000,"description":1001},"\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":1003,"title":1004,"description":1005},"\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":1007,"title":1008,"description":1009},"\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":1011,"title":1012,"description":1013},"\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":1015,"title":1016,"description":1017},"\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":1019,"title":1020,"description":1021},"\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":1023,"title":1024,"description":1025},"\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":1027,"title":1028,"description":1029},"\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":1031,"title":1032,"description":1033},"\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":1035,"title":1036,"description":1037},"\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api","On-ramp widget vs API: which integration fits your product?","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.",{"path":1039,"title":1040,"description":1041},"\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":1043,"title":1044,"description":1045},"\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":1047,"title":1048,"description":1049},"\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":1051,"title":1052,"description":1053},"\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":1055,"title":1056,"description":1057},"\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":1059,"title":1060,"description":1061},"\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":860,"title":5,"description":817},{"path":1064,"title":1065,"description":1066},"\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":1068,"title":1069,"description":1070},"\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":1072,"title":1073,"description":1074},"\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":1076,"title":1077,"description":1078},"\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":605,"title":1080,"description":1081},"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":619,"title":1083,"description":1084},"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":1086,"title":1087,"description":1088},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","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":1090,"title":1091,"description":1092},"\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":1094,"title":1095,"description":1096},"\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":1098,"title":1099,"description":1100},"\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":1102,"title":1103,"description":1104},"\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":1106,"title":1107,"description":1108},"\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":1110,"title":1111,"description":1112},"\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":1114,"title":1115,"description":1116},"\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":1118,"title":1119,"description":1120},"\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":1122,"title":1123,"description":1124},"\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":1126,"title":1127,"description":1128},"\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":1130,"title":1131,"description":1132},"\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":1134,"title":1135,"description":1136},"\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":1138,"title":1139,"description":1140},"\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":1142,"title":1143,"description":1144},"\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":1146,"title":1147,"description":1148},"\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":1150,"title":1151,"description":1152},"\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":1154,"title":1155,"description":1156},"\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":1158,"title":1159,"description":1160},"\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":1162,"title":1163,"description":1164},"\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":1166,"title":1167,"description":1168},"\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":1170,"title":1171,"description":1172},"\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":1174,"title":1175,"description":1176},"\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":1178,"title":1179,"description":1180},"\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":1182,"title":1183,"description":1184},"\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":1186,"title":1187,"description":1188},"\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":1190,"title":1191,"description":1192},"\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":1194,"title":1195,"description":1196},"\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":217,"title":1198,"description":1199},"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":1201,"title":1202,"description":1203},"\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":1205,"title":1206,"description":1207},"\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":1209,"title":1210,"description":1211},"\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":1213,"title":1214,"description":1215},"\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":1217,"title":1218,"description":1219},"\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.",1791469670005]