[{"data":1,"prerenderedAt":13772},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts":3,"resources-category-no-pre-funding-stablecoin-payouts":369},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":340,"description":341,"extension":342,"faq":343,"howto":6,"isBlog":359,"isChangelog":359,"meta":360,"navigation":362,"path":363,"pillar":359,"products":6,"rawbody":364,"role":6,"seo":365,"seoTitle":366,"stem":367,"thumbnail":6,"updated":6,"__hash__":368},"content\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts.md","What does \"no pre-funding\" mean in a stablecoin API?",null,{"type":8,"value":9,"toc":327},"minimark",[10,14,17,22,25,28,31,35,38,106,109,113,116,123,129,141,144,160,163,167,170,182,188,194,200,208,212,215,240,243,247,250,279,291,295,302,309,313,321],[11,12,13],"p",{},"No pre-funding means each payout is funded at the moment you send it, instead of from a balance you parked in advance. You don't keep reais in a Brazilian bank account to pay Brazilian contractors, and you don't top up a balance with your provider a week before payroll. With a stablecoin API, value moves on-chain at payout time, converts to local currency at a quoted rate, and lands over the local rail. The money leaves your treasury when the payment happens. Not before.",[11,15,16],{},"It sounds like a small operational detail. It isn't. Trapped capital is a CFO problem, not a crypto problem, and it's the difference between money that works and money that waits.",[18,19,21],"h2",{"id":20},"why-did-cross-border-payouts-ever-need-pre-funding","Why did cross-border payouts ever need pre-funding?",[11,23,24],{},"Because fast local payouts over bank rails need money that's already local.",[11,26,27],{},"If you want a contractor in Mexico paid over SPEI today, someone needs pesos in a Mexican bank account today. An international wire to get those pesos there takes 1 to 5 business days. So either you, or your provider, keeps a pile of pesos in Mexico and refills it with slower wires.",[11,29,30],{},"That pile is pre-funding. Banks have run it for decades through nostro and vostro accounts, balances one bank keeps at another in each currency it settles. It's the price of speed on traditional rails. Multiply it by every country you pay into.",[18,32,34],{"id":33},"what-are-the-three-funding-models","What are the three funding models?",[11,36,37],{},"Every payout provider uses one of these. Ask which one before you sign.",[39,40,41,60],"table",{},[42,43,44],"thead",{},[45,46,47,51,54,57],"tr",{},[48,49,50],"th",{},"Model",[48,52,53],{},"How it works",[48,55,56],{},"Capital tied up",[48,58,59],{},"FX exposure",[61,62,63,78,92],"tbody",{},[45,64,65,69,72,75],{},[66,67,68],"td",{},"Pre-funded local accounts",[66,70,71],{},"You hold a bank account and a balance in each destination currency, and pay out from it",[66,73,74],{},"One to two payout cycles per country",[66,76,77],{},"Weeks, on every foreign balance",[45,79,80,83,86,89],{},[66,81,82],{},"Pre-funded provider balance",[66,84,85],{},"You top up a balance with your provider in advance; it pays from its own local liquidity",[66,87,88],{},"At least one payout cycle, plus top-up lead time",[66,90,91],{},"Low to medium, depending on the balance currency",[45,93,94,97,100,103],{},[66,95,96],{},"Funded at send time",[66,98,99],{},"You fund each payout when you create it, from a wallet or a virtual USD account",[66,101,102],{},"None beyond the payout itself",[66,104,105],{},"Minutes, the length of the transfer",[11,107,108],{},"The middle model is the sneaky one. It gets marketed as \"no pre-funding\" because you don't hold foreign bank accounts. But if the payout draws from a balance you had to top up days earlier, you're still pre-funding. You just moved the float to the provider.",[18,110,112],{"id":111},"how-does-funding-at-send-time-actually-work","How does funding at send time actually work?",[11,114,115],{},"At BlindPay, a payout is funded from one of three sources, and none of them is a pre-loaded balance in the destination currency.",[11,117,118,122],{},[119,120,121],"strong",{},"1. A stablecoin wallet you control."," You hold USDC or USDT in your own wallet on a supported network. You request a quote, approve the exact quoted amount on-chain, and create the payout. BlindPay pulls only that amount, only at that moment.",[11,124,125,128],{},[119,126,127],{},"2. A managed wallet."," BlindPay generates the address and holds the keys, so there's no on-chain approval step. You still decide when funds go in and when each payout goes out.",[11,130,131,134,135,140],{},[119,132,133],{},"3. A virtual USD account."," A ",[136,137,139],"a",{"href":138},"\u002Fvirtual-accounts","virtual USD account"," is a US account number in your customer's name. Send dollars to it by ACH, wire, or SWIFT, and each deposit converts to USDC or USDT in the linked wallet. From there, the payout flow is the same.",[11,142,143],{},"In all three, the sequence is:",[145,146,147,151,154,157],"ol",{},[148,149,150],"li",{},"Request a quote. The rate, fees, and exact receive amount are locked for five minutes.",[148,152,153],{},"Fund the payout with the quoted stablecoin amount.",[148,155,156],{},"Stablecoins move on-chain in seconds.",[148,158,159],{},"Local currency lands over Pix, SPEI, ACH, SEPA, or another rail.",[11,161,162],{},"Nothing sits in Brazil. Nothing sits in Mexico. No destination-currency balance waits for payroll day.",[18,164,166],{"id":165},"whats-the-working-capital-math","What's the working-capital math?",[11,168,169],{},"An illustrative example. A staffing company pays contractors every two weeks, about 900,000 USD per cycle:",[171,172,173,176,179],"ul",{},[148,174,175],{},"Brazil: 450,000 USD",[148,177,178],{},"Mexico: 270,000 USD",[148,180,181],{},"Colombia: 180,000 USD",[11,183,184,187],{},[119,185,186],{},"With pre-funded local accounts."," Top-up wires take up to five business days, so the finance team keeps about 1.5 cycles in each country to be safe. That's roughly 1,350,000 USD sitting in three foreign bank accounts at all times. If that cash could earn 4% in short-term Treasury bills, the company gives up about 54,000 USD a year in yield. And it holds 1.35 million dollars' worth of reais and pesos, so a 3% adverse move in those currencies is a 40,500 USD swing it didn't plan for.",[11,189,190,193],{},[119,191,192],{},"With a pre-funded provider balance."," Better. No foreign bank accounts. But the balance still has to hold at least one cycle, plus the top-up lead time, so 900,000 USD or more sits idle with the provider.",[11,195,196,199],{},[119,197,198],{},"Funded at send time."," The treasury keeps its dollars until payout day. On payout day it funds exactly 900,000 USD worth of payouts, each at a quoted rate. Idle capital: zero. FX exposure: minutes.",[11,201,202,203,207],{},"Now add a fourth country. With pre-funded accounts, that's a new bank relationship, a new buffer, and a new currency position. Funded at send time, it's a new ",[204,205,206],"code",{},"type"," on a bank account. The expansion stops being a treasury project.",[18,209,211],{"id":210},"what-are-the-trade-offs","What are the trade-offs?",[11,213,214],{},"Being honest about it. Funding at send time has three constraints:",[171,216,217,228,234],{},[148,218,219,222,223,227],{},[119,220,221],{},"You need the funds on hand when you send."," Stablecoins in the wallet, or a USD deposit that has already landed in the virtual account. USD deposits by ACH or wire can take up to five business days to arrive, so plan the deposit, not the balance. Rail-by-rail timing is in ",[136,224,226],{"href":225},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times","how long a stablecoin payout takes",".",[148,229,230,233],{},[119,231,232],{},"Quotes expire."," A payout quote is valid for five minutes by default. Create the payout inside the window, or request a new quote.",[148,235,236,239],{},[119,237,238],{},"Self-custodied EVM wallets need an approval."," You approve the quoted amount on-chain before creating the payout. Managed wallets skip this.",[11,241,242],{},"None of these ask you to park capital. They ask you to be ready at the moment of payment, which is what treasury wants anyway.",[18,244,246],{"id":245},"what-should-you-ask-a-provider-about-pre-funding","What should you ask a provider about pre-funding?",[11,248,249],{},"Five questions that expose the funding model fast:",[145,251,252,258,263,268,273],{},[148,253,254,257],{},[119,255,256],{},"Does a payout draw from a balance I topped up in advance?"," If yes, it's pre-funded, whatever the website says.",[148,259,260],{},[119,261,262],{},"Is there a minimum balance, per currency or overall?",[148,264,265],{},[119,266,267],{},"Who holds the destination-currency liquidity, and when is it sourced?",[148,269,270],{},[119,271,272],{},"Is the FX quote binding, and for how long?",[148,274,275,278],{},[119,276,277],{},"If a payout fails, where do the funds go, and how fast?"," At BlindPay, stablecoin refunds return to the originating wallet right away.",[11,280,281,282,286,287,227],{},"Get the answers in writing. For the rest of the evaluation, read ",[136,283,285],{"href":284},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","how to choose a stablecoin API",", and for how stablecoins sit inside a multi-rail strategy, read ",[136,288,290],{"href":289},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts","stablecoins in payment orchestration",[18,292,294],{"id":293},"where-does-blindpay-fit","Where does BlindPay fit?",[11,296,297,301],{},[136,298,300],{"href":299},"\u002Fglobal-payments","BlindPay"," is a stablecoin API built on the funded-at-send-time model. Each payout is funded when you create it, from your own wallet, a managed wallet, or a virtual USD account. Payouts land in local currency over Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and wire in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries.",[11,303,304,305,227],{},"KYC, KYB, and sanctions screening run inside the API before money moves. Official SDKs cover Node, Python, Go, PHP, and Swift, and ",[136,306,308],{"href":307},"\u002Fpricing","pricing is published",[18,310,312],{"id":311},"what-to-do-next","What to do next",[11,314,315,316,320],{},"Pull last quarter's payout volume by country and add up the balances you kept in each one. That number is your pre-funding cost. Then run one test payout on a development instance with the ",[136,317,319],{"href":318},"\u002Fdocs\u002Fquickstart-payout","payout quickstart"," and see what funding at send time looks like in practice.",[11,322,323],{},[324,325,326],"em",{},"This article is for general information only and is not legal, tax, or financial advice.",{"title":328,"searchDepth":329,"depth":329,"links":330},"",2,[331,332,333,334,335,336,337,338],{"id":20,"depth":329,"text":21},{"id":33,"depth":329,"text":34},{"id":111,"depth":329,"text":112},{"id":165,"depth":329,"text":166},{"id":210,"depth":329,"text":211},{"id":245,"depth":329,"text":246},{"id":293,"depth":329,"text":294},{"id":311,"depth":329,"text":312},"payments","2026-08-21","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.","md",[344,347,350,353,356],{"q":345,"a":346},"What does no pre-funding mean for cross-border payments?","It means you fund each payout at the moment you send it, instead of keeping a balance in advance, either in a bank account in each destination country or in a balance held with your payment provider. With a stablecoin API, value moves on-chain at payout time and converts to local currency at a quoted rate, so there is no local balance to draw from.",{"q":348,"a":349},"Does BlindPay require pre-funding?","No. Each BlindPay payout is funded when you create it, from a stablecoin wallet you control, a BlindPay-managed wallet, or a virtual USD account that converts ACH, wire, or SWIFT deposits into USDC or USDT. There is no minimum balance to maintain in any destination currency.",{"q":351,"a":352},"Why do traditional cross-border providers require pre-funding?","Because fast local payouts over bank rails need money already sitting in the destination country. The provider, or you, keeps local currency in a local bank account and pays out from it, then refills it with slower international wires. That float is the price of speed on traditional rails.",{"q":354,"a":355},"How much working capital does no pre-funding free up?","It depends on volume and how long top-ups take. A company paying 900,000 USD every two weeks across three countries typically keeps 1.5 payout cycles in local balances, about 1.35 million USD. Funding each payout at send time frees that capital and cuts FX exposure from weeks to the length of a transfer.",{"q":357,"a":358},"Is there any downside to funding payouts at send time?","You need the funds available when you send, and you need to create the payout before the quote expires, which is five minutes by default. With a self-custodied EVM wallet there is also an on-chain approval step. Managed wallets skip that step.",false,{"author":361},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","---\ntitle: \"What does \\\"no pre-funding\\\" mean in a stablecoin API?\"\nseoTitle: \"What does no pre-funding mean in a stablecoin API?\"\ndescription: \"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.\"\ndate: \"2026-08-21\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What does no pre-funding mean for cross-border payments?\"\n    a: \"It means you fund each payout at the moment you send it, instead of keeping a balance in advance, either in a bank account in each destination country or in a balance held with your payment provider. With a stablecoin API, value moves on-chain at payout time and converts to local currency at a quoted rate, so there is no local balance to draw from.\"\n  - q: \"Does BlindPay require pre-funding?\"\n    a: \"No. Each BlindPay payout is funded when you create it, from a stablecoin wallet you control, a BlindPay-managed wallet, or a virtual USD account that converts ACH, wire, or SWIFT deposits into USDC or USDT. There is no minimum balance to maintain in any destination currency.\"\n  - q: \"Why do traditional cross-border providers require pre-funding?\"\n    a: \"Because fast local payouts over bank rails need money already sitting in the destination country. The provider, or you, keeps local currency in a local bank account and pays out from it, then refills it with slower international wires. That float is the price of speed on traditional rails.\"\n  - q: \"How much working capital does no pre-funding free up?\"\n    a: \"It depends on volume and how long top-ups take. A company paying 900,000 USD every two weeks across three countries typically keeps 1.5 payout cycles in local balances, about 1.35 million USD. Funding each payout at send time frees that capital and cuts FX exposure from weeks to the length of a transfer.\"\n  - q: \"Is there any downside to funding payouts at send time?\"\n    a: \"You need the funds available when you send, and you need to create the payout before the quote expires, which is five minutes by default. With a self-custodied EVM wallet there is also an on-chain approval step. Managed wallets skip that step.\"\n---\n\nNo pre-funding means each payout is funded at the moment you send it, instead of from a balance you parked in advance. You don't keep reais in a Brazilian bank account to pay Brazilian contractors, and you don't top up a balance with your provider a week before payroll. With a stablecoin API, value moves on-chain at payout time, converts to local currency at a quoted rate, and lands over the local rail. The money leaves your treasury when the payment happens. Not before.\n\nIt sounds like a small operational detail. It isn't. Trapped capital is a CFO problem, not a crypto problem, and it's the difference between money that works and money that waits.\n\n## Why did cross-border payouts ever need pre-funding?\n\nBecause fast local payouts over bank rails need money that's already local.\n\nIf you want a contractor in Mexico paid over SPEI today, someone needs pesos in a Mexican bank account today. An international wire to get those pesos there takes 1 to 5 business days. So either you, or your provider, keeps a pile of pesos in Mexico and refills it with slower wires.\n\nThat pile is pre-funding. Banks have run it for decades through nostro and vostro accounts, balances one bank keeps at another in each currency it settles. It's the price of speed on traditional rails. Multiply it by every country you pay into.\n\n## What are the three funding models?\n\nEvery payout provider uses one of these. Ask which one before you sign.\n\n| Model | How it works | Capital tied up | FX exposure |\n| --- | --- | --- | --- |\n| Pre-funded local accounts | You hold a bank account and a balance in each destination currency, and pay out from it | One to two payout cycles per country | Weeks, on every foreign balance |\n| Pre-funded provider balance | You top up a balance with your provider in advance; it pays from its own local liquidity | At least one payout cycle, plus top-up lead time | Low to medium, depending on the balance currency |\n| Funded at send time | You fund each payout when you create it, from a wallet or a virtual USD account | None beyond the payout itself | Minutes, the length of the transfer |\n\nThe middle model is the sneaky one. It gets marketed as \"no pre-funding\" because you don't hold foreign bank accounts. But if the payout draws from a balance you had to top up days earlier, you're still pre-funding. You just moved the float to the provider.\n\n## How does funding at send time actually work?\n\nAt BlindPay, a payout is funded from one of three sources, and none of them is a pre-loaded balance in the destination currency.\n\n**1. A stablecoin wallet you control.** You hold USDC or USDT in your own wallet on a supported network. You request a quote, approve the exact quoted amount on-chain, and create the payout. BlindPay pulls only that amount, only at that moment.\n\n**2. A managed wallet.** BlindPay generates the address and holds the keys, so there's no on-chain approval step. You still decide when funds go in and when each payout goes out.\n\n**3. A virtual USD account.** A [virtual USD account](\u002Fvirtual-accounts) is a US account number in your customer's name. Send dollars to it by ACH, wire, or SWIFT, and each deposit converts to USDC or USDT in the linked wallet. From there, the payout flow is the same.\n\nIn all three, the sequence is:\n\n1. Request a quote. The rate, fees, and exact receive amount are locked for five minutes.\n2. Fund the payout with the quoted stablecoin amount.\n3. Stablecoins move on-chain in seconds.\n4. Local currency lands over Pix, SPEI, ACH, SEPA, or another rail.\n\nNothing sits in Brazil. Nothing sits in Mexico. No destination-currency balance waits for payroll day.\n\n## What's the working-capital math?\n\nAn illustrative example. A staffing company pays contractors every two weeks, about 900,000 USD per cycle:\n\n- Brazil: 450,000 USD\n- Mexico: 270,000 USD\n- Colombia: 180,000 USD\n\n**With pre-funded local accounts.** Top-up wires take up to five business days, so the finance team keeps about 1.5 cycles in each country to be safe. That's roughly 1,350,000 USD sitting in three foreign bank accounts at all times. If that cash could earn 4% in short-term Treasury bills, the company gives up about 54,000 USD a year in yield. And it holds 1.35 million dollars' worth of reais and pesos, so a 3% adverse move in those currencies is a 40,500 USD swing it didn't plan for.\n\n**With a pre-funded provider balance.** Better. No foreign bank accounts. But the balance still has to hold at least one cycle, plus the top-up lead time, so 900,000 USD or more sits idle with the provider.\n\n**Funded at send time.** The treasury keeps its dollars until payout day. On payout day it funds exactly 900,000 USD worth of payouts, each at a quoted rate. Idle capital: zero. FX exposure: minutes.\n\nNow add a fourth country. With pre-funded accounts, that's a new bank relationship, a new buffer, and a new currency position. Funded at send time, it's a new `type` on a bank account. The expansion stops being a treasury project.\n\n## What are the trade-offs?\n\nBeing honest about it. Funding at send time has three constraints:\n\n- **You need the funds on hand when you send.** Stablecoins in the wallet, or a USD deposit that has already landed in the virtual account. USD deposits by ACH or wire can take up to five business days to arrive, so plan the deposit, not the balance. Rail-by-rail timing is in [how long a stablecoin payout takes](\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times).\n- **Quotes expire.** A payout quote is valid for five minutes by default. Create the payout inside the window, or request a new quote.\n- **Self-custodied EVM wallets need an approval.** You approve the quoted amount on-chain before creating the payout. Managed wallets skip this.\n\nNone of these ask you to park capital. They ask you to be ready at the moment of payment, which is what treasury wants anyway.\n\n## What should you ask a provider about pre-funding?\n\nFive questions that expose the funding model fast:\n\n1. **Does a payout draw from a balance I topped up in advance?** If yes, it's pre-funded, whatever the website says.\n2. **Is there a minimum balance, per currency or overall?**\n3. **Who holds the destination-currency liquidity, and when is it sourced?**\n4. **Is the FX quote binding, and for how long?**\n5. **If a payout fails, where do the funds go, and how fast?** At BlindPay, stablecoin refunds return to the originating wallet right away.\n\nGet the answers in writing. For the rest of the evaluation, read [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api), and for how stablecoins sit inside a multi-rail strategy, read [stablecoins in payment orchestration](\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts).\n\n## Where does BlindPay fit?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API built on the funded-at-send-time model. Each payout is funded when you create it, from your own wallet, a managed wallet, or a virtual USD account. Payouts land in local currency over Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and wire in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries.\n\nKYC, KYB, and sanctions screening run inside the API before money moves. Official SDKs cover Node, Python, Go, PHP, and Swift, and [pricing is published](\u002Fpricing).\n\n## What to do next\n\nPull last quarter's payout volume by country and add up the balances you kept in each one. That number is your pre-funding cost. Then run one test payout on a development instance with the [payout quickstart](\u002Fdocs\u002Fquickstart-payout) and see what funding at send time looks like in practice.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5,"description":341},"What does no pre-funding mean in a stablecoin API?","resources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","pjRMNEJOG6jQQEdxcvwR5DGuJklOuU9kExF1MsSzAEw",[370,694,1448,1895,2350,2828,3361,3950,4287,4642,5836,5946,6943,7496,7790,8080,8680,8820,8972,9328,9776,10052,10494,10869,11265,11508,11848,12136,12459,12763,12982,13305,13471],{"id":371,"title":372,"authors":6,"body":373,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":666,"description":667,"extension":342,"faq":668,"howto":6,"isBlog":359,"isChangelog":359,"meta":687,"navigation":362,"path":688,"pillar":359,"products":6,"rawbody":689,"role":6,"seo":690,"seoTitle":691,"stem":692,"thumbnail":6,"updated":6,"__hash__":693},"content\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared.md","AP2 vs ACP vs x402: agent payment protocols compared",{"type":8,"value":374,"toc":658},[375,378,382,460,474,494,498,524,533,537,552,556,565,568,572,581,613,621,625],[11,376,377],{},"Three protocols now compete to answer the same question for AI agents that spend money: AP2 (Google, co-governed with the FIDO Alliance), ACP (OpenAI and Stripe), and x402 (Coinbase, under a Linux Foundation project). Each one confirms an agent had permission to make a purchase. None of them reconcile what actually got spent once the transaction clears, and because stablecoin settlement cannot be undone, that gap turns into an operational problem the moment real money is involved.",[18,379,381],{"id":380},"what-ap2-acp-and-x402-actually-do","What AP2, ACP, and x402 actually do",[39,383,384,400],{},[42,385,386],{},[45,387,388,391,394,397],{},[48,389,390],{},"Protocol",[48,392,393],{},"Backed by",[48,395,396],{},"What it checks",[48,398,399],{},"Settlement rail",[61,401,402,423,441],{},[45,403,404,407,417,420],{},[66,405,406],{},"AP2 (Agent Payments Protocol)",[66,408,409,410,416],{},"Google, ",[136,411,415],{"href":412,"rel":413},"https:\u002F\u002Ffidoalliance.org\u002Ffido-alliance-to-develop-standards-for-trusted-ai-agent-interactions\u002F",[414],"nofollow","FIDO Alliance",", Mastercard",[66,418,419],{},"A chain of signed mandates (Intent, Cart, Payment) proving what a human approved",[66,421,422],{},"Card or stablecoin, protocol-agnostic",[45,424,425,428,435,438],{},[66,426,427],{},"ACP (Agentic Commerce Protocol)",[66,429,430],{},[136,431,434],{"href":432,"rel":433},"https:\u002F\u002Fgithub.com\u002Fagentic-commerce-protocol",[414],"OpenAI, Stripe",[66,436,437],{},"A negotiated cart handed off to a payment token",[66,439,440],{},"Card, processed by Stripe",[45,442,443,446,454,457],{},[66,444,445],{},"x402",[66,447,448,449],{},"Coinbase, ",[136,450,453],{"href":451,"rel":452},"https:\u002F\u002Fwww.coindesk.com\u002Ftech\u002F2026\u002F07\u002F15\u002Fvisa-mastercard-and-ripple-join-the-standard-letting-ai-agents-pay-in-stablecoins",[414],"Linux Foundation, Visa, Mastercard, Ripple",[66,455,456],{},"Nothing beyond payment itself, no signed approval step",[66,458,459],{},"Stablecoin, per HTTP request",[11,461,462,463,467,468,473],{},"AP2's mandates are verifiable credentials Google donated to the FIDO Alliance in April 2026 to make governance vendor-neutral; Mastercard folded in its own Verifiable Intent framework the same month. ACP stays narrow by design, aimed at checkout rather than general agent spend. x402 skips signed approval entirely in favor of speed, and now runs under a ",[136,464,466],{"href":451,"rel":465},[414],"Linux Foundation project backed by Visa, Mastercard, and Ripple",". Visa's Trusted Agent Protocol and Mastercard's Agent Pay run parallel agent-token schemes on the card rails, and both networks ",[136,469,472],{"href":470,"rel":471},"https:\u002F\u002Fwww.digitalcommerce360.com\u002F2026\u002F04\u002F02\u002Fvisa-mastercard-in-agentic-commerce\u002F",[414],"say they intend to converge"," toward supporting whichever protocols win adoption.",[11,475,476,477,481,482,487,488,493],{},"Four mechanisms, one shared checkpoint: authorization. None of them tell you whether thousands of agent transactions still line up with a budget after the fact, flag the ones that broke policy, or produce a record an auditor would accept. Reconciliation is a different job none of the three set out to do, and a finance team ends up building it themselves: matching every agent transaction to a policy, catching what slipped through, and keeping a record that survives an audit. That work looks a lot like what a ",[136,478,480],{"href":479},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api","stablecoin API"," already handles for wallets, conversion, and compliance in one integration, just applied to agent spend instead of human-initiated transfers. EMVCo ",[136,483,486],{"href":484,"rel":485},"https:\u002F\u002Fwww.emvco.com\u002Fnews\u002Femvco-working-on-how-global-specifications-can-support-agentic-payments\u002F",[414],"formed an agentic-payments task force"," in late 2025 to look at the gap, and ",[136,489,492],{"href":490,"rel":491},"https:\u002F\u002Ffdata.global\u002Ffdata-releases-white-paper-on-agentic-fintech-and-write-access-calling-for-a-principles-based-framework-for-the-next-generation-of-open-finance\u002F",[414],"FDATA's July 2026 white paper"," argues the hard problem stopped being authorization some time ago.",[18,495,497],{"id":496},"is-the-agent-payment-volume-real-yet","Is the agent-payment volume real yet?",[11,499,500,501,506,507,511,512,517,518,523],{},"x402's headline numbers ",[136,502,505],{"href":503,"rel":504},"https:\u002F\u002Fwww.coindesk.com\u002Fbusiness\u002F2026\u002F08\u002F23\u002Fcrypto-s-next-billion-users-might-be-ai-agents-and-they-re-paying-with-stablecoins",[414],"look like a working market",": about 165 million cumulative transactions and $50 million by April 2026. Narrow the window and the picture changes. Across the 30 days ending July 2026, the network processed roughly 75 million transactions but only ",[136,508,510],{"href":451,"rel":509},[414],"$24 million in real value",", most of it sub-dollar bot traffic. One ",[136,513,516],{"href":514,"rel":515},"https:\u002F\u002Fwww.coindesk.com\u002Fmarkets\u002F2026\u002F03\u002F11\u002Fcoinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet",[414],"tracker's estimate"," of non-gamified activity lands at around $28,000 a day, and a separate ",[136,519,522],{"href":520,"rel":521},"https:\u002F\u002Fen.cryptonomist.ch\u002F2026\u002F08\u002F25\u002Fagentic-stablecoin-payments-record\u002F",[414],"calculation"," puts agent-to-agent stablecoin volume at roughly 0.0001 percent of total annual stablecoin volume, a figure worth treating as directional since nobody agrees yet on what counts as an \"agent\" transaction.",[11,525,526,527,532],{},"That is thin ground to build a back office around a single protocol. Gartner expects ",[136,528,531],{"href":529,"rel":530},"https:\u002F\u002Fwww.gartner.com\u002Fen\u002Fnewsroom\u002Fpress-releases\u002F2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027",[414],"more than 40 percent of agentic-AI projects to be canceled by the end of 2027",", citing cost, unclear value, and missing risk controls.",[18,534,536],{"id":535},"what-chatgpt-instant-checkout-showed-about-authorization-alone","What ChatGPT Instant Checkout showed about authorization alone",[11,538,539,540,545,546,551],{},"OpenAI launched ",[136,541,544],{"href":542,"rel":543},"https:\u002F\u002Fwww.cnbc.com\u002F2025\u002F09\u002F29\u002Fchatgpt-instant-checkout-etsy-shopify.html",[414],"ChatGPT Instant Checkout"," alongside ACP in September 2025, starting with Etsy and then Shopify merchants including Glossier and SKIMS. By ",[136,547,550],{"href":548,"rel":549},"https:\u002F\u002Fwww.cnbc.com\u002F2026\u002F03\u002F24\u002Fopenai-revamps-shopping-experience-in-chatgpt-after-instant-checkout.html",[414],"March 2026 it was effectively shelved",": fewer than fifteen of Shopify's millions of merchants ever went live, and checkout moved back to the merchant's own site. The mandate signing never broke; stale inventory between the agent's view of a catalog and actual merchant stock, plus sales tax across jurisdictions, is what killed it. A signed mandate confirms an agent was cleared to buy something. It says nothing about whether that thing is in stock, priced correctly, or taxed right, a different failure mode from the reconciliation gap but the same root cause: these protocols check authorization and stop there.",[18,553,555],{"id":554},"the-authorized-but-wrong-purchase-has-no-playbook","The authorized-but-wrong purchase has no playbook",[11,557,558,559,564],{},"Fraud already has a playbook. Amex's ",[136,560,563],{"href":561,"rel":562},"https:\u002F\u002Fwww.worldpay.com\u002Fen\u002Finsights\u002Farticles\u002Fagentic-commerce-liability-is-still-being-written",[414],"Agent Purchase Protection"," shifts liability to Amex when a registered agent's purchase turns out fraudulent, Mastercard's Agent Pay tokens fall under existing card dispute rules, and Visa still calls its own liability terms early and evolving. None of that covers a purchase that was authorized and simply wrong: an agent books the wrong dates, or orders five hundred units instead of fifty because of a rounding error in an agent-to-agent negotiation. The signature checks out, nobody committed fraud, and the human is left holding a purchase that executed exactly as instructed. Both EMVCo's task force and FDATA's paper flag this as an open question, and neither has published a fix.",[11,566,567],{},"A card purchase like that can still be charged back, since the rail is reversible. Stablecoin settlement removes that safety net: once the transaction confirms on-chain, it is done. Most of what agents buy today, an API call, a unit of compute, needs a dispute window about as much as a vending machine does. But it means the call on whether a purchase should happen has to be correct before settlement, since there is no fixing it after.",[18,569,571],{"id":570},"what-to-build-now-regardless-of-which-protocol-wins","What to build now, regardless of which protocol wins",[11,573,574,575,580],{},"Four practices hold up no matter which of AP2, ACP, or x402 ends up dominant in a given ",[136,576,579],{"href":577,"rel":578},"https:\u002F\u002Fblindpay.com\u002Fglobal-payments",[414],"cross-border agent-payment integration",":",[171,582,583,589,595,601],{},[148,584,585,588],{},[119,586,587],{},"Separate negotiation from settlement."," Let the agent reason and assemble a cart with whichever protocol it prefers, then route the payment through a narrow, auditable API surface that does not care which negotiation produced it.",[148,590,591,594],{},[119,592,593],{},"Put spend policy in the API, not the prompt."," A system prompt capping spend is a suggestion an agent can lose track of three tool calls later. A server-side limit on amount, currency, counterparty, or category does not have that failure mode.",[148,596,597,600],{},[119,598,599],{},"Pair every tool call with its settlement receipt."," An idempotency key on the request and a webhook confirmation, both tied to the call that triggered them, let a finance team open one row per transaction and see what started it, what closed it, and whether it passed policy. Without that link, an agent firing the same purchase twice after a timeout looks identical to two legitimate ones, and nobody notices until the statement arrives.",[148,602,603,606,607,612],{},[119,604,605],{},"Put payment where the agent already looks for tools."," MCP's ",[136,608,611],{"href":609,"rel":610},"https:\u002F\u002Fblog.modelcontextprotocol.io\u002Fposts\u002F2026-07-28\u002F",[414],"July 2026 spec update"," added a formal extensions framework, so a payment capability can be exposed as one more discoverable tool instead of a bolt-on.",[11,614,615,616,620],{},"The same discipline, decoupled settlement, server-side policy, a receipt trail, is also what a solid ",[136,617,619],{"href":618},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide","stablecoin payments"," setup needs for human-initiated transfers, which is why agent and human flows can share one infrastructure instead of separate stacks.",[18,622,624],{"id":623},"where-blindpay-fits","Where BlindPay fits",[11,626,627,628,633,634,639,640,645,646,651,652,657],{},"BlindPay's MCP server and Agent Skills expose payments as tools an agent calls directly: quotes, payouts, ",[136,629,632],{"href":630,"rel":631},"https:\u002F\u002Fblindpay.com\u002Fvirtual-accounts",[414],"virtual accounts",", and webhooks, with idempotency and ",[136,635,638],{"href":636,"rel":637},"https:\u002F\u002Fblindpay.com\u002Fcompliance",[414],"reconciliation"," built underneath instead of left for someone to bolt on later. Cross-border transfers that need wire delivery settle as SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations, and corridors like ",[136,641,644],{"href":642,"rel":643},"https:\u002F\u002Fblindpay.com\u002Fusdc-to-brl",[414],"USDC to BRL"," settle the same whether a human or an agent initiated the payment. The ",[136,647,650],{"href":648,"rel":649},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction",[414],"getting started docs"," cover the API surface. ",[136,653,656],{"href":654,"rel":655},"https:\u002F\u002Fblindpay.com\u002Fcontact",[414],"Talk to the team"," if you are building the reconciliation layer for agent payments and want it wired to settlement instead of stapled on after.",{"title":328,"searchDepth":329,"depth":329,"links":659},[660,661,662,663,664,665],{"id":380,"depth":329,"text":381},{"id":496,"depth":329,"text":497},{"id":535,"depth":329,"text":536},{"id":554,"depth":329,"text":555},{"id":570,"depth":329,"text":571},{"id":623,"depth":329,"text":624},"2026-09-02","AP2, ACP, and x402 each verify that an AI agent had permission to spend. What each covers, who backs it, and the reconciliation gap none close.",[669,672,675,678,681,684],{"q":670,"a":671},"What is the difference between AP2, ACP, and x402?","AP2 is Google's protocol, now co-governed with the FIDO Alliance, and it wraps a purchase in a chain of signed mandates so an auditor can check the charge against what a person actually approved. ACP comes from OpenAI and Stripe and is built around checkout: an agent negotiates a cart, then a payment token takes over and Stripe settles it. x402, from Coinbase and now managed by a Linux Foundation project with Visa, Mastercard, and Ripple involved, drops the signed-approval step entirely and lets an agent pay per HTTP request in stablecoin. The card networks run their own agent-token schemes alongside all three. Every one of them answers the same question: was the agent allowed to spend.",{"q":673,"a":674},"Does x402's transaction volume represent real commerce?","Not mostly, no. By April 2026 the network had processed something like 165 million cumulative transactions worth $50 million, but zoom into a single 30-day window in July 2026 and it was 75 million transactions for just $24 million, most of it fractional-cent bot activity rather than anything resembling a merchant sale. One [tracker puts](https:\u002F\u002Fwww.coindesk.com\u002Fmarkets\u002F2026\u002F03\u002F11\u002Fcoinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) genuine, non-gamified volume at around $28,000 a day.",{"q":676,"a":677},"What happens if an AI agent makes an authorized but bad purchase?","No framework covers it yet. Card-network fraud rules and mandate signatures handle spend the agent was never allowed to make. Neither one addresses a purchase that was fully authorized, correctly signed, and still wrong: the wrong dates, the wrong quantity, a rounding error nobody caught. EMVCo has stood up a task force on agentic payments and FDATA published a governance white paper on the exact gap in July 2026. Neither has an answer yet.",{"q":679,"a":680},"Can a stablecoin payment made by an AI agent be reversed?","No. Card networks can freeze or unwind a transaction while a dispute plays out, because a bank sits in the middle of the rail. Stablecoin settlement has no equivalent intermediary: once a transaction confirms on-chain, it stands. That finality is a non-issue for small, well-defined purchases like an API call or a slice of compute. It matters a great deal once real judgment is involved, which means the review has to happen before the agent submits the transaction, not after.",{"q":682,"a":683},"What should a company building agent payments do now?","Split the agent's negotiation step from the actual settlement call, put spend limits in the API layer instead of a system prompt, and pair every tool call with its settlement receipt so idempotency keys and webhook confirmations become the audit trail finance can actually use. That holds regardless of which protocol ends up dominant.",{"q":685,"a":686},"What is MCP's role in agent payments?","MCP is already how an agent discovers and calls tools, so payment does not need a separate channel. It can register as one more tool inside that interface, exposed and negotiated the same way any other capability is, which gives spend limits and receipt logging one obvious place to live instead of a side system someone has to remember to check.",{},"\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared","---\ntitle: \"AP2 vs ACP vs x402: agent payment protocols compared\"\nseoTitle: \"AP2 vs ACP vs x402: agent payment protocols\"\ndescription: \"AP2, ACP, and x402 each verify that an AI agent had permission to spend. What each covers, who backs it, and the reconciliation gap none close.\"\ndate: \"2026-09-02\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is the difference between AP2, ACP, and x402?\"\n    a: \"AP2 is Google's protocol, now co-governed with the FIDO Alliance, and it wraps a purchase in a chain of signed mandates so an auditor can check the charge against what a person actually approved. ACP comes from OpenAI and Stripe and is built around checkout: an agent negotiates a cart, then a payment token takes over and Stripe settles it. x402, from Coinbase and now managed by a Linux Foundation project with Visa, Mastercard, and Ripple involved, drops the signed-approval step entirely and lets an agent pay per HTTP request in stablecoin. The card networks run their own agent-token schemes alongside all three. Every one of them answers the same question: was the agent allowed to spend.\"\n  - q: \"Does x402's transaction volume represent real commerce?\"\n    a: \"Not mostly, no. By April 2026 the network had processed something like 165 million cumulative transactions worth $50 million, but zoom into a single 30-day window in July 2026 and it was 75 million transactions for just $24 million, most of it fractional-cent bot activity rather than anything resembling a merchant sale. One [tracker puts](https:\u002F\u002Fwww.coindesk.com\u002Fmarkets\u002F2026\u002F03\u002F11\u002Fcoinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) genuine, non-gamified volume at around $28,000 a day.\"\n  - q: \"What happens if an AI agent makes an authorized but bad purchase?\"\n    a: \"No framework covers it yet. Card-network fraud rules and mandate signatures handle spend the agent was never allowed to make. Neither one addresses a purchase that was fully authorized, correctly signed, and still wrong: the wrong dates, the wrong quantity, a rounding error nobody caught. EMVCo has stood up a task force on agentic payments and FDATA published a governance white paper on the exact gap in July 2026. Neither has an answer yet.\"\n  - q: \"Can a stablecoin payment made by an AI agent be reversed?\"\n    a: \"No. Card networks can freeze or unwind a transaction while a dispute plays out, because a bank sits in the middle of the rail. Stablecoin settlement has no equivalent intermediary: once a transaction confirms on-chain, it stands. That finality is a non-issue for small, well-defined purchases like an API call or a slice of compute. It matters a great deal once real judgment is involved, which means the review has to happen before the agent submits the transaction, not after.\"\n  - q: \"What should a company building agent payments do now?\"\n    a: \"Split the agent's negotiation step from the actual settlement call, put spend limits in the API layer instead of a system prompt, and pair every tool call with its settlement receipt so idempotency keys and webhook confirmations become the audit trail finance can actually use. That holds regardless of which protocol ends up dominant.\"\n  - q: \"What is MCP's role in agent payments?\"\n    a: \"MCP is already how an agent discovers and calls tools, so payment does not need a separate channel. It can register as one more tool inside that interface, exposed and negotiated the same way any other capability is, which gives spend limits and receipt logging one obvious place to live instead of a side system someone has to remember to check.\"\n---\n\nThree protocols now compete to answer the same question for AI agents that spend money: AP2 (Google, co-governed with the FIDO Alliance), ACP (OpenAI and Stripe), and x402 (Coinbase, under a Linux Foundation project). Each one confirms an agent had permission to make a purchase. None of them reconcile what actually got spent once the transaction clears, and because stablecoin settlement cannot be undone, that gap turns into an operational problem the moment real money is involved.\n\n## What AP2, ACP, and x402 actually do\n\n| Protocol | Backed by | What it checks | Settlement rail |\n|---|---|---|---|\n| AP2 (Agent Payments Protocol) | Google, [FIDO Alliance](https:\u002F\u002Ffidoalliance.org\u002Ffido-alliance-to-develop-standards-for-trusted-ai-agent-interactions\u002F), Mastercard | A chain of signed mandates (Intent, Cart, Payment) proving what a human approved | Card or stablecoin, protocol-agnostic |\n| ACP (Agentic Commerce Protocol) | [OpenAI, Stripe](https:\u002F\u002Fgithub.com\u002Fagentic-commerce-protocol) | A negotiated cart handed off to a payment token | Card, processed by Stripe |\n| x402 | Coinbase, [Linux Foundation, Visa, Mastercard, Ripple](https:\u002F\u002Fwww.coindesk.com\u002Ftech\u002F2026\u002F07\u002F15\u002Fvisa-mastercard-and-ripple-join-the-standard-letting-ai-agents-pay-in-stablecoins) | Nothing beyond payment itself, no signed approval step | Stablecoin, per HTTP request |\n\nAP2's mandates are verifiable credentials Google donated to the FIDO Alliance in April 2026 to make governance vendor-neutral; Mastercard folded in its own Verifiable Intent framework the same month. ACP stays narrow by design, aimed at checkout rather than general agent spend. x402 skips signed approval entirely in favor of speed, and now runs under a [Linux Foundation project backed by Visa, Mastercard, and Ripple](https:\u002F\u002Fwww.coindesk.com\u002Ftech\u002F2026\u002F07\u002F15\u002Fvisa-mastercard-and-ripple-join-the-standard-letting-ai-agents-pay-in-stablecoins). Visa's Trusted Agent Protocol and Mastercard's Agent Pay run parallel agent-token schemes on the card rails, and both networks [say they intend to converge](https:\u002F\u002Fwww.digitalcommerce360.com\u002F2026\u002F04\u002F02\u002Fvisa-mastercard-in-agentic-commerce\u002F) toward supporting whichever protocols win adoption.\n\nFour mechanisms, one shared checkpoint: authorization. None of them tell you whether thousands of agent transactions still line up with a budget after the fact, flag the ones that broke policy, or produce a record an auditor would accept. Reconciliation is a different job none of the three set out to do, and a finance team ends up building it themselves: matching every agent transaction to a policy, catching what slipped through, and keeping a record that survives an audit. That work looks a lot like what a [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) already handles for wallets, conversion, and compliance in one integration, just applied to agent spend instead of human-initiated transfers. EMVCo [formed an agentic-payments task force](https:\u002F\u002Fwww.emvco.com\u002Fnews\u002Femvco-working-on-how-global-specifications-can-support-agentic-payments\u002F) in late 2025 to look at the gap, and [FDATA's July 2026 white paper](https:\u002F\u002Ffdata.global\u002Ffdata-releases-white-paper-on-agentic-fintech-and-write-access-calling-for-a-principles-based-framework-for-the-next-generation-of-open-finance\u002F) argues the hard problem stopped being authorization some time ago.\n\n## Is the agent-payment volume real yet?\n\nx402's headline numbers [look like a working market](https:\u002F\u002Fwww.coindesk.com\u002Fbusiness\u002F2026\u002F08\u002F23\u002Fcrypto-s-next-billion-users-might-be-ai-agents-and-they-re-paying-with-stablecoins): about 165 million cumulative transactions and $50 million by April 2026. Narrow the window and the picture changes. Across the 30 days ending July 2026, the network processed roughly 75 million transactions but only [$24 million in real value](https:\u002F\u002Fwww.coindesk.com\u002Ftech\u002F2026\u002F07\u002F15\u002Fvisa-mastercard-and-ripple-join-the-standard-letting-ai-agents-pay-in-stablecoins), most of it sub-dollar bot traffic. One [tracker's estimate](https:\u002F\u002Fwww.coindesk.com\u002Fmarkets\u002F2026\u002F03\u002F11\u002Fcoinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) of non-gamified activity lands at around $28,000 a day, and a separate [calculation](https:\u002F\u002Fen.cryptonomist.ch\u002F2026\u002F08\u002F25\u002Fagentic-stablecoin-payments-record\u002F) puts agent-to-agent stablecoin volume at roughly 0.0001 percent of total annual stablecoin volume, a figure worth treating as directional since nobody agrees yet on what counts as an \"agent\" transaction.\n\nThat is thin ground to build a back office around a single protocol. Gartner expects [more than 40 percent of agentic-AI projects to be canceled by the end of 2027](https:\u002F\u002Fwww.gartner.com\u002Fen\u002Fnewsroom\u002Fpress-releases\u002F2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027), citing cost, unclear value, and missing risk controls.\n\n## What ChatGPT Instant Checkout showed about authorization alone\n\nOpenAI launched [ChatGPT Instant Checkout](https:\u002F\u002Fwww.cnbc.com\u002F2025\u002F09\u002F29\u002Fchatgpt-instant-checkout-etsy-shopify.html) alongside ACP in September 2025, starting with Etsy and then Shopify merchants including Glossier and SKIMS. By [March 2026 it was effectively shelved](https:\u002F\u002Fwww.cnbc.com\u002F2026\u002F03\u002F24\u002Fopenai-revamps-shopping-experience-in-chatgpt-after-instant-checkout.html): fewer than fifteen of Shopify's millions of merchants ever went live, and checkout moved back to the merchant's own site. The mandate signing never broke; stale inventory between the agent's view of a catalog and actual merchant stock, plus sales tax across jurisdictions, is what killed it. A signed mandate confirms an agent was cleared to buy something. It says nothing about whether that thing is in stock, priced correctly, or taxed right, a different failure mode from the reconciliation gap but the same root cause: these protocols check authorization and stop there.\n\n## The authorized-but-wrong purchase has no playbook\n\nFraud already has a playbook. Amex's [Agent Purchase Protection](https:\u002F\u002Fwww.worldpay.com\u002Fen\u002Finsights\u002Farticles\u002Fagentic-commerce-liability-is-still-being-written) shifts liability to Amex when a registered agent's purchase turns out fraudulent, Mastercard's Agent Pay tokens fall under existing card dispute rules, and Visa still calls its own liability terms early and evolving. None of that covers a purchase that was authorized and simply wrong: an agent books the wrong dates, or orders five hundred units instead of fifty because of a rounding error in an agent-to-agent negotiation. The signature checks out, nobody committed fraud, and the human is left holding a purchase that executed exactly as instructed. Both EMVCo's task force and FDATA's paper flag this as an open question, and neither has published a fix.\n\nA card purchase like that can still be charged back, since the rail is reversible. Stablecoin settlement removes that safety net: once the transaction confirms on-chain, it is done. Most of what agents buy today, an API call, a unit of compute, needs a dispute window about as much as a vending machine does. But it means the call on whether a purchase should happen has to be correct before settlement, since there is no fixing it after.\n\n## What to build now, regardless of which protocol wins\n\nFour practices hold up no matter which of AP2, ACP, or x402 ends up dominant in a given [cross-border agent-payment integration](https:\u002F\u002Fblindpay.com\u002Fglobal-payments):\n\n- **Separate negotiation from settlement.** Let the agent reason and assemble a cart with whichever protocol it prefers, then route the payment through a narrow, auditable API surface that does not care which negotiation produced it.\n- **Put spend policy in the API, not the prompt.** A system prompt capping spend is a suggestion an agent can lose track of three tool calls later. A server-side limit on amount, currency, counterparty, or category does not have that failure mode.\n- **Pair every tool call with its settlement receipt.** An idempotency key on the request and a webhook confirmation, both tied to the call that triggered them, let a finance team open one row per transaction and see what started it, what closed it, and whether it passed policy. Without that link, an agent firing the same purchase twice after a timeout looks identical to two legitimate ones, and nobody notices until the statement arrives.\n- **Put payment where the agent already looks for tools.** MCP's [July 2026 spec update](https:\u002F\u002Fblog.modelcontextprotocol.io\u002Fposts\u002F2026-07-28\u002F) added a formal extensions framework, so a payment capability can be exposed as one more discoverable tool instead of a bolt-on.\n\nThe same discipline, decoupled settlement, server-side policy, a receipt trail, is also what a solid [stablecoin payments](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide) setup needs for human-initiated transfers, which is why agent and human flows can share one infrastructure instead of separate stacks.\n\n## Where BlindPay fits\n\nBlindPay's MCP server and Agent Skills expose payments as tools an agent calls directly: quotes, payouts, [virtual accounts](https:\u002F\u002Fblindpay.com\u002Fvirtual-accounts), and webhooks, with idempotency and [reconciliation](https:\u002F\u002Fblindpay.com\u002Fcompliance) built underneath instead of left for someone to bolt on later. Cross-border transfers that need wire delivery settle as SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations, and corridors like [USDC to BRL](https:\u002F\u002Fblindpay.com\u002Fusdc-to-brl) settle the same whether a human or an agent initiated the payment. The [getting started docs](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction) cover the API surface. [Talk to the team](https:\u002F\u002Fblindpay.com\u002Fcontact) if you are building the reconciliation layer for agent payments and want it wired to settlement instead of stapled on after.\n",{"title":372,"description":667},"AP2 vs ACP vs x402: agent payment protocols","resources\u002Fmore\u002Fagent-payment-protocols-compared","fjpTIAMvBiemsXFiwTA3o_11IRh-Kos5_6KzofeKS1c",{"id":695,"title":696,"authors":6,"body":697,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":1417,"description":1418,"extension":342,"faq":1419,"howto":6,"isBlog":359,"isChangelog":359,"meta":1441,"navigation":362,"path":1442,"pillar":359,"products":6,"rawbody":1443,"role":6,"seo":1444,"seoTitle":1445,"stem":1446,"thumbnail":6,"updated":6,"__hash__":1447},"content\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026.md","Best stablecoin payment platforms for fintech in 2026: a US comparison",{"type":8,"value":698,"toc":1398},[699,702,705,709,712,749,757,761,774,966,971,974,978,985,989,992,996,999,1003,1006,1010,1013,1017,1020,1024,1027,1038,1048,1051,1065,1073,1077,1080,1184,1187,1195,1199,1202,1213,1229,1235,1246,1256,1263,1267,1270,1276,1287,1293,1299,1318,1322,1325,1347,1351,1393],[11,700,701],{},"The best stablecoin payment platform for a US fintech in 2026 is the one that is licensed where you operate, reaches the countries your customers are in, settles when your product needs it to, and does not make your team rebuild what already works. No single provider wins on all four. This guide compares seven of them against those criteria so an engineering lead and a compliance lead can shortlist in one sitting.",[11,703,704],{},"It is written by BlindPay, which is one of the seven. The comparison holds BlindPay to the same table as everyone else, and the section on where each provider fits says plainly where a competitor is the better choice.",[18,706,708],{"id":707},"what-makes-a-stablecoin-payments-api-production-ready-in-2026","What makes a stablecoin payments API production-ready in 2026?",[11,710,711],{},"A stablecoin payments API is production-ready for a fintech when it clears five bars. Treat them as eligibility criteria: a provider that misses one is not a candidate, no matter how good the docs are.",[145,713,714,720,726,737,743],{},[148,715,716,719],{},[119,717,718],{},"Licensing you can verify."," In the US that means FinCEN registration as a Money Services Business with a public NMLS number, plus state money transmitter licenses, exemptions, or a licensed partner structure, published state by state. Abroad it means the local equivalent: Brazil's Central Bank authorization for virtual asset providers, an EMI license in Europe, and so on. If the status page does not exist, the answer is no.",[148,721,722,725],{},[119,723,724],{},"A quote before commitment."," The API returns the FX rate, the spread, and the payout fee as separate numbers before the payment executes. Blended rates hide costs and make reconciliation guesswork.",[148,727,728,731,732,736],{},[119,729,730],{},"Verification before movement."," KYC on the receiver, KYB on the business, sanctions screening, and receiving-account checks run before money leaves. On-chain transfers are final, so the checks are the recall window. ",[136,733,735],{"href":734},"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible","Reversibility"," is a design property, not a support ticket.",[148,738,739,742],{},[119,740,741],{},"A full payment lifecycle in the API."," Unique IDs, status per payment, webhooks on every change, the transaction hash, and for wires the UETR and MT103. Without this, a finance team reconciles by hand.",[148,744,745,748],{},[119,746,747],{},"Rails and currencies that match your customers."," Multi-chain support matters less than most comparison pages suggest. What matters is whether the platform can put local currency into a bank account in the countries you serve.",[11,750,751,752,756],{},"Documentation quality and sandbox fidelity sit just under these five. A ",[136,753,755],{"href":754},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","sandbox that hides production failure modes"," costs more time than bad docs.",[18,758,760],{"id":759},"how-do-the-top-stablecoin-payment-platforms-for-fintech-compare","How do the top stablecoin payment platforms for fintech compare?",[11,762,763,764,768,769,773],{},"The seven platforms below are the ones US fintechs most often shortlist. Rails, currencies, and fees change often, so treat the table as a map of each provider's center of gravity and confirm current details on their sites. The ",[136,765,767],{"href":766},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026","ten-provider API comparison"," goes wider, and the ",[136,770,772],{"href":771},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","provider types guide"," explains the custody and licensing models behind the table.",[39,775,776,798],{},[42,777,778],{},[45,779,780,783,786,789,792,795],{},[48,781,782],{},"Provider",[48,784,785],{},"Best for",[48,787,788],{},"Fiat rails",[48,790,791],{},"US licensing posture",[48,793,794],{},"Custody",[48,796,797],{},"Pricing",[61,799,800,825,849,873,896,919,943],{},[45,801,802,804,807,810,817,820],{},[66,803,300],{},[66,805,806],{},"Fintechs paying into Latin America and needing itemized quotes without pre-funding",[66,808,809],{},"Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO)",[66,811,812,813],{},"FinCEN MSB (NMLS #2745309), state MTLs in progress, ",[136,814,816],{"href":815},"\u002Flicenses","published",[66,818,819],{},"Non-custodial for the business",[66,821,822],{},[136,823,824],{"href":307},"Flat plus percentage, published",[45,826,827,834,837,840,843,846],{},[66,828,829],{},[136,830,833],{"href":831,"rel":832},"https:\u002F\u002Fwww.bridge.xyz",[414],"Bridge",[66,835,836],{},"Teams already on Stripe wanting stablecoin orchestration and issuance",[66,838,839],{},"ACH, wire, SEPA",[66,841,842],{},"US money transmission through Stripe entities",[66,844,845],{},"Provider custody",[66,847,848],{},"Percentage per conversion",[45,850,851,858,861,864,867,870],{},[66,852,853],{},[136,854,857],{"href":855,"rel":856},"https:\u002F\u002Fwww.circle.com",[414],"Circle",[66,859,860],{},"Holding, minting, and redeeming USDC at scale",[66,862,863],{},"Bank wires",[66,865,866],{},"Issuer, positioned for GENIUS Act licensing",[66,868,869],{},"Issuer or self-custody",[66,871,872],{},"Volume-based, enterprise",[45,874,875,882,885,888,891,893],{},[66,876,877],{},[136,878,881],{"href":879,"rel":880},"https:\u002F\u002Fzerohash.com",[414],"Zero Hash",[66,883,884],{},"Embedding crypto and stablecoin settlement behind a US brokerage-style product",[66,886,887],{},"ACH, wire",[66,889,890],{},"US MTLs, broker-dealer adjacent",[66,892,845],{},[66,894,895],{},"Enterprise quotes",[45,897,898,905,908,911,914,916],{},[66,899,900],{},[136,901,904],{"href":902,"rel":903},"https:\u002F\u002Fwww.bvnk.com",[414],"BVNK",[66,906,907],{},"European and UK fintechs with some US flow",[66,909,910],{},"SEPA, Faster Payments, SWIFT",[66,912,913],{},"EMI licenses in Europe, VASP registrations",[66,915,845],{},[66,917,918],{},"Enterprise tiers",[45,920,921,928,931,934,937,940],{},[66,922,923],{},[136,924,927],{"href":925,"rel":926},"https:\u002F\u002Fwww.fireblocks.com",[414],"Fireblocks",[66,929,930],{},"Fintechs that hold their own licenses and want custody tooling",[66,932,933],{},"On-chain only",[66,935,936],{},"Tooling for your licenses",[66,938,939],{},"Self-custody via MPC",[66,941,942],{},"Platform fee",[45,944,945,952,955,958,961,963],{},[66,946,947],{},[136,948,951],{"href":949,"rel":950},"https:\u002F\u002Fspherepay.co",[414],"Sphere",[66,953,954],{},"Developer-first teams needing ACH, SEPA, and Pix from one API",[66,956,957],{},"ACH, wire, SEPA, Pix",[66,959,960],{},"Provider-run compliance",[66,962,845],{},[66,964,965],{},"Per-transaction",[967,968,970],"h3",{"id":969},"_1-blindpay","1. BlindPay",[11,972,973],{},"Built for the \"we hold dollars, our customers need local currency\" problem. One API converts USDC or USDT into BRL, MXN, ARS, COP, USD, or EUR and pays out over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on the wire leg. Quotes itemize spread and payout fee. No pre-funding: the business funds each payout when it makes it. Virtual accounts turn incoming USD into stablecoins for pay-ins. Deepest coverage is the Americas. If most of your volume is US-to-US or intra-Europe, another provider on this list fits better.",[967,975,977],{"id":976},"_2-bridge","2. Bridge",[11,979,980,981,227],{},"Stripe acquired Bridge in 2025, and the product now sits inside Stripe's stack. Strong for orchestration between stablecoins and USD or EUR, for issuing a branded stablecoin, and for teams that want Stripe-grade docs and support. Local rails outside the US and Europe are thinner. The natural pick when Stripe is already your processor. Teams moving the other way use the ",[136,982,984],{"href":983},"\u002Fprompts\u002Fmigrate-from-bridge","Bridge migration prompt",[967,986,988],{"id":987},"_3-circle","3. Circle",[11,990,991],{},"Circle issues USDC and offers mint and redeem APIs, wallets, and cross-chain transfer. It is the right choice when the job is treasury-scale USDC operations rather than paying people in local currency. Circle does not run Pix or SPEI payouts, so most fintechs pair it with a payout provider.",[967,993,995],{"id":994},"_4-zero-hash","4. Zero Hash",[11,997,998],{},"A US-licensed infrastructure provider that lets a fintech embed crypto trading and stablecoin settlement behind its own brand. Strong on US state licensing and on the compliance paperwork a US bank partner will ask for. Cross-border local-currency payout is not the core product.",[967,1000,1002],{"id":1001},"_5-bvnk","5. BVNK",[11,1004,1005],{},"A European infrastructure provider with EMI licensing and deep SEPA and Faster Payments coverage, plus SWIFT. A good match for a fintech whose flows are mostly Europe and UK with some US and global settlement. US state licensing is not its home turf.",[967,1007,1009],{"id":1008},"_6-fireblocks","6. Fireblocks",[11,1011,1012],{},"Custody and wallet infrastructure, not a payment platform. If your fintech holds its own money transmitter licenses and wants to run stablecoin operations on its own rails, Fireblocks gives you MPC custody, policy engines, and connectivity to 60+ networks. You bring the compliance and the fiat rails. Several providers on this list run on it underneath.",[967,1014,1016],{"id":1015},"_7-sphere","7. Sphere",[11,1018,1019],{},"A developer-oriented API that combines ACH, wire, SEPA, and Pix with on-chain settlement and built-in KYC and KYB. Well suited to teams that want to ship a first corridor quickly with minimal enterprise process. Corridor depth and wire tooling are lighter than the larger providers.",[18,1021,1023],{"id":1022},"what-us-compliance-and-regulatory-considerations-apply-to-stablecoin-payments","What US compliance and regulatory considerations apply to stablecoin payments?",[11,1025,1026],{},"US compliance for stablecoin payments has two layers, and a fintech has to check both.",[11,1028,1029,1032,1033,1037],{},[119,1030,1031],{},"The issuer layer"," is governed by the GENIUS Act, signed in July 2025. It requires payment stablecoin issuers to hold 1:1 reserves in cash and short-term Treasuries, to be licensed federally or under a substantially similar state regime, and to publish reserve disclosures. Treasury published its implementing proposal on August 17, 2026, with comments due October 19, 2026, and the licensing requirement is expected to take effect January 18, 2027. After that date, a fintech should only move stablecoins from licensed issuers. USDC and PYUSD are positioned for this. Foreign-issued stablecoins face additional conditions. The ",[136,1034,1036],{"href":1035},"\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026","regulation tracker"," follows the rulemaking as it lands.",[11,1039,1040,1043,1044,1047],{},[119,1041,1042],{},"The platform layer"," is money transmission law. Any platform that receives and sends value on your behalf needs FinCEN registration as a Money Services Business and either state money transmitter licenses, an exemption, or a licensed partner structure, state by state. This is the part a bank partner or auditor will ask about first. BlindPay publishes its state-by-state status on the ",[136,1045,1046],{"href":815},"licenses page","; Bridge, Zero Hash, and Circle publish theirs. Any provider that cannot produce an NMLS number and a state map is a risk you are choosing to carry.",[11,1049,1050],{},"Two practical checks cover most of the exposure:",[171,1052,1053,1059],{},[148,1054,1055,1058],{},[119,1056,1057],{},"Who runs KYC and KYB, and where does the data live?"," If the provider runs it inside the API flow, your product inherits the checks. If not, you are building them.",[148,1060,1061,1064],{},[119,1062,1063],{},"What happens on a sanctions hit or a travel rule request?"," The answer should be a specific process with a specific response time, not \"we would look into it.\"",[11,1066,1067,1068,1072],{},"The choice between USDC and USDT interacts with all of this. USDC is easier to defend to a US compliance committee; USDT has deeper liquidity in emerging-market off-ramps. The ",[136,1069,1071],{"href":1070},"\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments","USDC vs USDT comparison"," covers the tradeoff.",[18,1074,1076],{"id":1075},"real-time-payments-vs-ach-how-do-settlement-speed-and-cost-compare","Real-time payments vs ACH: how do settlement speed and cost compare?",[11,1078,1079],{},"ACH is the rail most US fintechs already run on, so it is the honest baseline. The comparison below also includes RTP and FedNow because they are the domestic instant alternative.",[39,1081,1082,1101],{},[42,1083,1084],{},[45,1085,1086,1089,1092,1095,1098],{},[48,1087,1088],{},"Rail",[48,1090,1091],{},"Settlement",[48,1093,1094],{},"Hours",[48,1096,1097],{},"Reach",[48,1099,1100],{},"Typical cost",[61,1102,1103,1120,1136,1152,1168],{},[45,1104,1105,1108,1111,1114,1117],{},[66,1106,1107],{},"Standard ACH",[66,1109,1110],{},"1 to 3 business days",[66,1112,1113],{},"Banking windows",[66,1115,1116],{},"US only",[66,1118,1119],{},"Cents per item",[45,1121,1122,1125,1128,1131,1133],{},[66,1123,1124],{},"Same-day ACH",[66,1126,1127],{},"Same business day",[66,1129,1130],{},"Three windows per day",[66,1132,1116],{},[66,1134,1135],{},"Under a dollar per item",[45,1137,1138,1141,1144,1147,1150],{},[66,1139,1140],{},"RTP \u002F FedNow",[66,1142,1143],{},"Seconds",[66,1145,1146],{},"24\u002F7",[66,1148,1149],{},"US only, participating banks",[66,1151,1135],{},[45,1153,1154,1157,1160,1162,1165],{},[66,1155,1156],{},"International wire",[66,1158,1159],{},"1 to 5 business days",[66,1161,1113],{},[66,1163,1164],{},"Global",[66,1166,1167],{},"$25 to $50 plus 2 to 5 percent FX",[45,1169,1170,1173,1176,1178,1181],{},[66,1171,1172],{},"Stablecoin plus local payout",[66,1174,1175],{},"Minutes",[66,1177,1146],{},[66,1179,1180],{},"Wherever the provider has rails",[66,1182,1183],{},"Flat fee plus sub-percent to low single digit spread",[11,1185,1186],{},"The pattern is clear once the table is side by side. For a domestic US payment with no time pressure, ACH is the cheapest option and there is no reason to change it. For a domestic payment that has to land now, RTP or FedNow beats stablecoins on cost if both banks participate. For anything that crosses a border, stablecoin settlement is faster than a wire by days and cheaper by a wide margin, and it runs on weekends.",[11,1188,1189,1190,1194],{},"The business consequence is working capital. A payout that lands in minutes does not need to be sent early, so the fintech does not need money parked in destination accounts. Providers that require pre-funding erase this advantage; ask directly. The ",[136,1191,1193],{"href":1192},"\u002Fblog\u002Forchestrating-payment-rails-leaders","orchestration piece"," covers how leadership teams decide which flows go on which rail.",[18,1196,1198],{"id":1197},"what-are-the-b2b-infrastructure-use-cases-for-global-payments","What are the B2B infrastructure use cases for global payments?",[11,1200,1201],{},"The fintechs getting the most from stablecoin platforms in 2026 are not selling \"crypto.\" They are using stablecoin rails underneath a product that looks ordinary to the customer.",[11,1203,1204,1207,1208,1212],{},[119,1205,1206],{},"Cross-border supplier and vendor settlement."," A US platform paying suppliers in Mexico or Brazil funds in USD, converts to stablecoins, and pays out over SPEI or Pix in minutes. The supplier sees a local transfer. The ",[136,1209,1211],{"href":1210},"\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","stablecoin vs SWIFT comparison"," works the numbers.",[11,1214,1215,1218,1219,1223,1224,1228],{},[119,1216,1217],{},"Contractor and marketplace payouts."," Payroll platforms and marketplaces use the same flow to pay thousands of small balances daily instead of batching wires biweekly. The ",[136,1220,1222],{"href":1221},"\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","contractor payroll guide"," and the ",[136,1225,1227],{"href":1226},"\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","marketplace payouts guide"," cover the operational details.",[11,1230,1231,1234],{},[119,1232,1233],{},"Embedded pay-ins."," A fintech gives each customer a virtual US account. Incoming ACH or wire deposits convert to stablecoins automatically, which the fintech can hold, move, or pay out. This is the \"global account\" feature neobanks now ship.",[11,1236,1237,1240,1241,1245],{},[119,1238,1239],{},"Treasury movement."," Moving balances between entities or countries on a Sunday, at a quoted rate, without a correspondent bank chain. Settlement finality matters here; the ",[136,1242,1244],{"href":1243},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","SLA and finality guide"," explains what each provider promises.",[11,1247,1248,1251,1252,1255],{},[119,1249,1250],{},"Agent-driven payments."," A newer case: AI agents that need to pay for services or settle with other agents use stablecoin rails because they are programmable and always on. The ",[136,1253,1254],{"href":688},"agent payment protocol comparison"," maps the standards.",[11,1257,1258,1259,1262],{},"Across all five, the ",[136,1260,1261],{"href":299},"global payments"," architecture is the same: dollars in, stablecoin across, local currency out, with compliance inside the flow.",[18,1264,1266],{"id":1265},"how-should-a-fintech-evaluate-and-integrate-a-stablecoin-payment-platform","How should a fintech evaluate and integrate a stablecoin payment platform?",[11,1268,1269],{},"A four-week evaluation is enough to reach a confident decision. Longer usually means the criteria were not written down.",[11,1271,1272,1275],{},[119,1273,1274],{},"Week 1: eligibility."," Apply the five bars above to every candidate. Collect the NMLS number, the state map, the corridor list, and the published pricing. Cut anyone missing one.",[11,1277,1278,1281,1282,1286],{},[119,1279,1280],{},"Week 2: sandbox."," Integrate the shortlist's sandbox for one real flow, such as a single payout to one corridor. Wire up ",[136,1283,1285],{"href":1284},"\u002Fprompts\u002Fintegrate-webhooks","webhooks"," from day one so reconciliation is tested, not assumed. Force the failure paths: rejected receiving account, compliance hold, rail outage.",[11,1288,1289,1292],{},[119,1290,1291],{},"Week 3: production pilot."," Move one small live corridor with real money and real customers. Measure landed amount against quoted amount, time to landing, and support tickets generated. Compare against the same corridor on your current rail.",[11,1294,1295,1298],{},[119,1296,1297],{},"Week 4: decision."," Score on the five bars plus pilot results. Weight licensing and reconciliation above cost; cost differences between compliant providers are smaller than the cost of a compliance gap or a manual reconciliation process.",[11,1300,1301,1302,1304,1305,1304,1309,1313,1314,227],{},"Integration shape is consistent across providers: create a receiver with KYC data, request a quote, execute the payment, listen for the webhook, reconcile. Keep your processor for card acceptance and route the flows stablecoins do better through the new API. Migrating from another stablecoin provider follows the same path; the prompt library has guides for ",[136,1303,833],{"href":983},", ",[136,1306,1308],{"href":1307},"\u002Fprompts\u002Fmigrate-from-conduit","Conduit",[136,1310,1312],{"href":1311},"\u002Fprompts\u002Fmigrate-from-crossmint","Crossmint",", and ",[136,1315,1317],{"href":1316},"\u002Fprompts\u002Fmigrate-from-swift-wires","manual wire processes",[18,1319,1321],{"id":1320},"how-do-you-get-started-with-stablecoin-payments-for-a-fintech","How do you get started with stablecoin payments for a fintech?",[11,1323,1324],{},"Pick the one corridor where your current rail hurts most. For most US fintechs that is a payout into Latin America or a supplier settlement that currently goes by wire. Run that corridor through the four-week evaluation above with two or three providers from the table.",[11,1326,1327,1328,1332,1333,1337,1338,1341,1342,1346],{},"If the corridor is into the Americas and the requirement is a quoted rate, no pre-funding, and compliance run inside the API, BlindPay is built for that case: ",[136,1329,1331],{"href":648,"rel":1330},[414],"start in the sandbox",", check ",[136,1334,1336],{"href":1335},"\u002Fcoverage","coverage"," and ",[136,1339,1340],{"href":307},"pricing",", or ",[136,1343,1345],{"href":1344},"\u002Fcontact","contact BlindPay"," with the corridor. If the corridor is intra-Europe or the job is USDC treasury operations, start with BVNK or Circle instead.",[18,1348,1350],{"id":1349},"methodology-and-sources","Methodology and sources",[11,1352,1353,1354,1304,1358,1304,1362,1304,1366,1304,1370,1304,1374,1378,1379,1381,1382,1223,1387,1392],{},"Provider capabilities summarized from public materials as of September 2026: ",[136,1355,1357],{"href":831,"rel":1356},[414],"bridge.xyz",[136,1359,1361],{"href":855,"rel":1360},[414],"circle.com",[136,1363,1365],{"href":879,"rel":1364},[414],"zerohash.com",[136,1367,1369],{"href":902,"rel":1368},[414],"bvnk.com",[136,1371,1373],{"href":925,"rel":1372},[414],"fireblocks.com",[136,1375,1377],{"href":949,"rel":1376},[414],"spherepay.co",", and BlindPay's own documentation and ",[136,1380,1046],{"href":815},". GENIUS Act timeline from the ",[136,1383,1386],{"href":1384,"rel":1385},"https:\u002F\u002Fhome.treasury.gov\u002Fnews\u002Fpress-releases\u002Fsb0605",[414],"US Treasury's notice of proposed rulemaking",[136,1388,1391],{"href":1389,"rel":1390},"https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2026\u002Fbulletin-2026-3.html",[414],"OCC bulletin",". ACH timing from Nacha's same-day ACH schedule.",[11,1394,1395],{},[324,1396,1397],{},"This article is general information, not legal, tax, or financial advice.",{"title":328,"searchDepth":329,"depth":329,"links":1399},[1400,1401,1411,1412,1413,1414,1415,1416],{"id":707,"depth":329,"text":708},{"id":759,"depth":329,"text":760,"children":1402},[1403,1405,1406,1407,1408,1409,1410],{"id":969,"depth":1404,"text":970},3,{"id":976,"depth":1404,"text":977},{"id":987,"depth":1404,"text":988},{"id":994,"depth":1404,"text":995},{"id":1001,"depth":1404,"text":1002},{"id":1008,"depth":1404,"text":1009},{"id":1015,"depth":1404,"text":1016},{"id":1022,"depth":329,"text":1023},{"id":1075,"depth":329,"text":1076},{"id":1197,"depth":329,"text":1198},{"id":1265,"depth":329,"text":1266},{"id":1320,"depth":329,"text":1321},{"id":1349,"depth":329,"text":1350},"2026-09-07","Seven stablecoin payment platforms compared for US fintechs in 2026: production readiness, compliance, settlement speed against ACH, and evaluation.",[1420,1423,1426,1429,1432,1435,1438],{"q":1421,"a":1422},"What is a stablecoin payment platform and how does it differ from a traditional payment processor?","A stablecoin payment platform is an API that moves value using dollar-pegged tokens like USDC or USDT and converts between those tokens and bank money. A traditional processor like Stripe moves money through card networks and ACH. The stablecoin platform settles in minutes at any hour and reaches countries where card and ACH rails do not, while the processor handles consumer checkout, disputes, and subscriptions. Most fintechs run both.",{"q":1424,"a":1425},"Which stablecoin APIs are compliant with US fintech regulations in 2026?","Compliance in the US comes from two layers. The stablecoin issuer must be licensed under the GENIUS Act, which Circle and Paxos are positioned for. The platform moving the money must be registered with FinCEN as a Money Services Business and hold or be exempt from state money transmitter licenses. Bridge, Zero Hash, and BlindPay publish their registration status. Ask every provider for its NMLS number and state coverage map before signing.",{"q":1427,"a":1428},"How do stablecoin payments compare to ACH payments for real-time settlement?","Standard ACH settles in one to three business days and same-day ACH in a few hours during banking windows, both domestic only. Stablecoin transfers settle in seconds to minutes, 24\u002F7, and can be converted to local currency abroad. For a US-to-US payment with no urgency, ACH is cheaper. For anything cross-border, off-hours, or time-sensitive, stablecoin rails win.",{"q":1430,"a":1431},"Can a stablecoin API integrate with existing payment infrastructure like Stripe or QuickBooks Payments?","Yes. Stablecoin APIs sit beside your processor, not in place of it. The usual pattern is to keep Stripe for card acceptance and route payouts, cross-border settlement, or treasury moves through the stablecoin API, then reconcile both through webhooks into your ledger or accounting tool. Bridge is owned by Stripe and is the tightest fit if you are already deep in that ecosystem.",{"q":1433,"a":1434},"What are the transaction fees for stablecoin payments versus traditional global payment methods?","An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread and intermediary deductions. Stablecoin platforms charge a flat fee per payout plus a sub-percent to low single digit spread on conversion, and the on-chain transfer itself costs cents. The gap is largest on cross-border payments into Latin America, Africa, and Asia, and smallest on domestic US transfers.",{"q":1436,"a":1437},"How do stablecoin platforms handle cross-border or global payments for fintech startups?","The platform holds or receives stablecoins, converts them to the destination currency, and pays out over the local rail: Pix in Brazil, SPEI in Mexico, SEPA in Europe, or a SWIFT wire where nothing faster exists. The recipient gets local currency in a bank account and never touches a wallet. Coverage varies a lot by provider, so match the corridor list to where your customers are.",{"q":1439,"a":1440},"What payment history and reporting features should a stablecoin API offer fintech companies?","At minimum: a unique ID and status per payment, webhooks for every state change, an on-chain transaction hash, the FX rate and fees itemized per transaction, and an export or API endpoint that lets your finance team reconcile against bank statements. For wires, UETR tracking and MT103 confirmations. If the provider cannot show a payment's full lifecycle in one API call, reconciliation will be manual.",{"author":361},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026","---\ntitle: \"Best stablecoin payment platforms for fintech in 2026: a US comparison\"\nseoTitle: \"Best stablecoin payment platforms for fintech\"\ndescription: \"Seven stablecoin payment platforms compared for US fintechs in 2026: production readiness, compliance, settlement speed against ACH, and evaluation.\"\ndate: \"2026-09-07\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a stablecoin payment platform and how does it differ from a traditional payment processor?\"\n    a: \"A stablecoin payment platform is an API that moves value using dollar-pegged tokens like USDC or USDT and converts between those tokens and bank money. A traditional processor like Stripe moves money through card networks and ACH. The stablecoin platform settles in minutes at any hour and reaches countries where card and ACH rails do not, while the processor handles consumer checkout, disputes, and subscriptions. Most fintechs run both.\"\n  - q: \"Which stablecoin APIs are compliant with US fintech regulations in 2026?\"\n    a: \"Compliance in the US comes from two layers. The stablecoin issuer must be licensed under the GENIUS Act, which Circle and Paxos are positioned for. The platform moving the money must be registered with FinCEN as a Money Services Business and hold or be exempt from state money transmitter licenses. Bridge, Zero Hash, and BlindPay publish their registration status. Ask every provider for its NMLS number and state coverage map before signing.\"\n  - q: \"How do stablecoin payments compare to ACH payments for real-time settlement?\"\n    a: \"Standard ACH settles in one to three business days and same-day ACH in a few hours during banking windows, both domestic only. Stablecoin transfers settle in seconds to minutes, 24\u002F7, and can be converted to local currency abroad. For a US-to-US payment with no urgency, ACH is cheaper. For anything cross-border, off-hours, or time-sensitive, stablecoin rails win.\"\n  - q: \"Can a stablecoin API integrate with existing payment infrastructure like Stripe or QuickBooks Payments?\"\n    a: \"Yes. Stablecoin APIs sit beside your processor, not in place of it. The usual pattern is to keep Stripe for card acceptance and route payouts, cross-border settlement, or treasury moves through the stablecoin API, then reconcile both through webhooks into your ledger or accounting tool. Bridge is owned by Stripe and is the tightest fit if you are already deep in that ecosystem.\"\n  - q: \"What are the transaction fees for stablecoin payments versus traditional global payment methods?\"\n    a: \"An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread and intermediary deductions. Stablecoin platforms charge a flat fee per payout plus a sub-percent to low single digit spread on conversion, and the on-chain transfer itself costs cents. The gap is largest on cross-border payments into Latin America, Africa, and Asia, and smallest on domestic US transfers.\"\n  - q: \"How do stablecoin platforms handle cross-border or global payments for fintech startups?\"\n    a: \"The platform holds or receives stablecoins, converts them to the destination currency, and pays out over the local rail: Pix in Brazil, SPEI in Mexico, SEPA in Europe, or a SWIFT wire where nothing faster exists. The recipient gets local currency in a bank account and never touches a wallet. Coverage varies a lot by provider, so match the corridor list to where your customers are.\"\n  - q: \"What payment history and reporting features should a stablecoin API offer fintech companies?\"\n    a: \"At minimum: a unique ID and status per payment, webhooks for every state change, an on-chain transaction hash, the FX rate and fees itemized per transaction, and an export or API endpoint that lets your finance team reconcile against bank statements. For wires, UETR tracking and MT103 confirmations. If the provider cannot show a payment's full lifecycle in one API call, reconciliation will be manual.\"\n---\n\nThe best stablecoin payment platform for a US fintech in 2026 is the one that is licensed where you operate, reaches the countries your customers are in, settles when your product needs it to, and does not make your team rebuild what already works. No single provider wins on all four. This guide compares seven of them against those criteria so an engineering lead and a compliance lead can shortlist in one sitting.\n\nIt is written by BlindPay, which is one of the seven. The comparison holds BlindPay to the same table as everyone else, and the section on where each provider fits says plainly where a competitor is the better choice.\n\n## What makes a stablecoin payments API production-ready in 2026?\n\nA stablecoin payments API is production-ready for a fintech when it clears five bars. Treat them as eligibility criteria: a provider that misses one is not a candidate, no matter how good the docs are.\n\n1. **Licensing you can verify.** In the US that means FinCEN registration as a Money Services Business with a public NMLS number, plus state money transmitter licenses, exemptions, or a licensed partner structure, published state by state. Abroad it means the local equivalent: Brazil's Central Bank authorization for virtual asset providers, an EMI license in Europe, and so on. If the status page does not exist, the answer is no.\n2. **A quote before commitment.** The API returns the FX rate, the spread, and the payout fee as separate numbers before the payment executes. Blended rates hide costs and make reconciliation guesswork.\n3. **Verification before movement.** KYC on the receiver, KYB on the business, sanctions screening, and receiving-account checks run before money leaves. On-chain transfers are final, so the checks are the recall window. [Reversibility](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) is a design property, not a support ticket.\n4. **A full payment lifecycle in the API.** Unique IDs, status per payment, webhooks on every change, the transaction hash, and for wires the UETR and MT103. Without this, a finance team reconciles by hand.\n5. **Rails and currencies that match your customers.** Multi-chain support matters less than most comparison pages suggest. What matters is whether the platform can put local currency into a bank account in the countries you serve.\n\nDocumentation quality and sandbox fidelity sit just under these five. A [sandbox that hides production failure modes](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) costs more time than bad docs.\n\n## How do the top stablecoin payment platforms for fintech compare?\n\nThe seven platforms below are the ones US fintechs most often shortlist. Rails, currencies, and fees change often, so treat the table as a map of each provider's center of gravity and confirm current details on their sites. The [ten-provider API comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026) goes wider, and the [provider types guide](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026) explains the custody and licensing models behind the table.\n\n| Provider | Best for | Fiat rails | US licensing posture | Custody | Pricing |\n| --- | --- | --- | --- | --- | --- |\n| BlindPay | Fintechs paying into Latin America and needing itemized quotes without pre-funding | Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO) | FinCEN MSB (NMLS #2745309), state MTLs in progress, [published](\u002Flicenses) | Non-custodial for the business | [Flat plus percentage, published](\u002Fpricing) |\n| [Bridge](https:\u002F\u002Fwww.bridge.xyz) | Teams already on Stripe wanting stablecoin orchestration and issuance | ACH, wire, SEPA | US money transmission through Stripe entities | Provider custody | Percentage per conversion |\n| [Circle](https:\u002F\u002Fwww.circle.com) | Holding, minting, and redeeming USDC at scale | Bank wires | Issuer, positioned for GENIUS Act licensing | Issuer or self-custody | Volume-based, enterprise |\n| [Zero Hash](https:\u002F\u002Fzerohash.com) | Embedding crypto and stablecoin settlement behind a US brokerage-style product | ACH, wire | US MTLs, broker-dealer adjacent | Provider custody | Enterprise quotes |\n| [BVNK](https:\u002F\u002Fwww.bvnk.com) | European and UK fintechs with some US flow | SEPA, Faster Payments, SWIFT | EMI licenses in Europe, VASP registrations | Provider custody | Enterprise tiers |\n| [Fireblocks](https:\u002F\u002Fwww.fireblocks.com) | Fintechs that hold their own licenses and want custody tooling | On-chain only | Tooling for your licenses | Self-custody via MPC | Platform fee |\n| [Sphere](https:\u002F\u002Fspherepay.co) | Developer-first teams needing ACH, SEPA, and Pix from one API | ACH, wire, SEPA, Pix | Provider-run compliance | Provider custody | Per-transaction |\n\n### 1. BlindPay\n\nBuilt for the \"we hold dollars, our customers need local currency\" problem. One API converts USDC or USDT into BRL, MXN, ARS, COP, USD, or EUR and pays out over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on the wire leg. Quotes itemize spread and payout fee. No pre-funding: the business funds each payout when it makes it. Virtual accounts turn incoming USD into stablecoins for pay-ins. Deepest coverage is the Americas. If most of your volume is US-to-US or intra-Europe, another provider on this list fits better.\n\n### 2. Bridge\n\nStripe acquired Bridge in 2025, and the product now sits inside Stripe's stack. Strong for orchestration between stablecoins and USD or EUR, for issuing a branded stablecoin, and for teams that want Stripe-grade docs and support. Local rails outside the US and Europe are thinner. The natural pick when Stripe is already your processor. Teams moving the other way use the [Bridge migration prompt](\u002Fprompts\u002Fmigrate-from-bridge).\n\n### 3. Circle\n\nCircle issues USDC and offers mint and redeem APIs, wallets, and cross-chain transfer. It is the right choice when the job is treasury-scale USDC operations rather than paying people in local currency. Circle does not run Pix or SPEI payouts, so most fintechs pair it with a payout provider.\n\n### 4. Zero Hash\n\nA US-licensed infrastructure provider that lets a fintech embed crypto trading and stablecoin settlement behind its own brand. Strong on US state licensing and on the compliance paperwork a US bank partner will ask for. Cross-border local-currency payout is not the core product.\n\n### 5. BVNK\n\nA European infrastructure provider with EMI licensing and deep SEPA and Faster Payments coverage, plus SWIFT. A good match for a fintech whose flows are mostly Europe and UK with some US and global settlement. US state licensing is not its home turf.\n\n### 6. Fireblocks\n\nCustody and wallet infrastructure, not a payment platform. If your fintech holds its own money transmitter licenses and wants to run stablecoin operations on its own rails, Fireblocks gives you MPC custody, policy engines, and connectivity to 60+ networks. You bring the compliance and the fiat rails. Several providers on this list run on it underneath.\n\n### 7. Sphere\n\nA developer-oriented API that combines ACH, wire, SEPA, and Pix with on-chain settlement and built-in KYC and KYB. Well suited to teams that want to ship a first corridor quickly with minimal enterprise process. Corridor depth and wire tooling are lighter than the larger providers.\n\n## What US compliance and regulatory considerations apply to stablecoin payments?\n\nUS compliance for stablecoin payments has two layers, and a fintech has to check both.\n\n**The issuer layer** is governed by the GENIUS Act, signed in July 2025. It requires payment stablecoin issuers to hold 1:1 reserves in cash and short-term Treasuries, to be licensed federally or under a substantially similar state regime, and to publish reserve disclosures. Treasury published its implementing proposal on August 17, 2026, with comments due October 19, 2026, and the licensing requirement is expected to take effect January 18, 2027. After that date, a fintech should only move stablecoins from licensed issuers. USDC and PYUSD are positioned for this. Foreign-issued stablecoins face additional conditions. The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) follows the rulemaking as it lands.\n\n**The platform layer** is money transmission law. Any platform that receives and sends value on your behalf needs FinCEN registration as a Money Services Business and either state money transmitter licenses, an exemption, or a licensed partner structure, state by state. This is the part a bank partner or auditor will ask about first. BlindPay publishes its state-by-state status on the [licenses page](\u002Flicenses); Bridge, Zero Hash, and Circle publish theirs. Any provider that cannot produce an NMLS number and a state map is a risk you are choosing to carry.\n\nTwo practical checks cover most of the exposure:\n\n- **Who runs KYC and KYB, and where does the data live?** If the provider runs it inside the API flow, your product inherits the checks. If not, you are building them.\n- **What happens on a sanctions hit or a travel rule request?** The answer should be a specific process with a specific response time, not \"we would look into it.\"\n\nThe choice between USDC and USDT interacts with all of this. USDC is easier to defend to a US compliance committee; USDT has deeper liquidity in emerging-market off-ramps. The [USDC vs USDT comparison](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) covers the tradeoff.\n\n## Real-time payments vs ACH: how do settlement speed and cost compare?\n\nACH is the rail most US fintechs already run on, so it is the honest baseline. The comparison below also includes RTP and FedNow because they are the domestic instant alternative.\n\n| Rail | Settlement | Hours | Reach | Typical cost |\n| --- | --- | --- | --- | --- |\n| Standard ACH | 1 to 3 business days | Banking windows | US only | Cents per item |\n| Same-day ACH | Same business day | Three windows per day | US only | Under a dollar per item |\n| RTP \u002F FedNow | Seconds | 24\u002F7 | US only, participating banks | Under a dollar per item |\n| International wire | 1 to 5 business days | Banking windows | Global | $25 to $50 plus 2 to 5 percent FX |\n| Stablecoin plus local payout | Minutes | 24\u002F7 | Wherever the provider has rails | Flat fee plus sub-percent to low single digit spread |\n\nThe pattern is clear once the table is side by side. For a domestic US payment with no time pressure, ACH is the cheapest option and there is no reason to change it. For a domestic payment that has to land now, RTP or FedNow beats stablecoins on cost if both banks participate. For anything that crosses a border, stablecoin settlement is faster than a wire by days and cheaper by a wide margin, and it runs on weekends.\n\nThe business consequence is working capital. A payout that lands in minutes does not need to be sent early, so the fintech does not need money parked in destination accounts. Providers that require pre-funding erase this advantage; ask directly. The [orchestration piece](\u002Fblog\u002Forchestrating-payment-rails-leaders) covers how leadership teams decide which flows go on which rail.\n\n## What are the B2B infrastructure use cases for global payments?\n\nThe fintechs getting the most from stablecoin platforms in 2026 are not selling \"crypto.\" They are using stablecoin rails underneath a product that looks ordinary to the customer.\n\n**Cross-border supplier and vendor settlement.** A US platform paying suppliers in Mexico or Brazil funds in USD, converts to stablecoins, and pays out over SPEI or Pix in minutes. The supplier sees a local transfer. The [stablecoin vs SWIFT comparison](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments) works the numbers.\n\n**Contractor and marketplace payouts.** Payroll platforms and marketplaces use the same flow to pay thousands of small balances daily instead of batching wires biweekly. The [contractor payroll guide](\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors) and the [marketplace payouts guide](\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam) cover the operational details.\n\n**Embedded pay-ins.** A fintech gives each customer a virtual US account. Incoming ACH or wire deposits convert to stablecoins automatically, which the fintech can hold, move, or pay out. This is the \"global account\" feature neobanks now ship.\n\n**Treasury movement.** Moving balances between entities or countries on a Sunday, at a quoted rate, without a correspondent bank chain. Settlement finality matters here; the [SLA and finality guide](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality) explains what each provider promises.\n\n**Agent-driven payments.** A newer case: AI agents that need to pay for services or settle with other agents use stablecoin rails because they are programmable and always on. The [agent payment protocol comparison](\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared) maps the standards.\n\nAcross all five, the [global payments](\u002Fglobal-payments) architecture is the same: dollars in, stablecoin across, local currency out, with compliance inside the flow.\n\n## How should a fintech evaluate and integrate a stablecoin payment platform?\n\nA four-week evaluation is enough to reach a confident decision. Longer usually means the criteria were not written down.\n\n**Week 1: eligibility.** Apply the five bars above to every candidate. Collect the NMLS number, the state map, the corridor list, and the published pricing. Cut anyone missing one.\n\n**Week 2: sandbox.** Integrate the shortlist's sandbox for one real flow, such as a single payout to one corridor. Wire up [webhooks](\u002Fprompts\u002Fintegrate-webhooks) from day one so reconciliation is tested, not assumed. Force the failure paths: rejected receiving account, compliance hold, rail outage.\n\n**Week 3: production pilot.** Move one small live corridor with real money and real customers. Measure landed amount against quoted amount, time to landing, and support tickets generated. Compare against the same corridor on your current rail.\n\n**Week 4: decision.** Score on the five bars plus pilot results. Weight licensing and reconciliation above cost; cost differences between compliant providers are smaller than the cost of a compliance gap or a manual reconciliation process.\n\nIntegration shape is consistent across providers: create a receiver with KYC data, request a quote, execute the payment, listen for the webhook, reconcile. Keep your processor for card acceptance and route the flows stablecoins do better through the new API. Migrating from another stablecoin provider follows the same path; the prompt library has guides for [Bridge](\u002Fprompts\u002Fmigrate-from-bridge), [Conduit](\u002Fprompts\u002Fmigrate-from-conduit), [Crossmint](\u002Fprompts\u002Fmigrate-from-crossmint), and [manual wire processes](\u002Fprompts\u002Fmigrate-from-swift-wires).\n\n## How do you get started with stablecoin payments for a fintech?\n\nPick the one corridor where your current rail hurts most. For most US fintechs that is a payout into Latin America or a supplier settlement that currently goes by wire. Run that corridor through the four-week evaluation above with two or three providers from the table.\n\nIf the corridor is into the Americas and the requirement is a quoted rate, no pre-funding, and compliance run inside the API, BlindPay is built for that case: [start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction), check [coverage](\u002Fcoverage) and [pricing](\u002Fpricing), or [contact BlindPay](\u002Fcontact) with the corridor. If the corridor is intra-Europe or the job is USDC treasury operations, start with BVNK or Circle instead.\n\n## Methodology and sources\n\nProvider capabilities summarized from public materials as of September 2026: [bridge.xyz](https:\u002F\u002Fwww.bridge.xyz), [circle.com](https:\u002F\u002Fwww.circle.com), [zerohash.com](https:\u002F\u002Fzerohash.com), [bvnk.com](https:\u002F\u002Fwww.bvnk.com), [fireblocks.com](https:\u002F\u002Fwww.fireblocks.com), [spherepay.co](https:\u002F\u002Fspherepay.co), and BlindPay's own documentation and [licenses page](\u002Flicenses). GENIUS Act timeline from the [US Treasury's notice of proposed rulemaking](https:\u002F\u002Fhome.treasury.gov\u002Fnews\u002Fpress-releases\u002Fsb0605) and the [OCC bulletin](https:\u002F\u002Fwww.occ.gov\u002Fnews-issuances\u002Fbulletins\u002F2026\u002Fbulletin-2026-3.html). ACH timing from Nacha's same-day ACH schedule.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":696,"description":1418},"Best stablecoin payment platforms for fintech","resources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026","JkRftMMA1MeRCcWsRDIc0yXValtxBX_dEQJymAMu33U",{"id":1449,"title":1450,"authors":6,"body":1451,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":1873,"description":1874,"extension":342,"faq":1875,"howto":6,"isBlog":359,"isChangelog":359,"meta":1888,"navigation":362,"path":771,"pillar":359,"products":6,"rawbody":1889,"role":6,"seo":1890,"seoTitle":1891,"stem":1892,"thumbnail":6,"updated":1893,"__hash__":1894},"content\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026.md","Best stablecoin payment providers in 2026: how to choose",{"type":8,"value":1452,"toc":1862},[1453,1456,1465,1469,1487,1493,1496,1500,1707,1713,1717,1769,1773,1776,1781,1785,1791,1795,1798,1802,1805,1809,1827,1829,1858],[11,1454,1455],{},"A stablecoin payment provider moves money between digital dollars and bank accounts on behalf of a business: collecting from customers, paying out to people, or both. Choosing one comes down to three questions: which direction your money moves, which countries it moves between, and whose regulatory license covers the flow.",[11,1457,1458,1459,1464],{},"The category is crowded because the volume is real: public trackers such as ",[136,1460,1463],{"href":1461,"rel":1462},"https:\u002F\u002Fdefillama.com\u002Fstablecoins",[414],"DeFiLlama"," put circulating stablecoin supply above 200 billion dollars, and payment-focused usage keeps growing as businesses replace slow cross-border wires. This guide maps the provider types, compares ten options, and gives you the checklist we would use ourselves.",[18,1466,1468],{"id":1467},"what-are-the-four-types-of-stablecoin-payment-provider","What are the four types of stablecoin payment provider?",[11,1470,1471,1474,1475,1478,1479,1482,1483,1486],{},[119,1472,1473],{},"Payout and collection networks"," (BlindPay, BVNK) connect stablecoins to local bank rails, so a transfer that starts as USDC ends as reais, pesos, or dollars in a bank account. ",[119,1476,1477],{},"Issuer platforms"," (Circle) sit at the source: they mint and redeem the stablecoin itself and offer APIs around it. ",[119,1480,1481],{},"Orchestration layers"," (Bridge, Crossmint) wrap issuance, conversion, and wallets into developer products. ",[119,1484,1485],{},"Custody and infrastructure platforms"," (Fireblocks, Zero Hash) give regulated building blocks that businesses assemble under their own or the provider's licenses.",[11,1488,1489,1490,227],{},"Most buying confusion comes from comparing across types. A gateway that is excellent at merchant checkout may have no payout rails in Latin America, and an issuer platform will not deliver Pix. Start from your money flow, then compare within the right type. For the underlying mechanics, see ",[136,1491,1492],{"href":618},"stablecoin payments explained",[11,1494,1495],{},"Two concrete scenarios show the split. A European marketplace collecting card payments and paying 5,000 sellers across Latin America needs a payout network with local rails, and its gateway choice is almost irrelevant to that problem. A US neobank adding a \"buy USDC\" button needs a licensed infrastructure platform like Zero Hash, and payout corridors are irrelevant to that one. Write your scenario down first; the provider type usually falls out of the sentence.",[18,1497,1499],{"id":1498},"how-do-the-main-providers-compare","How do the main providers compare?",[39,1501,1502,1519],{},[42,1503,1504],{},[45,1505,1506,1508,1510,1513,1516],{},[48,1507,782],{},[48,1509,785],{},[48,1511,1512],{},"Directions",[48,1514,1515],{},"Settlement rails",[48,1517,1518],{},"Licensing posture",[61,1520,1521,1537,1556,1575,1593,1612,1632,1651,1669,1687],{},[45,1522,1523,1525,1528,1531,1534],{},[66,1524,300],{},[66,1526,1527],{},"Stablecoin-to-local-fiat payouts, Americas",[66,1529,1530],{},"Payout and collection",[66,1532,1533],{},"Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO), on-chain",[66,1535,1536],{},"MSB registrations, compliance in the API",[45,1538,1539,1544,1547,1550,1553],{},[66,1540,1541],{},[136,1542,857],{"href":855,"rel":1543},[414],[66,1545,1546],{},"Issuer-level USDC access",[66,1548,1549],{},"Mint, redeem, transfer",[66,1551,1552],{},"On-chain, US wires",[66,1554,1555],{},"US and EU issuer licenses",[45,1557,1558,1563,1566,1569,1572],{},[66,1559,1560],{},[136,1561,833],{"href":831,"rel":1562},[414],[66,1564,1565],{},"Stripe-ecosystem orchestration",[66,1567,1568],{},"Pay-in and payout",[66,1570,1571],{},"On-chain, ACH, wire, SEPA",[66,1573,1574],{},"US money transmission (Stripe)",[45,1576,1577,1582,1585,1587,1590],{},[66,1578,1579],{},[136,1580,904],{"href":902,"rel":1581},[414],[66,1583,1584],{},"High-volume EU merchants",[66,1586,1568],{},[66,1588,1589],{},"SEPA, Faster Payments, SWIFT, on-chain",[66,1591,1592],{},"EU EMI, VASP registrations",[45,1594,1595,1600,1603,1606,1609],{},[66,1596,1597],{},[136,1598,927],{"href":925,"rel":1599},[414],[66,1601,1602],{},"Institutional self-custody",[66,1604,1605],{},"Infrastructure only",[66,1607,1608],{},"On-chain",[66,1610,1611],{},"Tooling under your licenses",[45,1613,1614,1620,1623,1626,1629],{},[66,1615,1616],{},[136,1617,1312],{"href":1618,"rel":1619},"https:\u002F\u002Fwww.crossmint.com",[414],[66,1621,1622],{},"Consumer apps, embedded wallets",[66,1624,1625],{},"Pay-in focused",[66,1627,1628],{},"On-chain, cards",[66,1630,1631],{},"Provider-managed onboarding",[45,1633,1634,1639,1642,1645,1648],{},[66,1635,1636],{},[136,1637,881],{"href":879,"rel":1638},[414],[66,1640,1641],{},"US fintechs embedding crypto",[66,1643,1644],{},"Both, US-centric",[66,1646,1647],{},"On-chain, ACH, wire",[66,1649,1650],{},"US MTLs",[45,1652,1653,1659,1662,1664,1667],{},[66,1654,1655],{},[136,1656,1308],{"href":1657,"rel":1658},"https:\u002F\u002Fconduitpay.com",[414],[66,1660,1661],{},"Emerging-market corridors (Africa, Asia, LatAm)",[66,1663,1530],{},[66,1665,1666],{},"Pix, SPEI, Interac, mobile money, on-chain",[66,1668,960],{},[45,1670,1671,1676,1679,1681,1684],{},[66,1672,1673],{},[136,1674,951],{"href":949,"rel":1675},[414],[66,1677,1678],{},"On\u002Foff-ramps with virtual accounts",[66,1680,1568],{},[66,1682,1683],{},"ACH, wire, SEPA, Pix, on-chain",[66,1685,1686],{},"KYC, KYB, sanctions in the API",[45,1688,1689,1696,1699,1701,1704],{},[66,1690,1691],{},[136,1692,1695],{"href":1693,"rel":1694},"https:\u002F\u002Fborderless.xyz",[414],"Borderless",[66,1697,1698],{},"Broad coverage via partner network",[66,1700,1530],{},[66,1702,1703],{},"Local rails via licensed partners",[66,1705,1706],{},"Locally licensed partner institutions",[11,1708,1709,1710,227],{},"Capabilities shift quarter to quarter. Confirm rails, corridors, and fees on each provider's site before shortlisting; for BlindPay the current numbers are on the ",[136,1711,1712],{"href":307},"pricing page",[18,1714,1716],{"id":1715},"which-questions-decide-the-choice","Which questions decide the choice?",[145,1718,1719,1725,1734,1743,1749,1763],{},[148,1720,1721,1724],{},[119,1722,1723],{},"Direction."," Collecting from customers, paying suppliers and contractors, or moving your own treasury? Payout depth and pay-in depth rarely live in the same provider.",[148,1726,1727,1730,1731,1733],{},[119,1728,1729],{},"Corridors."," List the exact country pairs. A provider's marketing map and its production corridors differ; ask for delivered-amount quotes on your top three corridors and check ",[136,1732,1336],{"href":1335}," explicitly.",[148,1735,1736,1739,1740,1742],{},[119,1737,1738],{},"Compliance ownership."," Who runs KYC and KYB, who screens sanctions, who files travel rule data? Built-in compliance shortens your roadmap; bring-your-own-license platforms give control at the cost of obligations. The ",[136,1741,1036],{"href":1035}," summarizes what applies where.",[148,1744,1745,1748],{},[119,1746,1747],{},"Custody."," If holding funds with the provider is unacceptable, your shortlist shrinks to self-custody infrastructure plus a payout network that pulls from your wallet.",[148,1750,1751,1754,1755,1337,1758,1762],{},[119,1752,1753],{},"All-in cost."," Request the delivered amount for a fixed test payment, say 1,000 USDC to BRL, and compare across providers. Spread hides in the FX rate, not the fee line. Our live ",[136,1756,644],{"href":1757},"\u002Fusdc-to-brl",[136,1759,1761],{"href":1760},"\u002Fusdt-to-brl","USDT to BRL"," pages show quoted rates before you commit.",[148,1764,1765,1768],{},[119,1766,1767],{},"Time to first payment."," Ask each provider how long KYB review takes at your entity type. Onboarding, not engineering, is the usual critical path.",[18,1770,1772],{"id":1771},"what-does-onboarding-with-a-provider-actually-involve","What does onboarding with a provider actually involve?",[11,1774,1775],{},"Every regulated provider gates live payments behind business verification, and this step, not the API integration, sets your launch date. Expect to provide incorporation documents, proof of address, ownership structure down to ultimate beneficial owners (each owner passes individual KYC), a description of your business model, and often expected volumes and source of funds. Clean, consistent documents move through review in days; mismatched entity names or opaque ownership add weeks.",[11,1777,1778,1779,227],{},"Two practical tips. Run onboarding with two providers in parallel rather than serially, so a slow review does not stall the project. And ask each provider what triggers re-review later, such as volume jumps or new corridors, so growth does not surprise your operations team. What verification covers and why is explained in the provider-agnostic terms of our ",[136,1780,1036],{"href":1035},[18,1782,1784],{"id":1783},"how-do-pay-ins-and-payouts-differ-operationally","How do pay-ins and payouts differ operationally?",[11,1786,1787,1788,1790],{},"Collecting stablecoins is mostly a reconciliation problem: matching what arrived to who owes what, which is why ",[136,1789,632],{"href":138}," with per-customer account details beat shared wallet addresses for B2B collections. Paying out is mostly a verification problem: local rails reject transfers when the recipient name and tax ID do not match the receiving account, Pix being the strictest example, so payout quality depends on how well the provider validates recipient data before sending. Providers optimized for one direction routinely underperform in the other; weight your evaluation by where your volume actually is.",[18,1792,1794],{"id":1793},"where-do-these-options-fall-short","Where do these options fall short?",[11,1796,1797],{},"Every provider on the list has a gap. Issuer platforms stop at the dollar leg. EU-licensed gateways thin out outside Europe. US-centric platforms often have no emerging-market rails at all. Payout networks, BlindPay included, do not give you card acquiring or issuer-level mint and redeem. If most of your flow is domestic US ACH between US entities, a stablecoin provider adds a conversion step you may not need. And no provider removes the obligation to understand your own regulatory position, especially if you touch customer funds.",[18,1799,1801],{"id":1800},"how-should-you-run-a-pilot-before-committing","How should you run a pilot before committing?",[11,1803,1804],{},"Shortlist two providers, then run the same real payment through both within the same week, since FX rates move. A useful pilot has four measurements: the delivered amount for a fixed input (the true price), time from API call to bank credit (the true speed), the number of manual touches required (the true operational cost), and how the provider handled one deliberately imperfect payment, such as a slightly mismatched recipient name (the true failure behavior). The last one matters most in production: providers look identical on the happy path and completely different when a payout needs review, retry, or return. Insist on running the pilot in the corridor you care about, not the provider's best corridor.",[18,1806,1808],{"id":1807},"when-is-blindpay-the-right-provider","When is BlindPay the right provider?",[11,1810,1811,1812,1815,1816,1818,1819,1822,1823,1826],{},"BlindPay is built for one job done well: a business holds USDC or USDT and needs people paid in local currency, compliantly, through ",[136,1813,1814],{"href":299},"one API",". Payouts go out over Pix, SPEI, ACH, and SWIFT, with wires executed as POBO\u002FCOBO transfers carrying UETR tracking codes and MT103 confirmations; ",[136,1817,632],{"href":138}," handle the reverse direction by converting incoming bank transfers into stablecoins. KYC, KYB, sanctions screening, and travel rule handling run inside the flow, and FX is quoted before you commit. Depth is strongest in the Americas: Brazil, Mexico, the US, Argentina, Colombia. If that matches your corridor list, ",[136,1820,1821],{"href":1344},"talk to us","; if you need merchant card checkout or European EMI rails, one of the providers above is the better fit, and the comparison in ",[136,1824,1825],{"href":766},"best stablecoin APIs in 2026"," goes deeper on each.",[18,1828,1350],{"id":1349},[11,1830,1831,1832,1304,1835,1304,1838,1304,1841,1304,1844,1304,1848,1851,1852,1857],{},"Provider positioning summarized from public materials as of August 2026: ",[136,1833,1361],{"href":855,"rel":1834},[414],[136,1836,1357],{"href":831,"rel":1837},[414],[136,1839,1369],{"href":902,"rel":1840},[414],[136,1842,1373],{"href":925,"rel":1843},[414],[136,1845,1847],{"href":1618,"rel":1846},[414],"crossmint.com",[136,1849,1365],{"href":879,"rel":1850},[414],". Rail behavior from operator documentation, including the ",[136,1853,1856],{"href":1854,"rel":1855},"https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en",[414],"Banco Central do Brasil's Pix overview",". Supply figures from public dashboards such as DeFiLlama.",[11,1859,1860],{},[324,1861,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":1863},[1864,1865,1866,1867,1868,1869,1870,1871,1872],{"id":1467,"depth":329,"text":1468},{"id":1498,"depth":329,"text":1499},{"id":1715,"depth":329,"text":1716},{"id":1771,"depth":329,"text":1772},{"id":1783,"depth":329,"text":1784},{"id":1793,"depth":329,"text":1794},{"id":1800,"depth":329,"text":1801},{"id":1807,"depth":329,"text":1808},{"id":1349,"depth":329,"text":1350},"2026-08-15","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.",[1876,1879,1882,1885],{"q":1877,"a":1878},"What is a stablecoin payment provider?","A stablecoin payment provider is a regulated company that moves money between stablecoins and bank accounts for businesses: accepting stablecoin payments, paying out stablecoins as local currency, or both, through an API or dashboard.",{"q":1880,"a":1881},"What is the difference between a stablecoin payment gateway and a payout provider?","A gateway collects payments from your customers and settles to you. A payout provider sends money the other way, converting your stablecoins into local currency in someone else's bank account. Some providers do both, but most are stronger in one direction.",{"q":1883,"a":1884},"How much do stablecoin payment providers charge?","Most charge a percentage per conversion, sometimes with a flat fee per payout, plus an FX spread on non-USD currencies. Compare the amount delivered to the recipient rather than the quoted fee, because a low fee can hide a wide spread.",{"q":1886,"a":1887},"Are stablecoin payment providers regulated?","Serious providers operate as registered money services businesses, EMIs, or VASPs depending on the market, and run KYC, KYB, and sanctions screening before money moves. Check registrations for each country you need, not just the provider's home market.",{"author":361},"---\ntitle: \"Best stablecoin payment providers in 2026: how to choose\"\nseoTitle: \"Best stablecoin payment providers in 2026\"\ndescription: \"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.\"\ndate: \"2026-08-15\"\nupdated: \"2026-08-24\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a stablecoin payment provider?\"\n    a: \"A stablecoin payment provider is a regulated company that moves money between stablecoins and bank accounts for businesses: accepting stablecoin payments, paying out stablecoins as local currency, or both, through an API or dashboard.\"\n  - q: \"What is the difference between a stablecoin payment gateway and a payout provider?\"\n    a: \"A gateway collects payments from your customers and settles to you. A payout provider sends money the other way, converting your stablecoins into local currency in someone else's bank account. Some providers do both, but most are stronger in one direction.\"\n  - q: \"How much do stablecoin payment providers charge?\"\n    a: \"Most charge a percentage per conversion, sometimes with a flat fee per payout, plus an FX spread on non-USD currencies. Compare the amount delivered to the recipient rather than the quoted fee, because a low fee can hide a wide spread.\"\n  - q: \"Are stablecoin payment providers regulated?\"\n    a: \"Serious providers operate as registered money services businesses, EMIs, or VASPs depending on the market, and run KYC, KYB, and sanctions screening before money moves. Check registrations for each country you need, not just the provider's home market.\"\n---\n\nA stablecoin payment provider moves money between digital dollars and bank accounts on behalf of a business: collecting from customers, paying out to people, or both. Choosing one comes down to three questions: which direction your money moves, which countries it moves between, and whose regulatory license covers the flow.\n\nThe category is crowded because the volume is real: public trackers such as [DeFiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins) put circulating stablecoin supply above 200 billion dollars, and payment-focused usage keeps growing as businesses replace slow cross-border wires. This guide maps the provider types, compares ten options, and gives you the checklist we would use ourselves.\n\n## What are the four types of stablecoin payment provider?\n\n**Payout and collection networks** (BlindPay, BVNK) connect stablecoins to local bank rails, so a transfer that starts as USDC ends as reais, pesos, or dollars in a bank account. **Issuer platforms** (Circle) sit at the source: they mint and redeem the stablecoin itself and offer APIs around it. **Orchestration layers** (Bridge, Crossmint) wrap issuance, conversion, and wallets into developer products. **Custody and infrastructure platforms** (Fireblocks, Zero Hash) give regulated building blocks that businesses assemble under their own or the provider's licenses.\n\nMost buying confusion comes from comparing across types. A gateway that is excellent at merchant checkout may have no payout rails in Latin America, and an issuer platform will not deliver Pix. Start from your money flow, then compare within the right type. For the underlying mechanics, see [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\nTwo concrete scenarios show the split. A European marketplace collecting card payments and paying 5,000 sellers across Latin America needs a payout network with local rails, and its gateway choice is almost irrelevant to that problem. A US neobank adding a \"buy USDC\" button needs a licensed infrastructure platform like Zero Hash, and payout corridors are irrelevant to that one. Write your scenario down first; the provider type usually falls out of the sentence.\n\n## How do the main providers compare?\n\n| Provider | Best for | Directions | Settlement rails | Licensing posture |\n|---|---|---|---|---|\n| BlindPay | Stablecoin-to-local-fiat payouts, Americas | Payout and collection | Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO), on-chain | MSB registrations, compliance in the API |\n| [Circle](https:\u002F\u002Fwww.circle.com) | Issuer-level USDC access | Mint, redeem, transfer | On-chain, US wires | US and EU issuer licenses |\n| [Bridge](https:\u002F\u002Fwww.bridge.xyz) | Stripe-ecosystem orchestration | Pay-in and payout | On-chain, ACH, wire, SEPA | US money transmission (Stripe) |\n| [BVNK](https:\u002F\u002Fwww.bvnk.com) | High-volume EU merchants | Pay-in and payout | SEPA, Faster Payments, SWIFT, on-chain | EU EMI, VASP registrations |\n| [Fireblocks](https:\u002F\u002Fwww.fireblocks.com) | Institutional self-custody | Infrastructure only | On-chain | Tooling under your licenses |\n| [Crossmint](https:\u002F\u002Fwww.crossmint.com) | Consumer apps, embedded wallets | Pay-in focused | On-chain, cards | Provider-managed onboarding |\n| [Zero Hash](https:\u002F\u002Fzerohash.com) | US fintechs embedding crypto | Both, US-centric | On-chain, ACH, wire | US MTLs |\n| [Conduit](https:\u002F\u002Fconduitpay.com) | Emerging-market corridors (Africa, Asia, LatAm) | Payout and collection | Pix, SPEI, Interac, mobile money, on-chain | Provider-run compliance |\n| [Sphere](https:\u002F\u002Fspherepay.co) | On\u002Foff-ramps with virtual accounts | Pay-in and payout | ACH, wire, SEPA, Pix, on-chain | KYC, KYB, sanctions in the API |\n| [Borderless](https:\u002F\u002Fborderless.xyz) | Broad coverage via partner network | Payout and collection | Local rails via licensed partners | Locally licensed partner institutions |\n\nCapabilities shift quarter to quarter. Confirm rails, corridors, and fees on each provider's site before shortlisting; for BlindPay the current numbers are on the [pricing page](\u002Fpricing).\n\n## Which questions decide the choice?\n\n1. **Direction.** Collecting from customers, paying suppliers and contractors, or moving your own treasury? Payout depth and pay-in depth rarely live in the same provider.\n2. **Corridors.** List the exact country pairs. A provider's marketing map and its production corridors differ; ask for delivered-amount quotes on your top three corridors and check [coverage](\u002Fcoverage) explicitly.\n3. **Compliance ownership.** Who runs KYC and KYB, who screens sanctions, who files travel rule data? Built-in compliance shortens your roadmap; bring-your-own-license platforms give control at the cost of obligations. The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) summarizes what applies where.\n4. **Custody.** If holding funds with the provider is unacceptable, your shortlist shrinks to self-custody infrastructure plus a payout network that pulls from your wallet.\n5. **All-in cost.** Request the delivered amount for a fixed test payment, say 1,000 USDC to BRL, and compare across providers. Spread hides in the FX rate, not the fee line. Our live [USDC to BRL](\u002Fusdc-to-brl) and [USDT to BRL](\u002Fusdt-to-brl) pages show quoted rates before you commit.\n6. **Time to first payment.** Ask each provider how long KYB review takes at your entity type. Onboarding, not engineering, is the usual critical path.\n\n## What does onboarding with a provider actually involve?\n\nEvery regulated provider gates live payments behind business verification, and this step, not the API integration, sets your launch date. Expect to provide incorporation documents, proof of address, ownership structure down to ultimate beneficial owners (each owner passes individual KYC), a description of your business model, and often expected volumes and source of funds. Clean, consistent documents move through review in days; mismatched entity names or opaque ownership add weeks.\n\nTwo practical tips. Run onboarding with two providers in parallel rather than serially, so a slow review does not stall the project. And ask each provider what triggers re-review later, such as volume jumps or new corridors, so growth does not surprise your operations team. What verification covers and why is explained in the provider-agnostic terms of our [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026).\n\n## How do pay-ins and payouts differ operationally?\n\nCollecting stablecoins is mostly a reconciliation problem: matching what arrived to who owes what, which is why [virtual accounts](\u002Fvirtual-accounts) with per-customer account details beat shared wallet addresses for B2B collections. Paying out is mostly a verification problem: local rails reject transfers when the recipient name and tax ID do not match the receiving account, Pix being the strictest example, so payout quality depends on how well the provider validates recipient data before sending. Providers optimized for one direction routinely underperform in the other; weight your evaluation by where your volume actually is.\n\n## Where do these options fall short?\n\nEvery provider on the list has a gap. Issuer platforms stop at the dollar leg. EU-licensed gateways thin out outside Europe. US-centric platforms often have no emerging-market rails at all. Payout networks, BlindPay included, do not give you card acquiring or issuer-level mint and redeem. If most of your flow is domestic US ACH between US entities, a stablecoin provider adds a conversion step you may not need. And no provider removes the obligation to understand your own regulatory position, especially if you touch customer funds.\n\n## How should you run a pilot before committing?\n\nShortlist two providers, then run the same real payment through both within the same week, since FX rates move. A useful pilot has four measurements: the delivered amount for a fixed input (the true price), time from API call to bank credit (the true speed), the number of manual touches required (the true operational cost), and how the provider handled one deliberately imperfect payment, such as a slightly mismatched recipient name (the true failure behavior). The last one matters most in production: providers look identical on the happy path and completely different when a payout needs review, retry, or return. Insist on running the pilot in the corridor you care about, not the provider's best corridor.\n\n## When is BlindPay the right provider?\n\nBlindPay is built for one job done well: a business holds USDC or USDT and needs people paid in local currency, compliantly, through [one API](\u002Fglobal-payments). Payouts go out over Pix, SPEI, ACH, and SWIFT, with wires executed as POBO\u002FCOBO transfers carrying UETR tracking codes and MT103 confirmations; [virtual accounts](\u002Fvirtual-accounts) handle the reverse direction by converting incoming bank transfers into stablecoins. KYC, KYB, sanctions screening, and travel rule handling run inside the flow, and FX is quoted before you commit. Depth is strongest in the Americas: Brazil, Mexico, the US, Argentina, Colombia. If that matches your corridor list, [talk to us](\u002Fcontact); if you need merchant card checkout or European EMI rails, one of the providers above is the better fit, and the comparison in [best stablecoin APIs in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026) goes deeper on each.\n\n## Methodology and sources\n\nProvider positioning summarized from public materials as of August 2026: [circle.com](https:\u002F\u002Fwww.circle.com), [bridge.xyz](https:\u002F\u002Fwww.bridge.xyz), [bvnk.com](https:\u002F\u002Fwww.bvnk.com), [fireblocks.com](https:\u002F\u002Fwww.fireblocks.com), [crossmint.com](https:\u002F\u002Fwww.crossmint.com), [zerohash.com](https:\u002F\u002Fzerohash.com). Rail behavior from operator documentation, including the [Banco Central do Brasil's Pix overview](https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en). Supply figures from public dashboards such as DeFiLlama.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":1450,"description":1874},"Best stablecoin payment providers in 2026","resources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","2026-08-24","OOzo278vzIyConpd0PC_mxT6xozUjxobqF627GA208A",{"id":1896,"title":1897,"authors":6,"body":1898,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":2325,"description":2326,"extension":342,"faq":2327,"howto":6,"isBlog":359,"isChangelog":359,"meta":2343,"navigation":362,"path":2344,"pillar":359,"products":6,"rawbody":2345,"role":6,"seo":2346,"seoTitle":2347,"stem":2348,"thumbnail":6,"updated":6,"__hash__":2349},"content\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments.md","Build vs buy: should you build stablecoin payouts in-house or use an API?",{"type":8,"value":1899,"toc":2314},[1900,1903,1906,1910,1913,1916,1919,1923,1926,2064,2067,2071,2074,2100,2107,2110,2114,2117,2143,2146,2150,2153,2170,2173,2177,2180,2205,2208,2212,2239,2242,2246,2251,2297,2302,2304,2310],[11,1901,1902],{},"For most companies, buy. Building stablecoin payouts in-house means running wallet infrastructure across several blockchains, securing liquidity to convert stablecoins into local currency, signing banking partners in every payout country, holding licenses or working through licensed partners, and operating a compliance program that regulators will examine. Teams that have built it describe 12 or more months and a dedicated crew before the first dollar moves. A stablecoin API compresses that into an integration measured in days.",[11,1904,1905],{},"That's the short answer. The longer one depends on what you think you're building.",[18,1907,1909],{"id":1908},"why-does-building-look-easy-at-first","Why does building look easy at first?",[11,1911,1912],{},"Because the demo is easy. Sending USDC from one wallet to another is a few lines of code and costs a fraction of a cent on Base, Polygon, or Solana. A weekend hackathon can move a stablecoin across the world.",[11,1914,1915],{},"Then someone asks: \"How does the contractor in São Paulo get reais in her bank account?\" And the project changes shape.",[11,1917,1918],{},"Moving the token was never the hard part. Everything around it is.",[18,1920,1922],{"id":1921},"what-do-you-actually-have-to-build","What do you actually have to build?",[11,1924,1925],{},"Here's the stack, piece by piece, with what it takes to own each one.",[39,1927,1928,1941],{},[42,1929,1930],{},[45,1931,1932,1935,1938],{},[48,1933,1934],{},"Component",[48,1936,1937],{},"What building it means",[48,1939,1940],{},"What an API gives you",[61,1942,1943,1954,1965,1991,2002,2017,2031,2042,2053],{},[45,1944,1945,1948,1951],{},[66,1946,1947],{},"Wallets and key management",[66,1949,1950],{},"HSM or MPC custody, key rotation, per-network signing, gas management across 5+ chains",[66,1952,1953],{},"Your own wallet or a managed one, with the chain handled",[45,1955,1956,1959,1962],{},[66,1957,1958],{},"Liquidity and conversion",[66,1960,1961],{},"Contracts with OTC desks or exchanges per currency, spread management, failover",[66,1963,1964],{},"A quote with the rate, fee, and receive amount locked for five minutes",[45,1966,1967,1970,1973],{},[66,1968,1969],{},"Local payout rails",[66,1971,1972],{},"A banking partner or payment institution per country for Pix, SPEI, ACH, SEPA",[66,1974,1975,1976,1978,1979,1304,1982,1304,1985,1304,1988],{},"One ",[204,1977,206],{}," field on a bank account: ",[204,1980,1981],{},"pix",[204,1983,1984],{},"spei_bitso",[204,1986,1987],{},"ach",[204,1989,1990],{},"sepa",[45,1992,1993,1996,1999],{},[66,1994,1995],{},"Licensing",[66,1997,1998],{},"Money transmission licenses, or agreements with licensed partners, per market",[66,2000,2001],{},"The provider's licenses and partners",[45,2003,2004,2007,2010],{},[66,2005,2006],{},"KYC and KYB",[66,2008,2009],{},"Vendor integrations, document review, beneficial owner checks, re-verification",[66,2011,2012,2013,2016],{},"A customer object with ",[204,2014,2015],{},"kyc_status",", standard KYC in about 60 seconds",[45,2018,2019,2022,2025],{},[66,2020,2021],{},"Sanctions and monitoring",[66,2023,2024],{},"Screening on every sender and receiver, on-chain wallet risk, rule tuning",[66,2026,2027,2028],{},"Screening on customers and payouts, with holds surfaced as ",[204,2029,2030],{},"on_hold",[45,2032,2033,2036,2039],{},[66,2034,2035],{},"Travel rule",[66,2037,2038],{},"Data exchange with counterparties above thresholds",[66,2040,2041],{},"Handled in the flow",[45,2043,2044,2047,2050],{},[66,2045,2046],{},"Reconciliation",[66,2048,2049],{},"Matching on-chain transactions, FX trades, and bank deposits",[66,2051,2052],{},"One payout id with per-step tracking and webhooks",[45,2054,2055,2058,2061],{},[66,2056,2057],{},"Ops and support",[66,2059,2060],{},"Failed transfers, returned payments, RFIs, bank holidays",[66,2062,2063],{},"A status per payout and a team that handles returns",[11,2065,2066],{},"Nine components. Each one is a vendor contract, a hire, or both.",[18,2068,2070],{"id":2069},"what-does-building-cost-in-people-and-time","What does building cost in people and time?",[11,2072,2073],{},"Rough, but realistic for a team starting from zero on three Latin American corridors:",[171,2075,2076,2082,2088,2094],{},[148,2077,2078,2081],{},[119,2079,2080],{},"Engineering:"," two to three engineers for wallets, ledger, rail integrations, and reconciliation.",[148,2083,2084,2087],{},[119,2085,2086],{},"Treasury and ops:"," one person managing liquidity partners, FX, and failed payments.",[148,2089,2090,2093],{},[119,2091,2092],{},"Compliance:"," a compliance officer, plus analyst time for reviews and RFIs.",[148,2095,2096,2099],{},[119,2097,2098],{},"Legal:"," licensing or partner agreements per country, and they don't run in parallel as fast as you'd hope.",[11,2101,2102,2103,2106],{},"Call it five to eight people, and 12 or more months before production volume. Then the ongoing part: rules like MiCA in Europe and the GENIUS Act in the US keep changing the compliance surface (we track them in our ",[136,2104,2105],{"href":1035},"stablecoin regulation guide","), and every new country restarts the banking and licensing work.",[11,2108,2109],{},"Compare that with an API: a development instance on day one, a first test payout in about a day, and production access after compliance onboarding in up to three business days.",[18,2111,2113],{"id":2112},"when-does-building-make-sense","When does building make sense?",[11,2115,2116],{},"There are real cases. Build, or at least build more, when:",[171,2118,2119,2125,2131,2137],{},[148,2120,2121,2124],{},[119,2122,2123],{},"You are a licensed payments company"," and the rail margin is your business model. Owning the stack is the product.",[148,2126,2127,2130],{},[119,2128,2129],{},"One corridor carries enormous volume"," and you can justify direct banking and liquidity relationships there.",[148,2132,2133,2136],{},[119,2134,2135],{},"You need behavior no provider offers",", and you've actually checked.",[148,2138,2139,2142],{},[119,2140,2141],{},"You already hold the licenses"," in the markets you pay into.",[11,2144,2145],{},"If none of those describe you, building is a distraction from the product your customers actually pay for.",[18,2147,2149],{"id":2148},"when-does-buying-make-sense","When does buying make sense?",[11,2151,2152],{},"Buy when:",[171,2154,2155,2158,2161,2164,2167],{},[148,2156,2157],{},"Payments are a feature of your product, not the product.",[148,2159,2160],{},"You need more than one or two countries.",[148,2162,2163],{},"Your team would rather ship next quarter than next year.",[148,2165,2166],{},"You don't want to hold capital in foreign bank accounts.",[148,2168,2169],{},"Your compliance team wants a provider that runs KYC, KYB, and sanctions screening before money moves, with a record of each decision.",[11,2171,2172],{},"That describes most fintechs, marketplaces, payroll platforms, and B2B software companies we talk to.",[18,2174,2176],{"id":2175},"what-about-a-hybrid","What about a hybrid?",[11,2178,2179],{},"Most teams end up somewhere in between. Three splits we see often:",[145,2181,2182,2188,2199],{},[148,2183,2184,2187],{},[119,2185,2186],{},"Own the ledger and the UX, buy the rails."," Your product holds the customer relationship and the balances. A payout API handles conversion, local delivery, and compliance.",[148,2189,2190,2193,2194,2198],{},[119,2191,2192],{},"Own custody, buy the last mile."," An MPC custody provider like Fireblocks secures treasury. A payout API turns stablecoins into local currency. Read ",[136,2195,2197],{"href":2196},"\u002Fcompare\u002Ffireblocks","BlindPay vs Fireblocks"," for how the two fit together.",[148,2200,2201,2204],{},[119,2202,2203],{},"Own your wallet, buy everything else."," Send payouts from a wallet you control and approve each amount on-chain, so funds never sit with the provider longer than the transfer.",[11,2206,2207],{},"A hybrid keeps control where it matters to you and outsources the parts that need licenses and banking partners.",[18,2209,2211],{"id":2210},"five-questions-to-answer-before-deciding","Five questions to answer before deciding",[145,2213,2214,2219,2224,2229,2234],{},[148,2215,2216],{},[119,2217,2218],{},"Is the rail margin our business, or a cost of doing business?",[148,2220,2221],{},[119,2222,2223],{},"How many countries do we need in the next 18 months?",[148,2225,2226],{},[119,2227,2228],{},"Do we already hold, or want to hold, money transmission licenses?",[148,2230,2231],{},[119,2232,2233],{},"Who on our team owns compliance findings when a regulator asks?",[148,2235,2236],{},[119,2237,2238],{},"What would the same engineers ship if they weren't building payment rails?",[11,2240,2241],{},"If question five has an obvious answer, you already know what to do.",[18,2243,2245],{"id":2244},"how-does-blindpay-fit-a-buy-decision","How does BlindPay fit a buy decision?",[11,2247,2248,2250],{},[136,2249,300],{"href":299}," covers the rows in that table through one REST API:",[171,2252,2253,2262,2272,2278,2289],{},[148,2254,2255,2258,2259,2261],{},[119,2256,2257],{},"No pre-funding."," Fund each payout from your own stablecoin wallet or a ",[136,2260,139],{"href":138}," that converts ACH, wire, or SWIFT deposits into USDC or USDT.",[148,2263,2264,2267,2268,227],{},[119,2265,2266],{},"Automated compliance."," KYC, KYB, sanctions screening, and transaction monitoring run inside the API before money moves. See the ",[136,2269,2271],{"href":2270},"\u002Fcompliance","compliance program",[148,2273,2274,2277],{},[119,2275,2276],{},"Local rail orchestration."," Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and wire in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries, with UETR tracking and MT103 confirmations.",[148,2279,2280,2283,2284,2288],{},[119,2281,2282],{},"Developer tooling."," An ",[136,2285,2287],{"href":2286},"\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks","OpenAPI 3.1 spec and official SDKs"," for Node, Python, Go, PHP, and Swift, a CLI, and an MCP server.",[148,2290,2291,2296],{},[119,2292,2293,227],{},[136,2294,2295],{"href":307},"Published pricing"," You can model the cost before any call.",[11,2298,2299,2300,227],{},"For the evaluation criteria in detail, read ",[136,2301,285],{"href":284},[18,2303,312],{"id":311},[11,2305,2306,2307,2309],{},"Put the nine-row table in front of your team and mark each row \"build\" or \"buy.\" Be honest about the licensing and banking rows; those are the ones that sink timelines. Then spend one afternoon on a development instance and run the ",[136,2308,319],{"href":318},". If the API covers your rows, you just saved a year.",[11,2311,2312],{},[324,2313,326],{},{"title":328,"searchDepth":329,"depth":329,"links":2315},[2316,2317,2318,2319,2320,2321,2322,2323,2324],{"id":1908,"depth":329,"text":1909},{"id":1921,"depth":329,"text":1922},{"id":2069,"depth":329,"text":2070},{"id":2112,"depth":329,"text":2113},{"id":2148,"depth":329,"text":2149},{"id":2175,"depth":329,"text":2176},{"id":2210,"depth":329,"text":2211},{"id":2244,"depth":329,"text":2245},{"id":311,"depth":329,"text":312},"2026-07-23","Building stablecoin payouts in-house means wallets, liquidity, banking partners, licenses, and a compliance program. When building makes sense.",[2328,2331,2334,2337,2340],{"q":2329,"a":2330},"Should I build stablecoin payment infrastructure in-house?","For most companies, no. Building in-house means wallet infrastructure and key management across several networks, liquidity for stablecoin conversion, banking partners in every payout country, licenses or licensed partners for money transmission, and a compliance program with KYC, KYB, sanctions screening, and travel rule reporting. Teams that have built it describe 12 or more months before the first dollar moves. Building makes sense mainly for licensed payment companies whose margin is the rail itself.",{"q":2332,"a":2333},"How long does it take to integrate a stablecoin API instead?","With BlindPay, a first payout on a development instance is usually a day of work using the REST API or an official SDK. Production access requires compliance onboarding and takes up to three business days.",{"q":2335,"a":2336},"What is the hardest part of building stablecoin payouts yourself?","The last mile. Moving USDC on-chain is easy. Converting it to reais, pesos, or dollars at a good rate, at the moment you need it, and delivering it to a bank account over a local rail requires liquidity partners, banking relationships, and a license or licensed partner in each country.",{"q":2338,"a":2339},"Can I build part of the stack and buy the rest?","Yes, and many teams do. Common splits are keeping your own ledger and customer experience while buying payouts and compliance, or using an MPC custody provider for treasury and a payout API for local delivery.",{"q":2341,"a":2342},"Does using a stablecoin API mean giving up control of funds?","Not necessarily. With BlindPay you can send payouts from a blockchain wallet you control and approve each transfer amount on-chain, or use a managed wallet if you want BlindPay to handle signing. Stablecoin refunds return to the originating wallet.",{"author":361},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","---\ntitle: \"Build vs buy: should you build stablecoin payouts in-house or use an API?\"\nseoTitle: \"Build vs buy stablecoin payments infrastructure\"\ndescription: \"Building stablecoin payouts in-house means wallets, liquidity, banking partners, licenses, and a compliance program. When building makes sense.\"\ndate: \"2026-07-23\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Should I build stablecoin payment infrastructure in-house?\"\n    a: \"For most companies, no. Building in-house means wallet infrastructure and key management across several networks, liquidity for stablecoin conversion, banking partners in every payout country, licenses or licensed partners for money transmission, and a compliance program with KYC, KYB, sanctions screening, and travel rule reporting. Teams that have built it describe 12 or more months before the first dollar moves. Building makes sense mainly for licensed payment companies whose margin is the rail itself.\"\n  - q: \"How long does it take to integrate a stablecoin API instead?\"\n    a: \"With BlindPay, a first payout on a development instance is usually a day of work using the REST API or an official SDK. Production access requires compliance onboarding and takes up to three business days.\"\n  - q: \"What is the hardest part of building stablecoin payouts yourself?\"\n    a: \"The last mile. Moving USDC on-chain is easy. Converting it to reais, pesos, or dollars at a good rate, at the moment you need it, and delivering it to a bank account over a local rail requires liquidity partners, banking relationships, and a license or licensed partner in each country.\"\n  - q: \"Can I build part of the stack and buy the rest?\"\n    a: \"Yes, and many teams do. Common splits are keeping your own ledger and customer experience while buying payouts and compliance, or using an MPC custody provider for treasury and a payout API for local delivery.\"\n  - q: \"Does using a stablecoin API mean giving up control of funds?\"\n    a: \"Not necessarily. With BlindPay you can send payouts from a blockchain wallet you control and approve each transfer amount on-chain, or use a managed wallet if you want BlindPay to handle signing. Stablecoin refunds return to the originating wallet.\"\n---\n\nFor most companies, buy. Building stablecoin payouts in-house means running wallet infrastructure across several blockchains, securing liquidity to convert stablecoins into local currency, signing banking partners in every payout country, holding licenses or working through licensed partners, and operating a compliance program that regulators will examine. Teams that have built it describe 12 or more months and a dedicated crew before the first dollar moves. A stablecoin API compresses that into an integration measured in days.\n\nThat's the short answer. The longer one depends on what you think you're building.\n\n## Why does building look easy at first?\n\nBecause the demo is easy. Sending USDC from one wallet to another is a few lines of code and costs a fraction of a cent on Base, Polygon, or Solana. A weekend hackathon can move a stablecoin across the world.\n\nThen someone asks: \"How does the contractor in São Paulo get reais in her bank account?\" And the project changes shape.\n\nMoving the token was never the hard part. Everything around it is.\n\n## What do you actually have to build?\n\nHere's the stack, piece by piece, with what it takes to own each one.\n\n| Component | What building it means | What an API gives you |\n| --- | --- | --- |\n| Wallets and key management | HSM or MPC custody, key rotation, per-network signing, gas management across 5+ chains | Your own wallet or a managed one, with the chain handled |\n| Liquidity and conversion | Contracts with OTC desks or exchanges per currency, spread management, failover | A quote with the rate, fee, and receive amount locked for five minutes |\n| Local payout rails | A banking partner or payment institution per country for Pix, SPEI, ACH, SEPA | One `type` field on a bank account: `pix`, `spei_bitso`, `ach`, `sepa` |\n| Licensing | Money transmission licenses, or agreements with licensed partners, per market | The provider's licenses and partners |\n| KYC and KYB | Vendor integrations, document review, beneficial owner checks, re-verification | A customer object with `kyc_status`, standard KYC in about 60 seconds |\n| Sanctions and monitoring | Screening on every sender and receiver, on-chain wallet risk, rule tuning | Screening on customers and payouts, with holds surfaced as `on_hold` |\n| Travel rule | Data exchange with counterparties above thresholds | Handled in the flow |\n| Reconciliation | Matching on-chain transactions, FX trades, and bank deposits | One payout id with per-step tracking and webhooks |\n| Ops and support | Failed transfers, returned payments, RFIs, bank holidays | A status per payout and a team that handles returns |\n\nNine components. Each one is a vendor contract, a hire, or both.\n\n## What does building cost in people and time?\n\nRough, but realistic for a team starting from zero on three Latin American corridors:\n\n- **Engineering:** two to three engineers for wallets, ledger, rail integrations, and reconciliation.\n- **Treasury and ops:** one person managing liquidity partners, FX, and failed payments.\n- **Compliance:** a compliance officer, plus analyst time for reviews and RFIs.\n- **Legal:** licensing or partner agreements per country, and they don't run in parallel as fast as you'd hope.\n\nCall it five to eight people, and 12 or more months before production volume. Then the ongoing part: rules like MiCA in Europe and the GENIUS Act in the US keep changing the compliance surface (we track them in our [stablecoin regulation guide](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026)), and every new country restarts the banking and licensing work.\n\nCompare that with an API: a development instance on day one, a first test payout in about a day, and production access after compliance onboarding in up to three business days.\n\n## When does building make sense?\n\nThere are real cases. Build, or at least build more, when:\n\n- **You are a licensed payments company** and the rail margin is your business model. Owning the stack is the product.\n- **One corridor carries enormous volume** and you can justify direct banking and liquidity relationships there.\n- **You need behavior no provider offers**, and you've actually checked.\n- **You already hold the licenses** in the markets you pay into.\n\nIf none of those describe you, building is a distraction from the product your customers actually pay for.\n\n## When does buying make sense?\n\nBuy when:\n\n- Payments are a feature of your product, not the product.\n- You need more than one or two countries.\n- Your team would rather ship next quarter than next year.\n- You don't want to hold capital in foreign bank accounts.\n- Your compliance team wants a provider that runs KYC, KYB, and sanctions screening before money moves, with a record of each decision.\n\nThat describes most fintechs, marketplaces, payroll platforms, and B2B software companies we talk to.\n\n## What about a hybrid?\n\nMost teams end up somewhere in between. Three splits we see often:\n\n1. **Own the ledger and the UX, buy the rails.** Your product holds the customer relationship and the balances. A payout API handles conversion, local delivery, and compliance.\n2. **Own custody, buy the last mile.** An MPC custody provider like Fireblocks secures treasury. A payout API turns stablecoins into local currency. Read [BlindPay vs Fireblocks](\u002Fcompare\u002Ffireblocks) for how the two fit together.\n3. **Own your wallet, buy everything else.** Send payouts from a wallet you control and approve each amount on-chain, so funds never sit with the provider longer than the transfer.\n\nA hybrid keeps control where it matters to you and outsources the parts that need licenses and banking partners.\n\n## Five questions to answer before deciding\n\n1. **Is the rail margin our business, or a cost of doing business?**\n2. **How many countries do we need in the next 18 months?**\n3. **Do we already hold, or want to hold, money transmission licenses?**\n4. **Who on our team owns compliance findings when a regulator asks?**\n5. **What would the same engineers ship if they weren't building payment rails?**\n\nIf question five has an obvious answer, you already know what to do.\n\n## How does BlindPay fit a buy decision?\n\n[BlindPay](\u002Fglobal-payments) covers the rows in that table through one REST API:\n\n- **No pre-funding.** Fund each payout from your own stablecoin wallet or a [virtual USD account](\u002Fvirtual-accounts) that converts ACH, wire, or SWIFT deposits into USDC or USDT.\n- **Automated compliance.** KYC, KYB, sanctions screening, and transaction monitoring run inside the API before money moves. See the [compliance program](\u002Fcompliance).\n- **Local rail orchestration.** Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and wire in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries, with UETR tracking and MT103 confirmations.\n- **Developer tooling.** An [OpenAPI 3.1 spec and official SDKs](\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks) for Node, Python, Go, PHP, and Swift, a CLI, and an MCP server.\n- **[Published pricing](\u002Fpricing).** You can model the cost before any call.\n\nFor the evaluation criteria in detail, read [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api).\n\n## What to do next\n\nPut the nine-row table in front of your team and mark each row \"build\" or \"buy.\" Be honest about the licensing and banking rows; those are the ones that sink timelines. Then spend one afternoon on a development instance and run the [payout quickstart](\u002Fdocs\u002Fquickstart-payout). If the API covers your rows, you just saved a year.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":1897,"description":2326},"Build vs buy stablecoin payments infrastructure","resources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","mHJNiJeUjIwgNzeaTJQTNyTULsZzCZFv7bsDntmrlvA",{"id":2351,"title":2352,"authors":6,"body":2353,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":2803,"description":2804,"extension":342,"faq":2805,"howto":6,"isBlog":359,"isChangelog":359,"meta":2821,"navigation":362,"path":2822,"pillar":359,"products":6,"rawbody":2823,"role":6,"seo":2824,"seoTitle":2825,"stem":2826,"thumbnail":6,"updated":6,"__hash__":2827},"content\u002Fresources\u002Fmore\u002Fcrypto-payment-processor-for-businesses.md","Crypto payment processor for businesses: what to compare before you choose",{"type":8,"value":2354,"toc":2787},[2355,2378,2381,2385,2388,2402,2405,2409,2413,2420,2424,2427,2431,2434,2438,2441,2445,2448,2452,2460,2464,2467,2601,2604,2608,2611,2614,2637,2644,2648,2651,2707,2715,2719,2757,2772,2776],[11,2356,2357,2358,2361,2362,1304,2365,1304,2368,1304,2371,1313,2374,2377],{},"A business choosing a crypto payment processor should compare six things: ",[119,2359,2360],{},"settlement speed"," to your bank account, ",[119,2363,2364],{},"supported stablecoins and currencies",[119,2366,2367],{},"compliance and KYC\u002FKYB coverage",[119,2369,2370],{},"developer integration effort",[119,2372,2373],{},"regional payout coverage",[119,2375,2376],{},"pricing transparency",". Most providers look similar on a feature list. They separate on compliance (can you actually use them at volume, in your markets) and on payout coverage (can they get money into the bank accounts you need).",[11,2379,2380],{},"Below is a scorecard you can use on any provider, including us, and what to ask for each criterion.",[18,2382,2384],{"id":2383},"first-what-kind-of-processor-do-you-need","First, what kind of processor do you need?",[11,2386,2387],{},"\"Crypto payment processor\" covers two different jobs:",[171,2389,2390,2396],{},[148,2391,2392,2395],{},[119,2393,2394],{},"Checkout-first processors"," let consumers pay in crypto at checkout and settle the merchant in fiat. Think card-style acceptance with a crypto option.",[148,2397,2398,2401],{},[119,2399,2400],{},"Stablecoin payments APIs"," move money for the business: collecting through virtual accounts, converting stablecoins to local currency, and paying out over local rails across many countries.",[11,2403,2404],{},"BlindPay is the second kind. It's not a card acquirer and not a consumer checkout button. If all you need is a \"pay with crypto\" button on a US storefront, a checkout-first processor may fit better. If you need to collect, convert, and pay out across borders, keep reading.",[18,2406,2408],{"id":2407},"what-are-the-six-criteria-that-matter","What are the six criteria that matter?",[967,2410,2412],{"id":2411},"_1-settlement-speed","1. Settlement speed",[11,2414,2415,2416,227],{},"How long from payment to usable funds in your bank account, in your currency? On-chain confirmation takes seconds to minutes. The real variable is the last mile: Pix, SPEI, and RTP land in minutes, while some providers batch payouts daily or only settle to the US. Ask for the timeline per destination country, not a global average. More in ",[136,2417,2419],{"href":2418},"\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants","stablecoin settlement explained",[967,2421,2423],{"id":2422},"_2-supported-stablecoins-and-currencies","2. Supported stablecoins and currencies",[11,2425,2426],{},"USDC and USDT cover most volume. Check which networks are supported (low-fee chains like Polygon, Base, Arbitrum, Stellar, and Tron matter for small payments) and which fiat currencies the provider can convert into. A provider that supports 30 tokens but converts into five currencies is a trading venue, not a payments processor.",[967,2428,2430],{"id":2429},"_3-compliance-and-kyckyb-coverage","3. Compliance and KYC\u002FKYB coverage",[11,2432,2433],{},"Does the provider hold licenses in the markets you operate in, and publish them? Does it run KYB on you and KYC on your payees inside the API, or hand you a PDF form? How long does approval take? We cover this criterion in depth below, because it's usually the one that decides everything.",[967,2435,2437],{"id":2436},"_4-developer-integration-effort","4. Developer integration effort",[11,2439,2440],{},"SDKs in your language, an OpenAPI spec, a sandbox that behaves like production, webhooks for every status change, and docs that show real request and response payloads. Integration time ranges from a day for a hosted plugin to weeks for a full API build.",[967,2442,2444],{"id":2443},"_5-regional-payout-coverage","5. Regional payout coverage",[11,2446,2447],{},"Which countries can the provider pay out to, over which rails? \"100 countries via SWIFT\" and \"instant Pix in Brazil\" are very different claims. Map your top five payout destinations and check the rail and speed for each.",[967,2449,2451],{"id":2450},"_6-pricing-transparency","6. Pricing transparency",[11,2453,2454,2455,2459],{},"Can you see the FX spread, the payout fee, and any network fee as separate numbers on a quote? Or only a blended rate? Is there a pre-funding requirement hiding a capital cost? Compare ",[136,2456,2458],{"href":2457},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees","stablecoin fees against card processing"," with itemized numbers only.",[18,2461,2463],{"id":2462},"a-scorecard-you-can-use-on-any-provider","A scorecard you can use on any provider",[11,2465,2466],{},"Score each provider 1 to 5 per criterion. Weight the criteria by what your business depends on. The BlindPay column shows what we offer, so you have a reference point; the last column is what to check in everyone else, including us.",[39,2468,2469,2487],{},[42,2470,2471],{},[45,2472,2473,2476,2479,2481,2484],{},[48,2474,2475],{},"Criterion",[48,2477,2478],{},"Suggested weight",[48,2480,300],{},[48,2482,2483],{},"A \"5\" looks like",[48,2485,2486],{},"Ask every provider",[61,2488,2489,2508,2527,2546,2565,2583],{},[45,2490,2491,2496,2499,2502,2505],{},[66,2492,2493],{},[119,2494,2495],{},"Settlement speed",[66,2497,2498],{},"20%",[66,2500,2501],{},"Minutes on Pix, SPEI, and RTP; 24\u002F7",[66,2503,2504],{},"Minutes to local bank accounts, weekends included",[66,2506,2507],{},"\"What's the settlement time to my top three countries?\"",[45,2509,2510,2515,2518,2521,2524],{},[66,2511,2512],{},[119,2513,2514],{},"Stablecoins and currencies",[66,2516,2517],{},"10%",[66,2519,2520],{},"USDC and USDT on Polygon, Base, Arbitrum, Stellar, Tron; 80+ currencies",[66,2522,2523],{},"Major stablecoins on low-fee chains, conversion into your payout currencies",[66,2525,2526],{},"\"Which tokens, networks, and fiat currencies?\"",[45,2528,2529,2534,2537,2540,2543],{},[66,2530,2531],{},[119,2532,2533],{},"Compliance and KYC\u002FKYB",[66,2535,2536],{},"25%",[66,2538,2539],{},"KYC, KYB, sanctions, on-chain and local rail monitoring in the API; licenses published",[66,2541,2542],{},"Licensed in your markets, published licenses, fast onboarding, monitoring on both legs",[66,2544,2545],{},"\"Which licenses, where? How long does KYB take?\"",[45,2547,2548,2553,2556,2559,2562],{},[66,2549,2550],{},[119,2551,2552],{},"Developer effort",[66,2554,2555],{},"15%",[66,2557,2558],{},"Five official SDKs, OpenAPI spec, CLI, MCP server, sandbox",[66,2560,2561],{},"SDKs, OpenAPI, realistic sandbox, webhooks, clear docs",[66,2563,2564],{},"\"Can I get a sandbox key today?\"",[45,2566,2567,2572,2574,2577,2580],{},[66,2568,2569],{},[119,2570,2571],{},"Payout coverage",[66,2573,2498],{},[66,2575,2576],{},"100+ countries; Pix, SPEI, PSE, Transfers 3.0, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO) with UETR tracking and MT103 confirmations",[66,2578,2579],{},"Local instant rails in your key markets, tracked international wires elsewhere",[66,2581,2582],{},"\"Which rail do you use for each of my countries?\"",[45,2584,2585,2590,2592,2595,2598],{},[66,2586,2587],{},[119,2588,2589],{},"Pricing transparency",[66,2591,2517],{},[66,2593,2594],{},"Itemized spread and payout fee per quote; no pre-funding; published plans",[66,2596,2597],{},"Itemized, locked at execution, no hidden capital requirement",[66,2599,2600],{},"\"Send an itemized quote for this amount, this corridor, today.\"",[11,2602,2603],{},"The weights are a starting point. A marketplace paying 10,000 sellers weekly should weight payout coverage higher. A fintech offering accounts to its own users should weight compliance and developer effort higher.",[18,2605,2607],{"id":2606},"why-is-compliance-usually-the-deciding-criterion","Why is compliance usually the deciding criterion?",[11,2609,2610],{},"Because a processor you can't use at scale isn't a processor. It's a demo.",[11,2612,2613],{},"Three compliance questions separate providers that last from providers that don't:",[171,2615,2616,2622,2628],{},[148,2617,2618,2621],{},[119,2619,2620],{},"Do they hold their own licenses, or rent someone else's?"," A provider operating entirely under a partner's license can be offboarded by that partner with little notice. When that happens, every business built on top goes down with it. Published licenses in the markets you care about are the baseline.",[148,2623,2624,2627],{},[119,2625,2626],{},"How fast is onboarding?"," If your product onboards customers who need KYC or KYB, the provider's approval time becomes your conversion rate. Minutes and five business days are both \"supported.\" Only one keeps your signup funnel alive.",[148,2629,2630,2633,2634],{},[119,2631,2632],{},"Do they monitor both legs?"," The stablecoin leg is final in minutes. The ACH or wire funding it can be reversed for days. A provider that only checks identity at signup, and doesn't monitor the fiat side continuously, is carrying a fraud gap that eventually lands on someone. See ",[136,2635,2636],{"href":734},"are stablecoin payments reversible?",[11,2638,2639,2640],{},"What's interesting here is that fees rarely end up being the deciding factor for teams that have run payments at volume. Compliance approval times, settlement times, tracking visibility, and how fast errors get resolved matter more, because those are what customers feel. We break down licensing and KYB in ",[136,2641,2643],{"href":2642},"\u002Fresources\u002Fmore\u002Fdo-merchants-need-a-license-to-accept-stablecoins","do merchants need a license to accept stablecoin payments?",[18,2645,2647],{"id":2646},"what-does-good-developer-experience-look-like","What does good developer experience look like?",[11,2649,2650],{},"Check these before signing:",[171,2652,2653,2659,2665,2675,2681,2687],{},[148,2654,2655,2658],{},[119,2656,2657],{},"SDKs"," in the languages your team writes. Typed, maintained, versioned.",[148,2660,2661,2664],{},[119,2662,2663],{},"An OpenAPI spec",", so you can generate clients and validate requests.",[148,2666,2667,2670,2671,2674],{},[119,2668,2669],{},"A sandbox that matches production",": same endpoints, same webhooks, simulated payouts. See ",[136,2672,2673],{"href":754},"sandbox vs production"," for what to test.",[148,2676,2677,2680],{},[119,2678,2679],{},"Webhooks"," for every state change, with retries and signatures.",[148,2682,2683,2686],{},[119,2684,2685],{},"Tracking identifiers"," exposed in the API, like UETR on SWIFT transfers, so support can answer \"where's my money\" without opening a ticket.",[148,2688,2689,2692,2693,2697,2698,1313,2702,2706],{},[119,2690,2691],{},"AI tooling",", increasingly. BlindPay ships a ",[136,2694,2696],{"href":2695},"\u002Fblog\u002Fcli","CLI",", an ",[136,2699,2701],{"href":2700},"\u002Fblog\u002Fmcp","MCP server",[136,2703,2705],{"href":2704},"\u002Fblog\u002Fagent-skills","Agent Skills",", so coding assistants can read the API and run sandbox operations directly.",[11,2708,2709,2710,2714],{},"A realistic timeline for a full API integration (onboarding, quotes, payouts, webhooks) is days to a few weeks. Most of the variance comes from sandbox quality and how quickly your own KYB clears. Our guide on ",[136,2711,2713],{"href":2712},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api","how to integrate a stablecoin API"," walks through the build.",[18,2716,2718],{"id":2717},"how-should-you-run-the-evaluation","How should you run the evaluation?",[145,2720,2721,2727,2733,2739,2745,2751],{},[148,2722,2723,2726],{},[119,2724,2725],{},"List your top five payout or collection countries"," and the volume in each.",[148,2728,2729,2732],{},[119,2730,2731],{},"Shortlist three providers"," that cover those countries on local rails.",[148,2734,2735,2738],{},[119,2736,2737],{},"Request an itemized quote"," from each on the same amount, same corridor, same day.",[148,2740,2741,2744],{},[119,2742,2743],{},"Ask for published licenses"," and expected KYB turnaround.",[148,2746,2747,2750],{},[119,2748,2749],{},"Get sandbox keys"," and build one end-to-end flow with each, or at least your top choice.",[148,2752,2753,2756],{},[119,2754,2755],{},"Score them"," with the table above.",[11,2758,2759,2760,2764,2765,2769,2770,227],{},"For the broader picture of how stablecoin acceptance works, start with ",[136,2761,2763],{"href":2762},"\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments","how merchants accept stablecoin payments",". If you pay out across several countries, read ",[136,2766,2768],{"href":2767},"\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding","cross-border payments without pre-funding",". For more on choosing an API specifically, see ",[136,2771,285],{"href":284},[18,2773,2775],{"id":2774},"put-blindpay-through-the-scorecard","Put BlindPay through the scorecard",[11,2777,2778,2779,2782,2783,227],{},"We'd rather be picked on the scorecard than on a pitch. If you want sandbox access, published licenses, and an itemized quote for your corridors, ",[136,2780,2781],{"href":1344},"talk to the BlindPay team"," or start with the ",[136,2784,2786],{"href":2785},"\u002Fdocs\u002Fintroduction","docs",{"title":328,"searchDepth":329,"depth":329,"links":2788},[2789,2790,2798,2799,2800,2801,2802],{"id":2383,"depth":329,"text":2384},{"id":2407,"depth":329,"text":2408,"children":2791},[2792,2793,2794,2795,2796,2797],{"id":2411,"depth":1404,"text":2412},{"id":2422,"depth":1404,"text":2423},{"id":2429,"depth":1404,"text":2430},{"id":2436,"depth":1404,"text":2437},{"id":2443,"depth":1404,"text":2444},{"id":2450,"depth":1404,"text":2451},{"id":2462,"depth":329,"text":2463},{"id":2606,"depth":329,"text":2607},{"id":2646,"depth":329,"text":2647},{"id":2717,"depth":329,"text":2718},{"id":2774,"depth":329,"text":2775},"2026-09-18","Compare crypto payment processors on six criteria: settlement speed, stablecoins, compliance, dev effort, payout coverage, and pricing. Scorecard inside.",[2806,2809,2812,2815,2818],{"q":2807,"a":2808},"What should a business look for in a crypto payment processor?","Six things: settlement speed to your bank account, supported stablecoins and currencies, compliance and KYC\u002FKYB coverage, developer integration effort, regional payout coverage, and pricing transparency. Compliance and payout coverage usually decide whether a processor works at scale; the others decide how pleasant it is to use.",{"q":2810,"a":2811},"What is the difference between a crypto payment processor and a stablecoin payments API?","A crypto payment processor typically focuses on checkout: letting customers pay in crypto and settling the merchant in fiat. A stablecoin payments API like BlindPay focuses on moving money: collecting via virtual accounts, converting stablecoins to local currency, and paying out over local rails in many countries. Some businesses need one, some need both.",{"q":2813,"a":2814},"How long does it take to integrate a crypto payment processor?","A hosted checkout plugin can go live in a day. A full API integration covering customer onboarding, quotes, payouts, and webhooks typically takes days to a few weeks, depending on SDK quality, sandbox fidelity, and how fast the provider approves your KYB. Ask for a sandbox key before signing.",{"q":2816,"a":2817},"Why does compliance matter when choosing a crypto payment processor?","Because it decides whether you can actually use the processor at volume. A provider without the right licenses in your markets can be shut off by its own banking partners, and slow KYC or KYB approvals stall your customer onboarding. Check published licenses, onboarding times, and whether monitoring covers both the stablecoin and fiat legs.",{"q":2819,"a":2820},"How do crypto payment processors charge?","Common models are a percentage per transaction, a per-transaction fee plus network costs, a monthly subscription, or a negotiated enterprise contract. The fair comparison uses itemized quotes on the same amount, corridor, and day, with the FX spread and payout fee shown separately.",{},"\u002Fresources\u002Fmore\u002Fcrypto-payment-processor-for-businesses","---\ntitle: \"Crypto payment processor for businesses: what to compare before you choose\"\nseoTitle: \"Crypto payment processor for businesses: how to compare\"\ndescription: \"Compare crypto payment processors on six criteria: settlement speed, stablecoins, compliance, dev effort, payout coverage, and pricing. Scorecard inside.\"\ndate: \"2026-09-18\"\ncategory: \"payments\"\nfaq:\n  - q: \"What should a business look for in a crypto payment processor?\"\n    a: \"Six things: settlement speed to your bank account, supported stablecoins and currencies, compliance and KYC\u002FKYB coverage, developer integration effort, regional payout coverage, and pricing transparency. Compliance and payout coverage usually decide whether a processor works at scale; the others decide how pleasant it is to use.\"\n  - q: \"What is the difference between a crypto payment processor and a stablecoin payments API?\"\n    a: \"A crypto payment processor typically focuses on checkout: letting customers pay in crypto and settling the merchant in fiat. A stablecoin payments API like BlindPay focuses on moving money: collecting via virtual accounts, converting stablecoins to local currency, and paying out over local rails in many countries. Some businesses need one, some need both.\"\n  - q: \"How long does it take to integrate a crypto payment processor?\"\n    a: \"A hosted checkout plugin can go live in a day. A full API integration covering customer onboarding, quotes, payouts, and webhooks typically takes days to a few weeks, depending on SDK quality, sandbox fidelity, and how fast the provider approves your KYB. Ask for a sandbox key before signing.\"\n  - q: \"Why does compliance matter when choosing a crypto payment processor?\"\n    a: \"Because it decides whether you can actually use the processor at volume. A provider without the right licenses in your markets can be shut off by its own banking partners, and slow KYC or KYB approvals stall your customer onboarding. Check published licenses, onboarding times, and whether monitoring covers both the stablecoin and fiat legs.\"\n  - q: \"How do crypto payment processors charge?\"\n    a: \"Common models are a percentage per transaction, a per-transaction fee plus network costs, a monthly subscription, or a negotiated enterprise contract. The fair comparison uses itemized quotes on the same amount, corridor, and day, with the FX spread and payout fee shown separately.\"\n---\n\nA business choosing a crypto payment processor should compare six things: **settlement speed** to your bank account, **supported stablecoins and currencies**, **compliance and KYC\u002FKYB coverage**, **developer integration effort**, **regional payout coverage**, and **pricing transparency**. Most providers look similar on a feature list. They separate on compliance (can you actually use them at volume, in your markets) and on payout coverage (can they get money into the bank accounts you need).\n\nBelow is a scorecard you can use on any provider, including us, and what to ask for each criterion.\n\n## First, what kind of processor do you need?\n\n\"Crypto payment processor\" covers two different jobs:\n\n- **Checkout-first processors** let consumers pay in crypto at checkout and settle the merchant in fiat. Think card-style acceptance with a crypto option.\n- **Stablecoin payments APIs** move money for the business: collecting through virtual accounts, converting stablecoins to local currency, and paying out over local rails across many countries.\n\nBlindPay is the second kind. It's not a card acquirer and not a consumer checkout button. If all you need is a \"pay with crypto\" button on a US storefront, a checkout-first processor may fit better. If you need to collect, convert, and pay out across borders, keep reading.\n\n## What are the six criteria that matter?\n\n### 1. Settlement speed\n\nHow long from payment to usable funds in your bank account, in your currency? On-chain confirmation takes seconds to minutes. The real variable is the last mile: Pix, SPEI, and RTP land in minutes, while some providers batch payouts daily or only settle to the US. Ask for the timeline per destination country, not a global average. More in [stablecoin settlement explained](\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants).\n\n### 2. Supported stablecoins and currencies\n\nUSDC and USDT cover most volume. Check which networks are supported (low-fee chains like Polygon, Base, Arbitrum, Stellar, and Tron matter for small payments) and which fiat currencies the provider can convert into. A provider that supports 30 tokens but converts into five currencies is a trading venue, not a payments processor.\n\n### 3. Compliance and KYC\u002FKYB coverage\n\nDoes the provider hold licenses in the markets you operate in, and publish them? Does it run KYB on you and KYC on your payees inside the API, or hand you a PDF form? How long does approval take? We cover this criterion in depth below, because it's usually the one that decides everything.\n\n### 4. Developer integration effort\n\nSDKs in your language, an OpenAPI spec, a sandbox that behaves like production, webhooks for every status change, and docs that show real request and response payloads. Integration time ranges from a day for a hosted plugin to weeks for a full API build.\n\n### 5. Regional payout coverage\n\nWhich countries can the provider pay out to, over which rails? \"100 countries via SWIFT\" and \"instant Pix in Brazil\" are very different claims. Map your top five payout destinations and check the rail and speed for each.\n\n### 6. Pricing transparency\n\nCan you see the FX spread, the payout fee, and any network fee as separate numbers on a quote? Or only a blended rate? Is there a pre-funding requirement hiding a capital cost? Compare [stablecoin fees against card processing](\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees) with itemized numbers only.\n\n## A scorecard you can use on any provider\n\nScore each provider 1 to 5 per criterion. Weight the criteria by what your business depends on. The BlindPay column shows what we offer, so you have a reference point; the last column is what to check in everyone else, including us.\n\n| Criterion | Suggested weight | BlindPay | A \"5\" looks like | Ask every provider |\n| --- | --- | --- | --- | --- |\n| **Settlement speed** | 20% | Minutes on Pix, SPEI, and RTP; 24\u002F7 | Minutes to local bank accounts, weekends included | \"What's the settlement time to my top three countries?\" |\n| **Stablecoins and currencies** | 10% | USDC and USDT on Polygon, Base, Arbitrum, Stellar, Tron; 80+ currencies | Major stablecoins on low-fee chains, conversion into your payout currencies | \"Which tokens, networks, and fiat currencies?\" |\n| **Compliance and KYC\u002FKYB** | 25% | KYC, KYB, sanctions, on-chain and local rail monitoring in the API; licenses published | Licensed in your markets, published licenses, fast onboarding, monitoring on both legs | \"Which licenses, where? How long does KYB take?\" |\n| **Developer effort** | 15% | Five official SDKs, OpenAPI spec, CLI, MCP server, sandbox | SDKs, OpenAPI, realistic sandbox, webhooks, clear docs | \"Can I get a sandbox key today?\" |\n| **Payout coverage** | 20% | 100+ countries; Pix, SPEI, PSE, Transfers 3.0, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO) with UETR tracking and MT103 confirmations | Local instant rails in your key markets, tracked international wires elsewhere | \"Which rail do you use for each of my countries?\" |\n| **Pricing transparency** | 10% | Itemized spread and payout fee per quote; no pre-funding; published plans | Itemized, locked at execution, no hidden capital requirement | \"Send an itemized quote for this amount, this corridor, today.\" |\n\nThe weights are a starting point. A marketplace paying 10,000 sellers weekly should weight payout coverage higher. A fintech offering accounts to its own users should weight compliance and developer effort higher.\n\n## Why is compliance usually the deciding criterion?\n\nBecause a processor you can't use at scale isn't a processor. It's a demo.\n\nThree compliance questions separate providers that last from providers that don't:\n\n- **Do they hold their own licenses, or rent someone else's?** A provider operating entirely under a partner's license can be offboarded by that partner with little notice. When that happens, every business built on top goes down with it. Published licenses in the markets you care about are the baseline.\n- **How fast is onboarding?** If your product onboards customers who need KYC or KYB, the provider's approval time becomes your conversion rate. Minutes and five business days are both \"supported.\" Only one keeps your signup funnel alive.\n- **Do they monitor both legs?** The stablecoin leg is final in minutes. The ACH or wire funding it can be reversed for days. A provider that only checks identity at signup, and doesn't monitor the fiat side continuously, is carrying a fraud gap that eventually lands on someone. See [are stablecoin payments reversible?](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible)\n\nWhat's interesting here is that fees rarely end up being the deciding factor for teams that have run payments at volume. Compliance approval times, settlement times, tracking visibility, and how fast errors get resolved matter more, because those are what customers feel. We break down licensing and KYB in [do merchants need a license to accept stablecoin payments?](\u002Fresources\u002Fmore\u002Fdo-merchants-need-a-license-to-accept-stablecoins)\n\n## What does good developer experience look like?\n\nCheck these before signing:\n\n- **SDKs** in the languages your team writes. Typed, maintained, versioned.\n- **An OpenAPI spec**, so you can generate clients and validate requests.\n- **A sandbox that matches production**: same endpoints, same webhooks, simulated payouts. See [sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) for what to test.\n- **Webhooks** for every state change, with retries and signatures.\n- **Tracking identifiers** exposed in the API, like UETR on SWIFT transfers, so support can answer \"where's my money\" without opening a ticket.\n- **AI tooling**, increasingly. BlindPay ships a [CLI](\u002Fblog\u002Fcli), an [MCP server](\u002Fblog\u002Fmcp), and [Agent Skills](\u002Fblog\u002Fagent-skills), so coding assistants can read the API and run sandbox operations directly.\n\nA realistic timeline for a full API integration (onboarding, quotes, payouts, webhooks) is days to a few weeks. Most of the variance comes from sandbox quality and how quickly your own KYB clears. Our guide on [how to integrate a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api) walks through the build.\n\n## How should you run the evaluation?\n\n1. **List your top five payout or collection countries** and the volume in each.\n2. **Shortlist three providers** that cover those countries on local rails.\n3. **Request an itemized quote** from each on the same amount, same corridor, same day.\n4. **Ask for published licenses** and expected KYB turnaround.\n5. **Get sandbox keys** and build one end-to-end flow with each, or at least your top choice.\n6. **Score them** with the table above.\n\nFor the broader picture of how stablecoin acceptance works, start with [how merchants accept stablecoin payments](\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments). If you pay out across several countries, read [cross-border payments without pre-funding](\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding). For more on choosing an API specifically, see [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api).\n\n## Put BlindPay through the scorecard\n\nWe'd rather be picked on the scorecard than on a pitch. If you want sandbox access, published licenses, and an itemized quote for your corridors, [talk to the BlindPay team](\u002Fcontact) or start with the [docs](\u002Fdocs\u002Fintroduction).\n",{"title":2352,"description":2804},"Crypto payment processor for businesses: how to compare","resources\u002Fmore\u002Fcrypto-payment-processor-for-businesses","9Mfu6xpfurnMGJKo7jHHK3BnW4qzGV7S5SMrH8lPNnw",{"id":2829,"title":2830,"authors":6,"body":2831,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":666,"description":3338,"extension":342,"faq":3339,"howto":6,"isBlog":359,"isChangelog":359,"meta":3355,"navigation":362,"path":2767,"pillar":359,"products":6,"rawbody":3356,"role":6,"seo":3357,"seoTitle":3358,"stem":3359,"thumbnail":6,"updated":6,"__hash__":3360},"content\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding.md","How global merchants get paid across borders with stablecoins, no pre-funding required",{"type":8,"value":2832,"toc":3329},[2833,2843,2846,2850,2853,2856,2859,2885,2888,2892,2895,2898,2930,2937,2941,2948,2951,3058,3061,3064,3068,3071,3178,3184,3194,3198,3201,3242,3248,3252,3255,3303,3306,3320,3324],[11,2834,2835,2838,2839,2842],{},[119,2836,2837],{},"Pre-funding"," means holding local currency balances in every market before a payment can move there: reais in Brazil, pesos in Mexico, euros in Europe, all parked in local accounts ahead of time. It ties up capital, spreads it thin, and exposes it to FX swings. ",[119,2840,2841],{},"Stablecoin-based virtual accounts remove that requirement."," Value crosses the border as a digital dollar (USDC or USDT) and converts into local currency at execution, at a locked rate, then lands over the local rail in minutes. One float, in one place, instead of one per country.",[11,2844,2845],{},"That single change is what makes launching a new market a product decision instead of a treasury project.",[18,2847,2849],{"id":2848},"why-do-cross-border-merchants-pre-fund-at-all","Why do cross-border merchants pre-fund at all?",[11,2851,2852],{},"Because traditional rails can't move value across a border in real time.",[11,2854,2855],{},"A payout to a Brazilian seller over SWIFT passes through correspondent banks, each settling on its own schedule, over one to five business days. If a provider promises \"instant\" payouts in Brazil on those rails, the only way to deliver is to already have reais in Brazil. So they pre-fund. They keep balances in nostro accounts in every market, sized to cover the next few days or weeks of payouts, and top them up with slow wires.",[11,2857,2858],{},"That model has four built-in costs:",[171,2860,2861,2867,2873,2879],{},[148,2862,2863,2866],{},[119,2864,2865],{},"Trapped capital."," Money sitting in ten countries is money not working anywhere.",[148,2868,2869,2872],{},[119,2870,2871],{},"Fragmented liquidity."," Brazil runs dry while Mexico sits on a surplus. Rebalancing takes days.",[148,2874,2875,2878],{},[119,2876,2877],{},"FX exposure."," Every idle local balance moves with the currency while it waits.",[148,2880,2881,2884],{},[119,2882,2883],{},"Banking hours."," Top-ups stop on weekends and holidays, so buffers have to cover them.",[11,2886,2887],{},"Whoever carries those costs passes them on, usually as a wider FX spread on the merchant's payouts.",[18,2889,2891],{"id":2890},"how-do-stablecoin-rails-change-the-model","How do stablecoin rails change the model?",[11,2893,2894],{},"The stablecoin becomes the shared settlement asset across every market. Instead of pre-positioning reais, pesos, and euros, the merchant (or its provider) holds dollars in stablecoin form and converts at the moment a payment executes.",[11,2896,2897],{},"The flow looks like this:",[145,2899,2900,2906,2912,2918,2924],{},[148,2901,2902,2905],{},[119,2903,2904],{},"Collect."," Customers pay into a virtual account by bank transfer, or pay in USDC\u002FUSDT directly. Bank deposits auto-convert into stablecoins.",[148,2907,2908,2911],{},[119,2909,2910],{},"Hold one float."," Balances sit in stablecoins, not in ten local accounts.",[148,2913,2914,2917],{},[119,2915,2916],{},"Quote."," When a payout is due, request a quote: amount, destination currency, destination account.",[148,2919,2920,2923],{},[119,2921,2922],{},"Convert at execution."," The rate is locked when the payment runs. No balance needed in the destination country beforehand.",[148,2925,2926,2929],{},[119,2927,2928],{},"Deliver over the local rail."," Pix in Brazil, SPEI in Mexico, SEPA in Europe. Minutes on instant rails.",[11,2931,2932,2933,227],{},"BlindPay settles this way by design: no capital pre-positioned in destination accounts before a payout clears. It runs 24\u002F7, so Saturday payouts don't wait for Monday top-ups. We wrote about why the stablecoin part should stay invisible to the merchant in ",[136,2934,2936],{"href":2935},"\u002Fblog\u002Fstablecoin-for-the-ordinary","Stablecoin for the Ordinary",[18,2938,2940],{"id":2939},"a-worked-example-one-merchant-four-markets","A worked example: one merchant, four markets",[11,2942,2943,2944,2947],{},"A US-based marketplace pays sellers in ",[119,2945,2946],{},"Brazil, Mexico, Colombia, and Europe",". Monthly payouts: $400,000 to Brazil, $300,000 to Mexico, $150,000 to Colombia, $150,000 to Europe. $1M a month total.",[11,2949,2950],{},"These figures are illustrative, but the shape is what every finance lead running multi-market payouts recognizes.",[39,2952,2953,2965],{},[42,2954,2955],{},[45,2956,2957,2959,2962],{},[48,2958],{},[48,2960,2961],{},"Stablecoin virtual account model",[48,2963,2964],{},"Traditional pre-funded model",[61,2966,2967,2980,2993,3006,3019,3032,3045],{},[45,2968,2969,2974,2977],{},[66,2970,2971],{},[119,2972,2973],{},"Capital parked in destination markets",[66,2975,2976],{},"$0 in destination markets; one stablecoin float",[66,2978,2979],{},"Two weeks of payout buffer per market: about $500,000",[45,2981,2982,2987,2990],{},[66,2983,2984],{},[119,2985,2986],{},"Cost of that capital at 8% a year",[66,2988,2989],{},"None for destination buffers",[66,2991,2992],{},"About $40,000 a year, before FX losses on idle balances",[45,2994,2995,3000,3003],{},[66,2996,2997],{},[119,2998,2999],{},"Local bank relationships",[66,3001,3002],{},"One API integration",[66,3004,3005],{},"Four, often with a local entity or partner in each",[45,3007,3008,3013,3016],{},[66,3009,3010],{},[119,3011,3012],{},"Time to launch a fifth market",[66,3014,3015],{},"Days to weeks, once the market is covered and your KYB is done",[66,3017,3018],{},"Months: local entity or partner, bank account, compliance setup, then funding",[45,3020,3021,3026,3029],{},[66,3022,3023],{},[119,3024,3025],{},"Weekend payouts",[66,3027,3028],{},"Yes, 24\u002F7",[66,3030,3031],{},"Limited by top-up windows",[45,3033,3034,3039,3042],{},[66,3035,3036],{},[119,3037,3038],{},"Payout speed",[66,3040,3041],{},"Minutes on Pix, SPEI, and other instant rails",[66,3043,3044],{},"Fast only while the local buffer lasts",[45,3046,3047,3052,3055],{},[66,3048,3049],{},[119,3050,3051],{},"FX pricing",[66,3053,3054],{},"Quoted per payment, spread and payout fee itemized",[66,3056,3057],{},"Wider spreads to cover the provider's funding costs",[11,3059,3060],{},"The $500,000 is the number that gets a CFO's attention. It's half a month of payouts doing nothing, spread across four currencies, losing value whenever one of them weakens against the dollar.",[11,3062,3063],{},"The launch time is the number that gets a founder's attention. Adding Argentina under the old model is a project. Under the stablecoin model, it's a new destination currency in the same API call: Transfers 3.0 to a CBU or CVU.",[18,3065,3067],{"id":3066},"how-does-local-payment-rail-orchestration-work-on-the-payout-side","How does local payment rail orchestration work on the payout side?",[11,3069,3070],{},"Stablecoins handle the border. Local rails handle the last mile, and they're different in every country. Orchestration means picking the right rail per destination and handling its quirks so the merchant doesn't have to.",[39,3072,3073,3086],{},[42,3074,3075],{},[45,3076,3077,3080,3083],{},[48,3078,3079],{},"Destination",[48,3081,3082],{},"Rails BlindPay pays out on",[48,3084,3085],{},"Typical speed",[61,3087,3088,3101,3114,3127,3140,3153,3166],{},[45,3089,3090,3095,3098],{},[66,3091,3092],{},[119,3093,3094],{},"Brazil",[66,3096,3097],{},"Pix, TED, Boleto",[66,3099,3100],{},"Minutes on Pix, 24\u002F7",[45,3102,3103,3108,3111],{},[66,3104,3105],{},[119,3106,3107],{},"Mexico",[66,3109,3110],{},"SPEI",[66,3112,3113],{},"Minutes, 24\u002F7",[45,3115,3116,3121,3124],{},[66,3117,3118],{},[119,3119,3120],{},"Colombia",[66,3122,3123],{},"PSE",[66,3125,3126],{},"Usually minutes, within bank windows",[45,3128,3129,3134,3137],{},[66,3130,3131],{},[119,3132,3133],{},"Argentina",[66,3135,3136],{},"Transfers 3.0 (CBU\u002FCVU)",[66,3138,3139],{},"Same day",[45,3141,3142,3147,3150],{},[66,3143,3144],{},[119,3145,3146],{},"United States",[66,3148,3149],{},"ACH, RTP, domestic wire",[66,3151,3152],{},"Seconds on RTP; same day to 2 days on ACH",[45,3154,3155,3160,3163],{},[66,3156,3157],{},[119,3158,3159],{},"Europe",[66,3161,3162],{},"SEPA, across 40 SEPA-zone countries",[66,3164,3165],{},"Same day or next day",[45,3167,3168,3173,3176],{},[66,3169,3170],{},[119,3171,3172],{},"Everywhere else",[66,3174,3175],{},"SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations",[66,3177,1159],{},[11,3179,3180,3181,227],{},"BlindPay covers 100+ countries and 80+ currencies this way, from one integration. The full list is on the ",[136,3182,3183],{"href":1335},"coverage page",[11,3185,3186,3187,3189,3190,227],{},"On the collection side, ",[136,3188,632],{"href":138}," do the reverse: BlindPay issues US and local bank accounts in your name or your customer's name. A US buyer pays by ACH or wire like any domestic invoice. The deposit auto-converts into stablecoins and can settle to your local currency right after. No US entity required. We covered this in detail when we launched ",[136,3191,3193],{"href":3192},"\u002Fblog\u002Fintroducing-virtual-accounts","Named Virtual Accounts",[18,3195,3197],{"id":3196},"what-compliance-does-this-model-need","What compliance does this model need?",[11,3199,3200],{},"Moving money across borders without a local bank in every market doesn't mean moving it without rules. Doing this legitimately takes:",[171,3202,3203,3213,3219,3225,3231],{},[148,3204,3205,3208,3209,227],{},[119,3206,3207],{},"KYB on the merchant."," Company documents, beneficial owners, business activity. See ",[136,3210,3212],{"href":3211},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","what KYB is",[148,3214,3215,3218],{},[119,3216,3217],{},"KYC on individual payees."," Sellers, contractors, and creators receiving payouts get verified before their first payment.",[148,3220,3221,3224],{},[119,3222,3223],{},"Sanctions and watchlist screening"," on every counterparty and transaction.",[148,3226,3227,3230],{},[119,3228,3229],{},"On-chain monitoring"," of the stablecoin leg for exposure to sanctioned or high-risk wallets.",[148,3232,3233,3236,3237,3241],{},[119,3234,3235],{},"Local licensing"," in each market the provider serves. Brazil, for example, licenses virtual asset service providers under its own regime; see our ",[136,3238,3240],{"href":3239},"\u002Fresources\u002Fmore\u002Fpsav-brazil-explained","PSAV explainer",". The EU runs MiCA.",[11,3243,3244,3245,3247],{},"BlindPay runs KYC, KYB, sanctions screening, and transaction monitoring inside the same API, and publishes its licenses on the ",[136,3246,1046],{"href":815},". The merchant stays responsible for its own tax and accounting records in each market.",[18,3249,3251],{"id":3250},"is-this-model-right-for-your-expansion-plans","Is this model right for your expansion plans?",[11,3253,3254],{},"Run through this checklist:",[171,3256,3257,3263,3270,3277,3282,3289,3296],{},[148,3258,3259,3260,227],{},"You pay out, or plan to pay out, in ",[119,3261,3262],{},"two or more countries",[148,3264,3265,3266,3269],{},"You currently keep, or would need to keep, ",[119,3267,3268],{},"local balances"," in those markets.",[148,3271,3272,3273,3276],{},"Your payees are ",[119,3274,3275],{},"sellers, contractors, creators, or suppliers"," who want local currency in a local bank account.",[148,3278,3279,3281],{},[119,3280,3038],{}," matters to retention: sellers leave platforms that pay slowly.",[148,3283,3284,3285,3288],{},"You want to ",[119,3286,3287],{},"launch new markets"," without opening a bank relationship in each.",[148,3290,3291,3292,3295],{},"Your finance team wants ",[119,3293,3294],{},"one reconciliation flow"," instead of one per country.",[148,3297,3298,3299,3302],{},"You can complete ",[119,3300,3301],{},"KYB"," and collect KYC data from payees.",[11,3304,3305],{},"Three or more checks, and the pre-funded model is probably costing you more than you think.",[11,3307,3308,3309,3311,3312,3315,3316,227],{},"For more on the mechanics, read ",[136,3310,2419],{"href":2418},", and for a cost breakdown, ",[136,3313,3314],{"href":2457},"stablecoin fees vs card processing fees",". If you're comparing conversion partners, see ",[136,3317,3319],{"href":3318},"\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","how to choose an on\u002Foff-ramp provider",[18,3321,3323],{"id":3322},"expand-without-parking-capital","Expand without parking capital",[11,3325,3326,3327,227],{},"Every market you add under the old model costs a bank relationship and a buffer. Under a stablecoin model it costs a destination currency. If you want to map your current payout flows against this model, ",[136,3328,2781],{"href":1344},{"title":328,"searchDepth":329,"depth":329,"links":3330},[3331,3332,3333,3334,3335,3336,3337],{"id":2848,"depth":329,"text":2849},{"id":2890,"depth":329,"text":2891},{"id":2939,"depth":329,"text":2940},{"id":3066,"depth":329,"text":3067},{"id":3196,"depth":329,"text":3197},{"id":3250,"depth":329,"text":3251},{"id":3322,"depth":329,"text":3323},"Pre-funding means parking local currency in every market before money moves. Stablecoin virtual accounts remove it. A worked example across 4 countries.",[3340,3343,3346,3349,3352],{"q":3341,"a":3342},"What is pre-funding in cross-border payments?","Pre-funding means holding local currency balances in each country before a payment can go out there. A merchant or provider paying out in Brazil, Mexico, and Colombia needs reais, pesos, and Colombian pesos sitting in local accounts ahead of time. That capital is idle until spent, split across markets, and exposed to FX moves while it waits.",{"q":3344,"a":3345},"How do stablecoins remove the need for pre-funding?","Value crosses the border as a dollar stablecoin like USDC or USDT and converts into local currency at execution time, at a quoted and locked rate. The merchant keeps one float in one place instead of balances in every market, and the payout reaches the local bank account over the local rail, such as Pix, SPEI, or SEPA, usually in minutes.",{"q":3347,"a":3348},"How can merchants receive cross-border payments without a local entity?","With virtual accounts. BlindPay issues US and local bank accounts in the merchant's or end customer's name. Customers pay by ordinary bank transfer, such as ACH, Wire, or RTP in the US, and deposits auto-convert into stablecoins that can be held or settled to local currency. No foreign entity and no separate bank relationship per market.",{"q":3350,"a":3351},"Which local payment rails can stablecoin payouts reach?","Through BlindPay: Pix, TED, and Boleto in Brazil; SPEI in Mexico; PSE in Colombia; Transfers 3.0 in Argentina; ACH, RTP, and domestic wire in the US; SEPA across 40 SEPA-zone countries; and SWIFT (POBO\u002FCOBO) for everywhere else, covering 100+ countries and 80+ currencies.",{"q":3353,"a":3354},"Is it legal to move merchant payments across borders with stablecoins?","Yes, when the provider holds the required licenses in the markets it serves and runs KYB on businesses and KYC on individuals. The merchant stays responsible for its own tax and accounting records. Rules differ by country, for example Brazil's virtual asset service provider regime and MiCA in the European Union, so check the provider's published licenses.",{},"---\ntitle: \"How global merchants get paid across borders with stablecoins, no pre-funding required\"\nseoTitle: \"Cross-border merchant payments without pre-funding\"\ndescription: \"Pre-funding means parking local currency in every market before money moves. Stablecoin virtual accounts remove it. A worked example across 4 countries.\"\ndate: \"2026-09-02\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is pre-funding in cross-border payments?\"\n    a: \"Pre-funding means holding local currency balances in each country before a payment can go out there. A merchant or provider paying out in Brazil, Mexico, and Colombia needs reais, pesos, and Colombian pesos sitting in local accounts ahead of time. That capital is idle until spent, split across markets, and exposed to FX moves while it waits.\"\n  - q: \"How do stablecoins remove the need for pre-funding?\"\n    a: \"Value crosses the border as a dollar stablecoin like USDC or USDT and converts into local currency at execution time, at a quoted and locked rate. The merchant keeps one float in one place instead of balances in every market, and the payout reaches the local bank account over the local rail, such as Pix, SPEI, or SEPA, usually in minutes.\"\n  - q: \"How can merchants receive cross-border payments without a local entity?\"\n    a: \"With virtual accounts. BlindPay issues US and local bank accounts in the merchant's or end customer's name. Customers pay by ordinary bank transfer, such as ACH, Wire, or RTP in the US, and deposits auto-convert into stablecoins that can be held or settled to local currency. No foreign entity and no separate bank relationship per market.\"\n  - q: \"Which local payment rails can stablecoin payouts reach?\"\n    a: \"Through BlindPay: Pix, TED, and Boleto in Brazil; SPEI in Mexico; PSE in Colombia; Transfers 3.0 in Argentina; ACH, RTP, and domestic wire in the US; SEPA across 40 SEPA-zone countries; and SWIFT (POBO\u002FCOBO) for everywhere else, covering 100+ countries and 80+ currencies.\"\n  - q: \"Is it legal to move merchant payments across borders with stablecoins?\"\n    a: \"Yes, when the provider holds the required licenses in the markets it serves and runs KYB on businesses and KYC on individuals. The merchant stays responsible for its own tax and accounting records. Rules differ by country, for example Brazil's virtual asset service provider regime and MiCA in the European Union, so check the provider's published licenses.\"\n---\n\n**Pre-funding** means holding local currency balances in every market before a payment can move there: reais in Brazil, pesos in Mexico, euros in Europe, all parked in local accounts ahead of time. It ties up capital, spreads it thin, and exposes it to FX swings. **Stablecoin-based virtual accounts remove that requirement.** Value crosses the border as a digital dollar (USDC or USDT) and converts into local currency at execution, at a locked rate, then lands over the local rail in minutes. One float, in one place, instead of one per country.\n\nThat single change is what makes launching a new market a product decision instead of a treasury project.\n\n## Why do cross-border merchants pre-fund at all?\n\nBecause traditional rails can't move value across a border in real time.\n\nA payout to a Brazilian seller over SWIFT passes through correspondent banks, each settling on its own schedule, over one to five business days. If a provider promises \"instant\" payouts in Brazil on those rails, the only way to deliver is to already have reais in Brazil. So they pre-fund. They keep balances in nostro accounts in every market, sized to cover the next few days or weeks of payouts, and top them up with slow wires.\n\nThat model has four built-in costs:\n\n- **Trapped capital.** Money sitting in ten countries is money not working anywhere.\n- **Fragmented liquidity.** Brazil runs dry while Mexico sits on a surplus. Rebalancing takes days.\n- **FX exposure.** Every idle local balance moves with the currency while it waits.\n- **Banking hours.** Top-ups stop on weekends and holidays, so buffers have to cover them.\n\nWhoever carries those costs passes them on, usually as a wider FX spread on the merchant's payouts.\n\n## How do stablecoin rails change the model?\n\nThe stablecoin becomes the shared settlement asset across every market. Instead of pre-positioning reais, pesos, and euros, the merchant (or its provider) holds dollars in stablecoin form and converts at the moment a payment executes.\n\nThe flow looks like this:\n\n1. **Collect.** Customers pay into a virtual account by bank transfer, or pay in USDC\u002FUSDT directly. Bank deposits auto-convert into stablecoins.\n2. **Hold one float.** Balances sit in stablecoins, not in ten local accounts.\n3. **Quote.** When a payout is due, request a quote: amount, destination currency, destination account.\n4. **Convert at execution.** The rate is locked when the payment runs. No balance needed in the destination country beforehand.\n5. **Deliver over the local rail.** Pix in Brazil, SPEI in Mexico, SEPA in Europe. Minutes on instant rails.\n\nBlindPay settles this way by design: no capital pre-positioned in destination accounts before a payout clears. It runs 24\u002F7, so Saturday payouts don't wait for Monday top-ups. We wrote about why the stablecoin part should stay invisible to the merchant in [Stablecoin for the Ordinary](\u002Fblog\u002Fstablecoin-for-the-ordinary).\n\n## A worked example: one merchant, four markets\n\nA US-based marketplace pays sellers in **Brazil, Mexico, Colombia, and Europe**. Monthly payouts: $400,000 to Brazil, $300,000 to Mexico, $150,000 to Colombia, $150,000 to Europe. $1M a month total.\n\nThese figures are illustrative, but the shape is what every finance lead running multi-market payouts recognizes.\n\n| | Stablecoin virtual account model | Traditional pre-funded model |\n| --- | --- | --- |\n| **Capital parked in destination markets** | $0 in destination markets; one stablecoin float | Two weeks of payout buffer per market: about $500,000 |\n| **Cost of that capital at 8% a year** | None for destination buffers | About $40,000 a year, before FX losses on idle balances |\n| **Local bank relationships** | One API integration | Four, often with a local entity or partner in each |\n| **Time to launch a fifth market** | Days to weeks, once the market is covered and your KYB is done | Months: local entity or partner, bank account, compliance setup, then funding |\n| **Weekend payouts** | Yes, 24\u002F7 | Limited by top-up windows |\n| **Payout speed** | Minutes on Pix, SPEI, and other instant rails | Fast only while the local buffer lasts |\n| **FX pricing** | Quoted per payment, spread and payout fee itemized | Wider spreads to cover the provider's funding costs |\n\nThe $500,000 is the number that gets a CFO's attention. It's half a month of payouts doing nothing, spread across four currencies, losing value whenever one of them weakens against the dollar.\n\nThe launch time is the number that gets a founder's attention. Adding Argentina under the old model is a project. Under the stablecoin model, it's a new destination currency in the same API call: Transfers 3.0 to a CBU or CVU.\n\n## How does local payment rail orchestration work on the payout side?\n\nStablecoins handle the border. Local rails handle the last mile, and they're different in every country. Orchestration means picking the right rail per destination and handling its quirks so the merchant doesn't have to.\n\n| Destination | Rails BlindPay pays out on | Typical speed |\n| --- | --- | --- |\n| **Brazil** | Pix, TED, Boleto | Minutes on Pix, 24\u002F7 |\n| **Mexico** | SPEI | Minutes, 24\u002F7 |\n| **Colombia** | PSE | Usually minutes, within bank windows |\n| **Argentina** | Transfers 3.0 (CBU\u002FCVU) | Same day |\n| **United States** | ACH, RTP, domestic wire | Seconds on RTP; same day to 2 days on ACH |\n| **Europe** | SEPA, across 40 SEPA-zone countries | Same day or next day |\n| **Everywhere else** | SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations | 1 to 5 business days |\n\nBlindPay covers 100+ countries and 80+ currencies this way, from one integration. The full list is on the [coverage page](\u002Fcoverage).\n\nOn the collection side, [virtual accounts](\u002Fvirtual-accounts) do the reverse: BlindPay issues US and local bank accounts in your name or your customer's name. A US buyer pays by ACH or wire like any domestic invoice. The deposit auto-converts into stablecoins and can settle to your local currency right after. No US entity required. We covered this in detail when we launched [Named Virtual Accounts](\u002Fblog\u002Fintroducing-virtual-accounts).\n\n## What compliance does this model need?\n\nMoving money across borders without a local bank in every market doesn't mean moving it without rules. Doing this legitimately takes:\n\n- **KYB on the merchant.** Company documents, beneficial owners, business activity. See [what KYB is](\u002Fresources\u002Fmore\u002Fwhat-is-kyb).\n- **KYC on individual payees.** Sellers, contractors, and creators receiving payouts get verified before their first payment.\n- **Sanctions and watchlist screening** on every counterparty and transaction.\n- **On-chain monitoring** of the stablecoin leg for exposure to sanctioned or high-risk wallets.\n- **Local licensing** in each market the provider serves. Brazil, for example, licenses virtual asset service providers under its own regime; see our [PSAV explainer](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained). The EU runs MiCA.\n\nBlindPay runs KYC, KYB, sanctions screening, and transaction monitoring inside the same API, and publishes its licenses on the [licenses page](\u002Flicenses). The merchant stays responsible for its own tax and accounting records in each market.\n\n## Is this model right for your expansion plans?\n\nRun through this checklist:\n\n- You pay out, or plan to pay out, in **two or more countries**.\n- You currently keep, or would need to keep, **local balances** in those markets.\n- Your payees are **sellers, contractors, creators, or suppliers** who want local currency in a local bank account.\n- **Payout speed** matters to retention: sellers leave platforms that pay slowly.\n- You want to **launch new markets** without opening a bank relationship in each.\n- Your finance team wants **one reconciliation flow** instead of one per country.\n- You can complete **KYB** and collect KYC data from payees.\n\nThree or more checks, and the pre-funded model is probably costing you more than you think.\n\nFor more on the mechanics, read [stablecoin settlement explained](\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants), and for a cost breakdown, [stablecoin fees vs card processing fees](\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees). If you're comparing conversion partners, see [how to choose an on\u002Foff-ramp provider](\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider).\n\n## Expand without parking capital\n\nEvery market you add under the old model costs a bank relationship and a buffer. Under a stablecoin model it costs a destination currency. If you want to map your current payout flows against this model, [talk to the BlindPay team](\u002Fcontact).\n",{"title":2830,"description":3338},"Cross-border merchant payments without pre-funding","resources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding","7-ZVqJ4nPA3_S5CImE8jhuvK-ScQmS30HWKvSZ6yVrs",{"id":3362,"title":3363,"authors":6,"body":3364,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":3927,"description":3928,"extension":342,"faq":3929,"howto":6,"isBlog":359,"isChangelog":359,"meta":3945,"navigation":362,"path":225,"pillar":359,"products":6,"rawbody":3946,"role":6,"seo":3947,"seoTitle":3931,"stem":3948,"thumbnail":6,"updated":6,"__hash__":3949},"content\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times.md","How long does a stablecoin payout take? Settlement times by country and rail",{"type":8,"value":3365,"toc":3917},[3366,3369,3372,3375,3379,3385,3584,3591,3595,3598,3626,3629,3633,3636,3642,3707,3714,3731,3745,3749,3752,3758,3764,3770,3776,3785,3791,3795,3798,3808,3812,3815,3874,3879,3881,3896,3898,3913],[11,3367,3368],{},"A stablecoin payout takes as long as the local rail at the end of it. The on-chain leg settles in seconds to a couple of minutes. After that, the receiver gets funds instantly over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; in about one business day over TED, domestic wire, SEPA, and Colombian ACH; in about two business days over US ACH; and in up to five business days over SWIFT.",[11,3370,3371],{},"So \"stablecoin payouts are instant\" is half true. The stablecoin part is. The bank part is whatever the bank rail does.",[11,3373,3374],{},"Here's the full breakdown, with the rail-by-rail table, the steps that add time, and a few timelines you can reason about.",[18,3376,3378],{"id":3377},"what-are-the-settlement-times-by-rail","What are the settlement times by rail?",[11,3380,3381,3382,3384],{},"These are the estimated times of arrival for BlindPay payouts, by the ",[204,3383,206],{}," you set on the receiver's bank account.",[39,3386,3387,3406],{},[42,3388,3389],{},[45,3390,3391,3394,3396,3400,3403],{},[48,3392,3393],{},"Country",[48,3395,1088],{},[48,3397,3398],{},[204,3399,206],{},[48,3401,3402],{},"Estimated arrival",[48,3404,3405],{},"Runs 24\u002F7",[61,3407,3408,3425,3441,3459,3473,3489,3505,3521,3537,3552,3567],{},[45,3409,3410,3412,3415,3419,3422],{},[66,3411,3094],{},[66,3413,3414],{},"Pix",[66,3416,3417],{},[204,3418,1981],{},[66,3420,3421],{},"Instant",[66,3423,3424],{},"Yes",[45,3426,3427,3429,3432,3437,3439],{},[66,3428,3094],{},[66,3430,3431],{},"PIX Safe",[66,3433,3434],{},[204,3435,3436],{},"pix_safe",[66,3438,3421],{},[66,3440,3424],{},[45,3442,3443,3445,3448,3453,3456],{},[66,3444,3094],{},[66,3446,3447],{},"TED",[66,3449,3450],{},[204,3451,3452],{},"ted",[66,3454,3455],{},"~1 business day",[66,3457,3458],{},"No",[45,3460,3461,3463,3465,3469,3471],{},[66,3462,3107],{},[66,3464,3110],{},[66,3466,3467],{},[204,3468,1984],{},[66,3470,3421],{},[66,3472,3424],{},[45,3474,3475,3477,3480,3485,3487],{},[66,3476,3133],{},[66,3478,3479],{},"Transfers 3.0",[66,3481,3482],{},[204,3483,3484],{},"transfers_bitso",[66,3486,3421],{},[66,3488,3424],{},[45,3490,3491,3493,3496,3501,3503],{},[66,3492,3120],{},[66,3494,3495],{},"ACH",[66,3497,3498],{},[204,3499,3500],{},"ach_cop_bitso",[66,3502,3455],{},[66,3504,3458],{},[45,3506,3507,3509,3512,3517,3519],{},[66,3508,3146],{},[66,3510,3511],{},"RTP",[66,3513,3514],{},[204,3515,3516],{},"rtp",[66,3518,3421],{},[66,3520,3424],{},[45,3522,3523,3525,3528,3533,3535],{},[66,3524,3146],{},[66,3526,3527],{},"Domestic wire",[66,3529,3530],{},[204,3531,3532],{},"wire",[66,3534,3455],{},[66,3536,3458],{},[45,3538,3539,3541,3543,3547,3550],{},[66,3540,3146],{},[66,3542,3495],{},[66,3544,3545],{},[204,3546,1987],{},[66,3548,3549],{},"~2 business days",[66,3551,3458],{},[45,3553,3554,3556,3559,3563,3565],{},[66,3555,3159],{},[66,3557,3558],{},"SEPA",[66,3560,3561],{},[204,3562,1990],{},[66,3564,3455],{},[66,3566,3458],{},[45,3568,3569,3571,3574,3579,3582],{},[66,3570,1164],{},[66,3572,3573],{},"SWIFT",[66,3575,3576],{},[204,3577,3578],{},"international_swift",[66,3580,3581],{},"~5 business days",[66,3583,3458],{},[11,3585,3586,3587,227],{},"High transaction volumes can stretch any of these. SWIFT payouts have a 100 USD minimum and carry a UETR and an MT103 confirmation, so you can trace the wire. The live rail list is in the ",[136,3588,3590],{"href":3589},"\u002Fdocs\u002Fbank-accounts","bank accounts docs",[18,3592,3594],{"id":3593},"what-happens-between-send-and-arrived","What happens between \"send\" and \"arrived\"?",[11,3596,3597],{},"A stablecoin payout is four steps. Only one of them is slow, and it's rarely the blockchain.",[145,3599,3600,3606,3612,3620],{},[148,3601,3602,3605],{},[119,3603,3604],{},"Quote (you control this)."," Request a quote, show the receive amount, confirm. A quote is valid for five minutes by default, sometimes less on SEPA.",[148,3607,3608,3611],{},[119,3609,3610],{},"On-chain transfer (seconds to a couple of minutes)."," USDC or USDT moves from the funding wallet. Fast networks like Base, Polygon, Solana, and Stellar confirm in seconds.",[148,3613,3614,3617,3618,227],{},[119,3615,3616],{},"Compliance and conversion (usually seconds, sometimes a review)."," Screening runs on the payout. Most clear automatically. Some go to ",[204,3619,2030],{},[148,3621,3622,3625],{},[119,3623,3624],{},"Local delivery (the rail)."," This is the number in the table above.",[11,3627,3628],{},"Add them up and a Pix payout is minutes end to end. A SWIFT payout is days, and nearly all of that is SWIFT.",[18,3630,3632],{"id":3631},"why-would-a-payout-take-longer-than-the-table-says","Why would a payout take longer than the table says?",[11,3634,3635],{},"Three reasons, in order of how often they show up.",[11,3637,3638,3641],{},[119,3639,3640],{},"Cut-off times."," Banking rails have daily cut-offs. Submit after it and you're in the next business day's batch. In Eastern Time:",[39,3643,3644,3656],{},[42,3645,3646],{},[45,3647,3648,3650,3653],{},[48,3649,1088],{},[48,3651,3652],{},"Daily cut-off (ET)",[48,3654,3655],{},"Settlement after cut-off",[61,3657,3658,3667,3677,3685,3696],{},[45,3659,3660,3662,3665],{},[66,3661,3495],{},[66,3663,3664],{},"9:00 PM",[66,3666,1110],{},[45,3668,3669,3672,3675],{},[66,3670,3671],{},"Same-Day ACH",[66,3673,3674],{},"3:00 PM",[66,3676,1127],{},[45,3678,3679,3681,3683],{},[66,3680,3527],{},[66,3682,3674],{},[66,3684,1127],{},[45,3686,3687,3690,3693],{},[66,3688,3689],{},"International SWIFT",[66,3691,3692],{},"10:30 AM",[66,3694,3695],{},"Up to 5 business days",[45,3697,3698,3701,3704],{},[66,3699,3700],{},"TED (Brazil)",[66,3702,3703],{},"End of Brazilian banking day",[66,3705,3706],{},"Same or next banking day",[11,3708,3709,3710,227],{},"Business days exclude weekends, US federal holidays, and applicable international banking holidays. The full reference is in ",[136,3711,3713],{"href":3712},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times",[11,3715,3716,3719,3720,3722,3723,3725,3726,3730],{},[119,3717,3718],{},"Compliance holds."," A payout can land in ",[204,3721,2030],{}," for review. At BlindPay, every SWIFT payout starts in ",[204,3724,2030],{},", and USD ACH, wire, and RTP payouts pass through it too. Screening matches, unusually large amounts, and first-time activity can also trigger a hold. If compliance needs more information, it sends a request, and an unanswered request can end with the funds returned to the sender. Read ",[136,3727,3729],{"href":3728},"\u002Fdocs\u002Fkb\u002Fon-hold-transactions","on-hold transactions"," for how that works.",[11,3732,3733,3736,3737,3740,3741,3744],{},[119,3734,3735],{},"Bad bank details."," A wrong account number or a closed account means the receiving bank rejects the payment. The payout ends ",[204,3738,3739],{},"failed"," or ",[204,3742,3743],{},"refunded",". Stablecoin refunds go back to the originating wallet right away; fiat returns take as long as the receiving bank takes.",[18,3746,3748],{"id":3747},"what-do-real-timelines-look-like","What do real timelines look like?",[11,3750,3751],{},"A few scenarios. On USD and SWIFT payouts, review time comes on top of the rail time.",[11,3753,3754,3757],{},[119,3755,3756],{},"Saturday, 11:00 PM, 5,000 BRL to Brazil over Pix."," Quote, send, done. Reais land in minutes. Pix doesn't care that it's Saturday.",[11,3759,3760,3763],{},[119,3761,3762],{},"Tuesday, 2:00 PM ET, 20,000 MXN to Mexico over SPEI."," Minutes. SPEI runs around the clock too.",[11,3765,3766,3769],{},[119,3767,3768],{},"Friday, 4:00 PM ET, 3,000 USD to a US bank account over domestic wire."," That's after the 3:00 PM wire cut-off, so it goes out Monday and settles the same business day, plus any review time.",[11,3771,3772,3775],{},[119,3773,3774],{},"Friday, 4:00 PM ET, 3,000 USD over ACH."," Before the 9:00 PM ACH cut-off, so it's submitted Friday. About two business days means Tuesday, plus any review time.",[11,3777,3778,3781,3782,3784],{},[119,3779,3780],{},"Wednesday, 9:00 AM ET, 25,000 USD to a supplier in Hong Kong over SWIFT."," Before the 10:30 AM cut-off, starts in ",[204,3783,2030],{}," for review, then up to five business days on SWIFT, depending on the correspondent chain. Track it with the UETR.",[11,3786,3787,3790],{},[119,3788,3789],{},"Monday, noon, 2,000,000 COP to Colombia over ACH."," About one business day, so Tuesday.",[18,3792,3794],{"id":3793},"how-does-this-compare-with-a-traditional-wire","How does this compare with a traditional wire?",[11,3796,3797],{},"A SWIFT wire from a US bank to Brazil passes through one or two correspondent banks, each updating its own ledger and taking its own fee. That usually means 1 to 5 business days, and the receiving bank applies its own FX rate when the dollars arrive.",[11,3799,3800,3801,3804,3805,227],{},"The same payment as a stablecoin payout over Pix settles in minutes, at a rate you saw before you sent it. For corridors with an instant local rail, the difference is days versus minutes. For corridors that still end in SWIFT, the difference is smaller on speed and bigger on traceability and quote certainty. We go deeper in ",[136,3802,3803],{"href":1210},"stablecoins vs SWIFT for B2B payments",", and on what \"final\" actually means in ",[136,3806,3807],{"href":1243},"stablecoin API SLAs and settlement finality",[18,3809,3811],{"id":3810},"how-should-your-product-show-payout-timing","How should your product show payout timing?",[11,3813,3814],{},"A few things that save support tickets:",[171,3816,3817,3823,3842,3858,3868],{},[148,3818,3819,3822],{},[119,3820,3821],{},"Show the ETA per rail, not per provider."," \"Arrives in minutes\" for Pix, \"about 2 business days\" for ACH.",[148,3824,3825,3831,3832,1304,3835,1304,3838,1341,3840,227],{},[119,3826,3827,3828,3830],{},"Treat ",[204,3829,2030],{}," as pending."," Don't retry, don't show an error. It resolves to ",[204,3833,3834],{},"processing",[204,3836,3837],{},"completed",[204,3839,3739],{},[204,3841,3743],{},[148,3843,3844,3847,3848,3851,3852,1313,3854,3857],{},[119,3845,3846],{},"Listen for webhooks."," ",[204,3849,3850],{},"payout.update"," fires on every status change, including ",[204,3853,3739],{},[204,3855,3856],{},"payout.complete"," fires when local currency is delivered.",[148,3859,3860,3867],{},[119,3861,3862,3863,3866],{},"Read ",[204,3864,3865],{},"expires_at"," from the quote."," It's in epoch milliseconds. Don't hardcode five minutes.",[148,3869,3870,3873],{},[119,3871,3872],{},"Store the rail reference."," On SWIFT, keep the UETR; your finance team will ask for it.",[11,3875,3876,3877,227],{},"The full integration flow, with endpoints and statuses, is in ",[136,3878,2713],{"href":2712},[18,3880,294],{"id":293},[11,3882,3883,3885,3886,3889,3890,3892,3893,227],{},[136,3884,300],{"href":299}," pays out USDC and USDT as local currency over every rail in the table above, with ",[136,3887,3888],{"href":363},"no pre-funding",", a quote that locks the receive amount before you commit, and compliance screening inside the API. Payouts start from your own stablecoin wallet or from a ",[136,3891,139],{"href":138}," that converts ACH, wire, and SWIFT deposits into stablecoins. Rails cover Brazil, Mexico, Colombia, Argentina, the US, Europe, and 100+ countries over SWIFT (POBO\u002FCOBO). ",[136,3894,3895],{"href":307},"Pricing is published",[18,3897,312],{"id":311},[11,3899,3900,3901,1337,3904,3907,3908,1337,3910,3912],{},"List your top three payout countries and look up each rail in the table. If any of them has an instant rail, that's the corridor to launch first. Then create a development instance, run a test payout, and use the sentinel amounts ",[204,3902,3903],{},"66600",[204,3905,3906],{},"77700"," to force ",[204,3909,3739],{},[204,3911,3743],{}," so your UI handles the slow paths before real users hit them.",[11,3914,3915],{},[324,3916,326],{},{"title":328,"searchDepth":329,"depth":329,"links":3918},[3919,3920,3921,3922,3923,3924,3925,3926],{"id":3377,"depth":329,"text":3378},{"id":3593,"depth":329,"text":3594},{"id":3631,"depth":329,"text":3632},{"id":3747,"depth":329,"text":3748},{"id":3793,"depth":329,"text":3794},{"id":3810,"depth":329,"text":3811},{"id":293,"depth":329,"text":294},{"id":311,"depth":329,"text":312},"2026-08-06","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.",[3930,3933,3936,3939,3942],{"q":3931,"a":3932},"How long does a stablecoin payout take?","The on-chain leg takes seconds to a couple of minutes. The total time depends on the local rail at the end: instant over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; about one business day over TED, wire, SEPA, and Colombian ACH; about two business days over US ACH; and up to five business days over SWIFT.",{"q":3934,"a":3935},"Do stablecoin payouts work on weekends?","On instant rails, yes. Pix, SPEI, and Transfers 3.0 run 24\u002F7, so a payout sent on a Saturday night lands on a Saturday night. ACH, wire, SEPA, TED, and SWIFT follow banking days, so a weekend payout on those rails is delivered after the next business day opens.",{"q":3937,"a":3938},"Why is my stablecoin payout on hold?","A payout can sit in on_hold for compliance or banking review before release. At BlindPay every SWIFT payout starts in on_hold, and USD ACH, wire, and RTP payouts pass through it. Screening matches or unusual activity can also trigger a hold. A hold is a status, not an error, so show it as pending and do not retry.",{"q":3940,"a":3941},"What is the fastest country to send a stablecoin payout to?","Brazil, Mexico, and Argentina are among the fastest, because Pix, SPEI, and Transfers 3.0 settle in minutes, around the clock. In the US, RTP settles instantly, though USD payouts pass through a review step first.",{"q":3943,"a":3944},"How long is a stablecoin payout quote valid?","At BlindPay a payout quote is valid for five minutes by default and can be shorter for SEPA. Read expires_at from the response, which is in epoch milliseconds, rather than hardcoding the window.",{"author":361},"---\ntitle: \"How long does a stablecoin payout take? Settlement times by country and rail\"\nseoTitle: \"How long does a stablecoin payout take?\"\ndescription: \"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.\"\ndate: \"2026-08-06\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"How long does a stablecoin payout take?\"\n    a: \"The on-chain leg takes seconds to a couple of minutes. The total time depends on the local rail at the end: instant over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; about one business day over TED, wire, SEPA, and Colombian ACH; about two business days over US ACH; and up to five business days over SWIFT.\"\n  - q: \"Do stablecoin payouts work on weekends?\"\n    a: \"On instant rails, yes. Pix, SPEI, and Transfers 3.0 run 24\u002F7, so a payout sent on a Saturday night lands on a Saturday night. ACH, wire, SEPA, TED, and SWIFT follow banking days, so a weekend payout on those rails is delivered after the next business day opens.\"\n  - q: \"Why is my stablecoin payout on hold?\"\n    a: \"A payout can sit in on_hold for compliance or banking review before release. At BlindPay every SWIFT payout starts in on_hold, and USD ACH, wire, and RTP payouts pass through it. Screening matches or unusual activity can also trigger a hold. A hold is a status, not an error, so show it as pending and do not retry.\"\n  - q: \"What is the fastest country to send a stablecoin payout to?\"\n    a: \"Brazil, Mexico, and Argentina are among the fastest, because Pix, SPEI, and Transfers 3.0 settle in minutes, around the clock. In the US, RTP settles instantly, though USD payouts pass through a review step first.\"\n  - q: \"How long is a stablecoin payout quote valid?\"\n    a: \"At BlindPay a payout quote is valid for five minutes by default and can be shorter for SEPA. Read expires_at from the response, which is in epoch milliseconds, rather than hardcoding the window.\"\n---\n\nA stablecoin payout takes as long as the local rail at the end of it. The on-chain leg settles in seconds to a couple of minutes. After that, the receiver gets funds instantly over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; in about one business day over TED, domestic wire, SEPA, and Colombian ACH; in about two business days over US ACH; and in up to five business days over SWIFT.\n\nSo \"stablecoin payouts are instant\" is half true. The stablecoin part is. The bank part is whatever the bank rail does.\n\nHere's the full breakdown, with the rail-by-rail table, the steps that add time, and a few timelines you can reason about.\n\n## What are the settlement times by rail?\n\nThese are the estimated times of arrival for BlindPay payouts, by the `type` you set on the receiver's bank account.\n\n| Country | Rail | `type` | Estimated arrival | Runs 24\u002F7 |\n| --- | --- | --- | --- | --- |\n| Brazil | Pix | `pix` | Instant | Yes |\n| Brazil | PIX Safe | `pix_safe` | Instant | Yes |\n| Brazil | TED | `ted` | ~1 business day | No |\n| Mexico | SPEI | `spei_bitso` | Instant | Yes |\n| Argentina | Transfers 3.0 | `transfers_bitso` | Instant | Yes |\n| Colombia | ACH | `ach_cop_bitso` | ~1 business day | No |\n| United States | RTP | `rtp` | Instant | Yes |\n| United States | Domestic wire | `wire` | ~1 business day | No |\n| United States | ACH | `ach` | ~2 business days | No |\n| Europe | SEPA | `sepa` | ~1 business day | No |\n| Global | SWIFT | `international_swift` | ~5 business days | No |\n\nHigh transaction volumes can stretch any of these. SWIFT payouts have a 100 USD minimum and carry a UETR and an MT103 confirmation, so you can trace the wire. The live rail list is in the [bank accounts docs](\u002Fdocs\u002Fbank-accounts).\n\n## What happens between \"send\" and \"arrived\"?\n\nA stablecoin payout is four steps. Only one of them is slow, and it's rarely the blockchain.\n\n1. **Quote (you control this).** Request a quote, show the receive amount, confirm. A quote is valid for five minutes by default, sometimes less on SEPA.\n2. **On-chain transfer (seconds to a couple of minutes).** USDC or USDT moves from the funding wallet. Fast networks like Base, Polygon, Solana, and Stellar confirm in seconds.\n3. **Compliance and conversion (usually seconds, sometimes a review).** Screening runs on the payout. Most clear automatically. Some go to `on_hold`.\n4. **Local delivery (the rail).** This is the number in the table above.\n\nAdd them up and a Pix payout is minutes end to end. A SWIFT payout is days, and nearly all of that is SWIFT.\n\n## Why would a payout take longer than the table says?\n\nThree reasons, in order of how often they show up.\n\n**Cut-off times.** Banking rails have daily cut-offs. Submit after it and you're in the next business day's batch. In Eastern Time:\n\n| Rail | Daily cut-off (ET) | Settlement after cut-off |\n| --- | --- | --- |\n| ACH | 9:00 PM | 1 to 3 business days |\n| Same-Day ACH | 3:00 PM | Same business day |\n| Domestic wire | 3:00 PM | Same business day |\n| International SWIFT | 10:30 AM | Up to 5 business days |\n| TED (Brazil) | End of Brazilian banking day | Same or next banking day |\n\nBusiness days exclude weekends, US federal holidays, and applicable international banking holidays. The full reference is in [cut-off times](\u002Fdocs\u002Fkb\u002Fcut-off-times).\n\n**Compliance holds.** A payout can land in `on_hold` for review. At BlindPay, every SWIFT payout starts in `on_hold`, and USD ACH, wire, and RTP payouts pass through it too. Screening matches, unusually large amounts, and first-time activity can also trigger a hold. If compliance needs more information, it sends a request, and an unanswered request can end with the funds returned to the sender. Read [on-hold transactions](\u002Fdocs\u002Fkb\u002Fon-hold-transactions) for how that works.\n\n**Bad bank details.** A wrong account number or a closed account means the receiving bank rejects the payment. The payout ends `failed` or `refunded`. Stablecoin refunds go back to the originating wallet right away; fiat returns take as long as the receiving bank takes.\n\n## What do real timelines look like?\n\nA few scenarios. On USD and SWIFT payouts, review time comes on top of the rail time.\n\n**Saturday, 11:00 PM, 5,000 BRL to Brazil over Pix.** Quote, send, done. Reais land in minutes. Pix doesn't care that it's Saturday.\n\n**Tuesday, 2:00 PM ET, 20,000 MXN to Mexico over SPEI.** Minutes. SPEI runs around the clock too.\n\n**Friday, 4:00 PM ET, 3,000 USD to a US bank account over domestic wire.** That's after the 3:00 PM wire cut-off, so it goes out Monday and settles the same business day, plus any review time.\n\n**Friday, 4:00 PM ET, 3,000 USD over ACH.** Before the 9:00 PM ACH cut-off, so it's submitted Friday. About two business days means Tuesday, plus any review time.\n\n**Wednesday, 9:00 AM ET, 25,000 USD to a supplier in Hong Kong over SWIFT.** Before the 10:30 AM cut-off, starts in `on_hold` for review, then up to five business days on SWIFT, depending on the correspondent chain. Track it with the UETR.\n\n**Monday, noon, 2,000,000 COP to Colombia over ACH.** About one business day, so Tuesday.\n\n## How does this compare with a traditional wire?\n\nA SWIFT wire from a US bank to Brazil passes through one or two correspondent banks, each updating its own ledger and taking its own fee. That usually means 1 to 5 business days, and the receiving bank applies its own FX rate when the dollars arrive.\n\nThe same payment as a stablecoin payout over Pix settles in minutes, at a rate you saw before you sent it. For corridors with an instant local rail, the difference is days versus minutes. For corridors that still end in SWIFT, the difference is smaller on speed and bigger on traceability and quote certainty. We go deeper in [stablecoins vs SWIFT for B2B payments](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments), and on what \"final\" actually means in [stablecoin API SLAs and settlement finality](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality).\n\n## How should your product show payout timing?\n\nA few things that save support tickets:\n\n- **Show the ETA per rail, not per provider.** \"Arrives in minutes\" for Pix, \"about 2 business days\" for ACH.\n- **Treat `on_hold` as pending.** Don't retry, don't show an error. It resolves to `processing`, `completed`, `failed`, or `refunded`.\n- **Listen for webhooks.** `payout.update` fires on every status change, including `failed`, and `payout.complete` fires when local currency is delivered.\n- **Read `expires_at` from the quote.** It's in epoch milliseconds. Don't hardcode five minutes.\n- **Store the rail reference.** On SWIFT, keep the UETR; your finance team will ask for it.\n\nThe full integration flow, with endpoints and statuses, is in [how to integrate a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api).\n\n## Where does BlindPay fit?\n\n[BlindPay](\u002Fglobal-payments) pays out USDC and USDT as local currency over every rail in the table above, with [no pre-funding](\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts), a quote that locks the receive amount before you commit, and compliance screening inside the API. Payouts start from your own stablecoin wallet or from a [virtual USD account](\u002Fvirtual-accounts) that converts ACH, wire, and SWIFT deposits into stablecoins. Rails cover Brazil, Mexico, Colombia, Argentina, the US, Europe, and 100+ countries over SWIFT (POBO\u002FCOBO). [Pricing is published](\u002Fpricing).\n\n## What to do next\n\nList your top three payout countries and look up each rail in the table. If any of them has an instant rail, that's the corridor to launch first. Then create a development instance, run a test payout, and use the sentinel amounts `66600` and `77700` to force `failed` and `refunded` so your UI handles the slow paths before real users hit them.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":3363,"description":3928},"resources\u002Fmore\u002Fstablecoin-payout-settlement-times","FI86xHLyDVgCbEjXVeXYL7sjJQxJv0AEuLOJmGqJVfU",{"id":3951,"title":3952,"authors":6,"body":3953,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":4266,"description":4267,"extension":342,"faq":4268,"howto":6,"isBlog":359,"isChangelog":359,"meta":4281,"navigation":362,"path":3318,"pillar":359,"products":6,"rawbody":4282,"role":6,"seo":4283,"seoTitle":4284,"stem":4285,"thumbnail":6,"updated":4266,"__hash__":4286},"content\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider.md","How to choose the best on\u002Foff ramp provider for your fintech app",{"type":8,"value":3954,"toc":4244},[3955,3960,3963,3967,3970,3974,3985,3988,3992,3995,3998,4001,4012,4015,4019,4022,4025,4036,4043,4047,4050,4053,4064,4072,4076,4079,4082,4096,4103,4107,4110,4113,4124,4127,4131,4212,4216,4219,4229,4232,4240],[11,3956,3957],{},[324,3958,3959],{},"Reading time: about 7 minutes.",[11,3961,3962],{},"Six criteria decide whether an on\u002Foff ramp provider will work for a fintech app: the corridors it actually supports, whether it returns live quotes or batch rates, how fast fiat settles, which licenses it holds, how good the API is, and how deep its liquidity runs. Score every candidate on all six before looking at price.",[18,3964,3966],{"id":3965},"what-corridors-does-the-provider-actually-support","What corridors does the provider actually support?",[11,3968,3969],{},"A corridor is a specific pair: a fiat currency and rail on one side, a token and network on the other. A provider that lists \"Brazil\" may support Pix payouts in BRL but not Pix collection, or USDC on Polygon but not on Base. Coverage lists are marketing; corridors are what you integrate.",[967,3971,3973],{"id":3972},"how-to-test-it","How to test it",[171,3975,3976,3979,3982],{},[148,3977,3978],{},"Ask for the exact list of currency, rail, token, and network combinations, in both directions, as a machine-readable table rather than a map with flags.",[148,3980,3981],{},"Ask which corridors are live in production today versus \"coming soon\", and how many customers transact on each.",[148,3983,3984],{},"Run a sandbox quote on each corridor you need and confirm the response includes a real rate, not a placeholder.",[11,3986,3987],{},"A good answer is a published coverage page that names rails and networks per country, and a sandbox that returns quotes on every corridor you plan to ship.",[18,3989,3991],{"id":3990},"does-the-provider-offer-live-quotes-or-batch-rates","Does the provider offer live quotes or batch rates?",[11,3993,3994],{},"A live quote is a rate determined at the moment of the request, returned with a quote ID and an expiry, and honored on confirmation. A batch rate is a cached rate refreshed on a schedule, with the difference absorbed either by the provider's spread or by your user at settlement.",[11,3996,3997],{},"Batch rates are not acceptable for consumer-facing products. If the rate on the confirmation screen is not the rate that settles, every rate move becomes a support ticket or a hidden fee.",[967,3999,3973],{"id":4000},"how-to-test-it-1",[171,4002,4003,4006,4009],{},[148,4004,4005],{},"Request two quotes ten seconds apart on a volatile corridor such as USDC to ARS and check whether the rate changed.",[148,4007,4008],{},"Confirm the quote response includes a quote ID and an expiry timestamp, and that the transaction endpoint requires that ID.",[148,4010,4011],{},"Submit a transaction with an expired quote ID in the sandbox and check that it is rejected with a specific error code.",[11,4013,4014],{},"A good answer is a synchronous quote endpoint that returns rate, fee, quote ID, and expiry in one response, with the rate held for a stated window. Providers with their own liquidity, BlindPay among them, can do this because the quote comes from their own book rather than a partner's cache.",[18,4016,4018],{"id":4017},"how-fast-does-fiat-actually-settle","How fast does fiat actually settle?",[11,4020,4021],{},"The on-chain leg is fast on every provider. Fiat settlement is where providers differ, and it is set by the rail and by how the provider is connected to it: a direct connection to Pix or SPEI settles in seconds, while a provider routing through a partner bank adds hours.",[967,4023,3973],{"id":4024},"how-to-test-it-2",[171,4026,4027,4030,4033],{},[148,4028,4029],{},"Ask for median and p95 settlement time per rail over the last 90 days, not \"typically minutes\".",[148,4031,4032],{},"Ask whether the provider connects to each rail directly or through an intermediary, and who that intermediary is.",[148,4034,4035],{},"Run a small live payout on each rail after go-live and time it, including a Friday evening and a weekend.",[11,4037,4038,4039,4042],{},"A good answer is per-rail numbers the provider will put in writing, with instant rails settling in under five minutes end to end. The ",[136,4040,4041],{"href":1243},"settlement finality guide"," covers what to ask for in an SLA.",[18,4044,4046],{"id":4045},"what-licenses-and-compliance-does-the-provider-hold","What licenses and compliance does the provider hold?",[11,4048,4049],{},"Converting fiat to crypto is money transmission in the US and a regulated virtual asset service almost everywhere else. If the provider is not licensed for a corridor, either you are the unlicensed party or the flow stops when a bank asks questions.",[967,4051,3973],{"id":4052},"how-to-test-it-3",[171,4054,4055,4058,4061],{},[148,4056,4057],{},"Ask for the FinCEN MSB registration number and the list of state money transmitter licenses or exemptions, and check them against the public registries.",[148,4059,4060],{},"For each non-US corridor, ask which local authorization covers it (for example, a VASP registration in Brazil under Central Bank rules) and whether it is held directly or through a partner.",[148,4062,4063],{},"Ask what KYC, KYB, sanctions screening, and travel rule data exchange run inside the flow, and which vendors provide them.",[11,4065,4066,4067,4071],{},"A good answer is a public licenses page, registrations that match the registries, and compliance that runs inside the API rather than being left to you. What a ",[136,4068,4070],{"href":4069},"\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp","VASP"," is and who needs one is covered separately.",[18,4073,4075],{"id":4074},"how-good-is-the-api","How good is the API?",[11,4077,4078],{},"The API is the product. Sales calls, dashboards, and roadmaps are irrelevant if the endpoints are inconsistent, the errors are opaque, or the sandbox behaves differently from production.",[967,4080,3973],{"id":4081},"how-to-test-it-4",[171,4083,4084,4087,4090,4093],{},[148,4085,4086],{},"Ask for the OpenAPI spec before the first call and read it: consistent naming, typed errors, and idempotency keys on every write are the minimum.",[148,4088,4089],{},"Build the full happy path in sandbox (onboard a receiver, quote, execute, receive the webhook) and count the hours it takes.",[148,4091,4092],{},"Trigger failure paths in sandbox: expired quote, rejected bank account, insufficient balance, and confirm each returns a distinct error code.",[148,4094,4095],{},"Check that webhooks are signed, retried on failure, and carry enough data to reconcile without a follow-up request.",[11,4097,4098,4099,4102],{},"A good answer is an OpenAPI spec you can generate a client from, a sandbox that exercises failure paths, and a full integration in under two weeks. ",[136,4100,4101],{"href":754},"Sandbox vs production"," explains what sandboxes cannot show you.",[18,4104,4106],{"id":4105},"how-deep-is-the-liquidity","How deep is the liquidity?",[11,4108,4109],{},"Liquidity depth is how much volume a provider can convert on a corridor before the rate degrades. A provider that quotes a tight spread on $500 and a wide one on $50,000 is deep enough for consumer flows and not for treasury or payroll.",[967,4111,3973],{"id":4112},"how-to-test-it-5",[171,4114,4115,4118,4121],{},[148,4116,4117],{},"Request quotes for $500, $5,000, and $50,000 on the same corridor within a minute and compare the effective rate on each.",[148,4119,4120],{},"Ask for the maximum single-transaction size and the daily volume cap per corridor, and whether either changes without notice.",[148,4122,4123],{},"Ask whether the provider holds its own liquidity or routes to third parties, and what happens to your quote when a third party fails.",[11,4125,4126],{},"A good answer is a spread that barely moves between $500 and $50,000 and volume caps stated per corridor in writing. A provider that will not quote $50,000 in sandbox is telling you something.",[18,4128,4130],{"id":4129},"how-do-the-six-criteria-compare-side-by-side","How do the six criteria compare side by side?",[39,4132,4133,4145],{},[42,4134,4135],{},[45,4136,4137,4139,4142],{},[48,4138,2475],{},[48,4140,4141],{},"What good looks like",[48,4143,4144],{},"Red flag to watch for",[61,4146,4147,4158,4169,4180,4190,4201],{},[45,4148,4149,4152,4155],{},[66,4150,4151],{},"Corridor coverage",[66,4153,4154],{},"Published rails and networks per country, all live in sandbox",[66,4156,4157],{},"A map of countries with no rails or networks named",[45,4159,4160,4163,4166],{},[66,4161,4162],{},"Live quotes",[66,4164,4165],{},"Quote ID, expiry, and rate held for a stated window",[66,4167,4168],{},"Rate \"indicative\", settled at a rate you learn afterward",[45,4170,4171,4174,4177],{},[66,4172,4173],{},"Fiat settlement",[66,4175,4176],{},"Per-rail p95 in writing, instant rails under 5 minutes",[66,4178,4179],{},"\"Typically minutes\" with no numbers",[45,4181,4182,4184,4187],{},[66,4183,1995],{},[66,4185,4186],{},"Public licenses page matching FinCEN and state registries",[66,4188,4189],{},"Compliance \"handled by our partner\", partner unnamed",[45,4191,4192,4195,4198],{},[66,4193,4194],{},"API quality",[66,4196,4197],{},"OpenAPI spec, typed errors, signed webhooks, sandbox parity",[66,4199,4200],{},"PDF documentation, generic 400 errors, sandbox with canned responses",[45,4202,4203,4206,4209],{},[66,4204,4205],{},"Liquidity depth",[66,4207,4208],{},"Spread stable from $500 to $50,000, caps stated per corridor",[66,4210,4211],{},"Sandbox refuses large quotes, caps \"depend on market conditions\"",[18,4213,4215],{"id":4214},"how-should-you-score-providers-against-these-criteria","How should you score providers against these criteria?",[11,4217,4218],{},"Score each provider 1 to 3 on each criterion: 1 means it fails the test, 2 means it passes with caveats, 3 means it passes cleanly. Do the scoring after running the tests, not after the sales call.",[11,4220,4221,4222,4225,4226,227],{},"Weight corridor coverage, live quotes, and licensing as ",[119,4223,4224],{},"High",". Weight fiat settlement, API quality, and liquidity depth as ",[119,4227,4228],{},"Medium",[11,4230,4231],{},"A score of 1 on any High-weight criterion disqualifies the provider regardless of its total. A provider that does not cover your corridor, cannot hold a rate, or is not licensed where you operate is not a cheaper option, it is a liability you will replace within a year.",[11,4233,4234,4235,4239],{},"Among providers that clear the High-weight bar, sum the Medium scores and pick the highest. Use price to break ties only, and read the ",[136,4236,4238],{"href":4237},"\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained","pricing explainer"," first so that blended rates do not distort the comparison.",[11,4241,4242],{},[324,4243,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":4245},[4246,4249,4252,4255,4258,4261,4264,4265],{"id":3965,"depth":329,"text":3966,"children":4247},[4248],{"id":3972,"depth":1404,"text":3973},{"id":3990,"depth":329,"text":3991,"children":4250},[4251],{"id":4000,"depth":1404,"text":3973},{"id":4017,"depth":329,"text":4018,"children":4253},[4254],{"id":4024,"depth":1404,"text":3973},{"id":4045,"depth":329,"text":4046,"children":4256},[4257],{"id":4052,"depth":1404,"text":3973},{"id":4074,"depth":329,"text":4075,"children":4259},[4260],{"id":4081,"depth":1404,"text":3973},{"id":4105,"depth":329,"text":4106,"children":4262},[4263],{"id":4112,"depth":1404,"text":3973},{"id":4129,"depth":329,"text":4130},{"id":4214,"depth":329,"text":4215},"2026-08-28","Six criteria for evaluating a crypto on\u002Foff ramp provider: corridor coverage, live quotes, settlement speed, licensing, API quality, and liquidity.",[4269,4272,4275,4278],{"q":4270,"a":4271},"Is a crypto exchange a good on-ramp provider for a fintech app?","Usually not. Exchanges are built for traders who hold balances on the exchange, not for apps that need fiat in and tokens out to a user's wallet through an API. Their APIs are trading APIs, their compliance is scoped to their own customers, and their fiat rails are limited to the countries where they hold banking. A dedicated on\u002Foff ramp provider is built for embedding.",{"q":4273,"a":4274},"What is the best on\u002Foff ramp API?","The best on\u002Foff ramp API for a given app is the one that covers its corridors with live executable quotes, settles fiat over instant local rails, holds the licenses those corridors require, and documents everything in an OpenAPI spec with a sandbox that behaves like production. No single provider wins every corridor, so score candidates against those criteria for your actual countries and volumes.",{"q":4276,"a":4277},"What is the difference between an on-ramp provider and a crypto exchange?","An on-ramp provider converts a fiat payment into tokens delivered to a wallet, or the reverse, as a service embedded in another product. A crypto exchange is a venue where users trade assets and hold balances in an account. An exchange may run an on-ramp for its own users, but it is not designed to be the conversion layer inside someone else's app.",{"q":4279,"a":4280},"How long does it take to integrate an on\u002Foff ramp provider?","A working sandbox integration covering onboarding, quoting, and payout takes one to two engineering weeks with a well-documented REST API. Going live takes longer because of compliance review on your side and the provider's, typically two to six weeks. Providers without an OpenAPI spec or without sandbox parity add weeks of back-and-forth to that estimate.",{"author":361},"---\ntitle: \"How to choose the best on\u002Foff ramp provider for your fintech app\"\nseoTitle: \"How to choose an on\u002Foff ramp provider\"\ndescription: \"Six criteria for evaluating a crypto on\u002Foff ramp provider: corridor coverage, live quotes, settlement speed, licensing, API quality, and liquidity.\"\ndate: \"2026-08-28\"\nupdated: \"2026-08-28\"\nauthor: \"BlindPay Team\"\ncategory: \"payments\"\nfaq:\n  - q: \"Is a crypto exchange a good on-ramp provider for a fintech app?\"\n    a: \"Usually not. Exchanges are built for traders who hold balances on the exchange, not for apps that need fiat in and tokens out to a user's wallet through an API. Their APIs are trading APIs, their compliance is scoped to their own customers, and their fiat rails are limited to the countries where they hold banking. A dedicated on\u002Foff ramp provider is built for embedding.\"\n  - q: \"What is the best on\u002Foff ramp API?\"\n    a: \"The best on\u002Foff ramp API for a given app is the one that covers its corridors with live executable quotes, settles fiat over instant local rails, holds the licenses those corridors require, and documents everything in an OpenAPI spec with a sandbox that behaves like production. No single provider wins every corridor, so score candidates against those criteria for your actual countries and volumes.\"\n  - q: \"What is the difference between an on-ramp provider and a crypto exchange?\"\n    a: \"An on-ramp provider converts a fiat payment into tokens delivered to a wallet, or the reverse, as a service embedded in another product. A crypto exchange is a venue where users trade assets and hold balances in an account. An exchange may run an on-ramp for its own users, but it is not designed to be the conversion layer inside someone else's app.\"\n  - q: \"How long does it take to integrate an on\u002Foff ramp provider?\"\n    a: \"A working sandbox integration covering onboarding, quoting, and payout takes one to two engineering weeks with a well-documented REST API. Going live takes longer because of compliance review on your side and the provider's, typically two to six weeks. Providers without an OpenAPI spec or without sandbox parity add weeks of back-and-forth to that estimate.\"\n---\n\n*Reading time: about 7 minutes.*\n\nSix criteria decide whether an on\u002Foff ramp provider will work for a fintech app: the corridors it actually supports, whether it returns live quotes or batch rates, how fast fiat settles, which licenses it holds, how good the API is, and how deep its liquidity runs. Score every candidate on all six before looking at price.\n\n## What corridors does the provider actually support?\n\nA corridor is a specific pair: a fiat currency and rail on one side, a token and network on the other. A provider that lists \"Brazil\" may support Pix payouts in BRL but not Pix collection, or USDC on Polygon but not on Base. Coverage lists are marketing; corridors are what you integrate.\n\n### How to test it\n\n- Ask for the exact list of currency, rail, token, and network combinations, in both directions, as a machine-readable table rather than a map with flags.\n- Ask which corridors are live in production today versus \"coming soon\", and how many customers transact on each.\n- Run a sandbox quote on each corridor you need and confirm the response includes a real rate, not a placeholder.\n\nA good answer is a published coverage page that names rails and networks per country, and a sandbox that returns quotes on every corridor you plan to ship.\n\n## Does the provider offer live quotes or batch rates?\n\nA live quote is a rate determined at the moment of the request, returned with a quote ID and an expiry, and honored on confirmation. A batch rate is a cached rate refreshed on a schedule, with the difference absorbed either by the provider's spread or by your user at settlement.\n\nBatch rates are not acceptable for consumer-facing products. If the rate on the confirmation screen is not the rate that settles, every rate move becomes a support ticket or a hidden fee.\n\n### How to test it\n\n- Request two quotes ten seconds apart on a volatile corridor such as USDC to ARS and check whether the rate changed.\n- Confirm the quote response includes a quote ID and an expiry timestamp, and that the transaction endpoint requires that ID.\n- Submit a transaction with an expired quote ID in the sandbox and check that it is rejected with a specific error code.\n\nA good answer is a synchronous quote endpoint that returns rate, fee, quote ID, and expiry in one response, with the rate held for a stated window. Providers with their own liquidity, BlindPay among them, can do this because the quote comes from their own book rather than a partner's cache.\n\n## How fast does fiat actually settle?\n\nThe on-chain leg is fast on every provider. Fiat settlement is where providers differ, and it is set by the rail and by how the provider is connected to it: a direct connection to Pix or SPEI settles in seconds, while a provider routing through a partner bank adds hours.\n\n### How to test it\n\n- Ask for median and p95 settlement time per rail over the last 90 days, not \"typically minutes\".\n- Ask whether the provider connects to each rail directly or through an intermediary, and who that intermediary is.\n- Run a small live payout on each rail after go-live and time it, including a Friday evening and a weekend.\n\nA good answer is per-rail numbers the provider will put in writing, with instant rails settling in under five minutes end to end. The [settlement finality guide](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality) covers what to ask for in an SLA.\n\n## What licenses and compliance does the provider hold?\n\nConverting fiat to crypto is money transmission in the US and a regulated virtual asset service almost everywhere else. If the provider is not licensed for a corridor, either you are the unlicensed party or the flow stops when a bank asks questions.\n\n### How to test it\n\n- Ask for the FinCEN MSB registration number and the list of state money transmitter licenses or exemptions, and check them against the public registries.\n- For each non-US corridor, ask which local authorization covers it (for example, a VASP registration in Brazil under Central Bank rules) and whether it is held directly or through a partner.\n- Ask what KYC, KYB, sanctions screening, and travel rule data exchange run inside the flow, and which vendors provide them.\n\nA good answer is a public licenses page, registrations that match the registries, and compliance that runs inside the API rather than being left to you. What a [VASP](\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp) is and who needs one is covered separately.\n\n## How good is the API?\n\nThe API is the product. Sales calls, dashboards, and roadmaps are irrelevant if the endpoints are inconsistent, the errors are opaque, or the sandbox behaves differently from production.\n\n### How to test it\n\n- Ask for the OpenAPI spec before the first call and read it: consistent naming, typed errors, and idempotency keys on every write are the minimum.\n- Build the full happy path in sandbox (onboard a receiver, quote, execute, receive the webhook) and count the hours it takes.\n- Trigger failure paths in sandbox: expired quote, rejected bank account, insufficient balance, and confirm each returns a distinct error code.\n- Check that webhooks are signed, retried on failure, and carry enough data to reconcile without a follow-up request.\n\nA good answer is an OpenAPI spec you can generate a client from, a sandbox that exercises failure paths, and a full integration in under two weeks. [Sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) explains what sandboxes cannot show you.\n\n## How deep is the liquidity?\n\nLiquidity depth is how much volume a provider can convert on a corridor before the rate degrades. A provider that quotes a tight spread on $500 and a wide one on $50,000 is deep enough for consumer flows and not for treasury or payroll.\n\n### How to test it\n\n- Request quotes for $500, $5,000, and $50,000 on the same corridor within a minute and compare the effective rate on each.\n- Ask for the maximum single-transaction size and the daily volume cap per corridor, and whether either changes without notice.\n- Ask whether the provider holds its own liquidity or routes to third parties, and what happens to your quote when a third party fails.\n\nA good answer is a spread that barely moves between $500 and $50,000 and volume caps stated per corridor in writing. A provider that will not quote $50,000 in sandbox is telling you something.\n\n## How do the six criteria compare side by side?\n\n| Criterion | What good looks like | Red flag to watch for |\n| --- | --- | --- |\n| Corridor coverage | Published rails and networks per country, all live in sandbox | A map of countries with no rails or networks named |\n| Live quotes | Quote ID, expiry, and rate held for a stated window | Rate \"indicative\", settled at a rate you learn afterward |\n| Fiat settlement | Per-rail p95 in writing, instant rails under 5 minutes | \"Typically minutes\" with no numbers |\n| Licensing | Public licenses page matching FinCEN and state registries | Compliance \"handled by our partner\", partner unnamed |\n| API quality | OpenAPI spec, typed errors, signed webhooks, sandbox parity | PDF documentation, generic 400 errors, sandbox with canned responses |\n| Liquidity depth | Spread stable from $500 to $50,000, caps stated per corridor | Sandbox refuses large quotes, caps \"depend on market conditions\" |\n\n## How should you score providers against these criteria?\n\nScore each provider 1 to 3 on each criterion: 1 means it fails the test, 2 means it passes with caveats, 3 means it passes cleanly. Do the scoring after running the tests, not after the sales call.\n\nWeight corridor coverage, live quotes, and licensing as **High**. Weight fiat settlement, API quality, and liquidity depth as **Medium**.\n\nA score of 1 on any High-weight criterion disqualifies the provider regardless of its total. A provider that does not cover your corridor, cannot hold a rate, or is not licensed where you operate is not a cheaper option, it is a liability you will replace within a year.\n\nAmong providers that clear the High-weight bar, sum the Medium scores and pick the highest. Use price to break ties only, and read the [pricing explainer](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) first so that blended rates do not distort the comparison.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":3952,"description":4267},"How to choose an on\u002Foff ramp provider","resources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","Vm3rl_G7eInXYpm91JLnsyxl24S-2lweRdfhUuuO8nA",{"id":4288,"title":4289,"authors":6,"body":4290,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":4620,"description":4621,"extension":342,"faq":4622,"howto":6,"isBlog":359,"isChangelog":359,"meta":4635,"navigation":362,"path":4636,"pillar":359,"products":6,"rawbody":4637,"role":6,"seo":4638,"seoTitle":4639,"stem":4640,"thumbnail":6,"updated":6,"__hash__":4641},"content\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform.md","How to evaluate a payment orchestration platform for cross-border payments",{"type":8,"value":4291,"toc":4609},[4292,4295,4298,4302,4305,4308,4311,4322,4325,4329,4332,4334,4348,4358,4362,4365,4367,4378,4381,4385,4388,4390,4401,4407,4412,4416,4419,4421,4432,4435,4442,4446,4449,4451,4462,4472,4476,4479,4490,4496,4499,4503,4585,4587,4590,4605],[11,4293,4294],{},"Evaluating a payment orchestration platform for cross-border payments comes down to six things: which rails and corridors it reaches, whose compliance program covers each corridor, how good the developer experience is, how fast money settles and whether you have to pre-fund it, how transparent the FX is, and what it costs all-in.",[11,4296,4297],{},"Run every vendor through the same six. The ones that fail usually fail on the same two: corridor coverage and FX transparency.",[18,4299,4301],{"id":4300},"_1-rail-and-corridor-coverage","1. Rail and corridor coverage",[11,4303,4304],{},"Coverage is the first filter because nothing downstream matters if the platform cannot reach your markets. Check the specific pairs you send, not the marketing count of supported countries.",[11,4306,4307],{},"Look for depth on three rail types: SWIFT for the corridors that still demand a wire, local rails for the last mile (Pix in Brazil, SPEI in Mexico, SEPA in the euro area, ACH in the US), and stablecoin settlement for the corridors where correspondent chains are long and slow.",[11,4309,4310],{},"Ask:",[171,4312,4313,4316,4319],{},[148,4314,4315],{},"Which exact currency pairs and destination rails do you support today, in production, not on the roadmap?",[148,4317,4318],{},"What is the maximum single payout size per corridor, and what happens above it?",[148,4320,4321],{},"When a rail is down, what is the documented fallback, and has it been exercised?",[11,4323,4324],{},"A vendor strong in Europe may not deliver over Pix or SPEI at all. Coverage maps are marketing until you test a corridor in the sandbox.",[18,4326,4328],{"id":4327},"_2-compliance-coverage-per-corridor","2. Compliance coverage per corridor",[11,4330,4331],{},"The question is not whether a platform \"handles compliance\". It is who holds the regulatory relationship in each corridor and where the checks run.",[11,4333,4310],{},[171,4335,4336,4342,4345],{},[148,4337,4338,4339,4341],{},"Who runs KYC and ",[136,4340,3301],{"href":3211}," on receivers, you or the platform, and which licenses or agent relationships back that in each market?",[148,4343,4344],{},"Do sanctions screening and transaction monitoring run before funds move, or after?",[148,4346,4347],{},"How do you handle corridor-specific rules: Brazil's Central Bank Resolutions 519 through 521, MiCA in the EU, the GENIUS Act and Treasury rulemaking in the US?",[11,4349,4350,4351,1223,4355,4357],{},"If the answer to the first is \"you do\", the integration is far larger than the API docs suggest, and you are building a compliance program, not connecting to one. Screening that runs before funds move blocks a payment while the money is still yours. Screening that runs after freezes money already in flight. Our notes on ",[136,4352,4354],{"href":4353},"\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments","real-time transaction monitoring",[136,4356,1036],{"href":1035}," go deeper.",[18,4359,4361],{"id":4360},"_3-developer-experience","3. Developer experience",[11,4363,4364],{},"Payment code is the code you debug at 2am during a payout run. Documentation quality is a proxy for how the rest of the platform is built.",[11,4366,4310],{},[171,4368,4369,4372,4375],{},[148,4370,4371],{},"Is there a public sandbox with realistic test data, reachable today without a sales call?",[148,4373,4374],{},"Is there an OpenAPI spec, a real API reference with request and response examples, and SDKs for the languages we use?",[148,4376,4377],{},"Do webhooks cover every state transition, and are money-moving endpoints idempotent?",[11,4379,4380],{},"Error semantics are the tell. A production-grade platform surfaces every failure as a typed state you can branch on: receiver failed sanctions screening, Pix key name does not match the payout name, payout held pending a compliance information request. A weak one returns a 500 and an email address. You will hit all three of those cases in your first quarter.",[18,4382,4384],{"id":4383},"_4-settlement-speed-and-pre-funding","4. Settlement speed and pre-funding",[11,4386,4387],{},"Speed and working capital are the same question asked twice.",[11,4389,4310],{},[171,4391,4392,4395,4398],{},[148,4393,4394],{},"How long from API call to funds credited in the recipient's account, per corridor, including the local leg?",[148,4396,4397],{},"Do we need to pre-fund local accounts to hit that speed, and if so, how much?",[148,4399,4400],{},"What are the cut-off times, and does the rail run on weekends?",[11,4402,4403,4404,227],{},"Pre-funding is the cost nobody puts on the invoice. Holding two weeks of payout volume in three countries is millions of dollars of dead capital plus continuous FX exposure. A platform that settles at payout time removes that line entirely, which is the operational case for ",[136,4405,4406],{"href":289},"stablecoin settlement inside an orchestration strategy",[11,4408,4409,4410,227],{},"Also confirm what \"settled\" means on each rail. On-chain transfers are final on confirmation. Pix is final in seconds. ACH debits can be returned for days. Treating those as equivalent is how reconciliation breaks. See the ",[136,4411,4041],{"href":1243},[18,4413,4415],{"id":4414},"_5-fx-transparency","5. FX transparency",[11,4417,4418],{},"This is where the money is, and where most vendors are quietest.",[11,4420,4310],{},[171,4422,4423,4426,4429],{},[148,4424,4425],{},"Does the API return the exact rate, fee, and receive amount before we commit funds, and is that quote binding for a defined window?",[148,4427,4428],{},"What is the spread against mid-market, stated as a number, per corridor?",[148,4430,4431],{},"Are the FX spread and the transaction fee itemized separately, or blended into one rate?",[11,4433,4434],{},"A \"no fees\" pitch with a 3 percent spread is more expensive than a flat $2 fee on a 0.5 percent spread. On a $100,000 payout that is $3,000 in FX against about $502 all-in. Same payment, same day, and only one of them is advertised as free.",[11,4436,4437,4438,227],{},"Indicative quotes are the other trap. Indicative means the provider fills at whatever the book gives it and the receiver may get less than you were shown. Binding quotes are the standard to hold vendors to, for the reasons in ",[136,4439,4441],{"href":4440},"\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","on\u002Foff-ramp liquidity and live quotes",[18,4443,4445],{"id":4444},"_6-pricing-model","6. Pricing model",[11,4447,4448],{},"Three components, and you need all three to compare anything: per-transaction fees (flat, percentage, or both), the FX spread, and fixed costs like monthly minimums or committed volume tiers.",[11,4450,4310],{},[171,4452,4453,4456,4459],{},[148,4454,4455],{},"Is pricing published, or does it require a sales call?",[148,4457,4458],{},"Are there minimums, platform fees, or volume commitments?",[148,4460,4461],{},"Run our ten most common payments through your quote API: what does the receiver actually get?",[11,4463,4464,4465,4468,4469,4471],{},"That last question is the only fair comparison. Flat fees favor large transfers, percentages favor small ones, and the spread swamps both at volume. ",[136,4466,4467],{"href":307},"BlindPay publishes pricing",", and the ",[136,4470,4238],{"href":4237}," walks through why a blended rate hides the number you need.",[18,4473,4475],{"id":4474},"domestic-card-orchestrators-vs-cross-border-native-platforms","Domestic card orchestrators vs cross-border-native platforms",[11,4477,4478],{},"These get lumped together and they solve different problems.",[11,4480,4481,4484,4485,4489],{},[119,4482,4483],{},"Domestic card orchestrators"," route between acquirers to lift authorization rates. The transaction stays on one rail, in one currency, under one regulator. Success is measured in approval percentage points, and the engineering is about retry logic, network tokens, and issuer behavior. Real work, useful product, wrong tool for cross-border payouts. The ",[136,4486,4488],{"href":4487},"\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","orchestration vs gateway breakdown"," covers where that line sits.",[11,4491,4492,4495],{},[119,4493,4494],{},"Cross-border-native platforms"," route across rails that do not share a currency, a settlement time, or a regulator. Success is measured in delivery time, all-in cost, and how many corridors you can open without a new banking relationship. The engineering is about FX execution, per-corridor compliance, local rail integrations, and reconciliation across incompatible settlement models.",[11,4497,4498],{},"A platform built for acquirer routing can add a payout API. It will not have the licensing depth, the local rail integrations, or the FX machinery, and you find that out in the corridors that matter most. Judge on the criteria above, not the category label.",[18,4500,4502],{"id":4501},"summary-checklist","Summary checklist",[39,4504,4505,4517],{},[42,4506,4507],{},[45,4508,4509,4511,4514],{},[48,4510,2475],{},[48,4512,4513],{},"Why it matters",[48,4515,4516],{},"Question to ask",[61,4518,4519,4530,4541,4552,4563,4574],{},[45,4520,4521,4524,4527],{},[66,4522,4523],{},"Rail and corridor coverage",[66,4525,4526],{},"Nothing else matters if it cannot reach your markets",[66,4528,4529],{},"Which exact pairs are live in production today, and what is the documented fallback per rail?",[45,4531,4532,4535,4538],{},[66,4533,4534],{},"Compliance per corridor",[66,4536,4537],{},"Determines whether you connect to a program or build one",[66,4539,4540],{},"Who holds the license in each market, and do checks run before funds move?",[45,4542,4543,4546,4549],{},[66,4544,4545],{},"Developer experience",[66,4547,4548],{},"Error semantics decide your 2am debugging",[66,4550,4551],{},"Is there a public sandbox, an OpenAPI spec, and a typed error for every failure mode?",[45,4553,4554,4557,4560],{},[66,4555,4556],{},"Settlement and pre-funding",[66,4558,4559],{},"Pre-funding is dead capital plus FX exposure",[66,4561,4562],{},"How much do we hold locally to hit your quoted speed?",[45,4564,4565,4568,4571],{},[66,4566,4567],{},"FX transparency",[66,4569,4570],{},"The spread usually costs more than every fee combined",[66,4572,4573],{},"Is the quote binding, and are spread and fee itemized separately?",[45,4575,4576,4579,4582],{},[66,4577,4578],{},"Pricing model",[66,4580,4581],{},"Only the receive amount is comparable across vendors",[66,4583,4584],{},"Run our ten typical payments: what does the receiver actually get?",[18,4586,312],{"id":311},[11,4588,4589],{},"Pick your three highest-volume corridors. Send the same six questions to every vendor on your list, in writing, and run ten real payments through each sandbox. Compare on one number: what the receiver gets, and how long it took.",[11,4591,4592,4593,4596,4597,4601,4602,227],{},"The vendors that cannot give you that number in an API response are telling you something. ",[136,4594,4595],{"href":1335},"See coverage by country",", read ",[136,4598,4600],{"href":4599},"\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration","what payment orchestration is"," for the layers behind these criteria, or ",[136,4603,1331],{"href":648,"rel":4604},[414],[11,4606,4607],{},[324,4608,326],{},{"title":328,"searchDepth":329,"depth":329,"links":4610},[4611,4612,4613,4614,4615,4616,4617,4618,4619],{"id":4300,"depth":329,"text":4301},{"id":4327,"depth":329,"text":4328},{"id":4360,"depth":329,"text":4361},{"id":4383,"depth":329,"text":4384},{"id":4414,"depth":329,"text":4415},{"id":4444,"depth":329,"text":4445},{"id":4474,"depth":329,"text":4475},{"id":4501,"depth":329,"text":4502},{"id":311,"depth":329,"text":312},"2026-09-16","Six criteria for a cross-border orchestration platform: rail coverage, compliance per corridor, developer experience, speed, FX, and pricing.",[4623,4626,4629,4632],{"q":4624,"a":4625},"What is the single most important criterion when choosing a payment orchestration platform?","Corridor coverage, because nothing else matters if the platform cannot reach your markets. Once two or more vendors clear that bar, FX transparency is the tiebreaker, since the spread usually costs more than every listed fee combined.",{"q":4627,"a":4628},"Should I pick a domestic card orchestrator or a cross-border-native one?","It depends on the problem. Card orchestrators optimize authorization rates across acquirers on one rail in one country. Cross-border-native platforms route across rails, currencies, and regulators. The engineering behind each is different enough that few vendors do both well.",{"q":4630,"a":4631},"How long should a payment orchestration integration take?","Sandbox on day one, a first test payout within the week, and production traffic in two to four weeks. If the vendor's answer starts with a scheduled call and a PDF, expect months.",{"q":4633,"a":4634},"How do I compare pricing across orchestration vendors fairly?","Run the same payment through each vendor's quote and compare the amount the receiver actually gets. Listed fees are comparable across vendors, but FX spreads are where the real difference sits and they are often not disclosed.",{"author":361},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","---\ntitle: \"How to evaluate a payment orchestration platform for cross-border payments\"\nseoTitle: \"How to evaluate a payment orchestration platform\"\ndescription: \"Six criteria for a cross-border orchestration platform: rail coverage, compliance per corridor, developer experience, speed, FX, and pricing.\"\ndate: \"2026-09-16\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the single most important criterion when choosing a payment orchestration platform?\"\n    a: \"Corridor coverage, because nothing else matters if the platform cannot reach your markets. Once two or more vendors clear that bar, FX transparency is the tiebreaker, since the spread usually costs more than every listed fee combined.\"\n  - q: \"Should I pick a domestic card orchestrator or a cross-border-native one?\"\n    a: \"It depends on the problem. Card orchestrators optimize authorization rates across acquirers on one rail in one country. Cross-border-native platforms route across rails, currencies, and regulators. The engineering behind each is different enough that few vendors do both well.\"\n  - q: \"How long should a payment orchestration integration take?\"\n    a: \"Sandbox on day one, a first test payout within the week, and production traffic in two to four weeks. If the vendor's answer starts with a scheduled call and a PDF, expect months.\"\n  - q: \"How do I compare pricing across orchestration vendors fairly?\"\n    a: \"Run the same payment through each vendor's quote and compare the amount the receiver actually gets. Listed fees are comparable across vendors, but FX spreads are where the real difference sits and they are often not disclosed.\"\n---\n\nEvaluating a payment orchestration platform for cross-border payments comes down to six things: which rails and corridors it reaches, whose compliance program covers each corridor, how good the developer experience is, how fast money settles and whether you have to pre-fund it, how transparent the FX is, and what it costs all-in.\n\nRun every vendor through the same six. The ones that fail usually fail on the same two: corridor coverage and FX transparency.\n\n## 1. Rail and corridor coverage\n\nCoverage is the first filter because nothing downstream matters if the platform cannot reach your markets. Check the specific pairs you send, not the marketing count of supported countries.\n\nLook for depth on three rail types: SWIFT for the corridors that still demand a wire, local rails for the last mile (Pix in Brazil, SPEI in Mexico, SEPA in the euro area, ACH in the US), and stablecoin settlement for the corridors where correspondent chains are long and slow.\n\nAsk:\n\n- Which exact currency pairs and destination rails do you support today, in production, not on the roadmap?\n- What is the maximum single payout size per corridor, and what happens above it?\n- When a rail is down, what is the documented fallback, and has it been exercised?\n\nA vendor strong in Europe may not deliver over Pix or SPEI at all. Coverage maps are marketing until you test a corridor in the sandbox.\n\n## 2. Compliance coverage per corridor\n\nThe question is not whether a platform \"handles compliance\". It is who holds the regulatory relationship in each corridor and where the checks run.\n\nAsk:\n\n- Who runs KYC and [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) on receivers, you or the platform, and which licenses or agent relationships back that in each market?\n- Do sanctions screening and transaction monitoring run before funds move, or after?\n- How do you handle corridor-specific rules: Brazil's Central Bank Resolutions 519 through 521, MiCA in the EU, the GENIUS Act and Treasury rulemaking in the US?\n\nIf the answer to the first is \"you do\", the integration is far larger than the API docs suggest, and you are building a compliance program, not connecting to one. Screening that runs before funds move blocks a payment while the money is still yours. Screening that runs after freezes money already in flight. Our notes on [real-time transaction monitoring](\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments) and the [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) go deeper.\n\n## 3. Developer experience\n\nPayment code is the code you debug at 2am during a payout run. Documentation quality is a proxy for how the rest of the platform is built.\n\nAsk:\n\n- Is there a public sandbox with realistic test data, reachable today without a sales call?\n- Is there an OpenAPI spec, a real API reference with request and response examples, and SDKs for the languages we use?\n- Do webhooks cover every state transition, and are money-moving endpoints idempotent?\n\nError semantics are the tell. A production-grade platform surfaces every failure as a typed state you can branch on: receiver failed sanctions screening, Pix key name does not match the payout name, payout held pending a compliance information request. A weak one returns a 500 and an email address. You will hit all three of those cases in your first quarter.\n\n## 4. Settlement speed and pre-funding\n\nSpeed and working capital are the same question asked twice.\n\nAsk:\n\n- How long from API call to funds credited in the recipient's account, per corridor, including the local leg?\n- Do we need to pre-fund local accounts to hit that speed, and if so, how much?\n- What are the cut-off times, and does the rail run on weekends?\n\nPre-funding is the cost nobody puts on the invoice. Holding two weeks of payout volume in three countries is millions of dollars of dead capital plus continuous FX exposure. A platform that settles at payout time removes that line entirely, which is the operational case for [stablecoin settlement inside an orchestration strategy](\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts).\n\nAlso confirm what \"settled\" means on each rail. On-chain transfers are final on confirmation. Pix is final in seconds. ACH debits can be returned for days. Treating those as equivalent is how reconciliation breaks. See the [settlement finality guide](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality).\n\n## 5. FX transparency\n\nThis is where the money is, and where most vendors are quietest.\n\nAsk:\n\n- Does the API return the exact rate, fee, and receive amount before we commit funds, and is that quote binding for a defined window?\n- What is the spread against mid-market, stated as a number, per corridor?\n- Are the FX spread and the transaction fee itemized separately, or blended into one rate?\n\nA \"no fees\" pitch with a 3 percent spread is more expensive than a flat $2 fee on a 0.5 percent spread. On a $100,000 payout that is $3,000 in FX against about $502 all-in. Same payment, same day, and only one of them is advertised as free.\n\nIndicative quotes are the other trap. Indicative means the provider fills at whatever the book gives it and the receiver may get less than you were shown. Binding quotes are the standard to hold vendors to, for the reasons in [on\u002Foff-ramp liquidity and live quotes](\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes).\n\n## 6. Pricing model\n\nThree components, and you need all three to compare anything: per-transaction fees (flat, percentage, or both), the FX spread, and fixed costs like monthly minimums or committed volume tiers.\n\nAsk:\n\n- Is pricing published, or does it require a sales call?\n- Are there minimums, platform fees, or volume commitments?\n- Run our ten most common payments through your quote API: what does the receiver actually get?\n\nThat last question is the only fair comparison. Flat fees favor large transfers, percentages favor small ones, and the spread swamps both at volume. [BlindPay publishes pricing](\u002Fpricing), and the [pricing explainer](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) walks through why a blended rate hides the number you need.\n\n## Domestic card orchestrators vs cross-border-native platforms\n\nThese get lumped together and they solve different problems.\n\n**Domestic card orchestrators** route between acquirers to lift authorization rates. The transaction stays on one rail, in one currency, under one regulator. Success is measured in approval percentage points, and the engineering is about retry logic, network tokens, and issuer behavior. Real work, useful product, wrong tool for cross-border payouts. The [orchestration vs gateway breakdown](\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway) covers where that line sits.\n\n**Cross-border-native platforms** route across rails that do not share a currency, a settlement time, or a regulator. Success is measured in delivery time, all-in cost, and how many corridors you can open without a new banking relationship. The engineering is about FX execution, per-corridor compliance, local rail integrations, and reconciliation across incompatible settlement models.\n\nA platform built for acquirer routing can add a payout API. It will not have the licensing depth, the local rail integrations, or the FX machinery, and you find that out in the corridors that matter most. Judge on the criteria above, not the category label.\n\n## Summary checklist\n\n| Criterion | Why it matters | Question to ask |\n| --- | --- | --- |\n| Rail and corridor coverage | Nothing else matters if it cannot reach your markets | Which exact pairs are live in production today, and what is the documented fallback per rail? |\n| Compliance per corridor | Determines whether you connect to a program or build one | Who holds the license in each market, and do checks run before funds move? |\n| Developer experience | Error semantics decide your 2am debugging | Is there a public sandbox, an OpenAPI spec, and a typed error for every failure mode? |\n| Settlement and pre-funding | Pre-funding is dead capital plus FX exposure | How much do we hold locally to hit your quoted speed? |\n| FX transparency | The spread usually costs more than every fee combined | Is the quote binding, and are spread and fee itemized separately? |\n| Pricing model | Only the receive amount is comparable across vendors | Run our ten typical payments: what does the receiver actually get? |\n\n## What to do next\n\nPick your three highest-volume corridors. Send the same six questions to every vendor on your list, in writing, and run ten real payments through each sandbox. Compare on one number: what the receiver gets, and how long it took.\n\nThe vendors that cannot give you that number in an API response are telling you something. [See coverage by country](\u002Fcoverage), read [what payment orchestration is](\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration) for the layers behind these criteria, or [start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":4289,"description":4621},"How to evaluate a payment orchestration platform","resources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","S8v3FbtxO37Sp3066RWJBqzbqIPclpLf5oDoopqE7uU",{"id":4643,"title":4644,"authors":6,"body":4645,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":2803,"description":5784,"extension":342,"faq":5785,"howto":5801,"isBlog":359,"isChangelog":359,"meta":5828,"navigation":362,"path":5829,"pillar":359,"products":6,"rawbody":5830,"role":6,"seo":5831,"seoTitle":5832,"stem":5833,"thumbnail":6,"updated":5834,"__hash__":5835},"content\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api.md","How to issue stablecoin-funded cards through an API: a developer's guide",{"type":8,"value":4646,"toc":5766},[4647,4652,4658,4661,4668,4672,4675,4769,4772,4776,4779,4873,4876,4890,4894,4898,4901,4905,4908,4912,5067,5082,5086,5154,5157,5161,5273,5280,5284,5287,5586,5589,5609,5613,5616,5620,5623,5634,5638,5641,5645,5648,5709,5717,5721,5744,5748,5758,5762],[11,4648,4649],{},[324,4650,4651],{},"Reading time: about 8 minutes.",[11,4653,4654,4657],{},[119,4655,4656],{},"Summary:"," API-based stablecoin card issuing means creating cardholders, cards, and spending decisions through a card issuing provider's REST API, while funding each purchase from a stablecoin balance such as USDC. The provider handles the network connection and the sponsor bank. Your code decides who gets a card, how it is funded, and which transactions to approve.",[11,4659,4660],{},"This guide is for developers and technical founders deciding whether to build or integrate. It covers what each path requires, the objects any issuing API has to expose, and an integration flow you can follow as a checklist.",[11,4662,4663,4664,227],{},"One note on scope. The endpoints and payloads below are a generic shape shared by most issuing APIs, not one provider's reference. Names change between providers. The objects and their order do not. For the concepts behind the card itself, read ",[136,4665,4667],{"href":4666},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing","what stablecoin card issuing is",[18,4669,4671],{"id":4670},"should-you-build-card-issuing-in-house-or-use-an-api","Should you build card issuing in-house or use an API?",[11,4673,4674],{},"Building means becoming the issuer's technology and compliance partner yourself. Buying means integrating one that already is.",[39,4676,4677,4690],{},[42,4678,4679],{},[45,4680,4681,4684,4687],{},[48,4682,4683],{},"Requirement",[48,4685,4686],{},"Build in-house",[48,4688,4689],{},"Integrate an issuing API",[61,4691,4692,4703,4714,4725,4736,4747,4758],{},[45,4693,4694,4697,4700],{},[66,4695,4696],{},"Sponsor bank",[66,4698,4699],{},"Negotiate and sign a BIN sponsorship agreement",[66,4701,4702],{},"Provided; you are approved under the provider's program",[45,4704,4705,4708,4711],{},[66,4706,4707],{},"Card network",[66,4709,4710],{},"Meet Visa or Mastercard program and certification requirements",[66,4712,4713],{},"Provided",[45,4715,4716,4719,4722],{},[66,4717,4718],{},"Card data security",[66,4720,4721],{},"PCI DSS compliance for storing and processing card numbers",[66,4723,4724],{},"Provider's vault; you never touch the full card number",[45,4726,4727,4730,4733],{},[66,4728,4729],{},"Authorization engine",[66,4731,4732],{},"Build or license an issuer processor",[66,4734,4735],{},"Provided; you answer a webhook",[45,4737,4738,4741,4744],{},[66,4739,4740],{},"Compliance program",[66,4742,4743],{},"Written AML program, KYC, monitoring, filings, under the sponsor's oversight",[66,4745,4746],{},"Shared: the provider runs most checks, you own your program's policies",[45,4748,4749,4752,4755],{},[66,4750,4751],{},"Disputes and chargebacks",[66,4753,4754],{},"Build dispute operations",[66,4756,4757],{},"Provider workflow plus API events",[45,4759,4760,4763,4766],{},[66,4761,4762],{},"Time to first card",[66,4764,4765],{},"Typically a year or more",[66,4767,4768],{},"Sandbox in a day; production after program approval",[11,4770,4771],{},"Build only if card issuing is the product and you have the capital and patience for bank and network negotiations. Everyone else integrates, and spends the saved time on the ledger and UX, which is where programs actually differ.",[18,4773,4775],{"id":4774},"what-does-a-stablecoin-card-issuing-api-need-to-expose","What does a stablecoin card issuing API need to expose?",[11,4777,4778],{},"A usable issuing API has seven objects. If a provider is missing one, you will end up building it.",[39,4780,4781,4794],{},[42,4782,4783],{},[45,4784,4785,4788,4791],{},[48,4786,4787],{},"Object",[48,4789,4790],{},"What it does",[48,4792,4793],{},"Fields to look for",[61,4795,4796,4807,4818,4829,4840,4851,4862],{},[45,4797,4798,4801,4804],{},[66,4799,4800],{},"Cardholder",[66,4802,4803],{},"The verified person or business the card belongs to",[66,4805,4806],{},"KYC status, country, rejection reasons",[45,4808,4809,4812,4815],{},[66,4810,4811],{},"Funding source",[66,4813,4814],{},"The stablecoin balance that pays for purchases",[66,4816,4817],{},"Token, network, wallet address, custody model",[45,4819,4820,4823,4826],{},[66,4821,4822],{},"Card",[66,4824,4825],{},"A virtual or physical card",[66,4827,4828],{},"Status, limits, merchant category rules, expiry",[45,4830,4831,4834,4837],{},[66,4832,4833],{},"Authorization request",[66,4835,4836],{},"A real-time question from the network: approve this?",[66,4838,4839],{},"Amount, currency, merchant, MCC, deadline",[45,4841,4842,4845,4848],{},[66,4843,4844],{},"Transaction",[66,4846,4847],{},"The lifecycle after approval",[66,4849,4850],{},"Clearing amount, reversals, refunds, FX rate",[45,4852,4853,4856,4859],{},[66,4854,4855],{},"Dispute",[66,4857,4858],{},"A cardholder challenge to a transaction",[66,4860,4861],{},"Reason code, deadline, evidence",[45,4863,4864,4867,4870],{},[66,4865,4866],{},"Webhook endpoint",[66,4868,4869],{},"Where events are delivered",[66,4871,4872],{},"Signing secret, retry policy, event types",[11,4874,4875],{},"Two questions separate stablecoin-native providers from traditional ones bolted onto a wallet:",[171,4877,4878,4884],{},[148,4879,4880,4883],{},[119,4881,4882],{},"When does conversion happen?"," Just in time at authorization, so balances stay in USDC, or ahead of time into a fiat card balance.",[148,4885,4886,4889],{},[119,4887,4888],{},"Who holds the stablecoins?"," A custodial program wallet, or your own wallet with an on-chain spending allowance the provider can draw from.",[18,4891,4893],{"id":4892},"integration-flow-step-by-step","Integration flow, step by step",[967,4895,4897],{"id":4896},"_1-get-sandbox-credentials","1. Get sandbox credentials",[11,4899,4900],{},"Sign up, get sandbox keys, and before writing code ask for three lists: supported card currencies, cardholder countries the sponsor bank accepts, and stablecoins and networks the funding source supports. These decide your product more than any endpoint.",[967,4902,4904],{"id":4903},"_2-pass-kyb-for-your-business","2. Pass KYB for your business",[11,4906,4907],{},"The provider and its sponsor bank verify your company before approving the program: registration, beneficial owners, business model, and expected volumes. The approval sets your limits and card types. Plan for this to take longer than the code.",[967,4909,4911],{"id":4910},"_3-create-a-cardholder-and-pass-kyc","3. Create a cardholder and pass KYC",[4913,4914,4918],"pre",{"className":4915,"code":4916,"language":4917,"meta":328,"style":328},"language-bash shiki shiki-themes github-light","POST \u002Fv1\u002Fcardholders\nContent-Type: application\u002Fjson\nIdempotency-Key: 1c9f...\n\n{\n  \"type\": \"individual\",\n  \"first_name\": \"Ana\",\n  \"last_name\": \"Souza\",\n  \"date_of_birth\": \"1994-03-12\",\n  \"country\": \"BR\",\n  \"tax_id\": \"000.000.000-00\",\n  \"address\": { \"line1\": \"...\", \"city\": \"Recife\", \"postal_code\": \"...\" }\n}\n","bash",[204,4919,4920,4933,4941,4949,4955,4962,4974,4985,4996,5007,5018,5029,5061],{"__ignoreMap":328},[4921,4922,4925,4929],"span",{"class":4923,"line":4924},"line",1,[4921,4926,4928],{"class":4927},"s7eDp","POST",[4921,4930,4932],{"class":4931},"sYBdl"," \u002Fv1\u002Fcardholders\n",[4921,4934,4935,4938],{"class":4923,"line":329},[4921,4936,4937],{"class":4927},"Content-Type:",[4921,4939,4940],{"class":4931}," application\u002Fjson\n",[4921,4942,4943,4946],{"class":4923,"line":1404},[4921,4944,4945],{"class":4927},"Idempotency-Key:",[4921,4947,4948],{"class":4931}," 1c9f...\n",[4921,4950,4952],{"class":4923,"line":4951},4,[4921,4953,4954],{"emptyLinePlaceholder":362},"\n",[4921,4956,4958],{"class":4923,"line":4957},5,[4921,4959,4961],{"class":4960},"sgsFI","{\n",[4921,4963,4965,4968,4971],{"class":4923,"line":4964},6,[4921,4966,4967],{"class":4927},"  \"type\"",[4921,4969,580],{"class":4970},"sYu0t",[4921,4972,4973],{"class":4931}," \"individual\",\n",[4921,4975,4977,4980,4982],{"class":4923,"line":4976},7,[4921,4978,4979],{"class":4927},"  \"first_name\"",[4921,4981,580],{"class":4970},[4921,4983,4984],{"class":4931}," \"Ana\",\n",[4921,4986,4988,4991,4993],{"class":4923,"line":4987},8,[4921,4989,4990],{"class":4927},"  \"last_name\"",[4921,4992,580],{"class":4970},[4921,4994,4995],{"class":4931}," \"Souza\",\n",[4921,4997,4999,5002,5004],{"class":4923,"line":4998},9,[4921,5000,5001],{"class":4927},"  \"date_of_birth\"",[4921,5003,580],{"class":4970},[4921,5005,5006],{"class":4931}," \"1994-03-12\",\n",[4921,5008,5010,5013,5015],{"class":4923,"line":5009},10,[4921,5011,5012],{"class":4927},"  \"country\"",[4921,5014,580],{"class":4970},[4921,5016,5017],{"class":4931}," \"BR\",\n",[4921,5019,5021,5024,5026],{"class":4923,"line":5020},11,[4921,5022,5023],{"class":4927},"  \"tax_id\"",[4921,5025,580],{"class":4970},[4921,5027,5028],{"class":4931}," \"000.000.000-00\",\n",[4921,5030,5032,5035,5037,5040,5043,5046,5049,5052,5055,5058],{"class":4923,"line":5031},12,[4921,5033,5034],{"class":4927},"  \"address\"",[4921,5036,580],{"class":4970},[4921,5038,5039],{"class":4931}," {",[4921,5041,5042],{"class":4931}," \"line1\":",[4921,5044,5045],{"class":4931}," \"...\",",[4921,5047,5048],{"class":4931}," \"city\":",[4921,5050,5051],{"class":4931}," \"Recife\",",[4921,5053,5054],{"class":4931}," \"postal_code\":",[4921,5056,5057],{"class":4931}," \"...\"",[4921,5059,5060],{"class":4931}," }\n",[4921,5062,5064],{"class":4923,"line":5063},13,[4921,5065,5066],{"class":4960},"}\n",[11,5068,5069,5070,5073,5074,5077,5078,5081],{},"The response comes back with a status such as ",[204,5071,5072],{},"pending",". Wait for ",[204,5075,5076],{},"approved"," on a webhook before issuing a card. Treat ",[204,5079,5080],{},"rejected"," as final and show a clear message.",[967,5083,5085],{"id":5084},"_4-link-a-stablecoin-funding-source","4. Link a stablecoin funding source",[4913,5087,5089],{"className":4915,"code":5088,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Ffunding-sources\nContent-Type: application\u002Fjson\n\n{\n  \"type\": \"stablecoin_wallet\",\n  \"token\": \"USDC\",\n  \"network\": \"base\",\n  \"address\": \"0x...\"\n}\n",[204,5090,5091,5098,5104,5108,5112,5121,5131,5141,5150],{"__ignoreMap":328},[4921,5092,5093,5095],{"class":4923,"line":4924},[4921,5094,4928],{"class":4927},[4921,5096,5097],{"class":4931}," \u002Fv1\u002Ffunding-sources\n",[4921,5099,5100,5102],{"class":4923,"line":329},[4921,5101,4937],{"class":4927},[4921,5103,4940],{"class":4931},[4921,5105,5106],{"class":4923,"line":1404},[4921,5107,4954],{"emptyLinePlaceholder":362},[4921,5109,5110],{"class":4923,"line":4951},[4921,5111,4961],{"class":4960},[4921,5113,5114,5116,5118],{"class":4923,"line":4957},[4921,5115,4967],{"class":4927},[4921,5117,580],{"class":4970},[4921,5119,5120],{"class":4931}," \"stablecoin_wallet\",\n",[4921,5122,5123,5126,5128],{"class":4923,"line":4964},[4921,5124,5125],{"class":4927},"  \"token\"",[4921,5127,580],{"class":4970},[4921,5129,5130],{"class":4931}," \"USDC\",\n",[4921,5132,5133,5136,5138],{"class":4923,"line":4976},[4921,5134,5135],{"class":4927},"  \"network\"",[4921,5137,580],{"class":4970},[4921,5139,5140],{"class":4931}," \"base\",\n",[4921,5142,5143,5145,5147],{"class":4923,"line":4987},[4921,5144,5034],{"class":4927},[4921,5146,580],{"class":4970},[4921,5148,5149],{"class":4931}," \"0x...\"\n",[4921,5151,5152],{"class":4923,"line":4998},[4921,5153,5066],{"class":4960},[11,5155,5156],{},"In a custodial model you deposit USDC to an address the provider gives you. In an allowance model you approve a spending limit on-chain from your own wallet, and the provider pulls only what settles.",[967,5158,5160],{"id":5159},"_5-issue-a-virtual-card","5. Issue a virtual card",[4913,5162,5164],{"className":4915,"code":5163,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Fcards\nContent-Type: application\u002Fjson\n\n{\n  \"cardholder_id\": \"ch_...\",\n  \"funding_source_id\": \"fs_...\",\n  \"type\": \"virtual\",\n  \"currency\": \"USD\",\n  \"limits\": [{ \"amount\": 200000, \"interval\": \"monthly\" }],\n  \"blocked_mccs\": [\"7995\"]\n}\n",[204,5165,5166,5173,5179,5183,5187,5197,5207,5216,5226,5253,5269],{"__ignoreMap":328},[4921,5167,5168,5170],{"class":4923,"line":4924},[4921,5169,4928],{"class":4927},[4921,5171,5172],{"class":4931}," \u002Fv1\u002Fcards\n",[4921,5174,5175,5177],{"class":4923,"line":329},[4921,5176,4937],{"class":4927},[4921,5178,4940],{"class":4931},[4921,5180,5181],{"class":4923,"line":1404},[4921,5182,4954],{"emptyLinePlaceholder":362},[4921,5184,5185],{"class":4923,"line":4951},[4921,5186,4961],{"class":4960},[4921,5188,5189,5192,5194],{"class":4923,"line":4957},[4921,5190,5191],{"class":4927},"  \"cardholder_id\"",[4921,5193,580],{"class":4970},[4921,5195,5196],{"class":4931}," \"ch_...\",\n",[4921,5198,5199,5202,5204],{"class":4923,"line":4964},[4921,5200,5201],{"class":4927},"  \"funding_source_id\"",[4921,5203,580],{"class":4970},[4921,5205,5206],{"class":4931}," \"fs_...\",\n",[4921,5208,5209,5211,5213],{"class":4923,"line":4976},[4921,5210,4967],{"class":4927},[4921,5212,580],{"class":4970},[4921,5214,5215],{"class":4931}," \"virtual\",\n",[4921,5217,5218,5221,5223],{"class":4923,"line":4987},[4921,5219,5220],{"class":4927},"  \"currency\"",[4921,5222,580],{"class":4970},[4921,5224,5225],{"class":4931}," \"USD\",\n",[4921,5227,5228,5231,5233,5236,5239,5241,5244,5247,5250],{"class":4923,"line":4998},[4921,5229,5230],{"class":4927},"  \"limits\"",[4921,5232,580],{"class":4970},[4921,5234,5235],{"class":4960}," [{ ",[4921,5237,5238],{"class":4927},"\"amount\"",[4921,5240,580],{"class":4970},[4921,5242,5243],{"class":4931}," 200000,",[4921,5245,5246],{"class":4931}," \"interval\":",[4921,5248,5249],{"class":4931}," \"monthly\"",[4921,5251,5252],{"class":4931}," }],\n",[4921,5254,5255,5258,5260,5263,5266],{"class":4923,"line":5009},[4921,5256,5257],{"class":4927},"  \"blocked_mccs\"",[4921,5259,580],{"class":4970},[4921,5261,5262],{"class":4960}," [",[4921,5264,5265],{"class":4931},"\"7995\"",[4921,5267,5268],{"class":4960},"]\n",[4921,5270,5271],{"class":4923,"line":5020},[4921,5272,5066],{"class":4960},[11,5274,5275,5276,5279],{},"Amounts are in minor units, so ",[204,5277,5278],{},"200000"," is USD 2,000.00. MCC 7995 is gambling. Show the card number to the cardholder through the provider's embedded, PCI-compliant display component. Never proxy the full card number through your own backend, or you inherit PCI scope.",[967,5281,5283],{"id":5282},"_6-handle-the-authorization-webhook","6. Handle the authorization webhook",[11,5285,5286],{},"This is the heart of the integration. On each purchase the provider calls your endpoint and waits a few seconds for an answer. If you do not answer in time, the provider applies a default decision you configure.",[4913,5288,5292],{"className":5289,"code":5290,"language":5291,"meta":328,"style":328},"language-ts shiki shiki-themes github-light","app.post('\u002Fwebhooks\u002Fcard-authorization', async (req, res) => {\n  const event = verifySignature(req) \u002F\u002F provider-specific HMAC check; reject if invalid\n  const { authorization_id, card_id, amount, currency, merchant } = event\n\n  if (await ledger.seen(authorization_id))\n    return res.json(await ledger.decisionFor(authorization_id))\n\n  const card = await cards.get(card_id)\n  const available = await ledger.availableUsdc(card.accountId)\n  const needed = await quotes.toUsdcMinorUnits(amount, currency)\n\n  if (needed > available)\n    return res.json({ decision: 'decline', reason: 'insufficient_funds' })\n\n  await ledger.hold(card.accountId, authorization_id, needed)\n  return res.json({ decision: 'approve' })\n})\n","ts",[204,5293,5294,5335,5356,5395,5399,5418,5440,5444,5465,5484,5504,5508,5521,5544,5549,5563,5580],{"__ignoreMap":328},[4921,5295,5296,5299,5302,5305,5308,5310,5314,5317,5321,5323,5326,5329,5332],{"class":4923,"line":4924},[4921,5297,5298],{"class":4960},"app.",[4921,5300,5301],{"class":4927},"post",[4921,5303,5304],{"class":4960},"(",[4921,5306,5307],{"class":4931},"'\u002Fwebhooks\u002Fcard-authorization'",[4921,5309,1304],{"class":4960},[4921,5311,5313],{"class":5312},"sD7c4","async",[4921,5315,5316],{"class":4960}," (",[4921,5318,5320],{"class":5319},"sqxcx","req",[4921,5322,1304],{"class":4960},[4921,5324,5325],{"class":5319},"res",[4921,5327,5328],{"class":4960},") ",[4921,5330,5331],{"class":5312},"=>",[4921,5333,5334],{"class":4960}," {\n",[4921,5336,5337,5340,5343,5346,5349,5352],{"class":4923,"line":329},[4921,5338,5339],{"class":5312},"  const",[4921,5341,5342],{"class":4970}," event",[4921,5344,5345],{"class":5312}," =",[4921,5347,5348],{"class":4927}," verifySignature",[4921,5350,5351],{"class":4960},"(req) ",[4921,5353,5355],{"class":5354},"sAwPA","\u002F\u002F provider-specific HMAC check; reject if invalid\n",[4921,5357,5358,5360,5363,5366,5368,5371,5373,5376,5378,5381,5383,5386,5389,5392],{"class":4923,"line":1404},[4921,5359,5339],{"class":5312},[4921,5361,5362],{"class":4960}," { ",[4921,5364,5365],{"class":4970},"authorization_id",[4921,5367,1304],{"class":4960},[4921,5369,5370],{"class":4970},"card_id",[4921,5372,1304],{"class":4960},[4921,5374,5375],{"class":4970},"amount",[4921,5377,1304],{"class":4960},[4921,5379,5380],{"class":4970},"currency",[4921,5382,1304],{"class":4960},[4921,5384,5385],{"class":4970},"merchant",[4921,5387,5388],{"class":4960}," } ",[4921,5390,5391],{"class":5312},"=",[4921,5393,5394],{"class":4960}," event\n",[4921,5396,5397],{"class":4923,"line":4951},[4921,5398,4954],{"emptyLinePlaceholder":362},[4921,5400,5401,5404,5406,5409,5412,5415],{"class":4923,"line":4957},[4921,5402,5403],{"class":5312},"  if",[4921,5405,5316],{"class":4960},[4921,5407,5408],{"class":5312},"await",[4921,5410,5411],{"class":4960}," ledger.",[4921,5413,5414],{"class":4927},"seen",[4921,5416,5417],{"class":4960},"(authorization_id))\n",[4921,5419,5420,5423,5426,5429,5431,5433,5435,5438],{"class":4923,"line":4964},[4921,5421,5422],{"class":5312},"    return",[4921,5424,5425],{"class":4960}," res.",[4921,5427,5428],{"class":4927},"json",[4921,5430,5304],{"class":4960},[4921,5432,5408],{"class":5312},[4921,5434,5411],{"class":4960},[4921,5436,5437],{"class":4927},"decisionFor",[4921,5439,5417],{"class":4960},[4921,5441,5442],{"class":4923,"line":4976},[4921,5443,4954],{"emptyLinePlaceholder":362},[4921,5445,5446,5448,5451,5453,5456,5459,5462],{"class":4923,"line":4987},[4921,5447,5339],{"class":5312},[4921,5449,5450],{"class":4970}," card",[4921,5452,5345],{"class":5312},[4921,5454,5455],{"class":5312}," await",[4921,5457,5458],{"class":4960}," cards.",[4921,5460,5461],{"class":4927},"get",[4921,5463,5464],{"class":4960},"(card_id)\n",[4921,5466,5467,5469,5472,5474,5476,5478,5481],{"class":4923,"line":4998},[4921,5468,5339],{"class":5312},[4921,5470,5471],{"class":4970}," available",[4921,5473,5345],{"class":5312},[4921,5475,5455],{"class":5312},[4921,5477,5411],{"class":4960},[4921,5479,5480],{"class":4927},"availableUsdc",[4921,5482,5483],{"class":4960},"(card.accountId)\n",[4921,5485,5486,5488,5491,5493,5495,5498,5501],{"class":4923,"line":5009},[4921,5487,5339],{"class":5312},[4921,5489,5490],{"class":4970}," needed",[4921,5492,5345],{"class":5312},[4921,5494,5455],{"class":5312},[4921,5496,5497],{"class":4960}," quotes.",[4921,5499,5500],{"class":4927},"toUsdcMinorUnits",[4921,5502,5503],{"class":4960},"(amount, currency)\n",[4921,5505,5506],{"class":4923,"line":5020},[4921,5507,4954],{"emptyLinePlaceholder":362},[4921,5509,5510,5512,5515,5518],{"class":4923,"line":5031},[4921,5511,5403],{"class":5312},[4921,5513,5514],{"class":4960}," (needed ",[4921,5516,5517],{"class":5312},">",[4921,5519,5520],{"class":4960}," available)\n",[4921,5522,5523,5525,5527,5529,5532,5535,5538,5541],{"class":4923,"line":5063},[4921,5524,5422],{"class":5312},[4921,5526,5425],{"class":4960},[4921,5528,5428],{"class":4927},[4921,5530,5531],{"class":4960},"({ decision: ",[4921,5533,5534],{"class":4931},"'decline'",[4921,5536,5537],{"class":4960},", reason: ",[4921,5539,5540],{"class":4931},"'insufficient_funds'",[4921,5542,5543],{"class":4960}," })\n",[4921,5545,5547],{"class":4923,"line":5546},14,[4921,5548,4954],{"emptyLinePlaceholder":362},[4921,5550,5552,5555,5557,5560],{"class":4923,"line":5551},15,[4921,5553,5554],{"class":5312},"  await",[4921,5556,5411],{"class":4960},[4921,5558,5559],{"class":4927},"hold",[4921,5561,5562],{"class":4960},"(card.accountId, authorization_id, needed)\n",[4921,5564,5566,5569,5571,5573,5575,5578],{"class":4923,"line":5565},16,[4921,5567,5568],{"class":5312},"  return",[4921,5570,5425],{"class":4960},[4921,5572,5428],{"class":4927},[4921,5574,5531],{"class":4960},[4921,5576,5577],{"class":4931},"'approve'",[4921,5579,5543],{"class":4960},[4921,5581,5583],{"class":4923,"line":5582},17,[4921,5584,5585],{"class":4960},"})\n",[11,5587,5588],{},"Three rules make this handler reliable:",[171,5590,5591,5597,5603],{},[148,5592,5593,5596],{},[119,5594,5595],{},"Read from your ledger, not the blockchain."," An on-chain balance query is too slow for an authorization deadline. Keep a ledger that updates on deposit and settlement events.",[148,5598,5599,5602],{},[119,5600,5601],{},"Be idempotent."," Providers retry. Key on the authorization id and return the same decision.",[148,5604,5605,5608],{},[119,5606,5607],{},"Decide your timeout default deliberately."," Decline on timeout is safer. Approve on timeout is friendlier and needs a buffer.",[967,5610,5612],{"id":5611},"_7-process-clearing-reversals-and-refunds","7. Process clearing, reversals, and refunds",[11,5614,5615],{},"The authorized amount is not the final amount. Listen for clearing events and adjust the hold, release holds on reversals, and credit refunds. Post each event to your ledger once, keyed on its id.",[967,5617,5619],{"id":5618},"_8-settle-the-funding-side","8. Settle the funding side",[11,5621,5622],{},"At settlement the provider draws the stablecoins that cover the day's cleared purchases and pays the network, in fiat or in USDC where the network supports it. Reconcile the draw against your ledger daily.",[11,5624,5625,5626,5629,5630,5633],{},"If your treasury starts in a bank account, you need a way into stablecoins first. BlindPay ",[136,5627,5628],{"href":138},"virtual USD accounts"," accept ACH and wire deposits and convert them to USDC or USDT in a linked wallet, and the ",[136,5631,5632],{"href":2712},"stablecoin API integration guide"," walks through those calls with real endpoints.",[967,5635,5637],{"id":5636},"_9-go-live-with-low-limits","9. Go live with low limits",[11,5639,5640],{},"Switch to production keys, issue one card to an internal cardholder with a USD 50 limit, and buy something real. Check every event landed in the ledger. Then raise limits.",[18,5642,5644],{"id":5643},"where-does-kyc-and-kyb-sit-in-the-flow","Where does KYC and KYB sit in the flow?",[11,5646,5647],{},"Compliance is not a step. It is four checkpoints.",[39,5649,5650,5663],{},[42,5651,5652],{},[45,5653,5654,5657,5660],{},[48,5655,5656],{},"Checkpoint",[48,5658,5659],{},"Check",[48,5661,5662],{},"Why it cannot be skipped",[61,5664,5665,5676,5687,5698],{},[45,5666,5667,5670,5673],{},[66,5668,5669],{},"Program approval",[66,5671,5672],{},"KYB on your company and its beneficial owners",[66,5674,5675],{},"The sponsor bank must know who runs the program",[45,5677,5678,5681,5684],{},[66,5679,5680],{},"Cardholder creation",[66,5682,5683],{},"KYC on each cardholder, sanctions screening",[66,5685,5686],{},"A card is an account; account opening requires identification",[45,5688,5689,5692,5695],{},[66,5690,5691],{},"Funding",[66,5693,5694],{},"Wallet address screening",[66,5696,5697],{},"Stablecoin funds from a sanctioned address taint the program",[45,5699,5700,5703,5706],{},[66,5701,5702],{},"Every authorization",[66,5704,5705],{},"Transaction monitoring, velocity and merchant rules",[66,5707,5708],{},"The sponsor bank's AML program covers every transaction on its BIN",[11,5710,5711,5712,5716],{},"The sponsor bank carries the regulatory responsibility for every card on its BIN, and US sanctions compliance is strict liability. A provider that lets you skip a checkpoint is putting its bank relationship, and your program, at risk. The ",[136,5713,5715],{"href":5714},"\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance","compliance guide"," covers what each check involves and how it differs by country.",[18,5718,5720],{"id":5719},"testing-checklist-before-production","Testing checklist before production",[171,5722,5723,5726,5729,5732,5735,5738,5741],{},[148,5724,5725],{},"Approve, decline for insufficient funds, and decline on a blocked MCC",[148,5727,5728],{},"Webhook timeout and the configured default decision",[148,5730,5731],{},"Duplicate webhook delivery",[148,5733,5734],{},"Partial clearing below the authorized amount, and clearing above it (tips)",[148,5736,5737],{},"Full reversal and a refund days later",[148,5739,5740],{},"Cardholder KYC rejection",[148,5742,5743],{},"Funding source running low mid-month",[18,5745,5747],{"id":5746},"what-to-read-next","What to read next",[11,5749,5750,5751,5754,5755,5757],{},"Finish the series with the ",[136,5752,5753],{"href":5714},"compliance guide for stablecoin card issuing",". If your recipients need money in a bank account rather than on a card, the ",[136,5756,5632],{"href":2712}," covers local-currency payouts over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO).",[11,5759,5760],{},[324,5761,326],{},[5763,5764,5765],"style",{},"html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}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 .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);}html pre.shiki code .sD7c4, html code.shiki .sD7c4{--shiki-default:#D73A49}html pre.shiki code .sqxcx, html code.shiki .sqxcx{--shiki-default:#E36209}html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}",{"title":328,"searchDepth":329,"depth":329,"links":5767},[5768,5769,5770,5781,5782,5783],{"id":4670,"depth":329,"text":4671},{"id":4774,"depth":329,"text":4775},{"id":4892,"depth":329,"text":4893,"children":5771},[5772,5773,5774,5775,5776,5777,5778,5779,5780],{"id":4896,"depth":1404,"text":4897},{"id":4903,"depth":1404,"text":4904},{"id":4910,"depth":1404,"text":4911},{"id":5084,"depth":1404,"text":5085},{"id":5159,"depth":1404,"text":5160},{"id":5282,"depth":1404,"text":5283},{"id":5611,"depth":1404,"text":5612},{"id":5618,"depth":1404,"text":5619},{"id":5636,"depth":1404,"text":5637},{"id":5643,"depth":329,"text":5644},{"id":5719,"depth":329,"text":5720},{"id":5746,"depth":329,"text":5747},"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.",[5786,5789,5792,5795,5798],{"q":5787,"a":5788},"How do I issue a stablecoin-funded card through an API?","Integrate with a card issuing provider that supports stablecoin funding: pass KYB for your business, create a cardholder and pass KYC, link a USDC or USDT funding source, issue a virtual card with spend controls, and implement the authorization webhook that approves or declines each purchase against the stablecoin balance. The provider and its sponsor bank handle the card network connection.",{"q":5790,"a":5791},"What does a stablecoin card issuing API need to support?","At minimum: cardholder creation with KYC status, card issuance with limits and merchant controls, a funding source tied to a stablecoin balance, a synchronous authorization webhook, and events for clearing, reversals, refunds, and disputes. Sandbox simulation of authorizations and declines is also needed to test the integration before production.",{"q":5793,"a":5794},"Should I build card issuing in-house or use an API provider?","Use an API provider unless card issuing is the core business and you have years and a large budget. Building in-house means signing a BIN sponsor bank, meeting card network requirements, reaching PCI DSS compliance for card data, building or licensing an authorization engine, and running an anti-money-laundering program. An API provider has already done that, leaving you the product, ledger, and user experience.",{"q":5796,"a":5797},"How does KYC\u002FKYB fit into an API-based card issuing flow?","KYB runs once on your business before the program is approved, and KYC runs on every cardholder before a card can be issued. Sanctions screening repeats on cardholders and, for stablecoin funding, on wallet addresses, and transaction monitoring runs on every authorization. None of these can be skipped, because the sponsor bank carries the regulatory responsibility for every card on its BIN.",{"q":5799,"a":5800},"What is the typical integration flow for issuing a stablecoin-backed card?","Get sandbox keys, pass KYB, create and verify a cardholder, link a stablecoin funding source, issue a virtual card with limits, implement the authorization webhook, handle clearing and reversal events in your ledger, and go live with a small internal card first. Most of the engineering time goes into the authorization handler and the ledger, not the card creation calls.",{"name":5802,"steps":5803},"How to issue a stablecoin-funded card through an API",[5804,5807,5810,5813,5816,5819,5822,5825],{"name":5805,"text":5806},"Get sandbox credentials from a card issuing provider","Sign up with an issuing provider that supports stablecoin funding, get sandbox API keys, and confirm which card networks, card currencies, and cardholder countries its sponsor bank allows.",{"name":5808,"text":5809},"Pass KYB for your business","The provider and its sponsor bank verify your company, its registration, and its beneficial owners before approving the card program. Program approval defines limits, allowed countries, and card types.",{"name":5811,"text":5812},"Create a cardholder and pass KYC","Create a cardholder with name, date of birth, address, and a government ID number. Wait for an approved status before issuing a card; rejected or pending cardholders cannot receive one.",{"name":5814,"text":5815},"Link a stablecoin funding source","Attach the stablecoin balance that pays for purchases: a program wallet the provider holds, or your own wallet with an on-chain spending allowance. Record the network and token, such as USDC on Base or Solana.",{"name":5817,"text":5818},"Issue a virtual card with spend controls","Create a virtual card for the cardholder with spending limits, merchant category rules, and an expiry. Return the card details to the cardholder through the provider's PCI-compliant display component, never through your own servers.",{"name":5820,"text":5821},"Handle the authorization webhook","Implement a synchronous endpoint that receives each authorization request, verifies its signature, checks the available stablecoin balance in your ledger, places a hold, and returns approve or decline within the provider's deadline.",{"name":5823,"text":5824},"Process clearing, reversals, and refunds","Listen for clearing, reversal, and refund events, adjust holds to the final amounts, and post entries to your ledger. Key every event on its idempotency id so retries do not double-post.",{"name":5826,"text":5827},"Go live with low limits","Switch to production keys, issue a card to an internal cardholder with a small limit, and run a first live transaction end to end before raising limits.",{"author":361},"\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","---\ntitle: \"How to issue stablecoin-funded cards through an API: a developer's guide\"\nseoTitle: \"How to issue stablecoin-funded cards through an API\"\ndescription: \"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.\"\ndate: \"2026-09-18\"\nupdated: \"2026-09-21\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to issue a stablecoin-funded card through an API\"\n  steps:\n    - name: \"Get sandbox credentials from a card issuing provider\"\n      text: \"Sign up with an issuing provider that supports stablecoin funding, get sandbox API keys, and confirm which card networks, card currencies, and cardholder countries its sponsor bank allows.\"\n    - name: \"Pass KYB for your business\"\n      text: \"The provider and its sponsor bank verify your company, its registration, and its beneficial owners before approving the card program. Program approval defines limits, allowed countries, and card types.\"\n    - name: \"Create a cardholder and pass KYC\"\n      text: \"Create a cardholder with name, date of birth, address, and a government ID number. Wait for an approved status before issuing a card; rejected or pending cardholders cannot receive one.\"\n    - name: \"Link a stablecoin funding source\"\n      text: \"Attach the stablecoin balance that pays for purchases: a program wallet the provider holds, or your own wallet with an on-chain spending allowance. Record the network and token, such as USDC on Base or Solana.\"\n    - name: \"Issue a virtual card with spend controls\"\n      text: \"Create a virtual card for the cardholder with spending limits, merchant category rules, and an expiry. Return the card details to the cardholder through the provider's PCI-compliant display component, never through your own servers.\"\n    - name: \"Handle the authorization webhook\"\n      text: \"Implement a synchronous endpoint that receives each authorization request, verifies its signature, checks the available stablecoin balance in your ledger, places a hold, and returns approve or decline within the provider's deadline.\"\n    - name: \"Process clearing, reversals, and refunds\"\n      text: \"Listen for clearing, reversal, and refund events, adjust holds to the final amounts, and post entries to your ledger. Key every event on its idempotency id so retries do not double-post.\"\n    - name: \"Go live with low limits\"\n      text: \"Switch to production keys, issue a card to an internal cardholder with a small limit, and run a first live transaction end to end before raising limits.\"\nfaq:\n  - q: \"How do I issue a stablecoin-funded card through an API?\"\n    a: \"Integrate with a card issuing provider that supports stablecoin funding: pass KYB for your business, create a cardholder and pass KYC, link a USDC or USDT funding source, issue a virtual card with spend controls, and implement the authorization webhook that approves or declines each purchase against the stablecoin balance. The provider and its sponsor bank handle the card network connection.\"\n  - q: \"What does a stablecoin card issuing API need to support?\"\n    a: \"At minimum: cardholder creation with KYC status, card issuance with limits and merchant controls, a funding source tied to a stablecoin balance, a synchronous authorization webhook, and events for clearing, reversals, refunds, and disputes. Sandbox simulation of authorizations and declines is also needed to test the integration before production.\"\n  - q: \"Should I build card issuing in-house or use an API provider?\"\n    a: \"Use an API provider unless card issuing is the core business and you have years and a large budget. Building in-house means signing a BIN sponsor bank, meeting card network requirements, reaching PCI DSS compliance for card data, building or licensing an authorization engine, and running an anti-money-laundering program. An API provider has already done that, leaving you the product, ledger, and user experience.\"\n  - q: \"How does KYC\u002FKYB fit into an API-based card issuing flow?\"\n    a: \"KYB runs once on your business before the program is approved, and KYC runs on every cardholder before a card can be issued. Sanctions screening repeats on cardholders and, for stablecoin funding, on wallet addresses, and transaction monitoring runs on every authorization. None of these can be skipped, because the sponsor bank carries the regulatory responsibility for every card on its BIN.\"\n  - q: \"What is the typical integration flow for issuing a stablecoin-backed card?\"\n    a: \"Get sandbox keys, pass KYB, create and verify a cardholder, link a stablecoin funding source, issue a virtual card with limits, implement the authorization webhook, handle clearing and reversal events in your ledger, and go live with a small internal card first. Most of the engineering time goes into the authorization handler and the ledger, not the card creation calls.\"\n---\n\n*Reading time: about 8 minutes.*\n\n**Summary:** API-based stablecoin card issuing means creating cardholders, cards, and spending decisions through a card issuing provider's REST API, while funding each purchase from a stablecoin balance such as USDC. The provider handles the network connection and the sponsor bank. Your code decides who gets a card, how it is funded, and which transactions to approve.\n\nThis guide is for developers and technical founders deciding whether to build or integrate. It covers what each path requires, the objects any issuing API has to expose, and an integration flow you can follow as a checklist.\n\nOne note on scope. The endpoints and payloads below are a generic shape shared by most issuing APIs, not one provider's reference. Names change between providers. The objects and their order do not. For the concepts behind the card itself, read [what stablecoin card issuing is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing).\n\n## Should you build card issuing in-house or use an API?\n\nBuilding means becoming the issuer's technology and compliance partner yourself. Buying means integrating one that already is.\n\n| Requirement | Build in-house | Integrate an issuing API |\n|---|---|---|\n| Sponsor bank | Negotiate and sign a BIN sponsorship agreement | Provided; you are approved under the provider's program |\n| Card network | Meet Visa or Mastercard program and certification requirements | Provided |\n| Card data security | PCI DSS compliance for storing and processing card numbers | Provider's vault; you never touch the full card number |\n| Authorization engine | Build or license an issuer processor | Provided; you answer a webhook |\n| Compliance program | Written AML program, KYC, monitoring, filings, under the sponsor's oversight | Shared: the provider runs most checks, you own your program's policies |\n| Disputes and chargebacks | Build dispute operations | Provider workflow plus API events |\n| Time to first card | Typically a year or more | Sandbox in a day; production after program approval |\n\nBuild only if card issuing is the product and you have the capital and patience for bank and network negotiations. Everyone else integrates, and spends the saved time on the ledger and UX, which is where programs actually differ.\n\n## What does a stablecoin card issuing API need to expose?\n\nA usable issuing API has seven objects. If a provider is missing one, you will end up building it.\n\n| Object | What it does | Fields to look for |\n|---|---|---|\n| Cardholder | The verified person or business the card belongs to | KYC status, country, rejection reasons |\n| Funding source | The stablecoin balance that pays for purchases | Token, network, wallet address, custody model |\n| Card | A virtual or physical card | Status, limits, merchant category rules, expiry |\n| Authorization request | A real-time question from the network: approve this? | Amount, currency, merchant, MCC, deadline |\n| Transaction | The lifecycle after approval | Clearing amount, reversals, refunds, FX rate |\n| Dispute | A cardholder challenge to a transaction | Reason code, deadline, evidence |\n| Webhook endpoint | Where events are delivered | Signing secret, retry policy, event types |\n\nTwo questions separate stablecoin-native providers from traditional ones bolted onto a wallet:\n\n- **When does conversion happen?** Just in time at authorization, so balances stay in USDC, or ahead of time into a fiat card balance.\n- **Who holds the stablecoins?** A custodial program wallet, or your own wallet with an on-chain spending allowance the provider can draw from.\n\n## Integration flow, step by step\n\n### 1. Get sandbox credentials\n\nSign up, get sandbox keys, and before writing code ask for three lists: supported card currencies, cardholder countries the sponsor bank accepts, and stablecoins and networks the funding source supports. These decide your product more than any endpoint.\n\n### 2. Pass KYB for your business\n\nThe provider and its sponsor bank verify your company before approving the program: registration, beneficial owners, business model, and expected volumes. The approval sets your limits and card types. Plan for this to take longer than the code.\n\n### 3. Create a cardholder and pass KYC\n\n```bash\nPOST \u002Fv1\u002Fcardholders\nContent-Type: application\u002Fjson\nIdempotency-Key: 1c9f...\n\n{\n  \"type\": \"individual\",\n  \"first_name\": \"Ana\",\n  \"last_name\": \"Souza\",\n  \"date_of_birth\": \"1994-03-12\",\n  \"country\": \"BR\",\n  \"tax_id\": \"000.000.000-00\",\n  \"address\": { \"line1\": \"...\", \"city\": \"Recife\", \"postal_code\": \"...\" }\n}\n```\n\nThe response comes back with a status such as `pending`. Wait for `approved` on a webhook before issuing a card. Treat `rejected` as final and show a clear message.\n\n### 4. Link a stablecoin funding source\n\n```bash\nPOST \u002Fv1\u002Ffunding-sources\nContent-Type: application\u002Fjson\n\n{\n  \"type\": \"stablecoin_wallet\",\n  \"token\": \"USDC\",\n  \"network\": \"base\",\n  \"address\": \"0x...\"\n}\n```\n\nIn a custodial model you deposit USDC to an address the provider gives you. In an allowance model you approve a spending limit on-chain from your own wallet, and the provider pulls only what settles.\n\n### 5. Issue a virtual card\n\n```bash\nPOST \u002Fv1\u002Fcards\nContent-Type: application\u002Fjson\n\n{\n  \"cardholder_id\": \"ch_...\",\n  \"funding_source_id\": \"fs_...\",\n  \"type\": \"virtual\",\n  \"currency\": \"USD\",\n  \"limits\": [{ \"amount\": 200000, \"interval\": \"monthly\" }],\n  \"blocked_mccs\": [\"7995\"]\n}\n```\n\nAmounts are in minor units, so `200000` is USD 2,000.00. MCC 7995 is gambling. Show the card number to the cardholder through the provider's embedded, PCI-compliant display component. Never proxy the full card number through your own backend, or you inherit PCI scope.\n\n### 6. Handle the authorization webhook\n\nThis is the heart of the integration. On each purchase the provider calls your endpoint and waits a few seconds for an answer. If you do not answer in time, the provider applies a default decision you configure.\n\n```ts\napp.post('\u002Fwebhooks\u002Fcard-authorization', async (req, res) => {\n  const event = verifySignature(req) \u002F\u002F provider-specific HMAC check; reject if invalid\n  const { authorization_id, card_id, amount, currency, merchant } = event\n\n  if (await ledger.seen(authorization_id))\n    return res.json(await ledger.decisionFor(authorization_id))\n\n  const card = await cards.get(card_id)\n  const available = await ledger.availableUsdc(card.accountId)\n  const needed = await quotes.toUsdcMinorUnits(amount, currency)\n\n  if (needed > available)\n    return res.json({ decision: 'decline', reason: 'insufficient_funds' })\n\n  await ledger.hold(card.accountId, authorization_id, needed)\n  return res.json({ decision: 'approve' })\n})\n```\n\nThree rules make this handler reliable:\n\n- **Read from your ledger, not the blockchain.** An on-chain balance query is too slow for an authorization deadline. Keep a ledger that updates on deposit and settlement events.\n- **Be idempotent.** Providers retry. Key on the authorization id and return the same decision.\n- **Decide your timeout default deliberately.** Decline on timeout is safer. Approve on timeout is friendlier and needs a buffer.\n\n### 7. Process clearing, reversals, and refunds\n\nThe authorized amount is not the final amount. Listen for clearing events and adjust the hold, release holds on reversals, and credit refunds. Post each event to your ledger once, keyed on its id.\n\n### 8. Settle the funding side\n\nAt settlement the provider draws the stablecoins that cover the day's cleared purchases and pays the network, in fiat or in USDC where the network supports it. Reconcile the draw against your ledger daily.\n\nIf your treasury starts in a bank account, you need a way into stablecoins first. BlindPay [virtual USD accounts](\u002Fvirtual-accounts) accept ACH and wire deposits and convert them to USDC or USDT in a linked wallet, and the [stablecoin API integration guide](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api) walks through those calls with real endpoints.\n\n### 9. Go live with low limits\n\nSwitch to production keys, issue one card to an internal cardholder with a USD 50 limit, and buy something real. Check every event landed in the ledger. Then raise limits.\n\n## Where does KYC and KYB sit in the flow?\n\nCompliance is not a step. It is four checkpoints.\n\n| Checkpoint | Check | Why it cannot be skipped |\n|---|---|---|\n| Program approval | KYB on your company and its beneficial owners | The sponsor bank must know who runs the program |\n| Cardholder creation | KYC on each cardholder, sanctions screening | A card is an account; account opening requires identification |\n| Funding | Wallet address screening | Stablecoin funds from a sanctioned address taint the program |\n| Every authorization | Transaction monitoring, velocity and merchant rules | The sponsor bank's AML program covers every transaction on its BIN |\n\nThe sponsor bank carries the regulatory responsibility for every card on its BIN, and US sanctions compliance is strict liability. A provider that lets you skip a checkpoint is putting its bank relationship, and your program, at risk. The [compliance guide](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance) covers what each check involves and how it differs by country.\n\n## Testing checklist before production\n\n- Approve, decline for insufficient funds, and decline on a blocked MCC\n- Webhook timeout and the configured default decision\n- Duplicate webhook delivery\n- Partial clearing below the authorized amount, and clearing above it (tips)\n- Full reversal and a refund days later\n- Cardholder KYC rejection\n- Funding source running low mid-month\n\n## What to read next\n\nFinish the series with the [compliance guide for stablecoin card issuing](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance). If your recipients need money in a bank account rather than on a card, the [stablecoin API integration guide](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api) covers local-currency payouts over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":4644,"description":5784},"How to issue stablecoin-funded cards through an API","resources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","2026-09-21","e8K1BA3FCEuura-Pd44GEUrUNyY51HASy4fmnhgbHX0",{"id":5837,"title":5838,"authors":6,"body":5839,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":1893,"description":5915,"extension":342,"faq":5916,"howto":5926,"isBlog":359,"isChangelog":359,"meta":5940,"navigation":362,"path":5941,"pillar":359,"products":6,"rawbody":5942,"role":6,"seo":5943,"seoTitle":6,"stem":5944,"thumbnail":6,"updated":6,"__hash__":5945},"content\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil.md","How to send USDC to a bank account in Brazil",{"type":8,"value":5840,"toc":5907},[5841,5847,5854,5858,5861,5865,5868,5872,5875,5879,5882,5886,5896,5900],[11,5842,5843,5844,227],{},"To send USDC to a bank account in Brazil, request a USDC to BRL quote from a stablecoin payout API, submit the receiver's name and CPF or CNPJ for verification, transfer the quoted USDC, and the provider delivers reais to the receiver's account over Pix. The whole flow takes minutes, because Pix settles in seconds and runs 24\u002F7. The live rate is on our ",[136,5845,5846],{"href":1757},"USDC to BRL corridor page",[11,5848,5849,5850,227],{},"Below is the flow in detail, plus what can go wrong at each step. For a comparison of this route against exchanges and P2P, see ",[136,5851,5853],{"href":5852},"\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026","USDC to BRL routes compared",[18,5855,5857],{"id":5856},"step-1-get-a-quote","Step 1: get a quote",[11,5859,5860],{},"A quote locks the FX rate, the fee, and the exact BRL amount the receiver gets, typically for a few minutes. This matters because it removes rate risk from the transfer: the receiver amount is known before any money moves. Quotes also declare which side pays fees, so a payroll run can guarantee net amounts.",[18,5862,5864],{"id":5863},"step-2-verify-the-receiver","Step 2: verify the receiver",[11,5866,5867],{},"Brazilian institutions verify the receiver's name against their tax ID (CPF for individuals, CNPJ for companies) before crediting an account. A payout API collects these once, runs KYC on the receiver, and reuses the verified identity for every later payment. The most common failure in the entire flow is a name and tax ID mismatch, so exact beneficiary data is the one thing to get right.",[18,5869,5871],{"id":5870},"step-3-send-the-usdc","Step 3: send the USDC",[11,5873,5874],{},"Transfer the quoted USDC amount to the provider on a supported network. From here the provider converts to reais at the locked rate; there is no separate trading step, order book, or manual withdrawal, which is what separates this route from selling on an exchange.",[18,5876,5878],{"id":5877},"step-4-reais-arrive-over-pix","Step 4: reais arrive over Pix",[11,5880,5881],{},"Pix, the instant payment system run by the Banco Central do Brasil, settles transfers in seconds and is used by over 150 million Brazilians. Once conversion completes, the reais land in the receiver's account regardless of banking hours, weekends, or holidays.",[18,5883,5885],{"id":5884},"sending-at-scale","Sending at scale",[11,5887,5888,5889,5891,5892,227],{},"For one transfer, any compliant route works. For payroll, contractor payments, or marketplace payouts, the API route is built to repeat: one integration replaces per-transfer manual work, and each payment follows the same quote, verify, send, settle sequence. How the model works in general: ",[136,5890,1492],{"href":618},". Developer reference: ",[136,5893,5895],{"href":5894},"\u002Fdocs\u002Fpayouts","payouts documentation",[18,5897,5899],{"id":5898},"the-regulatory-backdrop","The regulatory backdrop",[11,5901,5902,5903,5906],{},"Brazil regulates virtual asset services under Law 14.478\u002F2022, and the Central Bank's Resolutions 519, 520, and 521 (effective February 2, 2026) created an authorization regime for providers. Details in ",[136,5904,5905],{"href":3239},"PSAV in Brazil explained",". Practical implication: choose a provider operating within that regime, and expect real KYC on both sender and receiver.",{"title":328,"searchDepth":329,"depth":329,"links":5908},[5909,5910,5911,5912,5913,5914],{"id":5856,"depth":329,"text":5857},{"id":5863,"depth":329,"text":5864},{"id":5870,"depth":329,"text":5871},{"id":5877,"depth":329,"text":5878},{"id":5884,"depth":329,"text":5885},{"id":5898,"depth":329,"text":5899},"Convert USDC to Brazilian reais and deliver them to a bank account over Pix with a stablecoin payout API. Quote, verify, send, and settle in minutes.",[5917,5920,5923],{"q":5918,"a":5919},"How long does sending USDC to a Brazilian bank account take?","Minutes. Pix, Brazil's instant payment system, settles in seconds once the reais leave the sending institution, and the conversion step before it typically takes a few minutes on a payout API.",{"q":5921,"a":5922},"What information do I need from the receiver?","Their full name, CPF (individuals) or CNPJ (companies), and a Pix key or bank account details. A mismatch between name and tax ID is the most common reason a Pix payout is rejected.",{"q":5924,"a":5925},"Is this legal in Brazil?","Yes. Brazil regulates virtual asset services under Law 14.478\u002F2022, and since February 2026 providers operate under the Central Bank's authorization regime (Resolutions 519, 520, and 521). Use a provider that operates within that regime.",{"name":5838,"steps":5927},[5928,5931,5934,5937],{"name":5929,"text":5930},"Get a quote","Request a USDC to BRL quote from a stablecoin payout API. The quote locks the exchange rate, fees, and the exact BRL amount the receiver gets, typically for a few minutes.",{"name":5932,"text":5933},"Verify the receiver","Provide the receiver's identity details: name, CPF or CNPJ, and Pix key or bank account. Brazilian institutions verify the name against the tax ID before crediting, so accurate data is a hard requirement.",{"name":5935,"text":5936},"Send the USDC","Transfer the quoted USDC amount to the provider on a supported network. The provider converts it to reais at the locked rate.",{"name":5938,"text":5939},"Reais arrive over Pix","The provider delivers BRL to the receiver's account via Pix, which settles in seconds and runs 24\u002F7. End-to-end time is dominated by the conversion step, usually minutes.",{"author":361},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","---\ntitle: \"How to send USDC to a bank account in Brazil\"\ndescription: \"Convert USDC to Brazilian reais and deliver them to a bank account over Pix with a stablecoin payout API. Quote, verify, send, and settle in minutes.\"\ndate: \"2026-08-24\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to send USDC to a bank account in Brazil\"\n  steps:\n    - name: \"Get a quote\"\n      text: \"Request a USDC to BRL quote from a stablecoin payout API. The quote locks the exchange rate, fees, and the exact BRL amount the receiver gets, typically for a few minutes.\"\n    - name: \"Verify the receiver\"\n      text: \"Provide the receiver's identity details: name, CPF or CNPJ, and Pix key or bank account. Brazilian institutions verify the name against the tax ID before crediting, so accurate data is a hard requirement.\"\n    - name: \"Send the USDC\"\n      text: \"Transfer the quoted USDC amount to the provider on a supported network. The provider converts it to reais at the locked rate.\"\n    - name: \"Reais arrive over Pix\"\n      text: \"The provider delivers BRL to the receiver's account via Pix, which settles in seconds and runs 24\u002F7. End-to-end time is dominated by the conversion step, usually minutes.\"\nfaq:\n  - q: \"How long does sending USDC to a Brazilian bank account take?\"\n    a: \"Minutes. Pix, Brazil's instant payment system, settles in seconds once the reais leave the sending institution, and the conversion step before it typically takes a few minutes on a payout API.\"\n  - q: \"What information do I need from the receiver?\"\n    a: \"Their full name, CPF (individuals) or CNPJ (companies), and a Pix key or bank account details. A mismatch between name and tax ID is the most common reason a Pix payout is rejected.\"\n  - q: \"Is this legal in Brazil?\"\n    a: \"Yes. Brazil regulates virtual asset services under Law 14.478\u002F2022, and since February 2026 providers operate under the Central Bank's authorization regime (Resolutions 519, 520, and 521). Use a provider that operates within that regime.\"\n---\n\nTo send USDC to a bank account in Brazil, request a USDC to BRL quote from a stablecoin payout API, submit the receiver's name and CPF or CNPJ for verification, transfer the quoted USDC, and the provider delivers reais to the receiver's account over Pix. The whole flow takes minutes, because Pix settles in seconds and runs 24\u002F7. The live rate is on our [USDC to BRL corridor page](\u002Fusdc-to-brl).\n\nBelow is the flow in detail, plus what can go wrong at each step. For a comparison of this route against exchanges and P2P, see [USDC to BRL routes compared](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026).\n\n## Step 1: get a quote\n\nA quote locks the FX rate, the fee, and the exact BRL amount the receiver gets, typically for a few minutes. This matters because it removes rate risk from the transfer: the receiver amount is known before any money moves. Quotes also declare which side pays fees, so a payroll run can guarantee net amounts.\n\n## Step 2: verify the receiver\n\nBrazilian institutions verify the receiver's name against their tax ID (CPF for individuals, CNPJ for companies) before crediting an account. A payout API collects these once, runs KYC on the receiver, and reuses the verified identity for every later payment. The most common failure in the entire flow is a name and tax ID mismatch, so exact beneficiary data is the one thing to get right.\n\n## Step 3: send the USDC\n\nTransfer the quoted USDC amount to the provider on a supported network. From here the provider converts to reais at the locked rate; there is no separate trading step, order book, or manual withdrawal, which is what separates this route from selling on an exchange.\n\n## Step 4: reais arrive over Pix\n\nPix, the instant payment system run by the Banco Central do Brasil, settles transfers in seconds and is used by over 150 million Brazilians. Once conversion completes, the reais land in the receiver's account regardless of banking hours, weekends, or holidays.\n\n## Sending at scale\n\nFor one transfer, any compliant route works. For payroll, contractor payments, or marketplace payouts, the API route is built to repeat: one integration replaces per-transfer manual work, and each payment follows the same quote, verify, send, settle sequence. How the model works in general: [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide). Developer reference: [payouts documentation](\u002Fdocs\u002Fpayouts).\n\n## The regulatory backdrop\n\nBrazil regulates virtual asset services under Law 14.478\u002F2022, and the Central Bank's Resolutions 519, 520, and 521 (effective February 2, 2026) created an authorization regime for providers. Details in [PSAV in Brazil explained](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained). Practical implication: choose a provider operating within that regime, and expect real KYC on both sender and receiver.\n",{"title":5838,"description":5915},"resources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","O3LXLy057_4tlKXRbM7q7TvaLhjjJMcEjtjPR9xptGk",{"id":5947,"title":5948,"authors":6,"body":5949,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":6895,"description":6896,"extension":342,"faq":6897,"howto":6916,"isBlog":359,"isChangelog":359,"meta":6937,"navigation":362,"path":2712,"pillar":359,"products":6,"rawbody":6938,"role":6,"seo":6939,"seoTitle":6940,"stem":6941,"thumbnail":6,"updated":6,"__hash__":6942},"content\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api.md","Integrating a stablecoin API: a developer's guide to cross-border payments with BlindPay",{"type":8,"value":5950,"toc":6884},[5951,5954,5960,5964,6039,6046,6050,6053,6085,6088,6103,6107,6120,6180,6213,6224,6228,6231,6241,6250,6298,6328,6331,6335,6370,6373,6463,6490,6493,6497,6513,6569,6579,6656,6673,6677,6680,6730,6745,6807,6824,6844,6848,6854,6861,6863,6877,6881],[11,5952,5953],{},"Integrating a stablecoin API for cross-border payments takes five steps: authenticate with an instance-scoped API key, onboard a customer through KYC or KYB, fund a virtual USD account or register a stablecoin wallet, quote and create a payout to a local bank account, and handle signed webhooks for status changes. With BlindPay, a first payout in the development environment is typically a day of work using the REST API or one of the official SDKs.",[11,5955,5956,5957,227],{},"This guide walks through that flow with the actual endpoints, statuses, and event names. It is written for a developer or technical founder who has never moved money over stablecoins before. For the category background, read ",[136,5958,5959],{"href":479},"what a stablecoin API is",[18,5961,5963],{"id":5962},"what-you-will-need-to-get-started","What you will need to get started",[39,5965,5966,5975],{},[42,5967,5968],{},[45,5969,5970,5972],{},[48,5971,4683],{},[48,5973,5974],{},"Where to get it",[61,5976,5977,5985,5993,6023,6031],{},[45,5978,5979,5982],{},[66,5980,5981],{},"A BlindPay account and a development instance",[66,5983,5984],{},"Dashboard at app.blindpay.com; instances are created there, not through the API",[45,5986,5987,5990],{},[66,5988,5989],{},"An API key scoped to that instance",[66,5991,5992],{},"Instance settings, API Keys tab; shown once, so store it in a secrets manager",[45,5994,5995,5998],{},[66,5996,5997],{},"An SDK or an HTTP client",[66,5999,6000,6003,6004,6007,6008,1304,6011,1341,6014,6017,6018],{},[204,6001,6002],{},"@blindpay\u002Fnode"," on npm, ",[204,6005,6006],{},"blindpay"," on PyPI, ",[204,6009,6010],{},"blindpay-go",[204,6012,6013],{},"blindpay-php",[204,6015,6016],{},"blindpay-swift","; or generate a client from the ",[136,6019,6022],{"href":6020,"rel":6021},"https:\u002F\u002Fapi.blindpay.com\u002Fdoc",[414],"OpenAPI spec",[45,6024,6025,6028],{},[66,6026,6027],{},"A blockchain wallet you control",[66,6029,6030],{},"Any EVM, Solana, or Stellar wallet on a supported network; testnets work on development instances",[45,6032,6033,6036],{},[66,6034,6035],{},"An HTTPS endpoint for webhooks",[66,6037,6038],{},"Public URL; local and private addresses are rejected, so use a tunnel in development",[11,6040,6041,6042,6045],{},"Development instances are free, rate-limited to about 100 requests per minute, and skip banking-partner review so virtual accounts and payouts resolve immediately. Production access requires compliance onboarding and takes up to three business days. Read ",[136,6043,2673],{"href":6044},"\u002Fdocs\u002Flearn\u002Fsandbox-vs-production"," for the exact behavioral differences.",[18,6047,6049],{"id":6048},"step-1-authenticate","Step 1: Authenticate",[11,6051,6052],{},"Every request carries the API key as a Bearer token and targets a specific instance:",[4913,6054,6056],{"className":4915,"code":6055,"language":4917,"meta":328,"style":328},"GET \u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\nHost: api.blindpay.com\nAuthorization: Bearer YOUR_API_KEY\n",[204,6057,6058,6066,6074],{"__ignoreMap":328},[4921,6059,6060,6063],{"class":4923,"line":4924},[4921,6061,6062],{"class":4927},"GET",[4921,6064,6065],{"class":4931}," \u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\n",[4921,6067,6068,6071],{"class":4923,"line":329},[4921,6069,6070],{"class":4927},"Host:",[4921,6072,6073],{"class":4931}," api.blindpay.com\n",[4921,6075,6076,6079,6082],{"class":4923,"line":1404},[4921,6077,6078],{"class":4927},"Authorization:",[4921,6080,6081],{"class":4931}," Bearer",[4921,6083,6084],{"class":4931}," YOUR_API_KEY\n",[11,6086,6087],{},"There is no separate sandbox hostname. Which environment you hit is decided entirely by which instance the key belongs to, so a development key fails against a production instance and vice versa. Keys are full read and write, optionally locked to an IPv4 allowlist.",[11,6089,6090,6091,6094,6095,6098,6099,6102],{},"Two headers are worth adopting from the first request. ",[204,6092,6093],{},"Idempotency-Key"," on any write makes a network retry safe: the same key with the same body returns the original response with ",[204,6096,6097],{},"Idempotency-Replayed: true",", and a different body returns a 422. On development instances a 429 comes with ",[204,6100,6101],{},"Retry-After",", so build the backoff in now rather than when production traffic arrives.",[18,6104,6106],{"id":6105},"step-2-onboard-a-customer","Step 2: Onboard a customer",[11,6108,6109,6110,6112,6113,3740,6116,6119],{},"A customer is the person or business you will pay or collect from. Create one with ",[204,6111,206],{}," set to ",[204,6114,6115],{},"individual",[204,6117,6118],{},"business"," and the identity fields the docs list for that type. Compliance runs immediately.",[39,6121,6122,6138],{},[42,6123,6124],{},[45,6125,6126,6129,6132,6135],{},[48,6127,6128],{},"Onboarding path",[48,6130,6131],{},"Who",[48,6133,6134],{},"How it resolves",[48,6136,6137],{},"Typical time",[61,6139,6140,6154,6168],{},[45,6141,6142,6145,6148,6151],{},[66,6143,6144],{},"KYC standard",[66,6146,6147],{},"Individuals in standard-risk countries",[66,6149,6150],{},"Automated",[66,6152,6153],{},"About 60 seconds",[45,6155,6156,6159,6162,6165],{},[66,6157,6158],{},"KYC enhanced",[66,6160,6161],{},"Individuals in high-risk countries",[66,6163,6164],{},"Review",[66,6166,6167],{},"3 hours to 1 business day",[45,6169,6170,6173,6176,6178],{},[66,6171,6172],{},"KYB standard",[66,6174,6175],{},"Businesses",[66,6177,6164],{},[66,6179,6167],{},[11,6181,6182,6183,6186,6187,6189,6190,6192,6193,1304,6196,1304,6199,6202,6203,6205,6206,3740,6209,6212],{},"Poll or, better, listen for ",[204,6184,6185],{},"customer.update"," until ",[204,6188,2015],{}," reads ",[204,6191,5076],{},". Other statuses include ",[204,6194,6195],{},"verifying",[204,6197,6198],{},"pending_review",[204,6200,6201],{},"compliance_request"," when the team needs a document, and ",[204,6204,5080],{}," with the reason in ",[204,6207,6208],{},"kyc_warnings",[204,6210,6211],{},"fraud_warnings",". Customers in prohibited countries are blocked at creation and cannot be overridden, and KYC data on an existing customer cannot be edited, so treat a rejection as \"create a corrected customer\" rather than \"patch this one.\"",[11,6214,6215,6216,6218,6219,6223],{},"This is the step that turns compliance from a project into an API call. Sanctions screening and risk scoring happen here and again on each transfer, which is why a payout can later sit in ",[204,6217,2030],{}," without anything being wrong on your side. Read ",[136,6220,6222],{"href":6221},"\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments","how to automate KYC and KYB for stablecoin payments"," for the design behind it.",[18,6225,6227],{"id":6226},"step-3-create-a-virtual-usd-account-or-register-a-wallet","Step 3: Create a virtual USD account or register a wallet",[11,6229,6230],{},"You need stablecoins in a wallet to send a payout. There are two ways to get there.",[11,6232,6233,6236,6237,6240],{},[119,6234,6235],{},"If you already hold USDC or USDT",", register the wallet on the customer with ",[204,6238,6239],{},"POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fblockchain-wallets",", choosing the network and address. You will send the payout from this wallet.",[11,6242,6243,6246,6247,6249],{},[119,6244,6245],{},"If you hold dollars in a bank",", create a ",[136,6248,139],{"href":138},". It is a dedicated US account number that accepts ACH, domestic wire, and SWIFT deposits (RTP for some account types) and converts every deposit to USDC or USDT in the linked wallet. First attach a blockchain wallet to the approved customer, then:",[4913,6251,6253],{"className":4915,"code":6252,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fvirtual-accounts\nContent-Type: application\u002Fjson\n\n{\n  \"token\": \"USDC\",\n  \"blockchain_wallet_id\": \"bw_000000000000\"\n}\n",[204,6254,6255,6262,6268,6272,6276,6284,6294],{"__ignoreMap":328},[4921,6256,6257,6259],{"class":4923,"line":4924},[4921,6258,4928],{"class":4927},[4921,6260,6261],{"class":4931}," \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fvirtual-accounts\n",[4921,6263,6264,6266],{"class":4923,"line":329},[4921,6265,4937],{"class":4927},[4921,6267,4940],{"class":4931},[4921,6269,6270],{"class":4923,"line":1404},[4921,6271,4954],{"emptyLinePlaceholder":362},[4921,6273,6274],{"class":4923,"line":4951},[4921,6275,4961],{"class":4960},[4921,6277,6278,6280,6282],{"class":4923,"line":4957},[4921,6279,5125],{"class":4927},[4921,6281,580],{"class":4970},[4921,6283,5130],{"class":4931},[4921,6285,6286,6289,6291],{"class":4923,"line":4964},[4921,6287,6288],{"class":4927},"  \"blockchain_wallet_id\"",[4921,6290,580],{"class":4970},[4921,6292,6293],{"class":4931}," \"bw_000000000000\"\n",[4921,6295,6296],{"class":4923,"line":4976},[4921,6297,5066],{"class":4960},[11,6299,6300,6301,6304,6305,1304,6307,6309,6310,6312,6313,6315,6316,6319,6320,6323,6324,6327],{},"The request also takes a ",[204,6302,6303],{},"banking_partner"," from the documented list, and eligibility depends on the customer's country and business type. The response includes ",[204,6306,1987],{},[204,6308,3532],{},", and where applicable ",[204,6311,3516],{}," objects with routing and account numbers, and SWIFT details once the account is ",[204,6314,5076],{},". In development the account is approved instantly with fake numbers. Each incoming deposit creates a payin and fires ",[204,6317,6318],{},"payin.new"," and then ",[204,6321,6322],{},"payin.complete",", which is your signal that stablecoins have landed. Business customers need a few extra fields before a virtual account can be created, such as business type, industry, and ownership, and the API returns ",[204,6325,6326],{},"missing_required_fields"," naming exactly which ones.",[11,6329,6330],{},"This is the \"no pre-funding\" model in practice: you fund each transfer when you need it, from a wallet you control, rather than parking a balance in each destination currency.",[18,6332,6334],{"id":6333},"step-4-add-a-bank-account-and-request-a-quote","Step 4: Add a bank account and request a quote",[11,6336,6337,6338,6340,6341,1304,6343,1341,6345,6347,6348,6350,6351,6353,6354,6356,6357,1304,6359,1341,6361,6363,6364,6366,6367,6369],{},"Register the receiver's bank account once, with the rail as its ",[204,6339,206],{},": ",[204,6342,1981],{},[204,6344,3436],{},[204,6346,3452],{}," for Brazil, ",[204,6349,1984],{}," for Mexico, ",[204,6352,3500],{}," for Colombia, ",[204,6355,3484],{}," for Argentina, ",[204,6358,1987],{},[204,6360,3516],{},[204,6362,3532],{}," for the United States, ",[204,6365,1990],{}," for Europe, and ",[204,6368,3578],{}," for everywhere else. The public rails endpoint returns the live list, with countries, and needs no API key.",[11,6371,6372],{},"Then request a quote:",[4913,6374,6376],{"className":4915,"code":6375,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fquotes\nContent-Type: application\u002Fjson\n\n{\n  \"bank_account_id\": \"ba_000000000000\",\n  \"currency_type\": \"receiver\",\n  \"request_amount\": 500000,\n  \"cover_fees\": false,\n  \"network\": \"base\",\n  \"token\": \"USDC\"\n}\n",[204,6377,6378,6385,6391,6395,6399,6409,6419,6429,6442,6450,6459],{"__ignoreMap":328},[4921,6379,6380,6382],{"class":4923,"line":4924},[4921,6381,4928],{"class":4927},[4921,6383,6384],{"class":4931}," \u002Fv1\u002Finstances\u002F{instance_id}\u002Fquotes\n",[4921,6386,6387,6389],{"class":4923,"line":329},[4921,6388,4937],{"class":4927},[4921,6390,4940],{"class":4931},[4921,6392,6393],{"class":4923,"line":1404},[4921,6394,4954],{"emptyLinePlaceholder":362},[4921,6396,6397],{"class":4923,"line":4951},[4921,6398,4961],{"class":4960},[4921,6400,6401,6404,6406],{"class":4923,"line":4957},[4921,6402,6403],{"class":4927},"  \"bank_account_id\"",[4921,6405,580],{"class":4970},[4921,6407,6408],{"class":4931}," \"ba_000000000000\",\n",[4921,6410,6411,6414,6416],{"class":4923,"line":4964},[4921,6412,6413],{"class":4927},"  \"currency_type\"",[4921,6415,580],{"class":4970},[4921,6417,6418],{"class":4931}," \"receiver\",\n",[4921,6420,6421,6424,6426],{"class":4923,"line":4976},[4921,6422,6423],{"class":4927},"  \"request_amount\"",[4921,6425,580],{"class":4970},[4921,6427,6428],{"class":4931}," 500000,\n",[4921,6430,6431,6434,6436,6439],{"class":4923,"line":4987},[4921,6432,6433],{"class":4927},"  \"cover_fees\"",[4921,6435,580],{"class":4970},[4921,6437,6438],{"class":4970}," false",[4921,6440,6441],{"class":4931},",\n",[4921,6443,6444,6446,6448],{"class":4923,"line":4998},[4921,6445,5135],{"class":4927},[4921,6447,580],{"class":4970},[4921,6449,5140],{"class":4931},[4921,6451,6452,6454,6456],{"class":4923,"line":5009},[4921,6453,5125],{"class":4927},[4921,6455,580],{"class":4970},[4921,6457,6458],{"class":4931}," \"USDC\"\n",[4921,6460,6461],{"class":4923,"line":5020},[4921,6462,5066],{"class":4960},[11,6464,6465,6466,6469,6470,1304,6473,1304,6476,1304,6479,6482,6483,6485,6486,6489],{},"Amounts are integers in minor units, so the request above is 5,000.00 in the receiver's currency. ",[204,6467,6468],{},"currency_type"," decides whether you are fixing the stablecoin amount sent or the fiat amount received. The response returns ",[204,6471,6472],{},"commercial_quotation",[204,6474,6475],{},"blindpay_quotation",[204,6477,6478],{},"sender_amount",[204,6480,6481],{},"receiver_amount",", and the fees as separate fields, plus ",[204,6484,3865],{}," in epoch milliseconds. A quote is valid for five minutes and backs exactly one payout. For EVM networks the response also includes a ",[204,6487,6488],{},"contract"," object with the address, ABI, and amount to approve.",[11,6491,6492],{},"Show the receiver amount to your user before they confirm. That one field is what makes stablecoin payouts comparable to any other rail: the receiver gets exactly this, and it was known before anything moved.",[18,6494,6496],{"id":6495},"step-5-create-the-payout","Step 5: Create the payout",[11,6498,6499,6500,6502,6503,6506,6507,1341,6510,227],{},"Approve the quoted stablecoin amount from your wallet on-chain using the ",[204,6501,6488],{}," details in the quote, then create the payout on the endpoint for your network: ",[204,6504,6505],{},"\u002Fpayouts\u002Fevm"," for Ethereum, Polygon, Base, and Arbitrum, ",[204,6508,6509],{},"\u002Fpayouts\u002Fsolana",[204,6511,6512],{},"\u002Fpayouts\u002Fstellar",[4913,6514,6516],{"className":4915,"code":6515,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fpayouts\u002Fevm\nContent-Type: application\u002Fjson\nIdempotency-Key: 8f6a0c2e-...\n\n{\n  \"quote_id\": \"qu_000000000000\",\n  \"sender_wallet_address\": \"0x...\"\n}\n",[204,6517,6518,6525,6531,6538,6542,6546,6556,6565],{"__ignoreMap":328},[4921,6519,6520,6522],{"class":4923,"line":4924},[4921,6521,4928],{"class":4927},[4921,6523,6524],{"class":4931}," \u002Fv1\u002Finstances\u002F{instance_id}\u002Fpayouts\u002Fevm\n",[4921,6526,6527,6529],{"class":4923,"line":329},[4921,6528,4937],{"class":4927},[4921,6530,4940],{"class":4931},[4921,6532,6533,6535],{"class":4923,"line":1404},[4921,6534,4945],{"class":4927},[4921,6536,6537],{"class":4931}," 8f6a0c2e-...\n",[4921,6539,6540],{"class":4923,"line":4951},[4921,6541,4954],{"emptyLinePlaceholder":362},[4921,6543,6544],{"class":4923,"line":4957},[4921,6545,4961],{"class":4960},[4921,6547,6548,6551,6553],{"class":4923,"line":4964},[4921,6549,6550],{"class":4927},"  \"quote_id\"",[4921,6552,580],{"class":4970},[4921,6554,6555],{"class":4931}," \"qu_000000000000\",\n",[4921,6557,6558,6561,6563],{"class":4923,"line":4976},[4921,6559,6560],{"class":4927},"  \"sender_wallet_address\"",[4921,6562,580],{"class":4970},[4921,6564,5149],{"class":4931},[4921,6566,6567],{"class":4923,"line":4987},[4921,6568,5066],{"class":4960},[11,6570,6571,6572,1304,6575,6578],{},"The response is a payout with ",[204,6573,6574],{},"id",[204,6576,6577],{},"status",", and five tracking objects covering the on-chain transaction, liquidity, partner fee, payment, and completion, each with its own step. The status values are:",[39,6580,6581,6594],{},[42,6582,6583],{},[45,6584,6585,6588,6591],{},[48,6586,6587],{},"Status",[48,6589,6590],{},"Meaning",[48,6592,6593],{},"What your system should do",[61,6595,6596,6608,6620,6632,6644],{},[45,6597,6598,6602,6605],{},[66,6599,6600],{},[204,6601,3834],{},[66,6603,6604],{},"Funds pulled, conversion and delivery in progress",[66,6606,6607],{},"Show pending",[45,6609,6610,6614,6617],{},[66,6611,6612],{},[204,6613,2030],{},[66,6615,6616],{},"Compliance or banking review before release; every SWIFT payout starts here, ACH, wire, and RTP pass through it",[66,6618,6619],{},"Show pending, do not retry",[45,6621,6622,6626,6629],{},[66,6623,6624],{},[204,6625,3837],{},[66,6627,6628],{},"Local currency delivered over the rail",[66,6630,6631],{},"Mark paid, store the rail reference",[45,6633,6634,6638,6641],{},[66,6635,6636],{},[204,6637,3739],{},[66,6639,6640],{},"Delivery could not complete",[66,6642,6643],{},"Surface the reason, funds return to the sender wallet",[45,6645,6646,6650,6653],{},[66,6647,6648],{},[204,6649,3743],{},[66,6651,6652],{},"Funds returned after a failure downstream",[66,6654,6655],{},"Reconcile the return",[11,6657,6658,6659,6662,6663,6665,6666,1337,6668,6665,6670,6672],{},"Delivery time depends on the rail: minutes on Pix, SPEI, and Transfers 3.0, instant on RTP, one to two business days on ACH, TED, and SEPA, up to five on SWIFT, where each payout carries a UETR and an MT103 confirmation. SWIFT payouts have a 100 USD minimum. In development, a ",[204,6660,6661],{},"request_amount"," of ",[204,6664,3903],{}," forces ",[204,6667,3739],{},[204,6669,3906],{},[204,6671,3743],{},", so you can test the unhappy paths without waiting for one to happen.",[18,6674,6676],{"id":6675},"step-6-handle-webhooks","Step 6: Handle webhooks",[11,6678,6679],{},"Polling works, but webhooks are how the integration is meant to run. Register an endpoint:",[4913,6681,6683],{"className":4915,"code":6682,"language":4917,"meta":328,"style":328},"POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fwebhook-endpoints\nContent-Type: application\u002Fjson\n\n{\n  \"url\": \"https:\u002F\u002Fexample.com\u002Fwebhooks\u002Fblindpay\",\n  \"events\": []\n}\n",[204,6684,6685,6692,6698,6702,6706,6716,6726],{"__ignoreMap":328},[4921,6686,6687,6689],{"class":4923,"line":4924},[4921,6688,4928],{"class":4927},[4921,6690,6691],{"class":4931}," \u002Fv1\u002Finstances\u002F{instance_id}\u002Fwebhook-endpoints\n",[4921,6693,6694,6696],{"class":4923,"line":329},[4921,6695,4937],{"class":4927},[4921,6697,4940],{"class":4931},[4921,6699,6700],{"class":4923,"line":1404},[4921,6701,4954],{"emptyLinePlaceholder":362},[4921,6703,6704],{"class":4923,"line":4951},[4921,6705,4961],{"class":4960},[4921,6707,6708,6711,6713],{"class":4923,"line":4957},[4921,6709,6710],{"class":4927},"  \"url\"",[4921,6712,580],{"class":4970},[4921,6714,6715],{"class":4931}," \"https:\u002F\u002Fexample.com\u002Fwebhooks\u002Fblindpay\",\n",[4921,6717,6718,6721,6723],{"class":4923,"line":4964},[4921,6719,6720],{"class":4927},"  \"events\"",[4921,6722,580],{"class":4970},[4921,6724,6725],{"class":4960}," []\n",[4921,6727,6728],{"class":4923,"line":4976},[4921,6729,5066],{"class":4960},[11,6731,6732,6733,6736,6737,6740,6741,6744],{},"An empty ",[204,6734,6735],{},"events"," array subscribes to everything. Fetch the endpoint's signing secret with a GET on its ",[204,6738,6739],{},"\u002Fsecret"," path; it starts with ",[204,6742,6743],{},"whsec_",". The events you will handle most:",[39,6746,6747,6757],{},[42,6748,6749],{},[45,6750,6751,6754],{},[48,6752,6753],{},"Event",[48,6755,6756],{},"Fires when",[61,6758,6759,6768,6777,6788,6797],{},[45,6760,6761,6765],{},[66,6762,6763],{},[204,6764,6185],{},[66,6766,6767],{},"KYC or KYB status changes",[45,6769,6770,6774],{},[66,6771,6772],{},[204,6773,6322],{},[66,6775,6776],{},"A virtual account deposit has converted and landed",[45,6778,6779,6783],{},[66,6780,6781],{},[204,6782,3850],{},[66,6784,6785,6786],{},"A payout changes status, including to ",[204,6787,3739],{},[45,6789,6790,6794],{},[66,6791,6792],{},[204,6793,3856],{},[66,6795,6796],{},"Local currency has been delivered",[45,6798,6799,6804],{},[66,6800,6801],{},[204,6802,6803],{},"virtualAccount.complete",[66,6805,6806],{},"A virtual account has finished review",[11,6808,6809,6810,1304,6813,1313,6816,6819,6820,6823],{},"Verify every delivery. The headers are ",[204,6811,6812],{},"svix-id",[204,6814,6815],{},"svix-timestamp",[204,6817,6818],{},"svix-signature",". Concatenate the id, the timestamp, and the raw body with dots, compute HMAC-SHA256 with the base64-decoded secret, and compare against each ",[204,6821,6822],{},"v1,"," entry in the signature header using a constant-time comparison. Reject anything older than five minutes.",[11,6825,6826,6827,6829,6830,6832,6833,6835,6836,6838,6839,6843],{},"Two details save debugging time. A ",[204,6828,3739],{}," payout fires ",[204,6831,3850],{},", not ",[204,6834,3856],{},", so key your terminal-state logic on status rather than event name. And retries reuse the same ",[204,6837,6812],{},", so store it and skip duplicates. Failed deliveries are retried with backoff over the following hours, and any event can be replayed from the dashboard without creating a new business event. Read the ",[136,6840,6842],{"href":6841},"\u002Fdocs\u002Flearn\u002Fwebhooks-events","webhook events reference"," for the full list.",[18,6845,6847],{"id":6846},"how-openapi-and-sdks-shorten-the-integration","How OpenAPI and SDKs shorten the integration",[11,6849,6850,6851,6853],{},"Every endpoint above is described in a single OpenAPI 3.1 document at ",[204,6852,6020],{},". The official SDKs for Node, Python, Go, PHP, and Swift are generated from it, so field names, enums, and error shapes match the docs exactly and a new API field shows up as a typed property rather than a surprise in a JSON blob.",[11,6855,6856,6857,6860],{},"The same spec is what makes AI-assisted integration work. The MCP server, ",[204,6858,6859],{},"npx -y @blindpay\u002Fmcp",", lets a coding agent in Claude Code or Codex call the API against your development instance while you build. The docs publish llms.txt and a raw markdown twin of every page, so an agent can read the reference the same way you do. The practical effect is that the first payout in development is usually a day of work, and most of that day is your own ledger and UI, not the API.",[18,6862,312],{"id":311},[11,6864,6865,6866,6868,6869,6871,6872,6874,6875,227],{},"Create a development instance, run the six steps above against testnet, and force a ",[204,6867,3739],{}," and a ",[204,6870,3743],{}," payout with the sentinel amounts before you write a line of production code. Then read ",[136,6873,285],{"href":284}," to check that the provider you are integrating clears the bar on pre-funding, compliance, and pricing, or go straight to the ",[136,6876,319],{"href":318},[11,6878,6879],{},[324,6880,326],{},[5763,6882,6883],{},"html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}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);}html pre.shiki code .sgsFI, html code.shiki .sgsFI{--shiki-default:#24292E}html pre.shiki code .sYu0t, html code.shiki .sYu0t{--shiki-default:#005CC5}",{"title":328,"searchDepth":329,"depth":329,"links":6885},[6886,6887,6888,6889,6890,6891,6892,6893,6894],{"id":5962,"depth":329,"text":5963},{"id":6048,"depth":329,"text":6049},{"id":6105,"depth":329,"text":6106},{"id":6226,"depth":329,"text":6227},{"id":6333,"depth":329,"text":6334},{"id":6495,"depth":329,"text":6496},{"id":6675,"depth":329,"text":6676},{"id":6846,"depth":329,"text":6847},{"id":311,"depth":329,"text":312},"2026-09-17","Step-by-step stablecoin API integration: authenticate, onboard a customer, open a virtual USD account, quote and send a payout, handle webhooks.",[6898,6901,6904,6907,6910,6913],{"q":6899,"a":6900},"Does the BlindPay API have a sandbox environment?","Yes. Every account can create development instances, and a development API key routes all requests to the development environment on the same hostname. Development instances skip banking-partner review, return fake bank account numbers, and accept sentinel amounts that force a payout into failed or refunded so you can test every path.",{"q":6902,"a":6903},"Which currencies and countries does the stablecoin API support?","Stablecoins USDC and USDT on Ethereum, Polygon, Base, Arbitrum, Solana, Stellar, and Tron, converting to BRL over Pix, PIX Safe, and TED in Brazil, MXN over SPEI in Mexico, COP over ACH in Colombia, ARS over Transfers 3.0 in Argentina, USD over ACH, RTP, and domestic wire in the United States, EUR over SEPA, and USD to 100+ countries over SWIFT (POBO\u002FCOBO). The live list is available from the public rails endpoint without an API key.",{"q":6905,"a":6906},"How are compliance checks handled during onboarding?","Each customer goes through KYC or KYB inside the API. Standard individual KYC is automated and typically resolves in about a minute. Enhanced KYC for high-risk countries and standard KYB for businesses go through review, usually within a few hours and up to one business day. Sanctions screening runs on customers and on payouts, and a hold shows up as an on_hold payout status rather than a silent delay.",{"q":6908,"a":6909},"Are webhooks reliable, and how do I verify them?","Deliveries are signed with HMAC-SHA256 and carry svix-id, svix-timestamp, and svix-signature headers. A non-2xx response is retried with backoff over the following hours, and svix-id stays the same across retries, so use it as your deduplication key. You can also replay any event from the dashboard.",{"q":6911,"a":6912},"Do I need to hold crypto to send a cross-border payout?","No. Deposit dollars into a virtual USD account over ACH, wire, or SWIFT and the deposit converts to USDC or USDT in the linked wallet. From there the payout flow is identical to sending from a wallet you funded yourself.",{"q":6914,"a":6915},"Which SDKs are available?","Official SDKs cover Node and TypeScript, Python, Go, PHP, and Swift, all generated from the OpenAPI specification. There is also an MCP server so AI coding tools can call the API directly, and the docs publish llms.txt for agent consumption.",{"name":6917,"steps":6918},"How to integrate a stablecoin API for cross-border payments",[6919,6922,6925,6928,6931,6934],{"name":6920,"text":6921},"Authenticate with an instance-scoped API key","Create a development instance in the dashboard, generate an API key, and send it as a Bearer token. Every request goes to https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002F{instance_id}\u002F... and the key decides whether you hit development or production.",{"name":6923,"text":6924},"Onboard a customer and pass KYC or KYB","Create a customer with type individual or business. Standard individual KYC is automated and usually resolves in about a minute; business KYB goes through review. Wait for kyc_status approved before creating accounts.",{"name":6926,"text":6927},"Create a virtual USD account or register a wallet","Attach a blockchain wallet to the approved customer, then create a virtual account that accepts ACH, wire, or SWIFT deposits and converts them to USDC or USDT into that wallet. If you already hold stablecoins, register the wallet and skip the virtual account.",{"name":6929,"text":6930},"Add the receiver's bank account and request a quote","Register the destination bank account with its rail type, such as pix, spei_bitso, ach, or international_swift. Request a quote with the amount in minor units; the response locks the rate, itemizes fees, shows the receive amount, and expires in five minutes.",{"name":6932,"text":6933},"Create the payout","Approve the quoted stablecoin amount on-chain from your wallet, then create the payout with the quote id and sender wallet address. The response returns a payout id with per-step tracking and a status of processing, on_hold, completed, failed, or refunded.",{"name":6935,"text":6936},"Handle webhooks for status updates","Register an HTTPS webhook endpoint, verify each delivery with the svix-id, svix-timestamp, and svix-signature headers using the endpoint secret, and dedupe on svix-id. Listen for payout.update and payout.complete to drive your ledger.",{"author":361},"---\ntitle: \"Integrating a stablecoin API: a developer's guide to cross-border payments with BlindPay\"\nseoTitle: \"How to integrate a stablecoin API\"\ndescription: \"Step-by-step stablecoin API integration: authenticate, onboard a customer, open a virtual USD account, quote and send a payout, handle webhooks.\"\ndate: \"2026-09-17\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to integrate a stablecoin API for cross-border payments\"\n  steps:\n    - name: \"Authenticate with an instance-scoped API key\"\n      text: \"Create a development instance in the dashboard, generate an API key, and send it as a Bearer token. Every request goes to https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002F{instance_id}\u002F... and the key decides whether you hit development or production.\"\n    - name: \"Onboard a customer and pass KYC or KYB\"\n      text: \"Create a customer with type individual or business. Standard individual KYC is automated and usually resolves in about a minute; business KYB goes through review. Wait for kyc_status approved before creating accounts.\"\n    - name: \"Create a virtual USD account or register a wallet\"\n      text: \"Attach a blockchain wallet to the approved customer, then create a virtual account that accepts ACH, wire, or SWIFT deposits and converts them to USDC or USDT into that wallet. If you already hold stablecoins, register the wallet and skip the virtual account.\"\n    - name: \"Add the receiver's bank account and request a quote\"\n      text: \"Register the destination bank account with its rail type, such as pix, spei_bitso, ach, or international_swift. Request a quote with the amount in minor units; the response locks the rate, itemizes fees, shows the receive amount, and expires in five minutes.\"\n    - name: \"Create the payout\"\n      text: \"Approve the quoted stablecoin amount on-chain from your wallet, then create the payout with the quote id and sender wallet address. The response returns a payout id with per-step tracking and a status of processing, on_hold, completed, failed, or refunded.\"\n    - name: \"Handle webhooks for status updates\"\n      text: \"Register an HTTPS webhook endpoint, verify each delivery with the svix-id, svix-timestamp, and svix-signature headers using the endpoint secret, and dedupe on svix-id. Listen for payout.update and payout.complete to drive your ledger.\"\nfaq:\n  - q: \"Does the BlindPay API have a sandbox environment?\"\n    a: \"Yes. Every account can create development instances, and a development API key routes all requests to the development environment on the same hostname. Development instances skip banking-partner review, return fake bank account numbers, and accept sentinel amounts that force a payout into failed or refunded so you can test every path.\"\n  - q: \"Which currencies and countries does the stablecoin API support?\"\n    a: \"Stablecoins USDC and USDT on Ethereum, Polygon, Base, Arbitrum, Solana, Stellar, and Tron, converting to BRL over Pix, PIX Safe, and TED in Brazil, MXN over SPEI in Mexico, COP over ACH in Colombia, ARS over Transfers 3.0 in Argentina, USD over ACH, RTP, and domestic wire in the United States, EUR over SEPA, and USD to 100+ countries over SWIFT (POBO\u002FCOBO). The live list is available from the public rails endpoint without an API key.\"\n  - q: \"How are compliance checks handled during onboarding?\"\n    a: \"Each customer goes through KYC or KYB inside the API. Standard individual KYC is automated and typically resolves in about a minute. Enhanced KYC for high-risk countries and standard KYB for businesses go through review, usually within a few hours and up to one business day. Sanctions screening runs on customers and on payouts, and a hold shows up as an on_hold payout status rather than a silent delay.\"\n  - q: \"Are webhooks reliable, and how do I verify them?\"\n    a: \"Deliveries are signed with HMAC-SHA256 and carry svix-id, svix-timestamp, and svix-signature headers. A non-2xx response is retried with backoff over the following hours, and svix-id stays the same across retries, so use it as your deduplication key. You can also replay any event from the dashboard.\"\n  - q: \"Do I need to hold crypto to send a cross-border payout?\"\n    a: \"No. Deposit dollars into a virtual USD account over ACH, wire, or SWIFT and the deposit converts to USDC or USDT in the linked wallet. From there the payout flow is identical to sending from a wallet you funded yourself.\"\n  - q: \"Which SDKs are available?\"\n    a: \"Official SDKs cover Node and TypeScript, Python, Go, PHP, and Swift, all generated from the OpenAPI specification. There is also an MCP server so AI coding tools can call the API directly, and the docs publish llms.txt for agent consumption.\"\n---\n\nIntegrating a stablecoin API for cross-border payments takes five steps: authenticate with an instance-scoped API key, onboard a customer through KYC or KYB, fund a virtual USD account or register a stablecoin wallet, quote and create a payout to a local bank account, and handle signed webhooks for status changes. With BlindPay, a first payout in the development environment is typically a day of work using the REST API or one of the official SDKs.\n\nThis guide walks through that flow with the actual endpoints, statuses, and event names. It is written for a developer or technical founder who has never moved money over stablecoins before. For the category background, read [what a stablecoin API is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api).\n\n## What you will need to get started\n\n| Requirement | Where to get it |\n| --- | --- |\n| A BlindPay account and a development instance | Dashboard at app.blindpay.com; instances are created there, not through the API |\n| An API key scoped to that instance | Instance settings, API Keys tab; shown once, so store it in a secrets manager |\n| An SDK or an HTTP client | `@blindpay\u002Fnode` on npm, `blindpay` on PyPI, `blindpay-go`, `blindpay-php`, or `blindpay-swift`; or generate a client from the [OpenAPI spec](https:\u002F\u002Fapi.blindpay.com\u002Fdoc) |\n| A blockchain wallet you control | Any EVM, Solana, or Stellar wallet on a supported network; testnets work on development instances |\n| An HTTPS endpoint for webhooks | Public URL; local and private addresses are rejected, so use a tunnel in development |\n\nDevelopment instances are free, rate-limited to about 100 requests per minute, and skip banking-partner review so virtual accounts and payouts resolve immediately. Production access requires compliance onboarding and takes up to three business days. Read [sandbox vs production](\u002Fdocs\u002Flearn\u002Fsandbox-vs-production) for the exact behavioral differences.\n\n## Step 1: Authenticate\n\nEvery request carries the API key as a Bearer token and targets a specific instance:\n\n```bash\nGET \u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\nHost: api.blindpay.com\nAuthorization: Bearer YOUR_API_KEY\n```\n\nThere is no separate sandbox hostname. Which environment you hit is decided entirely by which instance the key belongs to, so a development key fails against a production instance and vice versa. Keys are full read and write, optionally locked to an IPv4 allowlist.\n\nTwo headers are worth adopting from the first request. `Idempotency-Key` on any write makes a network retry safe: the same key with the same body returns the original response with `Idempotency-Replayed: true`, and a different body returns a 422. On development instances a 429 comes with `Retry-After`, so build the backoff in now rather than when production traffic arrives.\n\n## Step 2: Onboard a customer\n\nA customer is the person or business you will pay or collect from. Create one with `type` set to `individual` or `business` and the identity fields the docs list for that type. Compliance runs immediately.\n\n| Onboarding path | Who | How it resolves | Typical time |\n| --- | --- | --- | --- |\n| KYC standard | Individuals in standard-risk countries | Automated | About 60 seconds |\n| KYC enhanced | Individuals in high-risk countries | Review | 3 hours to 1 business day |\n| KYB standard | Businesses | Review | 3 hours to 1 business day |\n\nPoll or, better, listen for `customer.update` until `kyc_status` reads `approved`. Other statuses include `verifying`, `pending_review`, `compliance_request` when the team needs a document, and `rejected` with the reason in `kyc_warnings` or `fraud_warnings`. Customers in prohibited countries are blocked at creation and cannot be overridden, and KYC data on an existing customer cannot be edited, so treat a rejection as \"create a corrected customer\" rather than \"patch this one.\"\n\nThis is the step that turns compliance from a project into an API call. Sanctions screening and risk scoring happen here and again on each transfer, which is why a payout can later sit in `on_hold` without anything being wrong on your side. Read [how to automate KYC and KYB for stablecoin payments](\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments) for the design behind it.\n\n## Step 3: Create a virtual USD account or register a wallet\n\nYou need stablecoins in a wallet to send a payout. There are two ways to get there.\n\n**If you already hold USDC or USDT**, register the wallet on the customer with `POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fblockchain-wallets`, choosing the network and address. You will send the payout from this wallet.\n\n**If you hold dollars in a bank**, create a [virtual USD account](\u002Fvirtual-accounts). It is a dedicated US account number that accepts ACH, domestic wire, and SWIFT deposits (RTP for some account types) and converts every deposit to USDC or USDT in the linked wallet. First attach a blockchain wallet to the approved customer, then:\n\n```bash\nPOST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fvirtual-accounts\nContent-Type: application\u002Fjson\n\n{\n  \"token\": \"USDC\",\n  \"blockchain_wallet_id\": \"bw_000000000000\"\n}\n```\n\nThe request also takes a `banking_partner` from the documented list, and eligibility depends on the customer's country and business type. The response includes `ach`, `wire`, and where applicable `rtp` objects with routing and account numbers, and SWIFT details once the account is `approved`. In development the account is approved instantly with fake numbers. Each incoming deposit creates a payin and fires `payin.new` and then `payin.complete`, which is your signal that stablecoins have landed. Business customers need a few extra fields before a virtual account can be created, such as business type, industry, and ownership, and the API returns `missing_required_fields` naming exactly which ones.\n\nThis is the \"no pre-funding\" model in practice: you fund each transfer when you need it, from a wallet you control, rather than parking a balance in each destination currency.\n\n## Step 4: Add a bank account and request a quote\n\nRegister the receiver's bank account once, with the rail as its `type`: `pix`, `pix_safe`, or `ted` for Brazil, `spei_bitso` for Mexico, `ach_cop_bitso` for Colombia, `transfers_bitso` for Argentina, `ach`, `rtp`, or `wire` for the United States, `sepa` for Europe, and `international_swift` for everywhere else. The public rails endpoint returns the live list, with countries, and needs no API key.\n\nThen request a quote:\n\n```bash\nPOST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fquotes\nContent-Type: application\u002Fjson\n\n{\n  \"bank_account_id\": \"ba_000000000000\",\n  \"currency_type\": \"receiver\",\n  \"request_amount\": 500000,\n  \"cover_fees\": false,\n  \"network\": \"base\",\n  \"token\": \"USDC\"\n}\n```\n\nAmounts are integers in minor units, so the request above is 5,000.00 in the receiver's currency. `currency_type` decides whether you are fixing the stablecoin amount sent or the fiat amount received. The response returns `commercial_quotation`, `blindpay_quotation`, `sender_amount`, `receiver_amount`, and the fees as separate fields, plus `expires_at` in epoch milliseconds. A quote is valid for five minutes and backs exactly one payout. For EVM networks the response also includes a `contract` object with the address, ABI, and amount to approve.\n\nShow the receiver amount to your user before they confirm. That one field is what makes stablecoin payouts comparable to any other rail: the receiver gets exactly this, and it was known before anything moved.\n\n## Step 5: Create the payout\n\nApprove the quoted stablecoin amount from your wallet on-chain using the `contract` details in the quote, then create the payout on the endpoint for your network: `\u002Fpayouts\u002Fevm` for Ethereum, Polygon, Base, and Arbitrum, `\u002Fpayouts\u002Fsolana`, or `\u002Fpayouts\u002Fstellar`.\n\n```bash\nPOST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fpayouts\u002Fevm\nContent-Type: application\u002Fjson\nIdempotency-Key: 8f6a0c2e-...\n\n{\n  \"quote_id\": \"qu_000000000000\",\n  \"sender_wallet_address\": \"0x...\"\n}\n```\n\nThe response is a payout with `id`, `status`, and five tracking objects covering the on-chain transaction, liquidity, partner fee, payment, and completion, each with its own step. The status values are:\n\n| Status | Meaning | What your system should do |\n| --- | --- | --- |\n| `processing` | Funds pulled, conversion and delivery in progress | Show pending |\n| `on_hold` | Compliance or banking review before release; every SWIFT payout starts here, ACH, wire, and RTP pass through it | Show pending, do not retry |\n| `completed` | Local currency delivered over the rail | Mark paid, store the rail reference |\n| `failed` | Delivery could not complete | Surface the reason, funds return to the sender wallet |\n| `refunded` | Funds returned after a failure downstream | Reconcile the return |\n\nDelivery time depends on the rail: minutes on Pix, SPEI, and Transfers 3.0, instant on RTP, one to two business days on ACH, TED, and SEPA, up to five on SWIFT, where each payout carries a UETR and an MT103 confirmation. SWIFT payouts have a 100 USD minimum. In development, a `request_amount` of `66600` forces `failed` and `77700` forces `refunded`, so you can test the unhappy paths without waiting for one to happen.\n\n## Step 6: Handle webhooks\n\nPolling works, but webhooks are how the integration is meant to run. Register an endpoint:\n\n```bash\nPOST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fwebhook-endpoints\nContent-Type: application\u002Fjson\n\n{\n  \"url\": \"https:\u002F\u002Fexample.com\u002Fwebhooks\u002Fblindpay\",\n  \"events\": []\n}\n```\n\nAn empty `events` array subscribes to everything. Fetch the endpoint's signing secret with a GET on its `\u002Fsecret` path; it starts with `whsec_`. The events you will handle most:\n\n| Event | Fires when |\n| --- | --- |\n| `customer.update` | KYC or KYB status changes |\n| `payin.complete` | A virtual account deposit has converted and landed |\n| `payout.update` | A payout changes status, including to `failed` |\n| `payout.complete` | Local currency has been delivered |\n| `virtualAccount.complete` | A virtual account has finished review |\n\nVerify every delivery. The headers are `svix-id`, `svix-timestamp`, and `svix-signature`. Concatenate the id, the timestamp, and the raw body with dots, compute HMAC-SHA256 with the base64-decoded secret, and compare against each `v1,` entry in the signature header using a constant-time comparison. Reject anything older than five minutes.\n\nTwo details save debugging time. A `failed` payout fires `payout.update`, not `payout.complete`, so key your terminal-state logic on status rather than event name. And retries reuse the same `svix-id`, so store it and skip duplicates. Failed deliveries are retried with backoff over the following hours, and any event can be replayed from the dashboard without creating a new business event. Read the [webhook events reference](\u002Fdocs\u002Flearn\u002Fwebhooks-events) for the full list.\n\n## How OpenAPI and SDKs shorten the integration\n\nEvery endpoint above is described in a single OpenAPI 3.1 document at `https:\u002F\u002Fapi.blindpay.com\u002Fdoc`. The official SDKs for Node, Python, Go, PHP, and Swift are generated from it, so field names, enums, and error shapes match the docs exactly and a new API field shows up as a typed property rather than a surprise in a JSON blob.\n\nThe same spec is what makes AI-assisted integration work. The MCP server, `npx -y @blindpay\u002Fmcp`, lets a coding agent in Claude Code or Codex call the API against your development instance while you build. The docs publish llms.txt and a raw markdown twin of every page, so an agent can read the reference the same way you do. The practical effect is that the first payout in development is usually a day of work, and most of that day is your own ledger and UI, not the API.\n\n## What to do next\n\nCreate a development instance, run the six steps above against testnet, and force a `failed` and a `refunded` payout with the sentinel amounts before you write a line of production code. Then read [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api) to check that the provider you are integrating clears the bar on pre-funding, compliance, and pricing, or go straight to the [payout quickstart](\u002Fdocs\u002Fquickstart-payout).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5948,"description":6896},"How to integrate a stablecoin API","resources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api","0uqiOX9rfGDgGUm8M6Ob3CBHeHF6rg9C2zcrwBSPsro",{"id":6944,"title":6945,"authors":6,"body":6946,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":7466,"description":7467,"extension":342,"faq":7468,"howto":6,"isBlog":359,"isChangelog":359,"meta":7490,"navigation":362,"path":1226,"pillar":359,"products":6,"rawbody":7491,"role":6,"seo":7492,"seoTitle":7493,"stem":7494,"thumbnail":6,"updated":6,"__hash__":7495},"content\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam.md","Marketplace payouts in Latin America: stablecoin rails for sellers in Brazil, Mexico, Colombia, and Argentina",{"type":8,"value":6947,"toc":7454},[6948,6951,6954,6963,6967,6970,6976,6982,6988,6994,6997,7005,7009,7012,7019,7101,7107,7113,7118,7124,7130,7134,7137,7211,7221,7232,7243,7254,7260,7264,7267,7303,7306,7316,7327,7331,7334,7340,7344,7347,7371,7374,7380,7386,7396,7400,7415,7421,7425,7437,7440,7450],[11,6949,6950],{},"Marketplace payouts in Latin America are the payments a platform sends to its sellers, creators, drivers, or vendors in Brazil, Mexico, Colombia, and Argentina. Done over wires, they are slow, expensive, and unpredictable. Done over stablecoin rails, they land in minutes as local currency at a quoted amount, and the economics of a small payout stop being a problem.",[11,6952,6953],{},"This guide is for three readers: the operations lead at a marketplace with thousands of LATAM sellers, the engineer evaluating a payout API, and the CFO at a US or European company expanding into the region. It covers why the old rails fail, how stablecoin payouts work end to end, which local rails are supported, and what the integration looks like.",[11,6955,6956,6957,6962],{},"Latin America is the most stablecoin-native region for cross-border payments. In Fireblocks' 2025 institutional survey, ",[136,6958,6961],{"href":6959,"rel":6960},"https:\u002F\u002Fwww.fireblocks.com\u002Fblog\u002Fexecution-in-motion-how-latin-america-is-leading-stablecoin-adoption",[414],"71 percent of Latin American institutions"," already used stablecoins for cross-border payments, the highest rate of any region. Marketplaces are a large share of that flow.",[18,6964,6966],{"id":6965},"why-traditional-payment-methods-fail-latam-marketplaces","Why traditional payment methods fail LATAM marketplaces",[11,6968,6969],{},"Traditional payment methods fail LATAM marketplaces because they were built for a few large payments, not thousands of small ones. A freelance platform with 4,000 active sellers in Brazil that pays by international wire runs into the same four constraints every cycle.",[11,6971,6972,6975],{},[119,6973,6974],{},"Per-payout cost."," A wire costs $25 to $50 to send, so paying a $40 balance is a loss. Hence payout minimums.",[11,6977,6978,6981],{},[119,6979,6980],{},"Cycle time."," Batching makes wires cheaper, so payouts run weekly or biweekly. Sellers wait.",[11,6983,6984,6987],{},[119,6985,6986],{},"Landing time."," Two to five business days, plus a day of compliance screening at the receiving bank, plus receiving-bank fees the platform cannot predict. A seller below the minimum waits another two weeks; a seller above it gets money the following Wednesday, minus something.",[11,6989,6990,6993],{},[119,6991,6992],{},"Failure handling."," Bad account data fails days later with a code, and the money comes back minus fees. Support handles the fallout, and the ticket always reads the same way: \"Where is my money.\"",[11,6995,6996],{},"Domestic US rails do not help. ACH and real-time payments over RTP or FedNow are US-only. Card payouts to LATAM cards exist but carry 1.5 to 2.9 percent fees and multi-day settlement. Local processors solve one country at a time, so a platform in four countries ends up with four contracts, four pre-funded balances, and four reconciliation formats.",[11,6998,6999,7000,7004],{},"Stack those together and the seller experience is \"money arrives sometime in the next three weeks, amount varies.\" Sellers pick the platform that pays them fastest and most predictably, and in Latin America that has historically been the local one. For a grounding on the asset itself, the ",[136,7001,7003],{"href":7002},"\u002Fresources\u002Fmore\u002Fstablecoins","stablecoins section"," explains what USDC and USDT are and how they hold their peg.",[18,7006,7008],{"id":7007},"how-stablecoin-apis-power-real-time-payments-to-vendors","How stablecoin APIs power real-time payments to vendors",[11,7010,7011],{},"A stablecoin API powers real-time vendor payments by replacing the correspondent bank chain with a single conversion step. The platform funds in USD or USDC, each payout converts to local currency at a quoted rate, and the money lands over the local instant rail. The seller gives a bank account and sees a Pix or SPEI transfer arrive. They never see a wallet, a chain, or a token.",[11,7013,7014,7015,7018],{},"Run the four constraints again with a ",[136,7016,7017],{"href":299},"stablecoin payout API"," underneath.",[39,7020,7021,7034],{},[42,7022,7023],{},[45,7024,7025,7028,7031],{},[48,7026,7027],{},"Constraint",[48,7029,7030],{},"Wire-based payouts",[48,7032,7033],{},"Stablecoin payouts",[61,7035,7036,7046,7057,7068,7079,7090],{},[45,7037,7038,7041,7043],{},[66,7039,7040],{},"Cost per payout",[66,7042,1167],{},[66,7044,7045],{},"Flat fee plus sub-percent FX, quoted upfront",[45,7047,7048,7051,7054],{},[66,7049,7050],{},"Minimum balance",[66,7052,7053],{},"$50 to $100 typical",[66,7055,7056],{},"None needed",[45,7058,7059,7062,7065],{},[66,7060,7061],{},"Payout cycle",[66,7063,7064],{},"Weekly or biweekly",[66,7066,7067],{},"Daily or on demand",[45,7069,7070,7073,7076],{},[66,7071,7072],{},"Landing time",[66,7074,7075],{},"2 to 5 business days",[66,7077,7078],{},"Minutes in Brazil and Mexico, same day elsewhere",[45,7080,7081,7084,7087],{},[66,7082,7083],{},"Amount received",[66,7085,7086],{},"Varies",[66,7088,7089],{},"Matches the quote",[45,7091,7092,7095,7098],{},[66,7093,7094],{},"Pre-funded local balances",[66,7096,7097],{},"Required by many providers",[66,7099,7100],{},"Not required",[11,7102,7103,7106],{},[119,7104,7105],{},"Per-payout cost"," becomes a small flat fee plus a sub-percent spread, itemized in the quote. A $40 payout is fine. Minimums become a product choice, not a necessity.",[11,7108,7109,7112],{},[119,7110,7111],{},"Cycle time"," becomes whatever the platform wants. Daily. On demand. The moment an order clears. Pix and SPEI run 24\u002F7, so a Saturday 2am payout lands Saturday 2am.",[11,7114,7115,7117],{},[119,7116,7072],{}," becomes minutes, at the quoted amount. There are no intermediary deductions because there is no intermediary chain.",[11,7119,7120,7123],{},[119,7121,7122],{},"Failure handling"," moves to before the money leaves. Receiving account verification runs when the seller onboards and again before each payout. Most bad data is rejected while the funds are still the platform's. What does fail comes back by webhook with a reason in the same hour.",[11,7125,7126,7127,7129],{},"Which stablecoin to settle in matters less than most platforms expect. USDC is what most US companies hold; USDT has deeper liquidity in some LATAM off-ramps and can mean a tighter spread on a given corridor. Sellers paid in local currency never see the difference. The ",[136,7128,1071],{"href":1070}," covers when each is the better settlement asset.",[18,7131,7133],{"id":7132},"supported-payment-rails-pix-spei-pse-and-argentine-transfers","Supported payment rails: Pix, SPEI, PSE, and Argentine transfers",[11,7135,7136],{},"The four rails below cover the large majority of LATAM marketplace seller volume. Each has its own settlement behavior and its own verification rule, and a good payout API handles both inside the call.",[39,7138,7139,7154],{},[42,7140,7141],{},[45,7142,7143,7145,7147,7149,7151],{},[48,7144,3393],{},[48,7146,1088],{},[48,7148,1091],{},[48,7150,1094],{},[48,7152,7153],{},"Receiver verification",[61,7155,7156,7169,7183,7197],{},[45,7157,7158,7160,7162,7164,7166],{},[66,7159,3094],{},[66,7161,3414],{},[66,7163,1143],{},[66,7165,1146],{},[66,7167,7168],{},"CPF or CNPJ must match the account holder",[45,7170,7171,7173,7175,7178,7180],{},[66,7172,3107],{},[66,7174,3110],{},[66,7176,7177],{},"Near real time",[66,7179,1146],{},[66,7181,7182],{},"18-digit CLABE validated",[45,7184,7185,7187,7189,7191,7194],{},[66,7186,3120],{},[66,7188,3123],{},[66,7190,1175],{},[66,7192,7193],{},"Bank processing windows",[66,7195,7196],{},"Name and account checked",[45,7198,7199,7201,7203,7205,7208],{},[66,7200,3133],{},[66,7202,3479],{},[66,7204,3139],{},[66,7206,7207],{},"Bank hours, extended",[66,7209,7210],{},"Name must match the CBU, CVU, or alias",[11,7212,7213,7216,7217,7220],{},[119,7214,7215],{},"Pix (Brazil)."," Run by the Banco Central do Brasil, Pix settles in seconds, 24\u002F7, and is used by over 150 million Brazilians. Every serious USDC-to-BRL payout ends in a Pix transfer. Brazil requires the receiving account's CPF or CNPJ to match the seller, and a payout to an account in a spouse's name fails. The ",[136,7218,7219],{"href":5852},"USDC to BRL route guide"," compares paths and fees.",[11,7222,7223,7226,7227,7231],{},[119,7224,7225],{},"SPEI (Mexico)."," Run by Banco de Mexico, SPEI settles in near real time and runs 24\u002F7. Payouts go to an 18-digit CLABE, which the API validates before the payment executes. The ",[136,7228,7230],{"href":7229},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN guide"," covers the corridor.",[11,7233,7234,7237,7238,7242],{},[119,7235,7236],{},"PSE (Colombia)."," PSE is the interbank system Colombian banks use to move money between accounts. Unlike Pix it runs on bank processing windows rather than settling around the clock, so a payout is usually minutes but not guaranteed instant. The ",[136,7239,7241],{"href":7240},"\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026","USDC to COP guide"," explains the windows and why PSE payouts get delayed or rejected.",[11,7244,7245,7248,7249,7253],{},[119,7246,7247],{},"Transfers 3.0 (Argentina)."," Argentine transfers go to a CBU (bank account key) or CVU (virtual account key), often reached through an alias. Institutions verify the beneficiary name against the account holder before crediting, so accurate receiver data is a hard requirement. A minority of Argentine sellers prefer to hold dollars; for them a USDC payout to a wallet is a feature. The ",[136,7250,7252],{"href":7251},"\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026","USDC to ARS guide"," covers both paths.",[11,7255,7256,7257,227],{},"Sellers outside the region are paid through the same API over ACH or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on the wire leg. How leadership teams decide which flows go on which rail is covered in ",[136,7258,7259],{"href":1192},"orchestrating payment rails",[18,7261,7263],{"id":7262},"end-to-end-payout-workflow-from-stablecoin-hold-to-local-currency-delivery","End-to-end payout workflow: from stablecoin hold to local currency delivery",[11,7265,7266],{},"The end-to-end workflow has five steps, and the platform's code touches three of them.",[145,7268,7269,7275,7285,7291,7297],{},[148,7270,7271,7274],{},[119,7272,7273],{},"Buyer pays."," The buyer pays the marketplace as usual, by card, ACH, or bank transfer. Nothing changes on the acceptance side.",[148,7276,7277,7280,7281,7284],{},[119,7278,7279],{},"Platform holds in stablecoins."," While the order is pending (escrow, delivery, dispute window), the platform holds the balance in USD or USDC. A ",[136,7282,7283],{"href":138},"virtual account"," turns incoming USD into stablecoins automatically. Holding in a dollar-linked asset means no FX exposure in four local currencies and no pre-funded balances sitting idle in four countries.",[148,7286,7287,7290],{},[119,7288,7289],{},"Platform triggers the payout."," When the order clears, the platform requests a quote for the seller's amount and currency. The API returns the FX rate, spread, and payout fee as separate numbers. The platform executes against the seller's stored receiver ID.",[148,7292,7293,7296],{},[119,7294,7295],{},"Provider converts and delivers."," The stablecoin converts to local currency and the provider delivers it over Pix, SPEI, PSE, or an Argentine transfer, after verifying the receiving account. Compliance checks (KYC, sanctions screening, travel rule data) run inside this step.",[148,7298,7299,7302],{},[119,7300,7301],{},"Seller receives local currency."," The seller sees a local transfer in their bank account for the quoted amount. The platform receives a webhook with the final status and updates the seller dashboard.",[11,7304,7305],{},"Two properties of this flow deserve attention before committing.",[11,7307,7308,7311,7312,7315],{},[119,7309,7310],{},"Finality."," The on-chain transfer is final once confirmed, which is why receiver verification happens before money moves rather than after. ",[136,7313,7314],{"href":734},"Are stablecoin payments reversible"," explains what can and cannot be recalled on each leg.",[11,7317,7318,7321,7322,7326],{},[119,7319,7320],{},"Cross-chain and payables."," Since August 2026, BlindPay moves USDC across networks in a single transfer and pays invoices, boletos, and Pix codes straight from stablecoins, which matters for platforms that also settle with vendors who invoice rather than sell. The ",[136,7323,7325],{"href":7324},"\u002Fchangelog\u002F2026-08-20-payables-cross-chain-usdc-fx-export","Payables and cross-chain USDC changelog"," has the details.",[967,7328,7330],{"id":7329},"the-pre-funding-trap","The pre-funding trap",[11,7332,7333],{},"Several payout providers quote fast local payouts and then explain that the platform must keep a BRL balance in Brazil and an MXN balance in Mexico, topped up ahead of each cycle. That is pre-funding, and it means working capital sits idle in four countries, exposed to four currencies, waiting for payouts that may or may not happen.",[11,7335,7336,7337,7339],{},"For a marketplace with seasonal volume this is expensive in a way that never shows up as a fee. BlindPay quotes and settles without pre-funding: the platform funds the payout when it makes it, in USD or USDC, and the local currency leg happens at execution. The ",[136,7338,4238],{"href":4237}," covers why trapped capital belongs in any cost comparison.",[18,7341,7343],{"id":7342},"api-integration-for-global-payments-at-scale","API integration for global payments at scale",[11,7345,7346],{},"A marketplace payout integration has three parts, and the same three parts work whether the platform pays 40 sellers or 40,000.",[145,7348,7349,7355,7361],{},[148,7350,7351,7354],{},[119,7352,7353],{},"Seller onboarding."," Create a receiver with name, tax ID (CPF or CNPJ, RFC, cedula, or CUIT), and bank account. KYC and account verification run inline. Store the receiver ID against the seller record.",[148,7356,7357,7360],{},[119,7358,7359],{},"Payout."," Request a quote for the amount and currency, then execute against the receiver ID. Store the payout ID, the quoted rate, and the fee for the seller's payout history.",[148,7362,7363,7366,7367,7370],{},[119,7364,7365],{},"Reconciliation."," Listen for the webhook on every status change. Update the seller's balance and payout history, and surface the status in the seller dashboard. The ",[136,7368,7369],{"href":1284},"webhook integration prompt"," is the fastest path to a working listener.",[11,7372,7373],{},"Three operational details that platforms tend to underestimate:",[11,7375,7376,7379],{},[119,7377,7378],{},"Naming."," The Pix or SPEI should show a sender name the seller recognizes. Money from an unfamiliar name triggers support tickets and, in Brazil, occasionally a fraud report.",[11,7381,7382,7385],{},[119,7383,7384],{},"Predictability over speed."," A seller can plan around \"every Tuesday at 9am, the full amount.\" They cannot plan around \"sometime this week, minus something.\" If the platform moves to daily payouts, keep them boringly consistent.",[11,7387,7388,7391,7392,7395],{},[119,7389,7390],{},"Failure paths in sandbox."," Sandbox does not exercise real bank rejections, compliance holds, or a PSE window closing. ",[136,7393,7394],{"href":754},"Test those paths"," before the first production cycle, because production is where they show up.",[967,7397,7399],{"id":7398},"compliance-responsibilities-split-honestly","Compliance responsibilities, split honestly",[11,7401,7402,7403,7407,7408,1223,7411,7414],{},"The provider holds the licenses and runs KYC on each seller inside the onboarding flow. In Brazil that means operating under the Central Bank's virtual asset framework (Resolutions 519 through 521, in force since February 2026). Brazil's Resolution 561 on eFX in May 2026 made some platforms nervous; it does not affect the stablecoin plus local payout model, as ",[136,7404,7406],{"href":7405},"\u002Fblog\u002Fbcb-resolution-561-efx-stablecoins","BlindPay explained at the time",". The ",[136,7409,7410],{"href":4069},"VASP explainer",[136,7412,7413],{"href":3239},"PSAV guide for Brazil"," cover what the licenses mean.",[11,7416,7417,7418,7420],{},"The platform is responsible for its own ",[136,7419,3301],{"href":3211},", for collecting accurate seller data, and for the tax side: sellers still owe income tax locally and the platform still needs its usual records. Stablecoins change the rail. They do not change who owes what.",[18,7422,7424],{"id":7423},"start-processing-latam-marketplace-payouts-with-blindpay","Start processing LATAM marketplace payouts with BlindPay",[11,7426,7427,7428,1337,7430,7432,7433,7436],{},"BlindPay is a Y Combinator-backed stablecoin payout API built for exactly this flow: dollars or USDC in, Pix, SPEI, PSE, or Argentine transfer out, with the FX rate quoted before the payout executes, receiver verification and compliance run inside the call, and no pre-funding. It runs at $2.5 billion in annualized transfer volume across a payment network in 100+ countries, with published ",[136,7429,1340],{"href":307},[136,7431,1336],{"href":1335},". Where another provider is the better fit, the ",[136,7434,7435],{"href":771},"stablecoin payment providers comparison"," says so.",[11,7438,7439],{},"The fastest way to decide is a parallel run. Pull the last three payout cycles. Count the payouts under the minimum that had to wait, the wires that arrived short, and the support tickets that followed. Then run one cycle for one country through the sandbox, and price the same cycles as daily stablecoin payouts with no minimum. The difference is usually large enough to become a seller-facing feature: \"get paid the day you earn it.\"",[11,7441,7442,1341,7446,7449],{},[136,7443,7445],{"href":648,"rel":7444},[414],"Start in the sandbox",[136,7447,1345],{"href":654,"rel":7448},[414]," with your seller countries and monthly payout volume.",[11,7451,7452],{},[324,7453,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":7455},[7456,7457,7458,7459,7462,7465],{"id":6965,"depth":329,"text":6966},{"id":7007,"depth":329,"text":7008},{"id":7132,"depth":329,"text":7133},{"id":7262,"depth":329,"text":7263,"children":7460},[7461],{"id":7329,"depth":1404,"text":7330},{"id":7342,"depth":329,"text":7343,"children":7463},[7464],{"id":7398,"depth":1404,"text":7399},{"id":7423,"depth":329,"text":7424},"2026-09-06","How marketplaces pay sellers and creators across Latin America with stablecoins: Pix, SPEI, PSE, and Argentine transfers, the payout flow, and FX cost.",[7469,7472,7475,7478,7481,7484,7487],{"q":7470,"a":7471},"What are stablecoin payouts and how do they work for marketplaces in Latin America?","A stablecoin payout is a seller payment settled with a dollar-pegged token like USDC or USDT and delivered as local currency. The marketplace holds dollars or stablecoins, a payout API converts each seller's balance at a quoted rate, and the money lands over the local rail: Pix in Brazil, SPEI in Mexico, PSE in Colombia, or a bank transfer in Argentina. The seller gives a bank account and receives local currency. They never touch a wallet.",{"q":7473,"a":7474},"How do marketplace payouts via stablecoin APIs compare to traditional payment methods like ACH or wire transfers in Latin America?","ACH does not reach Latin America. An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread, takes 2 to 5 business days, and often arrives short after intermediary deductions. A stablecoin payout costs a flat fee plus a sub-percent spread quoted upfront, lands in minutes, and arrives at the quoted amount. The gap is widest on small, frequent payouts, which is exactly what marketplaces send.",{"q":7476,"a":7477},"What payment methods are supported for vendor payouts across Latin America?","Through a stablecoin payout API like BlindPay: Pix in Brazil, SPEI in Mexico, PSE in Colombia, and Transfers 3.0 to a CBU or CVU in Argentina, plus ACH and SWIFT (POBO\u002FCOBO) for sellers outside the region. Sellers who want to hold dollars can be paid in USDC or USDT to a wallet instead.",{"q":7479,"a":7480},"How long do marketplace payouts take using a stablecoin API in LATAM?","Minutes for Brazil and Mexico, because Pix and SPEI settle in near real time and run 24\u002F7. Colombia over PSE is usually minutes but follows bank processing windows. Argentina over Transfers 3.0 is same-day. In every case the stablecoin conversion takes a few minutes and the local rail sets the rest.",{"q":7482,"a":7483},"What does a stablecoin payout API integration look like for an existing marketplace platform?","Three parts. Create a receiver for each seller with name, tax ID, and bank account, and store the receiver ID. When a payout is due, request a quote and execute against that ID. Listen for the webhook to update the seller's balance and payout history. Most teams keep their existing processor for card acceptance and add the payout API beside it.",{"q":7485,"a":7486},"Are stablecoin-based marketplace payouts compliant with Latin American financial regulations?","Yes, when the provider holds the local licenses and runs KYC on each seller. Brazil's Central Bank licenses virtual asset service providers under Resolutions 519 through 521, in force since February 2026, and Resolution 561 on eFX does not affect the stablecoin plus local payout model. The marketplace remains responsible for its own KYB, accurate seller data, and normal tax records.",{"q":7488,"a":7489},"How do stablecoin APIs reduce FX fees on cross-border marketplace payments in Latin America?","A wire routes through correspondent banks that each take a fee, and the receiving bank sets its own FX rate, typically 2 to 5 percent off mid-market. A stablecoin payout has one conversion step at a rate quoted before the payment executes, with the spread and payout fee itemized. No intermediary chain means no hidden deductions, so the seller receives the amount the marketplace was quoted.",{"author":361},"---\ntitle: \"Marketplace payouts in Latin America: stablecoin rails for sellers in Brazil, Mexico, Colombia, and Argentina\"\nseoTitle: \"Marketplace stablecoin payouts in Latin America\"\ndescription: \"How marketplaces pay sellers and creators across Latin America with stablecoins: Pix, SPEI, PSE, and Argentine transfers, the payout flow, and FX cost.\"\ndate: \"2026-09-06\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What are stablecoin payouts and how do they work for marketplaces in Latin America?\"\n    a: \"A stablecoin payout is a seller payment settled with a dollar-pegged token like USDC or USDT and delivered as local currency. The marketplace holds dollars or stablecoins, a payout API converts each seller's balance at a quoted rate, and the money lands over the local rail: Pix in Brazil, SPEI in Mexico, PSE in Colombia, or a bank transfer in Argentina. The seller gives a bank account and receives local currency. They never touch a wallet.\"\n  - q: \"How do marketplace payouts via stablecoin APIs compare to traditional payment methods like ACH or wire transfers in Latin America?\"\n    a: \"ACH does not reach Latin America. An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread, takes 2 to 5 business days, and often arrives short after intermediary deductions. A stablecoin payout costs a flat fee plus a sub-percent spread quoted upfront, lands in minutes, and arrives at the quoted amount. The gap is widest on small, frequent payouts, which is exactly what marketplaces send.\"\n  - q: \"What payment methods are supported for vendor payouts across Latin America?\"\n    a: \"Through a stablecoin payout API like BlindPay: Pix in Brazil, SPEI in Mexico, PSE in Colombia, and Transfers 3.0 to a CBU or CVU in Argentina, plus ACH and SWIFT (POBO\u002FCOBO) for sellers outside the region. Sellers who want to hold dollars can be paid in USDC or USDT to a wallet instead.\"\n  - q: \"How long do marketplace payouts take using a stablecoin API in LATAM?\"\n    a: \"Minutes for Brazil and Mexico, because Pix and SPEI settle in near real time and run 24\u002F7. Colombia over PSE is usually minutes but follows bank processing windows. Argentina over Transfers 3.0 is same-day. In every case the stablecoin conversion takes a few minutes and the local rail sets the rest.\"\n  - q: \"What does a stablecoin payout API integration look like for an existing marketplace platform?\"\n    a: \"Three parts. Create a receiver for each seller with name, tax ID, and bank account, and store the receiver ID. When a payout is due, request a quote and execute against that ID. Listen for the webhook to update the seller's balance and payout history. Most teams keep their existing processor for card acceptance and add the payout API beside it.\"\n  - q: \"Are stablecoin-based marketplace payouts compliant with Latin American financial regulations?\"\n    a: \"Yes, when the provider holds the local licenses and runs KYC on each seller. Brazil's Central Bank licenses virtual asset service providers under Resolutions 519 through 521, in force since February 2026, and Resolution 561 on eFX does not affect the stablecoin plus local payout model. The marketplace remains responsible for its own KYB, accurate seller data, and normal tax records.\"\n  - q: \"How do stablecoin APIs reduce FX fees on cross-border marketplace payments in Latin America?\"\n    a: \"A wire routes through correspondent banks that each take a fee, and the receiving bank sets its own FX rate, typically 2 to 5 percent off mid-market. A stablecoin payout has one conversion step at a rate quoted before the payment executes, with the spread and payout fee itemized. No intermediary chain means no hidden deductions, so the seller receives the amount the marketplace was quoted.\"\n---\n\nMarketplace payouts in Latin America are the payments a platform sends to its sellers, creators, drivers, or vendors in Brazil, Mexico, Colombia, and Argentina. Done over wires, they are slow, expensive, and unpredictable. Done over stablecoin rails, they land in minutes as local currency at a quoted amount, and the economics of a small payout stop being a problem.\n\nThis guide is for three readers: the operations lead at a marketplace with thousands of LATAM sellers, the engineer evaluating a payout API, and the CFO at a US or European company expanding into the region. It covers why the old rails fail, how stablecoin payouts work end to end, which local rails are supported, and what the integration looks like.\n\nLatin America is the most stablecoin-native region for cross-border payments. In Fireblocks' 2025 institutional survey, [71 percent of Latin American institutions](https:\u002F\u002Fwww.fireblocks.com\u002Fblog\u002Fexecution-in-motion-how-latin-america-is-leading-stablecoin-adoption) already used stablecoins for cross-border payments, the highest rate of any region. Marketplaces are a large share of that flow.\n\n## Why traditional payment methods fail LATAM marketplaces\n\nTraditional payment methods fail LATAM marketplaces because they were built for a few large payments, not thousands of small ones. A freelance platform with 4,000 active sellers in Brazil that pays by international wire runs into the same four constraints every cycle.\n\n**Per-payout cost.** A wire costs $25 to $50 to send, so paying a $40 balance is a loss. Hence payout minimums.\n\n**Cycle time.** Batching makes wires cheaper, so payouts run weekly or biweekly. Sellers wait.\n\n**Landing time.** Two to five business days, plus a day of compliance screening at the receiving bank, plus receiving-bank fees the platform cannot predict. A seller below the minimum waits another two weeks; a seller above it gets money the following Wednesday, minus something.\n\n**Failure handling.** Bad account data fails days later with a code, and the money comes back minus fees. Support handles the fallout, and the ticket always reads the same way: \"Where is my money.\"\n\nDomestic US rails do not help. ACH and real-time payments over RTP or FedNow are US-only. Card payouts to LATAM cards exist but carry 1.5 to 2.9 percent fees and multi-day settlement. Local processors solve one country at a time, so a platform in four countries ends up with four contracts, four pre-funded balances, and four reconciliation formats.\n\nStack those together and the seller experience is \"money arrives sometime in the next three weeks, amount varies.\" Sellers pick the platform that pays them fastest and most predictably, and in Latin America that has historically been the local one. For a grounding on the asset itself, the [stablecoins section](\u002Fresources\u002Fmore\u002Fstablecoins) explains what USDC and USDT are and how they hold their peg.\n\n## How stablecoin APIs power real-time payments to vendors\n\nA stablecoin API powers real-time vendor payments by replacing the correspondent bank chain with a single conversion step. The platform funds in USD or USDC, each payout converts to local currency at a quoted rate, and the money lands over the local instant rail. The seller gives a bank account and sees a Pix or SPEI transfer arrive. They never see a wallet, a chain, or a token.\n\nRun the four constraints again with a [stablecoin payout API](\u002Fglobal-payments) underneath.\n\n| Constraint | Wire-based payouts | Stablecoin payouts |\n| --- | --- | --- |\n| Cost per payout | $25 to $50 plus 2 to 5 percent FX | Flat fee plus sub-percent FX, quoted upfront |\n| Minimum balance | $50 to $100 typical | None needed |\n| Payout cycle | Weekly or biweekly | Daily or on demand |\n| Landing time | 2 to 5 business days | Minutes in Brazil and Mexico, same day elsewhere |\n| Amount received | Varies | Matches the quote |\n| Pre-funded local balances | Required by many providers | Not required |\n\n**Per-payout cost** becomes a small flat fee plus a sub-percent spread, itemized in the quote. A $40 payout is fine. Minimums become a product choice, not a necessity.\n\n**Cycle time** becomes whatever the platform wants. Daily. On demand. The moment an order clears. Pix and SPEI run 24\u002F7, so a Saturday 2am payout lands Saturday 2am.\n\n**Landing time** becomes minutes, at the quoted amount. There are no intermediary deductions because there is no intermediary chain.\n\n**Failure handling** moves to before the money leaves. Receiving account verification runs when the seller onboards and again before each payout. Most bad data is rejected while the funds are still the platform's. What does fail comes back by webhook with a reason in the same hour.\n\nWhich stablecoin to settle in matters less than most platforms expect. USDC is what most US companies hold; USDT has deeper liquidity in some LATAM off-ramps and can mean a tighter spread on a given corridor. Sellers paid in local currency never see the difference. The [USDC vs USDT comparison](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) covers when each is the better settlement asset.\n\n## Supported payment rails: Pix, SPEI, PSE, and Argentine transfers\n\nThe four rails below cover the large majority of LATAM marketplace seller volume. Each has its own settlement behavior and its own verification rule, and a good payout API handles both inside the call.\n\n| Country | Rail | Settlement | Hours | Receiver verification |\n| --- | --- | --- | --- | --- |\n| Brazil | Pix | Seconds | 24\u002F7 | CPF or CNPJ must match the account holder |\n| Mexico | SPEI | Near real time | 24\u002F7 | 18-digit CLABE validated |\n| Colombia | PSE | Minutes | Bank processing windows | Name and account checked |\n| Argentina | Transfers 3.0 | Same day | Bank hours, extended | Name must match the CBU, CVU, or alias |\n\n**Pix (Brazil).** Run by the Banco Central do Brasil, Pix settles in seconds, 24\u002F7, and is used by over 150 million Brazilians. Every serious USDC-to-BRL payout ends in a Pix transfer. Brazil requires the receiving account's CPF or CNPJ to match the seller, and a payout to an account in a spouse's name fails. The [USDC to BRL route guide](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026) compares paths and fees.\n\n**SPEI (Mexico).** Run by Banco de Mexico, SPEI settles in near real time and runs 24\u002F7. Payouts go to an 18-digit CLABE, which the API validates before the payment executes. The [USDC to MXN guide](\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026) covers the corridor.\n\n**PSE (Colombia).** PSE is the interbank system Colombian banks use to move money between accounts. Unlike Pix it runs on bank processing windows rather than settling around the clock, so a payout is usually minutes but not guaranteed instant. The [USDC to COP guide](\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026) explains the windows and why PSE payouts get delayed or rejected.\n\n**Transfers 3.0 (Argentina).** Argentine transfers go to a CBU (bank account key) or CVU (virtual account key), often reached through an alias. Institutions verify the beneficiary name against the account holder before crediting, so accurate receiver data is a hard requirement. A minority of Argentine sellers prefer to hold dollars; for them a USDC payout to a wallet is a feature. The [USDC to ARS guide](\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026) covers both paths.\n\nSellers outside the region are paid through the same API over ACH or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on the wire leg. How leadership teams decide which flows go on which rail is covered in [orchestrating payment rails](\u002Fblog\u002Forchestrating-payment-rails-leaders).\n\n## End-to-end payout workflow: from stablecoin hold to local currency delivery\n\nThe end-to-end workflow has five steps, and the platform's code touches three of them.\n\n1. **Buyer pays.** The buyer pays the marketplace as usual, by card, ACH, or bank transfer. Nothing changes on the acceptance side.\n2. **Platform holds in stablecoins.** While the order is pending (escrow, delivery, dispute window), the platform holds the balance in USD or USDC. A [virtual account](\u002Fvirtual-accounts) turns incoming USD into stablecoins automatically. Holding in a dollar-linked asset means no FX exposure in four local currencies and no pre-funded balances sitting idle in four countries.\n3. **Platform triggers the payout.** When the order clears, the platform requests a quote for the seller's amount and currency. The API returns the FX rate, spread, and payout fee as separate numbers. The platform executes against the seller's stored receiver ID.\n4. **Provider converts and delivers.** The stablecoin converts to local currency and the provider delivers it over Pix, SPEI, PSE, or an Argentine transfer, after verifying the receiving account. Compliance checks (KYC, sanctions screening, travel rule data) run inside this step.\n5. **Seller receives local currency.** The seller sees a local transfer in their bank account for the quoted amount. The platform receives a webhook with the final status and updates the seller dashboard.\n\nTwo properties of this flow deserve attention before committing.\n\n**Finality.** The on-chain transfer is final once confirmed, which is why receiver verification happens before money moves rather than after. [Are stablecoin payments reversible](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) explains what can and cannot be recalled on each leg.\n\n**Cross-chain and payables.** Since August 2026, BlindPay moves USDC across networks in a single transfer and pays invoices, boletos, and Pix codes straight from stablecoins, which matters for platforms that also settle with vendors who invoice rather than sell. The [Payables and cross-chain USDC changelog](\u002Fchangelog\u002F2026-08-20-payables-cross-chain-usdc-fx-export) has the details.\n\n### The pre-funding trap\n\nSeveral payout providers quote fast local payouts and then explain that the platform must keep a BRL balance in Brazil and an MXN balance in Mexico, topped up ahead of each cycle. That is pre-funding, and it means working capital sits idle in four countries, exposed to four currencies, waiting for payouts that may or may not happen.\n\nFor a marketplace with seasonal volume this is expensive in a way that never shows up as a fee. BlindPay quotes and settles without pre-funding: the platform funds the payout when it makes it, in USD or USDC, and the local currency leg happens at execution. The [pricing explainer](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) covers why trapped capital belongs in any cost comparison.\n\n## API integration for global payments at scale\n\nA marketplace payout integration has three parts, and the same three parts work whether the platform pays 40 sellers or 40,000.\n\n1. **Seller onboarding.** Create a receiver with name, tax ID (CPF or CNPJ, RFC, cedula, or CUIT), and bank account. KYC and account verification run inline. Store the receiver ID against the seller record.\n2. **Payout.** Request a quote for the amount and currency, then execute against the receiver ID. Store the payout ID, the quoted rate, and the fee for the seller's payout history.\n3. **Reconciliation.** Listen for the webhook on every status change. Update the seller's balance and payout history, and surface the status in the seller dashboard. The [webhook integration prompt](\u002Fprompts\u002Fintegrate-webhooks) is the fastest path to a working listener.\n\nThree operational details that platforms tend to underestimate:\n\n**Naming.** The Pix or SPEI should show a sender name the seller recognizes. Money from an unfamiliar name triggers support tickets and, in Brazil, occasionally a fraud report.\n\n**Predictability over speed.** A seller can plan around \"every Tuesday at 9am, the full amount.\" They cannot plan around \"sometime this week, minus something.\" If the platform moves to daily payouts, keep them boringly consistent.\n\n**Failure paths in sandbox.** Sandbox does not exercise real bank rejections, compliance holds, or a PSE window closing. [Test those paths](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) before the first production cycle, because production is where they show up.\n\n### Compliance responsibilities, split honestly\n\nThe provider holds the licenses and runs KYC on each seller inside the onboarding flow. In Brazil that means operating under the Central Bank's virtual asset framework (Resolutions 519 through 521, in force since February 2026). Brazil's Resolution 561 on eFX in May 2026 made some platforms nervous; it does not affect the stablecoin plus local payout model, as [BlindPay explained at the time](\u002Fblog\u002Fbcb-resolution-561-efx-stablecoins). The [VASP explainer](\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp) and the [PSAV guide for Brazil](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained) cover what the licenses mean.\n\nThe platform is responsible for its own [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb), for collecting accurate seller data, and for the tax side: sellers still owe income tax locally and the platform still needs its usual records. Stablecoins change the rail. They do not change who owes what.\n\n## Start processing LATAM marketplace payouts with BlindPay\n\nBlindPay is a Y Combinator-backed stablecoin payout API built for exactly this flow: dollars or USDC in, Pix, SPEI, PSE, or Argentine transfer out, with the FX rate quoted before the payout executes, receiver verification and compliance run inside the call, and no pre-funding. It runs at $2.5 billion in annualized transfer volume across a payment network in 100+ countries, with published [pricing](\u002Fpricing) and [coverage](\u002Fcoverage). Where another provider is the better fit, the [stablecoin payment providers comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026) says so.\n\nThe fastest way to decide is a parallel run. Pull the last three payout cycles. Count the payouts under the minimum that had to wait, the wires that arrived short, and the support tickets that followed. Then run one cycle for one country through the sandbox, and price the same cycles as daily stablecoin payouts with no minimum. The difference is usually large enough to become a seller-facing feature: \"get paid the day you earn it.\"\n\n[Start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction), or [contact BlindPay](https:\u002F\u002Fblindpay.com\u002Fcontact) with your seller countries and monthly payout volume.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":6945,"description":7467},"Marketplace stablecoin payouts in Latin America","resources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","jdBtdZF-OW7WUjE_9VSjaT_eshfaHYQkj5zGZoWB1Ko",{"id":7497,"title":7498,"authors":6,"body":7499,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":7769,"description":7770,"extension":342,"faq":7771,"howto":6,"isBlog":359,"isChangelog":359,"meta":7784,"navigation":362,"path":4440,"pillar":359,"products":6,"rawbody":7785,"role":6,"seo":7786,"seoTitle":7787,"stem":7788,"thumbnail":6,"updated":7769,"__hash__":7789},"content\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes.md","On\u002Foff ramp liquidity with live quotes: how it works and why it matters",{"type":8,"value":7500,"toc":7761},[7501,7506,7509,7513,7594,7597,7601,7604,7624,7634,7638,7644,7650,7656,7660,7663,7666,7669,7672,7676,7679,7699,7702,7705,7709,7750,7757],[11,7502,7503],{},[324,7504,7505],{},"Reading time: about 6 minutes.",[11,7507,7508],{},"On\u002Foff ramp liquidity with live quotes means a provider holds enough fiat and stablecoin inventory to fill conversions on demand, and prices each one at the moment it is requested rather than from a cached rate. For a developer, the implication is that the rate returned by the quote endpoint is the rate that settles, as long as the transaction is confirmed inside the quote's window.",[18,7510,7512],{"id":7511},"what-is-the-difference-between-a-live-quote-and-a-batch-rate","What is the difference between a live quote and a batch rate?",[39,7514,7515,7527],{},[42,7516,7517],{},[45,7518,7519,7521,7524],{},[48,7520],{},[48,7522,7523],{},"Live quote",[48,7525,7526],{},"Batch rate",[61,7528,7529,7540,7551,7562,7573,7583],{},[45,7530,7531,7534,7537],{},[66,7532,7533],{},"When rate is determined",[66,7535,7536],{},"At the moment of the API request",[66,7538,7539],{},"On a schedule (every minute, hour, or day) and cached",[45,7541,7542,7545,7548],{},[66,7543,7544],{},"Rate window",[66,7546,7547],{},"Stated expiry, typically 10 seconds to 5 minutes, honored on confirmation",[66,7549,7550],{},"No commitment; settlement happens at the rate in effect later",[45,7552,7553,7556,7559],{},[66,7554,7555],{},"User experience",[66,7557,7558],{},"The amount on the confirmation screen is the amount that settles",[66,7560,7561],{},"The user sees an estimate and learns the real amount afterward",[45,7563,7564,7567,7570],{},[66,7565,7566],{},"Slippage risk",[66,7568,7569],{},"Carried by the provider inside the window",[66,7571,7572],{},"Carried by the user, or hidden inside a wider spread",[45,7574,7575,7577,7580],{},[66,7576,785],{},[66,7578,7579],{},"Consumer flows, payroll, any product that shows an amount before sending",[66,7581,7582],{},"Internal treasury moves where the sender tolerates variance",[45,7584,7585,7588,7591],{},[66,7586,7587],{},"Worst for",[66,7589,7590],{},"Nothing at the application layer; the cost is on the provider's side",[66,7592,7593],{},"Any flow where a person confirms a number they expect to receive",[11,7595,7596],{},"A batch rate is not a cheaper version of a live quote. It is a different allocation of risk, and the risk lands on the user.",[18,7598,7600],{"id":7599},"how-does-a-live-quote-actually-work-in-an-api","How does a live quote actually work in an API?",[11,7602,7603],{},"The flow has six steps, and the quote ID is what ties them together.",[145,7605,7606,7609,7612,7615,7618,7621],{},[148,7607,7608],{},"The application calls the quote endpoint with the corridor, the amount, and which side (sender or receiver) the amount is fixed on.",[148,7610,7611],{},"The provider returns the rate, the itemized fees, the resulting amount, a quote ID, and an expiry timestamp in a single synchronous response.",[148,7613,7614],{},"The application displays the amount and a countdown to the user.",[148,7616,7617],{},"The user confirms.",[148,7619,7620],{},"The application submits the transaction with the quote ID attached.",[148,7622,7623],{},"The provider checks that the quote has not expired, honors the quoted rate, and executes the conversion.",[11,7625,7626,7627,7629,7630,7633],{},"Providers that own their liquidity implement this directly. BlindPay, for example, returns ",[204,7628,3865],{}," with every quote and holds bank payout quotes for a default five minute window, rejecting late submissions with a ",[204,7631,7632],{},"quote_expired"," error so the client can re-quote.",[18,7635,7637],{"id":7636},"what-happens-when-a-live-quote-expires","What happens when a live quote expires?",[11,7639,7640,7643],{},[119,7641,7642],{},"The user confirms in time."," The transaction is submitted with a valid quote ID, the provider executes at the quoted rate, and the user receives the amount shown on screen. This is the only scenario in which the provider carries any rate risk.",[11,7645,7646,7649],{},[119,7647,7648],{},"The user does not confirm."," The quote lapses, nothing is executed, and no funds move. The application requests a new quote when the user returns, and the new amount may differ.",[11,7651,7652,7655],{},[119,7653,7654],{},"The quote expires during processing."," The application submitted the quote ID inside the window, so the provider honors it even if on-chain confirmation or fiat settlement finishes after the expiry timestamp. If the application submits after the window has closed, the provider rejects the transaction with an expiry error, and the correct client behavior is to re-quote and ask the user to confirm again rather than to retry blindly.",[18,7657,7659],{"id":7658},"how-does-liquidity-depth-affect-quote-quality","How does liquidity depth affect quote quality?",[11,7661,7662],{},"Liquidity depth is the volume a provider can convert on a corridor before the rate degrades. A deep book fills a large order at nearly the same price as a small one; a thin book has to reach for worse prices as the order grows.",[11,7664,7665],{},"Take a USDC to BRL corridor. A $500 quote and a $50,000 quote from a deep provider might differ by a few basis points, because both fill from the same inventory at the same price. The same two quotes from a thin provider might differ by 50 to 150 basis points, because the larger order exhausts the good inventory and fills the remainder at worse prices or is routed to a third party with its own markup.",[11,7667,7668],{},"Depth also sets reliability. A provider that has to source liquidity from a partner at quote time cannot guarantee the rate, so it either widens the spread to protect itself or quotes indicatively and settles at market.",[11,7670,7671],{},"To test depth during evaluation, request quotes at $500, $5,000, and $50,000 on the same corridor within one minute and compare the effective rate after fees. Then ask for the maximum single-transaction size per corridor and whether that limit is stated in writing. A provider whose spread is flat across the three sizes has the depth it claims.",[18,7673,7675],{"id":7674},"what-is-a-typical-rate-window-and-how-should-it-affect-your-ux-design","What is a typical rate window and how should it affect your UX design?",[11,7677,7678],{},"Most live quote windows fall between 10 and 90 seconds for crypto-native flows, with some providers holding bank payout quotes for several minutes. The window length dictates which confirmation pattern your interface can support.",[171,7680,7681,7687,7693],{},[148,7682,7683,7686],{},[119,7684,7685],{},"About 15 seconds:"," single-screen confirmation only. The amount and a confirm button must be on the same screen with a visible countdown, and the quote should be requested when that screen loads, not earlier.",[148,7688,7689,7692],{},[119,7690,7691],{},"About 60 seconds:"," multi-step confirmation is possible. The user can review a summary, pick a bank account, and confirm, provided the app re-quotes automatically if the timer runs out.",[148,7694,7695,7698],{},[119,7696,7697],{},"90 seconds and up:"," batch approval flows work. A finance user can review a list of payouts, each with its quoted amount, and approve them together before any quote lapses.",[11,7700,7701],{},"A window under 10 seconds is a bad consumer experience. Network latency, screen rendering, and the user reading the number consume most of it, so a meaningful share of confirmations arrive expired and the user sees a changed amount on every retry. If a provider's window is that short, either the corridor is illiquid or the provider is passing its own risk to your users.",[11,7703,7704],{},"Design for expiry as a normal path, not an error. Show the countdown, re-quote silently when it hits zero, and highlight the change only if the amount moved.",[18,7706,7708],{"id":7707},"what-should-a-developer-look-for-in-a-live-quote-api","What should a developer look for in a live quote API?",[171,7710,7711,7717,7723,7729,7735,7741],{},[148,7712,7713,7716],{},[119,7714,7715],{},"Synchronous response under one second."," The quote is on the critical path of the confirmation screen, so a slow endpoint eats into the rate window before the user sees a number.",[148,7718,7719,7722],{},[119,7720,7721],{},"Quote ID enforcement on the transaction endpoint."," The execute call must require the quote ID and reject unknown or expired ones, otherwise the \"honored rate\" is a promise with no mechanism behind it.",[148,7724,7725,7728],{},[119,7726,7727],{},"Explicit expiry timestamp and a distinct expiry error code."," The client needs the timestamp to render a countdown and the error code to distinguish \"re-quote\" from \"something else failed\".",[148,7730,7731,7734],{},[119,7732,7733],{},"Itemized fees in the quote."," Rate, spread, flat fee, and network fee as separate fields, so the amount displayed matches the amount settled and reconciliation works without guesswork.",[148,7736,7737,7740],{},[119,7738,7739],{},"Webhook settlement events."," Execution is asynchronous after confirmation, so the API must emit signed events for on-chain confirmation and fiat settlement rather than requiring polling.",[148,7742,7743,7746,7747,7749],{},[119,7744,7745],{},"Sandbox parity with production."," Expiry, rejection, and error codes must behave the same in sandbox, or the integration ships with untested failure paths. ",[136,7748,4101],{"href":754}," covers what sandboxes can and cannot exercise.",[11,7751,7752,7753,7756],{},"A provider that meets all six has built a live quote system. A provider that meets fewer has built a rate display. The ",[136,7754,7755],{"href":3318},"buyer's guide to on\u002Foff ramp providers"," shows how to weigh this against corridor coverage, settlement speed, and licensing.",[11,7758,7759],{},[324,7760,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":7762},[7763,7764,7765,7766,7767,7768],{"id":7511,"depth":329,"text":7512},{"id":7599,"depth":329,"text":7600},{"id":7636,"depth":329,"text":7637},{"id":7658,"depth":329,"text":7659},{"id":7674,"depth":329,"text":7675},{"id":7707,"depth":329,"text":7708},"2026-09-03","What live-quote liquidity means for developers: live quote vs batch rate, the quote ID flow, expiry handling, and how depth changes spread by size.",[7772,7775,7778,7781],{"q":7773,"a":7774},"What is quote slippage in crypto on-ramps?","Quote slippage is the difference between the rate shown to the user and the rate at which the conversion actually settles. It appears when a provider quotes a cached or indicative rate and executes later at the market rate. A live quote with a quote ID and an honored window removes slippage from the user's side: the provider absorbs any move within the window, and after expiry the user gets a fresh quote instead of a surprise.",{"q":7776,"a":7777},"How do I test live quotes during API integration?","Request two quotes ten seconds apart on a volatile corridor and confirm the rate moves. Confirm each response carries a quote ID and an expiry timestamp. Submit a transaction with an expired ID and confirm a specific expiry error code. Request quotes at $500, $5,000, and $50,000 on the same corridor and compare the effective rate. Finally, confirm the sandbox enforces the same rules as production.",{"q":7779,"a":7780},"Can I lock a live quote for longer than the standard window?","Sometimes, at a price. Some providers offer extended locks for scheduled or large payments, and the spread widens to cover the provider's exposure over the longer period. For most flows the better design is to request the quote at the last responsible moment, right before the user confirms, and to re-quote automatically when the window expires rather than pay for a lock you rarely need.",{"q":7782,"a":7783},"Why do some on-ramp providers not offer live quotes?","Because they do not hold the liquidity themselves. A provider that routes conversions to a third-party exchange or market maker cannot commit to a rate it does not control, so it quotes an indicative rate and settles at whatever the partner returns. Live quotes with an honored window require the provider to own or directly access the liquidity that fills the trade.",{"author":361},"---\ntitle: \"On\u002Foff ramp liquidity with live quotes: how it works and why it matters\"\nseoTitle: \"On\u002Foff ramp liquidity with live quotes\"\ndescription: \"What live-quote liquidity means for developers: live quote vs batch rate, the quote ID flow, expiry handling, and how depth changes spread by size.\"\ndate: \"2026-09-03\"\nupdated: \"2026-09-03\"\nauthor: \"BlindPay Team\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is quote slippage in crypto on-ramps?\"\n    a: \"Quote slippage is the difference between the rate shown to the user and the rate at which the conversion actually settles. It appears when a provider quotes a cached or indicative rate and executes later at the market rate. A live quote with a quote ID and an honored window removes slippage from the user's side: the provider absorbs any move within the window, and after expiry the user gets a fresh quote instead of a surprise.\"\n  - q: \"How do I test live quotes during API integration?\"\n    a: \"Request two quotes ten seconds apart on a volatile corridor and confirm the rate moves. Confirm each response carries a quote ID and an expiry timestamp. Submit a transaction with an expired ID and confirm a specific expiry error code. Request quotes at $500, $5,000, and $50,000 on the same corridor and compare the effective rate. Finally, confirm the sandbox enforces the same rules as production.\"\n  - q: \"Can I lock a live quote for longer than the standard window?\"\n    a: \"Sometimes, at a price. Some providers offer extended locks for scheduled or large payments, and the spread widens to cover the provider's exposure over the longer period. For most flows the better design is to request the quote at the last responsible moment, right before the user confirms, and to re-quote automatically when the window expires rather than pay for a lock you rarely need.\"\n  - q: \"Why do some on-ramp providers not offer live quotes?\"\n    a: \"Because they do not hold the liquidity themselves. A provider that routes conversions to a third-party exchange or market maker cannot commit to a rate it does not control, so it quotes an indicative rate and settles at whatever the partner returns. Live quotes with an honored window require the provider to own or directly access the liquidity that fills the trade.\"\n---\n\n*Reading time: about 6 minutes.*\n\nOn\u002Foff ramp liquidity with live quotes means a provider holds enough fiat and stablecoin inventory to fill conversions on demand, and prices each one at the moment it is requested rather than from a cached rate. For a developer, the implication is that the rate returned by the quote endpoint is the rate that settles, as long as the transaction is confirmed inside the quote's window.\n\n## What is the difference between a live quote and a batch rate?\n\n| | Live quote | Batch rate |\n| --- | --- | --- |\n| When rate is determined | At the moment of the API request | On a schedule (every minute, hour, or day) and cached |\n| Rate window | Stated expiry, typically 10 seconds to 5 minutes, honored on confirmation | No commitment; settlement happens at the rate in effect later |\n| User experience | The amount on the confirmation screen is the amount that settles | The user sees an estimate and learns the real amount afterward |\n| Slippage risk | Carried by the provider inside the window | Carried by the user, or hidden inside a wider spread |\n| Best for | Consumer flows, payroll, any product that shows an amount before sending | Internal treasury moves where the sender tolerates variance |\n| Worst for | Nothing at the application layer; the cost is on the provider's side | Any flow where a person confirms a number they expect to receive |\n\nA batch rate is not a cheaper version of a live quote. It is a different allocation of risk, and the risk lands on the user.\n\n## How does a live quote actually work in an API?\n\nThe flow has six steps, and the quote ID is what ties them together.\n\n1. The application calls the quote endpoint with the corridor, the amount, and which side (sender or receiver) the amount is fixed on.\n2. The provider returns the rate, the itemized fees, the resulting amount, a quote ID, and an expiry timestamp in a single synchronous response.\n3. The application displays the amount and a countdown to the user.\n4. The user confirms.\n5. The application submits the transaction with the quote ID attached.\n6. The provider checks that the quote has not expired, honors the quoted rate, and executes the conversion.\n\nProviders that own their liquidity implement this directly. BlindPay, for example, returns `expires_at` with every quote and holds bank payout quotes for a default five minute window, rejecting late submissions with a `quote_expired` error so the client can re-quote.\n\n## What happens when a live quote expires?\n\n**The user confirms in time.** The transaction is submitted with a valid quote ID, the provider executes at the quoted rate, and the user receives the amount shown on screen. This is the only scenario in which the provider carries any rate risk.\n\n**The user does not confirm.** The quote lapses, nothing is executed, and no funds move. The application requests a new quote when the user returns, and the new amount may differ.\n\n**The quote expires during processing.** The application submitted the quote ID inside the window, so the provider honors it even if on-chain confirmation or fiat settlement finishes after the expiry timestamp. If the application submits after the window has closed, the provider rejects the transaction with an expiry error, and the correct client behavior is to re-quote and ask the user to confirm again rather than to retry blindly.\n\n## How does liquidity depth affect quote quality?\n\nLiquidity depth is the volume a provider can convert on a corridor before the rate degrades. A deep book fills a large order at nearly the same price as a small one; a thin book has to reach for worse prices as the order grows.\n\nTake a USDC to BRL corridor. A $500 quote and a $50,000 quote from a deep provider might differ by a few basis points, because both fill from the same inventory at the same price. The same two quotes from a thin provider might differ by 50 to 150 basis points, because the larger order exhausts the good inventory and fills the remainder at worse prices or is routed to a third party with its own markup.\n\nDepth also sets reliability. A provider that has to source liquidity from a partner at quote time cannot guarantee the rate, so it either widens the spread to protect itself or quotes indicatively and settles at market.\n\nTo test depth during evaluation, request quotes at $500, $5,000, and $50,000 on the same corridor within one minute and compare the effective rate after fees. Then ask for the maximum single-transaction size per corridor and whether that limit is stated in writing. A provider whose spread is flat across the three sizes has the depth it claims.\n\n## What is a typical rate window and how should it affect your UX design?\n\nMost live quote windows fall between 10 and 90 seconds for crypto-native flows, with some providers holding bank payout quotes for several minutes. The window length dictates which confirmation pattern your interface can support.\n\n- **About 15 seconds:** single-screen confirmation only. The amount and a confirm button must be on the same screen with a visible countdown, and the quote should be requested when that screen loads, not earlier.\n- **About 60 seconds:** multi-step confirmation is possible. The user can review a summary, pick a bank account, and confirm, provided the app re-quotes automatically if the timer runs out.\n- **90 seconds and up:** batch approval flows work. A finance user can review a list of payouts, each with its quoted amount, and approve them together before any quote lapses.\n\nA window under 10 seconds is a bad consumer experience. Network latency, screen rendering, and the user reading the number consume most of it, so a meaningful share of confirmations arrive expired and the user sees a changed amount on every retry. If a provider's window is that short, either the corridor is illiquid or the provider is passing its own risk to your users.\n\nDesign for expiry as a normal path, not an error. Show the countdown, re-quote silently when it hits zero, and highlight the change only if the amount moved.\n\n## What should a developer look for in a live quote API?\n\n- **Synchronous response under one second.** The quote is on the critical path of the confirmation screen, so a slow endpoint eats into the rate window before the user sees a number.\n- **Quote ID enforcement on the transaction endpoint.** The execute call must require the quote ID and reject unknown or expired ones, otherwise the \"honored rate\" is a promise with no mechanism behind it.\n- **Explicit expiry timestamp and a distinct expiry error code.** The client needs the timestamp to render a countdown and the error code to distinguish \"re-quote\" from \"something else failed\".\n- **Itemized fees in the quote.** Rate, spread, flat fee, and network fee as separate fields, so the amount displayed matches the amount settled and reconciliation works without guesswork.\n- **Webhook settlement events.** Execution is asynchronous after confirmation, so the API must emit signed events for on-chain confirmation and fiat settlement rather than requiring polling.\n- **Sandbox parity with production.** Expiry, rejection, and error codes must behave the same in sandbox, or the integration ships with untested failure paths. [Sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) covers what sandboxes can and cannot exercise.\n\nA provider that meets all six has built a live quote system. A provider that meets fewer has built a rate display. The [buyer's guide to on\u002Foff ramp providers](\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider) shows how to weigh this against corridor coverage, settlement speed, and licensing.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":7498,"description":7770},"On\u002Foff ramp liquidity with live quotes","resources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","1v_gtGoQv63J-Ji3iiN3wkJI1njVT2cad1b-9su2tJ4",{"id":7791,"title":7792,"authors":6,"body":7793,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":4620,"description":8060,"extension":342,"faq":8061,"howto":6,"isBlog":359,"isChangelog":359,"meta":8074,"navigation":362,"path":4487,"pillar":359,"products":6,"rawbody":8075,"role":6,"seo":8076,"seoTitle":8077,"stem":8078,"thumbnail":6,"updated":6,"__hash__":8079},"content\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway.md","Payment orchestration vs payment gateway: what's the difference?",{"type":8,"value":7794,"toc":8051},[7795,7798,7801,7805,7897,7901,7904,7907,7910,7914,7917,7923,7929,7935,7941,7947,7950,7954,7957,7963,7969,7978,7988,7992,7995,7998,8001,8005,8019,8026,8033,8035,8038,8047],[11,7796,7797],{},"A payment gateway connects you to one processor and passes transactions through it on a fixed path. A payment orchestration platform connects to many providers and rails and actively decides, per transaction, which path to take based on cost, speed, corridor rules, and whether the provider is healthy right now.",[11,7799,7800],{},"The difference is the decision. Everything else follows from it.",[18,7802,7804],{"id":7803},"the-comparison-table","The comparison table",[39,7806,7807,7819],{},[42,7808,7809],{},[45,7810,7811,7813,7816],{},[48,7812],{},[48,7814,7815],{},"Payment gateway",[48,7817,7818],{},"Payment orchestration",[61,7820,7821,7832,7843,7854,7865,7876,7886],{},[45,7822,7823,7826,7829],{},[66,7824,7825],{},"What it connects to",[66,7827,7828],{},"One processor or acquirer",[66,7830,7831],{},"Many providers, banks, and rails",[45,7833,7834,7837,7840],{},[66,7835,7836],{},"Routing decisions",[66,7838,7839],{},"None, the path is fixed at integration time",[66,7841,7842],{},"Per transaction, on cost, speed, corridor, and provider health",[45,7844,7845,7848,7851],{},[66,7846,7847],{},"FX handling",[66,7849,7850],{},"The processor's rate, usually blended into one number",[66,7852,7853],{},"Quoted per transaction, spread and fee itemized separately",[45,7855,7856,7859,7862],{},[66,7857,7858],{},"Compliance scope",[66,7860,7861],{},"The processor's program, opaque to you",[66,7863,7864],{},"Screening runs in the routing path, rules vary per corridor",[45,7866,7867,7870,7873],{},[66,7868,7869],{},"Failover behavior",[66,7871,7872],{},"Manual. A rail outage is your outage",[66,7874,7875],{},"Automatic to a secondary rail or provider",[45,7877,7878,7880,7883],{},[66,7879,2046],{},[66,7881,7882],{},"One settlement file, one format",[66,7884,7885],{},"Normalized across every provider into one model",[45,7887,7888,7891,7894],{},[66,7889,7890],{},"Adding a country",[66,7892,7893],{},"A new integration and a new error vocabulary",[66,7895,7896],{},"A routing rule",[18,7898,7900],{"id":7899},"when-do-you-only-need-a-gateway","When do you only need a gateway?",[11,7902,7903],{},"Plenty of businesses never need orchestration, and vendors who pretend otherwise are wasting your engineering time.",[11,7905,7906],{},"Stay on a gateway when you sell in one country, settle in one currency, use one rail, and can tolerate the rail being down for a few hours. A Brazilian SaaS charging Brazilian customers in reais over Pix does not need a routing engine. It needs one good Pix integration.",[11,7908,7909],{},"The economics agree. A second integration costs weeks of engineering plus ongoing maintenance for every error code, webhook, and reconciliation format it brings with it. If the second rail is not earning that back in coverage, cost, or uptime, do not add it.",[18,7911,7913],{"id":7912},"when-do-you-need-orchestration","When do you need orchestration?",[11,7915,7916],{},"Concrete triggers, in the order teams usually hit them.",[11,7918,7919,7922],{},[119,7920,7921],{},"You operate in two or more countries."," The moment your provider's coverage map stops at a border, you are either turning away business or integrating a second provider. The second integration is where the normalization cost shows up.",[11,7924,7925,7928],{},[119,7926,7927],{},"You need fallback when a rail fails."," Every rail fails. Pix has had outages. SPEI has had outages. Correspondent banks hold wires without telling anyone. If a rail going down means payouts stop, you have concentration risk, not a payment system.",[11,7930,7931,7934],{},[119,7932,7933],{},"You settle in local currencies."," Multi-currency turns FX from a footnote into a line item. Once you are converting at volume, a half-point of spread across corridors is real money, and you need per-transaction visibility to find it.",[11,7936,7937,7940],{},[119,7938,7939],{},"You cannot answer \"what did that payout cost\"."," If the true all-in cost of a payment, including spread, is not available per transaction, your unit economics are a guess.",[11,7942,7943,7946],{},[119,7944,7945],{},"Your compliance requirements differ by corridor."," A payout into Brazil sits under Central Bank Resolutions 519 through 521. One into the EU sits under MiCA. A gateway built for one market does not model that.",[11,7948,7949],{},"Any one trigger justifies the look. Two or more and you are already paying the cost of orchestration, just in engineering hours instead of vendor fees.",[18,7951,7953],{"id":7952},"worked-example-25000-from-the-us-to-brazil","Worked example: $25,000 from the US to Brazil",[11,7955,7956],{},"Same payment, three paths. Numbers are typical ranges for a corporate payer, not a quote.",[11,7958,7959,7962],{},[119,7960,7961],{},"SWIFT wire."," Sending bank charges $25 to $50. One or two correspondent banks deduct $10 to $30 each, and nobody tells you in advance. The receiving bank in Brazil applies its own FX rate, commonly 2 to 5 percent off mid-market for a corporate receiver, and charges a landing fee. Total cost lands somewhere around $650 to $1,350. Delivery is 1 to 5 business days, longer if screening flags it. Send on Friday afternoon and the supplier has money Tuesday or Wednesday.",[11,7964,7965,7968],{},[119,7966,7967],{},"Local Pix payout, pre-funded."," You keep a BRL balance in a Brazilian account and pay out of it. Delivery is seconds, 24\u002F7, and the payout fee is small. The cost that does not appear on the invoice is the working capital parked in that account, plus whatever you paid in spread to get it there, plus the FX risk of holding reais.",[11,7970,7971,7974,7975,227],{},[119,7972,7973],{},"Stablecoin bridge into Pix."," Dollars convert to USDC, USDC moves on-chain in seconds, converts to reais at a rate you saw before committing, and delivers over Pix. All-in cost is typically a sub-percent spread plus a small flat fee, so roughly $150 to $250 on $25,000. Delivery is minutes, any hour, any day. No local balance to pre-fund, which is the ",[136,7976,7977],{"href":289},"working-capital argument for stablecoin settlement",[11,7979,7980,7981,7984,7985,7987],{},"The point is not that one path always wins. It is that a gateway picks for you at integration time and an orchestration layer picks per transaction. If that same supplier demands an MT103 next quarter, the orchestration path sends a wire through the same API and returns the document. The ",[136,7982,7983],{"href":1210},"full stablecoin vs SWIFT breakdown"," has the corridor-level numbers, and the ",[136,7986,7219],{"href":5852}," has timings per path.",[18,7989,7991],{"id":7990},"what-does-orchestration-cost-you-in-complexity","What does orchestration cost you in complexity?",[11,7993,7994],{},"The honest tradeoff, since nobody selling orchestration leads with it.",[11,7996,7997],{},"You gain a vendor between your app and your money. You gain routing configuration that can be wrong, which means a bad rule can send payments down an expensive path silently. You gain a dependency whose coverage map now bounds yours.",[11,7999,8000],{},"You mitigate all three the same way: pick a platform that shows you the chosen path and the itemized cost on every transaction, and that lets you pin a corridor to a specific rail when you want to override the router. If a vendor cannot tell you why it routed a payment the way it did, that is not orchestration, that is a black box with a nicer API.",[18,8002,8004],{"id":8003},"where-blindpay-sits","Where BlindPay sits",[11,8006,8007,8009,8010,8013,8014,8018],{},[136,8008,300],{"href":299}," is a cross-border orchestration layer built on stablecoin settlement. One API covers payouts over Pix, SPEI, SEPA, ACH, and SWIFT (POBO\u002FCOBO) across a 100+ country network, collections through ",[136,8011,8012],{"href":138},"virtual US accounts"," that settle as stablecoins, ",[136,8015,8017],{"href":8016},"\u002Fpobo-cobo-swift","SWIFT POBO and COBO"," with UETR tracking and MT103 confirmations when the receiver requires bank paperwork, and KYC, KYB, and sanctions screening inside the routing path rather than bolted beside it.",[11,8020,8021,8022,8025],{},"Quotes are live and itemized: you see the spread and the flat fee separately before you commit, and ",[136,8023,8024],{"href":307},"pricing is public"," without a sales call.",[11,8027,8028,8029,8032],{},"That is one option among several. The ",[136,8030,8031],{"href":4636},"evaluation checklist"," gives you the criteria to judge any vendor, including this one.",[18,8034,312],{"id":311},[11,8036,8037],{},"Count your payment provider integrations. If the answer is one and you operate in one country, stop reading and go build something else. If the answer is two or more, list the corridors each one covers and the all-in cost per corridor. The gaps and the overlaps are your orchestration case, in numbers your CFO can check.",[11,8039,8040,8041,8043,8044,227],{},"Start with ",[136,8042,4600],{"href":4599}," if the layers are new, or ",[136,8045,8046],{"href":1335},"see coverage by country",[11,8048,8049],{},[324,8050,326],{},{"title":328,"searchDepth":329,"depth":329,"links":8052},[8053,8054,8055,8056,8057,8058,8059],{"id":7803,"depth":329,"text":7804},{"id":7899,"depth":329,"text":7900},{"id":7912,"depth":329,"text":7913},{"id":7952,"depth":329,"text":7953},{"id":7990,"depth":329,"text":7991},{"id":8003,"depth":329,"text":8004},{"id":311,"depth":329,"text":312},"A gateway connects you to one processor. An orchestration platform connects to many rails and picks the best path per transaction. Table and example.",[8062,8065,8068,8071],{"q":8063,"a":8064},"Is a payment orchestration platform just a gateway with more integrations?","No. The difference is the decision, not the count. A gateway passes a transaction to a fixed destination. An orchestration platform evaluates cost, speed, corridor rules, and provider health, then chooses the path for that specific transaction.",{"q":8066,"a":8067},"Can I use both a gateway and an orchestration platform?","Yes, and most companies do. Orchestration sits in front of your existing providers, so your card gateway keeps handling card acceptance while the orchestration layer handles cross-border payouts and settlement.",{"q":8069,"a":8070},"Does orchestration make payments slower by adding a hop?","No. The routing decision takes milliseconds and happens before any money moves. The rail it picks is what determines speed, and routing to a 24\u002F7 local rail instead of a SWIFT wire usually takes days off the delivery time.",{"q":8072,"a":8073},"When is a gateway genuinely the better choice?","One country, one currency, one rail, and no requirement to fail over. At that shape, an orchestration layer adds configuration surface you will not use and a vendor you do not need.",{"author":361},"---\ntitle: \"Payment orchestration vs payment gateway: what's the difference?\"\nseoTitle: \"Payment orchestration vs payment gateway\"\ndescription: \"A gateway connects you to one processor. An orchestration platform connects to many rails and picks the best path per transaction. Table and example.\"\ndate: \"2026-09-16\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is a payment orchestration platform just a gateway with more integrations?\"\n    a: \"No. The difference is the decision, not the count. A gateway passes a transaction to a fixed destination. An orchestration platform evaluates cost, speed, corridor rules, and provider health, then chooses the path for that specific transaction.\"\n  - q: \"Can I use both a gateway and an orchestration platform?\"\n    a: \"Yes, and most companies do. Orchestration sits in front of your existing providers, so your card gateway keeps handling card acceptance while the orchestration layer handles cross-border payouts and settlement.\"\n  - q: \"Does orchestration make payments slower by adding a hop?\"\n    a: \"No. The routing decision takes milliseconds and happens before any money moves. The rail it picks is what determines speed, and routing to a 24\u002F7 local rail instead of a SWIFT wire usually takes days off the delivery time.\"\n  - q: \"When is a gateway genuinely the better choice?\"\n    a: \"One country, one currency, one rail, and no requirement to fail over. At that shape, an orchestration layer adds configuration surface you will not use and a vendor you do not need.\"\n---\n\nA payment gateway connects you to one processor and passes transactions through it on a fixed path. A payment orchestration platform connects to many providers and rails and actively decides, per transaction, which path to take based on cost, speed, corridor rules, and whether the provider is healthy right now.\n\nThe difference is the decision. Everything else follows from it.\n\n## The comparison table\n\n| | Payment gateway | Payment orchestration |\n| --- | --- | --- |\n| What it connects to | One processor or acquirer | Many providers, banks, and rails |\n| Routing decisions | None, the path is fixed at integration time | Per transaction, on cost, speed, corridor, and provider health |\n| FX handling | The processor's rate, usually blended into one number | Quoted per transaction, spread and fee itemized separately |\n| Compliance scope | The processor's program, opaque to you | Screening runs in the routing path, rules vary per corridor |\n| Failover behavior | Manual. A rail outage is your outage | Automatic to a secondary rail or provider |\n| Reconciliation | One settlement file, one format | Normalized across every provider into one model |\n| Adding a country | A new integration and a new error vocabulary | A routing rule |\n\n## When do you only need a gateway?\n\nPlenty of businesses never need orchestration, and vendors who pretend otherwise are wasting your engineering time.\n\nStay on a gateway when you sell in one country, settle in one currency, use one rail, and can tolerate the rail being down for a few hours. A Brazilian SaaS charging Brazilian customers in reais over Pix does not need a routing engine. It needs one good Pix integration.\n\nThe economics agree. A second integration costs weeks of engineering plus ongoing maintenance for every error code, webhook, and reconciliation format it brings with it. If the second rail is not earning that back in coverage, cost, or uptime, do not add it.\n\n## When do you need orchestration?\n\nConcrete triggers, in the order teams usually hit them.\n\n**You operate in two or more countries.** The moment your provider's coverage map stops at a border, you are either turning away business or integrating a second provider. The second integration is where the normalization cost shows up.\n\n**You need fallback when a rail fails.** Every rail fails. Pix has had outages. SPEI has had outages. Correspondent banks hold wires without telling anyone. If a rail going down means payouts stop, you have concentration risk, not a payment system.\n\n**You settle in local currencies.** Multi-currency turns FX from a footnote into a line item. Once you are converting at volume, a half-point of spread across corridors is real money, and you need per-transaction visibility to find it.\n\n**You cannot answer \"what did that payout cost\".** If the true all-in cost of a payment, including spread, is not available per transaction, your unit economics are a guess.\n\n**Your compliance requirements differ by corridor.** A payout into Brazil sits under Central Bank Resolutions 519 through 521. One into the EU sits under MiCA. A gateway built for one market does not model that.\n\nAny one trigger justifies the look. Two or more and you are already paying the cost of orchestration, just in engineering hours instead of vendor fees.\n\n## Worked example: $25,000 from the US to Brazil\n\nSame payment, three paths. Numbers are typical ranges for a corporate payer, not a quote.\n\n**SWIFT wire.** Sending bank charges $25 to $50. One or two correspondent banks deduct $10 to $30 each, and nobody tells you in advance. The receiving bank in Brazil applies its own FX rate, commonly 2 to 5 percent off mid-market for a corporate receiver, and charges a landing fee. Total cost lands somewhere around $650 to $1,350. Delivery is 1 to 5 business days, longer if screening flags it. Send on Friday afternoon and the supplier has money Tuesday or Wednesday.\n\n**Local Pix payout, pre-funded.** You keep a BRL balance in a Brazilian account and pay out of it. Delivery is seconds, 24\u002F7, and the payout fee is small. The cost that does not appear on the invoice is the working capital parked in that account, plus whatever you paid in spread to get it there, plus the FX risk of holding reais.\n\n**Stablecoin bridge into Pix.** Dollars convert to USDC, USDC moves on-chain in seconds, converts to reais at a rate you saw before committing, and delivers over Pix. All-in cost is typically a sub-percent spread plus a small flat fee, so roughly $150 to $250 on $25,000. Delivery is minutes, any hour, any day. No local balance to pre-fund, which is the [working-capital argument for stablecoin settlement](\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts).\n\nThe point is not that one path always wins. It is that a gateway picks for you at integration time and an orchestration layer picks per transaction. If that same supplier demands an MT103 next quarter, the orchestration path sends a wire through the same API and returns the document. The [full stablecoin vs SWIFT breakdown](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments) has the corridor-level numbers, and the [USDC to BRL route guide](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026) has timings per path.\n\n## What does orchestration cost you in complexity?\n\nThe honest tradeoff, since nobody selling orchestration leads with it.\n\nYou gain a vendor between your app and your money. You gain routing configuration that can be wrong, which means a bad rule can send payments down an expensive path silently. You gain a dependency whose coverage map now bounds yours.\n\nYou mitigate all three the same way: pick a platform that shows you the chosen path and the itemized cost on every transaction, and that lets you pin a corridor to a specific rail when you want to override the router. If a vendor cannot tell you why it routed a payment the way it did, that is not orchestration, that is a black box with a nicer API.\n\n## Where BlindPay sits\n\n[BlindPay](\u002Fglobal-payments) is a cross-border orchestration layer built on stablecoin settlement. One API covers payouts over Pix, SPEI, SEPA, ACH, and SWIFT (POBO\u002FCOBO) across a 100+ country network, collections through [virtual US accounts](\u002Fvirtual-accounts) that settle as stablecoins, [SWIFT POBO and COBO](\u002Fpobo-cobo-swift) with UETR tracking and MT103 confirmations when the receiver requires bank paperwork, and KYC, KYB, and sanctions screening inside the routing path rather than bolted beside it.\n\nQuotes are live and itemized: you see the spread and the flat fee separately before you commit, and [pricing is public](\u002Fpricing) without a sales call.\n\nThat is one option among several. The [evaluation checklist](\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform) gives you the criteria to judge any vendor, including this one.\n\n## What to do next\n\nCount your payment provider integrations. If the answer is one and you operate in one country, stop reading and go build something else. If the answer is two or more, list the corridors each one covers and the all-in cost per corridor. The gaps and the overlaps are your orchestration case, in numbers your CFO can check.\n\nStart with [what payment orchestration is](\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration) if the layers are new, or [see coverage by country](\u002Fcoverage).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":7792,"description":8060},"Payment orchestration vs payment gateway","resources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","ObEKh2uAKYwtrvQnGzfCCyEDijwYaMIfytTtGBKUh5U",{"id":8081,"title":8082,"authors":6,"body":8083,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":8656,"description":8657,"extension":342,"faq":8658,"howto":6,"isBlog":359,"isChangelog":359,"meta":8674,"navigation":362,"path":2286,"pillar":359,"products":6,"rawbody":8675,"role":6,"seo":8676,"seoTitle":8677,"stem":8678,"thumbnail":6,"updated":6,"__hash__":8679},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks.md","Stablecoin API SDKs: how one OpenAPI spec keeps five languages in sync",{"type":8,"value":8084,"toc":8644},[8085,8091,8094,8098,8101,8111,8114,8118,8121,8144,8147,8151,8265,8268,8272,8279,8432,8444,8447,8471,8474,8478,8481,8503,8506,8518,8522,8532,8549,8553,8560,8563,8590,8593,8597,8615,8617,8626,8628,8637,8641],[11,8086,8087,8088,8090],{},"BlindPay's stablecoin API is described by a single OpenAPI 3.1 specification at ",[204,8089,6020],{},". That one spec drives request validation on the server, the API reference, the official SDKs for Node, Python, Go, PHP, and Swift, and the tool surface of the MCP server. When a field changes, it changes everywhere at once, so the docs, the SDK, and the API can't disagree.",[11,8092,8093],{},"That's the design goal. Here's how it works, and why it matters more for a payments API than for most.",[18,8095,8097],{"id":8096},"why-does-drift-hurt-more-in-a-payments-api","Why does drift hurt more in a payments API?",[11,8099,8100],{},"Every API drifts. A field gets renamed, an enum gets a new value, an error changes shape, and the docs page updates a week later. Or never.",[11,8102,8103,8104,8106,8107,8110],{},"In most APIs that's annoying. In a payments API it's money. If your code doesn't know about a new payout status, a payout that went ",[204,8105,2030],{}," can look like it vanished. If the docs say an amount is in dollars and the API wants minor units, somebody sends 100 times what they meant. (Amounts in our API are integers in minor units. ",[204,8108,8109],{},"500000"," is 5,000.00. Every time.)",[11,8112,8113],{},"So the rule we work by: there is exactly one place a data shape is defined, and everything else is generated from it.",[18,8115,8117],{"id":8116},"where-does-the-spec-come-from","Where does the spec come from?",[11,8119,8120],{},"Inside the API, every request and response shape is a Zod schema in one shared contract package. Those schemas do three jobs from one definition:",[145,8122,8123,8129,8138],{},[148,8124,8125,8128],{},[119,8126,8127],{},"Validate requests and responses"," in the API itself.",[148,8130,8131,8134,8135,227],{},[119,8132,8133],{},"Generate the OpenAPI 3.1 document"," published at ",[204,8136,8137],{},"api.blindpay.com\u002Fdoc",[148,8139,8140,8143],{},[119,8141,8142],{},"Validate forms"," in the BlindPay dashboard.",[11,8145,8146],{},"Nobody hand-writes the OpenAPI file. When an engineer changes a schema, the spec is regenerated from it. The spec on the server is always the spec in the code.",[18,8148,8150],{"id":8149},"what-gets-generated-from-that-spec","What gets generated from that spec?",[39,8152,8153,8166],{},[42,8154,8155],{},[45,8156,8157,8160,8163],{},[48,8158,8159],{},"Artifact",[48,8161,8162],{},"Where",[48,8164,8165],{},"What it gives you",[61,8167,8168,8180,8193,8206,8219,8232,8243,8254],{},[45,8169,8170,8173,8177],{},[66,8171,8172],{},"OpenAPI 3.1 spec",[66,8174,8175],{},[204,8176,6020],{},[66,8178,8179],{},"The full contract, machine-readable",[45,8181,8182,8185,8190],{},[66,8183,8184],{},"API reference",[66,8186,8187],{},[204,8188,8189],{},"https:\u002F\u002Fapi.blindpay.com\u002Freference",[66,8191,8192],{},"Every endpoint, body, and response, interactive",[45,8194,8195,8198,8203],{},[66,8196,8197],{},"Node.js \u002F TypeScript SDK",[66,8199,8200],{},[204,8201,8202],{},"npm install @blindpay\u002Fnode",[66,8204,8205],{},"Typed methods and responses",[45,8207,8208,8211,8216],{},[66,8209,8210],{},"Python SDK",[66,8212,8213],{},[204,8214,8215],{},"pip install blindpay",[66,8217,8218],{},"The same surface in Python",[45,8220,8221,8224,8229],{},[66,8222,8223],{},"Go SDK",[66,8225,8226],{},[204,8227,8228],{},"go get github.com\u002Fblindpaylabs\u002Fblindpay-go",[66,8230,8231],{},"The same surface in Go",[45,8233,8234,8237,8240],{},[66,8235,8236],{},"PHP SDK",[66,8238,8239],{},"Composer",[66,8241,8242],{},"The same surface in PHP",[45,8244,8245,8248,8251],{},[66,8246,8247],{},"Swift SDK",[66,8249,8250],{},"Swift Package Manager",[66,8252,8253],{},"The same surface for iOS and macOS",[45,8255,8256,8258,8262],{},[66,8257,2701],{},[66,8259,8260],{},[204,8261,6859],{},[66,8263,8264],{},"API tools for AI coding assistants",[11,8266,8267],{},"Five SDKs, one contract. A new field shows up as a typed property, not a surprise inside a JSON blob.",[18,8269,8271],{"id":8270},"what-does-calling-the-api-look-like-from-an-sdk","What does calling the API look like from an SDK?",[11,8273,8274,8275,8278],{},"The Node SDK takes your API key and instance id once, then every method returns the same ",[204,8276,8277],{},"{ data, error }"," shape:",[4913,8280,8284],{"className":8281,"code":8282,"language":8283,"meta":328,"style":328},"language-typescript shiki shiki-themes github-light","import { BlindPay } from '@blindpay\u002Fnode'\n\nconst blindpay = new BlindPay({\n  apiKey: process.env.BLINDPAY_API_KEY!,\n  instanceId: process.env.BLINDPAY_INSTANCE_ID!,\n})\n\nconst { data, error } = await blindpay.available.getRails()\n\nif (error) {\n  throw new Error(error.message)\n}\n\nconsole.log(data) \u002F\u002F fully typed\n","typescript",[204,8285,8286,8300,8304,8323,8336,8348,8352,8356,8385,8389,8397,8410,8414,8418],{"__ignoreMap":328},[4921,8287,8288,8291,8294,8297],{"class":4923,"line":4924},[4921,8289,8290],{"class":5312},"import",[4921,8292,8293],{"class":4960}," { BlindPay } ",[4921,8295,8296],{"class":5312},"from",[4921,8298,8299],{"class":4931}," '@blindpay\u002Fnode'\n",[4921,8301,8302],{"class":4923,"line":329},[4921,8303,4954],{"emptyLinePlaceholder":362},[4921,8305,8306,8309,8312,8314,8317,8320],{"class":4923,"line":1404},[4921,8307,8308],{"class":5312},"const",[4921,8310,8311],{"class":4970}," blindpay",[4921,8313,5345],{"class":5312},[4921,8315,8316],{"class":5312}," new",[4921,8318,8319],{"class":4927}," BlindPay",[4921,8321,8322],{"class":4960},"({\n",[4921,8324,8325,8328,8331,8334],{"class":4923,"line":4951},[4921,8326,8327],{"class":4960},"  apiKey: process.env.",[4921,8329,8330],{"class":4970},"BLINDPAY_API_KEY",[4921,8332,8333],{"class":5312},"!",[4921,8335,6441],{"class":4960},[4921,8337,8338,8341,8344,8346],{"class":4923,"line":4957},[4921,8339,8340],{"class":4960},"  instanceId: process.env.",[4921,8342,8343],{"class":4970},"BLINDPAY_INSTANCE_ID",[4921,8345,8333],{"class":5312},[4921,8347,6441],{"class":4960},[4921,8349,8350],{"class":4923,"line":4964},[4921,8351,5585],{"class":4960},[4921,8353,8354],{"class":4923,"line":4976},[4921,8355,4954],{"emptyLinePlaceholder":362},[4921,8357,8358,8360,8362,8365,8367,8370,8372,8374,8376,8379,8382],{"class":4923,"line":4987},[4921,8359,8308],{"class":5312},[4921,8361,5362],{"class":4960},[4921,8363,8364],{"class":4970},"data",[4921,8366,1304],{"class":4960},[4921,8368,8369],{"class":4970},"error",[4921,8371,5388],{"class":4960},[4921,8373,5391],{"class":5312},[4921,8375,5455],{"class":5312},[4921,8377,8378],{"class":4960}," blindpay.available.",[4921,8380,8381],{"class":4927},"getRails",[4921,8383,8384],{"class":4960},"()\n",[4921,8386,8387],{"class":4923,"line":4998},[4921,8388,4954],{"emptyLinePlaceholder":362},[4921,8390,8391,8394],{"class":4923,"line":5009},[4921,8392,8393],{"class":5312},"if",[4921,8395,8396],{"class":4960}," (error) {\n",[4921,8398,8399,8402,8404,8407],{"class":4923,"line":5020},[4921,8400,8401],{"class":5312},"  throw",[4921,8403,8316],{"class":5312},[4921,8405,8406],{"class":4927}," Error",[4921,8408,8409],{"class":4960},"(error.message)\n",[4921,8411,8412],{"class":4923,"line":5031},[4921,8413,5066],{"class":4960},[4921,8415,8416],{"class":4923,"line":5063},[4921,8417,4954],{"emptyLinePlaceholder":362},[4921,8419,8420,8423,8426,8429],{"class":4923,"line":5546},[4921,8421,8422],{"class":4960},"console.",[4921,8424,8425],{"class":4927},"log",[4921,8427,8428],{"class":4960},"(data) ",[4921,8430,8431],{"class":5354},"\u002F\u002F fully typed\n",[11,8433,8434,8435,8437,8438,8443],{},"No exceptions to catch for API errors, no guessing the error shape. You check ",[204,8436,8369],{},", you move on. The SDK readmes on ",[136,8439,8442],{"href":8440,"rel":8441},"https:\u002F\u002Fgithub.com\u002Fblindpaylabs",[414],"GitHub"," have the full surface per language.",[11,8445,8446],{},"The same call over raw HTTP, if you'd rather skip the SDK:",[4913,8448,8450],{"className":4915,"code":8449,"language":4917,"meta":328,"style":328},"curl https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers \\\n  --header 'Authorization: Bearer YOUR_API_KEY'\n",[204,8451,8452,8463],{"__ignoreMap":328},[4921,8453,8454,8457,8460],{"class":4923,"line":4924},[4921,8455,8456],{"class":4927},"curl",[4921,8458,8459],{"class":4931}," https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers",[4921,8461,8462],{"class":4970}," \\\n",[4921,8464,8465,8468],{"class":4923,"line":329},[4921,8466,8467],{"class":4970},"  --header",[4921,8469,8470],{"class":4931}," 'Authorization: Bearer YOUR_API_KEY'\n",[11,8472,8473],{},"There's one base URL. Which environment you hit, development or production, is decided by which instance your key belongs to.",[18,8475,8477],{"id":8476},"what-if-my-language-isnt-one-of-the-five","What if my language isn't one of the five?",[11,8479,8480],{},"Generate a client. The spec is standard OpenAPI 3.1, so any generator works. For TypeScript types without the SDK:",[4913,8482,8484],{"className":4915,"code":8483,"language":4917,"meta":328,"style":328},"npx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc -o src\u002Fblindpay.d.ts\n",[204,8485,8486],{"__ignoreMap":328},[4921,8487,8488,8491,8494,8497,8500],{"class":4923,"line":4924},[4921,8489,8490],{"class":4927},"npx",[4921,8492,8493],{"class":4931}," openapi-typescript",[4921,8495,8496],{"class":4931}," https:\u002F\u002Fapi.blindpay.com\u002Fdoc",[4921,8498,8499],{"class":4970}," -o",[4921,8501,8502],{"class":4931}," src\u002Fblindpay.d.ts\n",[11,8504,8505],{},"Rust, Java, Kotlin, Ruby, C#: point your generator at the same URL. You'll get the same field names and enums the official SDKs use.",[11,8507,8508,8509,8512,8513,8517],{},"One caveat. A small number of endpoints are excluded from every generated SDK, currently ",[204,8510,8511],{},"POST \u002Fupload\u002Fextract",", which reads invoices with AI. Call those over raw HTTP. The ",[136,8514,8516],{"href":8515},"\u002Fdocs\u002Fsdks","SDK docs"," keep that list current.",[18,8519,8521],{"id":8520},"how-do-error-codes-stay-stable","How do error codes stay stable?",[11,8523,8524,8525,3740,8528,8531],{},"Errors are part of the contract too. Every error response carries a machine-readable code, like ",[204,8526,8527],{},"idempotency_key_payload_mismatch",[204,8529,8530],{},"idempotency_key_in_flight",". Your code can branch on the code, not on a message string that might get reworded.",[11,8533,8534,8535,8537,8538,8540,8541,8544,8545,227],{},"Idempotency is contract-level as well. Send an ",[204,8536,6093],{}," header on any write and a retry with the same body replays the original response with ",[204,8539,6097],{},". A retry with a different body gets a ",[204,8542,8543],{},"422",". That one header is what keeps a network timeout from turning into two payouts. Details in the ",[136,8546,8548],{"href":8547},"\u002Fdocs\u002Flearn\u002Fidempotency","idempotency docs",[18,8550,8552],{"id":8551},"how-does-this-help-ai-coding-assistants","How does this help AI coding assistants?",[11,8554,8555,8556,8559],{},"The same contract generates the tools in the ",[136,8557,8558],{"href":2700},"BlindPay MCP server",". When an endpoint is added or removed, the MCP tool surface changes with it, so an agent never calls a tool the API no longer has.",[11,8561,8562],{},"Around it:",[171,8564,8565,8571,8582],{},[148,8566,8567,8570],{},[119,8568,8569],{},"llms.txt and markdown pages."," The docs publish an llms.txt index and a markdown version of every page, so an agent reads the same reference you do.",[148,8572,8573,8577,8578,8581],{},[119,8574,8575,227],{},[136,8576,2705],{"href":2704}," Install with ",[204,8579,8580],{},"npx skills add blindpaylabs\u002Fskills"," to give Claude Code, Cursor, or Codex working knowledge of payouts, payins, and customers.",[148,8583,8584,8589],{},[119,8585,8586,227],{},[136,8587,8588],{"href":2695},"The CLI"," JSON output and predictable exit codes, so scripts and agents can drive it.",[11,8591,8592],{},"The practical effect: an assistant can build and test a payout flow against a development instance with the right field names on the first try, because it's reading the same contract the API enforces.",[18,8594,8596],{"id":8595},"what-does-this-mean-for-an-integration-timeline","What does this mean for an integration timeline?",[11,8598,8599,8600,6665,8602,1304,8604,6665,8606,8608,8609,8611,8612,227],{},"Faster, and fewer surprises in production. A first payout on a development instance is usually a day of work, and most of that day is your own ledger and UI, not the API. Development instances are free, skip banking-partner review, and accept sentinel amounts (",[204,8601,3903],{},[204,8603,3739],{},[204,8605,3906],{},[204,8607,3743],{},") so you can test every path. Payout timing by rail is in ",[136,8610,226],{"href":225},". The full flow, endpoint by endpoint, is in our ",[136,8613,8614],{"href":2712},"developer guide to integrating a stablecoin API",[18,8616,294],{"id":293},[11,8618,8619,8621,8622,8625],{},[136,8620,300],{"href":299}," is a stablecoin API for cross-border payouts and collections: USDC or USDT in, local currency out over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) to 100+ countries, with no pre-funding. KYC, KYB, and sanctions screening run inside the API. ",[136,8623,8624],{"href":138},"Virtual USD accounts"," turn ACH, wire, and SWIFT deposits into stablecoins. And every piece of it is described by the one spec above.",[18,8627,312],{"id":311},[11,8629,8630,8631,8634,8635,227],{},"Install the SDK for your stack, or run ",[204,8632,8633],{},"npx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc"," and read the generated types for ten minutes. You'll understand the whole API surface faster than any docs page could explain it. Then create a development instance and send your first test payout with the ",[136,8636,319],{"href":318},[11,8638,8639],{},[324,8640,326],{},[5763,8642,8643],{},"html pre.shiki code .sD7c4, html code.shiki .sD7c4{--shiki-default:#D73A49}html pre.shiki code .sgsFI, html code.shiki .sgsFI{--shiki-default:#24292E}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}html pre.shiki code .sYu0t, html code.shiki .sYu0t{--shiki-default:#005CC5}html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}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":328,"searchDepth":329,"depth":329,"links":8645},[8646,8647,8648,8649,8650,8651,8652,8653,8654,8655],{"id":8096,"depth":329,"text":8097},{"id":8116,"depth":329,"text":8117},{"id":8149,"depth":329,"text":8150},{"id":8270,"depth":329,"text":8271},{"id":8476,"depth":329,"text":8477},{"id":8520,"depth":329,"text":8521},{"id":8551,"depth":329,"text":8552},{"id":8595,"depth":329,"text":8596},{"id":293,"depth":329,"text":294},{"id":311,"depth":329,"text":312},"2026-09-11","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.",[8659,8662,8665,8668,8671],{"q":8660,"a":8661},"Which SDKs does the BlindPay stablecoin API support?","Official SDKs for Node.js and TypeScript (@blindpay\u002Fnode on npm), Python (blindpay on PyPI), Go (github.com\u002Fblindpaylabs\u002Fblindpay-go), PHP (Composer), and Swift (Swift Package Manager). For any other language, generate a typed client from the OpenAPI 3.1 spec at https:\u002F\u002Fapi.blindpay.com\u002Fdoc.",{"q":8663,"a":8664},"Where is the BlindPay OpenAPI spec?","At https:\u002F\u002Fapi.blindpay.com\u002Fdoc. It is an OpenAPI 3.1 document covering every public endpoint, and the interactive API reference lives at https:\u002F\u002Fapi.blindpay.com\u002Freference.",{"q":8666,"a":8667},"Can I generate my own client for a stablecoin API?","Yes. Download the OpenAPI spec and run a generator for your language. For TypeScript, npx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc -o src\u002Fblindpay.d.ts produces types for every request and response.",{"q":8669,"a":8670},"Are there endpoints the SDKs do not cover?","A small number, currently POST \u002Fupload\u002Fextract for reading invoices with AI. Call those over raw HTTP even if you use an SDK for everything else.",{"q":8672,"a":8673},"Can AI coding assistants use the BlindPay API?","Yes. The BlindPay MCP server, run with npx -y @blindpay\u002Fmcp, lets Claude Code, Cursor, and Codex call the API against a development instance. Its tools are generated from the same contract as the OpenAPI spec, and the docs publish llms.txt plus markdown versions of every page.",{"author":361},"---\ntitle: \"Stablecoin API SDKs: how one OpenAPI spec keeps five languages in sync\"\nseoTitle: \"Stablecoin API SDKs and OpenAPI docs\"\ndescription: \"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.\"\ndate: \"2026-09-11\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Which SDKs does the BlindPay stablecoin API support?\"\n    a: \"Official SDKs for Node.js and TypeScript (@blindpay\u002Fnode on npm), Python (blindpay on PyPI), Go (github.com\u002Fblindpaylabs\u002Fblindpay-go), PHP (Composer), and Swift (Swift Package Manager). For any other language, generate a typed client from the OpenAPI 3.1 spec at https:\u002F\u002Fapi.blindpay.com\u002Fdoc.\"\n  - q: \"Where is the BlindPay OpenAPI spec?\"\n    a: \"At https:\u002F\u002Fapi.blindpay.com\u002Fdoc. It is an OpenAPI 3.1 document covering every public endpoint, and the interactive API reference lives at https:\u002F\u002Fapi.blindpay.com\u002Freference.\"\n  - q: \"Can I generate my own client for a stablecoin API?\"\n    a: \"Yes. Download the OpenAPI spec and run a generator for your language. For TypeScript, npx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc -o src\u002Fblindpay.d.ts produces types for every request and response.\"\n  - q: \"Are there endpoints the SDKs do not cover?\"\n    a: \"A small number, currently POST \u002Fupload\u002Fextract for reading invoices with AI. Call those over raw HTTP even if you use an SDK for everything else.\"\n  - q: \"Can AI coding assistants use the BlindPay API?\"\n    a: \"Yes. The BlindPay MCP server, run with npx -y @blindpay\u002Fmcp, lets Claude Code, Cursor, and Codex call the API against a development instance. Its tools are generated from the same contract as the OpenAPI spec, and the docs publish llms.txt plus markdown versions of every page.\"\n---\n\nBlindPay's stablecoin API is described by a single OpenAPI 3.1 specification at `https:\u002F\u002Fapi.blindpay.com\u002Fdoc`. That one spec drives request validation on the server, the API reference, the official SDKs for Node, Python, Go, PHP, and Swift, and the tool surface of the MCP server. When a field changes, it changes everywhere at once, so the docs, the SDK, and the API can't disagree.\n\nThat's the design goal. Here's how it works, and why it matters more for a payments API than for most.\n\n## Why does drift hurt more in a payments API?\n\nEvery API drifts. A field gets renamed, an enum gets a new value, an error changes shape, and the docs page updates a week later. Or never.\n\nIn most APIs that's annoying. In a payments API it's money. If your code doesn't know about a new payout status, a payout that went `on_hold` can look like it vanished. If the docs say an amount is in dollars and the API wants minor units, somebody sends 100 times what they meant. (Amounts in our API are integers in minor units. `500000` is 5,000.00. Every time.)\n\nSo the rule we work by: there is exactly one place a data shape is defined, and everything else is generated from it.\n\n## Where does the spec come from?\n\nInside the API, every request and response shape is a Zod schema in one shared contract package. Those schemas do three jobs from one definition:\n\n1. **Validate requests and responses** in the API itself.\n2. **Generate the OpenAPI 3.1 document** published at `api.blindpay.com\u002Fdoc`.\n3. **Validate forms** in the BlindPay dashboard.\n\nNobody hand-writes the OpenAPI file. When an engineer changes a schema, the spec is regenerated from it. The spec on the server is always the spec in the code.\n\n## What gets generated from that spec?\n\n| Artifact | Where | What it gives you |\n| --- | --- | --- |\n| OpenAPI 3.1 spec | `https:\u002F\u002Fapi.blindpay.com\u002Fdoc` | The full contract, machine-readable |\n| API reference | `https:\u002F\u002Fapi.blindpay.com\u002Freference` | Every endpoint, body, and response, interactive |\n| Node.js \u002F TypeScript SDK | `npm install @blindpay\u002Fnode` | Typed methods and responses |\n| Python SDK | `pip install blindpay` | The same surface in Python |\n| Go SDK | `go get github.com\u002Fblindpaylabs\u002Fblindpay-go` | The same surface in Go |\n| PHP SDK | Composer | The same surface in PHP |\n| Swift SDK | Swift Package Manager | The same surface for iOS and macOS |\n| MCP server | `npx -y @blindpay\u002Fmcp` | API tools for AI coding assistants |\n\nFive SDKs, one contract. A new field shows up as a typed property, not a surprise inside a JSON blob.\n\n## What does calling the API look like from an SDK?\n\nThe Node SDK takes your API key and instance id once, then every method returns the same `{ data, error }` shape:\n\n```typescript\nimport { BlindPay } from '@blindpay\u002Fnode'\n\nconst blindpay = new BlindPay({\n  apiKey: process.env.BLINDPAY_API_KEY!,\n  instanceId: process.env.BLINDPAY_INSTANCE_ID!,\n})\n\nconst { data, error } = await blindpay.available.getRails()\n\nif (error) {\n  throw new Error(error.message)\n}\n\nconsole.log(data) \u002F\u002F fully typed\n```\n\nNo exceptions to catch for API errors, no guessing the error shape. You check `error`, you move on. The SDK readmes on [GitHub](https:\u002F\u002Fgithub.com\u002Fblindpaylabs) have the full surface per language.\n\nThe same call over raw HTTP, if you'd rather skip the SDK:\n\n```bash\ncurl https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers \\\n  --header 'Authorization: Bearer YOUR_API_KEY'\n```\n\nThere's one base URL. Which environment you hit, development or production, is decided by which instance your key belongs to.\n\n## What if my language isn't one of the five?\n\nGenerate a client. The spec is standard OpenAPI 3.1, so any generator works. For TypeScript types without the SDK:\n\n```bash\nnpx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc -o src\u002Fblindpay.d.ts\n```\n\nRust, Java, Kotlin, Ruby, C#: point your generator at the same URL. You'll get the same field names and enums the official SDKs use.\n\nOne caveat. A small number of endpoints are excluded from every generated SDK, currently `POST \u002Fupload\u002Fextract`, which reads invoices with AI. Call those over raw HTTP. The [SDK docs](\u002Fdocs\u002Fsdks) keep that list current.\n\n## How do error codes stay stable?\n\nErrors are part of the contract too. Every error response carries a machine-readable code, like `idempotency_key_payload_mismatch` or `idempotency_key_in_flight`. Your code can branch on the code, not on a message string that might get reworded.\n\nIdempotency is contract-level as well. Send an `Idempotency-Key` header on any write and a retry with the same body replays the original response with `Idempotency-Replayed: true`. A retry with a different body gets a `422`. That one header is what keeps a network timeout from turning into two payouts. Details in the [idempotency docs](\u002Fdocs\u002Flearn\u002Fidempotency).\n\n## How does this help AI coding assistants?\n\nThe same contract generates the tools in the [BlindPay MCP server](\u002Fblog\u002Fmcp). When an endpoint is added or removed, the MCP tool surface changes with it, so an agent never calls a tool the API no longer has.\n\nAround it:\n\n- **llms.txt and markdown pages.** The docs publish an llms.txt index and a markdown version of every page, so an agent reads the same reference you do.\n- **[Agent Skills](\u002Fblog\u002Fagent-skills).** Install with `npx skills add blindpaylabs\u002Fskills` to give Claude Code, Cursor, or Codex working knowledge of payouts, payins, and customers.\n- **[The CLI](\u002Fblog\u002Fcli).** JSON output and predictable exit codes, so scripts and agents can drive it.\n\nThe practical effect: an assistant can build and test a payout flow against a development instance with the right field names on the first try, because it's reading the same contract the API enforces.\n\n## What does this mean for an integration timeline?\n\nFaster, and fewer surprises in production. A first payout on a development instance is usually a day of work, and most of that day is your own ledger and UI, not the API. Development instances are free, skip banking-partner review, and accept sentinel amounts (`66600` forces `failed`, `77700` forces `refunded`) so you can test every path. Payout timing by rail is in [how long a stablecoin payout takes](\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times). The full flow, endpoint by endpoint, is in our [developer guide to integrating a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api).\n\n## Where does BlindPay fit?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API for cross-border payouts and collections: USDC or USDT in, local currency out over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) to 100+ countries, with no pre-funding. KYC, KYB, and sanctions screening run inside the API. [Virtual USD accounts](\u002Fvirtual-accounts) turn ACH, wire, and SWIFT deposits into stablecoins. And every piece of it is described by the one spec above.\n\n## What to do next\n\nInstall the SDK for your stack, or run `npx openapi-typescript https:\u002F\u002Fapi.blindpay.com\u002Fdoc` and read the generated types for ten minutes. You'll understand the whole API surface faster than any docs page could explain it. Then create a development instance and send your first test payout with the [payout quickstart](\u002Fdocs\u002Fquickstart-payout).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":8082,"description":8657},"Stablecoin API SDKs and OpenAPI docs","resources\u002Fmore\u002Fstablecoin-api-openapi-sdks","cnZdxzhXwtdfPb3AkrG-EXGL1KXeJS0zAhbMnMJ9FNM",{"id":8681,"title":8682,"authors":6,"body":8683,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":4266,"description":8794,"extension":342,"faq":8795,"howto":6,"isBlog":359,"isChangelog":359,"meta":8814,"navigation":362,"path":1243,"pillar":359,"products":6,"rawbody":8815,"role":6,"seo":8816,"seoTitle":8817,"stem":8818,"thumbnail":6,"updated":6,"__hash__":8819},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality.md","Stablecoin API SLAs and settlement finality explained",{"type":8,"value":8684,"toc":8787},[8685,8691,8695,8710,8713,8717,8720,8723,8727,8736,8739,8743,8749,8757,8761,8770],[11,8686,8687,8688,227],{},"An SLA percentage and a settlement guarantee are two different promises, and most stablecoin API providers do not say which one they are quoting. A vendor can publish 99.9% uptime and still leave a recipient waiting minutes, or longer, for money they can spend, because the percentage usually covers a narrower window than the one that matters to the recipient. For background on the full flow a stablecoin API handles, see ",[136,8689,8690],{"href":479},"what is a stablecoin API",[18,8692,8694],{"id":8693},"every-stablecoin-apis-sla-page-says-roughly-the-same-number","Every stablecoin API's SLA page says roughly the same number",[11,8696,8697,8698,8703,8704,8709],{},"BlindPay does not publish a single blended uptime number, because averaging every corridor into one figure hides the gap described below. Line up a handful of other stablecoin infrastructure providers, though, and their advertised SLAs sit in a narrow band. ",[136,8699,8702],{"href":8700,"rel":8701},"https:\u002F\u002Fwww.fireblocks.com\u002Fblog\u002Fhow-we-meet-institutional-standards-insurance-compliance-security\u002F",[414],"Fireblocks' own site commits to 99.9% uptime",", with roughly 99.97% actually delivered month to month. A third-party comparison table estimates Bridge and BVNK's negotiated enterprise SLAs land in that same range, though neither company posts the figure publicly, and puts Circle Mint and Crossmint close to 99.9% as well. Conduit's public tier sits at 99.5%, with a higher figure reserved for its enterprise add-on. Most of these numbers come from ",[136,8705,8708],{"href":8706,"rel":8707},"https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15232572-best-stablecoin-settlement-apis-2026-sla-guarantees-audit-trails-and-reconciliation-compared",[414],"a single third-party comparison"," rather than each company's own contract language, so the exact decimals are indicative and have not been checked against every provider's actual agreement. Companies running different architectures and different custody models converge on nearly the same headline figure.",[11,8711,8712],{},"That convergence is the tell. Uptime measures whether the API answers a request, not how fast money moves or how final it is once it arrives, and a system can drop almost no requests while still making a recipient wait. When every provider clusters around the same three or four nines, the number stops distinguishing anyone, and what is actually being measured behind it matters more than the digits.",[18,8714,8716],{"id":8715},"what-is-the-difference-between-t1-and-t2-and-which-one-is-a-provider-promising","What is the difference between T1 and T2, and which one is a provider promising?",[11,8718,8719],{},"Most published SLAs measure the span between an API call being accepted and a transaction being submitted onchain: call that T1. A request goes out, an accepted status and a transaction hash come back, and the clock stops there, which says nothing about whether the transaction is done. Economic finality, T2, is the point where reorg risk has cleared and the money is unreversibly available to whoever is supposed to receive it. On most chains T1 happens in a second or two. T2 can take meaningfully longer, and the gap between them is where a support ticket gets opened: the dashboard says success, the recipient says nothing has arrived.",[11,8721,8722],{},"This distinction is rarely spelled out on a pricing or SLA page. An accepted API response with a transaction hash is a technical acknowledgment, not a settlement guarantee, so if a provider does not say which one its SLA covers, the safe assumption is T1. It is the cheaper thing to measure and the one that makes the uptime number look best, since submission almost never fails even on the days downstream confirmation stalls. A lot of published reliability numbers answer \"did the API work\" while implying \"did the payment happen,\" and those are not the same question.",[18,8724,8726],{"id":8725},"how-long-does-an-fx-quote-stay-valid","How long does an FX quote stay valid?",[11,8728,8729,8730,8735],{},"Settlement speed is one number worth interrogating. Quote validity is another, and it gets less attention than it should. ",[136,8731,8734],{"href":8732,"rel":8733},"https:\u002F\u002Fdevelopers.circle.com\u002Fstablefx\u002Fconcepts\u002Ftechnical-guide",[414],"Circle's StableFX documentation states that quotes are generated across competing market makers in under 500 milliseconds",", and once a trade is created from a quote, both sides get a ten-minute window to submit signatures before it expires. That is a specific, written number a developer can hold Circle to. Most competitors are not nearly that explicit. A widely repeated secondary claim puts typical quote staleness across stablecoin APIs somewhere between 15 and 60 seconds, but that figure traces back to an aggregator comparison rather than each vendor's own documentation, so it reads more as a general sense of the market than a commitment any one company has made in writing. No other provider has been found to state its window this plainly in public documentation, though one may exist in materials that have not been published.",[11,8737,8738],{},"FX moves inside that window whether or not the provider discloses it. If an integration shows a customer a rate, waits on confirmation, then submits, and the quote has expired or gets re-priced on execution, someone absorbs the difference. Who that someone is should be established before a customer notices the number that settled does not match the number they saw.",[18,8740,8742],{"id":8741},"why-does-a-payout-on-one-corridor-settle-faster-than-another-on-the-same-rail","Why does a payout on one corridor settle faster than another on the same rail?",[11,8744,8745,8746,227],{},"A blended, platform-wide SLA hides something a corridor-level number would show plainly: the stablecoin leg of a payment is rarely the bottleneck. The fiat off-ramp is. A payout into Mexico or Brazil rides SPEI and PIX, both real-time payment rails, so once the stablecoin conversion clears, the recipient's bank account sees the funds within minutes. A payout riding a corridor without that same real-time layer can settle same-day or the next business day even when the onchain leg finished in seconds. The provider and the underlying token do not change between corridors, and neither does the published SLA, but the wait time differs by close to a full day depending on which currency it lands in. For the full mechanics of a cross-border payout, see the ",[136,8747,8748],{"href":618},"stablecoin payments guide",[11,8750,8751,8752,8754,8755,227],{},"Checking corridor by corridor instead of trusting a platform average matters: a company can be honestly reporting 99.9% uptime while the thing that actually matters, how long a specific payout to a specific country takes, is set by the local rail and has nothing to do with the API's own performance. That gap is easier to see across corridors on the ",[136,8753,1261],{"href":299}," page, and in more detail on a single route like ",[136,8756,644],{"href":1757},[18,8758,8760],{"id":8759},"what-to-ask-before-integrating","What to ask before integrating",[11,8762,8763,8764,8769],{},"A few questions cut through most of what a sales deck will not volunteer. Does the published SLA measure API acceptance to onchain submission, or acceptance to economic finality? How long is a quote valid, and who absorbs the difference if the market moves inside that window? What is the settlement time for this specific corridor, separate from the average across everything else the platform supports? And when a settlement webhook arrives twice, which ",[136,8765,8768],{"href":8766,"rel":8767},"https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15182330-stablecoin-webhooks-and-real-time-event-streaming-provider-integrations",[414],"most providers' at-least-once delivery models allow for",", does the integration correctly ignore the duplicate instead of double-processing it?",[11,8771,8772,8773,8775,8776,8779,8780,8782,8783,8786],{},"BlindPay quotes and settles named corridors: BRL, MXN, ARS, COP, and USD\u002FEUR, so these are not hypothetical questions there either. Rates come from live FX rather than a table refreshed on a schedule, and there is no pre-funding sitting idle in a nostro account. The settlement time quoted is corridor-specific, not a blended figure covering a fast rail and a slow one at once. Virtual account and payout details, along with the KYB and transaction-monitoring model behind them, are in the ",[136,8774,2786],{"href":2785}," and on the ",[136,8777,8778],{"href":2270},"compliance page",". The account infrastructure itself is covered on ",[136,8781,632],{"href":138},". Ask for a live quote on a specific corridor through ",[136,8784,8785],{"href":1344},"blindpay.com\u002Fcontact"," and compare the number against the SLA percentage quoted elsewhere.",{"title":328,"searchDepth":329,"depth":329,"links":8788},[8789,8790,8791,8792,8793],{"id":8693,"depth":329,"text":8694},{"id":8715,"depth":329,"text":8716},{"id":8725,"depth":329,"text":8726},{"id":8741,"depth":329,"text":8742},{"id":8759,"depth":329,"text":8760},"Stablecoin API uptime numbers cluster near 99.9% for a reason: most providers measure API acceptance, not the point where money becomes final.",[8796,8799,8802,8805,8808,8811],{"q":8797,"a":8798},"What's the difference between an SLA and a settlement guarantee for a stablecoin API?","An SLA measures whether the API responds and how often it stays up. A settlement guarantee is about when the recipient can spend the money, with no reorg risk left. A provider can hit 99.9% uptime on every call while the underlying transfer still takes minutes to clear, because the 99.9% almost always tracks submission, not the point where the transaction becomes final.",{"q":8800,"a":8801},"Why do so many stablecoin API providers publish an SLA close to 99.9%?","Most of them measure the same narrow thing: whether an API call was accepted and a transaction was submitted. Whether that transaction reached economic finality is a separate question that most SLAs never answer. Once the industry standardizes on the easiest metric to hit, providers with very different architectures land in a similar range, which makes the number a weak signal for comparing them.",{"q":8803,"a":8804},"What do T1 and T2 mean in stablecoin settlement?","T1 is the span from API acceptance to onchain submission, the point where a 200 response and a transaction reference come back. T2 is economic finality: the point at which the transaction can no longer be reversed by a chain reorganization, so the recipient can spend the funds. Published SLAs almost always cover T1 unless a provider states otherwise.",{"q":8806,"a":8807},"How long does a stablecoin FX quote stay valid before it expires?","It depends on the provider, and there is no industry standard. Circle publishes a hard number for this: quotes come back in under 500 milliseconds, and once a trade is created, the ten-minute signature window is a documented commitment, not a market default. Other providers publish shorter or looser windows, so the number should be confirmed in writing rather than assumed to match Circle's.",{"q":8809,"a":8810},"Does a stablecoin payout settle at the same speed in every country?","No. Settlement speed on the fiat leg depends mainly on the local payment rail; the stablecoin conversion itself typically clears in seconds. Corridors with real-time payment rails, like PIX in Brazil or SPEI in Mexico, settle in minutes once the onchain leg clears. Corridors without that infrastructure settle same-day or the next business day even when the crypto side finished instantly.",{"q":8812,"a":8813},"What should a developer ask a stablecoin API provider before integrating?","Whether the published SLA measures API acceptance to submission or acceptance to economic finality, how long a quote stays valid and who absorbs slippage if the market moves inside that window, what the settlement time is for the specific corridor being built against instead of a platform average, and how the integration should handle a settlement webhook that arrives more than once.",{},"---\ntitle: \"Stablecoin API SLAs and settlement finality explained\"\nseoTitle: \"Stablecoin API SLAs and settlement finality\"\ndescription: \"Stablecoin API uptime numbers cluster near 99.9% for a reason: most providers measure API acceptance, not the point where money becomes final.\"\ndate: \"2026-08-28\"\ncategory: \"payments\"\nfaq:\n  - q: \"What's the difference between an SLA and a settlement guarantee for a stablecoin API?\"\n    a: \"An SLA measures whether the API responds and how often it stays up. A settlement guarantee is about when the recipient can spend the money, with no reorg risk left. A provider can hit 99.9% uptime on every call while the underlying transfer still takes minutes to clear, because the 99.9% almost always tracks submission, not the point where the transaction becomes final.\"\n  - q: \"Why do so many stablecoin API providers publish an SLA close to 99.9%?\"\n    a: \"Most of them measure the same narrow thing: whether an API call was accepted and a transaction was submitted. Whether that transaction reached economic finality is a separate question that most SLAs never answer. Once the industry standardizes on the easiest metric to hit, providers with very different architectures land in a similar range, which makes the number a weak signal for comparing them.\"\n  - q: \"What do T1 and T2 mean in stablecoin settlement?\"\n    a: \"T1 is the span from API acceptance to onchain submission, the point where a 200 response and a transaction reference come back. T2 is economic finality: the point at which the transaction can no longer be reversed by a chain reorganization, so the recipient can spend the funds. Published SLAs almost always cover T1 unless a provider states otherwise.\"\n  - q: \"How long does a stablecoin FX quote stay valid before it expires?\"\n    a: \"It depends on the provider, and there is no industry standard. Circle publishes a hard number for this: quotes come back in under 500 milliseconds, and once a trade is created, the ten-minute signature window is a documented commitment, not a market default. Other providers publish shorter or looser windows, so the number should be confirmed in writing rather than assumed to match Circle's.\"\n  - q: \"Does a stablecoin payout settle at the same speed in every country?\"\n    a: \"No. Settlement speed on the fiat leg depends mainly on the local payment rail; the stablecoin conversion itself typically clears in seconds. Corridors with real-time payment rails, like PIX in Brazil or SPEI in Mexico, settle in minutes once the onchain leg clears. Corridors without that infrastructure settle same-day or the next business day even when the crypto side finished instantly.\"\n  - q: \"What should a developer ask a stablecoin API provider before integrating?\"\n    a: \"Whether the published SLA measures API acceptance to submission or acceptance to economic finality, how long a quote stays valid and who absorbs slippage if the market moves inside that window, what the settlement time is for the specific corridor being built against instead of a platform average, and how the integration should handle a settlement webhook that arrives more than once.\"\n---\n\nAn SLA percentage and a settlement guarantee are two different promises, and most stablecoin API providers do not say which one they are quoting. A vendor can publish 99.9% uptime and still leave a recipient waiting minutes, or longer, for money they can spend, because the percentage usually covers a narrower window than the one that matters to the recipient. For background on the full flow a stablecoin API handles, see [what is a stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api).\n\n## Every stablecoin API's SLA page says roughly the same number\n\nBlindPay does not publish a single blended uptime number, because averaging every corridor into one figure hides the gap described below. Line up a handful of other stablecoin infrastructure providers, though, and their advertised SLAs sit in a narrow band. [Fireblocks' own site commits to 99.9% uptime](https:\u002F\u002Fwww.fireblocks.com\u002Fblog\u002Fhow-we-meet-institutional-standards-insurance-compliance-security\u002F), with roughly 99.97% actually delivered month to month. A third-party comparison table estimates Bridge and BVNK's negotiated enterprise SLAs land in that same range, though neither company posts the figure publicly, and puts Circle Mint and Crossmint close to 99.9% as well. Conduit's public tier sits at 99.5%, with a higher figure reserved for its enterprise add-on. Most of these numbers come from [a single third-party comparison](https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15232572-best-stablecoin-settlement-apis-2026-sla-guarantees-audit-trails-and-reconciliation-compared) rather than each company's own contract language, so the exact decimals are indicative and have not been checked against every provider's actual agreement. Companies running different architectures and different custody models converge on nearly the same headline figure.\n\nThat convergence is the tell. Uptime measures whether the API answers a request, not how fast money moves or how final it is once it arrives, and a system can drop almost no requests while still making a recipient wait. When every provider clusters around the same three or four nines, the number stops distinguishing anyone, and what is actually being measured behind it matters more than the digits.\n\n## What is the difference between T1 and T2, and which one is a provider promising?\n\nMost published SLAs measure the span between an API call being accepted and a transaction being submitted onchain: call that T1. A request goes out, an accepted status and a transaction hash come back, and the clock stops there, which says nothing about whether the transaction is done. Economic finality, T2, is the point where reorg risk has cleared and the money is unreversibly available to whoever is supposed to receive it. On most chains T1 happens in a second or two. T2 can take meaningfully longer, and the gap between them is where a support ticket gets opened: the dashboard says success, the recipient says nothing has arrived.\n\nThis distinction is rarely spelled out on a pricing or SLA page. An accepted API response with a transaction hash is a technical acknowledgment, not a settlement guarantee, so if a provider does not say which one its SLA covers, the safe assumption is T1. It is the cheaper thing to measure and the one that makes the uptime number look best, since submission almost never fails even on the days downstream confirmation stalls. A lot of published reliability numbers answer \"did the API work\" while implying \"did the payment happen,\" and those are not the same question.\n\n## How long does an FX quote stay valid?\n\nSettlement speed is one number worth interrogating. Quote validity is another, and it gets less attention than it should. [Circle's StableFX documentation states that quotes are generated across competing market makers in under 500 milliseconds](https:\u002F\u002Fdevelopers.circle.com\u002Fstablefx\u002Fconcepts\u002Ftechnical-guide), and once a trade is created from a quote, both sides get a ten-minute window to submit signatures before it expires. That is a specific, written number a developer can hold Circle to. Most competitors are not nearly that explicit. A widely repeated secondary claim puts typical quote staleness across stablecoin APIs somewhere between 15 and 60 seconds, but that figure traces back to an aggregator comparison rather than each vendor's own documentation, so it reads more as a general sense of the market than a commitment any one company has made in writing. No other provider has been found to state its window this plainly in public documentation, though one may exist in materials that have not been published.\n\nFX moves inside that window whether or not the provider discloses it. If an integration shows a customer a rate, waits on confirmation, then submits, and the quote has expired or gets re-priced on execution, someone absorbs the difference. Who that someone is should be established before a customer notices the number that settled does not match the number they saw.\n\n## Why does a payout on one corridor settle faster than another on the same rail?\n\nA blended, platform-wide SLA hides something a corridor-level number would show plainly: the stablecoin leg of a payment is rarely the bottleneck. The fiat off-ramp is. A payout into Mexico or Brazil rides SPEI and PIX, both real-time payment rails, so once the stablecoin conversion clears, the recipient's bank account sees the funds within minutes. A payout riding a corridor without that same real-time layer can settle same-day or the next business day even when the onchain leg finished in seconds. The provider and the underlying token do not change between corridors, and neither does the published SLA, but the wait time differs by close to a full day depending on which currency it lands in. For the full mechanics of a cross-border payout, see the [stablecoin payments guide](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\nChecking corridor by corridor instead of trusting a platform average matters: a company can be honestly reporting 99.9% uptime while the thing that actually matters, how long a specific payout to a specific country takes, is set by the local rail and has nothing to do with the API's own performance. That gap is easier to see across corridors on the [global payments](\u002Fglobal-payments) page, and in more detail on a single route like [USDC to BRL](\u002Fusdc-to-brl).\n\n## What to ask before integrating\n\nA few questions cut through most of what a sales deck will not volunteer. Does the published SLA measure API acceptance to onchain submission, or acceptance to economic finality? How long is a quote valid, and who absorbs the difference if the market moves inside that window? What is the settlement time for this specific corridor, separate from the average across everything else the platform supports? And when a settlement webhook arrives twice, which [most providers' at-least-once delivery models allow for](https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15182330-stablecoin-webhooks-and-real-time-event-streaming-provider-integrations), does the integration correctly ignore the duplicate instead of double-processing it?\n\nBlindPay quotes and settles named corridors: BRL, MXN, ARS, COP, and USD\u002FEUR, so these are not hypothetical questions there either. Rates come from live FX rather than a table refreshed on a schedule, and there is no pre-funding sitting idle in a nostro account. The settlement time quoted is corridor-specific, not a blended figure covering a fast rail and a slow one at once. Virtual account and payout details, along with the KYB and transaction-monitoring model behind them, are in the [docs](\u002Fdocs\u002Fintroduction) and on the [compliance page](\u002Fcompliance). The account infrastructure itself is covered on [virtual accounts](\u002Fvirtual-accounts). Ask for a live quote on a specific corridor through [blindpay.com\u002Fcontact](\u002Fcontact) and compare the number against the SLA percentage quoted elsewhere.\n",{"title":8682,"description":8794},"Stablecoin API SLAs and settlement finality","resources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","6gQ9RTuBIat6DUsytRDhO7Sn6GRIdHXilJsLhHHBiyU",{"id":8821,"title":8822,"authors":6,"body":8823,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":8945,"description":8946,"extension":342,"faq":8947,"howto":6,"isBlog":359,"isChangelog":359,"meta":8966,"navigation":362,"path":754,"pillar":359,"products":6,"rawbody":8967,"role":6,"seo":8968,"seoTitle":8969,"stem":8970,"thumbnail":6,"updated":6,"__hash__":8971},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production.md","Stablecoin API sandbox vs production: what testing misses",{"type":8,"value":8824,"toc":8939},[8825,8828,8832,8841,8844,8847,8851,8857,8871,8874,8881,8885,8888,8903,8906,8909,8913,8916,8919,8922,8925],[11,8826,8827],{},"Bridge's own sandbox documentation states it outright: no payments webhook fires while a developer is in sandbox. Most evaluation checklists never catch that gap, because they test whether auth works and whether the response shape matches the docs. Almost none test what happens when a webhook arrives twice, or when a retry hits an idempotency key three seconds after it expired. A sandbox can return a clean 200 on every call and still never once have delivered a webhook to the server, or forced retry logic against an expired key. A green checklist says little about whether an integration survives its first bad day of production traffic.",[18,8829,8831],{"id":8830},"what-bridges-own-docs-admit-sandbox-cant-do","What Bridge's own docs admit sandbox can't do",[11,8833,8834,8835,8840],{},"Bridge is the stablecoin orchestration company Stripe acquired, and its docs state this directly: sandbox fires zero payments-related webhooks. There is no testnet or blockchain connectivity in sandbox either, and the environment is subject to what Bridge calls arbitrary rate limits, meaning it may drop requests without warning. Bridge's own recommendation, in ",[136,8836,8839],{"href":8837,"rel":8838},"https:\u002F\u002Fapidocs.bridge.xyz\u002Fget-started\u002Fintroduction\u002Fquick-start\u002Fsetting-up-sandbox",[414],"its quickstart documentation",", is to use sandbox for schema validation and do the rest of the testing in production.",[11,8842,8843],{},"That recommendation has a direct implication. A team that writes its webhook handler against sandbox and ships it has never seen that handler run against production traffic, because sandbox never sent it one. The first webhook it processes arrives after go-live, against a live customer's live transfer. If the handler has a bug, that bug becomes an incident involving somebody's money, not a failed test in CI.",[11,8845,8846],{},"The same gap likely exists elsewhere in the category, though this has not been audited across every competitor's docs the way Bridge documents its own limits, and few providers are this direct about what their sandbox skips. A provider can have solid production infrastructure and a sandbox that tests almost none of it, and a team evaluating providers by reading the docs alone has no way to tell the difference until it switches to a production key.",[18,8848,8850],{"id":8849},"idempotency-key-expiry-is-where-retry-logic-breaks","Idempotency key expiry is where retry logic breaks",[11,8852,8853,8854,8856],{},"Every serious ",[136,8855,480],{"href":479}," requires an idempotency key on requests that move money or trigger something irreversible, because retrying a POST over a flaky connection should never risk creating the same transfer twice. The mechanism is universal. The expiry behavior is not, and that gap is where naive retry logic breaks.",[11,8858,8859,8860,8865,8866,227],{},"Bridge documents a ",[136,8861,8864],{"href":8862,"rel":8863},"https:\u002F\u002Fapidocs.bridge.xyz\u002Fapi-reference\u002Fintroduction\u002Fidempotence",[414],"24-hour idempotency window",". Reuse the same key after 24 hours and the result is a 422 Unprocessable Entity: the key has expired and the request is treated as brand new. Circle runs a comparable pattern, a required Idempotency-Key header (UUID v4) on mutating endpoints, plus a separate ",[136,8867,8870],{"href":8868,"rel":8869},"https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fcpn\u002Fmanaged-payments\u002Fpayouts\u002Fcreate-payout",[414],"idempotencyKey field inside payout request bodies",[11,8872,8873],{},"Idempotency is not one behavior. It splits into different outcomes depending on what changed since the first request. Reuse a key exactly as sent and Bridge replays the original response, with no new side effect triggered. Reuse it after the 24-hour window closes, or reuse it inside that window with a changed body, and the result is an error instead: a fresh 422 in the first case, an unlabeled idempotency error in the second. Bridge's docs describe that second error without giving it its own status code, because the key no longer matches the request it originally guarded. A retry loop that only branches on 2xx versus non-2xx collapses both error cases into \"failed, try again,\" which is exactly how a stale key ends up firing a duplicate transfer.",[11,8875,8876,8877,8880],{},"BlindPay follows a similar pattern. Every mutating v1 endpoint, payins and payouts included, accepts an opt-in Idempotency-Key header. A repeated key returns the original response, with no duplicate action triggered. The terms-of-service acceptance endpoint handles idempotency on its own: it takes a separate idempotency_key UUID, and reusing that one is rejected outright. The exact expiry window on the general header, and whether a changed body against a reused key throws a distinct conflict error the way Bridge's does, are not yet public. Check the current ",[136,8878,8184],{"href":8879},"\u002Fdocs\u002Fapi\u002Freference"," for the endpoint in question before assuming it matches another provider's behavior.",[18,8882,8884],{"id":8883},"webhook-delivery-is-at-least-once-across-the-industry","Webhook delivery is at-least-once across the industry",[11,8886,8887],{},"Every stablecoin API webhook system worth using assumes the same thing: an endpoint might receive the same event more than once, and handling that safely is on the integrator. That is called at-least-once delivery. It exists because the alternative, guaranteeing exactly-once delivery over an unreliable network, is a much harder distributed-systems problem, and none of the providers covered here claim to have solved it. Providers retry on anything that is not a clean 2xx response, so a slow database write on the receiving end that causes a timeout looks, from the provider's side, exactly like a dropped request that needs retrying.",[11,8889,8890,8891,8896,8897,8902],{},"Circle's implementation is a useful reference for what careful design looks like here. Every webhook is ",[136,8892,8895],{"href":8893,"rel":8894},"https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fverify-webhook-signatures",[414],"signed with ECDSA over P-256",", and the public verification key comes from Circle's API by key ID rather than something hardcoded into the receiving app. That signature travels in an X-Circle-Signature header, checked before the payload is trusted. Circle's ",[136,8898,8901],{"href":8899,"rel":8900},"https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fwebhooks",[414],"documentation states outright that delivery is at least once",", and it tells integrators to deduplicate on the Notification ID before applying any side effect. In practice, a handler's job is to check whether it has already processed that ID and do nothing if it has.",[11,8904,8905],{},"BlindPay runs its webhooks through Svix, and the mechanics land in the same place as Circle's. A svix-id header stays constant across every redelivery attempt of the same event. The svix-timestamp and svix-signature pair is verified with HMAC-SHA256 before acting on the payload, and if an endpoint does not return a 2xx, Svix retries with backoff over the following hours. Deduplicating on svix-id covers the case, and a handler already built for Circle's Notification ID pattern needs little more than a header rename to work against BlindPay's.",[11,8907,8908],{},"One part of this has no clean answer. Neither Circle's nor Bridge's public docs, as of this writing, state a maximum retry window, so there is no single number to size a dedup store against. A naive in-memory set of notification IDs that gets wiped on every deploy loses that history the moment a service redeploys, which is exactly when a provider might still be retrying an event from before the restart. The safer posture is a persistent store with a retention window longer than whatever retry period a provider does document. How much longer is a judgment call, and neither company answers it directly.",[18,8910,8912],{"id":8911},"what-to-check-before-a-production-key-goes-live","What to check before a production key goes live",[11,8914,8915],{},"Run this checklist against a sandbox before a production key goes live. It groups by what kind of failure it catches: money movement or notifications.",[11,8917,8918],{},"On the money-movement side: replay a request with an idempotency key already used, and confirm the client branches on the error rather than retrying it blindly as a network failure. Set request amounts that force a failed transfer and a refunded one, then watch what the reconciliation logic does when a payment sits outside the happy path longer than expected.",[11,8920,8921],{},"On the notification side: trigger a webhook redelivery (most dashboards with an events log allow replaying a specific event manually), and confirm the handler recognizes the repeated ID, skips the side effect, and does not credit an account twice or fire a downstream notification twice. Confirm sandbox and production environments enforce the same dedup and retry rules. A sandbox that silently skips retries will never surface a bug that only shows up once backoff kicks in.",[11,8923,8924],{},"BlindPay's development instances are built so that last check actually holds. Webhooks fire with the same event names and payload shapes in development as in production, and signature verification works the same way too. Payins on a development instance auto-complete around 30 seconds after creation, so a full event can be observed landing rather than guessed at from documentation. Specific outcomes can also be forced by setting the request amount to 666.00 for a failed transfer or 777.00 for a refunded one, which is what \"simulate a stalled transfer\" means in practice: two API calls with different amounts. Every instance gets its own API key, so switching from a development key to a production one at go-live does not touch a single line of webhook-handling code, since the code was already exercised against the exact contract production uses.",[11,8926,8927,8928,8931,8932,1341,8935,8938],{},"Running that checklist against a current sandbox, on whatever provider is in use, surfaces the gap fast: if any of the four checks cannot run before a production key exists, that is the gap the sandbox is not reporting. For a broader view of what to evaluate across providers before committing to one, see the ",[136,8929,8930],{"href":766},"comparison of stablecoin APIs",". To run this checklist against BlindPay's sandbox, start with the ",[136,8933,8934],{"href":2785},"getting started guide",[136,8936,8937],{"href":1344},"talk to the team"," about a specific corridor.",{"title":328,"searchDepth":329,"depth":329,"links":8940},[8941,8942,8943,8944],{"id":8830,"depth":329,"text":8831},{"id":8849,"depth":329,"text":8850},{"id":8883,"depth":329,"text":8884},{"id":8911,"depth":329,"text":8912},"2026-08-27","Most stablecoin API sandboxes pass every test and still leave teams unprepared, because webhook delivery and idempotent retries are what sandboxes fake.",[8948,8951,8954,8957,8960,8963],{"q":8949,"a":8950},"Why does a stablecoin API sandbox pass but production still break?","Sandboxes validate request and response shapes. The failure paths that only surface under real load, webhook retries and idempotency key expiry chief among them, need separate testing. A sandbox that returns clean 200s on every call can still hide a webhook handler that has never processed a redelivered event.",{"q":8952,"a":8953},"Does Bridge's sandbox send webhooks?","No. Bridge states this plainly in its own docs: no webhook covering payments activity fires while a developer is in sandbox, and Bridge recommends validating webhook handling directly in production instead.",{"q":8955,"a":8956},"How long is a Bridge idempotency key valid for?","24 hours. After that window, reusing the key returns a 422 error. Changing the request body and reusing the key inside the window produces a second, separate error that Bridge's docs never label with its own status code.",{"q":8958,"a":8959},"What does 'at least once' webhook delivery mean for an integration?","A single event can reach a webhook endpoint more than once, for instance if the first delivery attempt times out or the server briefly returns a non-2xx response. The handler has to produce the same result whether it processes that event once or several times. Circle's webhooks, for example, are signed and explicitly documented as [at-least-once](https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fwebhooks), and Circle expects integrators to key their dedup logic off the notification ID rather than trust that each delivery is unique.",{"q":8961,"a":8962},"Does BlindPay's sandbox send real webhooks?","Yes. Development instances differ from production only in which API key signs the request. The events fired and their shapes stay identical, and verification works the same way too, so nothing about the handler needs to change at go-live.",{"q":8964,"a":8965},"What should a team test before moving a stablecoin integration to production?","Send a duplicate idempotency key and confirm the client handles the rejection, force a webhook redelivery and confirm the handler doesn't double-apply it, simulate a failed and a refunded transfer, and confirm dedup logic behaves the same way in sandbox as it will in production.",{},"---\ntitle: \"Stablecoin API sandbox vs production: what testing misses\"\nseoTitle: \"Stablecoin API sandbox vs production\"\ndescription: \"Most stablecoin API sandboxes pass every test and still leave teams unprepared, because webhook delivery and idempotent retries are what sandboxes fake.\"\ndate: \"2026-08-27\"\ncategory: \"payments\"\nfaq:\n  - q: \"Why does a stablecoin API sandbox pass but production still break?\"\n    a: \"Sandboxes validate request and response shapes. The failure paths that only surface under real load, webhook retries and idempotency key expiry chief among them, need separate testing. A sandbox that returns clean 200s on every call can still hide a webhook handler that has never processed a redelivered event.\"\n  - q: \"Does Bridge's sandbox send webhooks?\"\n    a: \"No. Bridge states this plainly in its own docs: no webhook covering payments activity fires while a developer is in sandbox, and Bridge recommends validating webhook handling directly in production instead.\"\n  - q: \"How long is a Bridge idempotency key valid for?\"\n    a: \"24 hours. After that window, reusing the key returns a 422 error. Changing the request body and reusing the key inside the window produces a second, separate error that Bridge's docs never label with its own status code.\"\n  - q: \"What does 'at least once' webhook delivery mean for an integration?\"\n    a: \"A single event can reach a webhook endpoint more than once, for instance if the first delivery attempt times out or the server briefly returns a non-2xx response. The handler has to produce the same result whether it processes that event once or several times. Circle's webhooks, for example, are signed and explicitly documented as [at-least-once](https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fwebhooks), and Circle expects integrators to key their dedup logic off the notification ID rather than trust that each delivery is unique.\"\n  - q: \"Does BlindPay's sandbox send real webhooks?\"\n    a: \"Yes. Development instances differ from production only in which API key signs the request. The events fired and their shapes stay identical, and verification works the same way too, so nothing about the handler needs to change at go-live.\"\n  - q: \"What should a team test before moving a stablecoin integration to production?\"\n    a: \"Send a duplicate idempotency key and confirm the client handles the rejection, force a webhook redelivery and confirm the handler doesn't double-apply it, simulate a failed and a refunded transfer, and confirm dedup logic behaves the same way in sandbox as it will in production.\"\n---\n\nBridge's own sandbox documentation states it outright: no payments webhook fires while a developer is in sandbox. Most evaluation checklists never catch that gap, because they test whether auth works and whether the response shape matches the docs. Almost none test what happens when a webhook arrives twice, or when a retry hits an idempotency key three seconds after it expired. A sandbox can return a clean 200 on every call and still never once have delivered a webhook to the server, or forced retry logic against an expired key. A green checklist says little about whether an integration survives its first bad day of production traffic.\n\n## What Bridge's own docs admit sandbox can't do\n\nBridge is the stablecoin orchestration company Stripe acquired, and its docs state this directly: sandbox fires zero payments-related webhooks. There is no testnet or blockchain connectivity in sandbox either, and the environment is subject to what Bridge calls arbitrary rate limits, meaning it may drop requests without warning. Bridge's own recommendation, in [its quickstart documentation](https:\u002F\u002Fapidocs.bridge.xyz\u002Fget-started\u002Fintroduction\u002Fquick-start\u002Fsetting-up-sandbox), is to use sandbox for schema validation and do the rest of the testing in production.\n\nThat recommendation has a direct implication. A team that writes its webhook handler against sandbox and ships it has never seen that handler run against production traffic, because sandbox never sent it one. The first webhook it processes arrives after go-live, against a live customer's live transfer. If the handler has a bug, that bug becomes an incident involving somebody's money, not a failed test in CI.\n\nThe same gap likely exists elsewhere in the category, though this has not been audited across every competitor's docs the way Bridge documents its own limits, and few providers are this direct about what their sandbox skips. A provider can have solid production infrastructure and a sandbox that tests almost none of it, and a team evaluating providers by reading the docs alone has no way to tell the difference until it switches to a production key.\n\n## Idempotency key expiry is where retry logic breaks\n\nEvery serious [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) requires an idempotency key on requests that move money or trigger something irreversible, because retrying a POST over a flaky connection should never risk creating the same transfer twice. The mechanism is universal. The expiry behavior is not, and that gap is where naive retry logic breaks.\n\nBridge documents a [24-hour idempotency window](https:\u002F\u002Fapidocs.bridge.xyz\u002Fapi-reference\u002Fintroduction\u002Fidempotence). Reuse the same key after 24 hours and the result is a 422 Unprocessable Entity: the key has expired and the request is treated as brand new. Circle runs a comparable pattern, a required Idempotency-Key header (UUID v4) on mutating endpoints, plus a separate [idempotencyKey field inside payout request bodies](https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fcpn\u002Fmanaged-payments\u002Fpayouts\u002Fcreate-payout).\n\nIdempotency is not one behavior. It splits into different outcomes depending on what changed since the first request. Reuse a key exactly as sent and Bridge replays the original response, with no new side effect triggered. Reuse it after the 24-hour window closes, or reuse it inside that window with a changed body, and the result is an error instead: a fresh 422 in the first case, an unlabeled idempotency error in the second. Bridge's docs describe that second error without giving it its own status code, because the key no longer matches the request it originally guarded. A retry loop that only branches on 2xx versus non-2xx collapses both error cases into \"failed, try again,\" which is exactly how a stale key ends up firing a duplicate transfer.\n\nBlindPay follows a similar pattern. Every mutating v1 endpoint, payins and payouts included, accepts an opt-in Idempotency-Key header. A repeated key returns the original response, with no duplicate action triggered. The terms-of-service acceptance endpoint handles idempotency on its own: it takes a separate idempotency_key UUID, and reusing that one is rejected outright. The exact expiry window on the general header, and whether a changed body against a reused key throws a distinct conflict error the way Bridge's does, are not yet public. Check the current [API reference](\u002Fdocs\u002Fapi\u002Freference) for the endpoint in question before assuming it matches another provider's behavior.\n\n## Webhook delivery is at-least-once across the industry\n\nEvery stablecoin API webhook system worth using assumes the same thing: an endpoint might receive the same event more than once, and handling that safely is on the integrator. That is called at-least-once delivery. It exists because the alternative, guaranteeing exactly-once delivery over an unreliable network, is a much harder distributed-systems problem, and none of the providers covered here claim to have solved it. Providers retry on anything that is not a clean 2xx response, so a slow database write on the receiving end that causes a timeout looks, from the provider's side, exactly like a dropped request that needs retrying.\n\nCircle's implementation is a useful reference for what careful design looks like here. Every webhook is [signed with ECDSA over P-256](https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fverify-webhook-signatures), and the public verification key comes from Circle's API by key ID rather than something hardcoded into the receiving app. That signature travels in an X-Circle-Signature header, checked before the payload is trusted. Circle's [documentation states outright that delivery is at least once](https:\u002F\u002Fdevelopers.circle.com\u002Fapi-reference\u002Fwebhooks), and it tells integrators to deduplicate on the Notification ID before applying any side effect. In practice, a handler's job is to check whether it has already processed that ID and do nothing if it has.\n\nBlindPay runs its webhooks through Svix, and the mechanics land in the same place as Circle's. A svix-id header stays constant across every redelivery attempt of the same event. The svix-timestamp and svix-signature pair is verified with HMAC-SHA256 before acting on the payload, and if an endpoint does not return a 2xx, Svix retries with backoff over the following hours. Deduplicating on svix-id covers the case, and a handler already built for Circle's Notification ID pattern needs little more than a header rename to work against BlindPay's.\n\nOne part of this has no clean answer. Neither Circle's nor Bridge's public docs, as of this writing, state a maximum retry window, so there is no single number to size a dedup store against. A naive in-memory set of notification IDs that gets wiped on every deploy loses that history the moment a service redeploys, which is exactly when a provider might still be retrying an event from before the restart. The safer posture is a persistent store with a retention window longer than whatever retry period a provider does document. How much longer is a judgment call, and neither company answers it directly.\n\n## What to check before a production key goes live\n\nRun this checklist against a sandbox before a production key goes live. It groups by what kind of failure it catches: money movement or notifications.\n\nOn the money-movement side: replay a request with an idempotency key already used, and confirm the client branches on the error rather than retrying it blindly as a network failure. Set request amounts that force a failed transfer and a refunded one, then watch what the reconciliation logic does when a payment sits outside the happy path longer than expected.\n\nOn the notification side: trigger a webhook redelivery (most dashboards with an events log allow replaying a specific event manually), and confirm the handler recognizes the repeated ID, skips the side effect, and does not credit an account twice or fire a downstream notification twice. Confirm sandbox and production environments enforce the same dedup and retry rules. A sandbox that silently skips retries will never surface a bug that only shows up once backoff kicks in.\n\nBlindPay's development instances are built so that last check actually holds. Webhooks fire with the same event names and payload shapes in development as in production, and signature verification works the same way too. Payins on a development instance auto-complete around 30 seconds after creation, so a full event can be observed landing rather than guessed at from documentation. Specific outcomes can also be forced by setting the request amount to 666.00 for a failed transfer or 777.00 for a refunded one, which is what \"simulate a stalled transfer\" means in practice: two API calls with different amounts. Every instance gets its own API key, so switching from a development key to a production one at go-live does not touch a single line of webhook-handling code, since the code was already exercised against the exact contract production uses.\n\nRunning that checklist against a current sandbox, on whatever provider is in use, surfaces the gap fast: if any of the four checks cannot run before a production key exists, that is the gap the sandbox is not reporting. For a broader view of what to evaluate across providers before committing to one, see the [comparison of stablecoin APIs](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026). To run this checklist against BlindPay's sandbox, start with the [getting started guide](\u002Fdocs\u002Fintroduction), or [talk to the team](\u002Fcontact) about a specific corridor.\n",{"title":8822,"description":8946},"Stablecoin API sandbox vs production","resources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","VDH3ed6OTaSP9_K9BGB-OG1I1vaX8YGUuOPIs5Eo_V4",{"id":8973,"title":8974,"authors":6,"body":8975,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":9303,"description":9304,"extension":342,"faq":9305,"howto":6,"isBlog":359,"isChangelog":359,"meta":9321,"navigation":362,"path":9322,"pillar":359,"products":6,"rawbody":9323,"role":6,"seo":9324,"seoTitle":9325,"stem":9326,"thumbnail":6,"updated":5834,"__hash__":9327},"content\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america.md","Stablecoin cards in Latin America: how they work in Brazil, Mexico, Argentina, and Colombia",{"type":8,"value":8976,"toc":9291},[8977,8981,8986,8989,8994,8998,9001,9007,9013,9019,9022,9026,9127,9130,9136,9139,9142,9145,9148,9155,9158,9161,9164,9171,9174,9177,9184,9188,9191,9202,9205,9209,9262,9271,9273,9287],[11,8978,8979],{},[324,8980,3959],{},[11,8982,8983,8985],{},[119,8984,4656],{}," A stablecoin card in Latin America is a Visa or Mastercard, usually denominated in US dollars, that spends from a USDC or USDT balance. People use them to hold dollars and spend them online or locally, and businesses use them to pay regional teams. Each country's card, crypto, and foreign-currency rules decide how programs are built and what they cost.",[11,8987,8988],{},"Latin America is where stablecoin cards stopped being a niche. The reasons are practical: people want dollars, international cards are expensive, and local instant payment rails set a high bar for anything slower.",[11,8990,8991,8992,227],{},"This guide goes country by country through the four markets that matter most. For the mechanics of the card itself, read ",[136,8993,4667],{"href":4666},[18,8995,8997],{"id":8996},"why-is-latin-america-a-stablecoin-card-market","Why is Latin America a stablecoin card market?",[11,8999,9000],{},"Three forces push in the same direction.",[11,9002,9003,9006],{},[119,9004,9005],{},"Dollar demand."," Households and freelancers in Argentina, Venezuela, and Colombia have held dollars for decades as a hedge against inflation and devaluation. A stablecoin balance is a dollar account that does not require a US bank.",[11,9008,9009,9012],{},[119,9010,9011],{},"Expensive foreign-currency spend."," Local cards spending abroad or in dollars often carry taxes and spreads. Brazil charges 3.5 percent IOF on foreign-currency spend on cards issued there. Argentina adds a 30 percent income tax withholding to foreign-currency card spend paid in pesos.",[11,9014,9015,9018],{},[119,9016,9017],{},"Dollar income."," A growing number of people earn in dollars from US and European clients. They want to receive, hold, and spend those dollars without converting everything on payday.",[11,9020,9021],{},"The networks noticed. When Mastercard announced stablecoin settlement in June 2026, it named ARQ, formerly DolarApp, among the first partners in the US and Latin America.",[18,9023,9025],{"id":9024},"country-by-country","Country by country",[39,9027,9028,9042],{},[42,9029,9030],{},[45,9031,9032,9034,9036,9038,9040],{},[48,9033],{},[48,9035,3094],{},[48,9037,3107],{},[48,9039,3133],{},[48,9041,3120],{},[61,9043,9044,9060,9077,9094,9110],{},[45,9045,9046,9049,9052,9055,9057],{},[66,9047,9048],{},"Local instant rail",[66,9050,9051],{},"Pix, 24\u002F7, seconds",[66,9053,9054],{},"SPEI, 24\u002F7, near real time",[66,9056,3479],{},[66,9058,9059],{},"PSE, minutes, bank windows",[45,9061,9062,9065,9068,9071,9074],{},[66,9063,9064],{},"Card issuers",[66,9066,9067],{},"Banks and BCB-authorized payment institutions",[66,9069,9070],{},"Banks and e-money institutions (IFPEs) under the 2018 Fintech Law",[66,9072,9073],{},"Banks and payment service providers under BCRA rules",[66,9075,9076],{},"Banks and financial institutions supervised by the SFC",[45,9078,9079,9082,9085,9088,9091],{},[66,9080,9081],{},"Virtual asset rules",[66,9083,9084],{},"Law 14.478\u002F2022 and BCB Resolutions 519, 520, and 521 (SPSAV regime, in force February 2026)",[66,9086,9087],{},"Fintech Law; Banco de México limits what regulated institutions can offer",[66,9089,9090],{},"Law 27,739 (2024), PSAV registry at the CNV",[66,9092,9093],{},"No dedicated license; UIAF Resolution 314 of 2021 reporting",[45,9095,9096,9099,9102,9105,9108],{},[66,9097,9098],{},"Foreign-currency card spend",[66,9100,9101],{},"3.5 percent IOF on locally issued cards",[66,9103,9104],{},"Network FX and issuer fees",[66,9106,9107],{},"30 percent withholding when paid in pesos",[66,9109,9104],{},[45,9111,9112,9115,9118,9121,9124],{},[66,9113,9114],{},"Main stablecoin card use",[66,9116,9117],{},"Travel, USD subscriptions, dollar savings",[66,9119,9120],{},"Remittance recipients, USD income",[66,9122,9123],{},"Savings and daily spend in dollars",[66,9125,9126],{},"Freelancer income in USD",[967,9128,3094],{"id":9129},"brazil",[11,9131,9132,9133,9135],{},"Brazil has the most developed rules of the four. Law 14.478\u002F2022 created the virtual asset framework, and the Banco Central do Brasil's Resolutions 519, 520, and 521 set up the SPSAV authorization regime, in force since February 2, 2026. The ",[136,9134,3240],{"href":3239}," covers who needs one.",[11,9137,9138],{},"The card side is separate. Card issuers are banks or payment institutions authorized by the BCB. A stablecoin card for Brazilian residents therefore needs a licensed issuer on the card side and an authorized provider on the stablecoin side.",[11,9140,9141],{},"The practical catch is Pix. Brazilians pay rent, utility bills, and each other over Pix, and many small merchants prefer it to cards. A card is great for a Netflix bill in dollars. It cannot pay a Pix charge or a boleto.",[967,9143,3107],{"id":9144},"mexico",[11,9146,9147],{},"Mexico regulates fintechs under the 2018 Fintech Law, with Banco de México and the CNBV as supervisors. E-money institutions (IFPEs) can issue prepaid cards, and banks issue debit cards. Banco de México restricts how regulated financial institutions offer virtual asset operations to the public, which shapes how stablecoin card programs for Mexican users are built: the card and the stablecoin balance often sit with different providers rather than with one Mexican bank.",[11,9149,9150,9151,9154],{},"Mexico is also the world's second-largest remittance recipient. For a family receiving dollars from the US, a USD stablecoin card is one option. A peso deposit over SPEI, which settles in near real time, is the other. The ",[136,9152,9153],{"href":7229},"USDC to MXN routes guide"," compares the cash-out side.",[967,9156,3133],{"id":9157},"argentina",[11,9159,9160],{},"Argentina is the market where dollar cards make the most intuitive sense. Law 27,739 of 2024 created a registration regime for virtual asset service providers (PSAVs) at the Comisión Nacional de Valores. The currency controls on individuals were loosened in April 2025, but the habit of holding dollars is older than any single policy.",[11,9162,9163],{},"The tax detail matters for card design. As of 2026, foreign-currency card spend that the cardholder pays in pesos carries a 30 percent withholding on account of income tax, which the cardholder can later reclaim or credit. Paying from a dollar balance avoids it. That is part of why stablecoin cards funded in USDT or USDC are popular for everyday spending, not just travel.",[11,9165,9166,9167,9170],{},"For peso needs, Transfers 3.0 moves money between bank accounts and wallets. The ",[136,9168,9169],{"href":7251},"USDC to ARS routes guide"," covers it.",[967,9172,3120],{"id":9173},"colombia",[11,9175,9176],{},"Colombia has no dedicated crypto license as of 2026. Virtual asset providers operate under anti-money-laundering reporting to the UIAF, the financial intelligence unit, under Resolution 314 of 2021, plus tax reporting to the DIAN. Card issuers are banks and financial institutions supervised by the Superintendencia Financiera.",[11,9178,9179,9180,9183],{},"The strongest use case is freelancers earning in dollars from foreign clients. A dollar card lets them spend without converting, and a PSE payout to a Colombian bank account covers pesos. The ",[136,9181,9182],{"href":7240},"USDC to COP routes guide"," compares both.",[18,9185,9187],{"id":9186},"what-a-usd-card-actually-costs-at-a-local-merchant","What a USD card actually costs at a local merchant",[11,9189,9190],{},"A USD stablecoin card used at a supermarket in São Paulo, Mexico City, or Bogotá goes through three steps:",[145,9192,9193,9196,9199],{},[148,9194,9195],{},"The merchant charges in local currency.",[148,9197,9198],{},"The network converts to USD at its daily rate.",[148,9200,9201],{},"The issuer may add a foreign transaction fee, often 1 to 3 percent, and debits the stablecoin balance.",[11,9203,9204],{},"So a USD card spent in local currency is not free. It is usually cheaper than a locally issued card spending in dollars, and it is more expensive than simply holding local currency for local spend. The right answer depends on where the money will be spent.",[18,9206,9208],{"id":9207},"card-or-local-payout-for-a-regional-team","Card or local payout for a regional team?",[39,9210,9211,9221],{},[42,9212,9213],{},[45,9214,9215,9218],{},[48,9216,9217],{},"If the recipient...",[48,9219,9220],{},"Pay with",[61,9222,9223,9231,9239,9247,9255],{},[45,9224,9225,9228],{},[66,9226,9227],{},"Spends mostly on USD subscriptions, tools, and travel",[66,9229,9230],{},"USD stablecoin card",[45,9232,9233,9236],{},[66,9234,9235],{},"Wants to save in dollars",[66,9237,9238],{},"USD stablecoin card or stablecoin balance",[45,9240,9241,9244],{},[66,9242,9243],{},"Pays rent, bills, and local suppliers",[66,9245,9246],{},"Pix, SPEI, Transfers 3.0, or PSE payout",[45,9248,9249,9252],{},[66,9250,9251],{},"Needs cash",[66,9253,9254],{},"Local bank payout",[45,9256,9257,9260],{},[66,9258,9259],{},"Is a supplier invoicing in local currency",[66,9261,9254],{},[11,9263,9264,9265,1337,9267,9270],{},"Many platforms offer both. BlindPay covers the local payout side: USDC or USDT converted and delivered over Pix and TED in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and PSE in Colombia, with compliance inside the API. The ",[136,9266,1227],{"href":1226},[136,9268,9269],{"href":1221},"LATAM contractor payroll guide"," cover those flows end to end.",[18,9272,5747],{"id":5746},[11,9274,9275,9276,9280,9281,1223,9284,9286],{},"For the cross-border card comparison, read ",[136,9277,9279],{"href":9278},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","stablecoin-funded virtual cards vs. traditional virtual cards",". If you are building a program, continue with the ",[136,9282,9283],{"href":5829},"developer's guide",[136,9285,5715],{"href":5714},", which covers how card and virtual asset rules stack by country.",[11,9288,9289],{},[324,9290,326],{},{"title":328,"searchDepth":329,"depth":329,"links":9292},[9293,9294,9300,9301,9302],{"id":8996,"depth":329,"text":8997},{"id":9024,"depth":329,"text":9025,"children":9295},[9296,9297,9298,9299],{"id":9129,"depth":1404,"text":3094},{"id":9144,"depth":1404,"text":3107},{"id":9157,"depth":1404,"text":3133},{"id":9173,"depth":1404,"text":3120},{"id":9186,"depth":329,"text":9187},{"id":9207,"depth":329,"text":9208},{"id":5746,"depth":329,"text":5747},"2026-09-13","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.",[9306,9309,9312,9315,9318],{"q":9307,"a":9308},"Are stablecoin cards legal in Latin America?","Yes, in Brazil, Mexico, Argentina, and Colombia, provided the card is issued by a licensed issuer and the stablecoin services come from a provider that meets local virtual asset and anti-money-laundering rules. Each country regulates the two layers separately: card issuing under payment or banking law, and the stablecoin conversion under its virtual asset framework, such as Brazil's SPSAV regime or Argentina's PSAV registry.",{"q":9310,"a":9311},"Why are dollar stablecoin cards popular in Argentina?","Argentines have a long history of protecting savings from inflation and devaluation by holding US dollars. A USD stablecoin card lets them hold USDT or USDC and spend it at local and online merchants without a foreign bank account. Foreign-currency card spend paid in pesos also carries a 30 percent income tax withholding as of 2026, which makes spending from a dollar balance more attractive.",{"q":9313,"a":9314},"How much does it cost to spend a USD stablecoin card in Brazil or Mexico?","When a USD card pays a merchant charging in reais or pesos, the card network converts at its daily rate and the issuer may add a foreign transaction fee, commonly 1 to 3 percent. Cards issued by Brazilian institutions pay a separate 3.5 percent IOF on foreign-currency spending, which is one reason Brazilians compare dollar cards and local accounts carefully.",{"q":9316,"a":9317},"Should I pay Latin American contractors with a card or a local bank transfer?","Use a card when the contractor spends mostly in US dollars or wants to keep a dollar balance, and a local bank transfer when the money is for rent, bills, and local suppliers. In Brazil those payments run on Pix and boleto, in Mexico on SPEI, and in Argentina on Transfers 3.0, which cards cannot pay. Many platforms offer both and let the contractor choose.",{"q":9319,"a":9320},"Do I need a local bank account to use a stablecoin card in Latin America?","No. A stablecoin card needs identity verification, not a local bank account, and it is funded from a stablecoin balance. Moving money from that balance into a local bank account is a separate step that needs a licensed off-ramp paying out over the country's rails, such as Pix in Brazil or SPEI in Mexico.",{"author":361},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america","---\ntitle: \"Stablecoin cards in Latin America: how they work in Brazil, Mexico, Argentina, and Colombia\"\nseoTitle: \"Stablecoin cards in Latin America\"\ndescription: \"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.\"\ndate: \"2026-09-13\"\nupdated: \"2026-09-21\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Are stablecoin cards legal in Latin America?\"\n    a: \"Yes, in Brazil, Mexico, Argentina, and Colombia, provided the card is issued by a licensed issuer and the stablecoin services come from a provider that meets local virtual asset and anti-money-laundering rules. Each country regulates the two layers separately: card issuing under payment or banking law, and the stablecoin conversion under its virtual asset framework, such as Brazil's SPSAV regime or Argentina's PSAV registry.\"\n  - q: \"Why are dollar stablecoin cards popular in Argentina?\"\n    a: \"Argentines have a long history of protecting savings from inflation and devaluation by holding US dollars. A USD stablecoin card lets them hold USDT or USDC and spend it at local and online merchants without a foreign bank account. Foreign-currency card spend paid in pesos also carries a 30 percent income tax withholding as of 2026, which makes spending from a dollar balance more attractive.\"\n  - q: \"How much does it cost to spend a USD stablecoin card in Brazil or Mexico?\"\n    a: \"When a USD card pays a merchant charging in reais or pesos, the card network converts at its daily rate and the issuer may add a foreign transaction fee, commonly 1 to 3 percent. Cards issued by Brazilian institutions pay a separate 3.5 percent IOF on foreign-currency spending, which is one reason Brazilians compare dollar cards and local accounts carefully.\"\n  - q: \"Should I pay Latin American contractors with a card or a local bank transfer?\"\n    a: \"Use a card when the contractor spends mostly in US dollars or wants to keep a dollar balance, and a local bank transfer when the money is for rent, bills, and local suppliers. In Brazil those payments run on Pix and boleto, in Mexico on SPEI, and in Argentina on Transfers 3.0, which cards cannot pay. Many platforms offer both and let the contractor choose.\"\n  - q: \"Do I need a local bank account to use a stablecoin card in Latin America?\"\n    a: \"No. A stablecoin card needs identity verification, not a local bank account, and it is funded from a stablecoin balance. Moving money from that balance into a local bank account is a separate step that needs a licensed off-ramp paying out over the country's rails, such as Pix in Brazil or SPEI in Mexico.\"\n---\n\n*Reading time: about 7 minutes.*\n\n**Summary:** A stablecoin card in Latin America is a Visa or Mastercard, usually denominated in US dollars, that spends from a USDC or USDT balance. People use them to hold dollars and spend them online or locally, and businesses use them to pay regional teams. Each country's card, crypto, and foreign-currency rules decide how programs are built and what they cost.\n\nLatin America is where stablecoin cards stopped being a niche. The reasons are practical: people want dollars, international cards are expensive, and local instant payment rails set a high bar for anything slower.\n\nThis guide goes country by country through the four markets that matter most. For the mechanics of the card itself, read [what stablecoin card issuing is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing).\n\n## Why is Latin America a stablecoin card market?\n\nThree forces push in the same direction.\n\n**Dollar demand.** Households and freelancers in Argentina, Venezuela, and Colombia have held dollars for decades as a hedge against inflation and devaluation. A stablecoin balance is a dollar account that does not require a US bank.\n\n**Expensive foreign-currency spend.** Local cards spending abroad or in dollars often carry taxes and spreads. Brazil charges 3.5 percent IOF on foreign-currency spend on cards issued there. Argentina adds a 30 percent income tax withholding to foreign-currency card spend paid in pesos.\n\n**Dollar income.** A growing number of people earn in dollars from US and European clients. They want to receive, hold, and spend those dollars without converting everything on payday.\n\nThe networks noticed. When Mastercard announced stablecoin settlement in June 2026, it named ARQ, formerly DolarApp, among the first partners in the US and Latin America.\n\n## Country by country\n\n| | Brazil | Mexico | Argentina | Colombia |\n|---|---|---|---|---|\n| Local instant rail | Pix, 24\u002F7, seconds | SPEI, 24\u002F7, near real time | Transfers 3.0 | PSE, minutes, bank windows |\n| Card issuers | Banks and BCB-authorized payment institutions | Banks and e-money institutions (IFPEs) under the 2018 Fintech Law | Banks and payment service providers under BCRA rules | Banks and financial institutions supervised by the SFC |\n| Virtual asset rules | Law 14.478\u002F2022 and BCB Resolutions 519, 520, and 521 (SPSAV regime, in force February 2026) | Fintech Law; Banco de México limits what regulated institutions can offer | Law 27,739 (2024), PSAV registry at the CNV | No dedicated license; UIAF Resolution 314 of 2021 reporting |\n| Foreign-currency card spend | 3.5 percent IOF on locally issued cards | Network FX and issuer fees | 30 percent withholding when paid in pesos | Network FX and issuer fees |\n| Main stablecoin card use | Travel, USD subscriptions, dollar savings | Remittance recipients, USD income | Savings and daily spend in dollars | Freelancer income in USD |\n\n### Brazil\n\nBrazil has the most developed rules of the four. Law 14.478\u002F2022 created the virtual asset framework, and the Banco Central do Brasil's Resolutions 519, 520, and 521 set up the SPSAV authorization regime, in force since February 2, 2026. The [PSAV explainer](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained) covers who needs one.\n\nThe card side is separate. Card issuers are banks or payment institutions authorized by the BCB. A stablecoin card for Brazilian residents therefore needs a licensed issuer on the card side and an authorized provider on the stablecoin side.\n\nThe practical catch is Pix. Brazilians pay rent, utility bills, and each other over Pix, and many small merchants prefer it to cards. A card is great for a Netflix bill in dollars. It cannot pay a Pix charge or a boleto.\n\n### Mexico\n\nMexico regulates fintechs under the 2018 Fintech Law, with Banco de México and the CNBV as supervisors. E-money institutions (IFPEs) can issue prepaid cards, and banks issue debit cards. Banco de México restricts how regulated financial institutions offer virtual asset operations to the public, which shapes how stablecoin card programs for Mexican users are built: the card and the stablecoin balance often sit with different providers rather than with one Mexican bank.\n\nMexico is also the world's second-largest remittance recipient. For a family receiving dollars from the US, a USD stablecoin card is one option. A peso deposit over SPEI, which settles in near real time, is the other. The [USDC to MXN routes guide](\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026) compares the cash-out side.\n\n### Argentina\n\nArgentina is the market where dollar cards make the most intuitive sense. Law 27,739 of 2024 created a registration regime for virtual asset service providers (PSAVs) at the Comisión Nacional de Valores. The currency controls on individuals were loosened in April 2025, but the habit of holding dollars is older than any single policy.\n\nThe tax detail matters for card design. As of 2026, foreign-currency card spend that the cardholder pays in pesos carries a 30 percent withholding on account of income tax, which the cardholder can later reclaim or credit. Paying from a dollar balance avoids it. That is part of why stablecoin cards funded in USDT or USDC are popular for everyday spending, not just travel.\n\nFor peso needs, Transfers 3.0 moves money between bank accounts and wallets. The [USDC to ARS routes guide](\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026) covers it.\n\n### Colombia\n\nColombia has no dedicated crypto license as of 2026. Virtual asset providers operate under anti-money-laundering reporting to the UIAF, the financial intelligence unit, under Resolution 314 of 2021, plus tax reporting to the DIAN. Card issuers are banks and financial institutions supervised by the Superintendencia Financiera.\n\nThe strongest use case is freelancers earning in dollars from foreign clients. A dollar card lets them spend without converting, and a PSE payout to a Colombian bank account covers pesos. The [USDC to COP routes guide](\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026) compares both.\n\n## What a USD card actually costs at a local merchant\n\nA USD stablecoin card used at a supermarket in São Paulo, Mexico City, or Bogotá goes through three steps:\n\n1. The merchant charges in local currency.\n2. The network converts to USD at its daily rate.\n3. The issuer may add a foreign transaction fee, often 1 to 3 percent, and debits the stablecoin balance.\n\nSo a USD card spent in local currency is not free. It is usually cheaper than a locally issued card spending in dollars, and it is more expensive than simply holding local currency for local spend. The right answer depends on where the money will be spent.\n\n## Card or local payout for a regional team?\n\n| If the recipient... | Pay with |\n|---|---|\n| Spends mostly on USD subscriptions, tools, and travel | USD stablecoin card |\n| Wants to save in dollars | USD stablecoin card or stablecoin balance |\n| Pays rent, bills, and local suppliers | Pix, SPEI, Transfers 3.0, or PSE payout |\n| Needs cash | Local bank payout |\n| Is a supplier invoicing in local currency | Local bank payout |\n\nMany platforms offer both. BlindPay covers the local payout side: USDC or USDT converted and delivered over Pix and TED in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and PSE in Colombia, with compliance inside the API. The [marketplace payouts guide](\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam) and [LATAM contractor payroll guide](\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors) cover those flows end to end.\n\n## What to read next\n\nFor the cross-border card comparison, read [stablecoin-funded virtual cards vs. traditional virtual cards](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts). If you are building a program, continue with the [developer's guide](\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api) and the [compliance guide](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance), which covers how card and virtual asset rules stack by country.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":8974,"description":9304},"Stablecoin cards in Latin America","resources\u002Fmore\u002Fstablecoin-cards-latin-america","Q29aP5IQ1Zr9DpKk9_gV9V4o2BKoHN1dGpB4Ae1NRcM",{"id":9329,"title":9330,"authors":6,"body":9331,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":9752,"description":9753,"extension":342,"faq":9754,"howto":6,"isBlog":359,"isChangelog":359,"meta":9770,"navigation":362,"path":2457,"pillar":359,"products":6,"rawbody":9771,"role":6,"seo":9772,"seoTitle":9773,"stem":9774,"thumbnail":6,"updated":6,"__hash__":9775},"content\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees.md","Stablecoin payment fees vs credit card processing fees: what merchants actually pay",{"type":8,"value":9332,"toc":9742},[9333,9352,9355,9359,9362,9382,9385,9399,9402,9428,9432,9435,9463,9466,9470,9576,9580,9583,9588,9608,9613,9630,9633,9637,9640,9672,9675,9679,9682,9708,9714,9718,9721,9733,9737],[11,9334,9335,9336,9339,9340,9343,9344,9347,9348,9351],{},"Card processing typically costs merchants ",[119,9337,9338],{},"1.5% to 3.5% per transaction",", and international sales add roughly ",[119,9341,9342],{},"1% in cross-border fees and 1% to 3% in currency conversion",", before chargebacks. A stablecoin payment costs a ",[119,9345,9346],{},"network fee of cents"," on low-cost chains (usually paid by the sender), plus a ",[119,9349,9350],{},"flat payout fee and a sub-percent FX spread"," if you convert to local currency. For cross-border merchants, the gap is often several percentage points of revenue.",[11,9353,9354],{},"The headline rates only tell half the story, though. Both rails have costs that don't show up on the pricing page. This guide puts all of them on the table.",[18,9356,9358],{"id":9357},"what-does-a-merchant-actually-pay-for-a-card-transaction","What does a merchant actually pay for a card transaction?",[11,9360,9361],{},"A card fee is three fees wearing a trench coat:",[171,9363,9364,9370,9376],{},[148,9365,9366,9369],{},[119,9367,9368],{},"Interchange:"," paid to the cardholder's issuing bank. The biggest piece, and it varies by card type, rewards tier, and whether the card was present.",[148,9371,9372,9375],{},[119,9373,9374],{},"Network assessment:"," paid to the card network.",[148,9377,9378,9381],{},[119,9379,9380],{},"Processor or acquirer markup:"," paid to whoever gave you the merchant account.",[11,9383,9384],{},"Blended, that lands at roughly 1.5% to 3.5% for most merchants. Then the international extras:",[171,9386,9387,9393],{},[148,9388,9389,9392],{},[119,9390,9391],{},"Cross-border fee:"," around 1% when the card was issued in another country.",[148,9394,9395,9398],{},[119,9396,9397],{},"Currency conversion:"," 1% to 3% when the customer pays in a currency different from yours.",[11,9400,9401],{},"And the ones nobody puts in a sales deck:",[171,9403,9404,9410,9416,9422],{},[148,9405,9406,9409],{},[119,9407,9408],{},"Chargeback fees:"," typically $15 to $100 per dispute, win or lose, on top of the lost sale.",[148,9411,9412,9415],{},[119,9413,9414],{},"Rolling reserves:"," higher-risk merchants often have 5% to 10% of revenue held back for months.",[148,9417,9418,9421],{},[119,9419,9420],{},"Payout delay:"," one to three business days of float on every sale. At scale, that's real working capital.",[148,9423,9424,9427],{},[119,9425,9426],{},"PCI compliance:"," audits, tooling, and scope reduction work.",[18,9429,9431],{"id":9430},"what-does-a-merchant-pay-for-a-stablecoin-transaction","What does a merchant pay for a stablecoin transaction?",[11,9433,9434],{},"Fewer layers, so fewer fees:",[171,9436,9437,9443,9449,9455],{},[148,9438,9439,9442],{},[119,9440,9441],{},"Network fee (gas):"," cents or less on Polygon, Base, Arbitrum, and Stellar. The sender usually pays it. Ethereum mainnet costs more, which is why payment flows mostly avoid it.",[148,9444,9445,9448],{},[119,9446,9447],{},"FX spread:"," only if you convert USDC or USDT into local currency. The difference between the mid-market rate and your conversion rate.",[148,9450,9451,9454],{},[119,9452,9453],{},"Payout fee:"," a flat or small fee to deliver funds to your bank over a local rail like Pix, SPEI, RTP, or SEPA.",[148,9456,9457,9460,9461,227],{},[119,9458,9459],{},"Platform fee:"," some providers charge a subscription. BlindPay's plans are on the ",[136,9462,1712],{"href":307},[11,9464,9465],{},"No interchange, because there's no issuing bank. No network assessment, because there's no card network. No chargebacks, because confirmed transfers are final.",[18,9467,9469],{"id":9468},"stablecoin-vs-card-fees-side-by-side","Stablecoin vs card fees, side by side",[39,9471,9472,9485],{},[42,9473,9474],{},[45,9475,9476,9479,9482],{},[48,9477,9478],{},"Cost",[48,9480,9481],{},"Stablecoin (USDC\u002FUSDT)",[48,9483,9484],{},"Credit card",[61,9486,9487,9500,9513,9526,9539,9552,9565],{},[45,9488,9489,9494,9497],{},[66,9490,9491],{},[119,9492,9493],{},"Base processing",[66,9495,9496],{},"Network fee of cents, usually paid by the sender",[66,9498,9499],{},"Typically 1.5% to 3.5%",[45,9501,9502,9507,9510],{},[66,9503,9504],{},[119,9505,9506],{},"Cross-border",[66,9508,9509],{},"None; the same transfer works in any country",[66,9511,9512],{},"Around 1% extra on foreign cards",[45,9514,9515,9520,9523],{},[66,9516,9517],{},[119,9518,9519],{},"Currency conversion",[66,9521,9522],{},"Sub-percent FX spread, only if you convert",[66,9524,9525],{},"1% to 3% markup",[45,9527,9528,9533,9536],{},[66,9529,9530],{},[119,9531,9532],{},"Payout to your bank",[66,9534,9535],{},"Flat payout fee; minutes over instant local rails",[66,9537,9538],{},"Included, but 1 to 3 business days",[45,9540,9541,9546,9549],{},[66,9542,9543],{},[119,9544,9545],{},"Chargebacks",[66,9547,9548],{},"None; transfers are final",[66,9550,9551],{},"$15 to $100 per dispute, plus the lost sale",[45,9553,9554,9559,9562],{},[66,9555,9556],{},[119,9557,9558],{},"Reserves",[66,9560,9561],{},"None",[66,9563,9564],{},"5% to 10% held for months on higher-risk accounts",[45,9566,9567,9572,9574],{},[66,9568,9569],{},[119,9570,9571],{},"Weekend settlement",[66,9573,3028],{},[66,9575,3458],{},[18,9577,9579],{"id":9578},"a-worked-example-100000-a-month-in-international-sales","A worked example: $100,000 a month in international sales",[11,9581,9582],{},"Take an online merchant selling $100,000 a month, mostly to customers outside its home country. These numbers are illustrative; your real rates depend on your processor, risk profile, and corridor.",[11,9584,9585],{},[119,9586,9587],{},"Cards:",[171,9589,9590,9593,9596,9599,9602],{},[148,9591,9592],{},"Processing at 2.9%: $2,900",[148,9594,9595],{},"Cross-border at 1%: $1,000",[148,9597,9598],{},"Currency conversion at 1.5%: $1,500",[148,9600,9601],{},"20 chargebacks at $25 each: $500, plus the value of the disputed goods",[148,9603,9604,9607],{},[119,9605,9606],{},"Total: around $5,900 a month, or 5.9% of revenue,"," before reserves and float",[11,9609,9610],{},[119,9611,9612],{},"Stablecoins, for the share of customers who pay that way:",[171,9614,9615,9618,9621,9624],{},[148,9616,9617],{},"Network fees: paid by the customer, cents each",[148,9619,9620],{},"Conversion to local currency at a sub-percent spread, plus a flat payout fee per settlement",[148,9622,9623],{},"No chargebacks, no reserves",[148,9625,9626,9629],{},[119,9627,9628],{},"Total: typically a fraction of the card cost,"," and settled the same day",[11,9631,9632],{},"That's why cross-border merchants are the ones moving first. A domestic merchant on a good card rate saves less. A merchant selling across borders, paying 5% to 6% all-in, saves most of it. BlindPay's own figure for replacing correspondent banking with stablecoin settlement and local rails is up to 90% lower transfer costs.",[18,9634,9636],{"id":9635},"what-are-the-hidden-costs-of-stablecoin-payments","What are the hidden costs of stablecoin payments?",[11,9638,9639],{},"Being honest about the stablecoin side:",[171,9641,9642,9648,9654,9660,9666],{},[148,9643,9644,9647],{},[119,9645,9646],{},"Customer adoption."," Not every customer holds USDC or USDT. Stablecoins work best as an added option, or for B2B invoices and marketplace payouts where the counterparty already uses them.",[148,9649,9650,9653],{},[119,9651,9652],{},"Refunds are manual."," No chargeback also means no automatic reversal. You send refunds yourself, so write the policy down.",[148,9655,9656,9659],{},[119,9657,9658],{},"Wrong-network transfers."," A customer who sends USDC on a network you don't support creates a support ticket and a recovery process. Be explicit at checkout.",[148,9661,9662,9665],{},[119,9663,9664],{},"Conversion spreads vary."," A provider quoting a low headline rate can make it back on the FX leg. Always ask for itemized quotes.",[148,9667,9668,9671],{},[119,9669,9670],{},"Accounting setup."," Your finance team needs a clear process for recording stablecoin receipts and conversions. It's not hard, but it's new.",[11,9673,9674],{},"None of these is a dealbreaker. All of them are cheaper than a 2% cross-border markup on every sale, forever.",[18,9676,9678],{"id":9677},"how-do-you-compare-quotes-fairly","How do you compare quotes fairly?",[11,9680,9681],{},"The trap is comparing a blended card rate to a stablecoin headline rate. Hold these constant instead:",[145,9683,9684,9690,9696,9702],{},[148,9685,9686,9689],{},[119,9687,9688],{},"Same amount."," Fees compress with size differently on each rail.",[148,9691,9692,9695],{},[119,9693,9694],{},"Same day."," FX and spreads move daily.",[148,9697,9698,9701],{},[119,9699,9700],{},"Same corridor."," USDC to BRL over Pix prices differently from USDT to EUR over SEPA.",[148,9703,9704,9707],{},[119,9705,9706],{},"Itemized fees."," Spread, payout fee, and network fee as separate numbers.",[11,9709,9710,9711,9713],{},"BlindPay quotes split the FX spread from the payout fee, so you can see what the conversion costs and what the delivery costs, and which one moved if a rate changes. You can check a public corridor like ",[136,9712,644],{"href":1757}," for today's rate.",[18,9715,9717],{"id":9716},"when-should-merchants-keep-cards","When should merchants keep cards?",[11,9719,9720],{},"When the customer doesn't hold stablecoins and won't. When the purchase depends on consumer credit. When sales are small, domestic, and low-risk on a great rate.",[11,9722,9723,9724,9726,9727,9729,9730,227],{},"The pattern we see work: keep cards at checkout, and use stablecoins for the expensive part, cross-border settlement and payouts. Our guide to ",[136,9725,2763],{"href":2762}," covers the receiving setup, and ",[136,9728,2419],{"href":2418}," covers how funds get to your bank. If you're choosing between tokens, see ",[136,9731,9732],{"href":1070},"USDC vs USDT for payments",[18,9734,9736],{"id":9735},"see-your-real-numbers","See your real numbers",[11,9738,9739,9740,227],{},"Pricing pages don't pay invoices; quotes do. If you want an itemized quote on your actual volume and corridor, ",[136,9741,2781],{"href":1344},{"title":328,"searchDepth":329,"depth":329,"links":9743},[9744,9745,9746,9747,9748,9749,9750,9751],{"id":9357,"depth":329,"text":9358},{"id":9430,"depth":329,"text":9431},{"id":9468,"depth":329,"text":9469},{"id":9578,"depth":329,"text":9579},{"id":9635,"depth":329,"text":9636},{"id":9677,"depth":329,"text":9678},{"id":9716,"depth":329,"text":9717},{"id":9735,"depth":329,"text":9736},"2026-08-20","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.",[9755,9758,9761,9764,9767],{"q":9756,"a":9757},"Are stablecoin payments cheaper than credit card processing?","Usually, yes, especially for international sales. Card processing typically costs 1.5 to 3.5 percent per transaction, plus about 1 percent in cross-border fees and 1 to 3 percent in currency conversion on foreign cards, plus chargeback fees. A stablecoin payment costs a network fee of cents on low-cost chains, usually paid by the sender, plus a flat payout fee and a sub-percent FX spread if the merchant converts to local currency.",{"q":9759,"a":9760},"What fees does a merchant pay to accept stablecoins?","Three possible costs: the network or gas fee, which the sender usually pays and which is cents or less on Polygon, Base, Arbitrum, and Stellar; the FX spread when converting USDC or USDT into local currency; and a payout fee to deliver funds to a bank account over a local rail. Some providers also charge a platform subscription. BlindPay itemizes the spread and payout fee separately on every quote.",{"q":9762,"a":9763},"Do stablecoin payments have chargeback fees?","No. A confirmed stablecoin transfer is final, so there are no chargebacks, no chargeback fees, and no rolling reserves held against future disputes. Merchants still issue refunds when they choose to, by sending a new transfer back to the customer.",{"q":9765,"a":9766},"What hidden costs do card payments have for merchants?","Beyond the headline rate: cross-border assessments on foreign cards, currency conversion markups, chargeback fees typically between $15 and $100 per dispute, rolling reserves that hold back a share of revenue for months, PCI compliance costs, and the working capital cost of waiting one to three business days for every payout.",{"q":9768,"a":9769},"When are card payments still the better choice?","When your customers don't hold stablecoins and won't get them, when you need consumer credit at checkout, or when your sales are small, domestic, and low-risk. Many merchants keep cards for checkout and use stablecoins for the expensive part: cross-border settlement and payouts.",{},"---\ntitle: \"Stablecoin payment fees vs credit card processing fees: what merchants actually pay\"\nseoTitle: \"Stablecoin fees vs card processing fees for merchants\"\ndescription: \"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.\"\ndate: \"2026-08-20\"\ncategory: \"payments\"\nfaq:\n  - q: \"Are stablecoin payments cheaper than credit card processing?\"\n    a: \"Usually, yes, especially for international sales. Card processing typically costs 1.5 to 3.5 percent per transaction, plus about 1 percent in cross-border fees and 1 to 3 percent in currency conversion on foreign cards, plus chargeback fees. A stablecoin payment costs a network fee of cents on low-cost chains, usually paid by the sender, plus a flat payout fee and a sub-percent FX spread if the merchant converts to local currency.\"\n  - q: \"What fees does a merchant pay to accept stablecoins?\"\n    a: \"Three possible costs: the network or gas fee, which the sender usually pays and which is cents or less on Polygon, Base, Arbitrum, and Stellar; the FX spread when converting USDC or USDT into local currency; and a payout fee to deliver funds to a bank account over a local rail. Some providers also charge a platform subscription. BlindPay itemizes the spread and payout fee separately on every quote.\"\n  - q: \"Do stablecoin payments have chargeback fees?\"\n    a: \"No. A confirmed stablecoin transfer is final, so there are no chargebacks, no chargeback fees, and no rolling reserves held against future disputes. Merchants still issue refunds when they choose to, by sending a new transfer back to the customer.\"\n  - q: \"What hidden costs do card payments have for merchants?\"\n    a: \"Beyond the headline rate: cross-border assessments on foreign cards, currency conversion markups, chargeback fees typically between $15 and $100 per dispute, rolling reserves that hold back a share of revenue for months, PCI compliance costs, and the working capital cost of waiting one to three business days for every payout.\"\n  - q: \"When are card payments still the better choice?\"\n    a: \"When your customers don't hold stablecoins and won't get them, when you need consumer credit at checkout, or when your sales are small, domestic, and low-risk. Many merchants keep cards for checkout and use stablecoins for the expensive part: cross-border settlement and payouts.\"\n---\n\nCard processing typically costs merchants **1.5% to 3.5% per transaction**, and international sales add roughly **1% in cross-border fees and 1% to 3% in currency conversion**, before chargebacks. A stablecoin payment costs a **network fee of cents** on low-cost chains (usually paid by the sender), plus a **flat payout fee and a sub-percent FX spread** if you convert to local currency. For cross-border merchants, the gap is often several percentage points of revenue.\n\nThe headline rates only tell half the story, though. Both rails have costs that don't show up on the pricing page. This guide puts all of them on the table.\n\n## What does a merchant actually pay for a card transaction?\n\nA card fee is three fees wearing a trench coat:\n\n- **Interchange:** paid to the cardholder's issuing bank. The biggest piece, and it varies by card type, rewards tier, and whether the card was present.\n- **Network assessment:** paid to the card network.\n- **Processor or acquirer markup:** paid to whoever gave you the merchant account.\n\nBlended, that lands at roughly 1.5% to 3.5% for most merchants. Then the international extras:\n\n- **Cross-border fee:** around 1% when the card was issued in another country.\n- **Currency conversion:** 1% to 3% when the customer pays in a currency different from yours.\n\nAnd the ones nobody puts in a sales deck:\n\n- **Chargeback fees:** typically $15 to $100 per dispute, win or lose, on top of the lost sale.\n- **Rolling reserves:** higher-risk merchants often have 5% to 10% of revenue held back for months.\n- **Payout delay:** one to three business days of float on every sale. At scale, that's real working capital.\n- **PCI compliance:** audits, tooling, and scope reduction work.\n\n## What does a merchant pay for a stablecoin transaction?\n\nFewer layers, so fewer fees:\n\n- **Network fee (gas):** cents or less on Polygon, Base, Arbitrum, and Stellar. The sender usually pays it. Ethereum mainnet costs more, which is why payment flows mostly avoid it.\n- **FX spread:** only if you convert USDC or USDT into local currency. The difference between the mid-market rate and your conversion rate.\n- **Payout fee:** a flat or small fee to deliver funds to your bank over a local rail like Pix, SPEI, RTP, or SEPA.\n- **Platform fee:** some providers charge a subscription. BlindPay's plans are on the [pricing page](\u002Fpricing).\n\nNo interchange, because there's no issuing bank. No network assessment, because there's no card network. No chargebacks, because confirmed transfers are final.\n\n## Stablecoin vs card fees, side by side\n\n| Cost | Stablecoin (USDC\u002FUSDT) | Credit card |\n| --- | --- | --- |\n| **Base processing** | Network fee of cents, usually paid by the sender | Typically 1.5% to 3.5% |\n| **Cross-border** | None; the same transfer works in any country | Around 1% extra on foreign cards |\n| **Currency conversion** | Sub-percent FX spread, only if you convert | 1% to 3% markup |\n| **Payout to your bank** | Flat payout fee; minutes over instant local rails | Included, but 1 to 3 business days |\n| **Chargebacks** | None; transfers are final | $15 to $100 per dispute, plus the lost sale |\n| **Reserves** | None | 5% to 10% held for months on higher-risk accounts |\n| **Weekend settlement** | Yes, 24\u002F7 | No |\n\n## A worked example: $100,000 a month in international sales\n\nTake an online merchant selling $100,000 a month, mostly to customers outside its home country. These numbers are illustrative; your real rates depend on your processor, risk profile, and corridor.\n\n**Cards:**\n\n- Processing at 2.9%: $2,900\n- Cross-border at 1%: $1,000\n- Currency conversion at 1.5%: $1,500\n- 20 chargebacks at $25 each: $500, plus the value of the disputed goods\n- **Total: around $5,900 a month, or 5.9% of revenue,** before reserves and float\n\n**Stablecoins, for the share of customers who pay that way:**\n\n- Network fees: paid by the customer, cents each\n- Conversion to local currency at a sub-percent spread, plus a flat payout fee per settlement\n- No chargebacks, no reserves\n- **Total: typically a fraction of the card cost,** and settled the same day\n\nThat's why cross-border merchants are the ones moving first. A domestic merchant on a good card rate saves less. A merchant selling across borders, paying 5% to 6% all-in, saves most of it. BlindPay's own figure for replacing correspondent banking with stablecoin settlement and local rails is up to 90% lower transfer costs.\n\n## What are the hidden costs of stablecoin payments?\n\nBeing honest about the stablecoin side:\n\n- **Customer adoption.** Not every customer holds USDC or USDT. Stablecoins work best as an added option, or for B2B invoices and marketplace payouts where the counterparty already uses them.\n- **Refunds are manual.** No chargeback also means no automatic reversal. You send refunds yourself, so write the policy down.\n- **Wrong-network transfers.** A customer who sends USDC on a network you don't support creates a support ticket and a recovery process. Be explicit at checkout.\n- **Conversion spreads vary.** A provider quoting a low headline rate can make it back on the FX leg. Always ask for itemized quotes.\n- **Accounting setup.** Your finance team needs a clear process for recording stablecoin receipts and conversions. It's not hard, but it's new.\n\nNone of these is a dealbreaker. All of them are cheaper than a 2% cross-border markup on every sale, forever.\n\n## How do you compare quotes fairly?\n\nThe trap is comparing a blended card rate to a stablecoin headline rate. Hold these constant instead:\n\n1. **Same amount.** Fees compress with size differently on each rail.\n2. **Same day.** FX and spreads move daily.\n3. **Same corridor.** USDC to BRL over Pix prices differently from USDT to EUR over SEPA.\n4. **Itemized fees.** Spread, payout fee, and network fee as separate numbers.\n\nBlindPay quotes split the FX spread from the payout fee, so you can see what the conversion costs and what the delivery costs, and which one moved if a rate changes. You can check a public corridor like [USDC to BRL](\u002Fusdc-to-brl) for today's rate.\n\n## When should merchants keep cards?\n\nWhen the customer doesn't hold stablecoins and won't. When the purchase depends on consumer credit. When sales are small, domestic, and low-risk on a great rate.\n\nThe pattern we see work: keep cards at checkout, and use stablecoins for the expensive part, cross-border settlement and payouts. Our guide to [how merchants accept stablecoin payments](\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments) covers the receiving setup, and [stablecoin settlement explained](\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants) covers how funds get to your bank. If you're choosing between tokens, see [USDC vs USDT for payments](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments).\n\n## See your real numbers\n\nPricing pages don't pay invoices; quotes do. If you want an itemized quote on your actual volume and corridor, [talk to the BlindPay team](\u002Fcontact).\n",{"title":9330,"description":9753},"Stablecoin fees vs card processing fees for merchants","resources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees","KzAv4QdhCvBFej2ec8si5ibkuRkKi4AtH99lQjxJ6vs",{"id":9777,"title":9778,"authors":6,"body":9779,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":1873,"description":10031,"extension":342,"faq":10032,"howto":6,"isBlog":359,"isChangelog":359,"meta":10045,"navigation":362,"path":618,"pillar":359,"products":6,"rawbody":10046,"role":6,"seo":10047,"seoTitle":10048,"stem":10049,"thumbnail":6,"updated":10050,"__hash__":10051},"content\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide.md","Stablecoin payments explained: a guide for businesses",{"type":8,"value":9780,"toc":10019},[9781,9784,9791,9795,9803,9806,9810,9813,9840,9846,9850,9864,9871,9875,9878,9904,9910,9914,9917,9939,9942,9946,9949,9954,9958,9961,9974,9980,9984,9987,9990,9994,10003,10007,10015],[11,9782,9783],{},"Stablecoin payments are transfers of dollar-pegged digital tokens, most commonly USDC and USDT, that settle on a blockchain in seconds to minutes, at any hour, in any country. Businesses use them to move money across borders without correspondent banks, and modern providers convert either end to ordinary bank money, so neither the payer nor the recipient has to touch crypto.",[11,9785,9786,9787,9790],{},"The scale is no longer niche: circulating stablecoin supply exceeds 200 billion dollars according to public trackers such as ",[136,9788,1463],{"href":1461,"rel":9789},[414],", and annual on-chain settlement runs into the trillions. Visa, Stripe, and the largest banks all ship stablecoin products. This guide covers what stablecoin payments are, how they work end to end, what they cost, and how a business starts accepting or sending them.",[18,9792,9794],{"id":9793},"what-are-stablecoin-payments","What are stablecoin payments?",[11,9796,9797,9798,9802],{},"A stablecoin is a digital token engineered to hold a fixed value, almost always one US dollar, backed by reserves of cash and short-term US Treasuries (the full mechanics are in ",[136,9799,9801],{"href":9800},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin","what is a stablecoin","). A stablecoin payment is simply a transfer of those tokens between two parties, recorded on a public blockchain.",[11,9804,9805],{},"What makes it a payment method rather than a crypto trade is the fiat edge on each side. A provider converts the sender's local currency into stablecoins, moves them, and converts back to the recipient's local currency. The token in the middle provides the speed, reach, and programmability; the edges keep both parties in the banking system they already use.",[18,9807,9809],{"id":9808},"how-do-stablecoin-payments-work-end-to-end","How do stablecoin payments work end to end?",[11,9811,9812],{},"A typical cross-border business payment has three legs:",[145,9814,9815,9825,9831],{},[148,9816,9817,9820,9821,9824],{},[119,9818,9819],{},"Funding."," The business either holds stablecoins in its own wallet or funds the payment with fiat that the provider converts. ",[136,9822,9823],{"href":138},"Virtual accounts"," automate this: incoming bank transfers arrive as stablecoins.",[148,9826,9827,9830],{},[119,9828,9829],{},"Transfer."," The tokens move on a blockchain network such as Base, Polygon, or Solana. This leg settles in seconds to minutes and costs cents.",[148,9832,9833,9835,9836,9839],{},[119,9834,7359],{}," The provider converts the tokens at a quoted FX rate and delivers local currency over a domestic rail: ",[136,9837,3414],{"href":1854,"rel":9838},[414]," in Brazil, SPEI in Mexico, ACH or wire in the US.",[11,9841,9842,9843,9845],{},"The recipient sees a normal bank credit. The sender sees an API call and a webhook. Corridor pages like ",[136,9844,644],{"href":1757}," show the live quoted rate for the full path.",[18,9847,9849],{"id":9848},"how-do-businesses-accept-stablecoin-payments","How do businesses accept stablecoin payments?",[11,9851,9852,9853,9856,9857,9860,9861,9863],{},"Three patterns cover most cases. First, ",[119,9854,9855],{},"direct wallet acceptance",": the business publishes a wallet address and receives tokens, simplest but leaves custody and compliance to you. Second, ",[119,9858,9859],{},"hosted checkout via a gateway",": the customer pays from their wallet and the provider settles fiat or stablecoins to you, the right pattern for merchant-style flows. Third, ",[119,9862,632],{},": the payer sends a regular bank transfer to account details in your name, and it lands as USDC, which suits invoicing and B2B collections where the payer has no wallet at all.",[11,9865,9866,9867,9870],{},"Which pattern fits depends on who your payers are. Crypto-native customers can pay a wallet address today; mainstream businesses paying invoices need virtual accounts so nothing changes on their side; consumer checkout needs a hosted gateway. The provider types behind each pattern are compared in ",[136,9868,9869],{"href":771},"best stablecoin payment providers in 2026",", and most companies start with exactly one pattern rather than all three.",[18,9872,9874],{"id":9873},"what-do-businesses-actually-use-stablecoin-payments-for","What do businesses actually use stablecoin payments for?",[11,9876,9877],{},"The workloads that moved first share one shape: money leaving a strong-currency business and arriving in another country's banking system.",[171,9879,9880,9886,9892,9898],{},[148,9881,9882,9885],{},[119,9883,9884],{},"Contractor and payroll payouts."," A US or European company pays engineers and creators in Brazil, Mexico, or Argentina; funds arrive over Pix or SPEI in minutes instead of wire days, and each payout is one API call.",[148,9887,9888,9891],{},[119,9889,9890],{},"Marketplace and platform disbursements."," Platforms with sellers in many countries replace a patchwork of local banking partners with a single payout integration.",[148,9893,9894,9897],{},[119,9895,9896],{},"B2B supplier payments."," Importers settle invoices with exporters without prefunding accounts in the destination country.",[148,9899,9900,9903],{},[119,9901,9902],{},"Treasury."," Companies in volatile-currency markets hold working balances in digital dollars and convert to local currency on the day they spend, rather than the day they invoice.",[11,9905,9906,9907,9909],{},"If your use case matches one of these, the corridor pages, such as ",[136,9908,644],{"href":1757},", show what the specific route costs today.",[18,9911,9913],{"id":9912},"how-much-do-stablecoin-payments-cost","How much do stablecoin payments cost?",[11,9915,9916],{},"Three cost components, in descending order of importance:",[171,9918,9919,9925,9933],{},[148,9920,9921,9924],{},[119,9922,9923],{},"FX spread",": the gap between the mid-market rate and the rate you are quoted when converting to or from local currency. On non-USD corridors this is usually the largest cost, and the least visible.",[148,9926,9927,9930,9931,227],{},[119,9928,9929],{},"Provider fee",": a percentage per conversion, a flat fee per payout, or both. BlindPay publishes its numbers on the ",[136,9932,1712],{"href":307},[148,9934,9935,9938],{},[119,9936,9937],{},"Network fee",": cents per transfer on modern chains; rounding error at business volumes.",[11,9940,9941],{},"Compare providers on the amount delivered for a fixed input, not on the advertised fee. Against the traditional alternative, the difference is structural: an international wire routes through correspondent banks that each take fees over 1 to 5 business days, while a stablecoin path collapses that to one conversion step and minutes of settlement.",[18,9943,9945],{"id":9944},"how-do-stablecoin-payments-compare-with-wires-and-cards","How do stablecoin payments compare with wires and cards?",[11,9947,9948],{},"Against an international wire, the stablecoin path wins on speed (minutes versus 1 to 5 business days), availability (24\u002F7 versus banking hours), and fee structure (one conversion step versus a chain of correspondent bank deductions that can leave the recipient short an unpredictable amount). The wire keeps an edge in one place: universal acceptance at any bank in the world with no provider in the middle.",[11,9950,9951,9952,227],{},"Against cards, the comparison is really about direction. Cards excel at consumer pay-in, with familiar checkout and chargeback protection for the buyer. Stablecoins excel at business payout and B2B settlement, where card rails barely exist, and their finality becomes a feature: no dispute window, no rolling reserve. Many businesses end up with both: cards collect from consumers, stablecoins pay out to suppliers and contractors. The provider types that serve each direction are mapped in ",[136,9953,9869],{"href":771},[18,9955,9957],{"id":9956},"are-stablecoin-payments-legal-and-regulated","Are stablecoin payments legal and regulated?",[11,9959,9960],{},"Yes, in most major markets, and the rules matured fast. The US GENIUS Act established a federal framework for payment stablecoin issuers. Europe's MiCA regulation governs issuance and service providers across the EU. Brazil's central bank brought virtual asset service providers under supervision with Resolutions 519, 520, and 521, effective February 2026. Japan regulates fiat-backed stablecoins under its Payment Services Act.",[9962,9963,9964,9967],"blockquote",{},[11,9965,9966],{},"President Trump and Congress delivered the GENIUS Act, establishing a landmark framework and clear rules of the road for payment stablecoins, and Treasury is moving quickly to implement that framework.",[11,9968,9969,9970],{},"Scott Bessent, US Treasury Secretary, in the ",[136,9971,9973],{"href":1384,"rel":9972},[414],"Treasury press release on the GENIUS Act rulemaking",[11,9975,9976,9977,227],{},"For a business, the practical consequence is that regulated providers carry the licensing and run KYC, KYB, and sanctions screening before money moves. Expect to verify your entity once at onboarding and to provide accurate recipient details per payment. The per-regime detail lives in our ",[136,9978,9979],{"href":1035},"stablecoin regulation tracker",[18,9981,9983],{"id":9982},"what-are-the-benefits-and-the-trade-offs","What are the benefits and the trade-offs?",[11,9985,9986],{},"The benefits: settlement in minutes instead of days, 24\u002F7 availability including weekends, reach into 100+ countries without local entities, finality with no chargebacks, and programmability, since every payment is an API call that can be automated. Treasury teams also gain a dollar-denominated working balance in markets with volatile local currencies.",[11,9988,9989],{},"The trade-offs are real too. Finality means errors cannot be clawed back, so recipient verification matters more than with cards. FX spread quality varies widely between providers. Accounting and tax treatment of token balances still needs a competent adviser in some jurisdictions. And acceptance is business-to-business first: paying a US landlord in stablecoins remains unusual, while paying a contractor in São Paulo is now routine.",[18,9991,9993],{"id":9992},"how-does-blindpay-handle-stablecoin-payments","How does BlindPay handle stablecoin payments?",[11,9995,9996,9997,10000,10001,227],{},"BlindPay is a ",[136,9998,9999],{"href":299},"stablecoin API for global payments",": one integration that turns USDC or USDT into local currency over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO wires with UETR tracking and MT103 confirmations), and turns incoming bank transfers into stablecoins through virtual accounts. FX is quoted before you commit, compliance checks run inside the flow, and coverage is deepest across the Americas. The provider field, including where competitors fit better, is compared honestly in ",[136,10002,1825],{"href":766},[18,10004,10006],{"id":10005},"how-do-you-get-started","How do you get started?",[11,10008,10009,10010,1341,10012,10014],{},"Start with one corridor and one direction. Pick the country pair with the most pain, request delivered-amount quotes from two or three providers, run a small live payment, and compare what actually arrived. Check corridor coverage on the ",[136,10011,3183],{"href":1335},[136,10013,1821],{"href":1344}," to run that first test payment against a live quote.",[11,10016,10017],{},[324,10018,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":10020},[10021,10022,10023,10024,10025,10026,10027,10028,10029,10030],{"id":9793,"depth":329,"text":9794},{"id":9808,"depth":329,"text":9809},{"id":9848,"depth":329,"text":9849},{"id":9873,"depth":329,"text":9874},{"id":9912,"depth":329,"text":9913},{"id":9944,"depth":329,"text":9945},{"id":9956,"depth":329,"text":9957},{"id":9982,"depth":329,"text":9983},{"id":9992,"depth":329,"text":9993},{"id":10005,"depth":329,"text":10006},"Stablecoin payments move dollar-pegged tokens between parties and settle in minutes, 24\u002F7. How they work, what they cost, and how businesses use them.",[10033,10036,10039,10042],{"q":10034,"a":10035},"What is a stablecoin payment?","A stablecoin payment is a transfer of a dollar-pegged digital token, such as USDC or USDT, from one party to another over a blockchain. It settles in seconds to minutes at any hour, and providers can convert either end to regular bank money.",{"q":10037,"a":10038},"Do customers need a crypto wallet to make stablecoin payments?","No. With virtual accounts and hosted checkout flows, the payer sends a normal bank transfer and the provider converts it to stablecoins behind the scenes. Wallets are only needed when a party wants to hold the tokens directly.",{"q":10040,"a":10041},"How fast are stablecoin payments?","The blockchain transfer itself settles in seconds to minutes. End to end, a cross-border payment that includes conversion to local currency usually completes in minutes when the destination rail is instant, such as Pix in Brazil, or within a business day over ACH.",{"q":10043,"a":10044},"Are stablecoin payments reversible?","On-chain transfers are final, with no chargeback mechanism. Businesses get finality and lower dispute costs, and in return they need accurate recipient verification before sending, which is why compliance checks run before money moves.",{"author":361},"---\ntitle: \"Stablecoin payments explained: a guide for businesses\"\nseoTitle: \"Stablecoin payments explained for businesses\"\ndescription: \"Stablecoin payments move dollar-pegged tokens between parties and settle in minutes, 24\u002F7. How they work, what they cost, and how businesses use them.\"\ndate: \"2026-08-15\"\nupdated: \"2026-09-01\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a stablecoin payment?\"\n    a: \"A stablecoin payment is a transfer of a dollar-pegged digital token, such as USDC or USDT, from one party to another over a blockchain. It settles in seconds to minutes at any hour, and providers can convert either end to regular bank money.\"\n  - q: \"Do customers need a crypto wallet to make stablecoin payments?\"\n    a: \"No. With virtual accounts and hosted checkout flows, the payer sends a normal bank transfer and the provider converts it to stablecoins behind the scenes. Wallets are only needed when a party wants to hold the tokens directly.\"\n  - q: \"How fast are stablecoin payments?\"\n    a: \"The blockchain transfer itself settles in seconds to minutes. End to end, a cross-border payment that includes conversion to local currency usually completes in minutes when the destination rail is instant, such as Pix in Brazil, or within a business day over ACH.\"\n  - q: \"Are stablecoin payments reversible?\"\n    a: \"On-chain transfers are final, with no chargeback mechanism. Businesses get finality and lower dispute costs, and in return they need accurate recipient verification before sending, which is why compliance checks run before money moves.\"\n---\n\nStablecoin payments are transfers of dollar-pegged digital tokens, most commonly USDC and USDT, that settle on a blockchain in seconds to minutes, at any hour, in any country. Businesses use them to move money across borders without correspondent banks, and modern providers convert either end to ordinary bank money, so neither the payer nor the recipient has to touch crypto.\n\nThe scale is no longer niche: circulating stablecoin supply exceeds 200 billion dollars according to public trackers such as [DeFiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins), and annual on-chain settlement runs into the trillions. Visa, Stripe, and the largest banks all ship stablecoin products. This guide covers what stablecoin payments are, how they work end to end, what they cost, and how a business starts accepting or sending them.\n\n## What are stablecoin payments?\n\nA stablecoin is a digital token engineered to hold a fixed value, almost always one US dollar, backed by reserves of cash and short-term US Treasuries (the full mechanics are in [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin)). A stablecoin payment is simply a transfer of those tokens between two parties, recorded on a public blockchain.\n\nWhat makes it a payment method rather than a crypto trade is the fiat edge on each side. A provider converts the sender's local currency into stablecoins, moves them, and converts back to the recipient's local currency. The token in the middle provides the speed, reach, and programmability; the edges keep both parties in the banking system they already use.\n\n## How do stablecoin payments work end to end?\n\nA typical cross-border business payment has three legs:\n\n1. **Funding.** The business either holds stablecoins in its own wallet or funds the payment with fiat that the provider converts. [Virtual accounts](\u002Fvirtual-accounts) automate this: incoming bank transfers arrive as stablecoins.\n2. **Transfer.** The tokens move on a blockchain network such as Base, Polygon, or Solana. This leg settles in seconds to minutes and costs cents.\n3. **Payout.** The provider converts the tokens at a quoted FX rate and delivers local currency over a domestic rail: [Pix](https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en) in Brazil, SPEI in Mexico, ACH or wire in the US.\n\nThe recipient sees a normal bank credit. The sender sees an API call and a webhook. Corridor pages like [USDC to BRL](\u002Fusdc-to-brl) show the live quoted rate for the full path.\n\n## How do businesses accept stablecoin payments?\n\nThree patterns cover most cases. First, **direct wallet acceptance**: the business publishes a wallet address and receives tokens, simplest but leaves custody and compliance to you. Second, **hosted checkout via a gateway**: the customer pays from their wallet and the provider settles fiat or stablecoins to you, the right pattern for merchant-style flows. Third, **virtual accounts**: the payer sends a regular bank transfer to account details in your name, and it lands as USDC, which suits invoicing and B2B collections where the payer has no wallet at all.\n\nWhich pattern fits depends on who your payers are. Crypto-native customers can pay a wallet address today; mainstream businesses paying invoices need virtual accounts so nothing changes on their side; consumer checkout needs a hosted gateway. The provider types behind each pattern are compared in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026), and most companies start with exactly one pattern rather than all three.\n\n## What do businesses actually use stablecoin payments for?\n\nThe workloads that moved first share one shape: money leaving a strong-currency business and arriving in another country's banking system.\n\n- **Contractor and payroll payouts.** A US or European company pays engineers and creators in Brazil, Mexico, or Argentina; funds arrive over Pix or SPEI in minutes instead of wire days, and each payout is one API call.\n- **Marketplace and platform disbursements.** Platforms with sellers in many countries replace a patchwork of local banking partners with a single payout integration.\n- **B2B supplier payments.** Importers settle invoices with exporters without prefunding accounts in the destination country.\n- **Treasury.** Companies in volatile-currency markets hold working balances in digital dollars and convert to local currency on the day they spend, rather than the day they invoice.\n\nIf your use case matches one of these, the corridor pages, such as [USDC to BRL](\u002Fusdc-to-brl), show what the specific route costs today.\n\n## How much do stablecoin payments cost?\n\nThree cost components, in descending order of importance:\n\n- **FX spread**: the gap between the mid-market rate and the rate you are quoted when converting to or from local currency. On non-USD corridors this is usually the largest cost, and the least visible.\n- **Provider fee**: a percentage per conversion, a flat fee per payout, or both. BlindPay publishes its numbers on the [pricing page](\u002Fpricing).\n- **Network fee**: cents per transfer on modern chains; rounding error at business volumes.\n\nCompare providers on the amount delivered for a fixed input, not on the advertised fee. Against the traditional alternative, the difference is structural: an international wire routes through correspondent banks that each take fees over 1 to 5 business days, while a stablecoin path collapses that to one conversion step and minutes of settlement.\n\n## How do stablecoin payments compare with wires and cards?\n\nAgainst an international wire, the stablecoin path wins on speed (minutes versus 1 to 5 business days), availability (24\u002F7 versus banking hours), and fee structure (one conversion step versus a chain of correspondent bank deductions that can leave the recipient short an unpredictable amount). The wire keeps an edge in one place: universal acceptance at any bank in the world with no provider in the middle.\n\nAgainst cards, the comparison is really about direction. Cards excel at consumer pay-in, with familiar checkout and chargeback protection for the buyer. Stablecoins excel at business payout and B2B settlement, where card rails barely exist, and their finality becomes a feature: no dispute window, no rolling reserve. Many businesses end up with both: cards collect from consumers, stablecoins pay out to suppliers and contractors. The provider types that serve each direction are mapped in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n\n## Are stablecoin payments legal and regulated?\n\nYes, in most major markets, and the rules matured fast. The US GENIUS Act established a federal framework for payment stablecoin issuers. Europe's MiCA regulation governs issuance and service providers across the EU. Brazil's central bank brought virtual asset service providers under supervision with Resolutions 519, 520, and 521, effective February 2026. Japan regulates fiat-backed stablecoins under its Payment Services Act.\n\n> President Trump and Congress delivered the GENIUS Act, establishing a landmark framework and clear rules of the road for payment stablecoins, and Treasury is moving quickly to implement that framework.\n>\n> Scott Bessent, US Treasury Secretary, in the [Treasury press release on the GENIUS Act rulemaking](https:\u002F\u002Fhome.treasury.gov\u002Fnews\u002Fpress-releases\u002Fsb0605)\n\nFor a business, the practical consequence is that regulated providers carry the licensing and run KYC, KYB, and sanctions screening before money moves. Expect to verify your entity once at onboarding and to provide accurate recipient details per payment. The per-regime detail lives in our [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026).\n\n## What are the benefits and the trade-offs?\n\nThe benefits: settlement in minutes instead of days, 24\u002F7 availability including weekends, reach into 100+ countries without local entities, finality with no chargebacks, and programmability, since every payment is an API call that can be automated. Treasury teams also gain a dollar-denominated working balance in markets with volatile local currencies.\n\nThe trade-offs are real too. Finality means errors cannot be clawed back, so recipient verification matters more than with cards. FX spread quality varies widely between providers. Accounting and tax treatment of token balances still needs a competent adviser in some jurisdictions. And acceptance is business-to-business first: paying a US landlord in stablecoins remains unusual, while paying a contractor in São Paulo is now routine.\n\n## How does BlindPay handle stablecoin payments?\n\nBlindPay is a [stablecoin API for global payments](\u002Fglobal-payments): one integration that turns USDC or USDT into local currency over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO wires with UETR tracking and MT103 confirmations), and turns incoming bank transfers into stablecoins through virtual accounts. FX is quoted before you commit, compliance checks run inside the flow, and coverage is deepest across the Americas. The provider field, including where competitors fit better, is compared honestly in [best stablecoin APIs in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026).\n\n## How do you get started?\n\nStart with one corridor and one direction. Pick the country pair with the most pain, request delivered-amount quotes from two or three providers, run a small live payment, and compare what actually arrived. Check corridor coverage on the [coverage page](\u002Fcoverage), or [talk to us](\u002Fcontact) to run that first test payment against a live quote.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":9778,"description":10031},"Stablecoin payments explained for businesses","resources\u002Fmore\u002Fstablecoin-payments-guide","2026-09-01","00UOXCpvRdukVGDZBnOm3OXD29rga0Tq_1WckXqEGEA",{"id":10053,"title":10054,"authors":6,"body":10055,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":10464,"description":10465,"extension":342,"faq":10466,"howto":6,"isBlog":359,"isChangelog":359,"meta":10488,"navigation":362,"path":1221,"pillar":359,"products":6,"rawbody":10489,"role":6,"seo":10490,"seoTitle":10491,"stem":10492,"thumbnail":6,"updated":6,"__hash__":10493},"content\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors.md","Stablecoin payroll for LATAM contractors: how it actually works in 2026",{"type":8,"value":10056,"toc":10456},[10057,10060,10063,10066,10070,10077,10080,10083,10089,10101,10107,10110,10114,10117,10124,10127,10133,10137,10143,10181,10184,10195,10199,10202,10208,10214,10220,10231,10234,10238,10245,10361,10364,10370,10379,10385,10391,10397,10401,10404,10418,10424,10434,10440,10443,10452],[11,10058,10059],{},"Stablecoin payroll is a way for US companies to pay contractors in Latin America using a dollar-pegged token like USDC or USDT as the settlement layer, so the payment lands in minutes at a cost known before it is sent, instead of a wire that takes 3 to 5 business days and arrives short. The contractor receives local currency in their bank account, or stablecoins if they prefer to hold dollars. In 2026 it has become the default for companies paying teams in Argentina, Brazil, Mexico, and Colombia.",[11,10061,10062],{},"This guide is for a US company paying independent contractors in those countries: the finance or HR lead running a monthly cycle of 5 to 50 payments, the controller who needs to know the tax treatment before signing off, and the contractor on the other end who is tired of losing money to bank fees and inflation.",[11,10064,10065],{},"Here is the normal experience it replaces. A startup with twelve contractors in Brazil, four in Mexico, and two in Colombia sends eighteen international wires on the last business day of the month. Three bounce for formatting reasons, two arrive short because an intermediary bank took a cut nobody could predict, and the Brazilian contractors get their reais on Wednesday of the following week, minus a 3 percent FX haircut from the receiving bank. That is not the bad case. That is the normal case.",[18,10067,10069],{"id":10068},"what-is-stablecoin-payroll-and-why-latam-contractors-prefer-it","What is stablecoin payroll and why LATAM contractors prefer it",[11,10071,10072,10073,10076],{},"Stablecoin payroll uses a ",[136,10074,10075],{"href":7002},"stablecoin",", a token designed to hold a 1:1 peg to the US dollar, to move value from the company to the contractor. What the contractor gets at the end is their choice. Most want local currency in their bank. A minority, especially in Argentina, want to hold dollars.",[11,10078,10079],{},"That second part is the one most guides get wrong. Stablecoin payroll does not mean contractors have to open a crypto wallet. A designer in São Paulo wants reais in her Nubank account. A developer in Guadalajara wants pesos over SPEI. The stablecoin moves the value across the border. The local rail puts it in their hands. The flow is sometimes called the stablecoin sandwich: fiat in, stablecoin across, fiat out.",[11,10081,10082],{},"Contractors prefer it for three reasons.",[11,10084,10085,10088],{},[119,10086,10087],{},"Speed."," A wire takes 3 to 5 business days, assuming no compliance hold at an intermediary bank. A stablecoin payout lands in minutes. For a freelancer juggling several clients, getting paid today instead of next week is the difference between paying rent on time and not.",[11,10090,10091,10094,10095,10100],{},[119,10092,10093],{},"Fee erosion."," On a $3,000 wire, the contractor commonly loses $85 to $170 to sending fees, intermediary deductions, and the receiving bank's exchange rate. On a stablecoin payout the amount quoted is the amount received. In the LATAM stablecoin payments map that BlindPay co-published with Bitso Business, Utila, and Minteo in 2025, mass payouts to freelancers in Mexico and Brazil showed an ",[136,10096,10099],{"href":10097,"rel":10098},"https:\u002F\u002Fbusiness.bitso.com\u002Fen\u002Fblog\u002Fthe-first-stablecoin-payments-map-in-latam",[414],"80 percent cut in settlement time"," compared with the wires they replaced.",[11,10102,10103,10106],{},[119,10104,10105],{},"Currency protection."," A contractor in Argentina paid in pesos watches the value fall within days. Paid in USDC to a wallet, they hold dollars and convert when they choose. For contractors in Brazil, Mexico, and Colombia the local currency payout is usually what they want, but the option to hold dollars is a real benefit for some.",[11,10108,10109],{},"For the company, the win is operational. One provider, one API or dashboard, one payment method that works the same in four countries, instead of four sets of banking requirements and four pre-funded balances.",[18,10111,10113],{"id":10112},"usdc-vs-usdt-choosing-the-right-stablecoin-for-latam-payments","USDC vs USDT: choosing the right stablecoin for LATAM payments",[11,10115,10116],{},"For most US companies USDC is the right default, and the choice only matters for contractors who want to hold stablecoins rather than receive local currency.",[11,10118,10119,10123],{},[136,10120,10122],{"href":10121},"\u002Fresources\u002Fmore\u002Fwhat-is-usdc","USDC"," is issued by Circle, publishes monthly reserve attestations, and is positioned for licensing under the GENIUS Act. It is the easier asset to justify to a US finance or legal team, and it is what most US companies already hold.",[11,10125,10126],{},"USDT, issued by Tether, has deeper liquidity in many LATAM off-ramps and local exchanges. On some corridors that means a slightly tighter spread when converting to local currency, and contractors in Argentina who plan to sell for pesos on a local exchange often find USDT easier to move.",[11,10128,10129,10130,10132],{},"If contractors are paid in local currency, they never see which token settled the payment, so the company should pick the one its compliance team prefers and let the provider handle conversion. If contractors are paid in stablecoins to a wallet, let each contractor choose. A provider that supports both, like BlindPay, removes the decision from the operations team. The ",[136,10131,1071],{"href":1070}," covers reserves, liquidity, and regulatory posture in detail.",[18,10134,10136],{"id":10135},"how-stablecoin-payroll-works-step-by-step","How stablecoin payroll works step-by-step",[11,10138,10139,10140,10142],{},"A stablecoin payroll run has five steps. With a payout platform like ",[136,10141,300],{"href":299}," the company's team touches three of them; the platform handles conversion, compliance, and delivery.",[145,10144,10145,10151,10160,10166,10175],{},[148,10146,10147,10150],{},[119,10148,10149],{},"Onboard each contractor once."," The contractor submits their name, tax ID (CPF in Brazil, RFC in Mexico, cedula in Colombia, CUIT in Argentina), and a bank account. Identity verification and receiving-account checks run inside the flow. A contractor who wants to hold dollars submits a wallet address instead. This takes minutes and happens one time.",[148,10152,10153,10156,10157,10159],{},[119,10154,10155],{},"Fund the run."," Send USDC or USDT from the company's treasury wallet, or send dollars by ACH or wire to a ",[136,10158,7283],{"href":138}," that converts them to stablecoins automatically. No pre-funding in a Brazilian or Mexican account.",[148,10161,10162,10165],{},[119,10163,10164],{},"Request a quote per payout."," The platform returns the FX rate, the spread, and the payout fee as separate numbers. The exact amount landing in the contractor's account is known before the company commits.",[148,10167,10168,10171,10172,7326],{},[119,10169,10170],{},"Execute."," The stablecoin moves on-chain, converts to local currency, and pays out over Pix in Brazil, SPEI in Mexico, PSE in Colombia, or Transfers 3.0 to a CBU or CVU in Argentina. A wallet payout skips the conversion and delivers USDC or USDT directly. Since August 2026, BlindPay also moves USDC across networks in a single transfer, so the company's treasury chain and the payout chain no longer have to match; the ",[136,10173,10174],{"href":7324},"cross-chain USDC changelog",[148,10176,10177,10180],{},[119,10178,10179],{},"Reconcile."," Each payout has an ID, a status, a transaction hash, and a webhook. The finance tool receives the event. The contractor receives the money.",[11,10182,10183],{},"End to end, a Brazilian payout over Pix usually completes in minutes. Same for SPEI in Mexico, which also runs 24\u002F7. Colombia over PSE follows bank processing windows and is usually minutes, sometimes longer. Argentina over Transfers 3.0 is same-day. A Friday evening run does not become a Tuesday deposit.",[11,10185,10186,10187,10189,10190,10194],{},"One property to understand before the first run: the on-chain transfer is final once confirmed. That is why receiver verification happens before the money moves, not after. ",[136,10188,7314],{"href":734}," explains what can be recalled on each leg. A contractor who received USDC and later wants dollars in a US account can use a ",[136,10191,10193],{"href":10192},"\u002Fusdc-to-usd","USDC to USD"," off-ramp.",[18,10196,10198],{"id":10197},"compliance-and-tax-reporting-for-us-companies","Compliance and tax reporting for US companies",[11,10200,10201],{},"Stablecoin payroll does not change what a US company owes or reports. It changes the settlement mechanism. Three rules cover most cases, and a tax advisor should confirm the specifics for the company's situation.",[11,10203,10204,10207],{},[119,10205,10206],{},"Non-US contractors performing services outside the US."," This is the typical LATAM contractor. Collect Form W-8BEN (or W-8BEN-E if the contractor invoices through a company) and keep it on file. No Form 1099-NEC is issued, and no US withholding applies, because the income is foreign-source services income. The W-8BEN is not filed with the IRS; it supports why no 1099 was issued if the company is audited.",[11,10209,10210,10213],{},[119,10211,10212],{},"US persons working abroad."," A US citizen or resident living in Mexico and invoicing as a contractor is reported on Form 1099-NEC like any domestic contractor. For payments made on or after January 1, 2026, the reporting threshold rose from $600 to $2,000 under the One Big Beautiful Bill Act, indexed for inflation from 2027. The reportable amount is the fair market value at the time of payment, which for a dollar-pegged stablecoin is the dollar amount.",[11,10215,10216,10219],{},[119,10217,10218],{},"Records."," Keep, per payment: date, contractor, amount, currency delivered, FX rate and fees, payout ID, and the on-chain transaction hash. A payout platform should provide this by API and export. The transaction hash is a public, timestamped record that a wire cannot match, and auditors have started to expect it.",[11,10221,10222,10223,10225,10226,7407,10228,10230],{},"On the platform side, the provider must be registered with FinCEN as a Money Services Business and hold or be exempt from state money transmitter licenses; BlindPay publishes its status on the ",[136,10224,1046],{"href":815},". On the receiving side, Brazil licenses virtual asset service providers under Central Bank Resolutions 519 through 521, in force since February 2, 2026, and Resolution 561 on eFX in May 2026 does not affect the stablecoin plus local rails model, as ",[136,10227,7406],{"href":7405},[136,10229,1036],{"href":1035}," keeps the country-by-country view current.",[11,10232,10233],{},"Contractors owe income tax in their own country on what they receive, and converting stablecoins to local currency may be a taxable event locally. The company is not responsible for the contractor's filing, but clear per-payment documentation helps them meet it.",[18,10235,10237],{"id":10236},"comparing-stablecoin-payroll-platforms-for-global-payments","Comparing stablecoin payroll platforms for global payments",[11,10239,10240,10241,10244],{},"Platforms that pay LATAM contractors with stablecoins fall into three groups: payout APIs that deliver local currency, contractor management platforms that added a stablecoin option, and exchange or wallet products that deliver tokens only. The table compares what a company evaluating them for a 5 to 50 contractor run should check. Capabilities change often; confirm current details on each provider's site. The ",[136,10242,10243],{"href":771},"provider comparison"," covers the wider field.",[39,10246,10247,10271],{},[42,10248,10249],{},[45,10250,10251,10254,10257,10260,10263,10265,10268],{},[48,10252,10253],{},"Platform type",[48,10255,10256],{},"Example",[48,10258,10259],{},"Contractor receives",[48,10261,10262],{},"LATAM rails",[48,10264,2837],{},[48,10266,10267],{},"Quote",[48,10269,10270],{},"Access",[61,10272,10273,10294,10317,10338],{},[45,10274,10275,10278,10280,10283,10286,10288,10291],{},[66,10276,10277],{},"Stablecoin payout API",[66,10279,300],{},[66,10281,10282],{},"Local currency or USDC\u002FUSDT",[66,10284,10285],{},"Pix, SPEI, PSE, Argentine transfers, plus ACH and SWIFT (POBO\u002FCOBO)",[66,10287,9561],{},[66,10289,10290],{},"Itemized: rate, spread, fee",[66,10292,10293],{},"API, dashboard, MCP for AI agents",[45,10295,10296,10299,10302,10305,10308,10311,10314],{},[66,10297,10298],{},"Contractor management platform with stablecoin option",[66,10300,10301],{},"Deel, Toku",[66,10303,10304],{},"Local currency or stablecoin, depending on plan",[66,10306,10307],{},"Via partner rails",[66,10309,10310],{},"Often required",[66,10312,10313],{},"Blended",[66,10315,10316],{},"Dashboard, some APIs",[45,10318,10319,10322,10324,10327,10329,10332,10335],{},[66,10320,10321],{},"Stripe-ecosystem stablecoin",[66,10323,833],{},[66,10325,10326],{},"USDC or USD\u002FEUR",[66,10328,839],{},[66,10330,10331],{},"Balance-based",[66,10333,10334],{},"Percentage",[66,10336,10337],{},"API",[45,10339,10340,10343,10346,10349,10352,10355,10358],{},[66,10341,10342],{},"Exchange or wallet payout",[66,10344,10345],{},"Bitso Business, local exchanges",[66,10347,10348],{},"Tokens or local currency at the exchange",[66,10350,10351],{},"Country-specific",[66,10353,10354],{},"Funds on exchange",[66,10356,10357],{},"Exchange rate",[66,10359,10360],{},"Dashboard, API",[11,10362,10363],{},"Five variables decide the choice.",[11,10365,10366,10369],{},[119,10367,10368],{},"What the contractor receives."," If most contractors want local currency, a payout API that delivers over Pix, SPEI, PSE, and Argentine transfers is the only category that does it in one integration. If most want to hold dollars, an exchange or wallet payout works, but the contractor then handles conversion themselves.",[11,10371,10372,10375,10376,10378],{},[119,10373,10374],{},"Fee structure."," Flat per payout, percentage, or both. For frequent smaller payments a low flat fee matters most; for larger payments the spread dominates. Compare on the company's actual payment pattern, and insist on an itemized quote. The ",[136,10377,4238],{"href":4237}," shows why a blended rate hides the real number.",[11,10380,10381,10384],{},[119,10382,10383],{},"Pre-funding."," Platforms that require a BRL balance in Brazil and an MXN balance in Mexico before payouts clear are tying up working capital that never shows up as a fee. Ask directly.",[11,10386,10387,10390],{},[119,10388,10389],{},"Compliance built in."," Receiver KYC, account verification, and sanctions screening should run inside the flow. The platform should publish its licenses.",[11,10392,10393,10396],{},[119,10394,10395],{},"API vs dashboard."," A team of two running monthly payroll wants a dashboard. A company with a payroll system wants an API and webhooks. The best platforms offer both.",[18,10398,10400],{"id":10399},"get-started-with-stablecoin-payments-for-your-latam-team","Get started with stablecoin payments for your LATAM team",[11,10402,10403],{},"Four steps take a company from wires to a working stablecoin payroll in one or two cycles.",[11,10405,10406,10409,10410,10412,10413,1337,10415,10417],{},[119,10407,10408],{},"Pick the platform against the five variables above."," For 5 to 50 contractors across Brazil, Mexico, Colombia, and Argentina, a payout API that delivers local currency with an itemized quote and no pre-funding covers the common case. BlindPay's ",[136,10411,1261],{"href":299}," product is built for that flow, with ",[136,10414,1340],{"href":307},[136,10416,1336],{"href":1335}," published.",[11,10419,10420,10423],{},[119,10421,10422],{},"Ask contractors what they want."," Local currency to a bank account, or stablecoins to a wallet. Most choose the bank account. Do not push wallets on people who did not ask for one; that moves the friction to them.",[11,10425,10426,10429,10430,10433],{},[119,10427,10428],{},"Run one cycle in parallel."," Pay one or two contractors over stablecoins and the rest by wire. Compare what landed, when, and what it cost. Test the failure paths too: a rejected receiving account, a compliance hold. ",[136,10431,10432],{"href":754},"Sandbox does not exercise those","; a small live pilot does.",[11,10435,10436,10439],{},[119,10437,10438],{},"Document from day one."," W-8BEN on file per foreign contractor, per-payment records with transaction hash, and a reconciliation step wired to the webhook. Habits set on the first run hold as the contractor base grows.",[11,10441,10442],{},"The shift is smaller than it looks. A company already paying international contractors has the hard parts done: the relationships, the schedule, the invoices. Stablecoin payroll swaps the settlement mechanism for one that is faster, cheaper, and easier to audit.",[11,10444,10445,1341,10448,10451],{},[136,10446,7445],{"href":648,"rel":10447},[414],[136,10449,1345],{"href":654,"rel":10450},[414]," with the countries and monthly volume.",[11,10453,10454],{},[324,10455,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":10457},[10458,10459,10460,10461,10462,10463],{"id":10068,"depth":329,"text":10069},{"id":10112,"depth":329,"text":10113},{"id":10135,"depth":329,"text":10136},{"id":10197,"depth":329,"text":10198},{"id":10236,"depth":329,"text":10237},{"id":10399,"depth":329,"text":10400},"2026-09-04","How US companies pay contractors in Argentina, Brazil, Mexico, and Colombia with stablecoins in 2026: USDC vs USDT, payout flow, and tax reporting.",[10467,10470,10473,10476,10479,10482,10485],{"q":10468,"a":10469},"What is stablecoin payroll and how does it work for LATAM contractors?","Stablecoin payroll is paying contractors with a dollar-pegged token like USDC or USDT as the settlement layer instead of an international wire. The company funds the run in dollars or stablecoins, a payout platform converts each payment at a quoted rate, and the contractor receives either local currency in their bank account over Pix, SPEI, PSE, or an Argentine transfer, or stablecoins in a wallet if they prefer to hold dollars. Settlement takes minutes instead of 3 to 5 business days.",{"q":10471,"a":10472},"Is it legal for US companies to pay contractors in stablecoins?","Yes. US companies may pay contractors in stablecoins through a provider registered with FinCEN as a Money Services Business. Stablecoin issuers are regulated under the GENIUS Act, signed in July 2025, with Treasury's implementing rules out for comment through October 19, 2026. On the receiving side, Brazil licenses virtual asset providers under Central Bank Resolutions 519 through 521, and Mexico, Colombia, and Argentina permit conversion to local currency through licensed providers. The payment is reportable like any other contractor payment.",{"q":10474,"a":10475},"How do stablecoin payments compare to ACH payments, wire transfers, and platforms like Wise or Stripe for international payroll?","ACH is US-only, so it cannot pay a contractor in Brazil. An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread and lands in 2 to 5 business days. Wise and Stripe-based payout tools reach Latin America with lower spreads than banks but still settle over local rails on their schedules and often require pre-funded balances. Stablecoin payroll settles in minutes, 24\u002F7, at a rate quoted before you send, with no pre-funding.",{"q":10477,"a":10478},"How much do contractors actually receive after fees when paid in USDC versus traditional bank transfers?","On a $3,000 payment by international wire, the contractor commonly receives $2,830 to $2,915 after sending fees, intermediary deductions, and the receiving bank's FX spread. Through a stablecoin payout with an itemized quote, the contractor receives the quoted amount, and the total cost is usually a small flat fee plus a sub-percent spread. Over a year of monthly payments the difference is typically several hundred dollars per contractor.",{"q":10480,"a":10481},"How fast are stablecoin payments compared to real-time payments and standard international wire transfers?","The stablecoin transfer settles in seconds, conversion takes a few minutes, and Pix in Brazil and SPEI in Mexico run 24\u002F7, so a payout lands in minutes at any hour. That matches domestic real-time payments like RTP or FedNow in speed, but works across borders. An international wire takes 2 to 5 business days and does not move on weekends. Colombia over PSE and Argentina over Transfers 3.0 are same-day.",{"q":10483,"a":10484},"What do LATAM contractors need to set up to receive stablecoin payroll payments?","For local currency: their name, tax ID (CPF in Brazil, RFC in Mexico, cedula in Colombia, CUIT in Argentina), and a bank account, entered once during onboarding. No wallet, no exchange account, no seed phrase. Contractors who want to hold dollars instead provide a wallet address that supports USDC or USDT. Onboarding with identity verification takes minutes.",{"q":10486,"a":10487},"How do companies handle tax reporting and compliance when using stablecoin payroll for international contractors?","The same way as for any contractor payment. For a non-US contractor performing services outside the US, collect Form W-8BEN (or W-8BEN-E for a company) and keep it on file; no Form 1099-NEC is issued and no withholding applies to foreign-source services income. For a US person working abroad, Form 1099-NEC applies at the new $2,000 threshold for tax year 2026. Keep the payout ID, date, amount, FX rate, fees, and transaction hash per payment. Confirm the specifics with a tax advisor.",{"author":361},"---\ntitle: \"Stablecoin payroll for LATAM contractors: how it actually works in 2026\"\nseoTitle: \"Stablecoin payroll for LATAM contractors in 2026\"\ndescription: \"How US companies pay contractors in Argentina, Brazil, Mexico, and Colombia with stablecoins in 2026: USDC vs USDT, payout flow, and tax reporting.\"\ndate: \"2026-09-04\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is stablecoin payroll and how does it work for LATAM contractors?\"\n    a: \"Stablecoin payroll is paying contractors with a dollar-pegged token like USDC or USDT as the settlement layer instead of an international wire. The company funds the run in dollars or stablecoins, a payout platform converts each payment at a quoted rate, and the contractor receives either local currency in their bank account over Pix, SPEI, PSE, or an Argentine transfer, or stablecoins in a wallet if they prefer to hold dollars. Settlement takes minutes instead of 3 to 5 business days.\"\n  - q: \"Is it legal for US companies to pay contractors in stablecoins?\"\n    a: \"Yes. US companies may pay contractors in stablecoins through a provider registered with FinCEN as a Money Services Business. Stablecoin issuers are regulated under the GENIUS Act, signed in July 2025, with Treasury's implementing rules out for comment through October 19, 2026. On the receiving side, Brazil licenses virtual asset providers under Central Bank Resolutions 519 through 521, and Mexico, Colombia, and Argentina permit conversion to local currency through licensed providers. The payment is reportable like any other contractor payment.\"\n  - q: \"How do stablecoin payments compare to ACH payments, wire transfers, and platforms like Wise or Stripe for international payroll?\"\n    a: \"ACH is US-only, so it cannot pay a contractor in Brazil. An international wire costs $25 to $50 to send plus a 2 to 5 percent FX spread and lands in 2 to 5 business days. Wise and Stripe-based payout tools reach Latin America with lower spreads than banks but still settle over local rails on their schedules and often require pre-funded balances. Stablecoin payroll settles in minutes, 24\u002F7, at a rate quoted before you send, with no pre-funding.\"\n  - q: \"How much do contractors actually receive after fees when paid in USDC versus traditional bank transfers?\"\n    a: \"On a $3,000 payment by international wire, the contractor commonly receives $2,830 to $2,915 after sending fees, intermediary deductions, and the receiving bank's FX spread. Through a stablecoin payout with an itemized quote, the contractor receives the quoted amount, and the total cost is usually a small flat fee plus a sub-percent spread. Over a year of monthly payments the difference is typically several hundred dollars per contractor.\"\n  - q: \"How fast are stablecoin payments compared to real-time payments and standard international wire transfers?\"\n    a: \"The stablecoin transfer settles in seconds, conversion takes a few minutes, and Pix in Brazil and SPEI in Mexico run 24\u002F7, so a payout lands in minutes at any hour. That matches domestic real-time payments like RTP or FedNow in speed, but works across borders. An international wire takes 2 to 5 business days and does not move on weekends. Colombia over PSE and Argentina over Transfers 3.0 are same-day.\"\n  - q: \"What do LATAM contractors need to set up to receive stablecoin payroll payments?\"\n    a: \"For local currency: their name, tax ID (CPF in Brazil, RFC in Mexico, cedula in Colombia, CUIT in Argentina), and a bank account, entered once during onboarding. No wallet, no exchange account, no seed phrase. Contractors who want to hold dollars instead provide a wallet address that supports USDC or USDT. Onboarding with identity verification takes minutes.\"\n  - q: \"How do companies handle tax reporting and compliance when using stablecoin payroll for international contractors?\"\n    a: \"The same way as for any contractor payment. For a non-US contractor performing services outside the US, collect Form W-8BEN (or W-8BEN-E for a company) and keep it on file; no Form 1099-NEC is issued and no withholding applies to foreign-source services income. For a US person working abroad, Form 1099-NEC applies at the new $2,000 threshold for tax year 2026. Keep the payout ID, date, amount, FX rate, fees, and transaction hash per payment. Confirm the specifics with a tax advisor.\"\n---\n\nStablecoin payroll is a way for US companies to pay contractors in Latin America using a dollar-pegged token like USDC or USDT as the settlement layer, so the payment lands in minutes at a cost known before it is sent, instead of a wire that takes 3 to 5 business days and arrives short. The contractor receives local currency in their bank account, or stablecoins if they prefer to hold dollars. In 2026 it has become the default for companies paying teams in Argentina, Brazil, Mexico, and Colombia.\n\nThis guide is for a US company paying independent contractors in those countries: the finance or HR lead running a monthly cycle of 5 to 50 payments, the controller who needs to know the tax treatment before signing off, and the contractor on the other end who is tired of losing money to bank fees and inflation.\n\nHere is the normal experience it replaces. A startup with twelve contractors in Brazil, four in Mexico, and two in Colombia sends eighteen international wires on the last business day of the month. Three bounce for formatting reasons, two arrive short because an intermediary bank took a cut nobody could predict, and the Brazilian contractors get their reais on Wednesday of the following week, minus a 3 percent FX haircut from the receiving bank. That is not the bad case. That is the normal case.\n\n## What is stablecoin payroll and why LATAM contractors prefer it\n\nStablecoin payroll uses a [stablecoin](\u002Fresources\u002Fmore\u002Fstablecoins), a token designed to hold a 1:1 peg to the US dollar, to move value from the company to the contractor. What the contractor gets at the end is their choice. Most want local currency in their bank. A minority, especially in Argentina, want to hold dollars.\n\nThat second part is the one most guides get wrong. Stablecoin payroll does not mean contractors have to open a crypto wallet. A designer in São Paulo wants reais in her Nubank account. A developer in Guadalajara wants pesos over SPEI. The stablecoin moves the value across the border. The local rail puts it in their hands. The flow is sometimes called the stablecoin sandwich: fiat in, stablecoin across, fiat out.\n\nContractors prefer it for three reasons.\n\n**Speed.** A wire takes 3 to 5 business days, assuming no compliance hold at an intermediary bank. A stablecoin payout lands in minutes. For a freelancer juggling several clients, getting paid today instead of next week is the difference between paying rent on time and not.\n\n**Fee erosion.** On a $3,000 wire, the contractor commonly loses $85 to $170 to sending fees, intermediary deductions, and the receiving bank's exchange rate. On a stablecoin payout the amount quoted is the amount received. In the LATAM stablecoin payments map that BlindPay co-published with Bitso Business, Utila, and Minteo in 2025, mass payouts to freelancers in Mexico and Brazil showed an [80 percent cut in settlement time](https:\u002F\u002Fbusiness.bitso.com\u002Fen\u002Fblog\u002Fthe-first-stablecoin-payments-map-in-latam) compared with the wires they replaced.\n\n**Currency protection.** A contractor in Argentina paid in pesos watches the value fall within days. Paid in USDC to a wallet, they hold dollars and convert when they choose. For contractors in Brazil, Mexico, and Colombia the local currency payout is usually what they want, but the option to hold dollars is a real benefit for some.\n\nFor the company, the win is operational. One provider, one API or dashboard, one payment method that works the same in four countries, instead of four sets of banking requirements and four pre-funded balances.\n\n## USDC vs USDT: choosing the right stablecoin for LATAM payments\n\nFor most US companies USDC is the right default, and the choice only matters for contractors who want to hold stablecoins rather than receive local currency.\n\n[USDC](\u002Fresources\u002Fmore\u002Fwhat-is-usdc) is issued by Circle, publishes monthly reserve attestations, and is positioned for licensing under the GENIUS Act. It is the easier asset to justify to a US finance or legal team, and it is what most US companies already hold.\n\nUSDT, issued by Tether, has deeper liquidity in many LATAM off-ramps and local exchanges. On some corridors that means a slightly tighter spread when converting to local currency, and contractors in Argentina who plan to sell for pesos on a local exchange often find USDT easier to move.\n\nIf contractors are paid in local currency, they never see which token settled the payment, so the company should pick the one its compliance team prefers and let the provider handle conversion. If contractors are paid in stablecoins to a wallet, let each contractor choose. A provider that supports both, like BlindPay, removes the decision from the operations team. The [USDC vs USDT comparison](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) covers reserves, liquidity, and regulatory posture in detail.\n\n## How stablecoin payroll works step-by-step\n\nA stablecoin payroll run has five steps. With a payout platform like [BlindPay](\u002Fglobal-payments) the company's team touches three of them; the platform handles conversion, compliance, and delivery.\n\n1. **Onboard each contractor once.** The contractor submits their name, tax ID (CPF in Brazil, RFC in Mexico, cedula in Colombia, CUIT in Argentina), and a bank account. Identity verification and receiving-account checks run inside the flow. A contractor who wants to hold dollars submits a wallet address instead. This takes minutes and happens one time.\n2. **Fund the run.** Send USDC or USDT from the company's treasury wallet, or send dollars by ACH or wire to a [virtual account](\u002Fvirtual-accounts) that converts them to stablecoins automatically. No pre-funding in a Brazilian or Mexican account.\n3. **Request a quote per payout.** The platform returns the FX rate, the spread, and the payout fee as separate numbers. The exact amount landing in the contractor's account is known before the company commits.\n4. **Execute.** The stablecoin moves on-chain, converts to local currency, and pays out over Pix in Brazil, SPEI in Mexico, PSE in Colombia, or Transfers 3.0 to a CBU or CVU in Argentina. A wallet payout skips the conversion and delivers USDC or USDT directly. Since August 2026, BlindPay also moves USDC across networks in a single transfer, so the company's treasury chain and the payout chain no longer have to match; the [cross-chain USDC changelog](\u002Fchangelog\u002F2026-08-20-payables-cross-chain-usdc-fx-export) has the details.\n5. **Reconcile.** Each payout has an ID, a status, a transaction hash, and a webhook. The finance tool receives the event. The contractor receives the money.\n\nEnd to end, a Brazilian payout over Pix usually completes in minutes. Same for SPEI in Mexico, which also runs 24\u002F7. Colombia over PSE follows bank processing windows and is usually minutes, sometimes longer. Argentina over Transfers 3.0 is same-day. A Friday evening run does not become a Tuesday deposit.\n\nOne property to understand before the first run: the on-chain transfer is final once confirmed. That is why receiver verification happens before the money moves, not after. [Are stablecoin payments reversible](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) explains what can be recalled on each leg. A contractor who received USDC and later wants dollars in a US account can use a [USDC to USD](\u002Fusdc-to-usd) off-ramp.\n\n## Compliance and tax reporting for US companies\n\nStablecoin payroll does not change what a US company owes or reports. It changes the settlement mechanism. Three rules cover most cases, and a tax advisor should confirm the specifics for the company's situation.\n\n**Non-US contractors performing services outside the US.** This is the typical LATAM contractor. Collect Form W-8BEN (or W-8BEN-E if the contractor invoices through a company) and keep it on file. No Form 1099-NEC is issued, and no US withholding applies, because the income is foreign-source services income. The W-8BEN is not filed with the IRS; it supports why no 1099 was issued if the company is audited.\n\n**US persons working abroad.** A US citizen or resident living in Mexico and invoicing as a contractor is reported on Form 1099-NEC like any domestic contractor. For payments made on or after January 1, 2026, the reporting threshold rose from $600 to $2,000 under the One Big Beautiful Bill Act, indexed for inflation from 2027. The reportable amount is the fair market value at the time of payment, which for a dollar-pegged stablecoin is the dollar amount.\n\n**Records.** Keep, per payment: date, contractor, amount, currency delivered, FX rate and fees, payout ID, and the on-chain transaction hash. A payout platform should provide this by API and export. The transaction hash is a public, timestamped record that a wire cannot match, and auditors have started to expect it.\n\nOn the platform side, the provider must be registered with FinCEN as a Money Services Business and hold or be exempt from state money transmitter licenses; BlindPay publishes its status on the [licenses page](\u002Flicenses). On the receiving side, Brazil licenses virtual asset service providers under Central Bank Resolutions 519 through 521, in force since February 2, 2026, and Resolution 561 on eFX in May 2026 does not affect the stablecoin plus local rails model, as [BlindPay explained at the time](\u002Fblog\u002Fbcb-resolution-561-efx-stablecoins). The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) keeps the country-by-country view current.\n\nContractors owe income tax in their own country on what they receive, and converting stablecoins to local currency may be a taxable event locally. The company is not responsible for the contractor's filing, but clear per-payment documentation helps them meet it.\n\n## Comparing stablecoin payroll platforms for global payments\n\nPlatforms that pay LATAM contractors with stablecoins fall into three groups: payout APIs that deliver local currency, contractor management platforms that added a stablecoin option, and exchange or wallet products that deliver tokens only. The table compares what a company evaluating them for a 5 to 50 contractor run should check. Capabilities change often; confirm current details on each provider's site. The [provider comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026) covers the wider field.\n\n| Platform type | Example | Contractor receives | LATAM rails | Pre-funding | Quote | Access |\n| --- | --- | --- | --- | --- | --- | --- |\n| Stablecoin payout API | BlindPay | Local currency or USDC\u002FUSDT | Pix, SPEI, PSE, Argentine transfers, plus ACH and SWIFT (POBO\u002FCOBO) | None | Itemized: rate, spread, fee | API, dashboard, MCP for AI agents |\n| Contractor management platform with stablecoin option | Deel, Toku | Local currency or stablecoin, depending on plan | Via partner rails | Often required | Blended | Dashboard, some APIs |\n| Stripe-ecosystem stablecoin | Bridge | USDC or USD\u002FEUR | ACH, wire, SEPA | Balance-based | Percentage | API |\n| Exchange or wallet payout | Bitso Business, local exchanges | Tokens or local currency at the exchange | Country-specific | Funds on exchange | Exchange rate | Dashboard, API |\n\nFive variables decide the choice.\n\n**What the contractor receives.** If most contractors want local currency, a payout API that delivers over Pix, SPEI, PSE, and Argentine transfers is the only category that does it in one integration. If most want to hold dollars, an exchange or wallet payout works, but the contractor then handles conversion themselves.\n\n**Fee structure.** Flat per payout, percentage, or both. For frequent smaller payments a low flat fee matters most; for larger payments the spread dominates. Compare on the company's actual payment pattern, and insist on an itemized quote. The [pricing explainer](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) shows why a blended rate hides the real number.\n\n**Pre-funding.** Platforms that require a BRL balance in Brazil and an MXN balance in Mexico before payouts clear are tying up working capital that never shows up as a fee. Ask directly.\n\n**Compliance built in.** Receiver KYC, account verification, and sanctions screening should run inside the flow. The platform should publish its licenses.\n\n**API vs dashboard.** A team of two running monthly payroll wants a dashboard. A company with a payroll system wants an API and webhooks. The best platforms offer both.\n\n## Get started with stablecoin payments for your LATAM team\n\nFour steps take a company from wires to a working stablecoin payroll in one or two cycles.\n\n**Pick the platform against the five variables above.** For 5 to 50 contractors across Brazil, Mexico, Colombia, and Argentina, a payout API that delivers local currency with an itemized quote and no pre-funding covers the common case. BlindPay's [global payments](\u002Fglobal-payments) product is built for that flow, with [pricing](\u002Fpricing) and [coverage](\u002Fcoverage) published.\n\n**Ask contractors what they want.** Local currency to a bank account, or stablecoins to a wallet. Most choose the bank account. Do not push wallets on people who did not ask for one; that moves the friction to them.\n\n**Run one cycle in parallel.** Pay one or two contractors over stablecoins and the rest by wire. Compare what landed, when, and what it cost. Test the failure paths too: a rejected receiving account, a compliance hold. [Sandbox does not exercise those](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production); a small live pilot does.\n\n**Document from day one.** W-8BEN on file per foreign contractor, per-payment records with transaction hash, and a reconciliation step wired to the webhook. Habits set on the first run hold as the contractor base grows.\n\nThe shift is smaller than it looks. A company already paying international contractors has the hard parts done: the relationships, the schedule, the invoices. Stablecoin payroll swaps the settlement mechanism for one that is faster, cheaper, and easier to audit.\n\n[Start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction), or [contact BlindPay](https:\u002F\u002Fblindpay.com\u002Fcontact) with the countries and monthly volume.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":10054,"description":10465},"Stablecoin payroll for LATAM contractors in 2026","resources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","nVFOXkH1R7sobHvZanluCWLgQqXWRMKRTTGqp-mpE5E",{"id":10495,"title":10496,"authors":6,"body":10497,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":3927,"description":10846,"extension":342,"faq":10847,"howto":6,"isBlog":359,"isChangelog":359,"meta":10863,"navigation":362,"path":2418,"pillar":359,"products":6,"rawbody":10864,"role":6,"seo":10865,"seoTitle":10866,"stem":10867,"thumbnail":6,"updated":6,"__hash__":10868},"content\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants.md","Stablecoin settlement explained: how merchants get paid faster than card networks",{"type":8,"value":10498,"toc":10836},[10499,10514,10517,10542,10546,10549,10641,10644,10648,10651,10654,10657,10660,10664,10667,10670,10690,10693,10697,10700,10703,10729,10738,10742,10745,10748,10754,10758,10761,10767,10773,10779,10782,10786,10818,10827,10831],[11,10500,10501,10502,10505,10506,10509,10510,10513],{},"Stablecoin payments settle in ",[119,10503,10504],{},"seconds to a few minutes",", on any day of the week, and the funds are final once the blockchain confirms them. Card networks typically pay merchants ",[119,10507,10508],{},"one to three business days"," after the sale, and cross-border wires take ",[119,10511,10512],{},"one to five business days",". If the merchant needs local currency, an off-ramp converts the stablecoins and pays out over a local rail like Pix, SPEI, or RTP, usually within minutes. No pre-funded accounts required.",[11,10515,10516],{},"That gap is not a small speed bump. It changes how much working capital a merchant needs, how exposed they are to chargebacks, and whether Friday night sales can pay Monday's suppliers.",[9962,10518,10519,10524,10530,10536],{},[11,10520,10521],{},[119,10522,10523],{},"Quick glossary",[11,10525,10526,10529],{},[119,10527,10528],{},"Settlement:"," the moment the merchant has usable funds in the account and currency they want. Not authorization, not \"pending.\" Usable.",[11,10531,10532,10535],{},[119,10533,10534],{},"Finality:"," the point after which a payment can't be reversed by the payer, the bank, or the network.",[11,10537,10538,10541],{},[119,10539,10540],{},"On-ramp \u002F off-ramp:"," services that convert fiat into stablecoins (on-ramp) and stablecoins back into fiat (off-ramp).",[18,10543,10545],{"id":10544},"how-long-does-settlement-take-on-each-payment-rail","How long does settlement take on each payment rail?",[11,10547,10548],{},"Here's the side-by-side most finance teams actually need:",[39,10550,10551,10569],{},[42,10552,10553],{},[45,10554,10555,10557,10560,10563,10566],{},[48,10556,1088],{},[48,10558,10559],{},"Time to usable funds",[48,10561,10562],{},"Typical cost to merchant",[48,10564,10565],{},"When is it final?",[48,10567,10568],{},"Runs on weekends?",[61,10570,10571,10589,10607,10624],{},[45,10572,10573,10577,10580,10583,10586],{},[66,10574,10575],{},[119,10576,9481],{},[66,10578,10579],{},"Seconds to minutes on-chain; minutes to local bank over instant rails",[66,10581,10582],{},"Network fee of cents, plus FX spread and payout fee if converted",[66,10584,10585],{},"Once confirmed on-chain, minutes",[66,10587,10588],{},"Yes, 24\u002F7\u002F365",[45,10590,10591,10596,10598,10601,10604],{},[66,10592,10593],{},[119,10594,10595],{},"Card networks",[66,10597,1110],{},[66,10599,10600],{},"Typically 1.5% to 3.5%, more on international cards",[66,10602,10603],{},"Open to chargebacks, typically for up to 120 days",[66,10605,10606],{},"Authorization yes, payout no",[45,10608,10609,10613,10616,10619,10622],{},[66,10610,10611],{},[119,10612,3495],{},[66,10614,10615],{},"Same day to 2 business days",[66,10617,10618],{},"Usually under $1 per transfer",[66,10620,10621],{},"Returns possible for days; up to 60 days on unauthorized consumer debits",[66,10623,3458],{},[45,10625,10626,10631,10633,10636,10639],{},[66,10627,10628],{},[119,10629,10630],{},"International wire (SWIFT)",[66,10632,1159],{},[66,10634,10635],{},"$25 to $50 per wire, plus FX spread and intermediary deductions",[66,10637,10638],{},"Final once credited, but recalls get requested",[66,10640,3458],{},[11,10642,10643],{},"The pattern: every traditional rail is either fast and reversible (cards), cheap and slow (ACH), or slow and expensive (wires). Stablecoin settlement is the first one that's fast, cheap, and final at the same time.",[18,10645,10647],{"id":10646},"why-is-stablecoin-settlement-faster-than-card-settlement","Why is stablecoin settlement faster than card settlement?",[11,10649,10650],{},"Because there are fewer parties in the middle.",[11,10652,10653],{},"A card payment moves through the cardholder's issuing bank, the card network, the merchant's acquirer, and a processor. Each one batches, nets, and reconciles on its own schedule. The acquirer usually waits for the network's daily clearing cycle, then pays the merchant on the next business day or two. Weekends and bank holidays add days.",[11,10655,10656],{},"A stablecoin payment is a single transfer recorded on a shared ledger. The payer's wallet sends the tokens, validators confirm the block, and the recipient's balance updates. There's no batch window and no bank that closes at 5pm.",[11,10658,10659],{},"What's interesting here is that the speed doesn't come from the blockchain being \"faster\" in some raw sense. It comes from the architecture: one ledger that everyone reads, instead of four ledgers that reconcile to each other overnight.",[18,10661,10663],{"id":10662},"what-does-settlement-finality-mean-for-merchant-risk","What does settlement finality mean for merchant risk?",[11,10665,10666],{},"A card sale that \"settled\" on Tuesday can come back in March. The cardholder files a dispute, the network pulls the funds, and the merchant pays a chargeback fee on top of losing the sale. For merchants selling digital goods or shipping internationally, chargebacks are a line item, not an edge case.",[11,10668,10669],{},"A confirmed stablecoin transfer can't be pulled back. No network, bank, or payer can reverse it. That gives merchants three things:",[171,10671,10672,10678,10684],{},[148,10673,10674,10677],{},[119,10675,10676],{},"No chargeback fraud."," The \"friendly fraud\" pattern, where a buyer receives goods and then disputes the charge, doesn't exist on this rail.",[148,10679,10680,10683],{},[119,10681,10682],{},"No dispute fees."," No per-chargeback penalty, no reserve held back by the acquirer to cover future disputes.",[148,10685,10686,10689],{},[119,10687,10688],{},"Cleaner cash forecasting."," Money that arrived is money you have.",[11,10691,10692],{},"Two honest caveats. First, refunds still exist; the merchant just sends them as a new transfer, so you need a written refund policy. Second, finality on the stablecoin leg doesn't make the fiat leg next to it final. If a customer funds a stablecoin purchase with an ACH debit, that ACH debit can still be returned for days. Good providers monitor the fiat side continuously for exactly this reason.",[18,10694,10696],{"id":10695},"how-do-merchants-turn-stablecoin-balances-into-local-currency","How do merchants turn stablecoin balances into local currency?",[11,10698,10699],{},"Most merchants don't want to hold USDC forever. They have payroll in reais, rent in pesos, and suppliers who invoice in euros. The conversion step is where settlement either stays fast or quietly becomes slow again.",[11,10701,10702],{},"A good off-ramp flow looks like this:",[145,10704,10705,10711,10717,10723],{},[148,10706,10707,10710],{},[119,10708,10709],{},"Request a quote."," Amount, source stablecoin, destination currency, destination bank account.",[148,10712,10713,10716],{},[119,10714,10715],{},"Review the itemized numbers."," The FX rate, the spread, and the payout fee, as separate lines.",[148,10718,10719,10722],{},[119,10720,10721],{},"Accept and execute."," The rate is locked at execution, so the amount that lands is the amount you were quoted.",[148,10724,10725,10728],{},[119,10726,10727],{},"Receive over the local rail."," Pix in Brazil and SPEI in Mexico land in minutes. RTP in the US lands in seconds. SEPA in Europe, PSE in Colombia, and Transfers 3.0 in Argentina follow their own windows, usually same day.",[11,10730,10731,10732,1337,10734,227],{},"BlindPay runs this conversion and payout in 100+ countries and 80+ currencies through one API. Live rates for common corridors are public, for example ",[136,10733,644],{"href":1757},[136,10735,10737],{"href":10736},"\u002Fusdc-to-mxn","USDC to MXN",[18,10739,10741],{"id":10740},"what-does-no-pre-funding-required-mean-in-practice","What does \"no pre-funding required\" mean in practice?",[11,10743,10744],{},"In traditional cross-border payments, a provider that pays out in Brazil needs reais sitting in a Brazilian account before the payment can go out. Same for Mexico, Colombia, the Philippines. That capital is trapped, spread across a dozen countries, idle until it's spent. Someone pays for it, and it's usually the merchant, through wider FX spreads.",[11,10746,10747],{},"With stablecoins as the settlement layer, the value crosses the border as a digital dollar and converts at the destination at execution time. The merchant doesn't park money in every market ahead of time. BlindPay settles without requiring capital pre-positioned in destination accounts, which is one of the main reasons its quotes can stay tight.",[11,10749,10750,10751,10753],{},"For merchants who receive dollars from customers by bank transfer rather than from wallets, ",[136,10752,3193],{"href":3192}," close the loop: a US account in your name with ACH, Wire, and RTP, where deposits auto-convert into stablecoins and can settle to local currency right after.",[18,10755,10757],{"id":10756},"a-settlement-timeline-side-by-side","A settlement timeline, side by side",[11,10759,10760],{},"A merchant in Mexico sells $10,000 of goods to a US buyer on a Friday evening.",[11,10762,10763,10766],{},[119,10764,10765],{},"By card:"," the authorization clears instantly. The acquirer includes the sale in Monday's batch. Funds reach the merchant's account Tuesday or Wednesday, minus 3% or more once cross-border and FX fees are counted. The sale stays disputable for months.",[11,10768,10769,10772],{},[119,10770,10771],{},"By international wire:"," the buyer's bank sends it Monday morning. It passes through one or two correspondent banks and lands Wednesday or Thursday, minus a $25 to $50 fee and an FX spread set by the receiving bank.",[11,10774,10775,10778],{},[119,10776,10777],{},"By stablecoin:"," the buyer sends 10,000 USDC Friday night. It confirms in seconds. The merchant requests a quote, locks the MXN rate, and the pesos land over SPEI in minutes. Friday night. Final.",[11,10780,10781],{},"Same sale. The difference is four to five days of working capital and zero dispute exposure.",[18,10783,10785],{"id":10784},"what-should-a-finance-lead-check-before-switching","What should a finance lead check before switching?",[171,10787,10788,10794,10800,10806,10812],{},[148,10789,10790,10793],{},[119,10791,10792],{},"Which stablecoins and networks"," your customers actually hold. USDC and USDT on low-fee chains cover most of it.",[148,10795,10796,10799],{},[119,10797,10798],{},"Which local rails"," the provider pays out on, and whether they're instant (Pix, SPEI, RTP) or batch.",[148,10801,10802,10805],{},[119,10803,10804],{},"Whether quotes are itemized."," Spread and payout fee as separate numbers, locked at execution.",[148,10807,10808,10811],{},[119,10809,10810],{},"Whether the provider needs you to pre-fund"," anything.",[148,10813,10814,10817],{},[119,10815,10816],{},"How compliance runs."," KYB on your business, KYC on counterparties, and monitoring on both the on-chain and fiat legs.",[11,10819,10820,10821,10823,10824,227],{},"For the full receiving flow, read ",[136,10822,2763],{"href":2762},". For the leadership case on combining stablecoins with instant local rails, see ",[136,10825,10826],{"href":1192},"Orchestrating Local Payments and Stablecoins",[18,10828,10830],{"id":10829},"get-paid-in-minutes-not-days","Get paid in minutes, not days",[11,10832,10833,10834,227],{},"Card-era settlement made sense when there was no alternative. There is now. If you want to see a live, itemized quote for your corridor and a real settlement timeline, ",[136,10835,2781],{"href":1344},{"title":328,"searchDepth":329,"depth":329,"links":10837},[10838,10839,10840,10841,10842,10843,10844,10845],{"id":10544,"depth":329,"text":10545},{"id":10646,"depth":329,"text":10647},{"id":10662,"depth":329,"text":10663},{"id":10695,"depth":329,"text":10696},{"id":10740,"depth":329,"text":10741},{"id":10756,"depth":329,"text":10757},{"id":10784,"depth":329,"text":10785},{"id":10829,"depth":329,"text":10830},"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.",[10848,10851,10854,10857,10860],{"q":10849,"a":10850},"How does stablecoin settlement work for merchants?","The customer sends USDC or USDT to the merchant's address. The blockchain confirms the transfer in seconds to a few minutes, and at that point the funds are final and usable. If the merchant wants local currency, an off-ramp converts the stablecoins at a quoted rate and pays out over a local rail like Pix, SPEI, RTP, or SEPA, usually within minutes.",{"q":10852,"a":10853},"How long does stablecoin settlement take compared to card payments?","On-chain settlement on networks like Polygon, Base, Stellar, or Tron takes seconds to a few minutes, 24 hours a day, including weekends. Card networks typically pay merchants one to three business days after the sale, and nothing moves on weekends or bank holidays. International wires take one to five business days.",{"q":10855,"a":10856},"What is settlement finality?","Finality is the point after which a payment cannot be reversed. A confirmed stablecoin transfer is final within minutes. A card payment is not truly final for months, because cardholders can file chargebacks, typically for up to 120 days. An ACH debit can be returned for days, and up to 60 days when a consumer claims it was unauthorized.",{"q":10858,"a":10859},"Do merchants need pre-funded accounts to receive stablecoin settlement?","No. With a stablecoin settlement provider like BlindPay, the merchant does not need to park capital in local accounts in each country before money can move. Funds are converted and delivered at execution time, at a rate quoted and locked before the payment runs.",{"q":10861,"a":10862},"How do merchants convert stablecoin balances into local currency?","Through an off-ramp. The merchant requests a quote for the amount and destination currency, accepts it, and the provider sells the stablecoins and pays out to the merchant's bank account over the local rail. BlindPay supports payouts in 100+ countries and 80+ currencies, including Pix in Brazil, SPEI in Mexico, PSE in Colombia, Transfers 3.0 in Argentina, ACH and RTP in the US, and SEPA in Europe.",{},"---\ntitle: \"Stablecoin settlement explained: how merchants get paid faster than card networks\"\nseoTitle: \"Stablecoin settlement for merchants, explained\"\ndescription: \"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.\"\ndate: \"2026-08-06\"\ncategory: \"payments\"\nfaq:\n  - q: \"How does stablecoin settlement work for merchants?\"\n    a: \"The customer sends USDC or USDT to the merchant's address. The blockchain confirms the transfer in seconds to a few minutes, and at that point the funds are final and usable. If the merchant wants local currency, an off-ramp converts the stablecoins at a quoted rate and pays out over a local rail like Pix, SPEI, RTP, or SEPA, usually within minutes.\"\n  - q: \"How long does stablecoin settlement take compared to card payments?\"\n    a: \"On-chain settlement on networks like Polygon, Base, Stellar, or Tron takes seconds to a few minutes, 24 hours a day, including weekends. Card networks typically pay merchants one to three business days after the sale, and nothing moves on weekends or bank holidays. International wires take one to five business days.\"\n  - q: \"What is settlement finality?\"\n    a: \"Finality is the point after which a payment cannot be reversed. A confirmed stablecoin transfer is final within minutes. A card payment is not truly final for months, because cardholders can file chargebacks, typically for up to 120 days. An ACH debit can be returned for days, and up to 60 days when a consumer claims it was unauthorized.\"\n  - q: \"Do merchants need pre-funded accounts to receive stablecoin settlement?\"\n    a: \"No. With a stablecoin settlement provider like BlindPay, the merchant does not need to park capital in local accounts in each country before money can move. Funds are converted and delivered at execution time, at a rate quoted and locked before the payment runs.\"\n  - q: \"How do merchants convert stablecoin balances into local currency?\"\n    a: \"Through an off-ramp. The merchant requests a quote for the amount and destination currency, accepts it, and the provider sells the stablecoins and pays out to the merchant's bank account over the local rail. BlindPay supports payouts in 100+ countries and 80+ currencies, including Pix in Brazil, SPEI in Mexico, PSE in Colombia, Transfers 3.0 in Argentina, ACH and RTP in the US, and SEPA in Europe.\"\n---\n\nStablecoin payments settle in **seconds to a few minutes**, on any day of the week, and the funds are final once the blockchain confirms them. Card networks typically pay merchants **one to three business days** after the sale, and cross-border wires take **one to five business days**. If the merchant needs local currency, an off-ramp converts the stablecoins and pays out over a local rail like Pix, SPEI, or RTP, usually within minutes. No pre-funded accounts required.\n\nThat gap is not a small speed bump. It changes how much working capital a merchant needs, how exposed they are to chargebacks, and whether Friday night sales can pay Monday's suppliers.\n\n> **Quick glossary**\n>\n> **Settlement:** the moment the merchant has usable funds in the account and currency they want. Not authorization, not \"pending.\" Usable.\n>\n> **Finality:** the point after which a payment can't be reversed by the payer, the bank, or the network.\n>\n> **On-ramp \u002F off-ramp:** services that convert fiat into stablecoins (on-ramp) and stablecoins back into fiat (off-ramp).\n\n## How long does settlement take on each payment rail?\n\nHere's the side-by-side most finance teams actually need:\n\n| Rail | Time to usable funds | Typical cost to merchant | When is it final? | Runs on weekends? |\n| --- | --- | --- | --- | --- |\n| **Stablecoin (USDC\u002FUSDT)** | Seconds to minutes on-chain; minutes to local bank over instant rails | Network fee of cents, plus FX spread and payout fee if converted | Once confirmed on-chain, minutes | Yes, 24\u002F7\u002F365 |\n| **Card networks** | 1 to 3 business days | Typically 1.5% to 3.5%, more on international cards | Open to chargebacks, typically for up to 120 days | Authorization yes, payout no |\n| **ACH** | Same day to 2 business days | Usually under $1 per transfer | Returns possible for days; up to 60 days on unauthorized consumer debits | No |\n| **International wire (SWIFT)** | 1 to 5 business days | $25 to $50 per wire, plus FX spread and intermediary deductions | Final once credited, but recalls get requested | No |\n\nThe pattern: every traditional rail is either fast and reversible (cards), cheap and slow (ACH), or slow and expensive (wires). Stablecoin settlement is the first one that's fast, cheap, and final at the same time.\n\n## Why is stablecoin settlement faster than card settlement?\n\nBecause there are fewer parties in the middle.\n\nA card payment moves through the cardholder's issuing bank, the card network, the merchant's acquirer, and a processor. Each one batches, nets, and reconciles on its own schedule. The acquirer usually waits for the network's daily clearing cycle, then pays the merchant on the next business day or two. Weekends and bank holidays add days.\n\nA stablecoin payment is a single transfer recorded on a shared ledger. The payer's wallet sends the tokens, validators confirm the block, and the recipient's balance updates. There's no batch window and no bank that closes at 5pm.\n\nWhat's interesting here is that the speed doesn't come from the blockchain being \"faster\" in some raw sense. It comes from the architecture: one ledger that everyone reads, instead of four ledgers that reconcile to each other overnight.\n\n## What does settlement finality mean for merchant risk?\n\nA card sale that \"settled\" on Tuesday can come back in March. The cardholder files a dispute, the network pulls the funds, and the merchant pays a chargeback fee on top of losing the sale. For merchants selling digital goods or shipping internationally, chargebacks are a line item, not an edge case.\n\nA confirmed stablecoin transfer can't be pulled back. No network, bank, or payer can reverse it. That gives merchants three things:\n\n- **No chargeback fraud.** The \"friendly fraud\" pattern, where a buyer receives goods and then disputes the charge, doesn't exist on this rail.\n- **No dispute fees.** No per-chargeback penalty, no reserve held back by the acquirer to cover future disputes.\n- **Cleaner cash forecasting.** Money that arrived is money you have.\n\nTwo honest caveats. First, refunds still exist; the merchant just sends them as a new transfer, so you need a written refund policy. Second, finality on the stablecoin leg doesn't make the fiat leg next to it final. If a customer funds a stablecoin purchase with an ACH debit, that ACH debit can still be returned for days. Good providers monitor the fiat side continuously for exactly this reason.\n\n## How do merchants turn stablecoin balances into local currency?\n\nMost merchants don't want to hold USDC forever. They have payroll in reais, rent in pesos, and suppliers who invoice in euros. The conversion step is where settlement either stays fast or quietly becomes slow again.\n\nA good off-ramp flow looks like this:\n\n1. **Request a quote.** Amount, source stablecoin, destination currency, destination bank account.\n2. **Review the itemized numbers.** The FX rate, the spread, and the payout fee, as separate lines.\n3. **Accept and execute.** The rate is locked at execution, so the amount that lands is the amount you were quoted.\n4. **Receive over the local rail.** Pix in Brazil and SPEI in Mexico land in minutes. RTP in the US lands in seconds. SEPA in Europe, PSE in Colombia, and Transfers 3.0 in Argentina follow their own windows, usually same day.\n\nBlindPay runs this conversion and payout in 100+ countries and 80+ currencies through one API. Live rates for common corridors are public, for example [USDC to BRL](\u002Fusdc-to-brl) and [USDC to MXN](\u002Fusdc-to-mxn).\n\n## What does \"no pre-funding required\" mean in practice?\n\nIn traditional cross-border payments, a provider that pays out in Brazil needs reais sitting in a Brazilian account before the payment can go out. Same for Mexico, Colombia, the Philippines. That capital is trapped, spread across a dozen countries, idle until it's spent. Someone pays for it, and it's usually the merchant, through wider FX spreads.\n\nWith stablecoins as the settlement layer, the value crosses the border as a digital dollar and converts at the destination at execution time. The merchant doesn't park money in every market ahead of time. BlindPay settles without requiring capital pre-positioned in destination accounts, which is one of the main reasons its quotes can stay tight.\n\nFor merchants who receive dollars from customers by bank transfer rather than from wallets, [Named Virtual Accounts](\u002Fblog\u002Fintroducing-virtual-accounts) close the loop: a US account in your name with ACH, Wire, and RTP, where deposits auto-convert into stablecoins and can settle to local currency right after.\n\n## A settlement timeline, side by side\n\nA merchant in Mexico sells $10,000 of goods to a US buyer on a Friday evening.\n\n**By card:** the authorization clears instantly. The acquirer includes the sale in Monday's batch. Funds reach the merchant's account Tuesday or Wednesday, minus 3% or more once cross-border and FX fees are counted. The sale stays disputable for months.\n\n**By international wire:** the buyer's bank sends it Monday morning. It passes through one or two correspondent banks and lands Wednesday or Thursday, minus a $25 to $50 fee and an FX spread set by the receiving bank.\n\n**By stablecoin:** the buyer sends 10,000 USDC Friday night. It confirms in seconds. The merchant requests a quote, locks the MXN rate, and the pesos land over SPEI in minutes. Friday night. Final.\n\nSame sale. The difference is four to five days of working capital and zero dispute exposure.\n\n## What should a finance lead check before switching?\n\n- **Which stablecoins and networks** your customers actually hold. USDC and USDT on low-fee chains cover most of it.\n- **Which local rails** the provider pays out on, and whether they're instant (Pix, SPEI, RTP) or batch.\n- **Whether quotes are itemized.** Spread and payout fee as separate numbers, locked at execution.\n- **Whether the provider needs you to pre-fund** anything.\n- **How compliance runs.** KYB on your business, KYC on counterparties, and monitoring on both the on-chain and fiat legs.\n\nFor the full receiving flow, read [how merchants accept stablecoin payments](\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments). For the leadership case on combining stablecoins with instant local rails, see [Orchestrating Local Payments and Stablecoins](\u002Fblog\u002Forchestrating-payment-rails-leaders).\n\n## Get paid in minutes, not days\n\nCard-era settlement made sense when there was no alternative. There is now. If you want to see a live, itemized quote for your corridor and a real settlement timeline, [talk to the BlindPay team](\u002Fcontact).\n",{"title":10496,"description":10846},"Stablecoin settlement for merchants, explained","resources\u002Fmore\u002Fstablecoin-settlement-for-merchants","m5sx7MGd6kQeg0KEqw98gMFWVxVaNwJOJx9OrgTGOi8",{"id":10870,"title":10871,"authors":6,"body":10872,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":11241,"description":11242,"extension":342,"faq":11243,"howto":6,"isBlog":359,"isChangelog":359,"meta":11259,"navigation":362,"path":9278,"pillar":359,"products":6,"rawbody":11260,"role":6,"seo":11261,"seoTitle":11262,"stem":11263,"thumbnail":6,"updated":5834,"__hash__":11264},"content\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts.md","Stablecoin-funded virtual cards vs. traditional virtual cards for cross-border payouts",{"type":8,"value":10873,"toc":11232},[10874,10878,10883,10886,10891,10895,10898,10901,10927,10930,10934,10937,11030,11033,11037,11040,11043,11049,11053,11056,11061,11081,11086,11097,11100,11110,11114,11174,11178,11213,11215,11228],[11,10875,10876],{},[324,10877,3959],{},[11,10879,10880,10882],{},[119,10881,4656],{}," A stablecoin-funded virtual card is a Visa or Mastercard card number, with no plastic, whose balance is funded from a stablecoin such as USDC instead of a bank deposit. Companies issue them to pay contractors, vendors, and employees abroad: the recipient spends online or through a mobile wallet, and the program converts the stablecoin to the merchant's currency.",[11,10884,10885],{},"The card leg is the same as any virtual card. The difference is upstream: how the money gets into the card program, how fast, and how much of it has to sit there in advance.",[11,10887,10888,10889,227],{},"This guide is written for operations and finance leads at marketplaces, payroll platforms, and gig-economy companies. For the basics, read ",[136,10890,4667],{"href":4666},[18,10892,10894],{"id":10893},"why-do-companies-pay-with-virtual-cards-instead-of-wires-or-ach","Why do companies pay with virtual cards instead of wires or ACH?",[11,10896,10897],{},"A wire needs the recipient's bank details, a correspondent chain, and one to five business days. ACH only works inside the US. For a platform paying 3,000 people in 40 countries, both break at scale.",[11,10899,10900],{},"Virtual cards fix four things:",[171,10902,10903,10909,10915,10921],{},[148,10904,10905,10908],{},[119,10906,10907],{},"Issuance in seconds."," A card number exists the moment the API call returns. No bank details to collect or validate.",[148,10910,10911,10914],{},[119,10912,10913],{},"Controls per payment."," A card can carry a limit, an expiry date, and a merchant category rule. A wire cannot.",[148,10916,10917,10920],{},[119,10918,10919],{},"No recipient bank account."," The recipient needs a phone, not a bank relationship. That matters in markets where many adults are unbanked or underbanked.",[148,10922,10923,10926],{},[119,10924,10925],{},"Clean reconciliation."," One card per contractor or per payment maps each transaction to a person without matching wire references.",[11,10928,10929],{},"The tradeoff: a card is only a payout if the recipient can spend it. More on that below.",[18,10931,10933],{"id":10932},"stablecoin-funded-vs-bank-funded-virtual-cards","Stablecoin-funded vs. bank-funded virtual cards",[11,10935,10936],{},"Both kinds run on Visa or Mastercard and look identical to the recipient. They differ in how the program is funded.",[39,10938,10939,10952],{},[42,10940,10941],{},[45,10942,10943,10946,10949],{},[48,10944,10945],{},"Dimension",[48,10947,10948],{},"Bank-funded virtual cards",[48,10950,10951],{},"Stablecoin-funded virtual cards",[61,10953,10954,10965,10976,10987,10998,11009,11020],{},[45,10955,10956,10959,10962],{},[66,10957,10958],{},"Funding the program",[66,10960,10961],{},"Wire or ACH into the issuer's account",[66,10963,10964],{},"Stablecoin transfer from a wallet",[45,10966,10967,10970,10973],{},[66,10968,10969],{},"Funding speed",[66,10971,10972],{},"Same day domestically; 1 to 5 business days cross-border",[66,10974,10975],{},"Minutes, including weekends and holidays",[45,10977,10978,10981,10984],{},[66,10979,10980],{},"Pre-funding requirement",[66,10982,10983],{},"Balance parked in the issuer account ahead of demand, often in each card currency",[66,10985,10986],{},"Top up just in time from a stablecoin treasury",[45,10988,10989,10992,10995],{},[66,10990,10991],{},"FX on the funding leg",[66,10993,10994],{},"Wire FX and correspondent fees when the treasury is in another currency",[66,10996,10997],{},"None for USD cards funded with USD stablecoins",[45,10999,11000,11003,11006],{},[66,11001,11002],{},"FX at point of sale",[66,11004,11005],{},"Network rate plus any issuer foreign transaction fee",[66,11007,11008],{},"Same",[45,11010,11011,11014,11017],{},[66,11012,11013],{},"Settlement finality of funding",[66,11015,11016],{},"Wire recall and ACH return windows",[66,11018,11019],{},"Final once the on-chain transfer confirms",[45,11021,11022,11025,11028],{},[66,11023,11024],{},"Card-leg disputes",[66,11026,11027],{},"Network rules",[66,11029,11027],{},[11,11031,11032],{},"Two rows are the same on purpose. Stablecoins change the funding side. They do not change what happens when a contractor in Lisbon buys a train ticket in euros on a USD card.",[18,11034,11036],{"id":11035},"where-stablecoins-remove-pre-funding","Where stablecoins remove pre-funding",[11,11038,11039],{},"Traditional global payouts carry a quiet cost: cash parked in advance. A company paying people in five countries often keeps a balance in each currency, or a large USD balance at the card issuer, sized for the busiest week of the month. That cash earns little and cannot be used elsewhere.",[11,11041,11042],{},"With stablecoin funding the treasury stays in one place, a USDC balance, and moves only when a card is loaded or a purchase settles. Because stablecoin transfers settle 24\u002F7, the top-up can happen at 2 a.m. on a Sunday without a banking window.",[11,11044,11045,11046,227],{},"The same logic applies to local bank payouts. BlindPay sends stablecoins out as local currency on demand, without pre-funded accounts in each country, which is covered in ",[136,11047,11048],{"href":1226},"stablecoin payouts for marketplaces in Latin America",[18,11050,11052],{"id":11051},"walkthrough-paying-a-contractor-in-brazil","Walkthrough: paying a contractor in Brazil",[11,11054,11055],{},"Take a US platform paying a designer in Recife USD 2,000 a month.",[11,11057,11058],{},[119,11059,11060],{},"Option A: stablecoin-funded virtual card",[145,11062,11063,11066,11069,11072,11075,11078],{},[148,11064,11065],{},"The platform onboards the designer through KYC. Name, date of birth, tax ID (CPF), and a document check.",[148,11067,11068],{},"The platform issues a USD virtual card with a USD 2,000 monthly limit.",[148,11070,11071],{},"On payday, the program loads USD 2,000 from the platform's USDC balance. No BRL account is needed anywhere.",[148,11073,11074],{},"The designer adds the card to Google Pay the same day.",[148,11076,11077],{},"USD-priced spend (Figma, Adobe, a flight booked in dollars) costs exactly what it says.",[148,11079,11080],{},"Spend in reais at a Recife supermarket is converted by the network at its daily rate, plus any foreign transaction fee set by the issuer.",[11,11082,11083],{},[119,11084,11085],{},"Option B: a Pix payout",[145,11087,11088,11091,11094],{},[148,11089,11090],{},"Same KYC, plus the designer's Pix key or bank details.",[148,11092,11093],{},"The platform sends USDC. BlindPay converts it to BRL and delivers it over Pix, usually within minutes.",[148,11095,11096],{},"The designer has reais in their own bank account and pays rent, bills, and boletos from it.",[11,11098,11099],{},"Option A is better when the designer spends in dollars or wants to keep a dollar balance. Option B is better when the money is for local life. In Brazil, rent, utility bills, and most person-to-person payments run on Pix and boleto, not cards, so a card-only payout pushes the contractor toward an ATM withdrawal and its fees.",[11,11101,11102,11103,11105,11106,11109],{},"Many platforms offer both and let the contractor choose. The ",[136,11104,9269],{"href":1221}," covers the Pix side in detail, and ",[136,11107,11108],{"href":5852},"USDC to BRL routes"," compares cash-out options.",[18,11111,11113],{"id":11112},"card-or-local-payout-how-to-decide","Card or local payout: how to decide",[39,11115,11116,11126],{},[42,11117,11118],{},[45,11119,11120,11123],{},[48,11121,11122],{},"Recipient need",[48,11124,11125],{},"Better fit",[61,11127,11128,11136,11144,11152,11159,11167],{},[45,11129,11130,11133],{},[66,11131,11132],{},"Pays for software, ads, or travel in USD",[66,11134,11135],{},"Virtual card",[45,11137,11138,11141],{},[66,11139,11140],{},"Wants to hold dollars in a high-inflation economy",[66,11142,11143],{},"Virtual card or USD stablecoin balance",[45,11145,11146,11149],{},[66,11147,11148],{},"Pays rent, bills, or local suppliers",[66,11150,11151],{},"Local bank payout (Pix, SPEI, Transfers 3.0)",[45,11153,11154,11156],{},[66,11155,9251],{},[66,11157,11158],{},"Local bank payout; ATM withdrawals on a card carry fees",[45,11160,11161,11164],{},[66,11162,11163],{},"One-time vendor payment with a spend cap",[66,11165,11166],{},"Single-use virtual card",[45,11168,11169,11172],{},[66,11170,11171],{},"Company needs a per-payment spending restriction",[66,11173,11135],{},[18,11175,11177],{"id":11176},"what-to-watch-before-launching","What to watch before launching",[171,11179,11180,11186,11192,11201,11207],{},[148,11181,11182,11185],{},[119,11183,11184],{},"Card acceptance in the recipient's country."," Online acceptance is near universal. In-person acceptance for foreign-issued cards varies, and some local merchants route only domestic cards.",[148,11187,11188,11191],{},[119,11189,11190],{},"Local tax on cross-border card spend."," Some countries tax foreign-currency card spend by residents. Argentina, for example, applies a 30 percent income tax withholding to foreign-currency card spend paid in pesos. Check the rules for the recipient's country before choosing a card as the default.",[148,11193,11194,11197,11198,11200],{},[119,11195,11196],{},"KYC depth."," A card that can spend thousands a month needs full cardholder verification. The ",[136,11199,5715],{"href":5714}," covers what the sponsor bank will require.",[148,11202,11203,11206],{},[119,11204,11205],{},"Program limits."," Sponsor banks set caps on load amounts and cardholder countries. Ask for the country list first.",[148,11208,11209,11212],{},[119,11210,11211],{},"Switching cost."," Card numbers get saved at merchants and tied to subscriptions, so moving a program to another provider later means reissuing every card and asking every recipient to update them. Choose the provider as if you will keep it.",[18,11214,5747],{"id":5746},[11,11216,11217,11218,11221,11222,11225,11226,227],{},"Continue with ",[136,11219,11220],{"href":9322},"stablecoin cards in Latin America"," for country-specific rules, or go to the ",[136,11223,11224],{"href":5829},"developer's guide to issuing stablecoin cards through an API",". If your recipients mostly need money in a bank account, start with the ",[136,11227,1211],{"href":1210},[11,11229,11230],{},[324,11231,326],{},{"title":328,"searchDepth":329,"depth":329,"links":11233},[11234,11235,11236,11237,11238,11239,11240],{"id":10893,"depth":329,"text":10894},{"id":10932,"depth":329,"text":10933},{"id":11035,"depth":329,"text":11036},{"id":11051,"depth":329,"text":11052},{"id":11112,"depth":329,"text":11113},{"id":11176,"depth":329,"text":11177},{"id":5746,"depth":329,"text":5747},"2026-09-10","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.",[11244,11247,11250,11253,11256],{"q":11245,"a":11246},"What is a stablecoin-funded virtual card?","A stablecoin-funded virtual card is a Visa or Mastercard card number with no plastic, whose balance is funded from a stablecoin such as USDC instead of a bank deposit. The recipient uses it online or through Apple Pay or Google Pay, and the card program converts the stablecoin into the merchant's currency at the moment of purchase.",{"q":11248,"a":11249},"Do I need to pre-fund local bank accounts to issue virtual cards internationally?","No. A virtual card is funded from the program's balance, not from a bank account in the recipient's country, so a company can issue cards to people in Brazil, Mexico, or the Philippines without opening accounts there. With stablecoin funding, the program balance itself can be topped up from a USDC wallet in minutes, any day of the week, instead of waiting for a cross-border wire.",{"q":11251,"a":11252},"How do stablecoin-funded virtual cards handle FX and settlement?","The card is usually denominated in US dollars and funded 1:1 from a dollar stablecoin, so there is no FX on the funding leg. When the recipient spends in another currency, the card network converts at its daily rate and the issuer may add a foreign transaction fee. On the back end, the program settles with the network in fiat or, where Visa or Mastercard support it, in USDC.",{"q":11254,"a":11255},"Can businesses pay international contractors with stablecoin-backed cards?","Yes. A business onboards the contractor through KYC, issues a virtual card, and loads each payment from its stablecoin balance, and the contractor spends it wherever the card network is accepted. Cards work well for online and card-accepting spend; contractors who need money for rent, bills, or local transfers are usually better served by a payout to a local bank account.",{"q":11257,"a":11258},"What are the advantages of stablecoin virtual cards over traditional ones for cross-border payouts?","Funding moves in minutes and on weekends instead of in one to five business days, the company can top up just in time instead of parking cash in the issuer account, and one stablecoin balance can fund cards in every country. The card leg itself, including acceptance, disputes, and FX at the point of sale, works the same as a traditional virtual card.",{"author":361},"---\ntitle: \"Stablecoin-funded virtual cards vs. traditional virtual cards for cross-border payouts\"\nseoTitle: \"Stablecoin virtual cards for cross-border payouts\"\ndescription: \"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.\"\ndate: \"2026-09-10\"\nupdated: \"2026-09-21\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a stablecoin-funded virtual card?\"\n    a: \"A stablecoin-funded virtual card is a Visa or Mastercard card number with no plastic, whose balance is funded from a stablecoin such as USDC instead of a bank deposit. The recipient uses it online or through Apple Pay or Google Pay, and the card program converts the stablecoin into the merchant's currency at the moment of purchase.\"\n  - q: \"Do I need to pre-fund local bank accounts to issue virtual cards internationally?\"\n    a: \"No. A virtual card is funded from the program's balance, not from a bank account in the recipient's country, so a company can issue cards to people in Brazil, Mexico, or the Philippines without opening accounts there. With stablecoin funding, the program balance itself can be topped up from a USDC wallet in minutes, any day of the week, instead of waiting for a cross-border wire.\"\n  - q: \"How do stablecoin-funded virtual cards handle FX and settlement?\"\n    a: \"The card is usually denominated in US dollars and funded 1:1 from a dollar stablecoin, so there is no FX on the funding leg. When the recipient spends in another currency, the card network converts at its daily rate and the issuer may add a foreign transaction fee. On the back end, the program settles with the network in fiat or, where Visa or Mastercard support it, in USDC.\"\n  - q: \"Can businesses pay international contractors with stablecoin-backed cards?\"\n    a: \"Yes. A business onboards the contractor through KYC, issues a virtual card, and loads each payment from its stablecoin balance, and the contractor spends it wherever the card network is accepted. Cards work well for online and card-accepting spend; contractors who need money for rent, bills, or local transfers are usually better served by a payout to a local bank account.\"\n  - q: \"What are the advantages of stablecoin virtual cards over traditional ones for cross-border payouts?\"\n    a: \"Funding moves in minutes and on weekends instead of in one to five business days, the company can top up just in time instead of parking cash in the issuer account, and one stablecoin balance can fund cards in every country. The card leg itself, including acceptance, disputes, and FX at the point of sale, works the same as a traditional virtual card.\"\n---\n\n*Reading time: about 7 minutes.*\n\n**Summary:** A stablecoin-funded virtual card is a Visa or Mastercard card number, with no plastic, whose balance is funded from a stablecoin such as USDC instead of a bank deposit. Companies issue them to pay contractors, vendors, and employees abroad: the recipient spends online or through a mobile wallet, and the program converts the stablecoin to the merchant's currency.\n\nThe card leg is the same as any virtual card. The difference is upstream: how the money gets into the card program, how fast, and how much of it has to sit there in advance.\n\nThis guide is written for operations and finance leads at marketplaces, payroll platforms, and gig-economy companies. For the basics, read [what stablecoin card issuing is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing).\n\n## Why do companies pay with virtual cards instead of wires or ACH?\n\nA wire needs the recipient's bank details, a correspondent chain, and one to five business days. ACH only works inside the US. For a platform paying 3,000 people in 40 countries, both break at scale.\n\nVirtual cards fix four things:\n\n- **Issuance in seconds.** A card number exists the moment the API call returns. No bank details to collect or validate.\n- **Controls per payment.** A card can carry a limit, an expiry date, and a merchant category rule. A wire cannot.\n- **No recipient bank account.** The recipient needs a phone, not a bank relationship. That matters in markets where many adults are unbanked or underbanked.\n- **Clean reconciliation.** One card per contractor or per payment maps each transaction to a person without matching wire references.\n\nThe tradeoff: a card is only a payout if the recipient can spend it. More on that below.\n\n## Stablecoin-funded vs. bank-funded virtual cards\n\nBoth kinds run on Visa or Mastercard and look identical to the recipient. They differ in how the program is funded.\n\n| Dimension | Bank-funded virtual cards | Stablecoin-funded virtual cards |\n|---|---|---|\n| Funding the program | Wire or ACH into the issuer's account | Stablecoin transfer from a wallet |\n| Funding speed | Same day domestically; 1 to 5 business days cross-border | Minutes, including weekends and holidays |\n| Pre-funding requirement | Balance parked in the issuer account ahead of demand, often in each card currency | Top up just in time from a stablecoin treasury |\n| FX on the funding leg | Wire FX and correspondent fees when the treasury is in another currency | None for USD cards funded with USD stablecoins |\n| FX at point of sale | Network rate plus any issuer foreign transaction fee | Same |\n| Settlement finality of funding | Wire recall and ACH return windows | Final once the on-chain transfer confirms |\n| Card-leg disputes | Network rules | Network rules |\n\nTwo rows are the same on purpose. Stablecoins change the funding side. They do not change what happens when a contractor in Lisbon buys a train ticket in euros on a USD card.\n\n## Where stablecoins remove pre-funding\n\nTraditional global payouts carry a quiet cost: cash parked in advance. A company paying people in five countries often keeps a balance in each currency, or a large USD balance at the card issuer, sized for the busiest week of the month. That cash earns little and cannot be used elsewhere.\n\nWith stablecoin funding the treasury stays in one place, a USDC balance, and moves only when a card is loaded or a purchase settles. Because stablecoin transfers settle 24\u002F7, the top-up can happen at 2 a.m. on a Sunday without a banking window.\n\nThe same logic applies to local bank payouts. BlindPay sends stablecoins out as local currency on demand, without pre-funded accounts in each country, which is covered in [stablecoin payouts for marketplaces in Latin America](\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam).\n\n## Walkthrough: paying a contractor in Brazil\n\nTake a US platform paying a designer in Recife USD 2,000 a month.\n\n**Option A: stablecoin-funded virtual card**\n\n1. The platform onboards the designer through KYC. Name, date of birth, tax ID (CPF), and a document check.\n2. The platform issues a USD virtual card with a USD 2,000 monthly limit.\n3. On payday, the program loads USD 2,000 from the platform's USDC balance. No BRL account is needed anywhere.\n4. The designer adds the card to Google Pay the same day.\n5. USD-priced spend (Figma, Adobe, a flight booked in dollars) costs exactly what it says.\n6. Spend in reais at a Recife supermarket is converted by the network at its daily rate, plus any foreign transaction fee set by the issuer.\n\n**Option B: a Pix payout**\n\n1. Same KYC, plus the designer's Pix key or bank details.\n2. The platform sends USDC. BlindPay converts it to BRL and delivers it over Pix, usually within minutes.\n3. The designer has reais in their own bank account and pays rent, bills, and boletos from it.\n\nOption A is better when the designer spends in dollars or wants to keep a dollar balance. Option B is better when the money is for local life. In Brazil, rent, utility bills, and most person-to-person payments run on Pix and boleto, not cards, so a card-only payout pushes the contractor toward an ATM withdrawal and its fees.\n\nMany platforms offer both and let the contractor choose. The [LATAM contractor payroll guide](\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors) covers the Pix side in detail, and [USDC to BRL routes](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026) compares cash-out options.\n\n## Card or local payout: how to decide\n\n| Recipient need | Better fit |\n|---|---|\n| Pays for software, ads, or travel in USD | Virtual card |\n| Wants to hold dollars in a high-inflation economy | Virtual card or USD stablecoin balance |\n| Pays rent, bills, or local suppliers | Local bank payout (Pix, SPEI, Transfers 3.0) |\n| Needs cash | Local bank payout; ATM withdrawals on a card carry fees |\n| One-time vendor payment with a spend cap | Single-use virtual card |\n| Company needs a per-payment spending restriction | Virtual card |\n\n## What to watch before launching\n\n- **Card acceptance in the recipient's country.** Online acceptance is near universal. In-person acceptance for foreign-issued cards varies, and some local merchants route only domestic cards.\n- **Local tax on cross-border card spend.** Some countries tax foreign-currency card spend by residents. Argentina, for example, applies a 30 percent income tax withholding to foreign-currency card spend paid in pesos. Check the rules for the recipient's country before choosing a card as the default.\n- **KYC depth.** A card that can spend thousands a month needs full cardholder verification. The [compliance guide](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance) covers what the sponsor bank will require.\n- **Program limits.** Sponsor banks set caps on load amounts and cardholder countries. Ask for the country list first.\n- **Switching cost.** Card numbers get saved at merchants and tied to subscriptions, so moving a program to another provider later means reissuing every card and asking every recipient to update them. Choose the provider as if you will keep it.\n\n## What to read next\n\nContinue with [stablecoin cards in Latin America](\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america) for country-specific rules, or go to the [developer's guide to issuing stablecoin cards through an API](\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api). If your recipients mostly need money in a bank account, start with the [stablecoin vs SWIFT comparison](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":10871,"description":11242},"Stablecoin virtual cards for cross-border payouts","resources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","CfUVHhljDwdjT8D-9pa9I5VCD58wWxt2mDscU-2zNgw",{"id":11266,"title":11267,"authors":6,"body":11268,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":11484,"description":11485,"extension":342,"faq":11486,"howto":6,"isBlog":359,"isChangelog":359,"meta":11502,"navigation":362,"path":1210,"pillar":359,"products":6,"rawbody":11503,"role":6,"seo":11504,"seoTitle":11505,"stem":11506,"thumbnail":6,"updated":6,"__hash__":11507},"content\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments.md","Stablecoins vs SWIFT for B2B cross-border payments: a real comparison",{"type":8,"value":11269,"toc":11474},[11270,11273,11276,11279,11283,11286,11289,11292,11295,11298,11306,11372,11375,11379,11382,11390,11393,11397,11400,11403,11406,11412,11416,11419,11424,11433,11436,11440,11443,11449,11453,11456,11459,11462,11464,11467],[11,11271,11272],{},"Most \"stablecoins vs SWIFT\" articles are written by people selling one of them. So start with the part that is inconvenient for a stablecoin provider to say: SWIFT works. It has moved trillions of dollars a day for fifty years, every bank on earth speaks it, and SWIFT gpi now lands most payments at the beneficiary bank within 24 hours.",[11,11274,11275],{},"If you are a Fortune 500 treasury moving $50 million between JPMorgan and Deutsche Bank, keep using it.",[11,11277,11278],{},"The comparison gets interesting one step down from that. A SaaS company paying a supplier in Colombia. A marketplace settling with sellers in Brazil. A fund distributing to LPs in Mexico. That is where the rails diverge, and where the numbers stop being close.",[18,11280,11282],{"id":11281},"they-are-not-the-same-kind-of-thing","They are not the same kind of thing",[11,11284,11285],{},"SWIFT is a messaging network. It does not move money. It sends a standardized instruction from your bank to the beneficiary's bank, often through one or two correspondent banks in between, and each bank in the chain updates its own ledger and takes its own fee. The money \"arrives\" when the last bank credits the account.",[11,11287,11288],{},"A stablecoin is a settlement asset. When USDC moves from one address to another, value has moved. There is no instruction waiting for someone to act on it. The transfer is the settlement.",[11,11290,11291],{},"That structural difference explains almost everything in the comparison below. Correspondent chains are why wires are slow, why fees are unpredictable, and why a payment can arrive short with no explanation. A direct settlement asset has none of those properties. It has different ones.",[18,11293,9478],{"id":11294},"cost",[11,11296,11297],{},"The visible wire fee is the small part. A US bank charges $25 to $50 to send. The intermediary bank deducts $10 to $30 nobody told you about. The receiving bank in Brazil or Argentina charges a landing fee and applies its own FX rate, which is typically 2 to 5 percent off mid-market for a corporate receiver. You find out the real cost when the supplier emails to say they got less than the invoice.",[11,11299,11300,11301,4468,11303,11305],{},"A stablecoin payment through a payout API has three costs: the chain fee (sub-cent on Polygon or Base, a few cents on most networks), the FX spread from stablecoin to local currency, and a flat payout fee. The difference is that all three are in the quote before you send. BlindPay itemizes the spread and the payout fee separately on the ",[136,11302,1712],{"href":307},[136,11304,4238],{"href":4237}," walks through why a blended rate hides the real number.",[39,11307,11308,11319],{},[42,11309,11310],{},[45,11311,11312,11314,11317],{},[48,11313],{},[48,11315,11316],{},"SWIFT wire to LATAM",[48,11318,1172],{},[61,11320,11321,11332,11342,11352,11363],{},[45,11322,11323,11326,11329],{},[66,11324,11325],{},"Sending fee",[66,11327,11328],{},"$25 to $50",[66,11330,11331],{},"Small flat fee",[45,11333,11334,11337,11340],{},[66,11335,11336],{},"Intermediary deductions",[66,11338,11339],{},"$10 to $30, unpredictable",[66,11341,9561],{},[45,11343,11344,11346,11349],{},[66,11345,9923],{},[66,11347,11348],{},"2 to 5 percent",[66,11350,11351],{},"Sub-percent, quoted upfront",[45,11353,11354,11357,11360],{},[66,11355,11356],{},"Receiving fee",[66,11358,11359],{},"Common",[66,11361,11362],{},"None over Pix or SPEI",[45,11364,11365,11368,11370],{},[66,11366,11367],{},"Known before sending",[66,11369,3458],{},[66,11371,3424],{},[11,11373,11374],{},"On a $100,000 supplier payment into Mexico, the wire path commonly totals $1,000 to $1,500 once the spread is counted. The stablecoin path is usually a few hundred dollars. Multiply by a monthly payment cycle and you have a line item a CFO will notice.",[18,11376,11378],{"id":11377},"speed","Speed",[11,11380,11381],{},"SWIFT gpi data says 92 percent of payments reach the beneficiary bank within 24 hours. That is true and also misleading. \"Reach the beneficiary bank\" is not \"available to the beneficiary\". Compliance screening at the receiving bank adds a business day in many emerging-market corridors. Send on Friday afternoon and the supplier has money on Tuesday, if nothing gets flagged.",[11,11383,11384,11385,1337,11387,11389],{},"Stablecoin settlement is seconds on-chain. Conversion to local currency is minutes. Pix in Brazil and SPEI in Mexico both run 24\u002F7, so the payout lands at 11pm on a Saturday if that is when you sent it. Colombia and Argentina are a bit slower on the local leg but still same-day. The ",[136,11386,644],{"href":5852},[136,11388,10737],{"href":7229}," route guides have timings per path.",[11,11391,11392],{},"The business impact is not the minutes. It is the working capital. Money that lands in minutes does not need to be sent three days early, so you do not need to pre-fund, and the supplier does not need to price your slowness into their terms.",[18,11394,11396],{"id":11395},"traceability","Traceability",[11,11398,11399],{},"This is where the picture is more even than the marketing suggests.",[11,11401,11402],{},"SWIFT gpi gives you a UETR, a unique end-to-end reference you can track through every bank in the chain. MT103 confirmations prove the payment was made. Auditors know these documents. Your bank knows them. That is a real advantage.",[11,11404,11405],{},"Stablecoin transfers give you a transaction hash on a public ledger. Anyone can verify it. The payout API gives you a status per payment and a webhook when it changes. What it did not historically give you is the bank-side paperwork.",[11,11407,11408,11409,11411],{},"That gap is closing. BlindPay runs SWIFT wires (POBO and COBO) with UETR tracking and MT103 confirmations alongside stablecoin settlement, so for a supplier who still wants a wire, you send one through the same API and get the same documents. The ",[136,11410,4041],{"href":1243}," explains what \"final\" means on each rail.",[18,11413,11415],{"id":11414},"failure-modes","Failure modes",[11,11417,11418],{},"Every rail fails. The question is how.",[11,11420,11421,11423],{},[119,11422,3573],{}," fails slowly and opaquely. A wire gets held for a compliance query at a correspondent bank. Nobody tells you. Ten days later the money comes back minus fees, with a code. Or it arrives short. Or it lands in the wrong account because a BIC was mistyped, and recall is a negotiation.",[11,11425,11426,11429,11430,11432],{},[119,11427,11428],{},"Stablecoin settlement"," fails fast and loudly. The receiving account fails verification and the API returns an error before any money moves. The local rail rejects the payout and you get a webhook with the reason. The on-chain transfer itself is final once confirmed, which is why the receiver check has to happen first. ",[136,11431,735],{"href":734}," is the right thing to worry about, and the answer is that the provider's pre-checks are your recall window.",[11,11434,11435],{},"Fast, loud failure is easier to build around than slow, quiet failure. Your finance team can act on an error in the same hour instead of the same fortnight.",[18,11437,11439],{"id":11438},"compliance","Compliance",[11,11441,11442],{},"Wires are not \"more compliant\" than stablecoin payments. They are more familiar. Both require KYB on your business, KYC on the receiver, sanctions screening, and a record of who paid whom and why.",[11,11444,11445,11446,11448],{},"The difference is where the checks sit. On a wire, they sit inside each bank in the chain and you do not see them. On a stablecoin payout through a licensed provider, they run inside the API flow, and they block the payment before money moves rather than freezing it after. Brazil's Central Bank now licenses virtual asset providers (Resolutions 519 through 521, effective February 2026), the US has the GENIUS Act with Treasury rules out for comment through October 19, 2026, and the EU has MiCA. The ",[136,11447,1036],{"href":1035}," keeps score.",[18,11450,11452],{"id":11451},"when-to-use-which","When to use which",[11,11454,11455],{},"Use SWIFT when the counterparty is a large bank in a major market, the amount is large enough that a 24 hour delay costs nothing, and the receiver insists on an MT103. Between two G10 banks, a wire is fine.",[11,11457,11458],{},"Use stablecoin settlement when the money is going into Latin America or another market where correspondent chains are long, when speed changes the business (payroll, marketplace payouts, supplier terms), when you want the cost known before you send, or when you are sending many mid-sized payments rather than one large one.",[11,11460,11461],{},"Use both when your suppliers are mixed. A single API that settles in stablecoins where it is better and sends a wire where it is required is the setup most companies land on.",[18,11463,312],{"id":311},[11,11465,11466],{},"Take last month's outgoing international payments. For each one, write down what you paid to send, what the receiver actually got, and how many days it took. Then price the same payments through a stablecoin quote. If the total is not materially lower and faster for your LATAM corridors, stay on wires. For most LATAM corridors it is, and by a lot.",[11,11468,11469,1341,11471,227],{},[136,11470,4595],{"href":1335},[136,11472,1331],{"href":648,"rel":11473},[414],{"title":328,"searchDepth":329,"depth":329,"links":11475},[11476,11477,11478,11479,11480,11481,11482,11483],{"id":11281,"depth":329,"text":11282},{"id":11294,"depth":329,"text":9478},{"id":11377,"depth":329,"text":11378},{"id":11395,"depth":329,"text":11396},{"id":11414,"depth":329,"text":11415},{"id":11438,"depth":329,"text":11439},{"id":11451,"depth":329,"text":11452},{"id":311,"depth":329,"text":312},"2026-09-05","Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes.",[11487,11490,11493,11496,11499],{"q":11488,"a":11489},"Are stablecoins replacing SWIFT?","No. SWIFT is a messaging network that tells banks to move money. Stablecoins are a settlement asset that moves value directly. For many corridors, especially into Latin America, stablecoin settlement is now faster and cheaper, but SWIFT remains the default for large corporate treasury flows between major banks.",{"q":11491,"a":11492},"How much cheaper is a stablecoin payment than a SWIFT wire?","A typical SWIFT wire into an emerging market costs $40 to $80 in fees plus a 2 to 5 percent FX spread and settles in 1 to 5 business days. A stablecoin payment with local payout usually costs a sub-percent spread plus a small flat fee and settles in minutes. On a $100,000 payment to Mexico the difference is often $750 to $1,000.",{"q":11494,"a":11495},"Can I track a stablecoin payment like a SWIFT gpi payment?","Yes, and often better. The on-chain transfer has a public transaction hash, and payout APIs return a status per payout with webhooks. For the bank leg, providers like BlindPay also run SWIFT (POBO\u002FCOBO) wires with UETR tracking and MT103 confirmations, so you get both.",{"q":11497,"a":11498},"Is a stablecoin payment reversible if I make a mistake?","The on-chain transfer is final once confirmed. Good providers verify the receiving account before the money moves, and the fiat payout leg follows the rules of the local rail. Treat the receiver check as your recall window.",{"q":11500,"a":11501},"Do I need a crypto wallet to pay suppliers with stablecoins?","No. With a stablecoin payments API you can fund from a bank account into a virtual account, and the supplier receives local currency in their bank. The stablecoin is the settlement layer in the middle.",{"author":361},"---\ntitle: \"Stablecoins vs SWIFT for B2B cross-border payments: a real comparison\"\nseoTitle: \"Stablecoins vs SWIFT for B2B payments\"\ndescription: \"Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes.\"\ndate: \"2026-09-05\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Are stablecoins replacing SWIFT?\"\n    a: \"No. SWIFT is a messaging network that tells banks to move money. Stablecoins are a settlement asset that moves value directly. For many corridors, especially into Latin America, stablecoin settlement is now faster and cheaper, but SWIFT remains the default for large corporate treasury flows between major banks.\"\n  - q: \"How much cheaper is a stablecoin payment than a SWIFT wire?\"\n    a: \"A typical SWIFT wire into an emerging market costs $40 to $80 in fees plus a 2 to 5 percent FX spread and settles in 1 to 5 business days. A stablecoin payment with local payout usually costs a sub-percent spread plus a small flat fee and settles in minutes. On a $100,000 payment to Mexico the difference is often $750 to $1,000.\"\n  - q: \"Can I track a stablecoin payment like a SWIFT gpi payment?\"\n    a: \"Yes, and often better. The on-chain transfer has a public transaction hash, and payout APIs return a status per payout with webhooks. For the bank leg, providers like BlindPay also run SWIFT (POBO\u002FCOBO) wires with UETR tracking and MT103 confirmations, so you get both.\"\n  - q: \"Is a stablecoin payment reversible if I make a mistake?\"\n    a: \"The on-chain transfer is final once confirmed. Good providers verify the receiving account before the money moves, and the fiat payout leg follows the rules of the local rail. Treat the receiver check as your recall window.\"\n  - q: \"Do I need a crypto wallet to pay suppliers with stablecoins?\"\n    a: \"No. With a stablecoin payments API you can fund from a bank account into a virtual account, and the supplier receives local currency in their bank. The stablecoin is the settlement layer in the middle.\"\n---\n\nMost \"stablecoins vs SWIFT\" articles are written by people selling one of them. So start with the part that is inconvenient for a stablecoin provider to say: SWIFT works. It has moved trillions of dollars a day for fifty years, every bank on earth speaks it, and SWIFT gpi now lands most payments at the beneficiary bank within 24 hours.\n\nIf you are a Fortune 500 treasury moving $50 million between JPMorgan and Deutsche Bank, keep using it.\n\nThe comparison gets interesting one step down from that. A SaaS company paying a supplier in Colombia. A marketplace settling with sellers in Brazil. A fund distributing to LPs in Mexico. That is where the rails diverge, and where the numbers stop being close.\n\n## They are not the same kind of thing\n\nSWIFT is a messaging network. It does not move money. It sends a standardized instruction from your bank to the beneficiary's bank, often through one or two correspondent banks in between, and each bank in the chain updates its own ledger and takes its own fee. The money \"arrives\" when the last bank credits the account.\n\nA stablecoin is a settlement asset. When USDC moves from one address to another, value has moved. There is no instruction waiting for someone to act on it. The transfer is the settlement.\n\nThat structural difference explains almost everything in the comparison below. Correspondent chains are why wires are slow, why fees are unpredictable, and why a payment can arrive short with no explanation. A direct settlement asset has none of those properties. It has different ones.\n\n## Cost\n\nThe visible wire fee is the small part. A US bank charges $25 to $50 to send. The intermediary bank deducts $10 to $30 nobody told you about. The receiving bank in Brazil or Argentina charges a landing fee and applies its own FX rate, which is typically 2 to 5 percent off mid-market for a corporate receiver. You find out the real cost when the supplier emails to say they got less than the invoice.\n\nA stablecoin payment through a payout API has three costs: the chain fee (sub-cent on Polygon or Base, a few cents on most networks), the FX spread from stablecoin to local currency, and a flat payout fee. The difference is that all three are in the quote before you send. BlindPay itemizes the spread and the payout fee separately on the [pricing page](\u002Fpricing), and the [pricing explainer](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) walks through why a blended rate hides the real number.\n\n| | SWIFT wire to LATAM | Stablecoin plus local payout |\n| --- | --- | --- |\n| Sending fee | $25 to $50 | Small flat fee |\n| Intermediary deductions | $10 to $30, unpredictable | None |\n| FX spread | 2 to 5 percent | Sub-percent, quoted upfront |\n| Receiving fee | Common | None over Pix or SPEI |\n| Known before sending | No | Yes |\n\nOn a $100,000 supplier payment into Mexico, the wire path commonly totals $1,000 to $1,500 once the spread is counted. The stablecoin path is usually a few hundred dollars. Multiply by a monthly payment cycle and you have a line item a CFO will notice.\n\n## Speed\n\nSWIFT gpi data says 92 percent of payments reach the beneficiary bank within 24 hours. That is true and also misleading. \"Reach the beneficiary bank\" is not \"available to the beneficiary\". Compliance screening at the receiving bank adds a business day in many emerging-market corridors. Send on Friday afternoon and the supplier has money on Tuesday, if nothing gets flagged.\n\nStablecoin settlement is seconds on-chain. Conversion to local currency is minutes. Pix in Brazil and SPEI in Mexico both run 24\u002F7, so the payout lands at 11pm on a Saturday if that is when you sent it. Colombia and Argentina are a bit slower on the local leg but still same-day. The [USDC to BRL](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026) and [USDC to MXN](\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026) route guides have timings per path.\n\nThe business impact is not the minutes. It is the working capital. Money that lands in minutes does not need to be sent three days early, so you do not need to pre-fund, and the supplier does not need to price your slowness into their terms.\n\n## Traceability\n\nThis is where the picture is more even than the marketing suggests.\n\nSWIFT gpi gives you a UETR, a unique end-to-end reference you can track through every bank in the chain. MT103 confirmations prove the payment was made. Auditors know these documents. Your bank knows them. That is a real advantage.\n\nStablecoin transfers give you a transaction hash on a public ledger. Anyone can verify it. The payout API gives you a status per payment and a webhook when it changes. What it did not historically give you is the bank-side paperwork.\n\nThat gap is closing. BlindPay runs SWIFT wires (POBO and COBO) with UETR tracking and MT103 confirmations alongside stablecoin settlement, so for a supplier who still wants a wire, you send one through the same API and get the same documents. The [settlement finality guide](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality) explains what \"final\" means on each rail.\n\n## Failure modes\n\nEvery rail fails. The question is how.\n\n**SWIFT** fails slowly and opaquely. A wire gets held for a compliance query at a correspondent bank. Nobody tells you. Ten days later the money comes back minus fees, with a code. Or it arrives short. Or it lands in the wrong account because a BIC was mistyped, and recall is a negotiation.\n\n**Stablecoin settlement** fails fast and loudly. The receiving account fails verification and the API returns an error before any money moves. The local rail rejects the payout and you get a webhook with the reason. The on-chain transfer itself is final once confirmed, which is why the receiver check has to happen first. [Reversibility](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) is the right thing to worry about, and the answer is that the provider's pre-checks are your recall window.\n\nFast, loud failure is easier to build around than slow, quiet failure. Your finance team can act on an error in the same hour instead of the same fortnight.\n\n## Compliance\n\nWires are not \"more compliant\" than stablecoin payments. They are more familiar. Both require KYB on your business, KYC on the receiver, sanctions screening, and a record of who paid whom and why.\n\nThe difference is where the checks sit. On a wire, they sit inside each bank in the chain and you do not see them. On a stablecoin payout through a licensed provider, they run inside the API flow, and they block the payment before money moves rather than freezing it after. Brazil's Central Bank now licenses virtual asset providers (Resolutions 519 through 521, effective February 2026), the US has the GENIUS Act with Treasury rules out for comment through October 19, 2026, and the EU has MiCA. The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) keeps score.\n\n## When to use which\n\nUse SWIFT when the counterparty is a large bank in a major market, the amount is large enough that a 24 hour delay costs nothing, and the receiver insists on an MT103. Between two G10 banks, a wire is fine.\n\nUse stablecoin settlement when the money is going into Latin America or another market where correspondent chains are long, when speed changes the business (payroll, marketplace payouts, supplier terms), when you want the cost known before you send, or when you are sending many mid-sized payments rather than one large one.\n\nUse both when your suppliers are mixed. A single API that settles in stablecoins where it is better and sends a wire where it is required is the setup most companies land on.\n\n## What to do next\n\nTake last month's outgoing international payments. For each one, write down what you paid to send, what the receiver actually got, and how many days it took. Then price the same payments through a stablecoin quote. If the total is not materially lower and faster for your LATAM corridors, stay on wires. For most LATAM corridors it is, and by a lot.\n\n[See coverage by country](\u002Fcoverage), or [start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction).\n",{"title":11267,"description":11485},"Stablecoins vs SWIFT for B2B payments","resources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","KXuDqBdngiWm4F3X3kqOy1JMsBkcDlo80l81-SXvRlc",{"id":11509,"title":11510,"authors":6,"body":11511,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":10050,"description":11825,"extension":342,"faq":11826,"howto":6,"isBlog":359,"isChangelog":359,"meta":11842,"navigation":362,"path":7251,"pillar":359,"products":6,"rawbody":11843,"role":6,"seo":11844,"seoTitle":11845,"stem":11846,"thumbnail":6,"updated":6,"__hash__":11847},"content\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026.md","USDC to ARS in 2026: routes, fees, and rules compared",{"type":8,"value":11512,"toc":11814},[11513,11520,11523,11527,11535,11541,11547,11553,11557,11642,11647,11651,11654,11668,11671,11674,11678,11681,11684,11688,11717,11721,11724,11738,11743,11747,11750,11754,11772,11774,11810],[11,11514,11515,11516,227],{},"There are four practical routes from USDC to Argentine pesos in 2026: send through a stablecoin payout API that delivers pesos directly, sell on an Argentine exchange and withdraw to a bank or wallet, trade peer-to-peer, or use a global exchange with an ARS ramp. They differ on fees, speed, KYC, and who carries the regulatory burden, and the right one depends on whether you are an individual cashing out or a business paying people at scale. You can see the live USDC to ARS rate on our ",[136,11517,11519],{"href":11518},"\u002Fusdc-to-ars","corridor page",[11,11521,11522],{},"The backdrop matters more here than in most corridors: Argentines have used stablecoins for years as a hedge against peso inflation and devaluation, and by mid-2025 stablecoin purchases made up over half of all exchange transactions involving the Argentine peso, according to Chainalysis's 2025 Latin America crypto adoption report. Every serious USDC-to-ARS route ends in a peso transfer over Transfers 3.0, the BCRA's instant payment scheme. And the exchange rate environment changed sharply in April 2025, when most of the \"cepo cambiario\" currency controls were lifted, so the honest cost comparison in 2026 looks different than it did two years ago.",[18,11524,11526],{"id":11525},"what-are-the-four-routes-from-usdc-to-ars","What are the four routes from USDC to ARS?",[11,11528,11529,11532,11533,227],{},[119,11530,11531],{},"Route 1: Stablecoin payout API."," A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: ",[136,11534,1492],{"href":618},[11,11536,11537,11540],{},[119,11538,11539],{},"Route 2: Argentine exchange off-ramp."," Send USDC to a local exchange, sell for ARS, withdraw to a bank account or wallet. Trading fees typically run 0.1 to 1 percent, plus network and withdrawal costs. KYC (DNI or CUIT) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.",[11,11542,11543,11546],{},[119,11544,11545],{},"Route 3: P2P marketplaces."," Trade USDC directly with a counterparty who sends you pesos. This has deep roots in Argentina, where informal cash exchange (\"cuevas\") long predates crypto P2P. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.",[11,11548,11549,11552],{},[119,11550,11551],{},"Route 4: Global exchange with an ARS ramp."," Some global exchanges support ARS deposits and withdrawals. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and ARS pairs get thinner liquidity than local venues, with wider spreads during volatile sessions.",[18,11554,11556],{"id":11555},"how-do-the-routes-compare","How do the routes compare?",[39,11558,11559,11576],{},[42,11560,11561],{},[45,11562,11563,11566,11569,11571,11574],{},[48,11564,11565],{},"Route",[48,11567,11568],{},"Speed (end to end)",[48,11570,1100],{},[48,11572,11573],{},"KYC",[48,11575,785],{},[61,11577,11578,11594,11611,11627],{},[45,11579,11580,11583,11585,11588,11591],{},[66,11581,11582],{},"Payout API",[66,11584,1175],{},[66,11586,11587],{},"Quoted FX rate + provider fee",[66,11589,11590],{},"Provider-run, per receiver",[66,11592,11593],{},"Businesses paying at scale",[45,11595,11596,11599,11602,11605,11608],{},[66,11597,11598],{},"Argentine exchange",[66,11600,11601],{},"Minutes to hours",[66,11603,11604],{},"0.1-1% trade + withdrawal",[66,11606,11607],{},"Full, per account",[66,11609,11610],{},"Individuals, occasional cash-out",[45,11612,11613,11616,11618,11621,11624],{},[66,11614,11615],{},"P2P marketplace",[66,11617,11601],{},[66,11619,11620],{},"Spread-dependent",[66,11622,11623],{},"Varies by venue",[66,11625,11626],{},"Small amounts, no business trail",[45,11628,11629,11632,11634,11637,11639],{},[66,11630,11631],{},"Global exchange + ARS ramp",[66,11633,11601],{},[66,11635,11636],{},"Stacked (trade + FX + withdrawal)",[66,11638,11607],{},[66,11640,11641],{},"Funds already on the exchange",[11,11643,11644,11645,227],{},"Compare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. This matters more in Argentina than in most corridors, because spreads between venues can move with the day's exchange rate volatility. Provider pricing models are compared in ",[136,11646,9869],{"href":771},[18,11648,11650],{"id":11649},"what-are-argentinas-rules-for-usdc-to-ars-in-2026","What are Argentina's rules for USDC to ARS in 2026?",[11,11652,11653],{},"Two layers, as of 2026:",[171,11655,11656,11662],{},[148,11657,11658,11661],{},[119,11659,11660],{},"Law 27,739 (2024)"," created Argentina's registration regime for Proveedores de Servicios de Activos Virtuales (PSAV), the entities that exchange, transfer, or custody virtual assets on behalf of others, in line with FATF Recommendation 15. The Comisión Nacional de Valores (CNV) is the supervisor, and CNV General Resolution 1058 sets the registration procedure through the government's online filing platform (TAD).",[148,11663,11664,11667],{},[119,11665,11666],{},"Tax",": AFIP taxes crypto disposals for individuals and companies, and reporting obligations continue to expand as Argentina implements the OECD's Crypto-Asset Reporting Framework alongside its existing income and personal-assets tax rules. Track cost basis in pesos at acquisition and disposal.",[11,11669,11670],{},"Worth stating plainly: the PSAV framework exists in law, but enforcement is still catching up to it. As of early September 2026, the CNV's own PSAV Registry lists zero registered legal entities and zero registered natural persons. That does not mean virtual asset activity in Argentina is unregulated on paper, but it does mean the registration regime has not yet produced a visible list of compliant providers the way, for example, Brazil's BCB authorization regime has started to. Businesses choosing a provider should ask directly about compliance posture rather than checking a public registry.",[11,11672,11673],{},"One operational rule dominates day-to-day payouts: Argentine transfers verify the receiver. A CBU (Clave Bancaria Uniforme) or CVU (Clave Virtual Uniforme), often reached through a shorter alias, must resolve to an account whose holder name matches the beneficiary on file, or the transfer is rejected. Mismatched beneficiary data is the top cause of failed Argentina payouts on any route, the same failure mode Brazil's Pix has.",[18,11675,11677],{"id":11676},"is-the-cepo-cambiario-still-a-factor-for-these-routes","Is the cepo cambiario still a factor for these routes?",[11,11679,11680],{},"Less than it was. For over a decade, Argentina's currency controls (the \"cepo cambiario\") forced a gap between the official peso rate and parallel rates like the \"dólar blue,\" and that gap is a large part of why Argentines turned to stablecoins in the first place. That changed on April 14, 2025, when the government lifted most restrictions on buying foreign currency for individuals and companies and moved to a single, floating exchange rate inside a band the BCRA has adjusted monthly since, based on recent inflation data.",[11,11682,11683],{},"The practical effect by late August 2026: the gap between the blue-market rate and the official rate has narrowed to roughly one to two percent, down from over 100 percent at points during 2023 and 2024. That is a genuinely different environment for pricing a USDC-to-ARS conversion than the corridor had for most of its history. It is not a guarantee of stability. Some restrictions on corporate profit repatriation and legacy debt payments eased on a slower schedule than the retail rules, the band itself can move, and a change in policy could reopen the gap. Treat any specific number here as a snapshot, not a permanent fact, and check the current BCRA framework before relying on it for a live conversion.",[18,11685,11687],{"id":11686},"which-route-fits-which-business","Which route fits which business?",[171,11689,11690,11696,11702,11708],{},[148,11691,11692,11695],{},[119,11693,11694],{},"Freelancer receiving USDC occasionally",": an Argentine exchange account is enough. Watch the spread and keep records for AFIP.",[148,11697,11698,11701],{},[119,11699,11700],{},"Company paying 1 or 2 Argentine contractors",": an exchange works but does not scale; every payment is manual and the compliance trail is yours to build.",[148,11703,11704,11707],{},[119,11705,11706],{},"Company paying tens to thousands of receivers"," (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, name\u002FCBU or CVU matching, and delivery over Transfers 3.0 happen inside one API call.",[148,11709,11710,11713,11714,11716],{},[119,11711,11712],{},"Treasury converting its own balance",": an exchange or OTC desk for large one-off conversions; an API with ",[136,11715,632],{"href":138}," if conversions recur as part of a product flow.",[18,11718,11720],{"id":11719},"which-network-should-you-send-usdc-on","Which network should you send USDC on?",[11,11722,11723],{},"USDC is issued natively on multiple blockchains, and the network choice affects cost and settlement time on every route. Ethereum mainnet carries the deepest liquidity but the highest fees, often dollars per transfer at busy times. Base, Polygon, Arbitrum, and Solana move the same USDC for cents and settle in seconds to minutes. Two practical rules:",[171,11725,11726,11732],{},[148,11727,11728,11731],{},[119,11729,11730],{},"Match the destination's supported networks."," An Argentine exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.",[148,11733,11734,11737],{},[119,11735,11736],{},"Prefer a cheap network your counterparty supports."," For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same ARS amount regardless.",[11,11739,11740,11741,227],{},"The token is worth one dollar on every chain; only the transport differs. More on how the token itself works: ",[136,11742,9801],{"href":9800},[18,11744,11746],{"id":11745},"where-these-routes-fall-short","Where these routes fall short",[11,11748,11749],{},"Honest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow, and Argentina's long informal-exchange culture makes counterparty risk easy to underestimate. Global exchanges quote thin ARS liquidity, and spreads widen fastest exactly when the peso is moving. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route removes Argentina's tax reporting obligations, or shields a business from exchange rate policy changing again.",[18,11751,11753],{"id":11752},"how-blindpay-handles-usdc-to-ars","How BlindPay handles USDC to ARS",[11,11755,11756,11757,11760,11761,11764,11765,11767,11768,227],{},"BlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over Transfers 3.0, usually within minutes. Receiver verification (including CBU\u002FCVU and name matching), sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the ",[136,11758,11759],{"href":11518},"USDC to ARS page",". The same API pays out over Pix, SPEI, PSE, SEPA, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in ",[136,11762,11763],{"href":1335},"100+ countries",", USDT works the same way, and ",[136,11766,1340],{"href":307}," is public. Agents and automated systems that need to route this corridor programmatically can start from ",[136,11769,11771],{"href":11770},"\u002Fagentic-payments","agentic payments",[18,11773,1350],{"id":1349},[11,11775,11776,11777,11782,11783,11788,11789,11794,11795,11800,11801,11806,11807,11809],{},"Rail and regulatory facts from primary sources: the BCRA's Transfers 3.0 documentation (",[136,11778,11781],{"href":11779,"rel":11780},"https:\u002F\u002Fwww.bcra.gob.ar\u002Fen\u002Ftransfers-3-0\u002F",[414],"bcra.gob.ar","), Law 27,739 and the PSAV framework via the CNV (",[136,11784,11787],{"href":11785,"rel":11786},"https:\u002F\u002Fwww.argentina.gob.ar\u002Fnoticias\u002Fregulacion-de-los-proveedores-de-servicios-de-activos-virtuales-psav",[414],"argentina.gob.ar","), the CNV's live PSAV Registry count (",[136,11790,11793],{"href":11791,"rel":11792},"https:\u002F\u002Fwww.cnv.gov.ar\u002FSitioWeb\u002FProveedoresServiciosActivosVirtuales\u002FRegistrosPSAV",[414],"cnv.gov.ar",", checked early September 2026), and the April 2025 currency control changes as summarized by the U.S. International Trade Administration (",[136,11796,11799],{"href":11797,"rel":11798},"https:\u002F\u002Fwww.trade.gov\u002Fmarket-intelligence\u002Fargentina-eliminates-capital-controls-and-payment-timelines",[414],"trade.gov","). The stablecoin adoption statistic is from Chainalysis's 2025 Latin America crypto adoption report (",[136,11802,11805],{"href":11803,"rel":11804},"https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flatin-america-crypto-adoption-2025\u002F",[414],"chainalysis.com","). Exchange fee ranges reflect published fee schedules of major Argentine venues as of 2026; live BlindPay FX quotes are on the ",[136,11808,11519],{"href":11518},". Regulatory and exchange-rate status described as of late August 2026 and subject to change.",[11,11811,11812],{},[324,11813,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":11815},[11816,11817,11818,11819,11820,11821,11822,11823,11824],{"id":11525,"depth":329,"text":11526},{"id":11555,"depth":329,"text":11556},{"id":11649,"depth":329,"text":11650},{"id":11676,"depth":329,"text":11677},{"id":11686,"depth":329,"text":11687},{"id":11719,"depth":329,"text":11720},{"id":11745,"depth":329,"text":11746},{"id":11752,"depth":329,"text":11753},{"id":1349,"depth":329,"text":1350},"Four ways to convert USDC to Argentine pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges. Fees, speed, KYC, and rules.",[11827,11830,11833,11836,11839],{"q":11828,"a":11829},"What is the cheapest way to convert USDC to ARS?","For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Argentine exchanges are usually cheapest, with trading fees around 0.1 to 1 percent plus a small transfer cost.",{"q":11831,"a":11832},"How fast does a USDC to ARS conversion arrive?","Over Transfers 3.0, seconds to minutes. The BCRA's instant transfer scheme credits funds in about 15 seconds, 24 hours a day, so end-to-end time is dominated by the conversion step ahead of it, typically a few minutes on exchanges and payout APIs.",{"q":11834,"a":11835},"Is converting USDC to ARS legal in Argentina?","Yes. Law 27,739 (2024) created a registration regime for Proveedores de Servicios de Activos Virtuales (PSAV), supervised by the Comisión Nacional de Valores (CNV). Providers of virtual asset services to Argentines are expected to register; individuals also owe tax on crypto gains under AFIP rules.",{"q":11837,"a":11838},"Is Argentina's cepo cambiario still in effect in 2026?","Mostly no. The government lifted most currency purchase restrictions for individuals and companies on April 14, 2025, moving to a single, floating exchange rate inside a band the BCRA adjusts monthly. Some restrictions on corporate profit repatriation and legacy debt eased on a slower timeline; check current BCRA rules before assuming full convertibility for a specific case.",{"q":11840,"a":11841},"Why do Transfers 3.0 payouts get rejected?","The most common reason is a mismatch between the receiver's name and the CBU or CVU (or alias) on the receiving account. Argentine institutions verify the beneficiary's name against the account holder before crediting, so accurate receiver data is a hard requirement, the same way Pix works in Brazil.",{"author":361},"---\ntitle: \"USDC to ARS in 2026: routes, fees, and rules compared\"\nseoTitle: \"USDC to ARS in 2026: routes, fees, and rules\"\ndescription: \"Four ways to convert USDC to Argentine pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges. Fees, speed, KYC, and rules.\"\ndate: \"2026-09-01\"\nauthor: \"BlindPay Team\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is the cheapest way to convert USDC to ARS?\"\n    a: \"For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Argentine exchanges are usually cheapest, with trading fees around 0.1 to 1 percent plus a small transfer cost.\"\n  - q: \"How fast does a USDC to ARS conversion arrive?\"\n    a: \"Over Transfers 3.0, seconds to minutes. The BCRA's instant transfer scheme credits funds in about 15 seconds, 24 hours a day, so end-to-end time is dominated by the conversion step ahead of it, typically a few minutes on exchanges and payout APIs.\"\n  - q: \"Is converting USDC to ARS legal in Argentina?\"\n    a: \"Yes. Law 27,739 (2024) created a registration regime for Proveedores de Servicios de Activos Virtuales (PSAV), supervised by the Comisión Nacional de Valores (CNV). Providers of virtual asset services to Argentines are expected to register; individuals also owe tax on crypto gains under AFIP rules.\"\n  - q: \"Is Argentina's cepo cambiario still in effect in 2026?\"\n    a: \"Mostly no. The government lifted most currency purchase restrictions for individuals and companies on April 14, 2025, moving to a single, floating exchange rate inside a band the BCRA adjusts monthly. Some restrictions on corporate profit repatriation and legacy debt eased on a slower timeline; check current BCRA rules before assuming full convertibility for a specific case.\"\n  - q: \"Why do Transfers 3.0 payouts get rejected?\"\n    a: \"The most common reason is a mismatch between the receiver's name and the CBU or CVU (or alias) on the receiving account. Argentine institutions verify the beneficiary's name against the account holder before crediting, so accurate receiver data is a hard requirement, the same way Pix works in Brazil.\"\n---\n\nThere are four practical routes from USDC to Argentine pesos in 2026: send through a stablecoin payout API that delivers pesos directly, sell on an Argentine exchange and withdraw to a bank or wallet, trade peer-to-peer, or use a global exchange with an ARS ramp. They differ on fees, speed, KYC, and who carries the regulatory burden, and the right one depends on whether you are an individual cashing out or a business paying people at scale. You can see the live USDC to ARS rate on our [corridor page](\u002Fusdc-to-ars).\n\nThe backdrop matters more here than in most corridors: Argentines have used stablecoins for years as a hedge against peso inflation and devaluation, and by mid-2025 stablecoin purchases made up over half of all exchange transactions involving the Argentine peso, according to Chainalysis's 2025 Latin America crypto adoption report. Every serious USDC-to-ARS route ends in a peso transfer over Transfers 3.0, the BCRA's instant payment scheme. And the exchange rate environment changed sharply in April 2025, when most of the \"cepo cambiario\" currency controls were lifted, so the honest cost comparison in 2026 looks different than it did two years ago.\n\n## What are the four routes from USDC to ARS?\n\n**Route 1: Stablecoin payout API.** A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\n**Route 2: Argentine exchange off-ramp.** Send USDC to a local exchange, sell for ARS, withdraw to a bank account or wallet. Trading fees typically run 0.1 to 1 percent, plus network and withdrawal costs. KYC (DNI or CUIT) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.\n\n**Route 3: P2P marketplaces.** Trade USDC directly with a counterparty who sends you pesos. This has deep roots in Argentina, where informal cash exchange (\"cuevas\") long predates crypto P2P. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.\n\n**Route 4: Global exchange with an ARS ramp.** Some global exchanges support ARS deposits and withdrawals. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and ARS pairs get thinner liquidity than local venues, with wider spreads during volatile sessions.\n\n## How do the routes compare?\n\n| Route | Speed (end to end) | Typical cost | KYC | Best for |\n|---|---|---|---|---|\n| Payout API | Minutes | Quoted FX rate + provider fee | Provider-run, per receiver | Businesses paying at scale |\n| Argentine exchange | Minutes to hours | 0.1-1% trade + withdrawal | Full, per account | Individuals, occasional cash-out |\n| P2P marketplace | Minutes to hours | Spread-dependent | Varies by venue | Small amounts, no business trail |\n| Global exchange + ARS ramp | Minutes to hours | Stacked (trade + FX + withdrawal) | Full, per account | Funds already on the exchange |\n\nCompare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. This matters more in Argentina than in most corridors, because spreads between venues can move with the day's exchange rate volatility. Provider pricing models are compared in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n\n## What are Argentina's rules for USDC to ARS in 2026?\n\nTwo layers, as of 2026:\n\n- **Law 27,739 (2024)** created Argentina's registration regime for Proveedores de Servicios de Activos Virtuales (PSAV), the entities that exchange, transfer, or custody virtual assets on behalf of others, in line with FATF Recommendation 15. The Comisión Nacional de Valores (CNV) is the supervisor, and CNV General Resolution 1058 sets the registration procedure through the government's online filing platform (TAD).\n- **Tax**: AFIP taxes crypto disposals for individuals and companies, and reporting obligations continue to expand as Argentina implements the OECD's Crypto-Asset Reporting Framework alongside its existing income and personal-assets tax rules. Track cost basis in pesos at acquisition and disposal.\n\nWorth stating plainly: the PSAV framework exists in law, but enforcement is still catching up to it. As of early September 2026, the CNV's own PSAV Registry lists zero registered legal entities and zero registered natural persons. That does not mean virtual asset activity in Argentina is unregulated on paper, but it does mean the registration regime has not yet produced a visible list of compliant providers the way, for example, Brazil's BCB authorization regime has started to. Businesses choosing a provider should ask directly about compliance posture rather than checking a public registry.\n\nOne operational rule dominates day-to-day payouts: Argentine transfers verify the receiver. A CBU (Clave Bancaria Uniforme) or CVU (Clave Virtual Uniforme), often reached through a shorter alias, must resolve to an account whose holder name matches the beneficiary on file, or the transfer is rejected. Mismatched beneficiary data is the top cause of failed Argentina payouts on any route, the same failure mode Brazil's Pix has.\n\n## Is the cepo cambiario still a factor for these routes?\n\nLess than it was. For over a decade, Argentina's currency controls (the \"cepo cambiario\") forced a gap between the official peso rate and parallel rates like the \"dólar blue,\" and that gap is a large part of why Argentines turned to stablecoins in the first place. That changed on April 14, 2025, when the government lifted most restrictions on buying foreign currency for individuals and companies and moved to a single, floating exchange rate inside a band the BCRA has adjusted monthly since, based on recent inflation data.\n\nThe practical effect by late August 2026: the gap between the blue-market rate and the official rate has narrowed to roughly one to two percent, down from over 100 percent at points during 2023 and 2024. That is a genuinely different environment for pricing a USDC-to-ARS conversion than the corridor had for most of its history. It is not a guarantee of stability. Some restrictions on corporate profit repatriation and legacy debt payments eased on a slower schedule than the retail rules, the band itself can move, and a change in policy could reopen the gap. Treat any specific number here as a snapshot, not a permanent fact, and check the current BCRA framework before relying on it for a live conversion.\n\n## Which route fits which business?\n\n- **Freelancer receiving USDC occasionally**: an Argentine exchange account is enough. Watch the spread and keep records for AFIP.\n- **Company paying 1 or 2 Argentine contractors**: an exchange works but does not scale; every payment is manual and the compliance trail is yours to build.\n- **Company paying tens to thousands of receivers** (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, name\u002FCBU or CVU matching, and delivery over Transfers 3.0 happen inside one API call.\n- **Treasury converting its own balance**: an exchange or OTC desk for large one-off conversions; an API with [virtual accounts](\u002Fvirtual-accounts) if conversions recur as part of a product flow.\n\n## Which network should you send USDC on?\n\nUSDC is issued natively on multiple blockchains, and the network choice affects cost and settlement time on every route. Ethereum mainnet carries the deepest liquidity but the highest fees, often dollars per transfer at busy times. Base, Polygon, Arbitrum, and Solana move the same USDC for cents and settle in seconds to minutes. Two practical rules:\n\n- **Match the destination's supported networks.** An Argentine exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.\n- **Prefer a cheap network your counterparty supports.** For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same ARS amount regardless.\n\nThe token is worth one dollar on every chain; only the transport differs. More on how the token itself works: [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin).\n\n## Where these routes fall short\n\nHonest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow, and Argentina's long informal-exchange culture makes counterparty risk easy to underestimate. Global exchanges quote thin ARS liquidity, and spreads widen fastest exactly when the peso is moving. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route removes Argentina's tax reporting obligations, or shields a business from exchange rate policy changing again.\n\n## How BlindPay handles USDC to ARS\n\nBlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over Transfers 3.0, usually within minutes. Receiver verification (including CBU\u002FCVU and name matching), sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the [USDC to ARS page](\u002Fusdc-to-ars). The same API pays out over Pix, SPEI, PSE, SEPA, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in [100+ countries](\u002Fcoverage), USDT works the same way, and [pricing](\u002Fpricing) is public. Agents and automated systems that need to route this corridor programmatically can start from [agentic payments](\u002Fagentic-payments).\n\n## Methodology and sources\n\nRail and regulatory facts from primary sources: the BCRA's Transfers 3.0 documentation ([bcra.gob.ar](https:\u002F\u002Fwww.bcra.gob.ar\u002Fen\u002Ftransfers-3-0\u002F)), Law 27,739 and the PSAV framework via the CNV ([argentina.gob.ar](https:\u002F\u002Fwww.argentina.gob.ar\u002Fnoticias\u002Fregulacion-de-los-proveedores-de-servicios-de-activos-virtuales-psav)), the CNV's live PSAV Registry count ([cnv.gov.ar](https:\u002F\u002Fwww.cnv.gov.ar\u002FSitioWeb\u002FProveedoresServiciosActivosVirtuales\u002FRegistrosPSAV), checked early September 2026), and the April 2025 currency control changes as summarized by the U.S. International Trade Administration ([trade.gov](https:\u002F\u002Fwww.trade.gov\u002Fmarket-intelligence\u002Fargentina-eliminates-capital-controls-and-payment-timelines)). The stablecoin adoption statistic is from Chainalysis's 2025 Latin America crypto adoption report ([chainalysis.com](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flatin-america-crypto-adoption-2025\u002F)). Exchange fee ranges reflect published fee schedules of major Argentine venues as of 2026; live BlindPay FX quotes are on the [corridor page](\u002Fusdc-to-ars). Regulatory and exchange-rate status described as of late August 2026 and subject to change.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":11510,"description":11825},"USDC to ARS in 2026: routes, fees, and rules","resources\u002Fmore\u002Fusdc-to-ars-routes-2026","7VB7dPiI6mmRKlGaziGt4hufL407a316Y_dqCsJSSPI",{"id":11849,"title":11850,"authors":6,"body":11851,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":1873,"description":12116,"extension":342,"faq":12117,"howto":6,"isBlog":359,"isChangelog":359,"meta":12130,"navigation":362,"path":5852,"pillar":359,"products":6,"rawbody":12131,"role":6,"seo":12132,"seoTitle":12133,"stem":12134,"thumbnail":6,"updated":6,"__hash__":12135},"content\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026.md","USDC to BRL in 2026: routes, fees, and rules compared",{"type":8,"value":11852,"toc":12105},[11853,11858,11861,11865,11872,11878,11883,11889,11891,11960,11965,11969,11972,11994,11997,11999,12022,12024,12026,12038,12042,12046,12049,12052,12054,12057,12061,12077,12079,12101],[11,11854,11855,11856,227],{},"There are four practical routes from USDC to Brazilian reais in 2026: send through a stablecoin payout API that delivers Pix directly, sell on a Brazilian exchange and withdraw over Pix, trade peer-to-peer, or use a global exchange with a BRL\u002FPix ramp. They differ on fees, speed, KYC, and who carries the regulatory burden, and the right one depends on whether you are an individual cashing out or a business paying people at scale. You can see the live USDC to BRL rate on our ",[136,11857,11519],{"href":1757},[11,11859,11860],{},"The backdrop matters: Pix, the instant payment system run by the Banco Central do Brasil, settles transfers in seconds, 24\u002F7, and is used by over 150 million Brazilians. Every serious USDC-to-BRL route ends in a Pix transfer. And since February 2, 2026, providers of virtual asset services in Brazil operate under the Central Bank's authorization regime (Resolutions 519, 520, and 521), so the compliant options are clearly marked.",[18,11862,11864],{"id":11863},"what-are-the-four-routes-from-usdc-to-brl","What are the four routes from USDC to BRL?",[11,11866,11867,11869,11870,227],{},[119,11868,11531],{}," A business sends USDC through an API; the provider converts at a quoted rate and delivers reais via Pix to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: ",[136,11871,1492],{"href":618},[11,11873,11874,11877],{},[119,11875,11876],{},"Route 2: Brazilian exchange off-ramp."," Send USDC to a local exchange, sell for BRL, withdraw via Pix. Trading fees typically run 0.1 to 0.5 percent, plus network and withdrawal costs. Full KYC (CPF or CNPJ) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.",[11,11879,11880,11882],{},[119,11881,11545],{}," Trade USDC directly with a counterparty who sends you Pix. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.",[11,11884,11885,11888],{},[119,11886,11887],{},"Route 4: Global exchange with a BRL\u002FPix ramp."," Some global exchanges support BRL deposits and withdrawals over Pix. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and BRL pairs get thinner liquidity than local venues.",[18,11890,11556],{"id":11555},[39,11892,11893,11907],{},[42,11894,11895],{},[45,11896,11897,11899,11901,11903,11905],{},[48,11898,11565],{},[48,11900,11568],{},[48,11902,1100],{},[48,11904,11573],{},[48,11906,785],{},[61,11908,11909,11921,11935,11947],{},[45,11910,11911,11913,11915,11917,11919],{},[66,11912,11582],{},[66,11914,1175],{},[66,11916,11587],{},[66,11918,11590],{},[66,11920,11593],{},[45,11922,11923,11926,11928,11931,11933],{},[66,11924,11925],{},"Brazilian exchange",[66,11927,11601],{},[66,11929,11930],{},"0.1-0.5% trade + withdrawal",[66,11932,11607],{},[66,11934,11610],{},[45,11936,11937,11939,11941,11943,11945],{},[66,11938,11615],{},[66,11940,11601],{},[66,11942,11620],{},[66,11944,11623],{},[66,11946,11626],{},[45,11948,11949,11952,11954,11956,11958],{},[66,11950,11951],{},"Global exchange + Pix",[66,11953,11601],{},[66,11955,11636],{},[66,11957,11607],{},[66,11959,11641],{},[11,11961,11962,11963,227],{},"Compare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. Provider pricing models are compared in ",[136,11964,9869],{"href":771},[18,11966,11968],{"id":11967},"what-are-brazils-rules-for-usdc-to-brl-in-2026","What are Brazil's rules for USDC to BRL in 2026?",[11,11970,11971],{},"Three layers, as of 2026:",[171,11973,11974,11980,11989],{},[148,11975,11976,11979],{},[119,11977,11978],{},"Law 14.478\u002F2022"," established the legal framework for virtual asset service providers and made the Banco Central do Brasil the supervisor.",[148,11981,11982,11985,11986,227],{},[119,11983,11984],{},"BCB Resolutions 519, 520, and 521",", published November 10, 2025 and effective February 2, 2026, created the SPSAV authorization regime. Companies providing virtual asset services to Brazilians must be authorized, with a transition window under Article 88 of Resolution 520 for firms already operating. The full regime is explained in ",[136,11987,11988],{"href":3239},"PSAV in Brazil",[148,11990,11991,11993],{},[119,11992,11666],{},": Receita Federal rules tax crypto disposals; reporting obligations were expanded by Normative Instruction 2,291\u002F2025. Individuals and companies converting USDC to BRL should track cost basis and report accordingly.",[11,11995,11996],{},"One operational rule dominates day-to-day payouts: Pix transfers verify the receiver. The beneficiary's name and tax ID (CPF or CNPJ) must match the receiving account or the transfer is rejected. Mismatched beneficiary data is the top cause of failed Brazil payouts on any route.",[18,11998,11687],{"id":11686},[171,12000,12001,12006,12011,12016],{},[148,12002,12003,12005],{},[119,12004,11694],{},": a Brazilian exchange account is enough. Watch the spread and keep records for tax.",[148,12007,12008,11701],{},[119,12009,12010],{},"Company paying 1 or 2 Brazilian contractors",[148,12012,12013,12015],{},[119,12014,11706],{}," (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, name\u002Ftax ID matching, and delivery over Pix happen inside one API call.",[148,12017,12018,11713,12020,11716],{},[119,12019,11712],{},[136,12021,632],{"href":138},[18,12023,11720],{"id":11719},[11,12025,11723],{},[171,12027,12028,12033],{},[148,12029,12030,12032],{},[119,12031,11730],{}," A Brazilian exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.",[148,12034,12035,12037],{},[119,12036,11736],{}," For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same BRL amount regardless.",[11,12039,11740,12040,227],{},[136,12041,9801],{"href":9800},[18,12043,12045],{"id":12044},"how-are-usdc-to-brl-conversions-taxed","How are USDC to BRL conversions taxed?",[11,12047,12048],{},"As of 2026, Brazil taxes crypto gains for individuals under Receita Federal rules, with reporting expanded by Normative Instruction 2,291\u002F2025, which widened the information providers must report on crypto transactions. Selling USDC for BRL is a disposal: if the reais received exceed the cost basis in reais, the difference is taxable gain. For companies, conversions flow through ordinary corporate accounting, and payouts to Brazilian contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.",[11,12050,12051],{},"Two habits save pain later. Keep the BRL value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over Pix from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.",[18,12053,11746],{"id":11745},[11,12055,12056],{},"Honest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin BRL liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route avoids Brazilian tax obligations.",[18,12058,12060],{"id":12059},"how-blindpay-handles-usdc-to-brl","How BlindPay handles USDC to BRL",[11,12062,12063,12064,12067,12068,12070,12071,12073,12074,12076],{},"BlindPay is a stablecoin API: your business sends USDC, the receiver gets reais over Pix, usually within minutes. Receiver verification (including CPF\u002FCNPJ matching), sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the ",[136,12065,12066],{"href":1757},"USDC to BRL page",". The same API pays out over SPEI, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in ",[136,12069,11763],{"href":1335},", USDT works the same way (",[136,12072,1761],{"href":1760},"), and ",[136,12075,1340],{"href":307}," is public.",[18,12078,1350],{"id":1349},[11,12080,12081,12082,12086,12087,12092,12093,12097,12098,12100],{},"Rail and regulatory facts from primary sources: the Banco Central do Brasil's Pix documentation (",[136,12083,12085],{"href":1854,"rel":12084},[414],"bcb.gov.br","), Law 14.478\u002F2022 (",[136,12088,12091],{"href":12089,"rel":12090},"https:\u002F\u002Fwww.planalto.gov.br\u002Fccivil_03\u002F_ato2019-2022\u002F2022\u002Flei\u002FL14478.htm",[414],"planalto.gov.br","), BCB Resolutions 519, 520, and 521 of November 2025 (",[136,12094,12085],{"href":12095,"rel":12096},"https:\u002F\u002Fwww.bcb.gov.br",[414],"), and Receita Federal guidance including Normative Instruction 2,291\u002F2025. Exchange fee ranges reflect published fee schedules of major Brazilian venues as of 2026; live BlindPay FX quotes are on the ",[136,12099,11519],{"href":1757},". Regulatory status described as of August 2026.",[11,12102,12103],{},[324,12104,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":12106},[12107,12108,12109,12110,12111,12112,12113,12114,12115],{"id":11863,"depth":329,"text":11864},{"id":11555,"depth":329,"text":11556},{"id":11967,"depth":329,"text":11968},{"id":11686,"depth":329,"text":11687},{"id":11719,"depth":329,"text":11720},{"id":12044,"depth":329,"text":12045},{"id":11745,"depth":329,"text":11746},{"id":12059,"depth":329,"text":12060},{"id":1349,"depth":329,"text":1350},"Four ways to convert USDC to Brazilian reais in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Pix. Fees, speed, KYC.",[12118,12121,12124,12127],{"q":12119,"a":12120},"What is the cheapest way to convert USDC to BRL?","For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Brazilian exchanges are usually cheapest, with trading fees around 0.1 to 0.5 percent plus a small Pix withdrawal cost.",{"q":12122,"a":12123},"How fast does a USDC to BRL conversion arrive?","Over Pix, minutes. Pix settles in seconds once reais leave the sending institution, so end-to-end time is dominated by the conversion step: typically a few minutes on exchanges and payout APIs.",{"q":12125,"a":12126},"Is converting USDC to BRL legal in Brazil?","Yes. Brazil regulates virtual asset services under Law 14.478\u002F2022, and the Central Bank's Resolutions 519, 520, and 521 (effective February 2026) created an authorization regime for providers. Individuals also owe tax on crypto gains under Receita Federal rules.",{"q":12128,"a":12129},"Why do Pix payouts get rejected?","The most common reason is a mismatch between the receiver's name or tax ID (CPF or CNPJ) and the receiving account. Brazilian institutions verify both before crediting, so accurate beneficiary data is a hard requirement.",{"author":361},"---\ntitle: \"USDC to BRL in 2026: routes, fees, and rules compared\"\nseoTitle: \"USDC to BRL in 2026: routes, fees, and rules\"\ndescription: \"Four ways to convert USDC to Brazilian reais in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Pix. Fees, speed, KYC.\"\ndate: \"2026-08-15\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the cheapest way to convert USDC to BRL?\"\n    a: \"For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Brazilian exchanges are usually cheapest, with trading fees around 0.1 to 0.5 percent plus a small Pix withdrawal cost.\"\n  - q: \"How fast does a USDC to BRL conversion arrive?\"\n    a: \"Over Pix, minutes. Pix settles in seconds once reais leave the sending institution, so end-to-end time is dominated by the conversion step: typically a few minutes on exchanges and payout APIs.\"\n  - q: \"Is converting USDC to BRL legal in Brazil?\"\n    a: \"Yes. Brazil regulates virtual asset services under Law 14.478\u002F2022, and the Central Bank's Resolutions 519, 520, and 521 (effective February 2026) created an authorization regime for providers. Individuals also owe tax on crypto gains under Receita Federal rules.\"\n  - q: \"Why do Pix payouts get rejected?\"\n    a: \"The most common reason is a mismatch between the receiver's name or tax ID (CPF or CNPJ) and the receiving account. Brazilian institutions verify both before crediting, so accurate beneficiary data is a hard requirement.\"\n---\n\nThere are four practical routes from USDC to Brazilian reais in 2026: send through a stablecoin payout API that delivers Pix directly, sell on a Brazilian exchange and withdraw over Pix, trade peer-to-peer, or use a global exchange with a BRL\u002FPix ramp. They differ on fees, speed, KYC, and who carries the regulatory burden, and the right one depends on whether you are an individual cashing out or a business paying people at scale. You can see the live USDC to BRL rate on our [corridor page](\u002Fusdc-to-brl).\n\nThe backdrop matters: Pix, the instant payment system run by the Banco Central do Brasil, settles transfers in seconds, 24\u002F7, and is used by over 150 million Brazilians. Every serious USDC-to-BRL route ends in a Pix transfer. And since February 2, 2026, providers of virtual asset services in Brazil operate under the Central Bank's authorization regime (Resolutions 519, 520, and 521), so the compliant options are clearly marked.\n\n## What are the four routes from USDC to BRL?\n\n**Route 1: Stablecoin payout API.** A business sends USDC through an API; the provider converts at a quoted rate and delivers reais via Pix to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\n**Route 2: Brazilian exchange off-ramp.** Send USDC to a local exchange, sell for BRL, withdraw via Pix. Trading fees typically run 0.1 to 0.5 percent, plus network and withdrawal costs. Full KYC (CPF or CNPJ) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.\n\n**Route 3: P2P marketplaces.** Trade USDC directly with a counterparty who sends you Pix. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.\n\n**Route 4: Global exchange with a BRL\u002FPix ramp.** Some global exchanges support BRL deposits and withdrawals over Pix. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and BRL pairs get thinner liquidity than local venues.\n\n## How do the routes compare?\n\n| Route | Speed (end to end) | Typical cost | KYC | Best for |\n|---|---|---|---|---|\n| Payout API | Minutes | Quoted FX rate + provider fee | Provider-run, per receiver | Businesses paying at scale |\n| Brazilian exchange | Minutes to hours | 0.1-0.5% trade + withdrawal | Full, per account | Individuals, occasional cash-out |\n| P2P marketplace | Minutes to hours | Spread-dependent | Varies by venue | Small amounts, no business trail |\n| Global exchange + Pix | Minutes to hours | Stacked (trade + FX + withdrawal) | Full, per account | Funds already on the exchange |\n\nCompare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. Provider pricing models are compared in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n\n## What are Brazil's rules for USDC to BRL in 2026?\n\nThree layers, as of 2026:\n\n- **Law 14.478\u002F2022** established the legal framework for virtual asset service providers and made the Banco Central do Brasil the supervisor.\n- **BCB Resolutions 519, 520, and 521**, published November 10, 2025 and effective February 2, 2026, created the SPSAV authorization regime. Companies providing virtual asset services to Brazilians must be authorized, with a transition window under Article 88 of Resolution 520 for firms already operating. The full regime is explained in [PSAV in Brazil](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained).\n- **Tax**: Receita Federal rules tax crypto disposals; reporting obligations were expanded by Normative Instruction 2,291\u002F2025. Individuals and companies converting USDC to BRL should track cost basis and report accordingly.\n\nOne operational rule dominates day-to-day payouts: Pix transfers verify the receiver. The beneficiary's name and tax ID (CPF or CNPJ) must match the receiving account or the transfer is rejected. Mismatched beneficiary data is the top cause of failed Brazil payouts on any route.\n\n## Which route fits which business?\n\n- **Freelancer receiving USDC occasionally**: a Brazilian exchange account is enough. Watch the spread and keep records for tax.\n- **Company paying 1 or 2 Brazilian contractors**: an exchange works but does not scale; every payment is manual and the compliance trail is yours to build.\n- **Company paying tens to thousands of receivers** (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, name\u002Ftax ID matching, and delivery over Pix happen inside one API call.\n- **Treasury converting its own balance**: an exchange or OTC desk for large one-off conversions; an API with [virtual accounts](\u002Fvirtual-accounts) if conversions recur as part of a product flow.\n\n## Which network should you send USDC on?\n\nUSDC is issued natively on multiple blockchains, and the network choice affects cost and settlement time on every route. Ethereum mainnet carries the deepest liquidity but the highest fees, often dollars per transfer at busy times. Base, Polygon, Arbitrum, and Solana move the same USDC for cents and settle in seconds to minutes. Two practical rules:\n\n- **Match the destination's supported networks.** A Brazilian exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.\n- **Prefer a cheap network your counterparty supports.** For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same BRL amount regardless.\n\nThe token is worth one dollar on every chain; only the transport differs. More on how the token itself works: [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin).\n\n## How are USDC to BRL conversions taxed?\n\nAs of 2026, Brazil taxes crypto gains for individuals under Receita Federal rules, with reporting expanded by Normative Instruction 2,291\u002F2025, which widened the information providers must report on crypto transactions. Selling USDC for BRL is a disposal: if the reais received exceed the cost basis in reais, the difference is taxable gain. For companies, conversions flow through ordinary corporate accounting, and payouts to Brazilian contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.\n\nTwo habits save pain later. Keep the BRL value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over Pix from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.\n\n## Where these routes fall short\n\nHonest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin BRL liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route avoids Brazilian tax obligations.\n\n## How BlindPay handles USDC to BRL\n\nBlindPay is a stablecoin API: your business sends USDC, the receiver gets reais over Pix, usually within minutes. Receiver verification (including CPF\u002FCNPJ matching), sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the [USDC to BRL page](\u002Fusdc-to-brl). The same API pays out over SPEI, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in [100+ countries](\u002Fcoverage), USDT works the same way ([USDT to BRL](\u002Fusdt-to-brl)), and [pricing](\u002Fpricing) is public.\n\n## Methodology and sources\n\nRail and regulatory facts from primary sources: the Banco Central do Brasil's Pix documentation ([bcb.gov.br](https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en)), Law 14.478\u002F2022 ([planalto.gov.br](https:\u002F\u002Fwww.planalto.gov.br\u002Fccivil_03\u002F_ato2019-2022\u002F2022\u002Flei\u002FL14478.htm)), BCB Resolutions 519, 520, and 521 of November 2025 ([bcb.gov.br](https:\u002F\u002Fwww.bcb.gov.br)), and Receita Federal guidance including Normative Instruction 2,291\u002F2025. Exchange fee ranges reflect published fee schedules of major Brazilian venues as of 2026; live BlindPay FX quotes are on the [corridor page](\u002Fusdc-to-brl). Regulatory status described as of August 2026.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":11850,"description":12116},"USDC to BRL in 2026: routes, fees, and rules","resources\u002Fmore\u002Fusdc-to-brl-routes-2026","yRvxxRYGpgI0kAzQSZwV6MduHuzKE1ycw3-tRE1YXf0",{"id":12137,"title":12138,"authors":6,"body":12139,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":10050,"description":12436,"extension":342,"faq":12437,"howto":6,"isBlog":359,"isChangelog":359,"meta":12453,"navigation":362,"path":7240,"pillar":359,"products":6,"rawbody":12454,"role":6,"seo":12455,"seoTitle":12456,"stem":12457,"thumbnail":6,"updated":10050,"__hash__":12458},"content\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026.md","USDC to COP in 2026: routes, fees, and rules compared",{"type":8,"value":12140,"toc":12424},[12141,12147,12155,12159,12166,12172,12177,12183,12185,12253,12257,12261,12264,12290,12293,12295,12318,12320,12322,12334,12338,12342,12351,12355,12358,12361,12363,12368,12372,12392,12394,12420],[11,12142,12143,12144,227],{},"There are four practical routes from USDC to Colombian pesos in 2026: a stablecoin payout API delivering PSE directly, a Colombian exchange off-ramp, a P2P trade, or a global exchange with a COP ramp. They differ on fees, speed, and KYC. See the live rate on our ",[136,12145,11519],{"href":12146},"\u002Fusdc-to-cop",[11,12148,12149,12150,12154],{},"The backdrop matters: stablecoins made up over half of all exchange purchases in Colombia between July 2024 and June 2025, according to ",[136,12151,12153],{"href":11803,"rel":12152},[414],"Chainalysis",", ahead of every other asset class Colombians trade. Persistent inflation, currency volatility, and restrictive capital controls across the region are the drivers Chainalysis names, not a Colombia-specific cause. Every route below ends in a PSE transfer, the interbank system Colombian banks use to move money between accounts, and unlike Brazil's Pix, PSE runs on bank processing windows rather than settling instantly around the clock.",[18,12156,12158],{"id":12157},"what-are-the-four-routes-from-usdc-to-cop","What are the four routes from USDC to COP?",[11,12160,12161,12163,12164,227],{},[119,12162,11531],{}," A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos via PSE to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: ",[136,12165,1492],{"href":618},[11,12167,12168,12171],{},[119,12169,12170],{},"Route 2: Colombian exchange off-ramp."," Send USDC to a local exchange, sell for COP, withdraw via PSE. Trading fees typically run 0.1 to 0.5 percent, plus network and withdrawal costs. Full KYC (cédula or NIT) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.",[11,12173,12174,12176],{},[119,12175,11545],{}," Trade USDC directly with a counterparty who sends you a bank transfer. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.",[11,12178,12179,12182],{},[119,12180,12181],{},"Route 4: Global exchange with a COP ramp."," Some global exchanges support COP deposits and withdrawals over PSE or local bank transfer. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and COP pairs get thinner liquidity than local venues.",[18,12184,11556],{"id":11555},[39,12186,12187,12201],{},[42,12188,12189],{},[45,12190,12191,12193,12195,12197,12199],{},[48,12192,11565],{},[48,12194,11568],{},[48,12196,1100],{},[48,12198,11573],{},[48,12200,785],{},[61,12202,12203,12215,12228,12240],{},[45,12204,12205,12207,12209,12211,12213],{},[66,12206,11582],{},[66,12208,1175],{},[66,12210,11587],{},[66,12212,11590],{},[66,12214,11593],{},[45,12216,12217,12220,12222,12224,12226],{},[66,12218,12219],{},"Colombian exchange",[66,12221,11601],{},[66,12223,11930],{},[66,12225,11607],{},[66,12227,11610],{},[45,12229,12230,12232,12234,12236,12238],{},[66,12231,11615],{},[66,12233,11601],{},[66,12235,11620],{},[66,12237,11623],{},[66,12239,11626],{},[45,12241,12242,12245,12247,12249,12251],{},[66,12243,12244],{},"Global exchange + PSE",[66,12246,11601],{},[66,12248,11636],{},[66,12250,11607],{},[66,12252,11641],{},[11,12254,11962,12255,227],{},[136,12256,9869],{"href":771},[18,12258,12260],{"id":12259},"what-are-colombias-rules-for-usdc-to-cop-in-2026","What are Colombia's rules for USDC to COP in 2026?",[11,12262,12263],{},"Colombia does not have a consolidated VASP license the way Brazil does. What exists instead, as of 2026:",[171,12265,12266,12272,12284],{},[148,12267,12268,12271],{},[119,12269,12270],{},"No ban, no dedicated license."," DIAN's Unified Concept 1621 of 2023 confirms cryptoassets are not legal tender in Colombia but their commercial use is permitted. DIAN itself has called for sector-specific regulation, which does not exist yet.",[148,12273,12274,12277,12278,12283],{},[119,12275,12276],{},"Proyecto de Ley 510 de 2025"," would have created the licensing regime DIAN is asking for: a framework covering VASP oversight, consumer protection, AML\u002FCTF measures, and financial education, filed in the Chamber of Representatives in February 2025 with Representative Julián López as lead sponsor. It passed committee and plenary debate in the Chamber but was archived under Article 190 of Law 5 of 1992, the rule that shelves a bill not passed within two ordinary legislative sessions, before reaching the Senate. The Chamber's own bill tracker lists it as archived, and ",[136,12279,12282],{"href":12280,"rel":12281},"https:\u002F\u002Fwww.portafolio.co\u002Feconomia\u002Fmercado-cripto-queda-sin-regulacion-integral-tras-archivo-de-ley-pese-a-mayores-controles-tributarios-500476",[414],"Portafolio",", Valora Analitik, and Infobae reported the archival in mid-August 2026. The Superintendencia Financiera has separately run a public consultation on a draft circular covering how banks may relate to VASPs.",[148,12285,12286,12289],{},[119,12287,12288],{},"AML reporting already applies."," UIAF Resolution 314 of 2021 requires VASPs to file Suspicious Transaction Reports immediately on detection, plus a monthly report through the SIREL platform even when nothing suspicious occurred. This obligation exists independent of Proyecto de Ley 510.",[11,12291,12292],{},"One operational rule dominates day-to-day payouts: PSE moves money on bank processing windows, not instantly. A transfer initiated late at night or on a bank holiday can sit until the next window opens, and receiver name or cédula mismatches are rejected the same way Pix and SPEI reject them elsewhere in Latin America.",[18,12294,11687],{"id":11686},[171,12296,12297,12302,12307,12312],{},[148,12298,12299,12301],{},[119,12300,11694],{},": a Colombian exchange account is enough. Watch the spread and keep records; Colombia's tax authority already requires exchanges to report user activity.",[148,12303,12304,11701],{},[119,12305,12306],{},"Company paying 1 or 2 Colombian contractors",[148,12308,12309,12311],{},[119,12310,11706],{}," (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, and delivery over PSE happen inside one API call.",[148,12313,12314,11713,12316,11716],{},[119,12315,11712],{},[136,12317,632],{"href":138},[18,12319,11720],{"id":11719},[11,12321,11723],{},[171,12323,12324,12329],{},[148,12325,12326,12328],{},[119,12327,11730],{}," A Colombian exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.",[148,12330,12331,12333],{},[119,12332,11736],{}," For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same COP amount regardless.",[11,12335,11740,12336,227],{},[136,12337,9801],{"href":9800},[18,12339,12341],{"id":12340},"why-does-colombia-have-so-much-stablecoin-volume","Why does Colombia have so much stablecoin volume?",[11,12343,12344,12345,12350],{},"Remittances are the largest single reason. Colombia received a record 13.098 billion dollars in remittances in 2025, up 10.6 percent from 2024's 11.843 billion, equal to roughly 3 percent of GDP, according to Banco de la República data reported by ",[136,12346,12349],{"href":12347,"rel":12348},"https:\u002F\u002Fportal.migracioncolombia.gov.co\u002Fdetalle-noticia\u002Fagenda-migcol\u002Fcomunicaciones-y-prensa\u002Fcolombia-recibio-13098-millones-de-dolares-en-remesas-en-2025",[414],"Colombia's Migration authority",". Most of that still arrives through traditional money transfer operators, but the peso's volatility against the dollar gives senders and receivers alike a reason to hold value in USDC between the moment it is sent and the moment it is spent, rather than converting immediately at each leg.",[18,12352,12354],{"id":12353},"how-are-usdc-to-cop-conversions-taxed","How are USDC to COP conversions taxed?",[11,12356,12357],{},"Colombia taxes crypto disposals for individuals and companies under its ordinary income tax rules; DIAN treats cryptoassets as taxable assets, not currency, so selling USDC for COP is a disposal event if the peso value received differs from cost basis. For companies, conversions flow through ordinary corporate accounting, and payouts to Colombian contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.",[11,12359,12360],{},"Two habits save pain later. Keep the COP value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over PSE from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.",[18,12362,11746],{"id":11745},[11,12364,12365,12366,227],{},"Honest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin COP liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route settles instantly around the clock: PSE's bank windows are a real constraint that Pix and Transfers 3.0 do not share, so plan payroll runs around business hours. AI agents that need to reason about a corridor's constraints before initiating a payout are covered in ",[136,12367,11771],{"href":11770},[18,12369,12371],{"id":12370},"how-blindpay-handles-usdc-to-cop","How BlindPay handles USDC to COP",[11,12373,12374,12375,12378,12379,11764,12381,12383,12384,12387,12388,227],{},"BlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over PSE, typically within minutes during bank processing windows. Receiver verification, sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the ",[136,12376,12377],{"href":12146},"USDC to COP page",". The same API pays out over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in ",[136,12380,11763],{"href":1335},[136,12382,1340],{"href":307}," is public. For the Brazil equivalent of this comparison, see ",[136,12385,12386],{"href":5852},"USDC to BRL routes in 2026",", or browse the rest of the ",[136,12389,12391],{"href":12390},"\u002Fresources\u002Fmore","resources library",[18,12393,1350],{"id":1349},[11,12395,12396,12397,12400,12401,12405,12406,12411,12412,12416,12417,12419],{},"Rail facts from BlindPay's own corridor data. Adoption statistic from Chainalysis's 2025 Latin America crypto adoption report (",[136,12398,11805],{"href":11803,"rel":12399},[414],"). Remittance figures from Banco de la República data as reported by Colombia's Migración authority (",[136,12402,12404],{"href":12347,"rel":12403},[414],"migracioncolombia.gov.co","). Regulatory facts from DIAN's Unified Concept 1621 of 2023, UIAF Resolution 314 of 2021, and Proyecto de Ley 510 de 2025's status on the ",[136,12407,12410],{"href":12408,"rel":12409},"https:\u002F\u002Fwww.camara.gov.co\u002Fservicios-activos-virtuales",[414],"Chamber of Representatives' bill tracker",", confirmed by ",[136,12413,12415],{"href":12280,"rel":12414},[414],"Portafolio's"," August 2026 reporting on its archival. Exchange fee ranges reflect published fee schedules of major venues as of 2026; live BlindPay FX quotes are on the ",[136,12418,11519],{"href":12146},". Regulatory status described as of September 2026.",[11,12421,12422],{},[324,12423,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":12425},[12426,12427,12428,12429,12430,12431,12432,12433,12434,12435],{"id":12157,"depth":329,"text":12158},{"id":11555,"depth":329,"text":11556},{"id":12259,"depth":329,"text":12260},{"id":11686,"depth":329,"text":11687},{"id":11719,"depth":329,"text":11720},{"id":12340,"depth":329,"text":12341},{"id":12353,"depth":329,"text":12354},{"id":11745,"depth":329,"text":11746},{"id":12370,"depth":329,"text":12371},{"id":1349,"depth":329,"text":1350},"Four ways to convert USDC to Colombian pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with PSE. Fees, speed, KYC.",[12438,12441,12444,12447,12450],{"q":12439,"a":12440},"What is the cheapest way to convert USDC to COP?","For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Colombian exchanges are usually cheapest, with trading fees around 0.1 to 0.5 percent plus a small PSE withdrawal cost.",{"q":12442,"a":12443},"How fast does a USDC to COP conversion arrive?","Minutes, over PSE, but not instantly. PSE moves money between Colombian banks in minutes rather than seconds, and transfers outside business hours can queue until the receiving bank's next processing window.",{"q":12445,"a":12446},"Is converting USDC to COP legal in Colombia?","Yes. Colombia has not banned crypto activity, and DIAN's Unified Concept 1621 of 2023 confirms cryptoassets are not legal tender but their commercial use is permitted. There is no dedicated licensing regime: Proyecto de Ley 510 de 2025, which would have created one, was archived under Article 190 of Law 5 of 1992 without becoming law, as listed on the Chamber of Representatives' own bill tracker and reported by Colombian outlets in August 2026.",{"q":12448,"a":12449},"Why do PSE payouts get delayed or rejected?","The most common causes are a mismatch between the receiver's name or cédula and the destination account, or a transfer initiated outside the receiving bank's processing window. Both are worth checking before assuming a payout has failed.",{"q":12451,"a":12452},"Does Colombia have licensed stablecoin providers like Brazil?","Not in any form. Brazil's VASP authorization regime took effect in February 2026 under BCB Resolutions 519, 520, and 521. Colombia's closest equivalent, Proyecto de Ley 510 de 2025, passed committee and plenary debate in the Chamber of Representatives but was archived under Article 190 of Law 5 of 1992 before reaching the Senate. Providers operate under existing AML rules (UIAF Resolution 314 of 2021) and DIAN tax reporting rather than a dedicated crypto license.",{"author":361},"---\ntitle: \"USDC to COP in 2026: routes, fees, and rules compared\"\nseoTitle: \"USDC to COP in 2026: routes, fees, and rules\"\ndescription: \"Four ways to convert USDC to Colombian pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with PSE. Fees, speed, KYC.\"\ndate: \"2026-09-01\"\nauthor: \"BlindPay Team\"\nupdated: \"2026-09-01\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is the cheapest way to convert USDC to COP?\"\n    a: \"For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Colombian exchanges are usually cheapest, with trading fees around 0.1 to 0.5 percent plus a small PSE withdrawal cost.\"\n  - q: \"How fast does a USDC to COP conversion arrive?\"\n    a: \"Minutes, over PSE, but not instantly. PSE moves money between Colombian banks in minutes rather than seconds, and transfers outside business hours can queue until the receiving bank's next processing window.\"\n  - q: \"Is converting USDC to COP legal in Colombia?\"\n    a: \"Yes. Colombia has not banned crypto activity, and DIAN's Unified Concept 1621 of 2023 confirms cryptoassets are not legal tender but their commercial use is permitted. There is no dedicated licensing regime: Proyecto de Ley 510 de 2025, which would have created one, was archived under Article 190 of Law 5 of 1992 without becoming law, as listed on the Chamber of Representatives' own bill tracker and reported by Colombian outlets in August 2026.\"\n  - q: \"Why do PSE payouts get delayed or rejected?\"\n    a: \"The most common causes are a mismatch between the receiver's name or cédula and the destination account, or a transfer initiated outside the receiving bank's processing window. Both are worth checking before assuming a payout has failed.\"\n  - q: \"Does Colombia have licensed stablecoin providers like Brazil?\"\n    a: \"Not in any form. Brazil's VASP authorization regime took effect in February 2026 under BCB Resolutions 519, 520, and 521. Colombia's closest equivalent, Proyecto de Ley 510 de 2025, passed committee and plenary debate in the Chamber of Representatives but was archived under Article 190 of Law 5 of 1992 before reaching the Senate. Providers operate under existing AML rules (UIAF Resolution 314 of 2021) and DIAN tax reporting rather than a dedicated crypto license.\"\n---\n\nThere are four practical routes from USDC to Colombian pesos in 2026: a stablecoin payout API delivering PSE directly, a Colombian exchange off-ramp, a P2P trade, or a global exchange with a COP ramp. They differ on fees, speed, and KYC. See the live rate on our [corridor page](\u002Fusdc-to-cop).\n\nThe backdrop matters: stablecoins made up over half of all exchange purchases in Colombia between July 2024 and June 2025, according to [Chainalysis](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flatin-america-crypto-adoption-2025\u002F), ahead of every other asset class Colombians trade. Persistent inflation, currency volatility, and restrictive capital controls across the region are the drivers Chainalysis names, not a Colombia-specific cause. Every route below ends in a PSE transfer, the interbank system Colombian banks use to move money between accounts, and unlike Brazil's Pix, PSE runs on bank processing windows rather than settling instantly around the clock.\n\n## What are the four routes from USDC to COP?\n\n**Route 1: Stablecoin payout API.** A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos via PSE to the receiver's account, after verifying the receiver's identity. One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\n**Route 2: Colombian exchange off-ramp.** Send USDC to a local exchange, sell for COP, withdraw via PSE. Trading fees typically run 0.1 to 0.5 percent, plus network and withdrawal costs. Full KYC (cédula or NIT) is required. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.\n\n**Route 3: P2P marketplaces.** Trade USDC directly with a counterparty who sends you a bank transfer. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.\n\n**Route 4: Global exchange with a COP ramp.** Some global exchanges support COP deposits and withdrawals over PSE or local bank transfer. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and COP pairs get thinner liquidity than local venues.\n\n## How do the routes compare?\n\n| Route | Speed (end to end) | Typical cost | KYC | Best for |\n|---|---|---|---|---|\n| Payout API | Minutes | Quoted FX rate + provider fee | Provider-run, per receiver | Businesses paying at scale |\n| Colombian exchange | Minutes to hours | 0.1-0.5% trade + withdrawal | Full, per account | Individuals, occasional cash-out |\n| P2P marketplace | Minutes to hours | Spread-dependent | Varies by venue | Small amounts, no business trail |\n| Global exchange + PSE | Minutes to hours | Stacked (trade + FX + withdrawal) | Full, per account | Funds already on the exchange |\n\nCompare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. Provider pricing models are compared in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n\n## What are Colombia's rules for USDC to COP in 2026?\n\nColombia does not have a consolidated VASP license the way Brazil does. What exists instead, as of 2026:\n\n- **No ban, no dedicated license.** DIAN's Unified Concept 1621 of 2023 confirms cryptoassets are not legal tender in Colombia but their commercial use is permitted. DIAN itself has called for sector-specific regulation, which does not exist yet.\n- **Proyecto de Ley 510 de 2025** would have created the licensing regime DIAN is asking for: a framework covering VASP oversight, consumer protection, AML\u002FCTF measures, and financial education, filed in the Chamber of Representatives in February 2025 with Representative Julián López as lead sponsor. It passed committee and plenary debate in the Chamber but was archived under Article 190 of Law 5 of 1992, the rule that shelves a bill not passed within two ordinary legislative sessions, before reaching the Senate. The Chamber's own bill tracker lists it as archived, and [Portafolio](https:\u002F\u002Fwww.portafolio.co\u002Feconomia\u002Fmercado-cripto-queda-sin-regulacion-integral-tras-archivo-de-ley-pese-a-mayores-controles-tributarios-500476), Valora Analitik, and Infobae reported the archival in mid-August 2026. The Superintendencia Financiera has separately run a public consultation on a draft circular covering how banks may relate to VASPs.\n- **AML reporting already applies.** UIAF Resolution 314 of 2021 requires VASPs to file Suspicious Transaction Reports immediately on detection, plus a monthly report through the SIREL platform even when nothing suspicious occurred. This obligation exists independent of Proyecto de Ley 510.\n\nOne operational rule dominates day-to-day payouts: PSE moves money on bank processing windows, not instantly. A transfer initiated late at night or on a bank holiday can sit until the next window opens, and receiver name or cédula mismatches are rejected the same way Pix and SPEI reject them elsewhere in Latin America.\n\n## Which route fits which business?\n\n- **Freelancer receiving USDC occasionally**: a Colombian exchange account is enough. Watch the spread and keep records; Colombia's tax authority already requires exchanges to report user activity.\n- **Company paying 1 or 2 Colombian contractors**: an exchange works but does not scale; every payment is manual and the compliance trail is yours to build.\n- **Company paying tens to thousands of receivers** (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver KYC, sanctions screening, and delivery over PSE happen inside one API call.\n- **Treasury converting its own balance**: an exchange or OTC desk for large one-off conversions; an API with [virtual accounts](\u002Fvirtual-accounts) if conversions recur as part of a product flow.\n\n## Which network should you send USDC on?\n\nUSDC is issued natively on multiple blockchains, and the network choice affects cost and settlement time on every route. Ethereum mainnet carries the deepest liquidity but the highest fees, often dollars per transfer at busy times. Base, Polygon, Arbitrum, and Solana move the same USDC for cents and settle in seconds to minutes. Two practical rules:\n\n- **Match the destination's supported networks.** A Colombian exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.\n- **Prefer a cheap network your counterparty supports.** For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same COP amount regardless.\n\nThe token is worth one dollar on every chain; only the transport differs. More on how the token itself works: [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin).\n\n## Why does Colombia have so much stablecoin volume?\n\nRemittances are the largest single reason. Colombia received a record 13.098 billion dollars in remittances in 2025, up 10.6 percent from 2024's 11.843 billion, equal to roughly 3 percent of GDP, according to Banco de la República data reported by [Colombia's Migration authority](https:\u002F\u002Fportal.migracioncolombia.gov.co\u002Fdetalle-noticia\u002Fagenda-migcol\u002Fcomunicaciones-y-prensa\u002Fcolombia-recibio-13098-millones-de-dolares-en-remesas-en-2025). Most of that still arrives through traditional money transfer operators, but the peso's volatility against the dollar gives senders and receivers alike a reason to hold value in USDC between the moment it is sent and the moment it is spent, rather than converting immediately at each leg.\n\n## How are USDC to COP conversions taxed?\n\nColombia taxes crypto disposals for individuals and companies under its ordinary income tax rules; DIAN treats cryptoassets as taxable assets, not currency, so selling USDC for COP is a disposal event if the peso value received differs from cost basis. For companies, conversions flow through ordinary corporate accounting, and payouts to Colombian contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.\n\nTwo habits save pain later. Keep the COP value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over PSE from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.\n\n## Where these routes fall short\n\nHonest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin COP liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route settles instantly around the clock: PSE's bank windows are a real constraint that Pix and Transfers 3.0 do not share, so plan payroll runs around business hours. AI agents that need to reason about a corridor's constraints before initiating a payout are covered in [agentic payments](\u002Fagentic-payments).\n\n## How BlindPay handles USDC to COP\n\nBlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over PSE, typically within minutes during bank processing windows. Receiver verification, sanctions screening, and travel rule data handling are built in, and the FX quote is shown before you commit; the live rate is on the [USDC to COP page](\u002Fusdc-to-cop). The same API pays out over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in [100+ countries](\u002Fcoverage), USDT works the same way, and [pricing](\u002Fpricing) is public. For the Brazil equivalent of this comparison, see [USDC to BRL routes in 2026](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026), or browse the rest of the [resources library](\u002Fresources\u002Fmore).\n\n## Methodology and sources\n\nRail facts from BlindPay's own corridor data. Adoption statistic from Chainalysis's 2025 Latin America crypto adoption report ([chainalysis.com](https:\u002F\u002Fwww.chainalysis.com\u002Fblog\u002Flatin-america-crypto-adoption-2025\u002F)). Remittance figures from Banco de la República data as reported by Colombia's Migración authority ([migracioncolombia.gov.co](https:\u002F\u002Fportal.migracioncolombia.gov.co\u002Fdetalle-noticia\u002Fagenda-migcol\u002Fcomunicaciones-y-prensa\u002Fcolombia-recibio-13098-millones-de-dolares-en-remesas-en-2025)). Regulatory facts from DIAN's Unified Concept 1621 of 2023, UIAF Resolution 314 of 2021, and Proyecto de Ley 510 de 2025's status on the [Chamber of Representatives' bill tracker](https:\u002F\u002Fwww.camara.gov.co\u002Fservicios-activos-virtuales), confirmed by [Portafolio's](https:\u002F\u002Fwww.portafolio.co\u002Feconomia\u002Fmercado-cripto-queda-sin-regulacion-integral-tras-archivo-de-ley-pese-a-mayores-controles-tributarios-500476) August 2026 reporting on its archival. Exchange fee ranges reflect published fee schedules of major venues as of 2026; live BlindPay FX quotes are on the [corridor page](\u002Fusdc-to-cop). Regulatory status described as of September 2026.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":12138,"description":12436},"USDC to COP in 2026: routes, fees, and rules","resources\u002Fmore\u002Fusdc-to-cop-routes-2026","tAkpShFICwt4uKdamB9A56ABcI8sxds0QTTUTYL578o",{"id":12460,"title":12461,"authors":6,"body":12462,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":10050,"description":12740,"extension":342,"faq":12741,"howto":6,"isBlog":359,"isChangelog":359,"meta":12757,"navigation":362,"path":7229,"pillar":359,"products":6,"rawbody":12758,"role":6,"seo":12759,"seoTitle":12760,"stem":12761,"thumbnail":6,"updated":10050,"__hash__":12762},"content\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026.md","USDC to MXN in 2026: routes, fees, and rules compared",{"type":8,"value":12463,"toc":12729},[12464,12469,12472,12476,12483,12489,12494,12500,12502,12571,12575,12579,12581,12601,12604,12606,12639,12641,12643,12655,12659,12663,12666,12669,12671,12674,12678,12699,12701,12725],[11,12465,12466,12467,227],{},"There are four practical routes from USDC to Mexican pesos in 2026: a stablecoin payout API delivering SPEI directly, a Mexican exchange off-ramp, a P2P trade, or a global exchange with an MXN\u002FSPEI ramp. They differ on fees, speed, and KYC. See the live rate on our ",[136,12468,11519],{"href":10736},[11,12470,12471],{},"The backdrop matters. SPEI, the interbank payment system run by Banco de Mexico, settles transfers in near real time, 24\u002F7, and Mexico is the world's second-largest remittance recipient after India: Banxico reported $61.8 billion arriving in 2025, even after a 4.6 percent drop from 2024, the biggest annual decline since 2009. Nearly all of it, 99.1 percent, already moves electronically rather than in cash. Every serious USDC-to-MXN route ends in a SPEI transfer, and a Senate bill introduced in May 2026 would give peso-pegged stablecoins their own licensing regime for the first time.",[18,12473,12475],{"id":12474},"what-are-the-four-routes-from-usdc-to-mxn","What are the four routes from USDC to MXN?",[11,12477,12478,12480,12481,227],{},[119,12479,11531],{}," A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos via SPEI to the receiver's CLABE, after verifying the receiver's identity on its own side (SPEI itself does not). One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: ",[136,12482,1492],{"href":618},[11,12484,12485,12488],{},[119,12486,12487],{},"Route 2: Mexican exchange off-ramp."," Send USDC to a local exchange, sell for MXN, withdraw via SPEI. Trading fees vary by provider, plus network and withdrawal costs. Full KYC is required for the exchange account. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.",[11,12490,12491,12493],{},[119,12492,11545],{}," Trade USDC directly with a counterparty who sends you a SPEI transfer. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.",[11,12495,12496,12499],{},[119,12497,12498],{},"Route 4: Global exchange with an MXN\u002FSPEI ramp."," Some global exchanges support MXN deposits and withdrawals over SPEI. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and MXN pairs get thinner liquidity than local venues.",[18,12501,11556],{"id":11555},[39,12503,12504,12518],{},[42,12505,12506],{},[45,12507,12508,12510,12512,12514,12516],{},[48,12509,11565],{},[48,12511,11568],{},[48,12513,1100],{},[48,12515,11573],{},[48,12517,785],{},[61,12519,12520,12532,12546,12558],{},[45,12521,12522,12524,12526,12528,12530],{},[66,12523,11582],{},[66,12525,1175],{},[66,12527,11587],{},[66,12529,11590],{},[66,12531,11593],{},[45,12533,12534,12537,12539,12542,12544],{},[66,12535,12536],{},"Mexican exchange",[66,12538,11601],{},[66,12540,12541],{},"Varies by provider, trade + withdrawal",[66,12543,11607],{},[66,12545,11610],{},[45,12547,12548,12550,12552,12554,12556],{},[66,12549,11615],{},[66,12551,11601],{},[66,12553,11620],{},[66,12555,11623],{},[66,12557,11626],{},[45,12559,12560,12563,12565,12567,12569],{},[66,12561,12562],{},"Global exchange + SPEI",[66,12564,11601],{},[66,12566,11636],{},[66,12568,11607],{},[66,12570,11641],{},[11,12572,11962,12573,227],{},[136,12574,9869],{"href":771},[18,12576,12578],{"id":12577},"what-are-mexicos-rules-for-usdc-to-mxn-in-2026","What are Mexico's rules for USDC to MXN in 2026?",[11,12580,11971],{},[171,12582,12583,12589,12595],{},[148,12584,12585,12588],{},[119,12586,12587],{},"The Fintech Law"," (Ley para Regular las Instituciones de Tecnologia Financiera, enacted 2018) is the base framework for virtual asset activity in Mexico, alongside the federal anti-money-laundering law. Banco de Mexico sets how financial institutions may interact with virtual assets; the CNBV supervises banks and fintech companies for compliance.",[148,12590,12591,12594],{},[119,12592,12593],{},"Banks stay out of public-facing crypto."," Mexican banks are generally barred from offering crypto services directly to retail customers; non-bank exchanges and payment companies operate outside that restriction, which is why the exchange and payout-API routes exist as separate businesses from the banking system.",[148,12596,12597,12600],{},[119,12598,12599],{},"A dedicated stablecoin regime is pending, not yet law."," The Murat Initiative, introduced in the Senate in May 2026, would create a licensing regime for Activos Virtuales Estables Referenciados en Moneda Nacional, peso-pegged stablecoins that guarantee par convertibility. It would require 1:1 reserve backing, bankruptcy-remote reserves, and Banxico authorization for foreign issuers, with criminal penalties for unauthorized issuance. As of this writing it has not passed; treat it as a signal of direction, not current law.",[11,12602,12603],{},"One operational rule dominates day-to-day payouts, and it cuts the opposite way from Brazil's Pix: SPEI does not check that the beneficiary's name matches the account. It credits a transfer based on the CLABE, the 18-digit account number, alone. A well-formed CLABE confirms the number is valid and names the receiving bank; it does not confirm who holds the account. Getting the right CLABE, and confirming who controls it before the first transfer, sits entirely with the sender.",[18,12605,11687],{"id":11686},[171,12607,12608,12613,12619,12624,12633],{},[148,12609,12610,12612],{},[119,12611,11694],{},": a Mexican exchange account is enough. Confirm the CLABE before every payout and keep records for tax.",[148,12614,12615,12618],{},[119,12616,12617],{},"Company paying 1 or 2 Mexican contractors",": an exchange works but does not scale; every payment is manual and CLABE verification is on you each time.",[148,12620,12621,12623],{},[119,12622,11706],{}," (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver verification, sanctions screening, and delivery over SPEI happen inside one API call instead of one manual check per transfer.",[148,12625,12626,12629,12630,12632],{},[119,12627,12628],{},"AI agents paying suppliers or contractors autonomously",": agent-driven payouts need the same SPEI delivery and receiver checks, callable without a dashboard. See ",[136,12631,11771],{"href":11770}," for how that works over an API or MCP server.",[148,12634,12635,11713,12637,11716],{},[119,12636,11712],{},[136,12638,632],{"href":138},[18,12640,11720],{"id":11719},[11,12642,11723],{},[171,12644,12645,12650],{},[148,12646,12647,12649],{},[119,12648,11730],{}," A Mexican exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.",[148,12651,12652,12654],{},[119,12653,11736],{}," For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same MXN amount regardless.",[11,12656,11740,12657,227],{},[136,12658,9801],{"href":9800},[18,12660,12662],{"id":12661},"how-are-usdc-to-mxn-conversions-taxed","How are USDC to MXN conversions taxed?",[11,12664,12665],{},"Mexico has no crypto-specific tax law. The SAT, Mexico's tax authority, treats cryptocurrency disposals under the existing income tax rules for the sale of goods: selling USDC for MXN is a taxable disposal, and any gain over cost basis adds to ordinary income for the year. Holding is not a taxable event; converting or spending is. For companies, conversions flow through ordinary corporate accounting, and payouts to Mexican contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.",[11,12667,12668],{},"Two habits save pain later. Keep the MXN value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over SPEI from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.",[18,12670,11746],{"id":11745},[11,12672,12673],{},"Honest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin MXN liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route removes the sender's responsibility to confirm a CLABE belongs to who it should, since SPEI itself will not catch a mismatch.",[18,12675,12677],{"id":12676},"how-blindpay-handles-usdc-to-mxn","How BlindPay handles USDC to MXN",[11,12679,12680,12681,12684,12685,12070,12687,12073,12691,12693,12694,12387,12697,227],{},"BlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over SPEI, usually within minutes. Receiver verification, sanctions screening, and travel rule data handling are built in on our side to cover the gap SPEI leaves open, and the FX quote is shown before you commit; the live rate is on the ",[136,12682,12683],{"href":10736},"USDC to MXN page",". The same API pays out over Pix, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in ",[136,12686,11763],{"href":1335},[136,12688,12690],{"href":12689},"\u002Fusdt-to-mxn","USDT to MXN",[136,12692,1340],{"href":307}," is public. For the Brazil side of this comparison, see ",[136,12695,12696],{"href":5852},"USDC to BRL routes for 2026",[136,12698,12391],{"href":12390},[18,12700,1350],{"id":1349},[11,12702,12703,12704,12709,12710,12715,12716,12721,12722,12724],{},"Rail and regulatory facts from primary and named sources: Banco de Mexico's SPEI documentation (",[136,12705,12708],{"href":12706,"rel":12707},"https:\u002F\u002Fwww.banxico.org.mx\u002Fservices\u002Finterbanking-electronic-payme.html",[414],"banxico.org.mx","), 2025 remittance figures reported by Banxico via ",[136,12711,12714],{"href":12712,"rel":12713},"https:\u002F\u002Fmexiconewsdaily.com\u002Fnews\u002Fremittance-biggest-decline-in-16-years\u002F",[414],"Mexico News Daily",", and reporting on the Fintech Law and the May 2026 Senate stablecoin bill via ",[136,12717,12720],{"href":12718,"rel":12719},"https:\u002F\u002Fwww.legalparadox.com\u002Finsights\u002Fstablecoin-regulation-in-mexico-guide-for-foreign-issuers",[414],"Legal Paradox",". Exchange fee language stays general rather than quoting a range, because published fee schedules vary by provider and change without notice; live BlindPay FX quotes are on the ",[136,12723,11519],{"href":10736},". Regulatory status described as of September 2026, and the Senate bill's progress should be checked before relying on it as settled law.",[11,12726,12727],{},[324,12728,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":12730},[12731,12732,12733,12734,12735,12736,12737,12738,12739],{"id":12474,"depth":329,"text":12475},{"id":11555,"depth":329,"text":11556},{"id":12577,"depth":329,"text":12578},{"id":11686,"depth":329,"text":11687},{"id":11719,"depth":329,"text":11720},{"id":12661,"depth":329,"text":12662},{"id":11745,"depth":329,"text":11746},{"id":12676,"depth":329,"text":12677},{"id":1349,"depth":329,"text":1350},"Four ways to convert USDC to Mexican pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with SPEI. Fees, speed, KYC.",[12742,12745,12748,12751,12754],{"q":12743,"a":12744},"What is the cheapest way to convert USDC to MXN?","For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Mexican exchanges are usually cheapest, though trading fees vary by provider and should be checked before each conversion.",{"q":12746,"a":12747},"How fast does a USDC to MXN conversion arrive?","Over SPEI, minutes. SPEI settles in near real time and runs 24\u002F7, so end-to-end time is dominated by the conversion step: typically a few minutes on exchanges and payout APIs.",{"q":12749,"a":12750},"Is converting USDC to MXN legal in Mexico?","Yes. Mexico regulates virtual asset activity under the 2018 Fintech Law, with Banco de Mexico and the CNBV as the main supervisors. Banks are generally barred from offering crypto services directly to the public, but non-bank exchanges and payment companies can operate. A Senate bill introduced in May 2026 would add a dedicated licensing regime for peso-pegged stablecoins.",{"q":12752,"a":12753},"Does SPEI verify the receiver before crediting a payment?","No, not by name. SPEI credits a transfer based on the CLABE, an 18-digit standardized account number, not on the beneficiary's name matching the account. A valid CLABE confirms the number is well formed and identifies the receiving bank; it does not confirm who owns the account. Getting the CLABE right, and confirming who holds it before sending, is the sender's responsibility.",{"q":12755,"a":12756},"What is a CLABE number?","CLABE (Clave Bancaria Estandarizada) is Mexico's 18-digit standard bank account number: 3 digits for the bank, 3 for the branch or region, 11 for the account, and a check digit. Every SPEI transfer needs a correct CLABE; every Mexican bank and most exchanges display it in the account details.",{"author":361},"---\ntitle: \"USDC to MXN in 2026: routes, fees, and rules compared\"\nseoTitle: \"USDC to MXN in 2026: routes, fees, and rules\"\ndescription: \"Four ways to convert USDC to Mexican pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with SPEI. Fees, speed, KYC.\"\ndate: \"2026-09-01\"\nauthor: \"BlindPay Team\"\nupdated: \"2026-09-01\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is the cheapest way to convert USDC to MXN?\"\n    a: \"For businesses paying many receivers, a stablecoin payout API is typically cheapest in total cost because it removes manual work, spread stacking, and failed-payment overhead. For individuals, Mexican exchanges are usually cheapest, though trading fees vary by provider and should be checked before each conversion.\"\n  - q: \"How fast does a USDC to MXN conversion arrive?\"\n    a: \"Over SPEI, minutes. SPEI settles in near real time and runs 24\u002F7, so end-to-end time is dominated by the conversion step: typically a few minutes on exchanges and payout APIs.\"\n  - q: \"Is converting USDC to MXN legal in Mexico?\"\n    a: \"Yes. Mexico regulates virtual asset activity under the 2018 Fintech Law, with Banco de Mexico and the CNBV as the main supervisors. Banks are generally barred from offering crypto services directly to the public, but non-bank exchanges and payment companies can operate. A Senate bill introduced in May 2026 would add a dedicated licensing regime for peso-pegged stablecoins.\"\n  - q: \"Does SPEI verify the receiver before crediting a payment?\"\n    a: \"No, not by name. SPEI credits a transfer based on the CLABE, an 18-digit standardized account number, not on the beneficiary's name matching the account. A valid CLABE confirms the number is well formed and identifies the receiving bank; it does not confirm who owns the account. Getting the CLABE right, and confirming who holds it before sending, is the sender's responsibility.\"\n  - q: \"What is a CLABE number?\"\n    a: \"CLABE (Clave Bancaria Estandarizada) is Mexico's 18-digit standard bank account number: 3 digits for the bank, 3 for the branch or region, 11 for the account, and a check digit. Every SPEI transfer needs a correct CLABE; every Mexican bank and most exchanges display it in the account details.\"\n---\n\nThere are four practical routes from USDC to Mexican pesos in 2026: a stablecoin payout API delivering SPEI directly, a Mexican exchange off-ramp, a P2P trade, or a global exchange with an MXN\u002FSPEI ramp. They differ on fees, speed, and KYC. See the live rate on our [corridor page](\u002Fusdc-to-mxn).\n\nThe backdrop matters. SPEI, the interbank payment system run by Banco de Mexico, settles transfers in near real time, 24\u002F7, and Mexico is the world's second-largest remittance recipient after India: Banxico reported $61.8 billion arriving in 2025, even after a 4.6 percent drop from 2024, the biggest annual decline since 2009. Nearly all of it, 99.1 percent, already moves electronically rather than in cash. Every serious USDC-to-MXN route ends in a SPEI transfer, and a Senate bill introduced in May 2026 would give peso-pegged stablecoins their own licensing regime for the first time.\n\n## What are the four routes from USDC to MXN?\n\n**Route 1: Stablecoin payout API.** A business sends USDC through an API; the provider converts at a quoted rate and delivers pesos via SPEI to the receiver's CLABE, after verifying the receiver's identity on its own side (SPEI itself does not). One integration replaces the per-transfer manual work of the other three routes. This is the route built for payroll, contractor payments, and marketplace payouts. How this model works in general: [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\n**Route 2: Mexican exchange off-ramp.** Send USDC to a local exchange, sell for MXN, withdraw via SPEI. Trading fees vary by provider, plus network and withdrawal costs. Full KYC is required for the exchange account. Best for individuals and small volumes; the drawbacks are manual work per conversion and per-account limits.\n\n**Route 3: P2P marketplaces.** Trade USDC directly with a counterparty who sends you a SPEI transfer. Spreads can be competitive and limits flexible, but counterparty risk is real, quality varies, and business use is impractical: no receipts, no compliance trail, no scale.\n\n**Route 4: Global exchange with an MXN\u002FSPEI ramp.** Some global exchanges support MXN deposits and withdrawals over SPEI. Useful if your assets already sit there; fees stack (trading plus conversion plus withdrawal) and MXN pairs get thinner liquidity than local venues.\n\n## How do the routes compare?\n\n| Route | Speed (end to end) | Typical cost | KYC | Best for |\n|---|---|---|---|---|\n| Payout API | Minutes | Quoted FX rate + provider fee | Provider-run, per receiver | Businesses paying at scale |\n| Mexican exchange | Minutes to hours | Varies by provider, trade + withdrawal | Full, per account | Individuals, occasional cash-out |\n| P2P marketplace | Minutes to hours | Spread-dependent | Varies by venue | Small amounts, no business trail |\n| Global exchange + SPEI | Minutes to hours | Stacked (trade + FX + withdrawal) | Full, per account | Funds already on the exchange |\n\nCompare total amount received, not the headline fee: a low fee over a poor rate loses to a fair rate with a visible fee. Provider pricing models are compared in [best stablecoin payment providers in 2026](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n\n## What are Mexico's rules for USDC to MXN in 2026?\n\nThree layers, as of 2026:\n\n- **The Fintech Law** (Ley para Regular las Instituciones de Tecnologia Financiera, enacted 2018) is the base framework for virtual asset activity in Mexico, alongside the federal anti-money-laundering law. Banco de Mexico sets how financial institutions may interact with virtual assets; the CNBV supervises banks and fintech companies for compliance.\n- **Banks stay out of public-facing crypto.** Mexican banks are generally barred from offering crypto services directly to retail customers; non-bank exchanges and payment companies operate outside that restriction, which is why the exchange and payout-API routes exist as separate businesses from the banking system.\n- **A dedicated stablecoin regime is pending, not yet law.** The Murat Initiative, introduced in the Senate in May 2026, would create a licensing regime for Activos Virtuales Estables Referenciados en Moneda Nacional, peso-pegged stablecoins that guarantee par convertibility. It would require 1:1 reserve backing, bankruptcy-remote reserves, and Banxico authorization for foreign issuers, with criminal penalties for unauthorized issuance. As of this writing it has not passed; treat it as a signal of direction, not current law.\n\nOne operational rule dominates day-to-day payouts, and it cuts the opposite way from Brazil's Pix: SPEI does not check that the beneficiary's name matches the account. It credits a transfer based on the CLABE, the 18-digit account number, alone. A well-formed CLABE confirms the number is valid and names the receiving bank; it does not confirm who holds the account. Getting the right CLABE, and confirming who controls it before the first transfer, sits entirely with the sender.\n\n## Which route fits which business?\n\n- **Freelancer receiving USDC occasionally**: a Mexican exchange account is enough. Confirm the CLABE before every payout and keep records for tax.\n- **Company paying 1 or 2 Mexican contractors**: an exchange works but does not scale; every payment is manual and CLABE verification is on you each time.\n- **Company paying tens to thousands of receivers** (payroll, marketplaces, remittance products): a payout API is the only route that scales. Receiver verification, sanctions screening, and delivery over SPEI happen inside one API call instead of one manual check per transfer.\n- **AI agents paying suppliers or contractors autonomously**: agent-driven payouts need the same SPEI delivery and receiver checks, callable without a dashboard. See [agentic payments](\u002Fagentic-payments) for how that works over an API or MCP server.\n- **Treasury converting its own balance**: an exchange or OTC desk for large one-off conversions; an API with [virtual accounts](\u002Fvirtual-accounts) if conversions recur as part of a product flow.\n\n## Which network should you send USDC on?\n\nUSDC is issued natively on multiple blockchains, and the network choice affects cost and settlement time on every route. Ethereum mainnet carries the deepest liquidity but the highest fees, often dollars per transfer at busy times. Base, Polygon, Arbitrum, and Solana move the same USDC for cents and settle in seconds to minutes. Two practical rules:\n\n- **Match the destination's supported networks.** A Mexican exchange that only credits Ethereum-based USDC will not see a Solana transfer; funds sent on an unsupported network are painful or impossible to recover. Check the deposit page or API documentation before sending.\n- **Prefer a cheap network your counterparty supports.** For payout APIs this is usually a non-issue: the provider accepts several networks and quotes the same MXN amount regardless.\n\nThe token is worth one dollar on every chain; only the transport differs. More on how the token itself works: [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin).\n\n## How are USDC to MXN conversions taxed?\n\nMexico has no crypto-specific tax law. The SAT, Mexico's tax authority, treats cryptocurrency disposals under the existing income tax rules for the sale of goods: selling USDC for MXN is a taxable disposal, and any gain over cost basis adds to ordinary income for the year. Holding is not a taxable event; converting or spending is. For companies, conversions flow through ordinary corporate accounting, and payouts to Mexican contractors or employees keep their normal labor and withholding treatment regardless of the rail used to deliver them.\n\nTwo habits save pain later. Keep the MXN value at acquisition and at disposal for every lot (exchanges and payout APIs both provide statements). And do not confuse the rail with the obligation: paying someone over SPEI from a stablecoin balance does not change what your business owes in taxes or reporting; it only changes how fast the money arrives.\n\n## Where these routes fall short\n\nHonest limits, route by route. Exchanges cap withdrawal amounts and require every receiver to have and manage their own account. P2P has no place in a business flow. Global exchanges quote thin MXN liquidity at bad hours. Payout APIs charge a provider fee on top of FX and require onboarding (KYB for your business, KYC for receivers) before the first real transfer; if you need an anonymous or same-minute one-off conversion, an API is the wrong tool. And no route removes the sender's responsibility to confirm a CLABE belongs to who it should, since SPEI itself will not catch a mismatch.\n\n## How BlindPay handles USDC to MXN\n\nBlindPay is a stablecoin API: your business sends USDC, the receiver gets pesos over SPEI, usually within minutes. Receiver verification, sanctions screening, and travel rule data handling are built in on our side to cover the gap SPEI leaves open, and the FX quote is shown before you commit; the live rate is on the [USDC to MXN page](\u002Fusdc-to-mxn). The same API pays out over Pix, ACH, and SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations) in [100+ countries](\u002Fcoverage), USDT works the same way ([USDT to MXN](\u002Fusdt-to-mxn)), and [pricing](\u002Fpricing) is public. For the Brazil side of this comparison, see [USDC to BRL routes for 2026](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026), or browse the rest of the [resources library](\u002Fresources\u002Fmore).\n\n## Methodology and sources\n\nRail and regulatory facts from primary and named sources: Banco de Mexico's SPEI documentation ([banxico.org.mx](https:\u002F\u002Fwww.banxico.org.mx\u002Fservices\u002Finterbanking-electronic-payme.html)), 2025 remittance figures reported by Banxico via [Mexico News Daily](https:\u002F\u002Fmexiconewsdaily.com\u002Fnews\u002Fremittance-biggest-decline-in-16-years\u002F), and reporting on the Fintech Law and the May 2026 Senate stablecoin bill via [Legal Paradox](https:\u002F\u002Fwww.legalparadox.com\u002Finsights\u002Fstablecoin-regulation-in-mexico-guide-for-foreign-issuers). Exchange fee language stays general rather than quoting a range, because published fee schedules vary by provider and change without notice; live BlindPay FX quotes are on the [corridor page](\u002Fusdc-to-mxn). Regulatory status described as of September 2026, and the Senate bill's progress should be checked before relying on it as settled law.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":12461,"description":12740},"USDC to MXN in 2026: routes, fees, and rules","resources\u002Fmore\u002Fusdc-to-mxn-routes-2026","8zXvcnguVxCdPcxw-s_BSNUQgfMSTccR0bARRcXzxTk",{"id":4,"title":5,"authors":6,"body":12764,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":340,"description":341,"extension":342,"faq":12974,"howto":6,"isBlog":359,"isChangelog":359,"meta":12980,"navigation":362,"path":363,"pillar":359,"products":6,"rawbody":364,"role":6,"seo":12981,"seoTitle":366,"stem":367,"thumbnail":6,"updated":6,"__hash__":368},{"type":8,"value":12765,"toc":12964},[12766,12768,12770,12772,12774,12776,12778,12780,12782,12828,12830,12832,12834,12838,12842,12848,12850,12860,12862,12864,12866,12874,12878,12882,12886,12890,12892,12894,12910,12912,12914,12916,12938,12944,12946,12950,12954,12956,12960],[11,12767,13],{},[11,12769,16],{},[18,12771,21],{"id":20},[11,12773,24],{},[11,12775,27],{},[11,12777,30],{},[18,12779,34],{"id":33},[11,12781,37],{},[39,12783,12784,12796],{},[42,12785,12786],{},[45,12787,12788,12790,12792,12794],{},[48,12789,50],{},[48,12791,53],{},[48,12793,56],{},[48,12795,59],{},[61,12797,12798,12808,12818],{},[45,12799,12800,12802,12804,12806],{},[66,12801,68],{},[66,12803,71],{},[66,12805,74],{},[66,12807,77],{},[45,12809,12810,12812,12814,12816],{},[66,12811,82],{},[66,12813,85],{},[66,12815,88],{},[66,12817,91],{},[45,12819,12820,12822,12824,12826],{},[66,12821,96],{},[66,12823,99],{},[66,12825,102],{},[66,12827,105],{},[11,12829,108],{},[18,12831,112],{"id":111},[11,12833,115],{},[11,12835,12836,122],{},[119,12837,121],{},[11,12839,12840,128],{},[119,12841,127],{},[11,12843,12844,134,12846,140],{},[119,12845,133],{},[136,12847,139],{"href":138},[11,12849,143],{},[145,12851,12852,12854,12856,12858],{},[148,12853,150],{},[148,12855,153],{},[148,12857,156],{},[148,12859,159],{},[11,12861,162],{},[18,12863,166],{"id":165},[11,12865,169],{},[171,12867,12868,12870,12872],{},[148,12869,175],{},[148,12871,178],{},[148,12873,181],{},[11,12875,12876,187],{},[119,12877,186],{},[11,12879,12880,193],{},[119,12881,192],{},[11,12883,12884,199],{},[119,12885,198],{},[11,12887,202,12888,207],{},[204,12889,206],{},[18,12891,211],{"id":210},[11,12893,214],{},[171,12895,12896,12902,12906],{},[148,12897,12898,222,12900,227],{},[119,12899,221],{},[136,12901,226],{"href":225},[148,12903,12904,233],{},[119,12905,232],{},[148,12907,12908,239],{},[119,12909,238],{},[11,12911,242],{},[18,12913,246],{"id":245},[11,12915,249],{},[145,12917,12918,12922,12926,12930,12934],{},[148,12919,12920,257],{},[119,12921,256],{},[148,12923,12924],{},[119,12925,262],{},[148,12927,12928],{},[119,12929,267],{},[148,12931,12932],{},[119,12933,272],{},[148,12935,12936,278],{},[119,12937,277],{},[11,12939,281,12940,286,12942,227],{},[136,12941,285],{"href":284},[136,12943,290],{"href":289},[18,12945,294],{"id":293},[11,12947,12948,301],{},[136,12949,300],{"href":299},[11,12951,304,12952,227],{},[136,12953,308],{"href":307},[18,12955,312],{"id":311},[11,12957,315,12958,320],{},[136,12959,319],{"href":318},[11,12961,12962],{},[324,12963,326],{},{"title":328,"searchDepth":329,"depth":329,"links":12965},[12966,12967,12968,12969,12970,12971,12972,12973],{"id":20,"depth":329,"text":21},{"id":33,"depth":329,"text":34},{"id":111,"depth":329,"text":112},{"id":165,"depth":329,"text":166},{"id":210,"depth":329,"text":211},{"id":245,"depth":329,"text":246},{"id":293,"depth":329,"text":294},{"id":311,"depth":329,"text":312},[12975,12976,12977,12978,12979],{"q":345,"a":346},{"q":348,"a":349},{"q":351,"a":352},{"q":354,"a":355},{"q":357,"a":358},{"author":361},{"title":5,"description":341},{"id":12983,"title":12984,"authors":6,"body":12985,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":13283,"description":13284,"extension":342,"faq":13285,"howto":6,"isBlog":359,"isChangelog":359,"meta":13298,"navigation":362,"path":13299,"pillar":359,"products":6,"rawbody":13300,"role":6,"seo":13301,"seoTitle":13302,"stem":13303,"thumbnail":6,"updated":13283,"__hash__":13304},"content\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp.md","What is a crypto on-ramp and off-ramp? A guide for fintech builders",{"type":8,"value":12986,"toc":13274},[12987,12991,12994,12998,13001,13024,13027,13031,13039,13059,13062,13066,13069,13140,13143,13147,13153,13159,13165,13169,13172,13219,13222,13226,13233,13240,13243,13247,13256,13262,13270],[11,12988,12989],{},[324,12990,7505],{},[11,12992,12993],{},"A crypto on-ramp converts fiat currency (dollars, reais, pesos) into crypto or stablecoins delivered to a wallet. A crypto off-ramp converts crypto or stablecoins back into fiat delivered to a bank account. They are the two ends of the same pipe: the on-ramp is how money enters a blockchain, and the off-ramp is how it leaves.",[18,12995,12997],{"id":12996},"how-does-a-crypto-on-ramp-work","How does a crypto on-ramp work?",[11,12999,13000],{},"An on-ramp takes a fiat payment on one side and delivers tokens on the other. The six steps below are the same whether the sender is a person paying by card or a company wiring $2 million.",[145,13002,13003,13006,13012,13015,13018,13021],{},[148,13004,13005],{},"The sender submits a fiat payment: a bank transfer, a card payment, or a local instant payment such as Pix or SPEI.",[148,13007,13008,13009,13011],{},"The provider verifies the sender's identity (KYC for a person, ",[136,13010,3301],{"href":3211}," for a business) and screens them against sanctions lists.",[148,13013,13014],{},"The provider quotes an exchange rate and a fee for converting that fiat amount into the chosen token.",[148,13016,13017],{},"The fiat lands in the provider's account and is matched to the quote.",[148,13019,13020],{},"The provider sends the equivalent stablecoin or crypto to the destination wallet on the chosen network.",[148,13022,13023],{},"The on-chain transaction confirms, and the provider emits a webhook marking the on-ramp complete.",[11,13025,13026],{},"Steps 1 and 2 happen once per sender. Steps 3 through 6 repeat on every payment.",[18,13028,13030],{"id":13029},"how-does-a-crypto-off-ramp-work","How does a crypto off-ramp work?",[11,13032,13033,13034,13038],{},"An off-ramp runs the same pipe in reverse: tokens in, fiat out to a verified bank account. The ",[136,13035,13037],{"href":13036},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","stablecoin off-ramp explainer"," covers the regulatory side in more depth.",[145,13040,13041,13044,13047,13050,13053,13056],{},[148,13042,13043],{},"The sender requests a quote to convert a token amount into a fiat currency for a verified bank account.",[148,13045,13046],{},"The provider returns a rate, a fee, and a quote ID with an expiry timestamp.",[148,13048,13049],{},"The sender transfers the stablecoin to the provider's deposit address on the specified network.",[148,13051,13052],{},"The provider confirms the on-chain deposit and locks the conversion at the quoted rate.",[148,13054,13055],{},"The provider pays out fiat over a local rail such as ACH, wire, Pix, SPEI, or SEPA.",[148,13057,13058],{},"The bank account is credited and the provider emits a settlement event.",[11,13060,13061],{},"The on-chain transfer in step 3 is final once confirmed. That is why account verification happens before any money moves.",[18,13063,13065],{"id":13064},"what-is-the-difference-between-an-on-ramp-and-an-off-ramp","What is the difference between an on-ramp and an off-ramp?",[11,13067,13068],{},"The two differ in direction, and everything else follows from that.",[39,13070,13071,13083],{},[42,13072,13073],{},[45,13074,13075,13077,13080],{},[48,13076],{},[48,13078,13079],{},"On-ramp",[48,13081,13082],{},"Off-ramp",[61,13084,13085,13096,13107,13118,13129],{},[45,13086,13087,13090,13093],{},[66,13088,13089],{},"Direction",[66,13091,13092],{},"Fiat into crypto",[66,13094,13095],{},"Crypto into fiat",[45,13097,13098,13101,13104],{},[66,13099,13100],{},"Input",[66,13102,13103],{},"Bank transfer, card, or instant payment",[66,13105,13106],{},"Stablecoin or crypto sent on-chain",[45,13108,13109,13112,13115],{},[66,13110,13111],{},"Output",[66,13113,13114],{},"Tokens in a wallet",[66,13116,13117],{},"Fiat in a bank account",[45,13119,13120,13123,13126],{},[66,13121,13122],{},"Common use case",[66,13124,13125],{},"Funding a wallet, collecting a payment in stablecoins, moving treasury on-chain",[66,13127,13128],{},"Paying a contractor in local currency, cashing out, settling a merchant",[45,13130,13131,13134,13137],{},[66,13132,13133],{},"Typical settlement time",[66,13135,13136],{},"Seconds on an instant rail, hours for a wire, up to 2 business days for ACH",[66,13138,13139],{},"Seconds over Pix or SPEI, same-day for ACH, hours for a wire",[11,13141,13142],{},"A payment that starts as a bank transfer and ends as a bank transfer, with a stablecoin in the middle, uses both. That pattern is sometimes called the stablecoin sandwich.",[18,13144,13146],{"id":13145},"why-do-fintech-products-need-an-on-ramp-or-off-ramp","Why do fintech products need an on-ramp or off-ramp?",[11,13148,13149,13152],{},[119,13150,13151],{},"Remittances."," A remittance app collects dollars from a sender in the US, moves value on-chain, and needs an off-ramp to deliver pesos over SPEI or reais over Pix. Without the off-ramp, the recipient gets a token they cannot spend at the grocery store.",[11,13154,13155,13158],{},[119,13156,13157],{},"Payroll."," A company paying contractors in Argentina, Brazil, and Colombia funds one stablecoin balance and off-ramps each payment into the contractor's local bank account. The off-ramp replaces four banking relationships and four pre-funded accounts with one integration.",[11,13160,13161,13164],{},[119,13162,13163],{},"Marketplaces."," A marketplace collects fiat from buyers through an on-ramp, holds the balance as stablecoins, and pays sellers in dozens of countries through an off-ramp. The on-chain balance is what makes a single treasury serve every corridor.",[18,13166,13168],{"id":13167},"what-payment-methods-do-on-ramps-support","What payment methods do on-ramps support?",[11,13170,13171],{},"Coverage varies by provider and by country. These are the methods that matter most, with the tradeoff each one carries.",[171,13173,13174,13180,13186,13192,13197,13202,13207,13213],{},[148,13175,13176,13179],{},[119,13177,13178],{},"Bank wire."," Handles large amounts with no practical ceiling, but costs $15 to $50 and takes hours to a day.",[148,13181,13182,13185],{},[119,13183,13184],{},"ACH (US)."," Cheap and familiar for US senders, but takes same-day to two business days and can be reversed for up to 60 days.",[148,13187,13188,13191],{},[119,13189,13190],{},"SEPA and SEPA Instant (EU)."," Low cost across the eurozone, and the Instant variant settles in seconds, though not every bank supports it.",[148,13193,13194,13196],{},[119,13195,7215],{}," Settles in seconds, 24\u002F7, at near-zero cost, which makes it the best on-ramp rail in Latin America.",[148,13198,13199,13201],{},[119,13200,7225],{}," Same profile as Pix: instant, round the clock, cheap, and universal among Mexican banks.",[148,13203,13204,13206],{},[119,13205,7236],{}," Bank-to-bank with broad coverage, but follows bank processing windows rather than settling instantly.",[148,13208,13209,13212],{},[119,13210,13211],{},"Debit and credit cards."," Instant authorization and the widest reach for consumers, but 2 to 4 percent in fees and the highest chargeback risk.",[148,13214,13215,13218],{},[119,13216,13217],{},"Apple Pay and Google Pay."," Same economics as cards with better conversion on mobile, and the same chargeback exposure.",[11,13220,13221],{},"The pattern is consistent: instant local rails are cheaper and safer than cards, and cards win only on reach and convenience.",[18,13223,13225],{"id":13224},"what-is-the-difference-between-an-on-ramp-provider-and-a-liquidity-provider","What is the difference between an on-ramp provider and a liquidity provider?",[11,13227,13228,13229,13232],{},"An ",[119,13230,13231],{},"on-ramp provider"," is the service a fintech integrates to convert fiat into tokens for its users. It owns the customer-facing flow: payment collection, identity checks, quoting, and delivery.",[11,13234,13235,13236,13239],{},"A ",[119,13237,13238],{},"liquidity provider"," is the counterparty that actually holds the fiat and the tokens and stands ready to exchange one for the other at a price. It is the source of the rate the on-ramp quotes.",[11,13241,13242],{},"Many on-ramps are resellers that route to third-party liquidity, which adds a markup and a dependency. Providers that hold their own liquidity, BlindPay is one example, can return a live executable rate directly from the API instead of a cached one from someone else's book.",[18,13244,13246],{"id":13245},"who-are-on-ramps-designed-for","Who are on-ramps designed for?",[11,13248,13249,13252,13253,13255],{},[119,13250,13251],{},"Fintech developers."," A developer building a wallet, a payments app, or a treasury product needs users to fund accounts from a bank and withdraw to a bank. An on\u002Foff ramp API, such as the one described in ",[136,13254,8690],{"href":479},", replaces months of banking, licensing, and blockchain work with a few endpoints.",[11,13257,13258,13261],{},[119,13259,13260],{},"Neobanks."," A neobank offering dollar accounts to customers in a high-inflation country uses an on-ramp to turn local currency deposits into USDC and an off-ramp to let customers spend or withdraw. The customer sees a dollar balance; the ramps do the conversion underneath.",[11,13263,13264,13266,13267,13269],{},[119,13265,13163],{}," A marketplace or gig platform with sellers in many countries collects buyer payments in fiat and pays sellers in their local currency. BlindPay's ",[136,13268,1261],{"href":299}," product is built for this shape: one balance in, local currency out over Pix, SPEI, PSE, ACH, and SEPA.",[11,13271,13272],{},[324,13273,1397],{},{"title":328,"searchDepth":329,"depth":329,"links":13275},[13276,13277,13278,13279,13280,13281,13282],{"id":12996,"depth":329,"text":12997},{"id":13029,"depth":329,"text":13030},{"id":13064,"depth":329,"text":13065},{"id":13145,"depth":329,"text":13146},{"id":13167,"depth":329,"text":13168},{"id":13224,"depth":329,"text":13225},{"id":13245,"depth":329,"text":13246},"2026-08-19","A crypto on-ramp converts fiat into stablecoins; an off-ramp converts them back into fiat in a bank account. How each works and who they are built for.",[13286,13289,13292,13295],{"q":13287,"a":13288},"Do I need an on-ramp if I already use a stablecoin wallet?","Yes, if any money enters that wallet from a bank account or card. A wallet holds and sends tokens, but it cannot accept dollars, reais, or pesos on its own. An on-ramp is the service that takes the fiat payment, converts it, and delivers stablecoins to the wallet address. Without one, the wallet can only receive tokens that already exist on-chain.",{"q":13290,"a":13291},"Is an on-ramp the same as a crypto exchange?","No. A crypto exchange is a venue where users trade assets against each other and hold balances in an account. An on-ramp is a conversion service that turns a fiat payment into tokens delivered to a wallet, usually embedded inside another product through an API. Exchanges often run an on-ramp internally, but most fintech apps integrate a dedicated on-ramp provider instead of an exchange.",{"q":13293,"a":13294},"How long does a crypto on-ramp take to complete?","The on-chain leg takes seconds to a few minutes on most networks. The fiat leg sets the total: an instant rail like Pix in Brazil or SPEI in Mexico completes in seconds, a card payment authorizes in seconds, ACH takes same-day to two business days, and a wire takes hours. In practice, an on-ramp over an instant rail completes in under five minutes end to end.",{"q":13296,"a":13297},"Are crypto on-ramps and off-ramps regulated?","Yes. In the US, a business that exchanges fiat for virtual currency is a money transmitter under FinCEN rules and must register as a Money Services Business and hold or be exempt from state licenses. Brazil licenses these businesses as virtual asset service providers under Central Bank rules, and the EU covers them under MiCA. A provider that cannot show its registrations should not be integrated.",{"author":361},"\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","---\ntitle: \"What is a crypto on-ramp and off-ramp? A guide for fintech builders\"\nseoTitle: \"What is a crypto on-ramp and off-ramp?\"\ndescription: \"A crypto on-ramp converts fiat into stablecoins; an off-ramp converts them back into fiat in a bank account. How each works and who they are built for.\"\ndate: \"2026-08-19\"\nupdated: \"2026-08-19\"\nauthor: \"BlindPay Team\"\ncategory: \"payments\"\nfaq:\n  - q: \"Do I need an on-ramp if I already use a stablecoin wallet?\"\n    a: \"Yes, if any money enters that wallet from a bank account or card. A wallet holds and sends tokens, but it cannot accept dollars, reais, or pesos on its own. An on-ramp is the service that takes the fiat payment, converts it, and delivers stablecoins to the wallet address. Without one, the wallet can only receive tokens that already exist on-chain.\"\n  - q: \"Is an on-ramp the same as a crypto exchange?\"\n    a: \"No. A crypto exchange is a venue where users trade assets against each other and hold balances in an account. An on-ramp is a conversion service that turns a fiat payment into tokens delivered to a wallet, usually embedded inside another product through an API. Exchanges often run an on-ramp internally, but most fintech apps integrate a dedicated on-ramp provider instead of an exchange.\"\n  - q: \"How long does a crypto on-ramp take to complete?\"\n    a: \"The on-chain leg takes seconds to a few minutes on most networks. The fiat leg sets the total: an instant rail like Pix in Brazil or SPEI in Mexico completes in seconds, a card payment authorizes in seconds, ACH takes same-day to two business days, and a wire takes hours. In practice, an on-ramp over an instant rail completes in under five minutes end to end.\"\n  - q: \"Are crypto on-ramps and off-ramps regulated?\"\n    a: \"Yes. In the US, a business that exchanges fiat for virtual currency is a money transmitter under FinCEN rules and must register as a Money Services Business and hold or be exempt from state licenses. Brazil licenses these businesses as virtual asset service providers under Central Bank rules, and the EU covers them under MiCA. A provider that cannot show its registrations should not be integrated.\"\n---\n\n*Reading time: about 6 minutes.*\n\nA crypto on-ramp converts fiat currency (dollars, reais, pesos) into crypto or stablecoins delivered to a wallet. A crypto off-ramp converts crypto or stablecoins back into fiat delivered to a bank account. They are the two ends of the same pipe: the on-ramp is how money enters a blockchain, and the off-ramp is how it leaves.\n\n## How does a crypto on-ramp work?\n\nAn on-ramp takes a fiat payment on one side and delivers tokens on the other. The six steps below are the same whether the sender is a person paying by card or a company wiring $2 million.\n\n1. The sender submits a fiat payment: a bank transfer, a card payment, or a local instant payment such as Pix or SPEI.\n2. The provider verifies the sender's identity (KYC for a person, [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) for a business) and screens them against sanctions lists.\n3. The provider quotes an exchange rate and a fee for converting that fiat amount into the chosen token.\n4. The fiat lands in the provider's account and is matched to the quote.\n5. The provider sends the equivalent stablecoin or crypto to the destination wallet on the chosen network.\n6. The on-chain transaction confirms, and the provider emits a webhook marking the on-ramp complete.\n\nSteps 1 and 2 happen once per sender. Steps 3 through 6 repeat on every payment.\n\n## How does a crypto off-ramp work?\n\nAn off-ramp runs the same pipe in reverse: tokens in, fiat out to a verified bank account. The [stablecoin off-ramp explainer](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp) covers the regulatory side in more depth.\n\n1. The sender requests a quote to convert a token amount into a fiat currency for a verified bank account.\n2. The provider returns a rate, a fee, and a quote ID with an expiry timestamp.\n3. The sender transfers the stablecoin to the provider's deposit address on the specified network.\n4. The provider confirms the on-chain deposit and locks the conversion at the quoted rate.\n5. The provider pays out fiat over a local rail such as ACH, wire, Pix, SPEI, or SEPA.\n6. The bank account is credited and the provider emits a settlement event.\n\nThe on-chain transfer in step 3 is final once confirmed. That is why account verification happens before any money moves.\n\n## What is the difference between an on-ramp and an off-ramp?\n\nThe two differ in direction, and everything else follows from that.\n\n| | On-ramp | Off-ramp |\n| --- | --- | --- |\n| Direction | Fiat into crypto | Crypto into fiat |\n| Input | Bank transfer, card, or instant payment | Stablecoin or crypto sent on-chain |\n| Output | Tokens in a wallet | Fiat in a bank account |\n| Common use case | Funding a wallet, collecting a payment in stablecoins, moving treasury on-chain | Paying a contractor in local currency, cashing out, settling a merchant |\n| Typical settlement time | Seconds on an instant rail, hours for a wire, up to 2 business days for ACH | Seconds over Pix or SPEI, same-day for ACH, hours for a wire |\n\nA payment that starts as a bank transfer and ends as a bank transfer, with a stablecoin in the middle, uses both. That pattern is sometimes called the stablecoin sandwich.\n\n## Why do fintech products need an on-ramp or off-ramp?\n\n**Remittances.** A remittance app collects dollars from a sender in the US, moves value on-chain, and needs an off-ramp to deliver pesos over SPEI or reais over Pix. Without the off-ramp, the recipient gets a token they cannot spend at the grocery store.\n\n**Payroll.** A company paying contractors in Argentina, Brazil, and Colombia funds one stablecoin balance and off-ramps each payment into the contractor's local bank account. The off-ramp replaces four banking relationships and four pre-funded accounts with one integration.\n\n**Marketplaces.** A marketplace collects fiat from buyers through an on-ramp, holds the balance as stablecoins, and pays sellers in dozens of countries through an off-ramp. The on-chain balance is what makes a single treasury serve every corridor.\n\n## What payment methods do on-ramps support?\n\nCoverage varies by provider and by country. These are the methods that matter most, with the tradeoff each one carries.\n\n- **Bank wire.** Handles large amounts with no practical ceiling, but costs $15 to $50 and takes hours to a day.\n- **ACH (US).** Cheap and familiar for US senders, but takes same-day to two business days and can be reversed for up to 60 days.\n- **SEPA and SEPA Instant (EU).** Low cost across the eurozone, and the Instant variant settles in seconds, though not every bank supports it.\n- **Pix (Brazil).** Settles in seconds, 24\u002F7, at near-zero cost, which makes it the best on-ramp rail in Latin America.\n- **SPEI (Mexico).** Same profile as Pix: instant, round the clock, cheap, and universal among Mexican banks.\n- **PSE (Colombia).** Bank-to-bank with broad coverage, but follows bank processing windows rather than settling instantly.\n- **Debit and credit cards.** Instant authorization and the widest reach for consumers, but 2 to 4 percent in fees and the highest chargeback risk.\n- **Apple Pay and Google Pay.** Same economics as cards with better conversion on mobile, and the same chargeback exposure.\n\nThe pattern is consistent: instant local rails are cheaper and safer than cards, and cards win only on reach and convenience.\n\n## What is the difference between an on-ramp provider and a liquidity provider?\n\nAn **on-ramp provider** is the service a fintech integrates to convert fiat into tokens for its users. It owns the customer-facing flow: payment collection, identity checks, quoting, and delivery.\n\nA **liquidity provider** is the counterparty that actually holds the fiat and the tokens and stands ready to exchange one for the other at a price. It is the source of the rate the on-ramp quotes.\n\nMany on-ramps are resellers that route to third-party liquidity, which adds a markup and a dependency. Providers that hold their own liquidity, BlindPay is one example, can return a live executable rate directly from the API instead of a cached one from someone else's book.\n\n## Who are on-ramps designed for?\n\n**Fintech developers.** A developer building a wallet, a payments app, or a treasury product needs users to fund accounts from a bank and withdraw to a bank. An on\u002Foff ramp API, such as the one described in [what is a stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api), replaces months of banking, licensing, and blockchain work with a few endpoints.\n\n**Neobanks.** A neobank offering dollar accounts to customers in a high-inflation country uses an on-ramp to turn local currency deposits into USDC and an off-ramp to let customers spend or withdraw. The customer sees a dollar balance; the ramps do the conversion underneath.\n\n**Marketplaces.** A marketplace or gig platform with sellers in many countries collects buyer payments in fiat and pays sellers in their local currency. BlindPay's [global payments](\u002Fglobal-payments) product is built for this shape: one balance in, local currency out over Pix, SPEI, PSE, ACH, and SEPA.\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":12984,"description":13284},"What is a crypto on-ramp and off-ramp?","resources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","Z-DgduY4HNW3mEjbcKMY3BfQxBLCWm2Q-vRFAj0jNzU",{"id":13306,"title":13307,"authors":6,"body":13308,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":10050,"description":13453,"extension":342,"faq":13454,"howto":6,"isBlog":359,"isChangelog":359,"meta":13466,"navigation":362,"path":13036,"pillar":359,"products":6,"rawbody":13467,"role":6,"seo":13468,"seoTitle":13456,"stem":13469,"thumbnail":6,"updated":10050,"__hash__":13470},"content\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp.md","What is a stablecoin off-ramp? How crypto becomes cash",{"type":8,"value":13309,"toc":13446},[13310,13313,13316,13320,13323,13342,13348,13352,13360,13372,13376,13381,13388,13392,13427,13431,13442],[11,13311,13312],{},"A stablecoin off-ramp converts stablecoins like USDC or USDT back into fiat currency and delivers it to a bank account. It is the exit door from crypto: dollars that moved on a blockchain become dollars, reais, or pesos sitting in an ordinary bank account, sent over the same rails a bank transfer would use.",[11,13314,13315],{},"Off-ramps matter because a stablecoin is only useful for payments if it eventually becomes spendable money. A business that receives USDC but has no way to convert it into local currency has a balance sheet entry, not a payment. The off-ramp is what closes the loop.",[18,13317,13319],{"id":13318},"how-does-a-stablecoin-off-ramp-work","How does a stablecoin off-ramp work?",[11,13321,13322],{},"Three things happen, usually inside seconds to minutes of each other:",[145,13324,13325,13331,13337],{},[148,13326,13327,13330],{},[119,13328,13329],{},"Receipt."," The off-ramp provider receives the stablecoin, either from the sender's wallet directly or from a payment flow where the sender never touched a wallet at all.",[148,13332,13333,13336],{},[119,13334,13335],{},"Conversion."," The provider converts the stablecoin to fiat at a quoted rate, sourcing liquidity from exchanges, market makers, or its own inventory.",[148,13338,13339,13341],{},[119,13340,7359],{}," The provider sends the converted fiat over a local bank rail: Pix in Brazil, SPEI in Mexico, ACH or wire in the US, and dozens of others depending on the destination.",[11,13343,13344,13345,13347],{},"Compliance runs underneath all three steps, not after them. A legitimate off-ramp screens the receiver against sanctions lists, verifies identity, and often checks the source of the stablecoin before releasing fiat. Skipping this is not a shortcut, it is the reason regulators built the licensing regimes described below. Most businesses never build this pipeline themselves; they call a ",[136,13346,480],{"href":479}," and get the whole flow behind one endpoint.",[18,13349,13351],{"id":13350},"who-regulates-stablecoin-off-ramps","Who regulates stablecoin off-ramps?",[11,13353,13354,13355,227],{},"In the US, FinCEN's 2013 guidance (FIN-2013-G001) is still the operating framework: \"an administrator or exchanger is an MSB under FinCEN's regulations, specifically, a money transmitter, unless a limitation to or exemption from the definition applies.\" An exchanger, in FinCEN's own words, is \"a person engaged as a business in the exchange of virtual currency for real currency, funds, or other virtual currency.\" That single sentence is why off-ramp providers need money transmitter licenses in most US states, not just a terms-of-service agreement. Full guidance is on ",[136,13356,13359],{"href":13357,"rel":13358},"https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-persons-administering",[414],"FinCEN's site",[11,13361,13362,13363,13365,13366,13369,13370,227],{},"Internationally, the same activity falls under the FATF's virtual asset service provider (VASP) category, which member countries implement through local licensing regimes. Brazil's PSAV framework is one concrete example, covered in our ",[136,13364,3240],{"href":3239},", and background on the VASP category itself is in ",[136,13367,13368],{"href":4069},"what is a VASP",". The regulatory direction is the same almost everywhere: converting stablecoins to fiat as a business requires a license, AML controls, and reporting, the same obligations a money transfer business carries. How these regimes compare across the EU, US, and Brazil is in our ",[136,13371,9979],{"href":1035},[18,13373,13375],{"id":13374},"whats-the-difference-between-an-on-ramp-and-an-off-ramp","What's the difference between an on-ramp and an off-ramp?",[11,13377,13378,13379,227],{},"An on-ramp moves fiat into stablecoins; an off-ramp moves stablecoins into fiat. A cross-border payout usually needs both, on opposite ends of the same transaction: a US business converts dollars to USDC (on-ramp), sends it in minutes, and a provider in Brazil converts it to reais and pays out over Pix (off-ramp). The sender and receiver each see a normal bank transaction; the stablecoin only exists for the seconds it takes to cross the border. That full flow, and the business cases behind it, is covered in our ",[136,13380,8748],{"href":618},[11,13382,13383,13384,13387],{},"Some providers only do one side. A crypto exchange might off-ramp for its own users but have no on-ramp product for businesses; a payments company might only care about the off-ramp because its customers already hold stablecoins. Knowing which side, or both, a provider actually covers is the first question to ask. The ",[136,13385,13386],{"href":13299},"on-ramp and off-ramp guide for fintech builders"," walks through both flows step by step.",[18,13389,13391],{"id":13390},"what-should-you-check-before-choosing-an-off-ramp","What should you check before choosing an off-ramp?",[171,13393,13394,13400,13406,13415,13421],{},[148,13395,13396,13399],{},[119,13397,13398],{},"Settlement speed and hours."," Some rails, like Pix, run 24\u002F7 in seconds. Others follow banking hours.",[148,13401,13402,13405],{},[119,13403,13404],{},"Rate transparency."," The quoted conversion rate should be visible before funds move, not disclosed after the fact.",[148,13407,13408,13411,13412,13414],{},[119,13409,13410],{},"Licensing."," Ask directly which money transmitter or VASP licenses the provider holds in the destination country, and check a published ",[136,13413,1046],{"href":815}," rather than taking a sales claim at face value.",[148,13416,13417,13420],{},[119,13418,13419],{},"Compliance depth."," Sanctions screening and KYC should run on every payout, not just above a threshold.",[148,13422,13423,13426],{},[119,13424,13425],{},"Coverage."," Which currencies and rails the provider actually reaches; a provider strong in one region may not off-ramp at all in another.",[18,13428,13430],{"id":13429},"how-does-blindpay-fit-in","How does BlindPay fit in?",[11,13432,13433,13435,13436,13438,13439,227],{},[136,13434,300],{"href":299}," runs both sides of this flow behind one API: convert fiat to USDC or USDT, send it, and off-ramp into local currency over Pix, SPEI, ACH, and wire across 100+ countries, with KYC, sanctions screening, and licensing handled on BlindPay's side. Rates are published, for example ",[136,13437,644],{"href":1757},", and more on how the pieces fit together is in the ",[136,13440,13441],{"href":12390},"resources hub",[11,13443,13444],{},[324,13445,326],{},{"title":328,"searchDepth":329,"depth":329,"links":13447},[13448,13449,13450,13451,13452],{"id":13318,"depth":329,"text":13319},{"id":13350,"depth":329,"text":13351},{"id":13374,"depth":329,"text":13375},{"id":13390,"depth":329,"text":13391},{"id":13429,"depth":329,"text":13430},"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.",[13455,13458,13461,13463],{"q":13456,"a":13457},"What is a stablecoin off-ramp?","A service that converts stablecoins like USDC or USDT into fiat currency and delivers it to a bank account. It is the step that turns on-chain dollars into money a business or person can actually spend through normal banking rails.",{"q":13459,"a":13460},"Is a stablecoin off-ramp regulated?","Yes, in most jurisdictions. In the US, FinCEN classifies businesses that exchange virtual currency for fiat as money transmitters, a category of money services business subject to AML registration and reporting. Other countries apply similar rules under their own VASP frameworks.",{"q":13375,"a":13462},"An on-ramp converts fiat into stablecoins, the entry point into crypto. An off-ramp converts stablecoins back into fiat, the exit point. A payment that starts as a bank transfer and ends as a bank transfer, with a stablecoin in the middle, uses both.",{"q":13464,"a":13465},"How long does off-ramping take?","The on-chain transfer settles in minutes regardless of amount. The off-ramp leg then depends on the local rail: Pix in Brazil settles in seconds, ACH in the US takes same-day to a few days, and a wire can take hours. The bottleneck is almost always the bank rail, not the blockchain.",{"author":361},"---\ntitle: \"What is a stablecoin off-ramp? How crypto becomes cash\"\nseoTitle: \"What is a stablecoin off-ramp?\"\ndescription: \"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.\"\ndate: \"2026-09-01\"\nauthor: \"BlindPay Team\"\nupdated: \"2026-09-01\"\ncategory: \"payments\"\nfaq:\n  - q: \"What is a stablecoin off-ramp?\"\n    a: \"A service that converts stablecoins like USDC or USDT into fiat currency and delivers it to a bank account. It is the step that turns on-chain dollars into money a business or person can actually spend through normal banking rails.\"\n  - q: \"Is a stablecoin off-ramp regulated?\"\n    a: \"Yes, in most jurisdictions. In the US, FinCEN classifies businesses that exchange virtual currency for fiat as money transmitters, a category of money services business subject to AML registration and reporting. Other countries apply similar rules under their own VASP frameworks.\"\n  - q: \"What's the difference between an on-ramp and an off-ramp?\"\n    a: \"An on-ramp converts fiat into stablecoins, the entry point into crypto. An off-ramp converts stablecoins back into fiat, the exit point. A payment that starts as a bank transfer and ends as a bank transfer, with a stablecoin in the middle, uses both.\"\n  - q: \"How long does off-ramping take?\"\n    a: \"The on-chain transfer settles in minutes regardless of amount. The off-ramp leg then depends on the local rail: Pix in Brazil settles in seconds, ACH in the US takes same-day to a few days, and a wire can take hours. The bottleneck is almost always the bank rail, not the blockchain.\"\n---\n\nA stablecoin off-ramp converts stablecoins like USDC or USDT back into fiat currency and delivers it to a bank account. It is the exit door from crypto: dollars that moved on a blockchain become dollars, reais, or pesos sitting in an ordinary bank account, sent over the same rails a bank transfer would use.\n\nOff-ramps matter because a stablecoin is only useful for payments if it eventually becomes spendable money. A business that receives USDC but has no way to convert it into local currency has a balance sheet entry, not a payment. The off-ramp is what closes the loop.\n\n## How does a stablecoin off-ramp work?\n\nThree things happen, usually inside seconds to minutes of each other:\n\n1. **Receipt.** The off-ramp provider receives the stablecoin, either from the sender's wallet directly or from a payment flow where the sender never touched a wallet at all.\n2. **Conversion.** The provider converts the stablecoin to fiat at a quoted rate, sourcing liquidity from exchanges, market makers, or its own inventory.\n3. **Payout.** The provider sends the converted fiat over a local bank rail: Pix in Brazil, SPEI in Mexico, ACH or wire in the US, and dozens of others depending on the destination.\n\nCompliance runs underneath all three steps, not after them. A legitimate off-ramp screens the receiver against sanctions lists, verifies identity, and often checks the source of the stablecoin before releasing fiat. Skipping this is not a shortcut, it is the reason regulators built the licensing regimes described below. Most businesses never build this pipeline themselves; they call a [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) and get the whole flow behind one endpoint.\n\n## Who regulates stablecoin off-ramps?\n\nIn the US, FinCEN's 2013 guidance (FIN-2013-G001) is still the operating framework: \"an administrator or exchanger is an MSB under FinCEN's regulations, specifically, a money transmitter, unless a limitation to or exemption from the definition applies.\" An exchanger, in FinCEN's own words, is \"a person engaged as a business in the exchange of virtual currency for real currency, funds, or other virtual currency.\" That single sentence is why off-ramp providers need money transmitter licenses in most US states, not just a terms-of-service agreement. Full guidance is on [FinCEN's site](https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-persons-administering).\n\nInternationally, the same activity falls under the FATF's virtual asset service provider (VASP) category, which member countries implement through local licensing regimes. Brazil's PSAV framework is one concrete example, covered in our [PSAV explainer](\u002Fresources\u002Fmore\u002Fpsav-brazil-explained), and background on the VASP category itself is in [what is a VASP](\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp). The regulatory direction is the same almost everywhere: converting stablecoins to fiat as a business requires a license, AML controls, and reporting, the same obligations a money transfer business carries. How these regimes compare across the EU, US, and Brazil is in our [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026).\n\n## What's the difference between an on-ramp and an off-ramp?\n\nAn on-ramp moves fiat into stablecoins; an off-ramp moves stablecoins into fiat. A cross-border payout usually needs both, on opposite ends of the same transaction: a US business converts dollars to USDC (on-ramp), sends it in minutes, and a provider in Brazil converts it to reais and pays out over Pix (off-ramp). The sender and receiver each see a normal bank transaction; the stablecoin only exists for the seconds it takes to cross the border. That full flow, and the business cases behind it, is covered in our [stablecoin payments guide](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\nSome providers only do one side. A crypto exchange might off-ramp for its own users but have no on-ramp product for businesses; a payments company might only care about the off-ramp because its customers already hold stablecoins. Knowing which side, or both, a provider actually covers is the first question to ask. The [on-ramp and off-ramp guide for fintech builders](\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp) walks through both flows step by step.\n\n## What should you check before choosing an off-ramp?\n\n- **Settlement speed and hours.** Some rails, like Pix, run 24\u002F7 in seconds. Others follow banking hours.\n- **Rate transparency.** The quoted conversion rate should be visible before funds move, not disclosed after the fact.\n- **Licensing.** Ask directly which money transmitter or VASP licenses the provider holds in the destination country, and check a published [licenses page](\u002Flicenses) rather than taking a sales claim at face value.\n- **Compliance depth.** Sanctions screening and KYC should run on every payout, not just above a threshold.\n- **Coverage.** Which currencies and rails the provider actually reaches; a provider strong in one region may not off-ramp at all in another.\n\n## How does BlindPay fit in?\n\n[BlindPay](\u002Fglobal-payments) runs both sides of this flow behind one API: convert fiat to USDC or USDT, send it, and off-ramp into local currency over Pix, SPEI, ACH, and wire across 100+ countries, with KYC, sanctions screening, and licensing handled on BlindPay's side. Rates are published, for example [USDC to BRL](\u002Fusdc-to-brl), and more on how the pieces fit together is in the [resources hub](\u002Fresources\u002Fmore).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":13307,"description":13453},"resources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","Xp5jvKs0yU_oB9uFtULQiIC0RWDmVOiqbsONZ2givE0",{"id":13472,"title":13473,"authors":6,"body":13474,"categories":6,"category":339,"categoryType":6,"compare":6,"contributors":6,"date":4620,"description":13749,"extension":342,"faq":13750,"howto":6,"isBlog":359,"isChangelog":359,"meta":13766,"navigation":362,"path":4599,"pillar":359,"products":6,"rawbody":13767,"role":6,"seo":13768,"seoTitle":13769,"stem":13770,"thumbnail":6,"updated":6,"__hash__":13771},"content\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration.md","What is payment orchestration? The routing layer, explained",{"type":8,"value":13475,"toc":13737},[13476,13479,13482,13485,13489,13492,13495,13498,13502,13509,13519,13522,13526,13529,13532,13546,13549,13553,13556,13559,13562,13566,13572,13578,13583,13587,13590,13593,13598,13602,13605,13608,13611,13616,13629,13639,13642,13698,13704,13708,13711,13714,13717,13719,13722,13733],[11,13477,13478],{},"Payment orchestration is the routing and operations layer that sits between your application and the payment processors, banks, and rails you use. Instead of integrating one processor and living inside its coverage map, you integrate one orchestration API, and it decides per transaction which rail to use, how to execute FX, which compliance checks to run, and how to reconcile settlement.",[11,13480,13481],{},"For cross-border money specifically, that means picking between SWIFT, local rails like Pix, SPEI, and SEPA, and stablecoin settlement, based on cost, speed, and what each corridor actually allows.",[11,13483,13484],{},"That is a different problem from domestic card orchestration. Card orchestrators toggle between acquirers like Stripe and Adyen to lift authorization rates on the same rail in the same country. Cross-border orchestration routes across rails that do not share a currency, a settlement time, or a regulator. Harder problem, bigger payoff.",[18,13486,13488],{"id":13487},"what-problem-does-payment-orchestration-actually-solve","What problem does payment orchestration actually solve?",[11,13490,13491],{},"Every payments team hits the same wall in the same order.",[11,13493,13494],{},"You launch with one processor. It works. Then you add a second country and the processor does not cover it, so you integrate a second provider with a different API, different error codes, different webhook shapes, and different reconciliation files. Then a rail goes down on a Friday and you have no fallback. Then finance asks why the same payout cost 0.4 percent in one corridor and 3 percent in another, and nobody can answer because the FX spread is buried inside each provider's rate.",[11,13496,13497],{},"Orchestration is the answer to that sprawl. One API shape, one set of statuses, one reconciliation model, and routing logic you can change without shipping code.",[18,13499,13501],{"id":13500},"layer-1-api-ingestion","Layer 1: API ingestion",[11,13503,13504,13505,13508],{},"The ingestion layer is the single interface your application talks to. One ",[204,13506,13507],{},"create payout"," call with a receiver, an amount, and a currency, regardless of whether the money will end up moving over Pix, SPEI, ACH, or SWIFT.",[11,13510,13511,13512,13515,13516,13518],{},"The work here is normalization. Provider A calls a failed payout ",[204,13513,13514],{},"DECLINED",", provider B calls it ",[204,13517,5080],{},", and provider C returns HTTP 200 with an error object. The ingestion layer collapses all of that into one status vocabulary and one webhook contract, with idempotency keys so a retry never sends money twice.",[11,13520,13521],{},"Example: your code posts the same payout object for a contractor in São Paulo and a supplier in Monterrey. Nothing in your codebase knows that one settles over Pix and the other over SPEI.",[18,13523,13525],{"id":13524},"layer-2-routing-engine","Layer 2: routing engine",[11,13527,13528],{},"The routing engine decides which path a given transaction takes. Inputs are the corridor, the amount, the currency pair, the speed you asked for, provider health, and cost.",[11,13530,13531],{},"A realistic rule set looks like this:",[171,13533,13534,13537,13540,13543],{},[148,13535,13536],{},"USD to BRL under $50,000: settle in stablecoins, pay out over Pix.",[148,13538,13539],{},"USD to BRL over $50,000 where the receiver requires an MT103: send a SWIFT wire.",[148,13541,13542],{},"Any corridor where the primary provider is failing health checks: fail over to the secondary.",[148,13544,13545],{},"Weekend payouts into Brazil or Mexico: prefer rails that run 24\u002F7, because SWIFT does not.",[11,13547,13548],{},"The routing engine is what people mean when they say orchestration is more than a router. It is a router with a cost model and a liveness check attached.",[18,13550,13552],{"id":13551},"layer-3-fx-execution","Layer 3: FX execution",[11,13554,13555],{},"Cross-border payments are FX trades with a delivery instruction stapled to them. The FX layer sources a rate, quotes it to you, holds it for a defined window, and executes the conversion when you commit.",[11,13557,13558],{},"Two things matter. The first is whether you see the rate before you commit funds, or find out after the receiver tells you the amount was short. The second is the spread against mid-market. A provider quoting \"no fees\" with a 3 percent spread is more expensive than one charging a flat $2 on a sub-percent spread, and on a $100,000 payment it is not close.",[11,13560,13561],{},"Example: a $100,000 USD to MXN payout at a 2.5 percent spread costs $2,500 in FX alone. At 0.5 percent it costs $500. Same payment, same day, same receiver.",[18,13563,13565],{"id":13564},"layer-4-compliance-screening","Layer 4: compliance screening",[11,13567,13568,13569,13571],{},"Compliance is a routing input, not a separate workflow. The orchestration layer runs KYC on individual receivers and ",[136,13570,3301],{"href":3211}," on business receivers, screens both against sanctions lists, monitors transactions for patterns, and exchanges travel rule data where the corridor requires it.",[11,13573,13574,13575,13577],{},"Doing this inside the routing path has a specific operational benefit: a receiver who fails screening gets blocked before any money moves, instead of after a correspondent bank freezes a wire that is already in flight. Fast, loud failure beats slow, quiet failure. Our note on ",[136,13576,4354],{"href":4353}," covers what runs in-line versus after the fact.",[11,13579,13580,13581,11448],{},"Rules also differ per corridor. Brazil licenses virtual asset providers under Central Bank Resolutions 519 through 521. The EU has MiCA. The US has the GENIUS Act. The ",[136,13582,1036],{"href":1035},[18,13584,13586],{"id":13585},"layer-5-settlement-and-reconciliation","Layer 5: settlement and reconciliation",[11,13588,13589],{},"The last layer answers the question finance actually asks: did the money land, how much of it, and against which invoice.",[11,13591,13592],{},"That means per-transaction status with webhooks on every state change, a settlement report per rail, and a reconciliation model that matches what you sent against what the receiver got, net of every fee and the FX spread. Without this layer you have a payment system that works and books that do not close.",[11,13594,13595,13596,227],{},"Settlement finality also varies by rail, and treating them as equivalent is how teams get burned. An on-chain transfer is final once confirmed. A Pix transfer is final in seconds. An ACH debit can be returned for days. We break the differences down in the ",[136,13597,4041],{"href":1243},[18,13599,13601],{"id":13600},"how-does-stablecoin-settlement-fit-as-a-rail","How does stablecoin settlement fit as a rail?",[11,13603,13604],{},"The classic orchestration picture has two settlement options for cross-border money: SWIFT for the long haul, local ACH-style rails for the last mile. Stablecoin settlement adds a third, and it changes the middle of the flow rather than the ends.",[11,13606,13607],{},"A USD to BRL payout over a stablecoin bridge looks like this: dollars in, converted to USDC, USDC moves on-chain in seconds, converted to reais at a quoted rate, delivered over Pix to the recipient's bank account. The recipient never sees a wallet or a token. They see reais in their bank, usually within minutes, at 11pm on a Saturday if that is when you sent it.",[11,13609,13610],{},"Two operational properties matter more than the speed.",[11,13612,13613,13615],{},[119,13614,2257],{}," The traditional way to pay fast in a local market is to park working capital in a local bank account and pay out of it. That capital is dead. Stablecoin settlement moves value at payout time, so the float stays in your treasury.",[11,13617,13618,13621,13622,13624,13625,13628],{},[119,13619,13620],{},"Price certainty at execution."," A live quote tells you the exact rate and fee before you commit. ",[136,13623,300],{"href":299}," works this way: quote first, commit second, with the spread and the flat fee itemized separately rather than blended into one rate. The ",[136,13626,13627],{"href":4440},"on\u002Foff-ramp liquidity guide"," explains why that ordering matters at scale.",[11,13630,13631,13632,1313,13635,13638],{},"Stablecoins do not replace SWIFT, and any vendor telling you otherwise is selling. For a $50 million treasury transfer between two G10 banks, use the wire. For mid-sized payouts into Latin America, the stablecoin path is usually faster and cheaper by a wide margin. The full comparison lives in ",[136,13633,13634],{"href":1210},"stablecoins vs SWIFT",[136,13636,13637],{"href":289},"how stablecoins fit into orchestration for cross-border payouts"," goes deeper on the mechanics.",[18,13640,8077],{"id":13641},"payment-orchestration-vs-payment-gateway",[39,13643,13644,13654],{},[42,13645,13646],{},[45,13647,13648,13650,13652],{},[48,13649],{},[48,13651,7815],{},[48,13653,7818],{},[61,13655,13656,13667,13678,13688],{},[45,13657,13658,13661,13664],{},[66,13659,13660],{},"Scope",[66,13662,13663],{},"One processor, one rail",[66,13665,13666],{},"Many providers and rails behind one API",[45,13668,13669,13672,13675],{},[66,13670,13671],{},"Routing logic",[66,13673,13674],{},"None, the path is fixed",[66,13676,13677],{},"Per-transaction, by cost, speed, and provider health",[45,13679,13680,13682,13685],{},[66,13681,7847],{},[66,13683,13684],{},"The processor's rate, usually blended",[66,13686,13687],{},"Quoted per transaction, spread itemized",[45,13689,13690,13692,13695],{},[66,13691,11439],{},[66,13693,13694],{},"Handled by the processor, opaque to you",[66,13696,13697],{},"Screening runs in the routing path, per corridor",[11,13699,13700,13701,227],{},"If you want the longer version of this table with a decision framework, read ",[136,13702,13703],{"href":4487},"payment orchestration vs payment gateway",[18,13705,13707],{"id":13706},"do-you-need-orchestration-yet","Do you need orchestration yet?",[11,13709,13710],{},"Three honest triggers.",[11,13712,13713],{},"You operate in two or more countries and are maintaining two or more provider integrations. You have had a rail go down with no fallback. You cannot state, per corridor, what a payout costs all-in.",[11,13715,13716],{},"Any one of those and orchestration pays for itself. None of them and a single gateway is the right call, and adding a routing layer is complexity you do not need yet.",[18,13718,312],{"id":311},[11,13720,13721],{},"Take last month's cross-border payouts. For each one, write down the rail, the total cost including the FX spread, and the time from API call to funds landing. If the answer varies by more than a point between corridors, or you cannot fill in a column, that gap is what orchestration closes.",[11,13723,13724,13725,4596,13727,1341,13730,227],{},"Then price the same payouts through a live quote. ",[136,13726,4595],{"href":1335},[136,13728,13729],{"href":4636},"how to evaluate an orchestration platform",[136,13731,1331],{"href":648,"rel":13732},[414],[11,13734,13735],{},[324,13736,326],{},{"title":328,"searchDepth":329,"depth":329,"links":13738},[13739,13740,13741,13742,13743,13744,13745,13746,13747,13748],{"id":13487,"depth":329,"text":13488},{"id":13500,"depth":329,"text":13501},{"id":13524,"depth":329,"text":13525},{"id":13551,"depth":329,"text":13552},{"id":13564,"depth":329,"text":13565},{"id":13585,"depth":329,"text":13586},{"id":13600,"depth":329,"text":13601},{"id":13641,"depth":329,"text":8077},{"id":13706,"depth":329,"text":13707},{"id":311,"depth":329,"text":312},"Payment orchestration is the routing layer between your app and every processor, bank, and rail. The five layers and how stablecoins fit.",[13751,13754,13757,13760,13763],{"q":13752,"a":13753},"Is payment orchestration the same as a payment gateway?","No. A gateway connects you to one processor and passes transactions through it. An orchestration platform connects to many providers and rails and decides per transaction which one to use, how to handle FX, and which compliance checks to run.",{"q":13755,"a":13756},"Do I need payment orchestration if I only operate in one country?","Usually not. One country, one currency, one rail is a gateway problem. Orchestration starts paying for itself when you have two or more countries, two or more rails, or a need to fail over when a provider goes down.",{"q":13758,"a":13759},"How does stablecoin settlement change payment orchestration?","It adds a rail that settles in minutes, 24\u002F7, without pre-funding local accounts. The orchestration layer can route a payout over a stablecoin bridge into a local rail like Pix or SPEI instead of sending a SWIFT wire and waiting days for it to land.",{"q":13761,"a":13762},"What does a payment orchestration platform cost?","Pricing is usually a flat fee per transaction, a percentage, or both, plus the FX spread on any currency conversion. The spread is where most of the real cost sits, so compare the total amount the receiver gets, not the advertised fee.",{"q":13764,"a":13765},"Does orchestration replace my existing processors?","No. It sits in front of them. You keep the provider relationships that work and the orchestration layer normalizes them behind one API, which also makes swapping one out a config change instead of a rebuild.",{"author":361},"---\ntitle: \"What is payment orchestration? The routing layer, explained\"\nseoTitle: \"What is payment orchestration?\"\ndescription: \"Payment orchestration is the routing layer between your app and every processor, bank, and rail. The five layers and how stablecoins fit.\"\ndate: \"2026-09-16\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is payment orchestration the same as a payment gateway?\"\n    a: \"No. A gateway connects you to one processor and passes transactions through it. An orchestration platform connects to many providers and rails and decides per transaction which one to use, how to handle FX, and which compliance checks to run.\"\n  - q: \"Do I need payment orchestration if I only operate in one country?\"\n    a: \"Usually not. One country, one currency, one rail is a gateway problem. Orchestration starts paying for itself when you have two or more countries, two or more rails, or a need to fail over when a provider goes down.\"\n  - q: \"How does stablecoin settlement change payment orchestration?\"\n    a: \"It adds a rail that settles in minutes, 24\u002F7, without pre-funding local accounts. The orchestration layer can route a payout over a stablecoin bridge into a local rail like Pix or SPEI instead of sending a SWIFT wire and waiting days for it to land.\"\n  - q: \"What does a payment orchestration platform cost?\"\n    a: \"Pricing is usually a flat fee per transaction, a percentage, or both, plus the FX spread on any currency conversion. The spread is where most of the real cost sits, so compare the total amount the receiver gets, not the advertised fee.\"\n  - q: \"Does orchestration replace my existing processors?\"\n    a: \"No. It sits in front of them. You keep the provider relationships that work and the orchestration layer normalizes them behind one API, which also makes swapping one out a config change instead of a rebuild.\"\n---\n\nPayment orchestration is the routing and operations layer that sits between your application and the payment processors, banks, and rails you use. Instead of integrating one processor and living inside its coverage map, you integrate one orchestration API, and it decides per transaction which rail to use, how to execute FX, which compliance checks to run, and how to reconcile settlement.\n\nFor cross-border money specifically, that means picking between SWIFT, local rails like Pix, SPEI, and SEPA, and stablecoin settlement, based on cost, speed, and what each corridor actually allows.\n\nThat is a different problem from domestic card orchestration. Card orchestrators toggle between acquirers like Stripe and Adyen to lift authorization rates on the same rail in the same country. Cross-border orchestration routes across rails that do not share a currency, a settlement time, or a regulator. Harder problem, bigger payoff.\n\n## What problem does payment orchestration actually solve?\n\nEvery payments team hits the same wall in the same order.\n\nYou launch with one processor. It works. Then you add a second country and the processor does not cover it, so you integrate a second provider with a different API, different error codes, different webhook shapes, and different reconciliation files. Then a rail goes down on a Friday and you have no fallback. Then finance asks why the same payout cost 0.4 percent in one corridor and 3 percent in another, and nobody can answer because the FX spread is buried inside each provider's rate.\n\nOrchestration is the answer to that sprawl. One API shape, one set of statuses, one reconciliation model, and routing logic you can change without shipping code.\n\n## Layer 1: API ingestion\n\nThe ingestion layer is the single interface your application talks to. One `create payout` call with a receiver, an amount, and a currency, regardless of whether the money will end up moving over Pix, SPEI, ACH, or SWIFT.\n\nThe work here is normalization. Provider A calls a failed payout `DECLINED`, provider B calls it `rejected`, and provider C returns HTTP 200 with an error object. The ingestion layer collapses all of that into one status vocabulary and one webhook contract, with idempotency keys so a retry never sends money twice.\n\nExample: your code posts the same payout object for a contractor in São Paulo and a supplier in Monterrey. Nothing in your codebase knows that one settles over Pix and the other over SPEI.\n\n## Layer 2: routing engine\n\nThe routing engine decides which path a given transaction takes. Inputs are the corridor, the amount, the currency pair, the speed you asked for, provider health, and cost.\n\nA realistic rule set looks like this:\n\n- USD to BRL under $50,000: settle in stablecoins, pay out over Pix.\n- USD to BRL over $50,000 where the receiver requires an MT103: send a SWIFT wire.\n- Any corridor where the primary provider is failing health checks: fail over to the secondary.\n- Weekend payouts into Brazil or Mexico: prefer rails that run 24\u002F7, because SWIFT does not.\n\nThe routing engine is what people mean when they say orchestration is more than a router. It is a router with a cost model and a liveness check attached.\n\n## Layer 3: FX execution\n\nCross-border payments are FX trades with a delivery instruction stapled to them. The FX layer sources a rate, quotes it to you, holds it for a defined window, and executes the conversion when you commit.\n\nTwo things matter. The first is whether you see the rate before you commit funds, or find out after the receiver tells you the amount was short. The second is the spread against mid-market. A provider quoting \"no fees\" with a 3 percent spread is more expensive than one charging a flat $2 on a sub-percent spread, and on a $100,000 payment it is not close.\n\nExample: a $100,000 USD to MXN payout at a 2.5 percent spread costs $2,500 in FX alone. At 0.5 percent it costs $500. Same payment, same day, same receiver.\n\n## Layer 4: compliance screening\n\nCompliance is a routing input, not a separate workflow. The orchestration layer runs KYC on individual receivers and [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) on business receivers, screens both against sanctions lists, monitors transactions for patterns, and exchanges travel rule data where the corridor requires it.\n\nDoing this inside the routing path has a specific operational benefit: a receiver who fails screening gets blocked before any money moves, instead of after a correspondent bank freezes a wire that is already in flight. Fast, loud failure beats slow, quiet failure. Our note on [real-time transaction monitoring](\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments) covers what runs in-line versus after the fact.\n\nRules also differ per corridor. Brazil licenses virtual asset providers under Central Bank Resolutions 519 through 521. The EU has MiCA. The US has the GENIUS Act. The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) keeps score.\n\n## Layer 5: settlement and reconciliation\n\nThe last layer answers the question finance actually asks: did the money land, how much of it, and against which invoice.\n\nThat means per-transaction status with webhooks on every state change, a settlement report per rail, and a reconciliation model that matches what you sent against what the receiver got, net of every fee and the FX spread. Without this layer you have a payment system that works and books that do not close.\n\nSettlement finality also varies by rail, and treating them as equivalent is how teams get burned. An on-chain transfer is final once confirmed. A Pix transfer is final in seconds. An ACH debit can be returned for days. We break the differences down in the [settlement finality guide](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality).\n\n## How does stablecoin settlement fit as a rail?\n\nThe classic orchestration picture has two settlement options for cross-border money: SWIFT for the long haul, local ACH-style rails for the last mile. Stablecoin settlement adds a third, and it changes the middle of the flow rather than the ends.\n\nA USD to BRL payout over a stablecoin bridge looks like this: dollars in, converted to USDC, USDC moves on-chain in seconds, converted to reais at a quoted rate, delivered over Pix to the recipient's bank account. The recipient never sees a wallet or a token. They see reais in their bank, usually within minutes, at 11pm on a Saturday if that is when you sent it.\n\nTwo operational properties matter more than the speed.\n\n**No pre-funding.** The traditional way to pay fast in a local market is to park working capital in a local bank account and pay out of it. That capital is dead. Stablecoin settlement moves value at payout time, so the float stays in your treasury.\n\n**Price certainty at execution.** A live quote tells you the exact rate and fee before you commit. [BlindPay](\u002Fglobal-payments) works this way: quote first, commit second, with the spread and the flat fee itemized separately rather than blended into one rate. The [on\u002Foff-ramp liquidity guide](\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes) explains why that ordering matters at scale.\n\nStablecoins do not replace SWIFT, and any vendor telling you otherwise is selling. For a $50 million treasury transfer between two G10 banks, use the wire. For mid-sized payouts into Latin America, the stablecoin path is usually faster and cheaper by a wide margin. The full comparison lives in [stablecoins vs SWIFT](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments), and [how stablecoins fit into orchestration for cross-border payouts](\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts) goes deeper on the mechanics.\n\n## Payment orchestration vs payment gateway\n\n| | Payment gateway | Payment orchestration |\n| --- | --- | --- |\n| Scope | One processor, one rail | Many providers and rails behind one API |\n| Routing logic | None, the path is fixed | Per-transaction, by cost, speed, and provider health |\n| FX handling | The processor's rate, usually blended | Quoted per transaction, spread itemized |\n| Compliance | Handled by the processor, opaque to you | Screening runs in the routing path, per corridor |\n\nIf you want the longer version of this table with a decision framework, read [payment orchestration vs payment gateway](\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway).\n\n## Do you need orchestration yet?\n\nThree honest triggers.\n\nYou operate in two or more countries and are maintaining two or more provider integrations. You have had a rail go down with no fallback. You cannot state, per corridor, what a payout costs all-in.\n\nAny one of those and orchestration pays for itself. None of them and a single gateway is the right call, and adding a routing layer is complexity you do not need yet.\n\n## What to do next\n\nTake last month's cross-border payouts. For each one, write down the rail, the total cost including the FX spread, and the time from API call to funds landing. If the answer varies by more than a point between corridors, or you cannot fill in a column, that gap is what orchestration closes.\n\nThen price the same payouts through a live quote. [See coverage by country](\u002Fcoverage), read [how to evaluate an orchestration platform](\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform), or [start in the sandbox](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":13473,"description":13749},"What is payment orchestration?","resources\u002Fmore\u002Fwhat-is-payment-orchestration","1BZtZVDWxMXuTK6bUz3SUPtcOM7Bdoue4vQ9mWVI6UI",1790103393150]