[{"data":1,"prerenderedAt":1463},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate":3,"resources-category-payout-quality-metrics-slippage-expiry-rate":924},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":894,"categoryType":6,"compare":6,"contributors":6,"date":895,"description":896,"extension":897,"faq":898,"howto":6,"isBlog":914,"isChangelog":914,"meta":915,"navigation":917,"path":918,"pillar":914,"products":6,"rawbody":919,"role":6,"seo":920,"seoTitle":921,"stem":922,"thumbnail":6,"updated":895,"__hash__":923},"content\u002Fresources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate.md","Payout quality metrics: realized slippage, quote expiry rate, and re-quote delta",null,{"type":8,"value":9,"toc":884},"minimark",[10,14,20,48,53,56,67,80,84,87,183,186,236,245,249,255,275,283,287,293,484,487,708,714,718,729,758,772,785,789,792,818,821,838,842,859,862,866,874,880],[11,12,13],"p",{},"Payout quality comes down to five numbers per corridor: realized slippage, quote expiry rate, re-quote delta, delivery success rate, and time to settle. On a binding quote, realized slippage should be zero. The other four tell you whether your screen flow, your corridors, and your provider are doing what they promised.",[11,15,16],{},[17,18,19],"strong",{},"Key takeaways",[21,22,23,27,30,38,45],"ul",{},[24,25,26],"li",{},"Realized slippage on a binding quote executed inside its window should be zero, every time.",[24,28,29],{},"Expiry rate measures your UX; re-quote delta measures the market; delivery success and time to settle measure the rails.",[24,31,32,33,37],{},"One event log row per quote, keyed by ",[34,35,36],"code",{},"quote_id",", is enough to compute all five.",[24,39,40,41,44],{},"Classify payout outcomes by the ",[34,42,43],{},"status"," field on each webhook, not by the event name.",[24,46,47],{},"Report time to settle as a median and a 90th percentile per rail. Averages hide the slow tail.",[49,50,52],"h2",{"id":51},"why-measure-payout-quality-at-all","Why measure payout quality at all?",[11,54,55],{},"Because a quote-based flow can fail quietly. A user sees one number, confirms, and either gets that number or does not. If you only track volume and revenue, you will not notice a corridor where one confirmation in five expires, or a rail whose slow tail doubled last month.",[11,57,58,59,66],{},"The approach borrows from site reliability engineering. Google's SRE book frames service quality as ",[60,61,65],"a",{"href":62,"rel":63},"https:\u002F\u002Fsre.google\u002Fsre-book\u002Fservice-level-objectives\u002F",[64],"nofollow","indicators, objectives, and agreements",": pick a few metrics users care about, set a target for each, and decide in advance what you do when you miss it. The five metrics below are those indicators for payouts.",[11,68,69,70,74,75,79],{},"They extend the three checks in ",[60,71,73],{"href":72},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","how live quotes turn the quoted rate into the rate you get",". Terms follow the ",[60,76,78],{"href":77},"\u002Fresources\u002Fmore\u002Fonramp-offramp-liquidity-glossary","on\u002Foff-ramp liquidity glossary",".",[49,81,83],{"id":82},"which-five-metrics-matter-and-how-do-you-calculate-them","Which five metrics matter, and how do you calculate them?",[11,85,86],{},"Each metric has one formula, a starting target, and a meaning when it goes wrong. Targets below are starting points; set your own after a few weeks of data.",[88,89,90,109],"table",{},[91,92,93],"thead",{},[94,95,96,100,103,106],"tr",{},[97,98,99],"th",{},"Metric",[97,101,102],{},"Formula",[97,104,105],{},"Starting target",[97,107,108],{},"A bad number tells you",[110,111,112,127,141,155,169],"tbody",{},[94,113,114,118,121,124],{},[115,116,117],"td",{},"Realized slippage",[115,119,120],{},"(quoted receiver_amount - delivered amount) \u002F quoted receiver_amount x 10,000",[115,122,123],{},"0 bps on a binding quote",[115,125,126],{},"The quote was not binding, or a fee landed outside the quote",[94,128,129,132,135,138],{},[115,130,131],{},"Quote expiry rate",[115,133,134],{},"quotes expired before confirm \u002F quotes shown",[115,136,137],{},"Under 10% on a single confirm screen",[115,139,140],{},"Quotes are fetched too early, or the flow is too long",[94,142,143,146,149,152],{},[115,144,145],{},"Re-quote delta",[115,147,148],{},"(new receiver_amount - old receiver_amount) \u002F old receiver_amount x 10,000",[115,150,151],{},"Within the corridor's normal range",[115,153,154],{},"The corridor is volatile right now",[94,156,157,160,163,166],{},[115,158,159],{},"Delivery success rate",[115,161,162],{},"completed \u002F (completed + failed + refunded)",[115,164,165],{},"Above 99% on established corridors",[115,167,168],{},"Bad recipient data, compliance holds, or a rail issue",[94,170,171,174,177,180],{},[115,172,173],{},"Time to settle",[115,175,176],{},"completed_at - executed_at, p50 and p90 per rail",[115,178,179],{},"Within the rail's expected window",[115,181,182],{},"A rail, a review step, or a cut-off is slowing payouts",[11,184,185],{},"A few rules for reading them:",[21,187,188,202,208,225],{},[24,189,190,193,194,197,198,201],{},[17,191,192],{},"Realized slippage is binary in practice."," On a binding quote executed before ",[34,195,196],{},"expires_at",", the recipient gets the quoted ",[34,199,200],{},"receiver_amount",". A non-zero value is not \"a bit of noise\", it is a finding.",[24,203,204,207],{},[17,205,206],{},"Re-quote delta needs the same inputs."," Compare quotes with the same amount, currency side, fee setting, and destination. Otherwise you are measuring your own changes.",[24,209,210,213,214,217,218,221,222,79],{},[17,211,212],{},"Delivery success excludes payouts still in flight."," Count only payouts that reached a terminal status: ",[34,215,216],{},"completed",", ",[34,219,220],{},"failed",", or ",[34,223,224],{},"refunded",[24,226,227,230,231,235],{},[17,228,229],{},"Time to settle is per rail."," Pix and SPEI settle in minutes, RTP is instant, and ACH, TED, and SEPA take about one to two business days, per BlindPay's ",[60,232,234],{"href":233},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times reference",". Blending them makes every number meaningless.",[11,237,238,239,244],{},"The policy benchmark for speed is the G20 roadmap. The ",[60,240,243],{"href":241,"rel":242},"https:\u002F\u002Fwww.fsb.org\u002F2021\u002F10\u002Ftargets-for-addressing-the-four-challenges-of-cross-border-payments-final-report\u002F",[64],"Financial Stability Board's targets"," aim for 75% of retail cross-border payments to make funds available within one hour of initiation, and the rest within one business day, by end-2027. Your p50 and p90 per rail show where you stand against that.",[49,246,248],{"id":247},"what-does-a-week-of-numbers-look-like","What does a week of numbers look like?",[11,250,251,254],{},[17,252,253],{},"Illustrative example."," A marketplace pays sellers in Brazil and Mexico. One week of data:",[21,256,257,260,263,266,269,272],{},[24,258,259],{},"Quotes shown: 4,000. Confirmed and executed: 3,250. Expired before confirm: 560. Abandoned without expiring: 190.",[24,261,262],{},"Expiry rate: 560 \u002F 4,000 = 14%.",[24,264,265],{},"Re-quotes after expiry: 480. Average re-quote delta: 9 bps on BRL, 6 bps on MXN.",[24,267,268],{},"Payouts finished: 3,240 completed, 6 failed, 4 refunded. Delivery success: 3,240 \u002F 3,250 = 99.69%.",[24,270,271],{},"Realized slippage: 0 bps on all 3,240 completed payouts.",[24,273,274],{},"Time to settle over Pix: p50 3 minutes, p90 11 minutes.",[11,276,277,278,282],{},"What to do with it. The 14% expiry rate is above the starting target, so look at the screen: the quote is probably fetched when the payout form opens, not when the user reaches the confirm step. Moving the quote request later is the cheapest fix. The delivery success rate is healthy; the 10 failures and refunds go to a weekly review of recipient bank details. ",[60,279,281],{"href":280},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes","Common stablecoin payout mistakes"," lists the usual causes.",[49,284,286],{"id":285},"what-should-the-event-log-store","What should the event log store?",[11,288,289,290,292],{},"One row per quote, keyed by ",[34,291,36],{},", updated as the payout moves. This is enough to compute all five metrics.",[88,294,295,308],{},[91,296,297],{},[94,298,299,302,305],{},[97,300,301],{},"Field",[97,303,304],{},"Source",[97,306,307],{},"Used for",[110,309,310,326,341,354,375,391,404,416,429,448,460,472],{},[94,311,312,316,323],{},[115,313,314],{},[34,315,36],{},[115,317,318,319,322],{},"Quote response (",[34,320,321],{},"qu_...",")",[115,324,325],{},"Primary key",[94,327,328,333,339],{},[115,329,330],{},[34,331,332],{},"requote_of",[115,334,335,336,338],{},"Your app: the expired ",[34,337,36],{}," this one replaced",[115,340,145],{},[94,342,343,348,351],{},[115,344,345],{},[34,346,347],{},"corridor",[115,349,350],{},"Your app: currency and rail",[115,352,353],{},"Grouping",[94,355,356,364,372],{},[115,357,358,217,361],{},[34,359,360],{},"quoted_sender_amount",[34,362,363],{},"quoted_receiver_amount",[115,365,366,367,217,370],{},"Quote response ",[34,368,369],{},"sender_amount",[34,371,200],{},[115,373,374],{},"Slippage, re-quote delta",[94,376,377,385,388],{},[115,378,379,217,382],{},[34,380,381],{},"commercial_quotation",[34,383,384],{},"blindpay_quotation",[115,386,387],{},"Quote response",[115,389,390],{},"Spread and cost tracking",[94,392,393,398,401],{},[115,394,395],{},[34,396,397],{},"quote_created_at",[115,399,400],{},"Your clock when the response arrives",[115,402,403],{},"Expiry analysis",[94,405,406,410,413],{},[115,407,408],{},[34,409,196],{},[115,411,412],{},"Quote response, epoch milliseconds",[115,414,415],{},"Expiry rate",[94,417,418,423,426],{},[115,419,420],{},[34,421,422],{},"confirmed_at",[115,424,425],{},"Your clock when the user confirms",[115,427,428],{},"Expiry rate, time on screen",[94,430,431,439,446],{},[115,432,433,217,436],{},[34,434,435],{},"payout_id",[34,437,438],{},"executed_at",[115,440,441,442,445],{},"Payout response (",[34,443,444],{},"po_...",") and your clock",[115,447,173],{},[94,449,450,454,457],{},[115,451,452],{},[34,453,43],{},[115,455,456],{},"Latest payout webhook",[115,458,459],{},"Delivery success",[94,461,462,467,470],{},[115,463,464],{},[34,465,466],{},"completed_at",[115,468,469],{},"Completion time from the payout's tracking objects",[115,471,173],{},[94,473,474,479,482],{},[115,475,476],{},[34,477,478],{},"delivered_amount",[115,480,481],{},"Recipient confirmation or bank statement, where you have it",[115,483,117],{},[11,485,486],{},"A sample row:",[488,489,494],"pre",{"className":490,"code":491,"language":492,"meta":493,"style":493},"language-json shiki shiki-themes github-light","{\n  \"quote_id\": \"qu_000000000000\",\n  \"requote_of\": null,\n  \"corridor\": \"BRL_pix\",\n  \"quoted_sender_amount\": 100000,\n  \"quoted_receiver_amount\": 537300,\n  \"commercial_quotation\": 5.4,\n  \"blindpay_quotation\": 5.373,\n  \"quote_created_at\": \"2026-10-12T14:00:02Z\",\n  \"expires_at\": 1791813902000,\n  \"confirmed_at\": \"2026-10-12T14:01:15Z\",\n  \"payout_id\": \"po_000000000000\",\n  \"executed_at\": \"2026-10-12T14:01:16Z\",\n  \"status\": \"completed\",\n  \"completed_at\": \"2026-10-12T14:04:40Z\",\n  \"delivered_amount\": 537300\n}\n","json","",[34,495,496,505,522,535,548,561,574,587,600,613,626,639,652,665,678,691,702],{"__ignoreMap":493},[497,498,501],"span",{"class":499,"line":500},"line",1,[497,502,504],{"class":503},"sgsFI","{\n",[497,506,508,512,515,519],{"class":499,"line":507},2,[497,509,511],{"class":510},"sYu0t","  \"quote_id\"",[497,513,514],{"class":503},": ",[497,516,518],{"class":517},"sYBdl","\"qu_000000000000\"",[497,520,521],{"class":503},",\n",[497,523,525,528,530,533],{"class":499,"line":524},3,[497,526,527],{"class":510},"  \"requote_of\"",[497,529,514],{"class":503},[497,531,532],{"class":510},"null",[497,534,521],{"class":503},[497,536,538,541,543,546],{"class":499,"line":537},4,[497,539,540],{"class":510},"  \"corridor\"",[497,542,514],{"class":503},[497,544,545],{"class":517},"\"BRL_pix\"",[497,547,521],{"class":503},[497,549,551,554,556,559],{"class":499,"line":550},5,[497,552,553],{"class":510},"  \"quoted_sender_amount\"",[497,555,514],{"class":503},[497,557,558],{"class":510},"100000",[497,560,521],{"class":503},[497,562,564,567,569,572],{"class":499,"line":563},6,[497,565,566],{"class":510},"  \"quoted_receiver_amount\"",[497,568,514],{"class":503},[497,570,571],{"class":510},"537300",[497,573,521],{"class":503},[497,575,577,580,582,585],{"class":499,"line":576},7,[497,578,579],{"class":510},"  \"commercial_quotation\"",[497,581,514],{"class":503},[497,583,584],{"class":510},"5.4",[497,586,521],{"class":503},[497,588,590,593,595,598],{"class":499,"line":589},8,[497,591,592],{"class":510},"  \"blindpay_quotation\"",[497,594,514],{"class":503},[497,596,597],{"class":510},"5.373",[497,599,521],{"class":503},[497,601,603,606,608,611],{"class":499,"line":602},9,[497,604,605],{"class":510},"  \"quote_created_at\"",[497,607,514],{"class":503},[497,609,610],{"class":517},"\"2026-10-12T14:00:02Z\"",[497,612,521],{"class":503},[497,614,616,619,621,624],{"class":499,"line":615},10,[497,617,618],{"class":510},"  \"expires_at\"",[497,620,514],{"class":503},[497,622,623],{"class":510},"1791813902000",[497,625,521],{"class":503},[497,627,629,632,634,637],{"class":499,"line":628},11,[497,630,631],{"class":510},"  \"confirmed_at\"",[497,633,514],{"class":503},[497,635,636],{"class":517},"\"2026-10-12T14:01:15Z\"",[497,638,521],{"class":503},[497,640,642,645,647,650],{"class":499,"line":641},12,[497,643,644],{"class":510},"  \"payout_id\"",[497,646,514],{"class":503},[497,648,649],{"class":517},"\"po_000000000000\"",[497,651,521],{"class":503},[497,653,655,658,660,663],{"class":499,"line":654},13,[497,656,657],{"class":510},"  \"executed_at\"",[497,659,514],{"class":503},[497,661,662],{"class":517},"\"2026-10-12T14:01:16Z\"",[497,664,521],{"class":503},[497,666,668,671,673,676],{"class":499,"line":667},14,[497,669,670],{"class":510},"  \"status\"",[497,672,514],{"class":503},[497,674,675],{"class":517},"\"completed\"",[497,677,521],{"class":503},[497,679,681,684,686,689],{"class":499,"line":680},15,[497,682,683],{"class":510},"  \"completed_at\"",[497,685,514],{"class":503},[497,687,688],{"class":517},"\"2026-10-12T14:04:40Z\"",[497,690,521],{"class":503},[497,692,694,697,699],{"class":499,"line":693},16,[497,695,696],{"class":510},"  \"delivered_amount\"",[497,698,514],{"class":503},[497,700,701],{"class":510},"537300\n",[497,703,705],{"class":499,"line":704},17,[497,706,707],{"class":503},"}\n",[11,709,710,711,713],{},"Two traps. ",[34,712,196],{}," is epoch milliseconds, not seconds; divide by 1,000 only if your date library expects seconds. And amounts are integers in minor units, so 537300 means R$5,373.00.",[49,715,717],{"id":716},"how-do-webhooks-feed-the-log","How do webhooks feed the log?",[11,719,720,721,723,724,728],{},"Webhooks update the ",[34,722,43],{}," and timestamps without polling. BlindPay sends three payout events, documented in the ",[60,725,727],{"href":726},"\u002Fdocs\u002Flearn\u002Fwebhooks-events","webhook events reference",":",[730,731,732,743,752],"ol",{},[24,733,734,737,738,740,741,79],{},[34,735,736],{},"payout.new",": the payout is created and the source funds are captured. Set ",[34,739,435],{}," and ",[34,742,43],{},[24,744,745,748,749,751],{},[34,746,747],{},"payout.update",": the payout moves through an intermediate step, such as document checks, manual review, or the bank send. A payout that reaches ",[34,750,220],{}," arrives here too.",[24,753,754,757],{},[34,755,756],{},"payout.complete",": the payout is confirmed at the destination or refunded.",[11,759,760,761,763,764,217,766,768,769,771],{},"So the rule is simple: on every payout event, read the ",[34,762,43],{}," field and write it to the row. Classify ",[34,765,216],{},[34,767,220],{},", and ",[34,770,224],{}," as terminal from the status, never from the event name alone. That keeps delivery success correct whichever event carried the change.",[11,773,774,775,779,780,784],{},"Verify every webhook signature before trusting it, and process events idempotently, since the same event can arrive twice. ",[60,776,778],{"href":777},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","Stablecoin webhooks and reconciliation"," covers both, and ",[60,781,783],{"href":782},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained","stablecoin payout statuses explained"," covers what each status means for the recipient.",[49,786,788],{"id":787},"what-should-the-dashboard-show","What should the dashboard show?",[11,790,791],{},"Three rows, read top to bottom in under a minute.",[21,793,794,800,806],{},[24,795,796,799],{},[17,797,798],{},"Row 1, health tiles."," Five numbers for the last 7 days, each against its target: realized slippage (should read 0 bps), expiry rate, average re-quote delta, delivery success rate, and Pix or SPEI p90 time to settle.",[24,801,802,805],{},[17,803,804],{},"Row 2, per-corridor trends."," One line chart per metric, split by corridor, over 90 days. Expiry rate and re-quote delta on the same time axis, so you can see when volatility drove expiries.",[24,807,808,811,812,814,815,817],{},[17,809,810],{},"Row 3, exceptions."," A table of payouts that broke a rule: any non-zero realized slippage, any payout past its rail's p90, and every ",[34,813,220],{}," or ",[34,816,224],{}," payout with its reason.",[11,819,820],{},"Alert on two things only: any non-zero realized slippage, and a delivery success rate that drops below target for a corridor. Everything else is a weekly review.",[11,822,823,824,828,829,833,834,79],{},"When an expired quote triggers a re-quote in your code, log the link between the two ids. ",[60,825,827],{"href":826},"\u002Fresources\u002Fmore\u002Fhandle-expired-quotes-typescript-python","How to handle expired quotes in TypeScript and Python"," shows the retry pattern, and ",[60,830,832],{"href":831},"\u002Fresources\u002Fmore\u002Fcost-per-delivered-dollar","cost per delivered dollar"," turns the same log into an all-in cost per corridor. For who absorbs the market move while a quote is open, see ",[60,835,837],{"href":836},"\u002Fresources\u002Fmore\u002Fwho-carries-fx-risk-stablecoin-payout","who carries FX risk in a stablecoin payout",[49,839,841],{"id":840},"how-does-blindpay-help-you-measure-this","How does BlindPay help you measure this?",[11,843,844,845,217,848,217,850,217,852,217,854,217,856,858],{},"Every BlindPay quote returns the fields the log needs: ",[34,846,847],{},"id",[34,849,196],{},[34,851,381],{},[34,853,384],{},[34,855,369],{},[34,857,200],{},", and the fee lines. Payout quotes lock the rate and fees for 5 minutes by default, and an expired quote is rejected instead of executed at a new rate, so realized slippage on BlindPay payouts executed in time is designed to be zero.",[11,860,861],{},"Payout webhooks are signed and carry the payout's status and tracking objects. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review.",[49,863,865],{"id":864},"what-to-do-next","What to do next",[11,867,868,869,873],{},"Add the event log table to your database, write one row per quote, and backfill a week of payouts. Then compute the five metrics per corridor and set your first targets. The ",[60,870,872],{"href":871},"\u002Fdocs\u002Fpayout-quotes","payout quotes docs"," list every field the log reads.",[11,875,876],{},[877,878,879],"em",{},"This article is general information, not legal, tax, or financial advice.",[881,882,883],"style",{},"html pre.shiki code .sgsFI, html code.shiki .sgsFI{--shiki-default:#24292E}html pre.shiki code .sYu0t, html code.shiki .sYu0t{--shiki-default:#005CC5}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":493,"searchDepth":507,"depth":507,"links":885},[886,887,888,889,890,891,892,893],{"id":51,"depth":507,"text":52},{"id":82,"depth":507,"text":83},{"id":247,"depth":507,"text":248},{"id":285,"depth":507,"text":286},{"id":716,"depth":507,"text":717},{"id":787,"depth":507,"text":788},{"id":840,"depth":507,"text":841},{"id":864,"depth":507,"text":865},"payments","2026-10-12","Five metrics for a quote-based payout flow: realized slippage, expiry rate, re-quote delta, delivery success, and time to settle, with formulas and a log.","md",[899,902,905,908,911],{"q":900,"a":901},"What metrics should I track for payout quality?","Track five per corridor: realized slippage (delivered vs quoted amount), quote expiry rate (quotes that lapse before the user confirms), re-quote delta (how much the amount moves between an expired quote and its replacement), delivery success rate (completed payouts over all finished payouts), and time to settle (execution to completion, at the median and 90th percentile).",{"q":903,"a":904},"What is realized slippage on a payout?","Realized slippage is the gap between the amount a quote promised the recipient and the amount that actually arrived, in basis points: (quoted receiver_amount minus delivered amount) divided by quoted receiver_amount, times 10,000. On a binding quote executed before it expires, it should be zero on every payout. Any non-zero value is worth a support ticket.",{"q":906,"a":907},"What is a good quote expiry rate?","There is no universal number, because it depends on your screen flow. As a starting point, aim for fewer than 1 in 10 quotes expiring on a single confirmation screen, then set your own baseline after a few weeks. A rising expiry rate usually means quotes are fetched too early, or the confirmation flow has too many steps.",{"q":909,"a":910},"What does a large re-quote delta mean?","It means the market moved during the quote window. Re-quote delta compares an expired quote with its replacement for the same inputs. Small deltas on liquid corridors are normal. Large or growing deltas on one corridor point to volatility, and they are a signal to fetch quotes later in the flow and to warn users when the new amount changes.",{"q":912,"a":913},"Which webhook events do I need to measure payout quality?","At BlindPay, payout.new fires when a payout is created and the source funds are captured, payout.update fires on intermediate steps, including a move to failed, and payout.complete fires when a payout is confirmed at the destination or refunded. Read the status field on every event to classify the outcome instead of relying on the event name alone.",false,{"author":916},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate","---\ntitle: \"Payout quality metrics: realized slippage, quote expiry rate, and re-quote delta\"\nseoTitle: \"Payout quality metrics: slippage, expiry, re-quote delta\"\ndescription: \"Five metrics for a quote-based payout flow: realized slippage, expiry rate, re-quote delta, delivery success, and time to settle, with formulas and a log.\"\ndate: \"2026-10-12\"\nupdated: \"2026-10-12\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What metrics should I track for payout quality?\"\n    a: \"Track five per corridor: realized slippage (delivered vs quoted amount), quote expiry rate (quotes that lapse before the user confirms), re-quote delta (how much the amount moves between an expired quote and its replacement), delivery success rate (completed payouts over all finished payouts), and time to settle (execution to completion, at the median and 90th percentile).\"\n  - q: \"What is realized slippage on a payout?\"\n    a: \"Realized slippage is the gap between the amount a quote promised the recipient and the amount that actually arrived, in basis points: (quoted receiver_amount minus delivered amount) divided by quoted receiver_amount, times 10,000. On a binding quote executed before it expires, it should be zero on every payout. Any non-zero value is worth a support ticket.\"\n  - q: \"What is a good quote expiry rate?\"\n    a: \"There is no universal number, because it depends on your screen flow. As a starting point, aim for fewer than 1 in 10 quotes expiring on a single confirmation screen, then set your own baseline after a few weeks. A rising expiry rate usually means quotes are fetched too early, or the confirmation flow has too many steps.\"\n  - q: \"What does a large re-quote delta mean?\"\n    a: \"It means the market moved during the quote window. Re-quote delta compares an expired quote with its replacement for the same inputs. Small deltas on liquid corridors are normal. Large or growing deltas on one corridor point to volatility, and they are a signal to fetch quotes later in the flow and to warn users when the new amount changes.\"\n  - q: \"Which webhook events do I need to measure payout quality?\"\n    a: \"At BlindPay, payout.new fires when a payout is created and the source funds are captured, payout.update fires on intermediate steps, including a move to failed, and payout.complete fires when a payout is confirmed at the destination or refunded. Read the status field on every event to classify the outcome instead of relying on the event name alone.\"\n---\n\nPayout quality comes down to five numbers per corridor: realized slippage, quote expiry rate, re-quote delta, delivery success rate, and time to settle. On a binding quote, realized slippage should be zero. The other four tell you whether your screen flow, your corridors, and your provider are doing what they promised.\n\n**Key takeaways**\n\n- Realized slippage on a binding quote executed inside its window should be zero, every time.\n- Expiry rate measures your UX; re-quote delta measures the market; delivery success and time to settle measure the rails.\n- One event log row per quote, keyed by `quote_id`, is enough to compute all five.\n- Classify payout outcomes by the `status` field on each webhook, not by the event name.\n- Report time to settle as a median and a 90th percentile per rail. Averages hide the slow tail.\n\n## Why measure payout quality at all?\n\nBecause a quote-based flow can fail quietly. A user sees one number, confirms, and either gets that number or does not. If you only track volume and revenue, you will not notice a corridor where one confirmation in five expires, or a rail whose slow tail doubled last month.\n\nThe approach borrows from site reliability engineering. Google's SRE book frames service quality as [indicators, objectives, and agreements](https:\u002F\u002Fsre.google\u002Fsre-book\u002Fservice-level-objectives\u002F): pick a few metrics users care about, set a target for each, and decide in advance what you do when you miss it. The five metrics below are those indicators for payouts.\n\nThey extend the three checks in [how live quotes turn the quoted rate into the rate you get](\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes). Terms follow the [on\u002Foff-ramp liquidity glossary](\u002Fresources\u002Fmore\u002Fonramp-offramp-liquidity-glossary).\n\n## Which five metrics matter, and how do you calculate them?\n\nEach metric has one formula, a starting target, and a meaning when it goes wrong. Targets below are starting points; set your own after a few weeks of data.\n\n| Metric | Formula | Starting target | A bad number tells you |\n| --- | --- | --- | --- |\n| Realized slippage | (quoted receiver_amount - delivered amount) \u002F quoted receiver_amount x 10,000 | 0 bps on a binding quote | The quote was not binding, or a fee landed outside the quote |\n| Quote expiry rate | quotes expired before confirm \u002F quotes shown | Under 10% on a single confirm screen | Quotes are fetched too early, or the flow is too long |\n| Re-quote delta | (new receiver_amount - old receiver_amount) \u002F old receiver_amount x 10,000 | Within the corridor's normal range | The corridor is volatile right now |\n| Delivery success rate | completed \u002F (completed + failed + refunded) | Above 99% on established corridors | Bad recipient data, compliance holds, or a rail issue |\n| Time to settle | completed_at - executed_at, p50 and p90 per rail | Within the rail's expected window | A rail, a review step, or a cut-off is slowing payouts |\n\nA few rules for reading them:\n\n- **Realized slippage is binary in practice.** On a binding quote executed before `expires_at`, the recipient gets the quoted `receiver_amount`. A non-zero value is not \"a bit of noise\", it is a finding.\n- **Re-quote delta needs the same inputs.** Compare quotes with the same amount, currency side, fee setting, and destination. Otherwise you are measuring your own changes.\n- **Delivery success excludes payouts still in flight.** Count only payouts that reached a terminal status: `completed`, `failed`, or `refunded`.\n- **Time to settle is per rail.** Pix and SPEI settle in minutes, RTP is instant, and ACH, TED, and SEPA take about one to two business days, per BlindPay's [cut-off times reference](\u002Fdocs\u002Fkb\u002Fcut-off-times). Blending them makes every number meaningless.\n\nThe policy benchmark for speed is the G20 roadmap. The [Financial Stability Board's targets](https:\u002F\u002Fwww.fsb.org\u002F2021\u002F10\u002Ftargets-for-addressing-the-four-challenges-of-cross-border-payments-final-report\u002F) aim for 75% of retail cross-border payments to make funds available within one hour of initiation, and the rest within one business day, by end-2027. Your p50 and p90 per rail show where you stand against that.\n\n## What does a week of numbers look like?\n\n**Illustrative example.** A marketplace pays sellers in Brazil and Mexico. One week of data:\n\n- Quotes shown: 4,000. Confirmed and executed: 3,250. Expired before confirm: 560. Abandoned without expiring: 190.\n- Expiry rate: 560 \u002F 4,000 = 14%.\n- Re-quotes after expiry: 480. Average re-quote delta: 9 bps on BRL, 6 bps on MXN.\n- Payouts finished: 3,240 completed, 6 failed, 4 refunded. Delivery success: 3,240 \u002F 3,250 = 99.69%.\n- Realized slippage: 0 bps on all 3,240 completed payouts.\n- Time to settle over Pix: p50 3 minutes, p90 11 minutes.\n\nWhat to do with it. The 14% expiry rate is above the starting target, so look at the screen: the quote is probably fetched when the payout form opens, not when the user reaches the confirm step. Moving the quote request later is the cheapest fix. The delivery success rate is healthy; the 10 failures and refunds go to a weekly review of recipient bank details. [Common stablecoin payout mistakes](\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes) lists the usual causes.\n\n## What should the event log store?\n\nOne row per quote, keyed by `quote_id`, updated as the payout moves. This is enough to compute all five metrics.\n\n| Field | Source | Used for |\n| --- | --- | --- |\n| `quote_id` | Quote response (`qu_...`) | Primary key |\n| `requote_of` | Your app: the expired `quote_id` this one replaced | Re-quote delta |\n| `corridor` | Your app: currency and rail | Grouping |\n| `quoted_sender_amount`, `quoted_receiver_amount` | Quote response `sender_amount`, `receiver_amount` | Slippage, re-quote delta |\n| `commercial_quotation`, `blindpay_quotation` | Quote response | Spread and cost tracking |\n| `quote_created_at` | Your clock when the response arrives | Expiry analysis |\n| `expires_at` | Quote response, epoch milliseconds | Expiry rate |\n| `confirmed_at` | Your clock when the user confirms | Expiry rate, time on screen |\n| `payout_id`, `executed_at` | Payout response (`po_...`) and your clock | Time to settle |\n| `status` | Latest payout webhook | Delivery success |\n| `completed_at` | Completion time from the payout's tracking objects | Time to settle |\n| `delivered_amount` | Recipient confirmation or bank statement, where you have it | Realized slippage |\n\nA sample row:\n\n```json\n{\n  \"quote_id\": \"qu_000000000000\",\n  \"requote_of\": null,\n  \"corridor\": \"BRL_pix\",\n  \"quoted_sender_amount\": 100000,\n  \"quoted_receiver_amount\": 537300,\n  \"commercial_quotation\": 5.4,\n  \"blindpay_quotation\": 5.373,\n  \"quote_created_at\": \"2026-10-12T14:00:02Z\",\n  \"expires_at\": 1791813902000,\n  \"confirmed_at\": \"2026-10-12T14:01:15Z\",\n  \"payout_id\": \"po_000000000000\",\n  \"executed_at\": \"2026-10-12T14:01:16Z\",\n  \"status\": \"completed\",\n  \"completed_at\": \"2026-10-12T14:04:40Z\",\n  \"delivered_amount\": 537300\n}\n```\n\nTwo traps. `expires_at` is epoch milliseconds, not seconds; divide by 1,000 only if your date library expects seconds. And amounts are integers in minor units, so 537300 means R$5,373.00.\n\n## How do webhooks feed the log?\n\nWebhooks update the `status` and timestamps without polling. BlindPay sends three payout events, documented in the [webhook events reference](\u002Fdocs\u002Flearn\u002Fwebhooks-events):\n\n1. `payout.new`: the payout is created and the source funds are captured. Set `payout_id` and `status`.\n2. `payout.update`: the payout moves through an intermediate step, such as document checks, manual review, or the bank send. A payout that reaches `failed` arrives here too.\n3. `payout.complete`: the payout is confirmed at the destination or refunded.\n\nSo the rule is simple: on every payout event, read the `status` field and write it to the row. Classify `completed`, `failed`, and `refunded` as terminal from the status, never from the event name alone. That keeps delivery success correct whichever event carried the change.\n\nVerify every webhook signature before trusting it, and process events idempotently, since the same event can arrive twice. [Stablecoin webhooks and reconciliation](\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation) covers both, and [stablecoin payout statuses explained](\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained) covers what each status means for the recipient.\n\n## What should the dashboard show?\n\nThree rows, read top to bottom in under a minute.\n\n- **Row 1, health tiles.** Five numbers for the last 7 days, each against its target: realized slippage (should read 0 bps), expiry rate, average re-quote delta, delivery success rate, and Pix or SPEI p90 time to settle.\n- **Row 2, per-corridor trends.** One line chart per metric, split by corridor, over 90 days. Expiry rate and re-quote delta on the same time axis, so you can see when volatility drove expiries.\n- **Row 3, exceptions.** A table of payouts that broke a rule: any non-zero realized slippage, any payout past its rail's p90, and every `failed` or `refunded` payout with its reason.\n\nAlert on two things only: any non-zero realized slippage, and a delivery success rate that drops below target for a corridor. Everything else is a weekly review.\n\nWhen an expired quote triggers a re-quote in your code, log the link between the two ids. [How to handle expired quotes in TypeScript and Python](\u002Fresources\u002Fmore\u002Fhandle-expired-quotes-typescript-python) shows the retry pattern, and [cost per delivered dollar](\u002Fresources\u002Fmore\u002Fcost-per-delivered-dollar) turns the same log into an all-in cost per corridor. For who absorbs the market move while a quote is open, see [who carries FX risk in a stablecoin payout](\u002Fresources\u002Fmore\u002Fwho-carries-fx-risk-stablecoin-payout).\n\n## How does BlindPay help you measure this?\n\nEvery BlindPay quote returns the fields the log needs: `id`, `expires_at`, `commercial_quotation`, `blindpay_quotation`, `sender_amount`, `receiver_amount`, and the fee lines. Payout quotes lock the rate and fees for 5 minutes by default, and an expired quote is rejected instead of executed at a new rate, so realized slippage on BlindPay payouts executed in time is designed to be zero.\n\nPayout webhooks are signed and carry the payout's status and tracking objects. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review.\n\n## What to do next\n\nAdd the event log table to your database, write one row per quote, and backfill a week of payouts. Then compute the five metrics per corridor and set your first targets. The [payout quotes docs](\u002Fdocs\u002Fpayout-quotes) list every field the log reads.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":5,"description":896},"Payout quality metrics: slippage, expiry, re-quote delta","resources\u002Fmore\u002Fpayout-quality-metrics-slippage-expiry-rate","KksqycMYL58W2lK_neMfc3QeRLVPXVmJ-SFtJgkYjqg",[925,929,933,937,941,945,949,953,957,961,965,969,973,977,980,984,987,991,995,999,1003,1007,1011,1015,1019,1023,1027,1031,1035,1039,1043,1047,1051,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,1155,1159,1163,1167,1171,1175,1179,1183,1187,1191,1195,1199,1203,1207,1211,1215,1219,1223,1227,1231,1235,1236,1240,1243,1247,1251,1255,1259,1263,1267,1270,1273,1277,1281,1285,1289,1293,1297,1301,1305,1308,1312,1316,1320,1324,1328,1332,1336,1340,1344,1348,1352,1356,1360,1364,1368,1372,1376,1380,1384,1388,1392,1396,1400,1404,1408,1412,1416,1420,1424,1428,1432,1436,1440,1444,1447,1451,1455,1459],{"path":926,"title":927,"description":928},"\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":930,"title":931,"description":932},"\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":934,"title":935,"description":936},"\u002Fresources\u002Fmore\u002Fbin-sponsor-vs-issuer-processor-vs-program-manager","BIN sponsor vs. issuer-processor vs. program manager: who does what in a card program","The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider.",{"path":938,"title":939,"description":940},"\u002Fresources\u002Fmore\u002Fbest-real-time-cross-border-settlement-providers-2026","Best real-time cross-border settlement providers for fintechs in 2026: low fees compared","A 10-point checklist and a side-by-side of BlindPay, Wise Platform, Airwallex, Thunes, Bridge, and Circle for real-time, low-fee cross-border settlement.",{"path":942,"title":943,"description":944},"\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":946,"title":947,"description":948},"\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":950,"title":951,"description":952},"\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":954,"title":955,"description":956},"\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":958,"title":959,"description":960},"\u002Fresources\u002Fmore\u002Fbridge-cards-and-blindpay-payouts","Bridge and BlindPay: stablecoin cards plus local-currency payouts in one stack","How a card program runs Bridge for stablecoin cards and wallets and BlindPay for bank funding and local payouts: architecture, flows, and who owns what.",{"path":962,"title":963,"description":964},"\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":966,"title":967,"description":968},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-card-program","Build vs. buy: should you build your own stablecoin card program?","Scoring build, assemble, and buy options for a stablecoin card program on network membership, BIN sponsorship, processing, compliance, time, and cost.",{"path":970,"title":971,"description":972},"\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":974,"title":975,"description":976},"\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":280,"title":978,"description":979},"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":981,"title":982,"description":983},"\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":831,"title":985,"description":986},"Cost per delivered dollar: the real cost of a cross-border payout","Cost per delivered dollar compares what you send with what lands, valued at the market rate. The formula, three worked setups, and 8 hidden costs.",{"path":988,"title":989,"description":990},"\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":992,"title":993,"description":994},"\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":996,"title":997,"description":998},"\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":1000,"title":1001,"description":1002},"\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":1004,"title":1005,"description":1006},"\u002Fresources\u002Fmore\u002Fstablecoin-card-balance-to-local-bank","From stablecoin to local bank: when to cash out over Pix, SPEI, ACH, SEPA, or SWIFT instead of using a card","When a stablecoin card is the wrong tool and a local bank payout fits: rent, payroll, invoices. Each rail compared, plus how a payout API flow works.",{"path":1008,"title":1009,"description":1010},"\u002Fresources\u002Fmore\u002Fhidden-fees-international-wires-our-sha-ben","Hidden fees in international wires: OUR, SHA, BEN, and a 7-point quote audit","Why suppliers get short-paid on international wires: SWIFT charge codes, intermediary deductions, and FX markups. Plus a 7-step audit for any quote.",{"path":1012,"title":1013,"description":1014},"\u002Fresources\u002Fmore\u002Fai-agents-live-fx-quotes-mcp","How AI agents get live FX quotes and pay out through MCP and Agent Skills","How an AI agent creates a live stablecoin quote, shows rate, fees, and expiry, waits for a human to confirm, and pays out through BlindPay's MCP server.",{"path":1016,"title":1017,"description":1018},"\u002Fresources\u002Fmore\u002Fpay-suppliers-brazil-mexico-from-us-bank-account","How a US company pays suppliers in Brazil and Mexico from a US bank account","Three ways to pay suppliers in Brazil and Mexico from dollars in a US bank account: an international wire, a fintech transfer, or USD to Pix or SPEI.",{"path":1020,"title":1021,"description":1022},"\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":1024,"title":1025,"description":1026},"\u002Fresources\u002Fmore\u002Fhow-stablecoin-card-issuers-make-money","How do stablecoin card issuers make money? Interchange, FX, and program economics","Where the revenue in a stablecoin card program comes from: interchange, FX, fees, and rewards, with an illustrative unit-economics model and the caps.",{"path":1028,"title":1029,"description":1030},"\u002Fresources\u002Fmore\u002Fhow-stablecoin-card-transactions-settle","How does a stablecoin card transaction work? Authorization, clearing, and settlement step by step","A $4.50 coffee and a $200 hotel hold, followed from tap to merchant payout: authorization, clearing, T+1 settlement, and how USDC becomes fiat at checkout.",{"path":1032,"title":1033,"description":1034},"\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":1036,"title":1037,"description":1038},"\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":1040,"title":1041,"description":1042},"\u002Fresources\u002Fmore\u002Flive-quotes-volatile-currencies-latin-america","How live quotes handle volatile currencies: BRL, MXN, COP, and ARS","A live quote locks one payout's rate, not your budget. How BRL, MXN, COP, and ARS rates are set, and how to design payouts around moving currencies.",{"path":1044,"title":1045,"description":1046},"\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":1048,"title":1049,"description":1050},"\u002Fresources\u002Fmore\u002Fhow-much-stablecoin-float-for-payouts","How much USDC should you hold to fund payouts? Sizing a stablecoin float without pre-funding","No pre-funding still means holding some USDC. How to size one stablecoin float for every payout corridor: lead time, safety stock, and a worked example.",{"path":1052,"title":1053,"description":1054},"\u002Fresources\u002Fmore\u002Fcross-border-payment-costs-2026","How much do cross-border payments cost in 2026? Fees by corridor and what counts as cheap","Sending $200 abroad costs 6.36% on average, per the World Bank. Here is where that money goes, how corridors differ, and what a cheap payment looks like.",{"path":1056,"title":1057,"description":1058},"\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":1060,"title":1061,"description":1062},"\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":1064,"title":1065,"description":1066},"\u002Fresources\u002Fmore\u002Fpartner-fees-markup-on-live-quotes","How platforms add their own margin to a live quote: partner fees explained","A partner fee is the markup a platform adds to a stablecoin quote. How to set percentage or flat fees, show them on the quote, and get paid each month.",{"path":1068,"title":1069,"description":1070},"\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":1072,"title":1073,"description":1074},"\u002Fresources\u002Fmore\u002Fhow-to-calculate-fx-spread","How to calculate FX spread on an international payment (with worked examples)","FX spread % = (mid rate - offered rate) \u002F mid rate x 100. Here is how to get the mid rate, fix the quote direction, and price the spread in dollars.",{"path":1076,"title":1077,"description":1078},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-card-issuing-provider","How to choose a stablecoin card issuing provider: an 8-point framework and a neutral look at Bridge, Rain, BVNK, and Gnosis Pay","An 8-point framework for choosing a stablecoin card issuing provider, a neutral look at Bridge, Rain, BVNK, and Gnosis Pay, and the payout layer beside it.",{"path":1080,"title":1081,"description":1082},"\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":1084,"title":1085,"description":1086},"\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":1088,"title":1089,"description":1090},"\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":1092,"title":1093,"description":1094},"\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":1096,"title":1097,"description":1098},"\u002Fresources\u002Fmore\u002Fonramp-offramp-liquidity-scorecard","How to evaluate an on\u002Foff-ramp provider's liquidity: a 10-point scorecard","Score any on\u002Foff-ramp provider's liquidity from 0 to 20: binding quotes, lock length, expiry, fees, depth, pre-funding, custody, and pricing.",{"path":1100,"title":1101,"description":1102},"\u002Fresources\u002Fmore\u002Ffund-stablecoin-card-pix-spei","How to fund a stablecoin card with Pix or SPEI, and cash out what is left","The full top-up and cash-out loop for stablecoin cards in Brazil and Mexico: Pix and SPEI payins, where FX happens, timing, limits, and what to check.",{"path":1104,"title":1105,"description":1106},"\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":1108,"title":1109,"description":1110},"\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":1112,"title":1113,"description":1114},"\u002Fresources\u002Fmore\u002Fhow-to-launch-a-stablecoin-card-program","How to launch a stablecoin card program: a 9-step plan and who does what","A 9-step plan to launch a stablecoin card program: market, program manager, sponsor bank and BIN, processor, custody, compliance, funding, and payouts.",{"path":1116,"title":1117,"description":1118},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-gbp-faster-payments","How to off-ramp USDC to GBP over UK Faster Payments: bank details, quotes, and timing","Turn USDC into pounds in a UK bank account over Faster Payments: sort code details, quotes in USDC or GBP, quote windows, timing, and a worked example.",{"path":1120,"title":1121,"description":1122},"\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":1124,"title":1125,"description":1126},"\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":1128,"title":1129,"description":1130},"\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":1132,"title":1133,"description":1134},"\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":1136,"title":1137,"description":1138},"\u002Fresources\u002Fmore\u002Fpay-exact-local-amount-receiver-side-quote","How to pay an exact BRL, MXN, or EUR amount from USDC: receiver-side quotes explained","Fix what the recipient gets, not what you send. How receiver-side quotes and cover_fees land exact amounts over Pix, SPEI, and SEPA, with worked examples.",{"path":1140,"title":1141,"description":1142},"\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":1144,"title":1145,"description":1146},"\u002Fresources\u002Fmore\u002Fbatch-stablecoin-payouts-live-quotes","How to run batch payouts with live quotes: one quote per payout, expiry, and rate drift","How to pay 100+ recipients from USDC with live quotes: quote and execute per payout, size the funding, handle expiry and retries, and track the batch.",{"path":1148,"title":1149,"description":1150},"\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":1152,"title":1153,"description":1154},"\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":1156,"title":1157,"description":1158},"\u002Fresources\u002Fmore\u002Fcross-border-quote-screen-fee-disclosure","How to show a cross-border payment quote to users: rate, fees, and expiry","What a cross-border quote screen must show: amount sent, rate, fees, amount received, expiry, and delivery date, plus the CFPB and EU disclosure rules.",{"path":1160,"title":1161,"description":1162},"\u002Fresources\u002Fmore\u002Fhow-freelancers-spend-usdc","How to spend USDC as a freelancer: stablecoin card, exchange off-ramp, or local bank payout","Three ways to spend USDC as a freelancer: a stablecoin card, an exchange off-ramp, or a local payout over Pix, SPEI, or ACH, compared on speed and cost.",{"path":1164,"title":1165,"description":1166},"\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":1168,"title":1169,"description":1170},"\u002Fresources\u002Fmore\u002Ftest-offramp-liquidity-depth","How to test an off-ramp's liquidity depth before you commit: a quote-ladder protocol","Quote $500, $5,000, $50,000, and $250,000 at the same moment, three times a day, and compare the rate. The protocol, log table, and pass rule.",{"path":1172,"title":1173,"description":1174},"\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":1176,"title":1177,"description":1178},"\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":1180,"title":1181,"description":1182},"\u002Fresources\u002Fmore\u002Findicative-rate-vs-binding-quote-api","Indicative rate vs binding quote: how to show a live price before the user commits","An indicative rate previews a price. A binding quote locks it. How to show a live price while the user types, then lock it before they pay.",{"path":1184,"title":1185,"description":1186},"\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":1188,"title":1189,"description":1190},"\u002Fresources\u002Fmore\u002Fjust-in-time-vs-prefunded-stablecoin-cards","Just-in-time vs prefunded stablecoin cards: which funding model is better?","Just-in-time vs prefunded stablecoin cards for users and program operators: when conversion happens, top-up fees, float, declines, and tax timing compared.",{"path":1192,"title":1193,"description":1194},"\u002Fresources\u002Fmore\u002Flive-quote-vs-forward-contract-vs-fixed-rate","Live quote vs forward contract vs fixed rate: which FX tool fits a cross-border payout?","A live quote holds a rate for minutes, a forward locks one for a future date, a fixed rate holds a day. How each prices risk, and when treasury uses each.",{"path":1196,"title":1197,"description":1198},"\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":1200,"title":1201,"description":1202},"\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":1204,"title":1205,"description":1206},"\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":1208,"title":1209,"description":1210},"\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":1212,"title":1213,"description":1214},"\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":1216,"title":1217,"description":1218},"\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":1220,"title":1221,"description":1222},"\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":1224,"title":1225,"description":1226},"\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":1228,"title":1229,"description":1230},"\u002Fresources\u002Fmore\u002Fpay-contractors-stablecoin-cards-or-payouts","Paying contractors and teams with stablecoins: cards, expense cards, or local payouts?","How to pay a global team with stablecoins: compare stablecoin cards, wallet payments, and local bank payouts by country, amount, frequency, and cost.",{"path":1232,"title":1233,"description":1234},"\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":918,"title":5,"description":896},{"path":1237,"title":1238,"description":1239},"\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":826,"title":1241,"description":1242},"Quote-then-execute in TypeScript and Python: how to handle expired quotes and re-quotes","TypeScript and Python code for a stablecoin payout API: read expires_at, approve, execute with an idempotency key, and re-quote on QUOTES_EXPIRED.",{"path":1244,"title":1245,"description":1246},"\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template","Stablecoin API RFP template: sections, scoring, and a vendor scorecard","How to write an RFP for a stablecoin API: the eight sections to include, pass or fail gates, 1 to 3 weighted scoring, a copyable scorecard, and a timeline.",{"path":1248,"title":1249,"description":1250},"\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":1252,"title":1253,"description":1254},"\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":1256,"title":1257,"description":1258},"\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":1260,"title":1261,"description":1262},"\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":1264,"title":1265,"description":1266},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Stablecoin API sandbox vs production: what testing misses","Most stablecoin API sandboxes pass every integration test and still leave a team unprepared for production, because webhook delivery and idempotent retries are exactly what sandboxes fake or skip.",{"path":777,"title":1268,"description":1269},"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":72,"title":1271,"description":1272},"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":1274,"title":1275,"description":1276},"\u002Fresources\u002Fmore\u002Fstablecoin-card-fees-explained","Stablecoin card fees explained: spread, FX markup, ATM, and hidden costs","How to calculate the real cost of a stablecoin card: spread, FX markup, top-up, ATM, and inactivity fees, with a worked $1,500 example and a checklist.",{"path":1278,"title":1279,"description":1280},"\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-platforms-compared","Stablecoin card issuing platforms compared: Bridge, Rain, Stripe Issuing, and where BlindPay fits","Bridge, Rain, and Stripe Issuing with Bridge compared layer by layer from their own pages, plus the funding and payout layer BlindPay runs around a card.",{"path":1282,"title":1283,"description":1284},"\u002Fresources\u002Fmore\u002Fstablecoin-card-vs-pix-spei-payouts","Stablecoin card or Pix and SPEI payout? When each one wins in Brazil and Mexico","When a stablecoin card fits in Brazil and Mexico, when a Pix or SPEI payout wins, and how to combine both for spending, rent, payroll, and suppliers.",{"path":1286,"title":1287,"description":1288},"\u002Fresources\u002Fmore\u002Fstablecoin-card-program-architecture","Stablecoin card program architecture: from bank deposit to card spend to local payout","A reference architecture for a stablecoin card program: KYC, bank deposit, conversion, wallet, JIT funding, network settlement, and local-currency payout.",{"path":1290,"title":1291,"description":1292},"\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":1294,"title":1295,"description":1296},"\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":1298,"title":1299,"description":1300},"\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":1302,"title":1303,"description":1304},"\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":782,"title":1306,"description":1307},"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":1309,"title":1310,"description":1311},"\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":1313,"title":1314,"description":1315},"\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":1317,"title":1318,"description":1319},"\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":1321,"title":1322,"description":1323},"\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":1325,"title":1326,"description":1327},"\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":1329,"title":1330,"description":1331},"\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":1333,"title":1334,"description":1335},"\u002Fresources\u002Fmore\u002Fswift-instant-cross-border-scheme-vs-stablecoins","Swift's new payments scheme and blockchain ledger vs stablecoins: what changes in 2026","Swift launched a retail payments scheme in June 2026 and a blockchain ledger pilot in July. What each one changes, and how they compare with stablecoins.",{"path":1337,"title":1338,"description":1339},"\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":1341,"title":1342,"description":1343},"\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":1345,"title":1346,"description":1347},"\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":1349,"title":1350,"description":1351},"\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":1353,"title":1354,"description":1355},"\u002Fresources\u002Fmore\u002Fstablecoin-card-for-travel","Using a stablecoin card abroad: FX rates, markups, ATM fees, and when a normal debit card is cheaper","How a stablecoin card prices purchases abroad: network FX rates, issuer markups, currency conversion, ATM fees, and when a fintech debit card costs less.",{"path":1357,"title":1358,"description":1359},"\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":1361,"title":1362,"description":1363},"\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":1365,"title":1366,"description":1367},"\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":1369,"title":1370,"description":1371},"\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":1373,"title":1374,"description":1375},"\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":1377,"title":1378,"description":1379},"\u002Fresources\u002Fmore\u002Fnostro-vostro-accounts-explained","What are nostro and vostro accounts? And why they force pre-funding","A nostro account is a bank's account at a foreign bank, in that bank's currency. A vostro is the same account seen from the other side. Why both trap cash.",{"path":1381,"title":1382,"description":1383},"\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":1385,"title":1386,"description":1387},"\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":1389,"title":1390,"description":1391},"\u002Fresources\u002Fmore\u002Fherstatt-risk-fx-settlement-risk","What is Herstatt risk? FX settlement risk, PvP, and what real-time settlement changes","Herstatt risk is paying your side of an FX trade and never getting the other. What happened in 1974, how PvP removes it, and where it remains.",{"path":1393,"title":1394,"description":1395},"\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":1397,"title":1398,"description":1399},"\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":1401,"title":1402,"description":1403},"\u002Fresources\u002Fmore\u002Fwhat-is-a-market-maker-stablecoin-payments","What is a market maker in stablecoin payments? How they set the rate on your quote","A market maker quotes a buy and a sell price and earns the gap. Who they are in stablecoin payments, how they shape your quote, and what to ask.",{"path":1405,"title":1406,"description":1407},"\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":1409,"title":1410,"description":1411},"\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":1413,"title":1414,"description":1415},"\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":1417,"title":1418,"description":1419},"\u002Fresources\u002Fmore\u002Fprefunding-and-collateral-in-card-issuing","What is prefunding in card issuing, and how do stablecoins reduce it?","Why card programs park cash before anyone spends, how weekends and holidays inflate the buffer, and how daily stablecoin settlement shrinks it.",{"path":1421,"title":1422,"description":1423},"\u002Fresources\u002Fmore\u002Fwhat-is-real-time-cross-border-settlement","What is real-time cross-border settlement? A 2026 guide","Real-time cross-border settlement means the recipient can use the money minutes after you send it. Which rails do it, what it costs, and where it stops.",{"path":1425,"title":1426,"description":1427},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","What to ask a stablecoin payments provider: 30 due diligence questions","The questions to ask a stablecoin payments vendor before you sign: licensing, custody, pricing, rails, compliance, failure handling, security, and exit.",{"path":1429,"title":1430,"description":1431},"\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":1433,"title":1434,"description":1435},"\u002Fresources\u002Fmore\u002Fwhere-is-the-exchange-rate-set-onramp-offramp","Where does the exchange rate get fixed in an on-ramp and off-ramp? A step-by-step map","A USD on-ramp and a USDC to BRL Pix off-ramp, step by step: who does what, where the exchange rate is locked, where fees apply, and what expiry changes.",{"path":1437,"title":1438,"description":1439},"\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":1441,"title":1442,"description":1443},"\u002Fresources\u002Fmore\u002Finstant-payment-systems-by-country","Which countries have instant payment systems? A 2026 reference table","Pix, SPEI, RTP, FedNow, SEPA Instant, Faster Payments, UPI, Bre-B, and more: who runs each instant payment system, when it launched, its hours, and limits.",{"path":836,"title":1445,"description":1446},"Who carries FX risk in a stablecoin payout? A step-by-step map, and why quotes expire","You carry FX risk until you lock a quote, the provider carries it inside the window, and it comes back to you on a refund. Step-by-step map and math.",{"path":1448,"title":1449,"description":1450},"\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":1452,"title":1453,"description":1454},"\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":1456,"title":1457,"description":1458},"\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.",{"path":1460,"title":1461,"description":1462},"\u002Fresources\u002Fmore\u002Fwhy-google-rate-differs-from-quote","Why is the rate on Google different from my off-ramp quote?","Google shows a delayed mid-market reference. An off-ramp quote is a price you can execute. Why the two differ, and how to measure the gap in bps.",1792077645525]