[{"data":1,"prerenderedAt":1285},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan":3,"resources-category-stablecoin-api-30-day-evaluation-plan":953},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":920,"categoryType":6,"compare":6,"contributors":6,"date":921,"description":922,"extension":923,"faq":924,"howto":6,"isBlog":943,"isChangelog":943,"meta":944,"navigation":946,"path":947,"pillar":943,"products":6,"rawbody":948,"role":6,"seo":949,"seoTitle":950,"stem":951,"thumbnail":6,"updated":921,"__hash__":952},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan.md","How to evaluate a stablecoin API in 30 days: a week-by-week plan",null,{"type":8,"value":9,"toc":907},"minimark",[10,14,17,23,42,51,56,59,137,140,144,147,190,196,200,203,329,346,351,355,358,382,391,397,402,406,409,447,450,520,525,529,532,659,666,670,673,676,679,682,849,852,856,859,864,878,884,887,891,899],[11,12,13],"p",{},"To evaluate a stablecoin API in 30 days, give each week one job: shortlist providers in writing in week 1, break their sandboxes in week 2, run compliance and commercial review in week 3, and pilot real payouts on one corridor in week 4. Decide on day 30 from measured cost, speed, and failure handling, not from demos.",[11,15,16],{},"Feature lists converge. Every provider claims quotes, webhooks, and global rails. The differences show up when a payout fails, when a quote expires, and when finance tries to close the month. This plan is built to surface those three things fast.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"Time-box the evaluation. Thirty days with weekly exit criteria beats an open-ended \"let's try a few providers.\"",[27,31,32],{},"Spend sandbox week on failure cases. A successful payout proves almost nothing.",[27,34,35],{},"Start compliance and contracting on day one. They are the slowest part, not the code.",[27,37,38],{},"Measure all-in cost: what you sent minus what arrived, valued at a reference rate, plus fixed fees and pre-funding.",[27,40,41],{},"Pilot with real money on one corridor. Only the bank leg shows real settlement time.",[11,43,44,45,50],{},"If you're still sorting out which kind of provider you need, read ",[46,47,49],"a",{"href":48},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","the types of stablecoin APIs"," first. This plan assumes you've narrowed it to payment APIs that convert between stablecoins and local currency.",[52,53,55],"h2",{"id":54},"who-needs-to-be-part-of-a-stablecoin-api-evaluation","Who needs to be part of a stablecoin API evaluation?",[11,57,58],{},"Five owners, each with one sign-off. Without all five, the evaluation ends in a decision that one team has to undo later.",[60,61,62,78],"table",{},[63,64,65],"thead",{},[66,67,68,72,75],"tr",{},[69,70,71],"th",{},"Owner",[69,73,74],{},"What they evaluate",[69,76,77],{},"What they sign off on",[79,80,81,93,104,115,126],"tbody",{},[66,82,83,87,90],{},[84,85,86],"td",{},"Engineering",[84,88,89],{},"API design, SDKs, webhooks, failure behavior",[84,91,92],{},"The sandbox test results",[66,94,95,98,101],{},[84,96,97],{},"Compliance",[84,99,100],{},"Licensing, KYC and KYB split, sanctions screening, record keeping",[84,102,103],{},"The responsibility split, in writing",[66,105,106,109,112],{},[84,107,108],{},"Finance",[84,110,111],{},"All-in cost, invoicing, reconciliation",[84,113,114],{},"The cost model and the pilot reconciliation",[66,116,117,120,123],{},[84,118,119],{},"Operations",[84,121,122],{},"Support response, incident process, recipient issues",[84,124,125],{},"The support runbook",[66,127,128,131,134],{},[84,129,130],{},"Product",[84,132,133],{},"Corridors, user experience, launch date",[84,135,136],{},"The final decision",[11,138,139],{},"Name the owners on day one, and give each one a calendar slot in week 4 to review pilot data.",[52,141,143],{"id":142},"what-should-happen-in-week-1","What should happen in week 1?",[11,145,146],{},"Week 1 turns a long list into two or three providers that answered your questions in writing.",[148,149,150,156,162,178,184],"ol",{},[27,151,152,155],{},[20,153,154],{},"Write the requirements on one page."," Corridors, rails, expected monthly volume and payout size, tokens and chains you hold, who must hold funds at each step, and who verifies your end users.",[27,157,158,161],{},[20,159,160],{},"Map providers by category."," Issuers, custodial wallet platforms, orchestration layers, and payout APIs solve different problems. Drop any that don't do the job on your page.",[27,163,164,167,168,172,173,177],{},[20,165,166],{},"Send written questions."," Use a fixed list so answers are comparable. The ",[46,169,171],{"href":170},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","six questions that matter"," are a short version; the ",[46,174,176],{"href":175},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","30 due diligence questions"," are the long one.",[27,179,180,183],{},[20,181,182],{},"Ask for a sandbox and a sample quote."," A sample quote for your top corridor at your typical amount, with fees itemized.",[27,185,186,189],{},[20,187,188],{},"Start compliance and contract review now."," Request the provider's licensing summary and the standard contract on day one, not in week 3.",[11,191,192,195],{},[20,193,194],{},"Exit criterion:"," two or three providers with written answers, sandbox access, and a sample quote. A provider that can't give you a sandbox in week 1 is telling you something.",[52,197,199],{"id":198},"what-should-you-test-in-the-sandbox-in-week-2","What should you test in the sandbox in week 2?",[11,201,202],{},"Test the failure paths. Every sandbox handles the happy path; the question is whether your system ends each unhappy case in the right state without manual fixes.",[60,204,205,218],{},[63,206,207],{},[66,208,209,212,215],{},[69,210,211],{},"Test",[69,213,214],{},"How to trigger it",[69,216,217],{},"Pass if",[79,219,220,231,242,252,263,274,285,296,307,318],{},[66,221,222,225,228],{},[84,223,224],{},"Successful payout",[84,226,227],{},"Normal quote and execution",[84,229,230],{},"Status and webhooks arrive in order; ledger balances",[66,232,233,236,239],{},[84,234,235],{},"Failed payout",[84,237,238],{},"The provider's documented test trigger",[84,240,241],{},"Your ledger marks it failed and doesn't release funds twice",[66,243,244,247,249],{},[84,245,246],{},"Refunded payout",[84,248,238],{},[84,250,251],{},"Stablecoins return and your ledger shows the refund",[66,253,254,257,260],{},[84,255,256],{},"Expired quote",[84,258,259],{},"Execute after the quote window",[84,261,262],{},"You get a clear error and request a new quote",[66,264,265,268,271],{},[84,266,267],{},"Duplicate request",[84,269,270],{},"Same idempotency key, sent twice",[84,272,273],{},"One payout exists, not two",[66,275,276,279,282],{},[84,277,278],{},"Duplicate webhook",[84,280,281],{},"Replay an event from the dashboard",[84,283,284],{},"Your handler skips the repeat",[66,286,287,290,293],{},[84,288,289],{},"Out-of-order webhooks",[84,291,292],{},"Delay one event in your receiver",[84,294,295],{},"Final state is still correct",[66,297,298,301,304],{},[84,299,300],{},"Invalid bank details",[84,302,303],{},"Bad account number or check digit",[84,305,306],{},"Rejected at creation, not days later",[66,308,309,312,315],{},[84,310,311],{},"Compliance hold",[84,313,314],{},"Ask the provider how to simulate one",[84,316,317],{},"Your UI shows \"under review,\" not \"failed\"",[66,319,320,323,326],{},[84,321,322],{},"Rate limit",[84,324,325],{},"Burst requests",[84,327,328],{},"Your client backs off and retries",[11,330,331,332,336,337,341,342,345],{},"Sandboxes fake some of these. ",[46,333,335],{"href":334},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Sandbox vs production"," lists what typically doesn't carry over, so note which tests a provider can't run at all. On BlindPay, development instances are free, and setting a payout's request amount to 666.00 or 777.00 forces a ",[338,339,340],"code",{},"failed"," or ",[338,343,344],{},"refunded"," result, so both failure paths take two API calls.",[11,347,348,350],{},[20,349,194],{}," each provider's results in one table, with every failing test explained.",[52,352,354],{"id":353},"what-does-week-3-cover","What does week 3 cover?",[11,356,357],{},"Week 3 is compliance and commercial review: who is licensed for what, who does which checks, and what the contract says when something goes wrong.",[11,359,360,363,364,370,371,376,377,381],{},[20,361,362],{},"Compliance."," Check registrations yourself instead of trusting a slide. In the US, FinCEN's ",[46,365,369],{"href":366,"rel":367},"https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fmsb-state-selector",[368],"nofollow","MSB registrant search"," shows federal registration, and ",[46,372,375],{"href":373,"rel":374},"https:\u002F\u002Fwww.nmlsconsumeraccess.org\u002F",[368],"NMLS Consumer Access"," shows many state licenses. Then write down who runs KYC, KYB, sanctions screening, transaction monitoring, and record keeping for your flow. ",[46,378,380],{"href":379},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi","Which license a stablecoin payment flow needs"," explains the categories.",[11,383,384,385,390],{},"If you work with a bank partner, expect it to ask how you chose and monitor the provider. US bank regulators' ",[46,386,389],{"href":387,"rel":388},"https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html",[368],"2023 interagency guidance on third-party relationships"," treats vendor risk as a life cycle and says not every third party carries the same risk. Your week 3 notes become that evidence.",[11,392,393,396],{},[20,394,395],{},"Commercial."," Get pricing in writing for your corridors and amounts, including anything billed monthly. Read the contract for minimums, termination terms, data export on exit, support response times, and what happens to funds in a payout that can't complete.",[11,398,399,401],{},[20,400,194],{}," compliance has a signed responsibility split, and finance has written pricing for the pilot corridor.",[52,403,405],{"id":404},"how-do-you-run-the-week-4-pilot","How do you run the week 4 pilot?",[11,407,408],{},"Run real payouts on one corridor, in small amounts, and record everything. This is where settlement time, support quality, and reconciliation become numbers.",[148,410,411,417,423,429,435,441],{},[27,412,413,416],{},[20,414,415],{},"Pick one corridor"," that matters to your launch.",[27,418,419,422],{},[20,420,421],{},"Pay internal recipients first."," Team members or your own accounts in the destination country.",[27,424,425,428],{},[20,426,427],{},"Cap each payout"," at an amount you'd accept losing time on, not money.",[27,430,431,434],{},[20,432,433],{},"Add a handful of real recipients"," once internal payouts reconcile.",[27,436,437,440],{},[20,438,439],{},"File one support ticket on purpose."," Ask a real question and time the answer.",[27,442,443,446],{},[20,444,445],{},"Close the books on the pilot."," Finance reconciles every payout against the provider's records.",[11,448,449],{},"Log every pilot payout with the same fields, for every provider:",[60,451,452,462],{},[63,453,454],{},[66,455,456,459],{},[69,457,458],{},"Field",[69,460,461],{},"Why you need it",[79,463,464,472,480,488,496,504,512],{},[66,465,466,469],{},[84,467,468],{},"Quote ID and payout ID",[84,470,471],{},"Ties your ledger to the provider's",[66,473,474,477],{},[84,475,476],{},"Amount sent and amount received",[84,478,479],{},"The basis of all-in cost",[66,481,482,485],{},[84,483,484],{},"Reference rate at quote time",[84,486,487],{},"Lets you price the spread",[66,489,490,493],{},[84,491,492],{},"Quote, execution, and completion timestamps",[84,494,495],{},"Real settlement time",[66,497,498,501],{},[84,499,500],{},"Rail reference (tracking key, UETR, trace ID)",[84,502,503],{},"Proof of delivery for recipients",[66,505,506,509],{},[84,507,508],{},"Status history",[84,510,511],{},"Shows whether statuses are honest",[66,513,514,517],{},[84,515,516],{},"Support time, if any",[84,518,519],{},"Real support quality",[11,521,522,524],{},[20,523,194],{}," every pilot payout is either completed and reconciled, or explained.",[52,526,528],{"id":527},"where-do-stablecoin-api-costs-hide","Where do stablecoin API costs hide?",[11,530,531],{},"Most of the cost isn't in the fee line. It sits in the rate, in the contract, or in capital you never see on an invoice.",[60,533,534,547],{},[63,535,536],{},[66,537,538,541,544],{},[69,539,540],{},"Cost",[69,542,543],{},"Where it hides",[69,545,546],{},"How to catch it in the evaluation",[79,548,549,560,571,582,593,604,615,626,637,648],{},[66,550,551,554,557],{},[84,552,553],{},"FX spread",[84,555,556],{},"Inside the exchange rate, not as a fee",[84,558,559],{},"Compare each quote to a reference rate recorded at the same minute",[66,561,562,565,568],{},[84,563,564],{},"Percentage fee",[84,566,567],{},"The quote's fee fields, or a blended rate",[84,569,570],{},"Ask for itemized quotes",[66,572,573,576,579],{},[84,574,575],{},"Flat per-payout fee",[84,577,578],{},"Small print; hurts small payouts most",[84,580,581],{},"Model your real payout size, not an average",[66,583,584,587,590],{},[84,585,586],{},"Network fee",[84,588,589],{},"Which side pays gas, and on which chain",[84,591,592],{},"Check who pays on the chain you'll use",[66,594,595,598,601],{},[84,596,597],{},"Monthly or platform fee",[84,599,600],{},"The contract, not the pricing page",[84,602,603],{},"Read the order form",[66,605,606,609,612],{},[84,607,608],{},"Minimum volume",[84,610,611],{},"The contract",[84,613,614],{},"Model a slow month",[66,616,617,620,623],{},[84,618,619],{},"Pre-funding",[84,621,622],{},"Capital parked in a destination account",[84,624,625],{},"Price it at your cost of capital",[66,627,628,631,634],{},[84,629,630],{},"Requotes",[84,632,633],{},"Rate movement between expired quotes",[84,635,636],{},"Count requotes in the pilot",[66,638,639,642,645],{},[84,640,641],{},"Failure handling",[84,643,644],{},"Return fees and staff time",[84,646,647],{},"Count failed and returned payouts in the pilot",[66,649,650,653,656],{},[84,651,652],{},"Invoice-billed fees",[84,654,655],{},"Charged at month end, not deducted from the payout",[84,657,658],{},"Read the first invoice, not just the quotes",[11,660,661,665],{},[46,662,664],{"href":663},"\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained","Stablecoin API pricing explained"," goes deeper on mint fees, burn fees, and itemized quotes.",[52,667,669],{"id":668},"how-do-you-compare-all-in-cost-between-providers","How do you compare all-in cost between providers?",[11,671,672],{},"Compare all-in cost: the dollar value you sent minus what arrived, valued at a reference rate, plus fixed monthly costs and the carrying cost of any pre-funded balance, divided by volume.",[11,674,675],{},"All-in cost = (value sent − value received at the reference rate) + monthly fees + pre-funding cost",[11,677,678],{},"Here's a worked example. Every number is hypothetical and chosen to show the method. None describes a real provider.",[11,680,681],{},"Assumptions: payouts of $1,000 each to one corridor, a network fee of $0.05 per payout, and a 5% annual cost of capital. Provider B requires a pre-funded balance equal to half a month's volume.",[60,683,684,703],{},[63,685,686],{},[66,687,688,691,694,697,700],{},[69,689,690],{},"Cost line",[69,692,693],{},"Provider A, 100 payouts",[69,695,696],{},"Provider B, 100 payouts",[69,698,699],{},"Provider A, 1,000 payouts",[69,701,702],{},"Provider B, 1,000 payouts",[79,704,705,722,736,753,766,781,796,823],{},[66,706,707,710,713,716,719],{},[84,708,709],{},"Percentage fee (A 0.50%, B 0.20%)",[84,711,712],{},"$500",[84,714,715],{},"$200",[84,717,718],{},"$5,000",[84,720,721],{},"$2,000",[66,723,724,727,730,732,734],{},[84,725,726],{},"Flat fee (A $0, B $2)",[84,728,729],{},"$0",[84,731,715],{},[84,733,729],{},[84,735,721],{},[66,737,738,741,744,747,750],{},[84,739,740],{},"Spread vs reference (A 0.30%, B 0.60%)",[84,742,743],{},"$300",[84,745,746],{},"$600",[84,748,749],{},"$3,000",[84,751,752],{},"$6,000",[66,754,755,758,760,762,764],{},[84,756,757],{},"Monthly platform fee (A $0, B $500)",[84,759,729],{},[84,761,712],{},[84,763,729],{},[84,765,712],{},[66,767,768,771,773,776,778],{},[84,769,770],{},"Pre-funding cost at 5% a year, one month",[84,772,729],{},[84,774,775],{},"$208",[84,777,729],{},[84,779,780],{},"$2,083",[66,782,783,786,789,791,794],{},[84,784,785],{},"Network fees",[84,787,788],{},"$5",[84,790,788],{},[84,792,793],{},"$50",[84,795,793],{},[66,797,798,803,808,813,818],{},[84,799,800],{},[20,801,802],{},"Total",[84,804,805],{},[20,806,807],{},"$805",[84,809,810],{},[20,811,812],{},"$1,713",[84,814,815],{},[20,816,817],{},"$8,050",[84,819,820],{},[20,821,822],{},"$12,633",[66,824,825,830,835,840,844],{},[84,826,827],{},[20,828,829],{},"All-in cost as % of volume",[84,831,832],{},[20,833,834],{},"0.81%",[84,836,837],{},[20,838,839],{},"1.71%",[84,841,842],{},[20,843,834],{},[84,845,846],{},[20,847,848],{},"1.26%",[11,850,851],{},"Provider B has the lower headline fee and still costs more at both volumes. The spread and the parked capital do the damage, and neither appears as a fee line. Fixed costs shrink as volume grows, so run the model at your expected volume and at a slow month.",[52,853,855],{"id":854},"how-do-you-make-the-decision-on-day-30","How do you make the decision on day 30?",[11,857,858],{},"Use gates first, then scores. A provider that fails a gate is out, no matter how cheap it is.",[11,860,861],{},[20,862,863],{},"Gates (pass or fail):",[148,865,866,869,872,875],{},[27,867,868],{},"Your launch corridors are live in production, in the direction you need.",[27,870,871],{},"Compliance signed the responsibility split.",[27,873,874],{},"Every sandbox failure test ended in the right state, or the gap is understood.",[27,876,877],{},"Every pilot payout reconciled.",[11,879,880,883],{},[20,881,882],{},"Scores (weight them to your business):"," all-in cost at expected volume, median and slowest settlement time in the pilot, support response time, and developer experience as your engineers rated it.",[11,885,886],{},"Write the decision down with the pilot log attached. In six months, when someone asks why you picked this provider, that page is the answer.",[52,888,890],{"id":889},"how-does-blindpay-fit-a-30-day-evaluation","How does BlindPay fit a 30-day evaluation?",[11,892,893,894,898],{},"BlindPay is built to be tested before anyone signs. Development instances are free, there's no setup fee or monthly minimum, and every quote returns the sender amount, receiver amount, and fee fields before you execute, so most of the pilot log above comes straight from the API. A ",[46,895,897],{"href":896},"\u002Fdocs\u002Flearn\u002Fbilling","fee schedule endpoint"," returns the flat and percentage fee per rail and network on your instance. SDKs cover Node.js, Python, Go, PHP, and Swift, and payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) with no pre-funding.",[11,900,901,902,906],{},"Start week 2 today: create a development instance and run the failure tests from the ",[46,903,905],{"href":904},"\u002Fdocs\u002Fquickstart-payout","payout quickstart",".",{"title":908,"searchDepth":909,"depth":909,"links":910},"",2,[911,912,913,914,915,916,917,918,919],{"id":54,"depth":909,"text":55},{"id":142,"depth":909,"text":143},{"id":198,"depth":909,"text":199},{"id":353,"depth":909,"text":354},{"id":404,"depth":909,"text":405},{"id":527,"depth":909,"text":528},{"id":668,"depth":909,"text":669},{"id":854,"depth":909,"text":855},{"id":889,"depth":909,"text":890},"payments","2026-10-06","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.","md",[925,928,931,934,937,940],{"q":926,"a":927},"How long does it take to evaluate a stablecoin API?","About 30 days is enough for most fintechs if the work is split by week: a written shortlist in week 1, sandbox testing in week 2, compliance and commercial review in week 3, and a small live pilot in week 4. Longer evaluations usually stall in contracting or compliance review, not in engineering, so start those conversations on day one.",{"q":929,"a":930},"What should you test in a stablecoin API sandbox?","Test the unhappy paths, not only a successful payout. Force a failed payout and a refunded one, let a quote expire, send the same request twice with one idempotency key, replay a webhook, submit invalid bank details, and hit the rate limit. A provider passes when your system ends each case in the right state without a person fixing the ledger.",{"q":932,"a":933},"How do you compare the real cost of two stablecoin APIs?","Compare all-in cost on the same corridor, the same amounts, and the same day. Take the dollar value you sent, subtract what the recipient received converted at a reference rate you record at quote time, then add monthly fees and the cost of any pre-funded balance. Divide by volume. Headline fees alone often rank providers in the wrong order.",{"q":935,"a":936},"Should a stablecoin API pilot use real money?","Yes, in small amounts on one corridor. Sandboxes skip the bank leg, so only real payouts show settlement time, how recipients' banks behave, what support looks like, and whether your reconciliation closes. Start with internal recipients, cap each payout, and stop the pilot if any payout ends in a state your ledger cannot explain.",{"q":938,"a":939},"Who should sign off on a stablecoin API choice?","Engineering signs off on integration and failure handling, compliance on licensing and the split of KYC, KYB, and screening duties, finance on all-in cost and reconciliation, and operations on support and incident handling. Product owns the final call. If one of those owners has not seen pilot data, the decision is not ready.",{"q":941,"a":942},"What are red flags when evaluating a stablecoin API?","A sandbox that requires a sales call, pricing that only arrives by email as one blended rate, no written answer on who holds funds at each step, statuses that jump from pending to done with nothing in between, and no clear rule for what happens to stablecoins when a payout cannot complete. Each one turns into a cost after launch.",false,{"author":945},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan","---\ntitle: \"How to evaluate a stablecoin API in 30 days: a week-by-week plan\"\nseoTitle: \"How to evaluate a stablecoin API in 30 days\"\ndescription: \"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.\"\ndate: \"2026-10-06\"\nupdated: \"2026-10-06\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"How long does it take to evaluate a stablecoin API?\"\n    a: \"About 30 days is enough for most fintechs if the work is split by week: a written shortlist in week 1, sandbox testing in week 2, compliance and commercial review in week 3, and a small live pilot in week 4. Longer evaluations usually stall in contracting or compliance review, not in engineering, so start those conversations on day one.\"\n  - q: \"What should you test in a stablecoin API sandbox?\"\n    a: \"Test the unhappy paths, not only a successful payout. Force a failed payout and a refunded one, let a quote expire, send the same request twice with one idempotency key, replay a webhook, submit invalid bank details, and hit the rate limit. A provider passes when your system ends each case in the right state without a person fixing the ledger.\"\n  - q: \"How do you compare the real cost of two stablecoin APIs?\"\n    a: \"Compare all-in cost on the same corridor, the same amounts, and the same day. Take the dollar value you sent, subtract what the recipient received converted at a reference rate you record at quote time, then add monthly fees and the cost of any pre-funded balance. Divide by volume. Headline fees alone often rank providers in the wrong order.\"\n  - q: \"Should a stablecoin API pilot use real money?\"\n    a: \"Yes, in small amounts on one corridor. Sandboxes skip the bank leg, so only real payouts show settlement time, how recipients' banks behave, what support looks like, and whether your reconciliation closes. Start with internal recipients, cap each payout, and stop the pilot if any payout ends in a state your ledger cannot explain.\"\n  - q: \"Who should sign off on a stablecoin API choice?\"\n    a: \"Engineering signs off on integration and failure handling, compliance on licensing and the split of KYC, KYB, and screening duties, finance on all-in cost and reconciliation, and operations on support and incident handling. Product owns the final call. If one of those owners has not seen pilot data, the decision is not ready.\"\n  - q: \"What are red flags when evaluating a stablecoin API?\"\n    a: \"A sandbox that requires a sales call, pricing that only arrives by email as one blended rate, no written answer on who holds funds at each step, statuses that jump from pending to done with nothing in between, and no clear rule for what happens to stablecoins when a payout cannot complete. Each one turns into a cost after launch.\"\n---\n\nTo evaluate a stablecoin API in 30 days, give each week one job: shortlist providers in writing in week 1, break their sandboxes in week 2, run compliance and commercial review in week 3, and pilot real payouts on one corridor in week 4. Decide on day 30 from measured cost, speed, and failure handling, not from demos.\n\nFeature lists converge. Every provider claims quotes, webhooks, and global rails. The differences show up when a payout fails, when a quote expires, and when finance tries to close the month. This plan is built to surface those three things fast.\n\n**Key takeaways**\n\n- Time-box the evaluation. Thirty days with weekly exit criteria beats an open-ended \"let's try a few providers.\"\n- Spend sandbox week on failure cases. A successful payout proves almost nothing.\n- Start compliance and contracting on day one. They are the slowest part, not the code.\n- Measure all-in cost: what you sent minus what arrived, valued at a reference rate, plus fixed fees and pre-funding.\n- Pilot with real money on one corridor. Only the bank leg shows real settlement time.\n\nIf you're still sorting out which kind of provider you need, read [the types of stablecoin APIs](\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis) first. This plan assumes you've narrowed it to payment APIs that convert between stablecoins and local currency.\n\n## Who needs to be part of a stablecoin API evaluation?\n\nFive owners, each with one sign-off. Without all five, the evaluation ends in a decision that one team has to undo later.\n\n| Owner | What they evaluate | What they sign off on |\n| --- | --- | --- |\n| Engineering | API design, SDKs, webhooks, failure behavior | The sandbox test results |\n| Compliance | Licensing, KYC and KYB split, sanctions screening, record keeping | The responsibility split, in writing |\n| Finance | All-in cost, invoicing, reconciliation | The cost model and the pilot reconciliation |\n| Operations | Support response, incident process, recipient issues | The support runbook |\n| Product | Corridors, user experience, launch date | The final decision |\n\nName the owners on day one, and give each one a calendar slot in week 4 to review pilot data.\n\n## What should happen in week 1?\n\nWeek 1 turns a long list into two or three providers that answered your questions in writing.\n\n1. **Write the requirements on one page.** Corridors, rails, expected monthly volume and payout size, tokens and chains you hold, who must hold funds at each step, and who verifies your end users.\n2. **Map providers by category.** Issuers, custodial wallet platforms, orchestration layers, and payout APIs solve different problems. Drop any that don't do the job on your page.\n3. **Send written questions.** Use a fixed list so answers are comparable. The [six questions that matter](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api) are a short version; the [30 due diligence questions](\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence) are the long one.\n4. **Ask for a sandbox and a sample quote.** A sample quote for your top corridor at your typical amount, with fees itemized.\n5. **Start compliance and contract review now.** Request the provider's licensing summary and the standard contract on day one, not in week 3.\n\n**Exit criterion:** two or three providers with written answers, sandbox access, and a sample quote. A provider that can't give you a sandbox in week 1 is telling you something.\n\n## What should you test in the sandbox in week 2?\n\nTest the failure paths. Every sandbox handles the happy path; the question is whether your system ends each unhappy case in the right state without manual fixes.\n\n| Test | How to trigger it | Pass if |\n| --- | --- | --- |\n| Successful payout | Normal quote and execution | Status and webhooks arrive in order; ledger balances |\n| Failed payout | The provider's documented test trigger | Your ledger marks it failed and doesn't release funds twice |\n| Refunded payout | The provider's documented test trigger | Stablecoins return and your ledger shows the refund |\n| Expired quote | Execute after the quote window | You get a clear error and request a new quote |\n| Duplicate request | Same idempotency key, sent twice | One payout exists, not two |\n| Duplicate webhook | Replay an event from the dashboard | Your handler skips the repeat |\n| Out-of-order webhooks | Delay one event in your receiver | Final state is still correct |\n| Invalid bank details | Bad account number or check digit | Rejected at creation, not days later |\n| Compliance hold | Ask the provider how to simulate one | Your UI shows \"under review,\" not \"failed\" |\n| Rate limit | Burst requests | Your client backs off and retries |\n\nSandboxes fake some of these. [Sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) lists what typically doesn't carry over, so note which tests a provider can't run at all. On BlindPay, development instances are free, and setting a payout's request amount to 666.00 or 777.00 forces a `failed` or `refunded` result, so both failure paths take two API calls.\n\n**Exit criterion:** each provider's results in one table, with every failing test explained.\n\n## What does week 3 cover?\n\nWeek 3 is compliance and commercial review: who is licensed for what, who does which checks, and what the contract says when something goes wrong.\n\n**Compliance.** Check registrations yourself instead of trusting a slide. In the US, FinCEN's [MSB registrant search](https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fmsb-state-selector) shows federal registration, and [NMLS Consumer Access](https:\u002F\u002Fwww.nmlsconsumeraccess.org\u002F) shows many state licenses. Then write down who runs KYC, KYB, sanctions screening, transaction monitoring, and record keeping for your flow. [Which license a stablecoin payment flow needs](\u002Fresources\u002Fmore\u002Fstablecoin-payment-licenses-msb-mtl-vasp-emi) explains the categories.\n\nIf you work with a bank partner, expect it to ask how you chose and monitor the provider. US bank regulators' [2023 interagency guidance on third-party relationships](https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2023\u002Fbulletin-2023-17.html) treats vendor risk as a life cycle and says not every third party carries the same risk. Your week 3 notes become that evidence.\n\n**Commercial.** Get pricing in writing for your corridors and amounts, including anything billed monthly. Read the contract for minimums, termination terms, data export on exit, support response times, and what happens to funds in a payout that can't complete.\n\n**Exit criterion:** compliance has a signed responsibility split, and finance has written pricing for the pilot corridor.\n\n## How do you run the week 4 pilot?\n\nRun real payouts on one corridor, in small amounts, and record everything. This is where settlement time, support quality, and reconciliation become numbers.\n\n1. **Pick one corridor** that matters to your launch.\n2. **Pay internal recipients first.** Team members or your own accounts in the destination country.\n3. **Cap each payout** at an amount you'd accept losing time on, not money.\n4. **Add a handful of real recipients** once internal payouts reconcile.\n5. **File one support ticket on purpose.** Ask a real question and time the answer.\n6. **Close the books on the pilot.** Finance reconciles every payout against the provider's records.\n\nLog every pilot payout with the same fields, for every provider:\n\n| Field | Why you need it |\n| --- | --- |\n| Quote ID and payout ID | Ties your ledger to the provider's |\n| Amount sent and amount received | The basis of all-in cost |\n| Reference rate at quote time | Lets you price the spread |\n| Quote, execution, and completion timestamps | Real settlement time |\n| Rail reference (tracking key, UETR, trace ID) | Proof of delivery for recipients |\n| Status history | Shows whether statuses are honest |\n| Support time, if any | Real support quality |\n\n**Exit criterion:** every pilot payout is either completed and reconciled, or explained.\n\n## Where do stablecoin API costs hide?\n\nMost of the cost isn't in the fee line. It sits in the rate, in the contract, or in capital you never see on an invoice.\n\n| Cost | Where it hides | How to catch it in the evaluation |\n| --- | --- | --- |\n| FX spread | Inside the exchange rate, not as a fee | Compare each quote to a reference rate recorded at the same minute |\n| Percentage fee | The quote's fee fields, or a blended rate | Ask for itemized quotes |\n| Flat per-payout fee | Small print; hurts small payouts most | Model your real payout size, not an average |\n| Network fee | Which side pays gas, and on which chain | Check who pays on the chain you'll use |\n| Monthly or platform fee | The contract, not the pricing page | Read the order form |\n| Minimum volume | The contract | Model a slow month |\n| Pre-funding | Capital parked in a destination account | Price it at your cost of capital |\n| Requotes | Rate movement between expired quotes | Count requotes in the pilot |\n| Failure handling | Return fees and staff time | Count failed and returned payouts in the pilot |\n| Invoice-billed fees | Charged at month end, not deducted from the payout | Read the first invoice, not just the quotes |\n\n[Stablecoin API pricing explained](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) goes deeper on mint fees, burn fees, and itemized quotes.\n\n## How do you compare all-in cost between providers?\n\nCompare all-in cost: the dollar value you sent minus what arrived, valued at a reference rate, plus fixed monthly costs and the carrying cost of any pre-funded balance, divided by volume.\n\nAll-in cost = (value sent − value received at the reference rate) + monthly fees + pre-funding cost\n\nHere's a worked example. Every number is hypothetical and chosen to show the method. None describes a real provider.\n\nAssumptions: payouts of $1,000 each to one corridor, a network fee of $0.05 per payout, and a 5% annual cost of capital. Provider B requires a pre-funded balance equal to half a month's volume.\n\n| Cost line | Provider A, 100 payouts | Provider B, 100 payouts | Provider A, 1,000 payouts | Provider B, 1,000 payouts |\n| --- | --- | --- | --- | --- |\n| Percentage fee (A 0.50%, B 0.20%) | $500 | $200 | $5,000 | $2,000 |\n| Flat fee (A $0, B $2) | $0 | $200 | $0 | $2,000 |\n| Spread vs reference (A 0.30%, B 0.60%) | $300 | $600 | $3,000 | $6,000 |\n| Monthly platform fee (A $0, B $500) | $0 | $500 | $0 | $500 |\n| Pre-funding cost at 5% a year, one month | $0 | $208 | $0 | $2,083 |\n| Network fees | $5 | $5 | $50 | $50 |\n| **Total** | **$805** | **$1,713** | **$8,050** | **$12,633** |\n| **All-in cost as % of volume** | **0.81%** | **1.71%** | **0.81%** | **1.26%** |\n\nProvider B has the lower headline fee and still costs more at both volumes. The spread and the parked capital do the damage, and neither appears as a fee line. Fixed costs shrink as volume grows, so run the model at your expected volume and at a slow month.\n\n## How do you make the decision on day 30?\n\nUse gates first, then scores. A provider that fails a gate is out, no matter how cheap it is.\n\n**Gates (pass or fail):**\n\n1. Your launch corridors are live in production, in the direction you need.\n2. Compliance signed the responsibility split.\n3. Every sandbox failure test ended in the right state, or the gap is understood.\n4. Every pilot payout reconciled.\n\n**Scores (weight them to your business):** all-in cost at expected volume, median and slowest settlement time in the pilot, support response time, and developer experience as your engineers rated it.\n\nWrite the decision down with the pilot log attached. In six months, when someone asks why you picked this provider, that page is the answer.\n\n## How does BlindPay fit a 30-day evaluation?\n\nBlindPay is built to be tested before anyone signs. Development instances are free, there's no setup fee or monthly minimum, and every quote returns the sender amount, receiver amount, and fee fields before you execute, so most of the pilot log above comes straight from the API. A [fee schedule endpoint](\u002Fdocs\u002Flearn\u002Fbilling) returns the flat and percentage fee per rail and network on your instance. SDKs cover Node.js, Python, Go, PHP, and Swift, and payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) with no pre-funding.\n\nStart week 2 today: create a development instance and run the failure tests from the [payout quickstart](\u002Fdocs\u002Fquickstart-payout).\n",{"title":5,"description":922},"How to evaluate a stablecoin API in 30 days","resources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan","VF9tqN-e8D8_gLEg0QuFOEe65zAs7KXNj8KDDznC-7Q",[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,1055,1059,1063,1067,1071,1075,1079,1083,1087,1091,1095,1099,1103,1107,1111,1115,1119,1123,1127,1131,1135,1139,1143,1147,1151,1154,1158,1162,1166,1170,1174,1178,1182,1186,1190,1194,1198,1202,1206,1210,1214,1218,1222,1226,1230,1234,1238,1242,1246,1250,1254,1258,1262,1266,1269,1273,1277,1281],{"path":955,"title":956,"description":957},"\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":959,"title":960,"description":961},"\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":963,"title":964,"description":965},"\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":967,"title":968,"description":969},"\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":971,"title":972,"description":973},"\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":975,"title":976,"description":977},"\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":979,"title":980,"description":981},"\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":983,"title":984,"description":985},"\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":987,"title":988,"description":989},"\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":991,"title":992,"description":993},"\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":995,"title":996,"description":997},"\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":999,"title":1000,"description":1001},"\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":1003,"title":1004,"description":1005},"\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":1007,"title":1008,"description":1009},"\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":1011,"title":1012,"description":1013},"\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":1015,"title":1016,"description":1017},"\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":1019,"title":1020,"description":1021},"\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":1023,"title":1024,"description":1025},"\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":1027,"title":1028,"description":1029},"\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":1031,"title":1032,"description":1033},"\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":1035,"title":1036,"description":1037},"\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":1039,"title":1040,"description":1041},"\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":1043,"title":1044,"description":1045},"\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":1047,"title":1048,"description":1049},"\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":1051,"title":1052,"description":1053},"\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":947,"title":5,"description":922},{"path":1056,"title":1057,"description":1058},"\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":1060,"title":1061,"description":1062},"\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":1064,"title":1065,"description":1066},"\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":1068,"title":1069,"description":1070},"\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":1072,"title":1073,"description":1074},"\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":1076,"title":1077,"description":1078},"\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":1080,"title":1081,"description":1082},"\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":1084,"title":1085,"description":1086},"\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":1088,"title":1089,"description":1090},"\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":1092,"title":1093,"description":1094},"\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":1096,"title":1097,"description":1098},"\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":1100,"title":1101,"description":1102},"\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":1104,"title":1105,"description":1106},"\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":1108,"title":1109,"description":1110},"\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":1112,"title":1113,"description":1114},"\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":1116,"title":1117,"description":1118},"\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":1120,"title":1121,"description":1122},"\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":1124,"title":1125,"description":1126},"\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":1128,"title":1129,"description":1130},"\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":1132,"title":1133,"description":1134},"\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":1136,"title":1137,"description":1138},"\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":1140,"title":1141,"description":1142},"\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":1144,"title":1145,"description":1146},"\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":1148,"title":1149,"description":1150},"\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":334,"title":1152,"description":1153},"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":1155,"title":1156,"description":1157},"\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":1159,"title":1160,"description":1161},"\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":1163,"title":1164,"description":1165},"\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":1167,"title":1168,"description":1169},"\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":1171,"title":1172,"description":1173},"\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":1175,"title":1176,"description":1177},"\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":1179,"title":1180,"description":1181},"\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":1183,"title":1184,"description":1185},"\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":1187,"title":1188,"description":1189},"\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":1191,"title":1192,"description":1193},"\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":1195,"title":1196,"description":1197},"\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":1199,"title":1200,"description":1201},"\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":1203,"title":1204,"description":1205},"\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":1207,"title":1208,"description":1209},"\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":1211,"title":1212,"description":1213},"\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":1215,"title":1216,"description":1217},"\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":1219,"title":1220,"description":1221},"\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":1223,"title":1224,"description":1225},"\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":1227,"title":1228,"description":1229},"\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":1231,"title":1232,"description":1233},"\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":1235,"title":1236,"description":1237},"\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":1239,"title":1240,"description":1241},"\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":1243,"title":1244,"description":1245},"\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":1247,"title":1248,"description":1249},"\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":1251,"title":1252,"description":1253},"\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":1255,"title":1256,"description":1257},"\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":1259,"title":1260,"description":1261},"\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":1263,"title":1264,"description":1265},"\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":175,"title":1267,"description":1268},"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":1270,"title":1271,"description":1272},"\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":1274,"title":1275,"description":1276},"\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":1278,"title":1279,"description":1280},"\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":1282,"title":1283,"description":1284},"\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.",1791398891744]