[{"data":1,"prerenderedAt":10123},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-safe":3,"resources-category-are-stablecoin-payments-safe":563},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":534,"description":535,"extension":536,"faq":537,"howto":6,"isBlog":553,"isChangelog":553,"meta":554,"navigation":556,"path":557,"pillar":553,"products":6,"rawbody":558,"role":6,"seo":559,"seoTitle":560,"stem":561,"thumbnail":6,"updated":534,"__hash__":562},"content\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-safe.md","Are stablecoin payments safe? The risks businesses should check, and how to reduce them",null,{"type":8,"value":9,"toc":518},"minimark",[10,14,17,22,122,125,129,140,143,166,179,182,186,195,203,207,210,213,233,246,250,253,261,265,268,281,285,288,309,317,321,330,338,342,345,434,437,441,467,474,478,481,499,511],[11,12,13],"p",{},"Stablecoin payments are safe when four layers hold: a fully reserved stablecoin, a reliable network, a licensed provider with clear custody, and your own controls on addresses and networks. The technology rarely fails on its own. Losses usually come from a weak issuer, a provider that holds your money without saying so, or a human who pasted the wrong address.",[11,15,16],{},"So the useful question isn't \"are stablecoins safe?\" It's \"which of the seven risks below have I covered?\"",[18,19,21],"h2",{"id":20},"what-are-the-risks-of-stablecoin-payments","What are the risks of stablecoin payments?",[23,24,25,41],"table",{},[26,27,28],"thead",{},[29,30,31,35,38],"tr",{},[32,33,34],"th",{},"Risk",[32,36,37],{},"What can go wrong",[32,39,40],{},"How to reduce it",[42,43,44,56,67,78,89,100,111],"tbody",{},[29,45,46,50,53],{},[47,48,49],"td",{},"Issuer and reserves",[47,51,52],{},"The stablecoin trades below $1 or redemptions slow down",[47,54,55],{},"Use fully reserved, attested stablecoins from regulated issuers",[29,57,58,61,64],{},[47,59,60],{},"Network",[47,62,63],{},"The blockchain halts or fees spike",[47,65,66],{},"Support more than one network per stablecoin",[29,68,69,72,75],{},[47,70,71],{},"Irreversible errors",[47,73,74],{},"Funds go to the wrong address or network",[47,76,77],{},"Allowlist addresses, test with small amounts",[29,79,80,83,86],{},[47,81,82],{},"Custody and provider",[47,84,85],{},"The provider holding your funds fails or freezes",[47,87,88],{},"Know who holds the funds at every step",[29,90,91,94,97],{},[47,92,93],{},"Conversion to cash",[47,95,96],{},"You can't off-ramp when you need to",[47,98,99],{},"Check corridors, limits, and liquidity before you depend on them",[29,101,102,105,108],{},[47,103,104],{},"Fraud",[47,106,107],{},"Address poisoning, malicious approvals, reversed bank deposits",[47,109,110],{},"Verify addresses out of band, approve exact amounts, hold risky deposits",[29,112,113,116,119],{},[47,114,115],{},"Compliance",[47,117,118],{},"Funds tied to a sanctioned party get frozen",[47,120,121],{},"Screen counterparties and wallet addresses, not just customers",[11,123,124],{},"Each one is covered below.",[18,126,128],{"id":127},"can-a-stablecoin-lose-its-peg","Can a stablecoin lose its peg?",[11,130,131,132,139],{},"Yes, and a major one already has. On March 10, 2023, Circle disclosed that $3.3 billion of the reserves backing USDC were held at Silicon Valley Bank, which had just failed. USDC ",[133,134,138],"a",{"href":135,"rel":136},"https:\u002F\u002Fwww.axios.com\u002F2023\u002F03\u002F11\u002Fcircle-usdc-peg-svb",[137],"nofollow","traded below 90 cents"," the next day. It returned to about $1 within days, once US authorities said all of the bank's deposits would be protected.",[11,141,142],{},"The lesson isn't that USDC is unsafe. It's that a stablecoin is only as good as its reserves and where they sit. Before you hold a balance, check:",[144,145,146,154,160],"ul",{},[147,148,149,153],"li",{},[150,151,152],"strong",{},"What backs it."," Cash and short-term government debt, or something riskier.",[147,155,156,159],{},[150,157,158],{},"How often reserves are reported."," Monthly reports with an independent accountant's attestation are the norm for the large regulated issuers.",[147,161,162,165],{},[150,163,164],{},"Who can redeem, and how fast."," Redemption at par is what holds the peg.",[11,167,168,169,173,174,178],{},"Regulation is tightening this. In the EU, ",[133,170,172],{"href":171},"\u002Fresources\u002Fmore\u002Fmica-stablecoin-rules-explained","MiCA"," already requires e-money tokens to be fully reserved and redeemable at par. In the US, the GENIUS Act requires 1:1 reserves in cash and short-term Treasuries, with monthly disclosure, once its rules take effect. ",[133,175,177],{"href":176},"\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments","USDC vs USDT for payments"," compares how the two largest issuers report.",[11,180,181],{},"Stablecoins are not bank deposits and are not FDIC insured. Treat a stablecoin balance like a claim on the issuer's reserves, because that's what it is.",[18,183,185],{"id":184},"what-happens-if-a-blockchain-network-goes-down","What happens if a blockchain network goes down?",[11,187,188,189,194],{},"Payments on that network stop until it recovers. Solana, for example, ",[133,190,193],{"href":191,"rel":192},"https:\u002F\u002Fcointelegraph.com\u002Fnews\u002Fsolana-network-outage-block-production-halted",[137],"halted block production for about five hours"," on February 6, 2024. Funds weren't lost, but nothing moved.",[11,196,197,198,202],{},"Outages like that are rare on the major networks, and fee spikes are more common. Both are manageable if you don't depend on a single chain. A provider that settles the same stablecoin on several networks lets you route around a bad day. ",[133,199,201],{"href":200},"\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment","What happens on-chain in a stablecoin payment"," explains what the network does during a transfer.",[18,204,206],{"id":205},"can-stablecoin-payments-be-reversed-or-recovered","Can stablecoin payments be reversed or recovered?",[11,208,209],{},"No, not by the network. A confirmed transfer is final. There's no chargeback and no recall message. That finality is useful, since it proves exactly who held the funds and when, but it means mistakes stick.",[11,211,212],{},"The common ones:",[144,214,215,221,227],{},[147,216,217,220],{},[150,218,219],{},"Wrong address."," A typo, or an address copied from the wrong place.",[147,222,223,226],{},[150,224,225],{},"Wrong network."," The right address on a chain the receiver doesn't monitor.",[147,228,229,232],{},[150,230,231],{},"Unsupported token."," A stablecoin the receiving provider can't accept on that network.",[11,234,235,236,240,241,245],{},"Controls that work: an allowlist of saved recipient addresses, a small test transfer before any large first payment, and a provider that rejects unsupported token and network pairs before anything moves. ",[133,237,239],{"href":238},"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible","Are stablecoin payments reversible"," goes deeper on finality, and ",[133,242,244],{"href":243},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes","common stablecoin payout mistakes"," lists the errors to block in your code.",[18,247,249],{"id":248},"what-happens-if-the-provider-fails","What happens if the provider fails?",[11,251,252],{},"That depends on custody. If a provider holds your stablecoins or fiat between steps, you're exposed to its solvency, its banks, and its operations. If the flow is non-custodial, the funds stay in a wallet you control until the payment executes.",[11,254,255,256,260],{},"Neither model is automatically right. Custodial products can be convenient. What matters is knowing which one you're using, product by product. A provider can be non-custodial for payouts and custodial for a hosted wallet. ",[133,257,259],{"href":258},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps","Custodial vs non-custodial off-ramps"," walks through what happens in each model when a provider becomes insolvent or loses its bank.",[18,262,264],{"id":263},"can-you-always-convert-stablecoins-back-to-cash","Can you always convert stablecoins back to cash?",[11,266,267],{},"Not everywhere, and not in any amount. Converting stablecoins to local currency needs a licensed off-ramp in the destination country, a local payout rail, and enough liquidity for your volume. Per-transaction and monthly limits apply by verification tier.",[11,269,270,271,275,276,280],{},"The risk shows up when a business holds stablecoins assuming it can exit anytime, then hits a corridor that isn't supported or a limit it didn't plan for. Check the corridors you need, the limits that apply to you, and how liquidity holds up at your largest payment size. ",[133,272,274],{"href":273},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-limits","Stablecoin off-ramp limits"," and ",[133,277,279],{"href":278},"\u002Fresources\u002Fmore\u002Fliquidity-risk-global-payouts","liquidity risk in global payouts"," cover both.",[18,282,284],{"id":283},"what-fraud-should-businesses-watch-for","What fraud should businesses watch for?",[11,286,287],{},"Three patterns account for most of it.",[289,290,291,297,303],"ol",{},[147,292,293,296],{},[150,294,295],{},"Address poisoning."," An attacker sends a tiny transfer from an address that looks like one you use, same first and last characters. The next time someone copies an address from transaction history, they copy the attacker's. Verify full addresses against a saved allowlist, never from history.",[147,298,299,302],{},[150,300,301],{},"Malicious approvals."," On EVM chains, a token approval lets a contract spend tokens from your wallet. A phishing site that tricks you into an unlimited approval can drain the wallet later. Approve only the exact amount a payment needs, and revoke approvals you no longer use.",[147,304,305,308],{},[150,306,307],{},"Reversed bank deposits."," A fraudster funds an account by ACH, receives stablecoins, then reverses the ACH while its return window is still open. The stablecoins are gone and the platform eats the loss. This is why providers hold new or unusual bank deposits and monitor the fiat leg continuously.",[11,310,311,312,316],{},"Identity checks at signup don't catch any of these on their own. Transaction monitoring does. ",[133,313,315],{"href":314},"\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments","Real-time transaction monitoring"," covers the rules providers run.",[18,318,320],{"id":319},"can-a-stablecoin-be-frozen","Can a stablecoin be frozen?",[11,322,323,324,329],{},"Yes. USDC and USDT both let their issuers block specific addresses, and issuers use it for sanctions and law-enforcement requests. The US Treasury's Office of Foreign Assets Control also lists specific blockchain addresses on its ",[133,325,328],{"href":326,"rel":327},"https:\u002F\u002Fofac.treasury.gov\u002Fspecially-designated-nationals-and-blocked-persons-list-sdn-human-readable-lists",[137],"sanctions list",".",[11,331,332,333,337],{},"For a legitimate business, the exposure is indirect: taking payment from an address that's later frozen or tied to a sanctioned party. The fix is screening. Providers check wallet addresses against sanctions and risk data, not only the people behind them, and the ",[133,334,336],{"href":335},"\u002Fresources\u002Fmore\u002Ftravel-rule-stablecoin-off-ramps","travel rule"," makes sure identity data moves with transfers between providers.",[18,339,341],{"id":340},"are-stablecoin-payments-safer-than-wires-or-cards","Are stablecoin payments safer than wires or cards?",[11,343,344],{},"Different, not strictly safer. Each rail puts the risk in a different place.",[23,346,347,362],{},[26,348,349],{},[29,350,351,353,356,359],{},[32,352],{},[32,354,355],{},"Stablecoin payment",[32,357,358],{},"International wire",[32,360,361],{},"Card payment",[42,363,364,378,392,406,420],{},[29,365,366,369,372,375],{},[47,367,368],{},"Reversibility",[47,370,371],{},"Final once confirmed",[47,373,374],{},"Recall possible, not guaranteed",[47,376,377],{},"Chargebacks for months",[29,379,380,383,386,389],{},[47,381,382],{},"Main fraud risk",[47,384,385],{},"Wrong address, phishing, reversed funding",[47,387,388],{},"Business email compromise, fake invoices",[47,390,391],{},"Stolen cards, friendly fraud",[29,393,394,397,400,403],{},[47,395,396],{},"Visibility",[47,398,399],{},"Every transfer is on a public ledger",[47,401,402],{},"Status via tracking, if the banks report it",[47,404,405],{},"Processor dashboards",[29,407,408,411,414,417],{},[47,409,410],{},"Deposit insurance",[47,412,413],{},"None",[47,415,416],{},"Bank deposits at either end are insured to limits",[47,418,419],{},"Card network rules protect the payer",[29,421,422,425,428,431],{},[47,423,424],{},"Settlement speed",[47,426,427],{},"Seconds to minutes",[47,429,430],{},"1 to 5 business days",[47,432,433],{},"Days for the merchant",[11,435,436],{},"For a business paying suppliers or contractors, finality is often a feature: the payment can't be clawed back after the goods ship. For a business collecting from strangers, card chargebacks protect the payer, and stablecoins don't.",[18,438,440],{"id":439},"how-can-a-business-make-stablecoin-payments-safer","How can a business make stablecoin payments safer?",[289,442,443,446,449,452,455,458,461,464],{},[147,444,445],{},"Use fully reserved stablecoins from regulated issuers, and check their reserve reports.",[147,447,448],{},"Know who holds your funds at every step, product by product.",[147,450,451],{},"Keep an allowlist of recipient addresses and networks. Never copy from history.",[147,453,454],{},"Send a small test transfer before any large first payment.",[147,456,457],{},"Approve exact amounts on EVM chains and revoke old approvals.",[147,459,460],{},"Support more than one network for each stablecoin you rely on.",[147,462,463],{},"Screen counterparties and wallet addresses, not just your own customers.",[147,465,466],{},"Confirm corridors, limits, and liquidity before you depend on an off-ramp.",[11,468,469,470,329],{},"The questions to put to a provider are in ",[133,471,473],{"href":472},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","30 due diligence questions",[18,475,477],{"id":476},"how-does-blindpay-reduce-these-risks","How does BlindPay reduce these risks?",[11,479,480],{},"BlindPay converts USDC and USDT to and from local currency, with compliance in the payment flow. Payouts from an external wallet are non-custodial: the stablecoins move only when the quoted payout executes, and a refunded payout returns them to the wallet that funded it right away. Managed wallets, in beta, are custodied by BlindPay, and the docs say so.",[11,482,483,484,488,489,493,494,498],{},"Every customer is verified with KYC or KYB before their first transaction, and payouts are screened as they run. Payouts to US bank accounts pass through a compliance review step, and a payout that needs a closer look moves to ",[485,486,487],"code",{},"on_hold"," with a webhook, for up to 30 days, as described in ",[133,490,492],{"href":491},"\u002Fdocs\u002Fkb\u002Fon-hold-transactions","on-hold transactions",". The API rejects unsupported token and network pairs before any funds move, across Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, and Tron (",[133,495,497],{"href":496},"\u002Fdocs\u002Fkb\u002Fsupported-chains","supported chains",").",[11,500,501,502,506,507,329],{},"BlindPay is registered with FinCEN as a Money Services Business and lists its licenses on the ",[133,503,505],{"href":504},"\u002Flicenses","licenses page",". Security controls, including SOC 2 Type 2 and independent penetration testing, are on the ",[133,508,510],{"href":509},"\u002Fsecurity","security page",[11,512,513,514,329],{},"Pick the one risk in the table above you've covered least, and fix that first. For how stablecoin payments work end to end, start with ",[133,515,517],{"href":516},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide","stablecoin payments explained",{"title":519,"searchDepth":520,"depth":520,"links":521},"",2,[522,523,524,525,526,527,528,529,530,531,532],{"id":20,"depth":520,"text":21},{"id":127,"depth":520,"text":128},{"id":184,"depth":520,"text":185},{"id":205,"depth":520,"text":206},{"id":248,"depth":520,"text":249},{"id":263,"depth":520,"text":264},{"id":283,"depth":520,"text":284},{"id":319,"depth":520,"text":320},{"id":340,"depth":520,"text":341},{"id":439,"depth":520,"text":440},{"id":476,"depth":520,"text":477},"stablecoins","2026-09-26","Stablecoin payments are as safe as the issuer, the network, the provider, and your own controls. The seven risks to check, with real incidents and fixes.","md",[538,541,544,547,550],{"q":539,"a":540},"Are stablecoin payments safe for businesses?","They can be, when four things hold: the stablecoin is fully reserved and redeemable, the network is reliable, the provider is licensed and clear about custody, and your own team checks addresses and networks before sending. Most losses come from operational mistakes and fraud, not from the technology failing.",{"q":542,"a":543},"Can USDC lose its peg?","It has, briefly. In March 2023, USDC traded below 90 cents after Circle disclosed that $3.3 billion of its reserves sat at Silicon Valley Bank, which had just failed. It returned to about $1 within days, once US authorities guaranteed the bank's deposits. The episode showed that reserve quality and where reserves are held matter as much as the 1:1 promise.",{"q":545,"a":546},"Are stablecoins FDIC insured?","No. A stablecoin is not a bank deposit, and the GENIUS Act bars issuers from marketing payment stablecoins as federally insured. Protection comes from the issuer's reserves and, under the GENIUS Act, from holders' priority claim on those reserves if the issuer fails.",{"q":548,"a":549},"Can a stablecoin transaction be frozen?","Yes. The major dollar stablecoins, including USDC and USDT, let their issuers block specific addresses, and issuers use this for sanctions and law-enforcement requests. For a business, the practical risk is receiving funds from an address that is later frozen or flagged, which is why providers screen wallet addresses as well as people.",{"q":551,"a":552},"What happens if I send stablecoins to the wrong address?","The transfer is final on-chain, so there is no bank to call for a recall. If the address belongs to a cooperative party or a known exchange, you can ask them to send it back. If it belongs to no one, or to a scammer, the funds are usually gone. Test with a small amount before a large first transfer.",false,{"author":555},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-safe","---\ntitle: \"Are stablecoin payments safe? The risks businesses should check, and how to reduce them\"\nseoTitle: \"Are stablecoin payments safe? Risks for businesses\"\ndescription: \"Stablecoin payments are as safe as the issuer, the network, the provider, and your own controls. The seven risks to check, with real incidents and fixes.\"\ndate: \"2026-09-26\"\nupdated: \"2026-09-26\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Are stablecoin payments safe for businesses?\"\n    a: \"They can be, when four things hold: the stablecoin is fully reserved and redeemable, the network is reliable, the provider is licensed and clear about custody, and your own team checks addresses and networks before sending. Most losses come from operational mistakes and fraud, not from the technology failing.\"\n  - q: \"Can USDC lose its peg?\"\n    a: \"It has, briefly. In March 2023, USDC traded below 90 cents after Circle disclosed that $3.3 billion of its reserves sat at Silicon Valley Bank, which had just failed. It returned to about $1 within days, once US authorities guaranteed the bank's deposits. The episode showed that reserve quality and where reserves are held matter as much as the 1:1 promise.\"\n  - q: \"Are stablecoins FDIC insured?\"\n    a: \"No. A stablecoin is not a bank deposit, and the GENIUS Act bars issuers from marketing payment stablecoins as federally insured. Protection comes from the issuer's reserves and, under the GENIUS Act, from holders' priority claim on those reserves if the issuer fails.\"\n  - q: \"Can a stablecoin transaction be frozen?\"\n    a: \"Yes. The major dollar stablecoins, including USDC and USDT, let their issuers block specific addresses, and issuers use this for sanctions and law-enforcement requests. For a business, the practical risk is receiving funds from an address that is later frozen or flagged, which is why providers screen wallet addresses as well as people.\"\n  - q: \"What happens if I send stablecoins to the wrong address?\"\n    a: \"The transfer is final on-chain, so there is no bank to call for a recall. If the address belongs to a cooperative party or a known exchange, you can ask them to send it back. If it belongs to no one, or to a scammer, the funds are usually gone. Test with a small amount before a large first transfer.\"\n---\n\nStablecoin payments are safe when four layers hold: a fully reserved stablecoin, a reliable network, a licensed provider with clear custody, and your own controls on addresses and networks. The technology rarely fails on its own. Losses usually come from a weak issuer, a provider that holds your money without saying so, or a human who pasted the wrong address.\n\nSo the useful question isn't \"are stablecoins safe?\" It's \"which of the seven risks below have I covered?\"\n\n## What are the risks of stablecoin payments?\n\n| Risk | What can go wrong | How to reduce it |\n| --- | --- | --- |\n| Issuer and reserves | The stablecoin trades below $1 or redemptions slow down | Use fully reserved, attested stablecoins from regulated issuers |\n| Network | The blockchain halts or fees spike | Support more than one network per stablecoin |\n| Irreversible errors | Funds go to the wrong address or network | Allowlist addresses, test with small amounts |\n| Custody and provider | The provider holding your funds fails or freezes | Know who holds the funds at every step |\n| Conversion to cash | You can't off-ramp when you need to | Check corridors, limits, and liquidity before you depend on them |\n| Fraud | Address poisoning, malicious approvals, reversed bank deposits | Verify addresses out of band, approve exact amounts, hold risky deposits |\n| Compliance | Funds tied to a sanctioned party get frozen | Screen counterparties and wallet addresses, not just customers |\n\nEach one is covered below.\n\n## Can a stablecoin lose its peg?\n\nYes, and a major one already has. On March 10, 2023, Circle disclosed that $3.3 billion of the reserves backing USDC were held at Silicon Valley Bank, which had just failed. USDC [traded below 90 cents](https:\u002F\u002Fwww.axios.com\u002F2023\u002F03\u002F11\u002Fcircle-usdc-peg-svb) the next day. It returned to about $1 within days, once US authorities said all of the bank's deposits would be protected.\n\nThe lesson isn't that USDC is unsafe. It's that a stablecoin is only as good as its reserves and where they sit. Before you hold a balance, check:\n\n- **What backs it.** Cash and short-term government debt, or something riskier.\n- **How often reserves are reported.** Monthly reports with an independent accountant's attestation are the norm for the large regulated issuers.\n- **Who can redeem, and how fast.** Redemption at par is what holds the peg.\n\nRegulation is tightening this. In the EU, [MiCA](\u002Fresources\u002Fmore\u002Fmica-stablecoin-rules-explained) already requires e-money tokens to be fully reserved and redeemable at par. In the US, the GENIUS Act requires 1:1 reserves in cash and short-term Treasuries, with monthly disclosure, once its rules take effect. [USDC vs USDT for payments](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) compares how the two largest issuers report.\n\nStablecoins are not bank deposits and are not FDIC insured. Treat a stablecoin balance like a claim on the issuer's reserves, because that's what it is.\n\n## What happens if a blockchain network goes down?\n\nPayments on that network stop until it recovers. Solana, for example, [halted block production for about five hours](https:\u002F\u002Fcointelegraph.com\u002Fnews\u002Fsolana-network-outage-block-production-halted) on February 6, 2024. Funds weren't lost, but nothing moved.\n\nOutages like that are rare on the major networks, and fee spikes are more common. Both are manageable if you don't depend on a single chain. A provider that settles the same stablecoin on several networks lets you route around a bad day. [What happens on-chain in a stablecoin payment](\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment) explains what the network does during a transfer.\n\n## Can stablecoin payments be reversed or recovered?\n\nNo, not by the network. A confirmed transfer is final. There's no chargeback and no recall message. That finality is useful, since it proves exactly who held the funds and when, but it means mistakes stick.\n\nThe common ones:\n\n- **Wrong address.** A typo, or an address copied from the wrong place.\n- **Wrong network.** The right address on a chain the receiver doesn't monitor.\n- **Unsupported token.** A stablecoin the receiving provider can't accept on that network.\n\nControls that work: an allowlist of saved recipient addresses, a small test transfer before any large first payment, and a provider that rejects unsupported token and network pairs before anything moves. [Are stablecoin payments reversible](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) goes deeper on finality, and [common stablecoin payout mistakes](\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes) lists the errors to block in your code.\n\n## What happens if the provider fails?\n\nThat depends on custody. If a provider holds your stablecoins or fiat between steps, you're exposed to its solvency, its banks, and its operations. If the flow is non-custodial, the funds stay in a wallet you control until the payment executes.\n\nNeither model is automatically right. Custodial products can be convenient. What matters is knowing which one you're using, product by product. A provider can be non-custodial for payouts and custodial for a hosted wallet. [Custodial vs non-custodial off-ramps](\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps) walks through what happens in each model when a provider becomes insolvent or loses its bank.\n\n## Can you always convert stablecoins back to cash?\n\nNot everywhere, and not in any amount. Converting stablecoins to local currency needs a licensed off-ramp in the destination country, a local payout rail, and enough liquidity for your volume. Per-transaction and monthly limits apply by verification tier.\n\nThe risk shows up when a business holds stablecoins assuming it can exit anytime, then hits a corridor that isn't supported or a limit it didn't plan for. Check the corridors you need, the limits that apply to you, and how liquidity holds up at your largest payment size. [Stablecoin off-ramp limits](\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-limits) and [liquidity risk in global payouts](\u002Fresources\u002Fmore\u002Fliquidity-risk-global-payouts) cover both.\n\n## What fraud should businesses watch for?\n\nThree patterns account for most of it.\n\n1. **Address poisoning.** An attacker sends a tiny transfer from an address that looks like one you use, same first and last characters. The next time someone copies an address from transaction history, they copy the attacker's. Verify full addresses against a saved allowlist, never from history.\n2. **Malicious approvals.** On EVM chains, a token approval lets a contract spend tokens from your wallet. A phishing site that tricks you into an unlimited approval can drain the wallet later. Approve only the exact amount a payment needs, and revoke approvals you no longer use.\n3. **Reversed bank deposits.** A fraudster funds an account by ACH, receives stablecoins, then reverses the ACH while its return window is still open. The stablecoins are gone and the platform eats the loss. This is why providers hold new or unusual bank deposits and monitor the fiat leg continuously.\n\nIdentity checks at signup don't catch any of these on their own. Transaction monitoring does. [Real-time transaction monitoring](\u002Fresources\u002Fmore\u002Freal-time-transaction-monitoring-stablecoin-payments) covers the rules providers run.\n\n## Can a stablecoin be frozen?\n\nYes. USDC and USDT both let their issuers block specific addresses, and issuers use it for sanctions and law-enforcement requests. The US Treasury's Office of Foreign Assets Control also lists specific blockchain addresses on its [sanctions list](https:\u002F\u002Fofac.treasury.gov\u002Fspecially-designated-nationals-and-blocked-persons-list-sdn-human-readable-lists).\n\nFor a legitimate business, the exposure is indirect: taking payment from an address that's later frozen or tied to a sanctioned party. The fix is screening. Providers check wallet addresses against sanctions and risk data, not only the people behind them, and the [travel rule](\u002Fresources\u002Fmore\u002Ftravel-rule-stablecoin-off-ramps) makes sure identity data moves with transfers between providers.\n\n## Are stablecoin payments safer than wires or cards?\n\nDifferent, not strictly safer. Each rail puts the risk in a different place.\n\n| | Stablecoin payment | International wire | Card payment |\n| --- | --- | --- | --- |\n| Reversibility | Final once confirmed | Recall possible, not guaranteed | Chargebacks for months |\n| Main fraud risk | Wrong address, phishing, reversed funding | Business email compromise, fake invoices | Stolen cards, friendly fraud |\n| Visibility | Every transfer is on a public ledger | Status via tracking, if the banks report it | Processor dashboards |\n| Deposit insurance | None | Bank deposits at either end are insured to limits | Card network rules protect the payer |\n| Settlement speed | Seconds to minutes | 1 to 5 business days | Days for the merchant |\n\nFor a business paying suppliers or contractors, finality is often a feature: the payment can't be clawed back after the goods ship. For a business collecting from strangers, card chargebacks protect the payer, and stablecoins don't.\n\n## How can a business make stablecoin payments safer?\n\n1. Use fully reserved stablecoins from regulated issuers, and check their reserve reports.\n2. Know who holds your funds at every step, product by product.\n3. Keep an allowlist of recipient addresses and networks. Never copy from history.\n4. Send a small test transfer before any large first payment.\n5. Approve exact amounts on EVM chains and revoke old approvals.\n6. Support more than one network for each stablecoin you rely on.\n7. Screen counterparties and wallet addresses, not just your own customers.\n8. Confirm corridors, limits, and liquidity before you depend on an off-ramp.\n\nThe questions to put to a provider are in [30 due diligence questions](\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence).\n\n## How does BlindPay reduce these risks?\n\nBlindPay converts USDC and USDT to and from local currency, with compliance in the payment flow. Payouts from an external wallet are non-custodial: the stablecoins move only when the quoted payout executes, and a refunded payout returns them to the wallet that funded it right away. Managed wallets, in beta, are custodied by BlindPay, and the docs say so.\n\nEvery customer is verified with KYC or KYB before their first transaction, and payouts are screened as they run. Payouts to US bank accounts pass through a compliance review step, and a payout that needs a closer look moves to `on_hold` with a webhook, for up to 30 days, as described in [on-hold transactions](\u002Fdocs\u002Fkb\u002Fon-hold-transactions). The API rejects unsupported token and network pairs before any funds move, across Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, and Tron ([supported chains](\u002Fdocs\u002Fkb\u002Fsupported-chains)).\n\nBlindPay is registered with FinCEN as a Money Services Business and lists its licenses on the [licenses page](\u002Flicenses). Security controls, including SOC 2 Type 2 and independent penetration testing, are on the [security page](\u002Fsecurity).\n\nPick the one risk in the table above you've covered least, and fix that first. For how stablecoin payments work end to end, start with [stablecoin payments explained](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n",{"title":5,"description":535},"Are stablecoin payments safe? Risks for businesses","resources\u002Fmore\u002Fare-stablecoin-payments-safe","WStmGbAQpW5bZgJFzcuk-Xith1kxgCiwH46s1m495xk",[564,903,1253,1789,2154,2637,2885,3566,4172,4541,5222,5686,5857,5994,6396,6710,7027,7489,7947,8051,8332,8666,9111,9685],{"id":4,"title":5,"authors":6,"body":565,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":534,"description":535,"extension":536,"faq":895,"howto":6,"isBlog":553,"isChangelog":553,"meta":901,"navigation":556,"path":557,"pillar":553,"products":6,"rawbody":558,"role":6,"seo":902,"seoTitle":560,"stem":561,"thumbnail":6,"updated":534,"__hash__":562},{"type":8,"value":566,"toc":882},[567,569,571,573,643,645,647,652,654,668,674,676,678,683,687,689,691,693,707,713,715,717,721,723,725,731,733,735,749,753,755,760,764,766,768,834,836,838,856,860,862,864,872,878],[11,568,13],{},[11,570,16],{},[18,572,21],{"id":20},[23,574,575,585],{},[26,576,577],{},[29,578,579,581,583],{},[32,580,34],{},[32,582,37],{},[32,584,40],{},[42,586,587,595,603,611,619,627,635],{},[29,588,589,591,593],{},[47,590,49],{},[47,592,52],{},[47,594,55],{},[29,596,597,599,601],{},[47,598,60],{},[47,600,63],{},[47,602,66],{},[29,604,605,607,609],{},[47,606,71],{},[47,608,74],{},[47,610,77],{},[29,612,613,615,617],{},[47,614,82],{},[47,616,85],{},[47,618,88],{},[29,620,621,623,625],{},[47,622,93],{},[47,624,96],{},[47,626,99],{},[29,628,629,631,633],{},[47,630,104],{},[47,632,107],{},[47,634,110],{},[29,636,637,639,641],{},[47,638,115],{},[47,640,118],{},[47,642,121],{},[11,644,124],{},[18,646,128],{"id":127},[11,648,131,649,139],{},[133,650,138],{"href":135,"rel":651},[137],[11,653,142],{},[144,655,656,660,664],{},[147,657,658,153],{},[150,659,152],{},[147,661,662,159],{},[150,663,158],{},[147,665,666,165],{},[150,667,164],{},[11,669,168,670,173,672,178],{},[133,671,172],{"href":171},[133,673,177],{"href":176},[11,675,181],{},[18,677,185],{"id":184},[11,679,188,680,194],{},[133,681,193],{"href":191,"rel":682},[137],[11,684,197,685,202],{},[133,686,201],{"href":200},[18,688,206],{"id":205},[11,690,209],{},[11,692,212],{},[144,694,695,699,703],{},[147,696,697,220],{},[150,698,219],{},[147,700,701,226],{},[150,702,225],{},[147,704,705,232],{},[150,706,231],{},[11,708,235,709,240,711,245],{},[133,710,239],{"href":238},[133,712,244],{"href":243},[18,714,249],{"id":248},[11,716,252],{},[11,718,255,719,260],{},[133,720,259],{"href":258},[18,722,264],{"id":263},[11,724,267],{},[11,726,270,727,275,729,280],{},[133,728,274],{"href":273},[133,730,279],{"href":278},[18,732,284],{"id":283},[11,734,287],{},[289,736,737,741,745],{},[147,738,739,296],{},[150,740,295],{},[147,742,743,302],{},[150,744,301],{},[147,746,747,308],{},[150,748,307],{},[11,750,311,751,316],{},[133,752,315],{"href":314},[18,754,320],{"id":319},[11,756,323,757,329],{},[133,758,328],{"href":326,"rel":759},[137],[11,761,332,762,337],{},[133,763,336],{"href":335},[18,765,341],{"id":340},[11,767,344],{},[23,769,770,782],{},[26,771,772],{},[29,773,774,776,778,780],{},[32,775],{},[32,777,355],{},[32,779,358],{},[32,781,361],{},[42,783,784,794,804,814,824],{},[29,785,786,788,790,792],{},[47,787,368],{},[47,789,371],{},[47,791,374],{},[47,793,377],{},[29,795,796,798,800,802],{},[47,797,382],{},[47,799,385],{},[47,801,388],{},[47,803,391],{},[29,805,806,808,810,812],{},[47,807,396],{},[47,809,399],{},[47,811,402],{},[47,813,405],{},[29,815,816,818,820,822],{},[47,817,410],{},[47,819,413],{},[47,821,416],{},[47,823,419],{},[29,825,826,828,830,832],{},[47,827,424],{},[47,829,427],{},[47,831,430],{},[47,833,433],{},[11,835,436],{},[18,837,440],{"id":439},[289,839,840,842,844,846,848,850,852,854],{},[147,841,445],{},[147,843,448],{},[147,845,451],{},[147,847,454],{},[147,849,457],{},[147,851,460],{},[147,853,463],{},[147,855,466],{},[11,857,469,858,329],{},[133,859,473],{"href":472},[18,861,477],{"id":476},[11,863,480],{},[11,865,483,866,488,868,493,870,498],{},[485,867,487],{},[133,869,492],{"href":491},[133,871,497],{"href":496},[11,873,501,874,506,876,329],{},[133,875,505],{"href":504},[133,877,510],{"href":509},[11,879,513,880,329],{},[133,881,517],{"href":516},{"title":519,"searchDepth":520,"depth":520,"links":883},[884,885,886,887,888,889,890,891,892,893,894],{"id":20,"depth":520,"text":21},{"id":127,"depth":520,"text":128},{"id":184,"depth":520,"text":185},{"id":205,"depth":520,"text":206},{"id":248,"depth":520,"text":249},{"id":263,"depth":520,"text":264},{"id":283,"depth":520,"text":284},{"id":319,"depth":520,"text":320},{"id":340,"depth":520,"text":341},{"id":439,"depth":520,"text":440},{"id":476,"depth":520,"text":477},[896,897,898,899,900],{"q":539,"a":540},{"q":542,"a":543},{"q":545,"a":546},{"q":548,"a":549},{"q":551,"a":552},{"author":555},{"title":5,"description":535},{"id":904,"title":905,"authors":6,"body":906,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1226,"description":1227,"extension":536,"faq":1228,"howto":6,"isBlog":553,"isChangelog":553,"meta":1247,"navigation":556,"path":1248,"pillar":553,"products":6,"rawbody":1249,"role":6,"seo":1250,"seoTitle":905,"stem":1251,"thumbnail":6,"updated":6,"__hash__":1252},"content\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026.md","Best stablecoin APIs for cross-border payments in 2026: BlindPay, Circle, Stripe, Bridge, and Fireblocks compared",{"type":8,"value":907,"toc":1213},[908,911,918,922,1053,1056,1060,1079,1084,1089,1095,1100,1104,1107,1112,1115,1119,1132,1136,1139,1143,1163,1166,1170,1179,1192,1196,1207],[11,909,910],{},"The best stablecoin API for cross-border payments depends on which job you are hiring it for. BlindPay is built for paying out stablecoins as local currency across borders with no pre-funding. Circle issues USDC and runs the infrastructure for the dollar leg. Stripe brings stablecoin payments to its merchant base and owns Bridge, a stablecoin orchestration API. Fireblocks secures the assets with MPC custody and leaves the payment logic to you.",[11,912,913,914,329],{},"This comparison covers those five providers across primary use case, pre-funding requirement, supported payout regions, and developer experience, then works through how to choose by buyer scenario. For the wider field of ten providers, including BVNK, Zero Hash, Conduit, Sphere, and Borderless, read the ",[133,915,917],{"href":916},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026","broader stablecoin API comparison",[18,919,921],{"id":920},"how-do-the-five-providers-compare","How do the five providers compare?",[23,923,924,943],{},[26,925,926],{},[29,927,928,931,934,937,940],{},[32,929,930],{},"Provider",[32,932,933],{},"Primary use case",[32,935,936],{},"Pre-funding required",[32,938,939],{},"Supported payout regions",[32,941,942],{},"Developer experience",[42,944,945,969,990,1011,1032],{},[29,946,947,953,956,959,962],{},[47,948,949],{},[133,950,952],{"href":951},"\u002Fglobal-payments","BlindPay",[47,954,955],{},"Stablecoin payouts and collections into local currency",[47,957,958],{},"No",[47,960,961],{},"Brazil (Pix), Mexico (SPEI), Colombia, Argentina, United States (ACH, RTP), Europe (SEPA), 100+ countries via SWIFT (POBO\u002FCOBO)",[47,963,964,965],{},"REST API with OpenAPI spec, SDKs for Node, Python, Go, PHP, and Swift, MCP server, public sandbox, ",[133,966,968],{"href":967},"\u002Fpricing","published pricing",[29,970,971,978,981,984,987],{},[47,972,973],{},[133,974,977],{"href":975,"rel":976},"https:\u002F\u002Fwww.circle.com",[137],"Circle",[47,979,980],{},"USDC and EURC issuance, programmable wallets, Circle Payments Network",[47,982,983],{},"Circle Mint requires funded accounts for mint and redeem",[47,985,986],{},"On-chain globally; fiat delivery via Circle Payments Network partner institutions",[47,988,989],{},"Well-documented APIs and SDKs for wallets and transfers; Mint and CPN access through a sales process",[29,991,992,999,1002,1005,1008],{},[47,993,994],{},[133,995,998],{"href":996,"rel":997},"https:\u002F\u002Fstripe.com",[137],"Stripe",[47,1000,1001],{},"Stablecoin payments and financial accounts for existing Stripe merchants",[47,1003,1004],{},"Balances held in Stripe accounts",[47,1006,1007],{},"Markets where Stripe operates, subject to product eligibility",[47,1009,1010],{},"Stripe's developer tooling; stablecoin features gated by account and region",[29,1012,1013,1020,1023,1026,1029],{},[47,1014,1015],{},[133,1016,1019],{"href":1017,"rel":1018},"https:\u002F\u002Fwww.bridge.xyz",[137],"Bridge",[47,1021,1022],{},"Stablecoin orchestration: issuance, wallets, conversion, virtual accounts, cards",[47,1024,1025],{},"Provider-managed custodial wallets or self-custody, funded per flow",[47,1027,1028],{},"United States, Europe, United Kingdom, Mexico, Brazil, Colombia via ACH, wire, SEPA, Faster Payments, SPEI, Pix",[47,1030,1031],{},"REST API and docs, hosted KYC links, sandbox; pricing through sales",[29,1033,1034,1041,1044,1047,1050],{},[47,1035,1036],{},[133,1037,1040],{"href":1038,"rel":1039},"https:\u002F\u002Fwww.fireblocks.com",[137],"Fireblocks",[47,1042,1043],{},"MPC custody, treasury security, wallet infrastructure across 60+ networks",[47,1045,1046],{},"Not applicable; you hold your own assets",[47,1048,1049],{},"On-chain; fiat off-ramps via third-party network partners",[47,1051,1052],{},"Enterprise SDKs and APIs for custody and wallet operations",[11,1054,1055],{},"Rails, regions, and features change often. Treat the table as a snapshot of each provider's center of gravity and confirm current details on each provider's site before committing.",[18,1057,1059],{"id":1058},"what-does-each-provider-actually-do-well","What does each provider actually do well?",[11,1061,1062,1064,1065,1069,1070,275,1074,1078],{},[150,1063,952],{}," is a payout and collection network. A business sends USDC or USDT, or deposits dollars into a ",[133,1066,1068],{"href":1067},"\u002Fvirtual-accounts","virtual USD account",", and the receiver gets local currency over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on every wire. KYC, KYB, sanctions screening, and travel rule compliance run inside the API before money moves. There is no pre-funding requirement, pricing is published, and every quote shows the exact receive amount before you commit. Depth is strongest in the Americas, with corridors such as ",[133,1071,1073],{"href":1072},"\u002Fusdc-to-brl","USDC to BRL",[133,1075,1077],{"href":1076},"\u002Fusdc-to-mxn","USDC to MXN",". BlindPay does not issue stablecoins, does not offer custody as a product, and is not a card acquirer.",[11,1080,1081,1083],{},[150,1082,977],{}," is the issuer of USDC, the largest regulated dollar stablecoin, and of EURC. Its developer platform covers programmable wallets, cross-chain transfers through CCTP, and Circle Mint for institutional mint and redeem. The Circle Payments Network connects banks and payment institutions for cross-border settlement in USDC. If your product is built around holding or issuing digital dollars, Circle is the anchor. It is not a local-currency payout network, and access to Mint and CPN goes through a sales process.",[11,1085,1086,1088],{},[150,1087,998],{}," acquired Bridge in 2025 and has since added stablecoin payments and stablecoin financial accounts to its platform. For a merchant already on Stripe, that means accepting USDC at checkout or holding a stablecoin balance without a new vendor. Stripe moves money through card networks and ACH at its core, and its stablecoin features are gated by account eligibility and region, so it is a strong option for existing Stripe customers and a weak fit as a standalone cross-border payout API.",[11,1090,1091,1094],{},[150,1092,1093],{},"Bridge, a Stripe company",", is a general-purpose stablecoin infrastructure API: issuance of branded stablecoins, managed and self-custody wallets, fiat-to-stablecoin conversion, virtual accounts in several currencies, and stablecoin-backed cards. Its payout rails cover the United States, Europe, the United Kingdom, Mexico, Brazil, and Colombia. It is the tightest fit if you already run on Stripe and want stablecoin flows next to card flows, or if you want to launch your own stablecoin.",[11,1096,1097,1099],{},[150,1098,1040],{}," is digital-asset custody and wallet infrastructure, not a payments company. Institutions choose it for MPC self-custody, policy engines, and treasury security across more than 60 networks, then layer payment logic on top themselves or through Fireblocks network partners. If custody comes first and payouts come second, Fireblocks is the base layer, and a payout API like BlindPay handles the last mile.",[18,1101,1103],{"id":1102},"how-should-you-choose","How should you choose?",[11,1105,1106],{},"Three buyer scenarios cover most of the teams comparing these providers.",[1108,1109,1111],"h3",{"id":1110},"a-fintech-startup-that-needs-fast-integration","A fintech startup that needs fast integration",[11,1113,1114],{},"You need a public sandbox, SDKs in your stack, published pricing, and no minimum volume. Start with the providers that let you integrate without a sales call: BlindPay and Bridge both do. Run ten real test payments through the sandbox and look at the error responses, not just the happy path. If you already process cards on Stripe, Bridge keeps your vendor count at one. If your users are in Latin America and need local currency in a bank account, BlindPay's corridor depth is the differentiator.",[1108,1116,1118],{"id":1117},"an-enterprise-that-needs-compliance-coverage","An enterprise that needs compliance coverage",[11,1120,1121,1122,1126,1127,1131],{},"You need to know who holds the license in each market, whether KYC, KYB, and sanctions screening run before funds move, and how travel rule data is handled. Ask every provider for its licensing posture per country in writing. BlindPay runs compliance inside the API and publishes its ",[133,1123,1125],{"href":1124},"\u002Fcompliance","compliance program",". Circle is regulated as a money transmitter and BitLicense holder in the United States and under MiCA in Europe. Bridge operates under Stripe's US money transmission entities. Fireblocks provides tooling for your own compliance program rather than running one for you. Read ",[133,1128,1130],{"href":1129},"\u002Fresources\u002Fmore\u002Fcompliance-agents-cross-border-stablecoin-payments","compliance agents for cross-border stablecoin payments"," for what automated compliance looks like in practice.",[1108,1133,1135],{"id":1134},"a-company-that-needs-local-payout-rails-without-pre-funding","A company that needs local payout rails without pre-funding",[11,1137,1138],{},"This is the scenario where the five providers separate most sharply. If your payments land in Brazil, Mexico, Colombia, or Argentina and you cannot afford to park capital in each currency, BlindPay is the provider designed for that exact problem: fund each transfer when you send it, get a quoted receive amount, and deliver over the local rail. Bridge covers several of the same countries with a custodial wallet model. Circle and Fireblocks hand you the stablecoin leg and leave the local payout to partners.",[18,1140,1142],{"id":1141},"which-questions-should-you-ask-before-choosing","Which questions should you ask before choosing?",[144,1144,1145,1148,1151,1154,1157,1160],{},[147,1146,1147],{},"Which exact corridors are live in production today, and which are on a roadmap?",[147,1149,1150],{},"Do I need to pre-fund a balance in the destination currency?",[147,1152,1153],{},"Is the FX quote binding, and are the spread and fee shown separately?",[147,1155,1156],{},"Who holds the license in each market I pay into?",[147,1158,1159],{},"Is there a public sandbox, an OpenAPI spec, and an SDK in my language?",[147,1161,1162],{},"What does the receiver actually get on a $10,000 payment to each of my top three corridors?",[11,1164,1165],{},"The last question is the only one that lets you compare providers on a single number. Run it through every sandbox before you sign anything.",[18,1167,1169],{"id":1168},"when-is-blindpay-the-right-choice","When is BlindPay the right choice?",[11,1171,1172,1173,1175,1176,1178],{},"If the job is \"we hold digital dollars, or can deposit dollars, and need people paid in their local currency, compliantly, without pre-funding, through one API\", that is the problem ",[133,1174,952],{"href":951}," is built for. Stablecoin in, Pix, SPEI, ACH, or SWIFT out (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), a quoted rate before you commit, ",[133,1177,968],{"href":967},", and compliance run before money moves.",[11,1180,1181,1182,1186,1187,1191],{},"If the job is issuing a stablecoin, choose Circle or Bridge. If the job is securing assets, choose Fireblocks. If the job is stablecoin checkout for an existing Stripe merchant, choose Stripe. Most teams combine two of these. Read ",[133,1183,1185],{"href":1184},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","how to choose a stablecoin API"," for the full evaluation criteria, or ",[133,1188,1190],{"href":1189},"\u002Fcontact","talk to us"," with one corridor and expand from there.",[18,1193,1195],{"id":1194},"methodology-and-sources","Methodology and sources",[11,1197,1198,1199,275,1202,1206],{},"Provider descriptions are based on public product pages and documentation reviewed in September 2026, plus BlindPay's own ",[133,1200,1201],{"href":967},"pricing",[133,1203,1205],{"href":1204},"\u002Fdocs\u002Fkb\u002Fsupported-countries","coverage"," pages. No provider was ranked on undisclosed data. Where a capability was not visible on a provider's public pages, the table says so rather than guessing.",[11,1208,1209],{},[1210,1211,1212],"em",{},"This article is for general information only and is not legal, tax, or financial advice.",{"title":519,"searchDepth":520,"depth":520,"links":1214},[1215,1216,1217,1223,1224,1225],{"id":920,"depth":520,"text":921},{"id":1058,"depth":520,"text":1059},{"id":1102,"depth":520,"text":1103,"children":1218},[1219,1221,1222],{"id":1110,"depth":1220,"text":1111},3,{"id":1117,"depth":1220,"text":1118},{"id":1134,"depth":1220,"text":1135},{"id":1141,"depth":520,"text":1142},{"id":1168,"depth":520,"text":1169},{"id":1194,"depth":520,"text":1195},"2026-09-17","Five stablecoin APIs compared for cross-border payments: primary use case, pre-funding requirement, payout regions, and developer experience, plus how to choose by buyer scenario.",[1229,1232,1235,1238,1241,1244],{"q":1230,"a":1231},"What is the best stablecoin API for cross-border payments?","For paying out stablecoins as local currency across borders with no pre-funding, BlindPay is the most direct fit: USDC or USDT in, Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO) out, with compliance handled in the API. Circle fits issuer-level USDC access, Stripe and Bridge fit teams already on Stripe, and Fireblocks fits institutions that need MPC custody first.",{"q":1233,"a":1234},"Is Stripe a stablecoin API?","Partly. Stripe offers stablecoin payments and stablecoin financial accounts to its merchants, and it owns Bridge, which is a full stablecoin infrastructure API. If you want stablecoin flows next to your existing Stripe card flows, Stripe plus Bridge is the path. Stripe itself is not a standalone cross-border stablecoin payout API.",{"q":1236,"a":1237},"Does Circle offer an API?","Yes. Circle offers APIs for programmable wallets, cross-chain transfers, and minting and redeeming USDC through Circle Mint, plus the Circle Payments Network for banks and payment institutions. It is infrastructure for the USDC leg rather than a local-currency payout network.",{"q":1239,"a":1240},"What is the cheapest way to send stablecoins across borders?","Sending the stablecoin on-chain is close to free on networks like Base, Polygon, or Solana. The cost sits in the conversion to local currency, so the cheapest route is a provider that quotes the FX rate and fee before you commit and publishes its pricing. Compare providers on the amount the receiver gets, not the advertised fee.",{"q":1242,"a":1243},"Do stablecoin APIs require pre-funding?","Some do. Providers that settle through pre-funded local balances require you to hold capital in each destination currency. BlindPay does not: each transfer is funded at the moment you send it, from a virtual USD account or a stablecoin wallet. Confirm the pre-funding model with any provider before signing.",{"q":1245,"a":1246},"Which stablecoin API is best for a startup?","A startup usually needs a public sandbox, SDKs in its stack, published pricing, and no minimum volume. BlindPay and Bridge both offer self-serve developer access. Circle and Fireblocks skew toward enterprise agreements, and Stripe's stablecoin features depend on your Stripe account being eligible.",{"author":555},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026","---\ntitle: \"Best stablecoin APIs for cross-border payments in 2026: BlindPay, Circle, Stripe, Bridge, and Fireblocks compared\"\nseoTitle: \"Best stablecoin APIs for cross-border payments in 2026: BlindPay, Circle, Stripe, Bridge, and Fireblocks compared\"\ndescription: \"Five stablecoin APIs compared for cross-border payments: primary use case, pre-funding requirement, payout regions, and developer experience, plus how to choose by buyer scenario.\"\ndate: \"2026-09-17\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the best stablecoin API for cross-border payments?\"\n    a: \"For paying out stablecoins as local currency across borders with no pre-funding, BlindPay is the most direct fit: USDC or USDT in, Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO) out, with compliance handled in the API. Circle fits issuer-level USDC access, Stripe and Bridge fit teams already on Stripe, and Fireblocks fits institutions that need MPC custody first.\"\n  - q: \"Is Stripe a stablecoin API?\"\n    a: \"Partly. Stripe offers stablecoin payments and stablecoin financial accounts to its merchants, and it owns Bridge, which is a full stablecoin infrastructure API. If you want stablecoin flows next to your existing Stripe card flows, Stripe plus Bridge is the path. Stripe itself is not a standalone cross-border stablecoin payout API.\"\n  - q: \"Does Circle offer an API?\"\n    a: \"Yes. Circle offers APIs for programmable wallets, cross-chain transfers, and minting and redeeming USDC through Circle Mint, plus the Circle Payments Network for banks and payment institutions. It is infrastructure for the USDC leg rather than a local-currency payout network.\"\n  - q: \"What is the cheapest way to send stablecoins across borders?\"\n    a: \"Sending the stablecoin on-chain is close to free on networks like Base, Polygon, or Solana. The cost sits in the conversion to local currency, so the cheapest route is a provider that quotes the FX rate and fee before you commit and publishes its pricing. Compare providers on the amount the receiver gets, not the advertised fee.\"\n  - q: \"Do stablecoin APIs require pre-funding?\"\n    a: \"Some do. Providers that settle through pre-funded local balances require you to hold capital in each destination currency. BlindPay does not: each transfer is funded at the moment you send it, from a virtual USD account or a stablecoin wallet. Confirm the pre-funding model with any provider before signing.\"\n  - q: \"Which stablecoin API is best for a startup?\"\n    a: \"A startup usually needs a public sandbox, SDKs in its stack, published pricing, and no minimum volume. BlindPay and Bridge both offer self-serve developer access. Circle and Fireblocks skew toward enterprise agreements, and Stripe's stablecoin features depend on your Stripe account being eligible.\"\n---\n\nThe best stablecoin API for cross-border payments depends on which job you are hiring it for. BlindPay is built for paying out stablecoins as local currency across borders with no pre-funding. Circle issues USDC and runs the infrastructure for the dollar leg. Stripe brings stablecoin payments to its merchant base and owns Bridge, a stablecoin orchestration API. Fireblocks secures the assets with MPC custody and leaves the payment logic to you.\n\nThis comparison covers those five providers across primary use case, pre-funding requirement, supported payout regions, and developer experience, then works through how to choose by buyer scenario. For the wider field of ten providers, including BVNK, Zero Hash, Conduit, Sphere, and Borderless, read the [broader stablecoin API comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026).\n\n## How do the five providers compare?\n\n| Provider | Primary use case | Pre-funding required | Supported payout regions | Developer experience |\n| --- | --- | --- | --- | --- |\n| [BlindPay](\u002Fglobal-payments) | Stablecoin payouts and collections into local currency | No | Brazil (Pix), Mexico (SPEI), Colombia, Argentina, United States (ACH, RTP), Europe (SEPA), 100+ countries via SWIFT (POBO\u002FCOBO) | REST API with OpenAPI spec, SDKs for Node, Python, Go, PHP, and Swift, MCP server, public sandbox, [published pricing](\u002Fpricing) |\n| [Circle](https:\u002F\u002Fwww.circle.com) | USDC and EURC issuance, programmable wallets, Circle Payments Network | Circle Mint requires funded accounts for mint and redeem | On-chain globally; fiat delivery via Circle Payments Network partner institutions | Well-documented APIs and SDKs for wallets and transfers; Mint and CPN access through a sales process |\n| [Stripe](https:\u002F\u002Fstripe.com) | Stablecoin payments and financial accounts for existing Stripe merchants | Balances held in Stripe accounts | Markets where Stripe operates, subject to product eligibility | Stripe's developer tooling; stablecoin features gated by account and region |\n| [Bridge](https:\u002F\u002Fwww.bridge.xyz) | Stablecoin orchestration: issuance, wallets, conversion, virtual accounts, cards | Provider-managed custodial wallets or self-custody, funded per flow | United States, Europe, United Kingdom, Mexico, Brazil, Colombia via ACH, wire, SEPA, Faster Payments, SPEI, Pix | REST API and docs, hosted KYC links, sandbox; pricing through sales |\n| [Fireblocks](https:\u002F\u002Fwww.fireblocks.com) | MPC custody, treasury security, wallet infrastructure across 60+ networks | Not applicable; you hold your own assets | On-chain; fiat off-ramps via third-party network partners | Enterprise SDKs and APIs for custody and wallet operations |\n\nRails, regions, and features change often. Treat the table as a snapshot of each provider's center of gravity and confirm current details on each provider's site before committing.\n\n## What does each provider actually do well?\n\n**BlindPay** is a payout and collection network. A business sends USDC or USDT, or deposits dollars into a [virtual USD account](\u002Fvirtual-accounts), and the receiver gets local currency over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on every wire. KYC, KYB, sanctions screening, and travel rule compliance run inside the API before money moves. There is no pre-funding requirement, pricing is published, and every quote shows the exact receive amount before you commit. Depth is strongest in the Americas, with corridors such as [USDC to BRL](\u002Fusdc-to-brl) and [USDC to MXN](\u002Fusdc-to-mxn). BlindPay does not issue stablecoins, does not offer custody as a product, and is not a card acquirer.\n\n**Circle** is the issuer of USDC, the largest regulated dollar stablecoin, and of EURC. Its developer platform covers programmable wallets, cross-chain transfers through CCTP, and Circle Mint for institutional mint and redeem. The Circle Payments Network connects banks and payment institutions for cross-border settlement in USDC. If your product is built around holding or issuing digital dollars, Circle is the anchor. It is not a local-currency payout network, and access to Mint and CPN goes through a sales process.\n\n**Stripe** acquired Bridge in 2025 and has since added stablecoin payments and stablecoin financial accounts to its platform. For a merchant already on Stripe, that means accepting USDC at checkout or holding a stablecoin balance without a new vendor. Stripe moves money through card networks and ACH at its core, and its stablecoin features are gated by account eligibility and region, so it is a strong option for existing Stripe customers and a weak fit as a standalone cross-border payout API.\n\n**Bridge, a Stripe company**, is a general-purpose stablecoin infrastructure API: issuance of branded stablecoins, managed and self-custody wallets, fiat-to-stablecoin conversion, virtual accounts in several currencies, and stablecoin-backed cards. Its payout rails cover the United States, Europe, the United Kingdom, Mexico, Brazil, and Colombia. It is the tightest fit if you already run on Stripe and want stablecoin flows next to card flows, or if you want to launch your own stablecoin.\n\n**Fireblocks** is digital-asset custody and wallet infrastructure, not a payments company. Institutions choose it for MPC self-custody, policy engines, and treasury security across more than 60 networks, then layer payment logic on top themselves or through Fireblocks network partners. If custody comes first and payouts come second, Fireblocks is the base layer, and a payout API like BlindPay handles the last mile.\n\n## How should you choose?\n\nThree buyer scenarios cover most of the teams comparing these providers.\n\n### A fintech startup that needs fast integration\n\nYou need a public sandbox, SDKs in your stack, published pricing, and no minimum volume. Start with the providers that let you integrate without a sales call: BlindPay and Bridge both do. Run ten real test payments through the sandbox and look at the error responses, not just the happy path. If you already process cards on Stripe, Bridge keeps your vendor count at one. If your users are in Latin America and need local currency in a bank account, BlindPay's corridor depth is the differentiator.\n\n### An enterprise that needs compliance coverage\n\nYou need to know who holds the license in each market, whether KYC, KYB, and sanctions screening run before funds move, and how travel rule data is handled. Ask every provider for its licensing posture per country in writing. BlindPay runs compliance inside the API and publishes its [compliance program](\u002Fcompliance). Circle is regulated as a money transmitter and BitLicense holder in the United States and under MiCA in Europe. Bridge operates under Stripe's US money transmission entities. Fireblocks provides tooling for your own compliance program rather than running one for you. Read [compliance agents for cross-border stablecoin payments](\u002Fresources\u002Fmore\u002Fcompliance-agents-cross-border-stablecoin-payments) for what automated compliance looks like in practice.\n\n### A company that needs local payout rails without pre-funding\n\nThis is the scenario where the five providers separate most sharply. If your payments land in Brazil, Mexico, Colombia, or Argentina and you cannot afford to park capital in each currency, BlindPay is the provider designed for that exact problem: fund each transfer when you send it, get a quoted receive amount, and deliver over the local rail. Bridge covers several of the same countries with a custodial wallet model. Circle and Fireblocks hand you the stablecoin leg and leave the local payout to partners.\n\n## Which questions should you ask before choosing?\n\n- Which exact corridors are live in production today, and which are on a roadmap?\n- Do I need to pre-fund a balance in the destination currency?\n- Is the FX quote binding, and are the spread and fee shown separately?\n- Who holds the license in each market I pay into?\n- Is there a public sandbox, an OpenAPI spec, and an SDK in my language?\n- What does the receiver actually get on a $10,000 payment to each of my top three corridors?\n\nThe last question is the only one that lets you compare providers on a single number. Run it through every sandbox before you sign anything.\n\n## When is BlindPay the right choice?\n\nIf the job is \"we hold digital dollars, or can deposit dollars, and need people paid in their local currency, compliantly, without pre-funding, through one API\", that is the problem [BlindPay](\u002Fglobal-payments) is built for. Stablecoin in, Pix, SPEI, ACH, or SWIFT out (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), a quoted rate before you commit, [published pricing](\u002Fpricing), and compliance run before money moves.\n\nIf the job is issuing a stablecoin, choose Circle or Bridge. If the job is securing assets, choose Fireblocks. If the job is stablecoin checkout for an existing Stripe merchant, choose Stripe. Most teams combine two of these. Read [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api) for the full evaluation criteria, or [talk to us](\u002Fcontact) with one corridor and expand from there.\n\n## Methodology and sources\n\nProvider descriptions are based on public product pages and documentation reviewed in September 2026, plus BlindPay's own [pricing](\u002Fpricing) and [coverage](\u002Fdocs\u002Fkb\u002Fsupported-countries) pages. No provider was ranked on undisclosed data. Where a capability was not visible on a provider's public pages, the table says so rather than guessing.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":905,"description":1227},"resources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026","6u_RXhs9j9Vxjx7x7GmmVA_dOjczXfbeFxcmjhIaJXQ",{"id":1254,"title":1255,"authors":6,"body":1256,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1768,"description":1769,"extension":536,"faq":1770,"howto":6,"isBlog":553,"isChangelog":553,"meta":1783,"navigation":556,"path":916,"pillar":553,"products":6,"rawbody":1784,"role":6,"seo":1785,"seoTitle":1255,"stem":1786,"thumbnail":6,"updated":1787,"__hash__":1788},"content\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026.md","Best stablecoin APIs in 2026: 10 providers compared",{"type":8,"value":1257,"toc":1756},[1258,1261,1264,1268,1271,1274,1286,1290,1293,1297,1549,1552,1556,1572,1577,1591,1596,1601,1606,1611,1616,1621,1626,1631,1635,1638,1640,1669,1673,1676,1689,1693,1696,1698,1709,1711,1751],[11,1259,1260],{},"A stablecoin API lets a business send, receive, and convert digital dollars programmatically, without building blockchain infrastructure or a compliance program from scratch. The best one for you depends on whether you need issuance, custody, merchant acceptance, or payouts to bank accounts.",[11,1262,1263],{},"The market behind these APIs is large and growing: public trackers such as DeFiLlama put circulating stablecoin supply above 200 billion dollars, and annual settlement volume is measured in trillions. In 2026, most serious providers fall into one of four camps: issuers, orchestration layers, custody platforms, and payout networks. This comparison covers ten of the most cited providers and where each one actually fits.",[18,1265,1267],{"id":1266},"what-is-a-stablecoin-api","What is a stablecoin API?",[11,1269,1270],{},"A stablecoin API is a hosted service that exposes stablecoin operations, such as minting, transfers, conversion, and fiat payouts, through standard HTTP endpoints. Instead of running nodes, managing keys, and registering as a money services business in every market, a business makes API calls and the provider handles execution, custody or settlement, and regulatory obligations.",[11,1272,1273],{},"The build-versus-buy math is lopsided. Building the same capability in-house means blockchain infrastructure across several networks, banking partnerships in every payout country, an FX desk, and a compliance program with KYC, KYB, sanctions screening, and travel rule reporting. That is a multi-year project for a payments company and a distraction for everyone else. An API compresses it into an integration measured in days and a per-transaction cost.",[11,1275,1276,1277,275,1281,1285],{},"If you are new to the underlying asset, start with ",[133,1278,1280],{"href":1279},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin","what is a stablecoin",[133,1282,1284],{"href":1283},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api","what is a stablecoin API",", then come back to compare providers.",[18,1287,1289],{"id":1288},"what-makes-a-stablecoin-payments-api-different","What makes a stablecoin payments API different?",[11,1291,1292],{},"A stablecoin payments API is the subset of this category built around moving money to people and businesses: quoting FX, converting between stablecoins and local currency, and delivering over local bank rails with compliance inside the flow. Issuer APIs and custody platforms expose the asset; a stablecoin payments API completes the payment. Most of the comparison below turns on which side of that line a provider sits.",[18,1294,1296],{"id":1295},"how-do-the-10-providers-compare","How do the 10 providers compare?",[23,1298,1299,1320],{},[26,1300,1301],{},[29,1302,1303,1305,1308,1311,1314,1317],{},[32,1304,930],{},[32,1306,1307],{},"Rails",[32,1309,1310],{},"Currencies",[32,1312,1313],{},"Custody model",[32,1315,1316],{},"Pricing model",[32,1318,1319],{},"Compliance scope",[42,1321,1322,1343,1365,1387,1410,1432,1456,1479,1503,1525],{},[29,1323,1324,1326,1329,1332,1335,1340],{},[47,1325,952],{},[47,1327,1328],{},"Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO), on-chain",[47,1330,1331],{},"USDC, USDT to BRL, MXN, USD, ARS, COP, EUR",[47,1333,1334],{},"Non-custodial for the business",[47,1336,1337],{},[133,1338,1339],{"href":967},"Flat plus percentage, published",[47,1341,1342],{},"KYC, KYB, sanctions, travel rule handled",[29,1344,1345,1350,1353,1356,1359,1362],{},[47,1346,1347],{},[133,1348,977],{"href":975,"rel":1349},[137],[47,1351,1352],{},"On-chain (many networks), bank wires",[47,1354,1355],{},"USDC, EURC, USD",[47,1357,1358],{},"Issuer custody or self-custody",[47,1360,1361],{},"Volume-based, enterprise quotes",[47,1363,1364],{},"Issuer-level, US and EU regulated",[29,1366,1367,1372,1375,1378,1381,1384],{},[47,1368,1369],{},[133,1370,1019],{"href":1017,"rel":1371},[137],[47,1373,1374],{},"On-chain, ACH, wire, SEPA",[47,1376,1377],{},"USDC, USDT, USDB, USD, EUR",[47,1379,1380],{},"Provider custody",[47,1382,1383],{},"Percentage per conversion",[47,1385,1386],{},"US money transmission via Stripe entities",[29,1388,1389,1396,1399,1402,1404,1407],{},[47,1390,1391],{},[133,1392,1395],{"href":1393,"rel":1394},"https:\u002F\u002Fwww.bvnk.com",[137],"BVNK",[47,1397,1398],{},"On-chain, SEPA, Faster Payments, SWIFT",[47,1400,1401],{},"USDC, USDT, EUR, GBP, USD",[47,1403,1380],{},[47,1405,1406],{},"Enterprise, volume tiers",[47,1408,1409],{},"EMI licenses in Europe, VASP registrations",[29,1411,1412,1417,1420,1423,1426,1429],{},[47,1413,1414],{},[133,1415,1040],{"href":1038,"rel":1416},[137],[47,1418,1419],{},"On-chain (60+ networks)",[47,1421,1422],{},"Most major stablecoins",[47,1424,1425],{},"Self-custody via MPC",[47,1427,1428],{},"Platform fee, enterprise",[47,1430,1431],{},"Tooling for your own licenses",[29,1433,1434,1441,1444,1447,1450,1453],{},[47,1435,1436],{},[133,1437,1440],{"href":1438,"rel":1439},"https:\u002F\u002Fwww.crossmint.com",[137],"Crossmint",[47,1442,1443],{},"On-chain, cards for on-ramp",[47,1445,1446],{},"USDC and others",[47,1448,1449],{},"Managed wallets",[47,1451,1452],{},"Per-transaction",[47,1454,1455],{},"Onboarding and screening built in",[29,1457,1458,1465,1468,1471,1473,1476],{},[47,1459,1460],{},[133,1461,1464],{"href":1462,"rel":1463},"https:\u002F\u002Fzerohash.com",[137],"Zero Hash",[47,1466,1467],{},"On-chain, ACH, wire",[47,1469,1470],{},"USDC and others, USD",[47,1472,1380],{},[47,1474,1475],{},"Enterprise quotes",[47,1477,1478],{},"US MTLs, broker-dealer adjacent",[29,1480,1481,1488,1491,1494,1497,1500],{},[47,1482,1483],{},[133,1484,1487],{"href":1485,"rel":1486},"https:\u002F\u002Fconduitpay.com",[137],"Conduit",[47,1489,1490],{},"Pix, SPEI, Interac, mobile money, on-chain",[47,1492,1493],{},"USDC, USDT to LatAm, Africa, Asia locals",[47,1495,1496],{},"Provider custody (Fireblocks-based)",[47,1498,1499],{},"Volume tiers, per-corridor on quote",[47,1501,1502],{},"Provider-run compliance",[29,1504,1505,1512,1515,1518,1520,1522],{},[47,1506,1507],{},[133,1508,1511],{"href":1509,"rel":1510},"https:\u002F\u002Fspherepay.co",[137],"Sphere",[47,1513,1514],{},"ACH, wire, SEPA, Pix, on-chain",[47,1516,1517],{},"USDC, USDT, EURC to USD, EUR, BRL",[47,1519,1380],{},[47,1521,1452],{},[47,1523,1524],{},"KYC, KYB, sanctions in the API",[29,1526,1527,1534,1537,1540,1543,1546],{},[47,1528,1529],{},[133,1530,1533],{"href":1531,"rel":1532},"https:\u002F\u002Fborderless.xyz",[137],"Borderless",[47,1535,1536],{},"Local rails via partner institutions",[47,1538,1539],{},"Many fiat currencies via partner network",[47,1541,1542],{},"Varies by partner",[47,1544,1545],{},"Enterprise",[47,1547,1548],{},"Locally licensed partner institutions",[11,1550,1551],{},"Rails, supported currencies, and fees change often. Treat the table as a map of each provider's center of gravity and confirm current details on their sites.",[18,1553,1555],{"id":1554},"where-does-each-provider-fit-best","Where does each provider fit best?",[11,1557,1558,1560,1561,1564,1565,1567,1568,1571],{},[150,1559,952],{}," is a payout and collection network: a business sends USDC or USDT and the receiver gets local currency over ",[133,1562,1563],{"href":951},"Pix, SPEI, ACH, or wire",", with KYC, KYB, sanctions screening, and travel rule compliance handled by the API. Cross-border wires run as SWIFT payments and collections on behalf of (POBO\u002FCOBO), with UETR tracking and MT103 confirmations for every transfer. Depth is strongest in the Americas corridors, such as ",[133,1566,1073],{"href":1072},", and ",[133,1569,1570],{"href":1067},"virtual accounts"," cover the reverse direction, converting incoming bank transfers into stablecoins. BlindPay is not a card acquirer and not a consumer wallet; if you need merchant card acceptance or issuer-level USDC access, pair it with one of the providers below.",[11,1573,1574,1576],{},[150,1575,977],{}," is the issuer of USDC. If you want mint-and-redeem access at issuer level, or your product is built around holding USDC reserves, Circle is the anchor integration. It is infrastructure for the dollar leg, not a payout network for local currencies.",[1578,1579,1580,1583],"blockquote",{},[11,1581,1582],{},"USDC has become the largest regulated digital dollar in the world, with 108% year-over-year circulation growth.",[11,1584,1585,1586],{},"Jeremy Allaire, Co-Founder and CEO, Circle, in the ",[133,1587,1590],{"href":1588,"rel":1589},"https:\u002F\u002Fwww.circle.com\u002Freports\u002Finternet-financial-system\u002Ffounders-letter",[137],"2026 Internet Financial System Report",[11,1592,1593,1595],{},[150,1594,1093],{},", is a stablecoin orchestration API: issuance, conversion, and virtual accounts, tightly integrated with the Stripe ecosystem since the acquisition. A strong default if you already run on Stripe and want stablecoin flows next to card flows.",[11,1597,1598,1600],{},[150,1599,1395],{}," targets high-volume merchants and PSPs, with European licensing depth (EMI) and strong EUR and GBP rails. It fits businesses collecting large stablecoin volumes and settling into European bank accounts.",[11,1602,1603,1605],{},[150,1604,1040],{}," is custody and wallet infrastructure, not a payments company. Institutions that must self-custody with MPC and route across many chains choose it, then layer payment logic on top themselves.",[11,1607,1608,1610],{},[150,1609,1440],{}," comes from the wallet and NFT side and fits consumer-facing apps that need embedded wallets plus stablecoin checkout, more than B2B treasury flows.",[11,1612,1613,1615],{},[150,1614,1464],{}," is regulated B2B plumbing for US fintechs and brokerages that want crypto and stablecoin capabilities inside their own products, under Zero Hash's licenses.",[11,1617,1618,1620],{},[150,1619,1487],{}," focuses on emerging-market corridors across Africa, Asia, and Latin America, with local rails such as Pix, SPEI, Interac, and mobile money behind one API, and custody built on Fireblocks. It fits businesses whose corridor map skews toward Africa and Asia alongside the Americas.",[11,1622,1623,1625],{},[150,1624,1511],{}," is an on-ramp and off-ramp API converting between USD, EUR, BRL and USDC, USDT, EURC, with virtual accounts that turn fiat deposits into stablecoins. It fits fintechs that want ramp infrastructure with compliance embedded in the API.",[11,1627,1628,1630],{},[150,1629,1533],{}," is an orchestration and liquidity network rather than a direct provider: one API routes payouts and collections through locally licensed partner institutions across a wide country set. It fits platforms that want breadth of coverage through partners and accept that capabilities vary by corridor.",[18,1632,1634],{"id":1633},"which-blockchain-networks-should-a-stablecoin-api-support","Which blockchain networks should a stablecoin API support?",[11,1636,1637],{},"For payments, the network choice matters less than newcomers expect, because the provider abstracts it, but three things are worth checking. Cost and speed: modern networks such as Base, Polygon, and Solana settle in seconds for cents, while Ethereum mainnet remains the expensive, maximally liquid anchor. Counterparty compatibility: if your customers or partners already hold USDC on a specific chain, receiving natively there avoids bridge risk entirely. And native issuance: prefer stablecoins issued natively on a network over bridged versions, since a natively issued USDC is a direct claim on the issuer's reserves. A good API supports several networks behind one endpoint and lets the business think in dollars, not chains.",[18,1639,1142],{"id":1141},[144,1641,1642,1649,1655,1658,1666],{},[147,1643,1644,1645,329],{},"Which direction does your money move: pay-in, payout, or both? Payout networks and merchant gateways are different products, as covered in ",[133,1646,1648],{"href":1647},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","how to choose a stablecoin payment provider",[147,1650,1651,1652,1654],{},"Which corridors matter? A provider with deep US rails may have nothing in Brazil or Mexico. Check ",[133,1653,1205],{"href":1204}," country by country.",[147,1656,1657],{},"Who holds the funds? Provider custody simplifies integration; self-custody reduces counterparty risk but moves obligations to you.",[147,1659,1660,1661,1665],{},"Whose license do you operate under? Most businesses want the provider's licenses to cover the flow. See the ",[133,1662,1664],{"href":1663},"\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026","stablecoin regulation tracker"," for how MiCA, the GENIUS Act, and Brazil's VASP rules split those obligations.",[147,1667,1668],{},"What is the all-in cost? Compare the delivered amount after FX and fees, not the headline fee.",[18,1670,1672],{"id":1671},"how-do-you-compare-pricing-across-stablecoin-apis","How do you compare pricing across stablecoin APIs?",[11,1674,1675],{},"Published pricing rarely tells the whole story, so run the same test against every shortlisted provider: quote a fixed amount, say 1,000 USDC to Brazilian reais, and record the amount delivered to the recipient's bank account. That single number folds together the provider fee, the FX spread, and any hidden minimums.",[11,1677,1678,1679,275,1681,1685,1686,329],{},"Three patterns to watch. First, percentage fees compound with spread: a provider advertising 0.5% can deliver less than one advertising 1% if its FX rate sits further from mid-market. Second, flat fees dominate at small ticket sizes and vanish at large ones, so test at your real average payment size. Third, some providers price pay-in and payout differently; if you run both directions, quote both. Live corridor pages like ",[133,1680,1073],{"href":1072},[133,1682,1684],{"href":1683},"\u002Fusdt-to-brl","USDT to BRL"," show this delivered-amount math with current rates, and BlindPay's fee schedule is published on the ",[133,1687,1688],{"href":967},"pricing page",[18,1690,1692],{"id":1691},"where-do-these-options-fall-short","Where do these options fall short?",[11,1694,1695],{},"No provider on this list covers everything. Issuer platforms do not deliver local currency in emerging markets. Payout networks do not give you issuer-level mint and redeem. Custody platforms leave licensing to you. Most published pricing is incomplete, and FX spreads are usually only visible at quote time. And every provider gates activity behind KYB review, so onboarding time, not engineering, is the usual bottleneck. If your volumes are small and purely domestic in the US, traditional rails may still be cheaper than any stablecoin route.",[18,1697,1169],{"id":1168},[11,1699,1700,1701,1703,1704,1706,1707,1191],{},"If the job is \"we hold digital dollars and need people paid in their local currency, compliantly, through one API\", that is the exact problem ",[133,1702,952],{"href":951}," is built for. Stablecoin in, Pix, SPEI, ACH, or SWIFT out (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), with a quoted FX rate before you commit, published ",[133,1705,1201],{"href":967},", and compliance checks run before money moves. Teams usually ",[133,1708,1190],{"href":1189},[18,1710,1195],{"id":1194},[11,1712,1713,1714,1718,1719,1718,1723,1718,1727,1718,1731,1718,1735,1739,1740,1745,1746,329],{},"Provider capabilities summarized from public materials as of August 2026: ",[133,1715,1717],{"href":975,"rel":1716},[137],"circle.com",", ",[133,1720,1722],{"href":1017,"rel":1721},[137],"bridge.xyz",[133,1724,1726],{"href":1393,"rel":1725},[137],"bvnk.com",[133,1728,1730],{"href":1038,"rel":1729},[137],"fireblocks.com",[133,1732,1734],{"href":1438,"rel":1733},[137],"crossmint.com",[133,1736,1738],{"href":1462,"rel":1737},[137],"zerohash.com",", and BlindPay's own documentation. Supply and volume figures from public dashboards such as ",[133,1741,1744],{"href":1742,"rel":1743},"https:\u002F\u002Fdefillama.com\u002Fstablecoins",[137],"DeFiLlama",". Rail descriptions from operator pages, including the ",[133,1747,1750],{"href":1748,"rel":1749},"https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en",[137],"Banco Central do Brasil's Pix overview",[11,1752,1753],{},[1210,1754,1755],{},"This article is general information, not legal, tax, or financial advice.",{"title":519,"searchDepth":520,"depth":520,"links":1757},[1758,1759,1760,1761,1762,1763,1764,1765,1766,1767],{"id":1266,"depth":520,"text":1267},{"id":1288,"depth":520,"text":1289},{"id":1295,"depth":520,"text":1296},{"id":1554,"depth":520,"text":1555},{"id":1633,"depth":520,"text":1634},{"id":1141,"depth":520,"text":1142},{"id":1671,"depth":520,"text":1672},{"id":1691,"depth":520,"text":1692},{"id":1168,"depth":520,"text":1169},{"id":1194,"depth":520,"text":1195},"2026-08-15","Ten stablecoin APIs compared for 2026: BlindPay, Circle, Bridge, BVNK, Fireblocks, Crossmint, Zero Hash, Conduit, Sphere, and Borderless, across rails, custody, pricing, and compliance.",[1771,1774,1777,1780],{"q":1772,"a":1773},"What is the best stablecoin API?","It depends on the job. BlindPay is the strongest fit for paying out stablecoins as local currency in markets like Brazil and Mexico with compliance built in. Circle fits issuer-level integrations, Bridge fits orchestration inside the Stripe ecosystem, BVNK fits high-volume European merchants, and Fireblocks fits custody-heavy institutions.",{"q":1775,"a":1776},"Do stablecoin APIs require a crypto license?","Usually the provider holds the licenses and registrations, such as money transmitter licenses or VASP registrations, and the business integrates under the provider's regulatory umbrella. Requirements vary by country, so confirm the provider's licensing posture for each market you operate in.",{"q":1778,"a":1779},"Can a stablecoin API convert USDC to local currency?","Yes. Payout-focused stablecoin APIs convert USDC or USDT to fiat at a quoted rate and deliver funds over local rails such as Pix in Brazil, SPEI in Mexico, or ACH in the United States.",{"q":1781,"a":1782},"How long does it take to integrate a stablecoin API?","A basic payout or pay-in integration typically takes days to a few weeks. Timelines depend mostly on compliance onboarding (KYB review) rather than engineering work, since most providers expose standard REST APIs and webhooks.",{"author":555},"---\ntitle: \"Best stablecoin APIs in 2026: 10 providers compared\"\nseoTitle: \"Best stablecoin APIs in 2026: 10 providers compared\"\ndescription: \"Ten stablecoin APIs compared for 2026: BlindPay, Circle, Bridge, BVNK, Fireblocks, Crossmint, Zero Hash, Conduit, Sphere, and Borderless, across rails, custody, pricing, and compliance.\"\ndate: \"2026-08-15\"\nupdated: \"2026-09-01\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the best stablecoin API?\"\n    a: \"It depends on the job. BlindPay is the strongest fit for paying out stablecoins as local currency in markets like Brazil and Mexico with compliance built in. Circle fits issuer-level integrations, Bridge fits orchestration inside the Stripe ecosystem, BVNK fits high-volume European merchants, and Fireblocks fits custody-heavy institutions.\"\n  - q: \"Do stablecoin APIs require a crypto license?\"\n    a: \"Usually the provider holds the licenses and registrations, such as money transmitter licenses or VASP registrations, and the business integrates under the provider's regulatory umbrella. Requirements vary by country, so confirm the provider's licensing posture for each market you operate in.\"\n  - q: \"Can a stablecoin API convert USDC to local currency?\"\n    a: \"Yes. Payout-focused stablecoin APIs convert USDC or USDT to fiat at a quoted rate and deliver funds over local rails such as Pix in Brazil, SPEI in Mexico, or ACH in the United States.\"\n  - q: \"How long does it take to integrate a stablecoin API?\"\n    a: \"A basic payout or pay-in integration typically takes days to a few weeks. Timelines depend mostly on compliance onboarding (KYB review) rather than engineering work, since most providers expose standard REST APIs and webhooks.\"\n---\n\nA stablecoin API lets a business send, receive, and convert digital dollars programmatically, without building blockchain infrastructure or a compliance program from scratch. The best one for you depends on whether you need issuance, custody, merchant acceptance, or payouts to bank accounts.\n\nThe market behind these APIs is large and growing: public trackers such as DeFiLlama put circulating stablecoin supply above 200 billion dollars, and annual settlement volume is measured in trillions. In 2026, most serious providers fall into one of four camps: issuers, orchestration layers, custody platforms, and payout networks. This comparison covers ten of the most cited providers and where each one actually fits.\n\n## What is a stablecoin API?\n\nA stablecoin API is a hosted service that exposes stablecoin operations, such as minting, transfers, conversion, and fiat payouts, through standard HTTP endpoints. Instead of running nodes, managing keys, and registering as a money services business in every market, a business makes API calls and the provider handles execution, custody or settlement, and regulatory obligations.\n\nThe build-versus-buy math is lopsided. Building the same capability in-house means blockchain infrastructure across several networks, banking partnerships in every payout country, an FX desk, and a compliance program with KYC, KYB, sanctions screening, and travel rule reporting. That is a multi-year project for a payments company and a distraction for everyone else. An API compresses it into an integration measured in days and a per-transaction cost.\n\nIf you are new to the underlying asset, start with [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin) and [what is a stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api), then come back to compare providers.\n\n## What makes a stablecoin payments API different?\n\nA stablecoin payments API is the subset of this category built around moving money to people and businesses: quoting FX, converting between stablecoins and local currency, and delivering over local bank rails with compliance inside the flow. Issuer APIs and custody platforms expose the asset; a stablecoin payments API completes the payment. Most of the comparison below turns on which side of that line a provider sits.\n\n## How do the 10 providers compare?\n\n| Provider | Rails | Currencies | Custody model | Pricing model | Compliance scope |\n|---|---|---|---|---|---|\n| BlindPay | Pix, SPEI, ACH, SWIFT (POBO\u002FCOBO), on-chain | USDC, USDT to BRL, MXN, USD, ARS, COP, EUR | Non-custodial for the business | [Flat plus percentage, published](\u002Fpricing) | KYC, KYB, sanctions, travel rule handled |\n| [Circle](https:\u002F\u002Fwww.circle.com) | On-chain (many networks), bank wires | USDC, EURC, USD | Issuer custody or self-custody | Volume-based, enterprise quotes | Issuer-level, US and EU regulated |\n| [Bridge](https:\u002F\u002Fwww.bridge.xyz) | On-chain, ACH, wire, SEPA | USDC, USDT, USDB, USD, EUR | Provider custody | Percentage per conversion | US money transmission via Stripe entities |\n| [BVNK](https:\u002F\u002Fwww.bvnk.com) | On-chain, SEPA, Faster Payments, SWIFT | USDC, USDT, EUR, GBP, USD | Provider custody | Enterprise, volume tiers | EMI licenses in Europe, VASP registrations |\n| [Fireblocks](https:\u002F\u002Fwww.fireblocks.com) | On-chain (60+ networks) | Most major stablecoins | Self-custody via MPC | Platform fee, enterprise | Tooling for your own licenses |\n| [Crossmint](https:\u002F\u002Fwww.crossmint.com) | On-chain, cards for on-ramp | USDC and others | Managed wallets | Per-transaction | Onboarding and screening built in |\n| [Zero Hash](https:\u002F\u002Fzerohash.com) | On-chain, ACH, wire | USDC and others, USD | Provider custody | Enterprise quotes | US MTLs, broker-dealer adjacent |\n| [Conduit](https:\u002F\u002Fconduitpay.com) | Pix, SPEI, Interac, mobile money, on-chain | USDC, USDT to LatAm, Africa, Asia locals | Provider custody (Fireblocks-based) | Volume tiers, per-corridor on quote | Provider-run compliance |\n| [Sphere](https:\u002F\u002Fspherepay.co) | ACH, wire, SEPA, Pix, on-chain | USDC, USDT, EURC to USD, EUR, BRL | Provider custody | Per-transaction | KYC, KYB, sanctions in the API |\n| [Borderless](https:\u002F\u002Fborderless.xyz) | Local rails via partner institutions | Many fiat currencies via partner network | Varies by partner | Enterprise | Locally licensed partner institutions |\n\nRails, supported currencies, and fees change often. Treat the table as a map of each provider's center of gravity and confirm current details on their sites.\n\n## Where does each provider fit best?\n\n**BlindPay** is a payout and collection network: a business sends USDC or USDT and the receiver gets local currency over [Pix, SPEI, ACH, or wire](\u002Fglobal-payments), with KYC, KYB, sanctions screening, and travel rule compliance handled by the API. Cross-border wires run as SWIFT payments and collections on behalf of (POBO\u002FCOBO), with UETR tracking and MT103 confirmations for every transfer. Depth is strongest in the Americas corridors, such as [USDC to BRL](\u002Fusdc-to-brl), and [virtual accounts](\u002Fvirtual-accounts) cover the reverse direction, converting incoming bank transfers into stablecoins. BlindPay is not a card acquirer and not a consumer wallet; if you need merchant card acceptance or issuer-level USDC access, pair it with one of the providers below.\n\n**Circle** is the issuer of USDC. If you want mint-and-redeem access at issuer level, or your product is built around holding USDC reserves, Circle is the anchor integration. It is infrastructure for the dollar leg, not a payout network for local currencies.\n\n> USDC has become the largest regulated digital dollar in the world, with 108% year-over-year circulation growth.\n>\n> Jeremy Allaire, Co-Founder and CEO, Circle, in the [2026 Internet Financial System Report](https:\u002F\u002Fwww.circle.com\u002Freports\u002Finternet-financial-system\u002Ffounders-letter)\n\n**Bridge, a Stripe company**, is a stablecoin orchestration API: issuance, conversion, and virtual accounts, tightly integrated with the Stripe ecosystem since the acquisition. A strong default if you already run on Stripe and want stablecoin flows next to card flows.\n\n**BVNK** targets high-volume merchants and PSPs, with European licensing depth (EMI) and strong EUR and GBP rails. It fits businesses collecting large stablecoin volumes and settling into European bank accounts.\n\n**Fireblocks** is custody and wallet infrastructure, not a payments company. Institutions that must self-custody with MPC and route across many chains choose it, then layer payment logic on top themselves.\n\n**Crossmint** comes from the wallet and NFT side and fits consumer-facing apps that need embedded wallets plus stablecoin checkout, more than B2B treasury flows.\n\n**Zero Hash** is regulated B2B plumbing for US fintechs and brokerages that want crypto and stablecoin capabilities inside their own products, under Zero Hash's licenses.\n\n**Conduit** focuses on emerging-market corridors across Africa, Asia, and Latin America, with local rails such as Pix, SPEI, Interac, and mobile money behind one API, and custody built on Fireblocks. It fits businesses whose corridor map skews toward Africa and Asia alongside the Americas.\n\n**Sphere** is an on-ramp and off-ramp API converting between USD, EUR, BRL and USDC, USDT, EURC, with virtual accounts that turn fiat deposits into stablecoins. It fits fintechs that want ramp infrastructure with compliance embedded in the API.\n\n**Borderless** is an orchestration and liquidity network rather than a direct provider: one API routes payouts and collections through locally licensed partner institutions across a wide country set. It fits platforms that want breadth of coverage through partners and accept that capabilities vary by corridor.\n\n## Which blockchain networks should a stablecoin API support?\n\nFor payments, the network choice matters less than newcomers expect, because the provider abstracts it, but three things are worth checking. Cost and speed: modern networks such as Base, Polygon, and Solana settle in seconds for cents, while Ethereum mainnet remains the expensive, maximally liquid anchor. Counterparty compatibility: if your customers or partners already hold USDC on a specific chain, receiving natively there avoids bridge risk entirely. And native issuance: prefer stablecoins issued natively on a network over bridged versions, since a natively issued USDC is a direct claim on the issuer's reserves. A good API supports several networks behind one endpoint and lets the business think in dollars, not chains.\n\n## Which questions should you ask before choosing?\n\n- Which direction does your money move: pay-in, payout, or both? Payout networks and merchant gateways are different products, as covered in [how to choose a stablecoin payment provider](\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026).\n- Which corridors matter? A provider with deep US rails may have nothing in Brazil or Mexico. Check [coverage](\u002Fdocs\u002Fkb\u002Fsupported-countries) country by country.\n- Who holds the funds? Provider custody simplifies integration; self-custody reduces counterparty risk but moves obligations to you.\n- Whose license do you operate under? Most businesses want the provider's licenses to cover the flow. See the [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) for how MiCA, the GENIUS Act, and Brazil's VASP rules split those obligations.\n- What is the all-in cost? Compare the delivered amount after FX and fees, not the headline fee.\n\n## How do you compare pricing across stablecoin APIs?\n\nPublished pricing rarely tells the whole story, so run the same test against every shortlisted provider: quote a fixed amount, say 1,000 USDC to Brazilian reais, and record the amount delivered to the recipient's bank account. That single number folds together the provider fee, the FX spread, and any hidden minimums.\n\nThree patterns to watch. First, percentage fees compound with spread: a provider advertising 0.5% can deliver less than one advertising 1% if its FX rate sits further from mid-market. Second, flat fees dominate at small ticket sizes and vanish at large ones, so test at your real average payment size. Third, some providers price pay-in and payout differently; if you run both directions, quote both. Live corridor pages like [USDC to BRL](\u002Fusdc-to-brl) and [USDT to BRL](\u002Fusdt-to-brl) show this delivered-amount math with current rates, and BlindPay's fee schedule is published on the [pricing page](\u002Fpricing).\n\n## Where do these options fall short?\n\nNo provider on this list covers everything. Issuer platforms do not deliver local currency in emerging markets. Payout networks do not give you issuer-level mint and redeem. Custody platforms leave licensing to you. Most published pricing is incomplete, and FX spreads are usually only visible at quote time. And every provider gates activity behind KYB review, so onboarding time, not engineering, is the usual bottleneck. If your volumes are small and purely domestic in the US, traditional rails may still be cheaper than any stablecoin route.\n\n## When is BlindPay the right choice?\n\nIf the job is \"we hold digital dollars and need people paid in their local currency, compliantly, through one API\", that is the exact problem [BlindPay](\u002Fglobal-payments) is built for. Stablecoin in, Pix, SPEI, ACH, or SWIFT out (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), with a quoted FX rate before you commit, published [pricing](\u002Fpricing), and compliance checks run before money moves. Teams usually [talk to us](\u002Fcontact) with one corridor and expand from there.\n\n## Methodology and sources\n\nProvider capabilities 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), and BlindPay's own documentation. Supply and volume figures from public dashboards such as [DeFiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins). Rail descriptions from operator pages, including the [Banco Central do Brasil's Pix overview](https:\u002F\u002Fwww.bcb.gov.br\u002Fen\u002Ffinancialstability\u002Fpix_en).\n\n*This article is general information, not legal, tax, or financial advice.*\n",{"title":1255,"description":1769},"resources\u002Fmore\u002Fbest-stablecoin-apis-2026","2026-09-01","AuohrUNH3RVuW_Vx4TT21OIBaflMwX-e1Sqko1RyJ44",{"id":1790,"title":1791,"authors":6,"body":1792,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":2128,"description":2129,"extension":536,"faq":2130,"howto":6,"isBlog":553,"isChangelog":553,"meta":2146,"navigation":556,"path":2147,"pillar":553,"products":6,"rawbody":2148,"role":6,"seo":2149,"seoTitle":2150,"stem":2151,"thumbnail":6,"updated":2152,"__hash__":2153},"content\u002Fresources\u002Fmore\u002Fcrypto-debit-card-vs-stablecoin-card-for-business.md","Crypto debit card vs. stablecoin card for business: custody, accounting, tax, and controls compared",{"type":8,"value":1793,"toc":2117},[1794,1799,1805,1808,1815,1819,1822,1825,1840,1843,1847,1952,1956,1959,1962,1965,1968,1972,1975,1978,1982,1985,1991,1997,2000,2017,2021,2024,2044,2047,2051,2054,2067,2071,2077,2082,2088,2092,2113],[11,1795,1796],{},[1210,1797,1798],{},"Reading time: about 6 minutes.",[11,1800,1801,1804],{},[150,1802,1803],{},"Summary:"," For a business, the difference between a crypto debit card and a stablecoin card is what gets sold at checkout. A crypto debit card sells a volatile asset like bitcoin or ether at the moment of purchase. A stablecoin card spends a dollar-pegged token like USDC, so the amount leaving the balance matches the invoice and budgets stay in dollars.",[11,1806,1807],{},"For a consumer, the choice between the two is mostly about taste. For a company, it touches budgeting, the general ledger, the tax return, and the audit. This guide compares them on the questions a finance team actually asks.",[11,1809,1810,1811,329],{},"If you are new to the category, start with ",[133,1812,1814],{"href":1813},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing","what stablecoin card issuing is",[18,1816,1818],{"id":1817},"why-does-the-difference-matter-more-for-a-company","Why does the difference matter more for a company?",[11,1820,1821],{},"A consumer who spends bitcoin on a card makes one decision: \"I'm fine selling some bitcoin.\" A company makes that decision on every card, every employee, every day, and then has to account for it.",[11,1823,1824],{},"Picture a USD 12,000 monthly software budget spread across 20 employee cards.",[144,1826,1827,1834],{},[147,1828,1829,1830,1833],{},"On a ",[150,1831,1832],{},"crypto debit card"," funded with ether, the ether needed to cover that budget can swing by thousands of dollars in a month. Each purchase is a sale at a different price, with its own cost basis.",[147,1835,1829,1836,1839],{},[150,1837,1838],{},"stablecoin card"," funded with USDC, the budget is USD 12,000 plus fees. Each purchase is a dollar-denominated expense.",[11,1841,1842],{},"That one property, a stable unit, is why corporate programs are built on stablecoins and consumer programs still offer both.",[18,1844,1846],{"id":1845},"crypto-debit-card-vs-stablecoin-card-side-by-side","Crypto debit card vs. stablecoin card: side-by-side",[23,1848,1849,1862],{},[26,1850,1851],{},[29,1852,1853,1856,1859],{},[32,1854,1855],{},"Dimension",[32,1857,1858],{},"Crypto debit card",[32,1860,1861],{},"Stablecoin card",[42,1863,1864,1875,1886,1897,1908,1919,1930,1941],{},[29,1865,1866,1869,1872],{},[47,1867,1868],{},"Asset spent",[47,1870,1871],{},"Bitcoin, ether, or other volatile tokens",[47,1873,1874],{},"USDC, USDT, or another fiat-pegged stablecoin",[29,1876,1877,1880,1883],{},[47,1878,1879],{},"Budget predictability",[47,1881,1882],{},"Low; required balance moves with price",[47,1884,1885],{},"High; USD 1 of balance covers USD 1 of spend",[29,1887,1888,1891,1894],{},[47,1889,1890],{},"Tax event per swipe (US)",[47,1892,1893],{},"Sale of property with a real gain or loss",[47,1895,1896],{},"Disposal with a gain or loss usually near zero",[29,1898,1899,1902,1905],{},[47,1900,1901],{},"Accounting entries per purchase",[47,1903,1904],{},"Expense, plus a realized gain or loss, plus a basis lot update",[47,1906,1907],{},"Expense, plus a near-zero conversion line",[29,1909,1910,1913,1916],{},[47,1911,1912],{},"Custody",[47,1914,1915],{},"Usually the exchange that issues the card",[47,1917,1918],{},"Program wallet or self-custody with a spending allowance",[29,1920,1921,1924,1927],{},[47,1922,1923],{},"Multi-user controls",[47,1925,1926],{},"Rare; most are consumer products",[47,1928,1929],{},"Standard on corporate programs: per-card limits, merchant category rules",[29,1931,1932,1935,1938],{},[47,1933,1934],{},"Expense tooling",[47,1936,1937],{},"Monthly statement",[47,1939,1940],{},"Per-transaction data, receipts, accounting exports",[29,1942,1943,1946,1949],{},[47,1944,1945],{},"Who typically issues",[47,1947,1948],{},"Crypto exchanges",[47,1950,1951],{},"Card issuing platforms and corporate card providers",[18,1953,1955],{"id":1954},"how-does-tax-treatment-differ","How does tax treatment differ?",[11,1957,1958],{},"In the US, the IRS treats digital assets as property. Spending one on a card is a disposal, so the company recognizes a gain or loss equal to the difference between the purchase price and its cost basis in the tokens it spent.",[11,1960,1961],{},"With bitcoin or ether that difference is real. A company that bought ether at USD 2,000 and spends it on a card when it trades at USD 3,000 has a taxable gain on every purchase, even if the purchase itself is a USD 40 lunch. A card with hundreds of transactions a month turns into hundreds of lots to track.",[11,1963,1964],{},"With a dollar stablecoin the same rule applies, but USDC bought at USD 1.00 and spent at USD 1.00 produces a gain of roughly zero. Tracking is still required. The numbers just stop mattering.",[11,1966,1967],{},"Other countries tax digital asset disposals on their own rules. Check with an adviser before funding a card program in a new entity.",[18,1969,1971],{"id":1970},"how-does-the-accounting-differ","How does the accounting differ?",[11,1973,1974],{},"Under US GAAP, ASU 2023-08 requires in-scope crypto assets such as bitcoin and ether to be measured at fair value, with changes flowing through net income each period. A company spending ether on cards is running its expense program through a fair-value line.",[11,1976,1977],{},"Fully reserved stablecoins are often treated differently, because they give the holder a claim on the issuer rather than being a standalone crypto asset, and many companies account for them closer to a financial asset. Where your stablecoins land is a question for your auditor, but the practical result is the same: a stablecoin card produces expense lines your controller recognizes, and a crypto card produces expense lines plus investment activity.",[18,1979,1981],{"id":1980},"who-holds-the-money","Who holds the money?",[11,1983,1984],{},"This is the question most people skip, and the one that matters most after 2022.",[11,1986,1987,1990],{},[150,1988,1989],{},"Exchange-issued crypto cards"," usually spend from the exchange account. The company's balance is a claim on the exchange. If the exchange fails, the card stops working and the balance joins the bankruptcy estate.",[11,1992,1993,1996],{},[150,1994,1995],{},"Stablecoin card programs"," vary. Some hold the stablecoins in a custodial program wallet. Others let the company keep funds in its own wallet and grant the program a spending allowance through a smart contract, so the program can pull only what each purchase needs. The second model keeps treasury under the company's keys.",[11,1998,1999],{},"Two more questions belong on the list:",[144,2001,2002,2011],{},[147,2003,2004,2007,2008,2010],{},[150,2005,2006],{},"Which stablecoin?"," Tokens from licensed issuers, such as those operating under the US GENIUS Act or the EU's MiCA, hold 1:1 reserves and publish disclosures. The ",[133,2009,1664],{"href":1663}," lists where each regime stands.",[147,2012,2013,2016],{},[150,2014,2015],{},"Who is the sponsor bank?"," Every Visa or Mastercard program has one. If the provider cannot name it, walk away.",[18,2018,2020],{"id":2019},"what-spend-controls-should-a-business-card-have","What spend controls should a business card have?",[11,2022,2023],{},"These are card-program features, not stablecoin features, but consumer crypto cards rarely have them:",[144,2025,2026,2029,2032,2035,2038,2041],{},[147,2027,2028],{},"Per-card and per-employee spending limits, daily and monthly",[147,2030,2031],{},"Merchant category code (MCC) allow and block lists",[147,2033,2034],{},"Single-use and vendor-locked virtual cards",[147,2036,2037],{},"Instant freeze and reissue from an API or dashboard",[147,2039,2040],{},"Real-time transaction data with receipt capture",[147,2042,2043],{},"Exports to the accounting system",[11,2045,2046],{},"If a program lacks most of these, it was built for consumers.",[18,2048,2050],{"id":2049},"when-is-a-card-the-wrong-tool","When is a card the wrong tool?",[11,2052,2053],{},"Cards pay merchants. They are a poor fit for paying people or suppliers who need money in a local bank account: a landlord in São Paulo who takes Pix, a supplier in Mexico City who invoices for SPEI, a contractor who pays rent in pesos.",[11,2055,2056,2057,2061,2062,2066],{},"For those payments, a direct local-currency payout is simpler and cheaper than a card plus a cash withdrawal. BlindPay converts USDC or USDT to local currency over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), with ",[133,2058,2060],{"href":2059},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","settlement windows published per rail",". The ",[133,2063,2065],{"href":2064},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","cross-border virtual card guide"," compares both options for contractor payouts.",[18,2068,2070],{"id":2069},"how-to-choose","How to choose",[11,2072,2073,2074,2076],{},"Use a ",[150,2075,1838],{}," if the company holds or receives digital dollars and wants to spend them on software, ads, travel, or team expenses with normal controls and normal books.",[11,2078,2073,2079,2081],{},[150,2080,1832],{}," only if the company deliberately holds bitcoin or ether as a treasury asset, accepts that each swipe is a sale, and has a tax process for lot tracking.",[11,2083,2073,2084,2087],{},[150,2085,2086],{},"local bank payout"," when the recipient is a person or supplier, not a merchant.",[18,2089,2091],{"id":2090},"what-to-read-next","What to read next",[11,2093,2094,2095,2098,2099,2103,2104,2108,2109,329],{},"Next in this series: ",[133,2096,2097],{"href":2064},"stablecoin-funded virtual cards for cross-border payouts",", then ",[133,2100,2102],{"href":2101},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america","stablecoin cards in Latin America",", the ",[133,2105,2107],{"href":2106},"\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","developer's guide",", and the ",[133,2110,2112],{"href":2111},"\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance","compliance guide",[11,2114,2115],{},[1210,2116,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":2118},[2119,2120,2121,2122,2123,2124,2125,2126,2127],{"id":1817,"depth":520,"text":1818},{"id":1845,"depth":520,"text":1846},{"id":1954,"depth":520,"text":1955},{"id":1970,"depth":520,"text":1971},{"id":1980,"depth":520,"text":1981},{"id":2019,"depth":520,"text":2020},{"id":2049,"depth":520,"text":2050},{"id":2069,"depth":520,"text":2070},{"id":2090,"depth":520,"text":2091},"2026-09-08","Why a company should treat crypto debit cards and stablecoin cards differently: budget predictability, custody risk, per-swipe tax events, accounting, and spend controls.",[2131,2134,2137,2140,2143],{"q":2132,"a":2133},"Is a crypto debit card the same as a stablecoin card?","No. A crypto debit card sells a volatile asset such as bitcoin or ether at the moment of purchase, while a stablecoin card spends a token pegged 1:1 to a currency, usually the US dollar. Both run on Visa or Mastercard and look the same at checkout, but the stablecoin card's balance does not move with the market.",{"q":2135,"a":2136},"Can a business get a crypto debit card?","Most crypto debit cards are consumer products issued by exchanges to individual account holders, with no multi-user controls or expense reporting. Businesses that want to spend digital dollars usually use a corporate card program funded from a stablecoin treasury instead, which adds per-card limits, merchant category controls, and accounting exports.",{"q":2138,"a":2139},"Is spending USDC on a card a taxable event?","In the US, the IRS treats digital assets, including stablecoins, as property, so spending USDC is technically a disposal. Because USDC is designed to hold a value of one dollar, the gain or loss on each purchase is usually close to zero, unlike bitcoin or ether, where every swipe can realize a real gain or loss. Confirm treatment for your entity and jurisdiction with a tax adviser.",{"q":2141,"a":2142},"Which is better for company expenses, a crypto card or a stablecoin card?","For company expenses, a stablecoin card is almost always the better fit because the balance needed for a purchase matches the invoice and budgets stay in dollars. A crypto debit card makes sense only when the company deliberately holds volatile assets and accepts that each purchase is also a sale of those assets.",{"q":2144,"a":2145},"Are stablecoin cards safe for businesses?","The card leg carries the same protections as any Visa or Mastercard program, including network dispute rights. The risks sit elsewhere: who holds the stablecoins backing the card, whether the stablecoin comes from a regulated issuer, and whether the program's sponsor bank and conversion partners are licensed. A business should ask the provider for the custody model, the sponsor bank, and the stablecoin issuer before funding a program.",{"author":555},"\u002Fresources\u002Fmore\u002Fcrypto-debit-card-vs-stablecoin-card-for-business","---\ntitle: \"Crypto debit card vs. stablecoin card for business: custody, accounting, tax, and controls compared\"\nseoTitle: \"Crypto debit card vs. stablecoin card for business\"\ndescription: \"Why a company should treat crypto debit cards and stablecoin cards differently: budget predictability, custody risk, per-swipe tax events, accounting, and spend controls.\"\ndate: \"2026-09-08\"\nupdated: \"2026-09-21\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is a crypto debit card the same as a stablecoin card?\"\n    a: \"No. A crypto debit card sells a volatile asset such as bitcoin or ether at the moment of purchase, while a stablecoin card spends a token pegged 1:1 to a currency, usually the US dollar. Both run on Visa or Mastercard and look the same at checkout, but the stablecoin card's balance does not move with the market.\"\n  - q: \"Can a business get a crypto debit card?\"\n    a: \"Most crypto debit cards are consumer products issued by exchanges to individual account holders, with no multi-user controls or expense reporting. Businesses that want to spend digital dollars usually use a corporate card program funded from a stablecoin treasury instead, which adds per-card limits, merchant category controls, and accounting exports.\"\n  - q: \"Is spending USDC on a card a taxable event?\"\n    a: \"In the US, the IRS treats digital assets, including stablecoins, as property, so spending USDC is technically a disposal. Because USDC is designed to hold a value of one dollar, the gain or loss on each purchase is usually close to zero, unlike bitcoin or ether, where every swipe can realize a real gain or loss. Confirm treatment for your entity and jurisdiction with a tax adviser.\"\n  - q: \"Which is better for company expenses, a crypto card or a stablecoin card?\"\n    a: \"For company expenses, a stablecoin card is almost always the better fit because the balance needed for a purchase matches the invoice and budgets stay in dollars. A crypto debit card makes sense only when the company deliberately holds volatile assets and accepts that each purchase is also a sale of those assets.\"\n  - q: \"Are stablecoin cards safe for businesses?\"\n    a: \"The card leg carries the same protections as any Visa or Mastercard program, including network dispute rights. The risks sit elsewhere: who holds the stablecoins backing the card, whether the stablecoin comes from a regulated issuer, and whether the program's sponsor bank and conversion partners are licensed. A business should ask the provider for the custody model, the sponsor bank, and the stablecoin issuer before funding a program.\"\n---\n\n*Reading time: about 6 minutes.*\n\n**Summary:** For a business, the difference between a crypto debit card and a stablecoin card is what gets sold at checkout. A crypto debit card sells a volatile asset like bitcoin or ether at the moment of purchase. A stablecoin card spends a dollar-pegged token like USDC, so the amount leaving the balance matches the invoice and budgets stay in dollars.\n\nFor a consumer, the choice between the two is mostly about taste. For a company, it touches budgeting, the general ledger, the tax return, and the audit. This guide compares them on the questions a finance team actually asks.\n\nIf you are new to the category, start with [what stablecoin card issuing is](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing).\n\n## Why does the difference matter more for a company?\n\nA consumer who spends bitcoin on a card makes one decision: \"I'm fine selling some bitcoin.\" A company makes that decision on every card, every employee, every day, and then has to account for it.\n\nPicture a USD 12,000 monthly software budget spread across 20 employee cards.\n\n- On a **crypto debit card** funded with ether, the ether needed to cover that budget can swing by thousands of dollars in a month. Each purchase is a sale at a different price, with its own cost basis.\n- On a **stablecoin card** funded with USDC, the budget is USD 12,000 plus fees. Each purchase is a dollar-denominated expense.\n\nThat one property, a stable unit, is why corporate programs are built on stablecoins and consumer programs still offer both.\n\n## Crypto debit card vs. stablecoin card: side-by-side\n\n| Dimension | Crypto debit card | Stablecoin card |\n|---|---|---|\n| Asset spent | Bitcoin, ether, or other volatile tokens | USDC, USDT, or another fiat-pegged stablecoin |\n| Budget predictability | Low; required balance moves with price | High; USD 1 of balance covers USD 1 of spend |\n| Tax event per swipe (US) | Sale of property with a real gain or loss | Disposal with a gain or loss usually near zero |\n| Accounting entries per purchase | Expense, plus a realized gain or loss, plus a basis lot update | Expense, plus a near-zero conversion line |\n| Custody | Usually the exchange that issues the card | Program wallet or self-custody with a spending allowance |\n| Multi-user controls | Rare; most are consumer products | Standard on corporate programs: per-card limits, merchant category rules |\n| Expense tooling | Monthly statement | Per-transaction data, receipts, accounting exports |\n| Who typically issues | Crypto exchanges | Card issuing platforms and corporate card providers |\n\n## How does tax treatment differ?\n\nIn the US, the IRS treats digital assets as property. Spending one on a card is a disposal, so the company recognizes a gain or loss equal to the difference between the purchase price and its cost basis in the tokens it spent.\n\nWith bitcoin or ether that difference is real. A company that bought ether at USD 2,000 and spends it on a card when it trades at USD 3,000 has a taxable gain on every purchase, even if the purchase itself is a USD 40 lunch. A card with hundreds of transactions a month turns into hundreds of lots to track.\n\nWith a dollar stablecoin the same rule applies, but USDC bought at USD 1.00 and spent at USD 1.00 produces a gain of roughly zero. Tracking is still required. The numbers just stop mattering.\n\nOther countries tax digital asset disposals on their own rules. Check with an adviser before funding a card program in a new entity.\n\n## How does the accounting differ?\n\nUnder US GAAP, ASU 2023-08 requires in-scope crypto assets such as bitcoin and ether to be measured at fair value, with changes flowing through net income each period. A company spending ether on cards is running its expense program through a fair-value line.\n\nFully reserved stablecoins are often treated differently, because they give the holder a claim on the issuer rather than being a standalone crypto asset, and many companies account for them closer to a financial asset. Where your stablecoins land is a question for your auditor, but the practical result is the same: a stablecoin card produces expense lines your controller recognizes, and a crypto card produces expense lines plus investment activity.\n\n## Who holds the money?\n\nThis is the question most people skip, and the one that matters most after 2022.\n\n**Exchange-issued crypto cards** usually spend from the exchange account. The company's balance is a claim on the exchange. If the exchange fails, the card stops working and the balance joins the bankruptcy estate.\n\n**Stablecoin card programs** vary. Some hold the stablecoins in a custodial program wallet. Others let the company keep funds in its own wallet and grant the program a spending allowance through a smart contract, so the program can pull only what each purchase needs. The second model keeps treasury under the company's keys.\n\nTwo more questions belong on the list:\n\n- **Which stablecoin?** Tokens from licensed issuers, such as those operating under the US GENIUS Act or the EU's MiCA, hold 1:1 reserves and publish disclosures. The [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) lists where each regime stands.\n- **Who is the sponsor bank?** Every Visa or Mastercard program has one. If the provider cannot name it, walk away.\n\n## What spend controls should a business card have?\n\nThese are card-program features, not stablecoin features, but consumer crypto cards rarely have them:\n\n- Per-card and per-employee spending limits, daily and monthly\n- Merchant category code (MCC) allow and block lists\n- Single-use and vendor-locked virtual cards\n- Instant freeze and reissue from an API or dashboard\n- Real-time transaction data with receipt capture\n- Exports to the accounting system\n\nIf a program lacks most of these, it was built for consumers.\n\n## When is a card the wrong tool?\n\nCards pay merchants. They are a poor fit for paying people or suppliers who need money in a local bank account: a landlord in São Paulo who takes Pix, a supplier in Mexico City who invoices for SPEI, a contractor who pays rent in pesos.\n\nFor those payments, a direct local-currency payout is simpler and cheaper than a card plus a cash withdrawal. BlindPay converts USDC or USDT to local currency over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), with [settlement windows published per rail](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality). The [cross-border virtual card guide](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts) compares both options for contractor payouts.\n\n## How to choose\n\nUse a **stablecoin card** if the company holds or receives digital dollars and wants to spend them on software, ads, travel, or team expenses with normal controls and normal books.\n\nUse a **crypto debit card** only if the company deliberately holds bitcoin or ether as a treasury asset, accepts that each swipe is a sale, and has a tax process for lot tracking.\n\nUse a **local bank payout** when the recipient is a person or supplier, not a merchant.\n\n## What to read next\n\nNext in this series: [stablecoin-funded virtual cards for cross-border payouts](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts), then [stablecoin cards in Latin America](\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america), the [developer's guide](\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api), and the [compliance guide](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":1791,"description":2129},"Crypto debit card vs. stablecoin card for business","resources\u002Fmore\u002Fcrypto-debit-card-vs-stablecoin-card-for-business","2026-09-21","RZLUG3OJbvGZSOgc5fhwZvE73syEYuRWzvDhQw9KLm4",{"id":2155,"title":2156,"authors":6,"body":2157,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":2612,"description":2613,"extension":536,"faq":2614,"howto":6,"isBlog":553,"isChangelog":553,"meta":2630,"navigation":556,"path":2631,"pillar":553,"products":6,"rawbody":2632,"role":6,"seo":2633,"seoTitle":2634,"stem":2635,"thumbnail":6,"updated":6,"__hash__":2636},"content\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments.md","How merchants accept stablecoin payments: the complete 2026 guide",{"type":8,"value":2158,"toc":2601},[2159,2174,2177,2181,2196,2199,2225,2228,2232,2235,2279,2282,2286,2401,2404,2408,2411,2414,2448,2455,2459,2462,2474,2477,2481,2484,2487,2507,2512,2516,2519,2525,2531,2534,2538,2541,2579,2591,2595],[11,2160,2161,2162,2165,2166,2169,2170,2173],{},"To accept stablecoin payments, a merchant needs three things: a ",[150,2163,2164],{},"receiving method"," (a wallet address or a payments API that generates one), an ",[150,2167,2168],{},"off-ramp"," that converts USDC or USDT into local currency when you need fiat, and a ",[150,2171,2172],{},"settlement destination",", usually your business bank account. The customer sends dollar-pegged tokens, the transfer settles on-chain in seconds, and the funds land in your account in minutes over a local rail. No card network in the middle, no chargebacks, and no two to three day wait.",[11,2175,2176],{},"That's the short answer. The rest of this guide covers each step, the three ways to set it up, what it costs, and what a real merchant flow looks like.",[18,2178,2180],{"id":2179},"what-is-a-stablecoin-payment-in-plain-terms","What is a stablecoin payment, in plain terms?",[11,2182,2183,2184,2187,2188,2191,2192,2195],{},"A ",[150,2185,2186],{},"stablecoin"," is a digital token pegged to a currency, almost always the US dollar. One USDC is designed to be worth one dollar, backed by cash and short-term Treasuries held by the issuer. The two that matter for merchants are ",[150,2189,2190],{},"USDC"," (issued by Circle) and ",[150,2193,2194],{},"USDT"," (issued by Tether).",[11,2197,2198],{},"A stablecoin payment is a transfer of those tokens from the customer's wallet to yours, recorded on a public blockchain like Polygon, Base, Tron, or Stellar. A few terms you'll see:",[144,2200,2201,2207,2213,2219],{},[147,2202,2203,2206],{},[150,2204,2205],{},"Wallet:"," an address that holds stablecoins. Think of it as an account number on the blockchain.",[147,2208,2209,2212],{},[150,2210,2211],{},"Gas fee:"," the network fee paid to process a transfer. On the chains most payment providers use, it's a few cents or less.",[147,2214,2215,2218],{},[150,2216,2217],{},"On-ramp \u002F off-ramp:"," services that convert fiat into stablecoins (on-ramp) and stablecoins back into fiat (off-ramp).",[147,2220,2221,2224],{},[150,2222,2223],{},"Settlement:"," the moment the merchant has usable funds, in the currency they want, in the account they want.",[11,2226,2227],{},"Nothing about this requires the merchant to hold crypto as an investment. Stablecoins here are a payment rail, the same way ACH or Pix is a payment rail.",[18,2229,2231],{"id":2230},"how-does-a-stablecoin-payment-flow-from-customer-to-merchant","How does a stablecoin payment flow from customer to merchant?",[11,2233,2234],{},"Here is the full path, step by step:",[289,2236,2237,2243,2249,2255,2261,2267,2273],{},[147,2238,2239,2242],{},[150,2240,2241],{},"The customer chooses to pay in stablecoins."," At checkout or on an invoice, they select USDC or USDT and a network.",[147,2244,2245,2248],{},[150,2246,2247],{},"The merchant shows a payment address."," Either a fixed wallet address, or a unique address generated per order by a payments API so each payment reconciles to one invoice automatically.",[147,2250,2251,2254],{},[150,2252,2253],{},"The customer sends the transfer."," Their wallet or exchange account broadcasts it to the blockchain.",[147,2256,2257,2260],{},[150,2258,2259],{},"The network confirms it."," On Polygon, Base, or Stellar this takes seconds. Once confirmed, the payment is final.",[147,2262,2263,2266],{},[150,2264,2265],{},"The merchant's system gets notified."," A webhook or a block explorer check marks the order as paid.",[147,2268,2269,2272],{},[150,2270,2271],{},"The balance is converted, if needed."," An off-ramp sells the USDC or USDT for local currency at a quoted rate.",[147,2274,2275,2278],{},[150,2276,2277],{},"Funds settle to the bank account."," The local rail delivers the money: Pix in Brazil, SPEI in Mexico, PSE in Colombia, Transfers 3.0 in Argentina, ACH or RTP in the US, SEPA in Europe.",[11,2280,2281],{},"Steps 1 through 5 are about receiving. Steps 6 and 7 are about getting paid in something you can spend on payroll and rent. Most of the complexity, and most of the compliance work, lives in 6 and 7.",[18,2283,2285],{"id":2284},"what-are-the-three-ways-to-accept-stablecoin-payments","What are the three ways to accept stablecoin payments?",[23,2287,2288,2303],{},[26,2289,2290],{},[29,2291,2292,2294,2297,2300],{},[32,2293],{},[32,2295,2296],{},"Payments API or orchestration provider (like BlindPay)",[32,2298,2299],{},"Self-custody wallet",[32,2301,2302],{},"Card network with crypto rails",[42,2304,2305,2321,2337,2353,2369,2385],{},[29,2306,2307,2312,2315,2318],{},[47,2308,2309],{},[150,2310,2311],{},"How it works",[47,2313,2314],{},"A provider handles receiving, conversion, and payout to your bank through one API",[47,2316,2317],{},"You publish your own wallet address and manage the keys",[47,2319,2320],{},"The customer pays in crypto, the network settles to you in fiat like a card sale",[29,2322,2323,2328,2331,2334],{},[47,2324,2325],{},[150,2326,2327],{},"Speed to your bank",[47,2329,2330],{},"Minutes over local rails like Pix, SPEI, or RTP",[47,2332,2333],{},"Depends on the exchange you use to cash out, often one to three days",[47,2335,2336],{},"Card-style settlement, typically one to three business days",[29,2338,2339,2344,2347,2350],{},[47,2340,2341],{},[150,2342,2343],{},"Cost",[47,2345,2346],{},"Network fee plus an itemized FX spread and payout fee",[47,2348,2349],{},"Gas fees plus exchange fees and withdrawal fees",[47,2351,2352],{},"Card-style processing fees, often similar to regular card pricing",[29,2354,2355,2360,2363,2366],{},[47,2356,2357],{},[150,2358,2359],{},"Compliance burden",[47,2361,2362],{},"Provider runs KYC, KYB, and transaction screening",[47,2364,2365],{},"All on you: sanctions screening, record keeping, tax lots",[47,2367,2368],{},"Network and acquirer handle it",[29,2370,2371,2376,2379,2382],{},[47,2372,2373],{},[150,2374,2375],{},"Technical lift",[47,2377,2378],{},"One integration, webhooks for status",[47,2380,2381],{},"Low to start, high to reconcile at volume",[47,2383,2384],{},"Low, usually a checkout plugin",[29,2386,2387,2392,2395,2398],{},[47,2388,2389],{},[150,2390,2391],{},"Best for",[47,2393,2394],{},"Businesses that want fiat in local accounts, across many countries",[47,2396,2397],{},"Very low volume, crypto-native teams",[47,2399,2400],{},"Merchants who want no change to their card workflow",[11,2402,2403],{},"What's interesting here is that the first column is the only one that gets you both the speed of stablecoins and money in a local bank account. The self-custody route is fast on-chain and slow off-chain. The card route keeps the card-era settlement timeline.",[18,2405,2407],{"id":2406},"where-does-blindpay-fit","Where does BlindPay fit?",[11,2409,2410],{},"BlindPay sits in the first column, on the settlement side. It's not a card acquirer and not a checkout button. It's the layer that turns stablecoin balances into local currency and gets money into the right bank account, in 100+ countries and 80+ currencies, through one API.",[11,2412,2413],{},"In practice that looks like:",[144,2415,2416,2425,2436,2442],{},[147,2417,2418,2421,2422,329],{},[150,2419,2420],{},"Stablecoin to local fiat payouts."," Convert USDC or USDT and pay out over Pix, SPEI, PSE, Transfers 3.0, ACH, RTP, SEPA, or SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), at a rate quoted and locked before execution. See ",[133,2423,2424],{"href":951},"global payments",[147,2426,2427,2430,2431,2435],{},[150,2428,2429],{},"Virtual accounts for USD collection."," If your customers pay in dollars from a bank account instead of a wallet, ",[133,2432,2434],{"href":2433},"\u002Fblog\u002Fintroducing-virtual-accounts","Named Virtual Accounts"," give them a US account in your name with ACH, Wire, and RTP. Deposits auto-convert into stablecoins, then settle wherever you need.",[147,2437,2438,2441],{},[150,2439,2440],{},"No pre-funding."," You don't park capital in destination accounts before a payout clears.",[147,2443,2444,2447],{},[150,2445,2446],{},"Compliance in the flow."," KYC, KYB, sanctions screening, and on-chain monitoring run inside the same API.",[11,2449,2450,2451,329],{},"We wrote more about why the blockchain part should stay invisible to merchants in ",[133,2452,2454],{"href":2453},"\u002Fblog\u002Fstablecoin-for-the-ordinary","Stablecoin for the Ordinary",[18,2456,2458],{"id":2457},"which-stablecoins-should-a-merchant-accept","Which stablecoins should a merchant accept?",[11,2460,2461],{},"Start with USDC and USDT. Between them they cover the vast majority of stablecoin payment volume.",[144,2463,2464,2469],{},[147,2465,2466,2468],{},[150,2467,2190],{}," is the common choice in the US and Europe, with monthly reserve attestations published by Circle.",[147,2470,2471,2473],{},[150,2472,2194],{}," has the deepest liquidity in Latin America, Africa, and Asia. If your customers are in Brazil, Argentina, or Nigeria, a lot of them already hold it.",[11,2475,2476],{},"The network matters as much as the token. Accept on low-fee chains (Polygon, Base, Arbitrum, Stellar, Tron) so customers aren't paying a few dollars in gas on a $30 order. Tell customers exactly which network to use. A USDC transfer sent on the wrong chain is the most common support ticket in stablecoin acceptance.",[18,2478,2480],{"id":2479},"how-much-does-it-cost","How much does it cost?",[11,2482,2483],{},"A card payment typically costs the merchant 1.5 to 3.5 percent, plus another 1 to 2 percent on international cards, plus a currency conversion spread if the customer pays in another currency. Then there's the chargeback exposure.",[11,2485,2486],{},"A stablecoin payment breaks down differently:",[144,2488,2489,2495,2501],{},[147,2490,2491,2494],{},[150,2492,2493],{},"Network fee:"," cents or less on low-cost chains, usually paid by the sender.",[147,2496,2497,2500],{},[150,2498,2499],{},"FX spread:"," the difference between the mid-market rate and your conversion rate, when you off-ramp to local currency.",[147,2502,2503,2506],{},[150,2504,2505],{},"Payout fee:"," a flat or small fee to deliver funds over the local rail.",[11,2508,2509,2510,329],{},"The honest comparison depends on your corridor and volume. A merchant receiving USDC and paying out BRL over Pix will see a very different number than one receiving USDT and paying out EUR over SEPA. Ask for an itemized quote on your real amount before comparing anything. BlindPay splits the spread and the payout fee into separate numbers so you can see which one moved. Plan pricing is on the ",[133,2511,1688],{"href":967},[18,2513,2515],{"id":2514},"an-example-a-marketplace-paying-out-to-global-sellers","An example: a marketplace paying out to global sellers",[11,2517,2518],{},"Take a US marketplace with 2,000 sellers in Brazil and Mexico. Buyers pay by card. Sellers get paid out weekly.",[11,2520,2521,2524],{},[150,2522,2523],{},"Before:"," the marketplace sends international wires. Each one costs $25 to $50, takes two to five business days, and arrives short after intermediary bank deductions. Small sellers wait a week for $80 payouts that lose $30 on the way. Support spends Mondays answering \"where is my money.\"",[11,2526,2527,2530],{},[150,2528,2529],{},"After:"," the marketplace holds its payout float in USDC. Every Friday it requests a quote per seller and executes. BlindPay converts USDC to BRL and MXN at locked rates and pays out over Pix and SPEI. Sellers see funds in minutes, at the amount they were quoted. The marketplace reconciles through webhooks instead of bank statements.",[11,2532,2533],{},"Same buyers, same checkout. The only change is the settlement rail, and it's the part sellers actually feel.",[18,2535,2537],{"id":2536},"what-do-merchants-need-to-get-started","What do merchants need to get started?",[11,2539,2540],{},"A short checklist:",[289,2542,2543,2549,2555,2561,2567,2573],{},[147,2544,2545,2548],{},[150,2546,2547],{},"Decide what you're accepting."," USDC, USDT, or both, and on which networks.",[147,2550,2551,2554],{},[150,2552,2553],{},"Decide where the money should end up."," Stay in stablecoins, convert to USD, or convert to local currency in each market.",[147,2556,2557,2560],{},[150,2558,2559],{},"Pick your receiving setup."," Self-custody wallet, payments API, or card network, using the table above.",[147,2562,2563,2566],{},[150,2564,2565],{},"Complete business verification."," Any regulated provider will run KYB on your company. Have your incorporation documents and beneficial owner details ready.",[147,2568,2569,2572],{},[150,2570,2571],{},"Integrate and test in sandbox."," Wire up webhooks for payment status before going live.",[147,2574,2575,2578],{},[150,2576,2577],{},"Write a refund policy."," There are no chargebacks, so refunds are a transfer you send. Make the policy explicit.",[11,2580,2581,2582,2586,2587,329],{},"For the leadership view on how stablecoins, local rails, and virtual accounts combine, read ",[133,2583,2585],{"href":2584},"\u002Fblog\u002Forchestrating-payment-rails-leaders","Orchestrating Local Payments and Stablecoins",". For the API itself, start with the ",[133,2588,2590],{"href":2589},"\u002Fdocs\u002Fintroduction","BlindPay docs",[18,2592,2594],{"id":2593},"start-accepting-stablecoin-payments","Start accepting stablecoin payments",[11,2596,2597,2598,329],{},"The receiving part is easy. Getting paid in local currency, in minutes, compliantly, in every market you sell into is the part worth solving properly. If you want to see a live quote for your corridor, ",[133,2599,2600],{"href":1189},"talk to the BlindPay team",{"title":519,"searchDepth":520,"depth":520,"links":2602},[2603,2604,2605,2606,2607,2608,2609,2610,2611],{"id":2179,"depth":520,"text":2180},{"id":2230,"depth":520,"text":2231},{"id":2284,"depth":520,"text":2285},{"id":2406,"depth":520,"text":2407},{"id":2457,"depth":520,"text":2458},{"id":2479,"depth":520,"text":2480},{"id":2514,"depth":520,"text":2515},{"id":2536,"depth":520,"text":2537},{"id":2593,"depth":520,"text":2594},"2026-07-21","To accept stablecoin payments you need a receiving method, an off-ramp to local currency, and a settlement account. The full flow, costs, and options.",[2615,2618,2621,2624,2627],{"q":2616,"a":2617},"How do I accept stablecoin payments as a merchant?","You need three things: a way to receive the stablecoin (a wallet address or a payments API), an off-ramp that converts USDC or USDT into local currency when you need fiat, and a settlement destination such as your business bank account. Most merchants use a payments API for the second and third parts so they never manage private keys, gas fees, or conversion themselves.",{"q":2619,"a":2620},"Which stablecoins can merchants accept?","USDC and USDT cover almost all merchant stablecoin volume. Both are pegged one to one to the US dollar. USDC is issued by Circle and publishes monthly reserve attestations; USDT is issued by Tether and has the deepest liquidity in Latin America and Asia. BlindPay supports both on Polygon, Base, Arbitrum, Stellar, and Tron.",{"q":2622,"a":2623},"How fast do merchants get paid with stablecoins?","The stablecoin transfer itself settles on-chain in seconds to a few minutes. Converting to local currency and landing in a bank account depends on the local rail: minutes over Pix in Brazil or SPEI in Mexico, seconds over RTP in the US, and same day in most other corridors. Card networks typically take one to three business days.",{"q":2625,"a":2626},"Are there chargebacks on stablecoin payments?","No. A confirmed stablecoin transfer is final and cannot be pulled back by the payer or a card network. Refunds still happen, but the merchant sends them as a new transfer. That removes chargeback fraud and dispute fees, but it also means merchants need clear refund policies and good address checks before sending.",{"q":2628,"a":2629},"What does it cost to accept stablecoin payments compared to cards?","Card processing typically costs 1.5 to 3.5 percent per transaction, plus cross-border and currency conversion fees on international cards. Stablecoin acceptance costs a network fee of a few cents on low-cost chains plus an FX spread and payout fee when you convert to local currency. Ask any provider for an itemized quote on your real corridor before comparing.",{},"\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments","---\ntitle: \"How merchants accept stablecoin payments: the complete 2026 guide\"\nseoTitle: \"How merchants accept stablecoin payments (2026 guide)\"\ndescription: \"To accept stablecoin payments you need a receiving method, an off-ramp to local currency, and a settlement account. The full flow, costs, and options.\"\ndate: \"2026-07-21\"\ncategory: \"stablecoins\"\nfaq:\n  - q: \"How do I accept stablecoin payments as a merchant?\"\n    a: \"You need three things: a way to receive the stablecoin (a wallet address or a payments API), an off-ramp that converts USDC or USDT into local currency when you need fiat, and a settlement destination such as your business bank account. Most merchants use a payments API for the second and third parts so they never manage private keys, gas fees, or conversion themselves.\"\n  - q: \"Which stablecoins can merchants accept?\"\n    a: \"USDC and USDT cover almost all merchant stablecoin volume. Both are pegged one to one to the US dollar. USDC is issued by Circle and publishes monthly reserve attestations; USDT is issued by Tether and has the deepest liquidity in Latin America and Asia. BlindPay supports both on Polygon, Base, Arbitrum, Stellar, and Tron.\"\n  - q: \"How fast do merchants get paid with stablecoins?\"\n    a: \"The stablecoin transfer itself settles on-chain in seconds to a few minutes. Converting to local currency and landing in a bank account depends on the local rail: minutes over Pix in Brazil or SPEI in Mexico, seconds over RTP in the US, and same day in most other corridors. Card networks typically take one to three business days.\"\n  - q: \"Are there chargebacks on stablecoin payments?\"\n    a: \"No. A confirmed stablecoin transfer is final and cannot be pulled back by the payer or a card network. Refunds still happen, but the merchant sends them as a new transfer. That removes chargeback fraud and dispute fees, but it also means merchants need clear refund policies and good address checks before sending.\"\n  - q: \"What does it cost to accept stablecoin payments compared to cards?\"\n    a: \"Card processing typically costs 1.5 to 3.5 percent per transaction, plus cross-border and currency conversion fees on international cards. Stablecoin acceptance costs a network fee of a few cents on low-cost chains plus an FX spread and payout fee when you convert to local currency. Ask any provider for an itemized quote on your real corridor before comparing.\"\n---\n\nTo accept stablecoin payments, a merchant needs three things: a **receiving method** (a wallet address or a payments API that generates one), an **off-ramp** that converts USDC or USDT into local currency when you need fiat, and a **settlement destination**, usually your business bank account. The customer sends dollar-pegged tokens, the transfer settles on-chain in seconds, and the funds land in your account in minutes over a local rail. No card network in the middle, no chargebacks, and no two to three day wait.\n\nThat's the short answer. The rest of this guide covers each step, the three ways to set it up, what it costs, and what a real merchant flow looks like.\n\n## What is a stablecoin payment, in plain terms?\n\nA **stablecoin** is a digital token pegged to a currency, almost always the US dollar. One USDC is designed to be worth one dollar, backed by cash and short-term Treasuries held by the issuer. The two that matter for merchants are **USDC** (issued by Circle) and **USDT** (issued by Tether).\n\nA stablecoin payment is a transfer of those tokens from the customer's wallet to yours, recorded on a public blockchain like Polygon, Base, Tron, or Stellar. A few terms you'll see:\n\n- **Wallet:** an address that holds stablecoins. Think of it as an account number on the blockchain.\n- **Gas fee:** the network fee paid to process a transfer. On the chains most payment providers use, it's a few cents or less.\n- **On-ramp \u002F off-ramp:** services that convert fiat into stablecoins (on-ramp) and stablecoins back into fiat (off-ramp).\n- **Settlement:** the moment the merchant has usable funds, in the currency they want, in the account they want.\n\nNothing about this requires the merchant to hold crypto as an investment. Stablecoins here are a payment rail, the same way ACH or Pix is a payment rail.\n\n## How does a stablecoin payment flow from customer to merchant?\n\nHere is the full path, step by step:\n\n1. **The customer chooses to pay in stablecoins.** At checkout or on an invoice, they select USDC or USDT and a network.\n2. **The merchant shows a payment address.** Either a fixed wallet address, or a unique address generated per order by a payments API so each payment reconciles to one invoice automatically.\n3. **The customer sends the transfer.** Their wallet or exchange account broadcasts it to the blockchain.\n4. **The network confirms it.** On Polygon, Base, or Stellar this takes seconds. Once confirmed, the payment is final.\n5. **The merchant's system gets notified.** A webhook or a block explorer check marks the order as paid.\n6. **The balance is converted, if needed.** An off-ramp sells the USDC or USDT for local currency at a quoted rate.\n7. **Funds settle to the bank account.** The local rail delivers the money: Pix in Brazil, SPEI in Mexico, PSE in Colombia, Transfers 3.0 in Argentina, ACH or RTP in the US, SEPA in Europe.\n\nSteps 1 through 5 are about receiving. Steps 6 and 7 are about getting paid in something you can spend on payroll and rent. Most of the complexity, and most of the compliance work, lives in 6 and 7.\n\n## What are the three ways to accept stablecoin payments?\n\n| | Payments API or orchestration provider (like BlindPay) | Self-custody wallet | Card network with crypto rails |\n| --- | --- | --- | --- |\n| **How it works** | A provider handles receiving, conversion, and payout to your bank through one API | You publish your own wallet address and manage the keys | The customer pays in crypto, the network settles to you in fiat like a card sale |\n| **Speed to your bank** | Minutes over local rails like Pix, SPEI, or RTP | Depends on the exchange you use to cash out, often one to three days | Card-style settlement, typically one to three business days |\n| **Cost** | Network fee plus an itemized FX spread and payout fee | Gas fees plus exchange fees and withdrawal fees | Card-style processing fees, often similar to regular card pricing |\n| **Compliance burden** | Provider runs KYC, KYB, and transaction screening | All on you: sanctions screening, record keeping, tax lots | Network and acquirer handle it |\n| **Technical lift** | One integration, webhooks for status | Low to start, high to reconcile at volume | Low, usually a checkout plugin |\n| **Best for** | Businesses that want fiat in local accounts, across many countries | Very low volume, crypto-native teams | Merchants who want no change to their card workflow |\n\nWhat's interesting here is that the first column is the only one that gets you both the speed of stablecoins and money in a local bank account. The self-custody route is fast on-chain and slow off-chain. The card route keeps the card-era settlement timeline.\n\n## Where does BlindPay fit?\n\nBlindPay sits in the first column, on the settlement side. It's not a card acquirer and not a checkout button. It's the layer that turns stablecoin balances into local currency and gets money into the right bank account, in 100+ countries and 80+ currencies, through one API.\n\nIn practice that looks like:\n\n- **Stablecoin to local fiat payouts.** Convert USDC or USDT and pay out over Pix, SPEI, PSE, Transfers 3.0, ACH, RTP, SEPA, or SWIFT (POBO\u002FCOBO, with UETR tracking and MT103 confirmations), at a rate quoted and locked before execution. See [global payments](\u002Fglobal-payments).\n- **Virtual accounts for USD collection.** If your customers pay in dollars from a bank account instead of a wallet, [Named Virtual Accounts](\u002Fblog\u002Fintroducing-virtual-accounts) give them a US account in your name with ACH, Wire, and RTP. Deposits auto-convert into stablecoins, then settle wherever you need.\n- **No pre-funding.** You don't park capital in destination accounts before a payout clears.\n- **Compliance in the flow.** KYC, KYB, sanctions screening, and on-chain monitoring run inside the same API.\n\nWe wrote more about why the blockchain part should stay invisible to merchants in [Stablecoin for the Ordinary](\u002Fblog\u002Fstablecoin-for-the-ordinary).\n\n## Which stablecoins should a merchant accept?\n\nStart with USDC and USDT. Between them they cover the vast majority of stablecoin payment volume.\n\n- **USDC** is the common choice in the US and Europe, with monthly reserve attestations published by Circle.\n- **USDT** has the deepest liquidity in Latin America, Africa, and Asia. If your customers are in Brazil, Argentina, or Nigeria, a lot of them already hold it.\n\nThe network matters as much as the token. Accept on low-fee chains (Polygon, Base, Arbitrum, Stellar, Tron) so customers aren't paying a few dollars in gas on a $30 order. Tell customers exactly which network to use. A USDC transfer sent on the wrong chain is the most common support ticket in stablecoin acceptance.\n\n## How much does it cost?\n\nA card payment typically costs the merchant 1.5 to 3.5 percent, plus another 1 to 2 percent on international cards, plus a currency conversion spread if the customer pays in another currency. Then there's the chargeback exposure.\n\nA stablecoin payment breaks down differently:\n\n- **Network fee:** cents or less on low-cost chains, usually paid by the sender.\n- **FX spread:** the difference between the mid-market rate and your conversion rate, when you off-ramp to local currency.\n- **Payout fee:** a flat or small fee to deliver funds over the local rail.\n\nThe honest comparison depends on your corridor and volume. A merchant receiving USDC and paying out BRL over Pix will see a very different number than one receiving USDT and paying out EUR over SEPA. Ask for an itemized quote on your real amount before comparing anything. BlindPay splits the spread and the payout fee into separate numbers so you can see which one moved. Plan pricing is on the [pricing page](\u002Fpricing).\n\n## An example: a marketplace paying out to global sellers\n\nTake a US marketplace with 2,000 sellers in Brazil and Mexico. Buyers pay by card. Sellers get paid out weekly.\n\n**Before:** the marketplace sends international wires. Each one costs $25 to $50, takes two to five business days, and arrives short after intermediary bank deductions. Small sellers wait a week for $80 payouts that lose $30 on the way. Support spends Mondays answering \"where is my money.\"\n\n**After:** the marketplace holds its payout float in USDC. Every Friday it requests a quote per seller and executes. BlindPay converts USDC to BRL and MXN at locked rates and pays out over Pix and SPEI. Sellers see funds in minutes, at the amount they were quoted. The marketplace reconciles through webhooks instead of bank statements.\n\nSame buyers, same checkout. The only change is the settlement rail, and it's the part sellers actually feel.\n\n## What do merchants need to get started?\n\nA short checklist:\n\n1. **Decide what you're accepting.** USDC, USDT, or both, and on which networks.\n2. **Decide where the money should end up.** Stay in stablecoins, convert to USD, or convert to local currency in each market.\n3. **Pick your receiving setup.** Self-custody wallet, payments API, or card network, using the table above.\n4. **Complete business verification.** Any regulated provider will run KYB on your company. Have your incorporation documents and beneficial owner details ready.\n5. **Integrate and test in sandbox.** Wire up webhooks for payment status before going live.\n6. **Write a refund policy.** There are no chargebacks, so refunds are a transfer you send. Make the policy explicit.\n\nFor the leadership view on how stablecoins, local rails, and virtual accounts combine, read [Orchestrating Local Payments and Stablecoins](\u002Fblog\u002Forchestrating-payment-rails-leaders). For the API itself, start with the [BlindPay docs](\u002Fdocs\u002Fintroduction).\n\n## Start accepting stablecoin payments\n\nThe receiving part is easy. Getting paid in local currency, in minutes, compliantly, in every market you sell into is the part worth solving properly. If you want to see a live quote for your corridor, [talk to the BlindPay team](\u002Fcontact).\n",{"title":2156,"description":2613},"How merchants accept stablecoin payments (2026 guide)","resources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments","_uAlCs-1UX7w28m91I0m48_godCyzLRNSkw6-cgGI1g",{"id":2638,"title":2639,"authors":6,"body":2640,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":2864,"description":2865,"extension":536,"faq":2866,"howto":6,"isBlog":553,"isChangelog":553,"meta":2879,"navigation":556,"path":2880,"pillar":553,"products":6,"rawbody":2881,"role":6,"seo":2882,"seoTitle":2639,"stem":2883,"thumbnail":6,"updated":6,"__hash__":2884},"content\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts.md","How stablecoins fit into payment orchestration for cross-border payouts",{"type":8,"value":2641,"toc":2854},[2642,2650,2653,2657,2660,2666,2672,2678,2682,2688,2694,2700,2703,2707,2710,2713,2719,2725,2728,2732,2735,2738,2741,2752,2756,2766,2776,2782,2786,2789,2797,2804,2808,2811,2819,2826,2830,2833,2850],[11,2643,2644,2645,2649],{},"Stablecoins are a settlement rail inside a ",[133,2646,2648],{"href":2647},"\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration","payment orchestration"," strategy, not a replacement for banking. In a cross-border payout, the orchestration layer converts your dollars to USDC or USDT, moves that value on-chain in seconds, converts it to local currency at a quoted rate, and delivers it over the destination country's own rail, such as Pix in Brazil or SPEI in Mexico.",[11,2651,2652],{},"The recipient gets local currency in their bank account. They never see a wallet, a token, or a chain. That invisibility is the whole design.",[18,2654,2656],{"id":2655},"what-actually-hurts-about-cross-border-payouts","What actually hurts about cross-border payouts",[11,2658,2659],{},"Three problems, and stablecoin settlement addresses a different mechanism in each.",[11,2661,2662,2665],{},[150,2663,2664],{},"Pre-funding."," The only way to pay fast in a local market over traditional rails is to keep money there already. A local bank account in Brazil, funded in reais, drawn down as you pay. That capital is dead. It also carries FX risk, because you bought reais at one rate and will pay out over weeks at others.",[11,2667,2668,2671],{},[150,2669,2670],{},"Multi-day settlement."," A SWIFT wire is a message, not a movement. It passes through one or two correspondent banks, each updating its own ledger and taking its own fee. SWIFT gpi data says 92 percent reach the beneficiary bank within 24 hours, which is true and also not the number you care about. Reaching the bank is not being available to the recipient. Screening at the receiving bank adds a business day in most emerging-market corridors.",[11,2673,2674,2677],{},[150,2675,2676],{},"Opaque FX."," The receiving bank applies its own rate, typically 2 to 5 percent off mid-market for a corporate receiver. You find out what it was when the supplier emails to say the invoice came in short.",[18,2679,2681],{"id":2680},"how-does-stablecoin-settlement-change-each-one","How does stablecoin settlement change each one?",[11,2683,2684,2687],{},[150,2685,2686],{},"Pre-funding goes away."," Value moves at payout time. There is no local balance to fund in advance, so the float stays in your treasury instead of sitting in a Brazilian bank earning nothing.",[11,2689,2690,2693],{},[150,2691,2692],{},"Settlement collapses to minutes."," The on-chain leg is seconds. The local leg is whatever the destination rail does, and Pix and SPEI both run 24\u002F7. A payout sent at 11pm on a Saturday lands at 11pm on a Saturday.",[11,2695,2696,2699],{},[150,2697,2698],{},"FX becomes a quote."," You see the rate and the fee before you commit funds, with the spread itemized separately from the flat fee rather than blended into one number you cannot decompose.",[11,2701,2702],{},"What does not change: compliance, licensing, and the fact that the last mile is still a bank account. Anyone pitching stablecoins as a way around those is pitching a problem, not a product.",[18,2704,2706],{"id":2705},"why-does-no-pre-funding-change-your-working-capital","Why does \"no pre-funding\" change your working capital?",[11,2708,2709],{},"This is the part finance cares about and engineering usually skips.",[11,2711,2712],{},"Take a marketplace paying out $2M a month into Brazil, on weekly cycles. Same total volume, two operating models.",[11,2714,2715,2718],{},[150,2716,2717],{},"Before, with a pre-funded local account."," To pay reliably you hold roughly two weeks of payout volume as a buffer, so about $1M sits in a BRL account at all times. You bought those reais at some rate and you are exposed to every move until you spend them. Topping the account up means a wire, which means 1 to 5 days of lead time, which means the buffer has to be big enough to cover the lag. If you expand to Mexico and Colombia, you do it again per country. Three countries, three buffers, roughly $2M to $3M of working capital doing nothing but waiting.",[11,2720,2721,2724],{},[150,2722,2723],{},"After, with stablecoin settlement."," You fund each payout run when you run it. There is no per-country buffer, because the rail does not require a local balance to draw from. That $1M to $3M goes back into the business, and the FX exposure shrinks from weeks to the length of a transfer.",[11,2726,2727],{},"The second-order effect is the one that compounds: adding a country stops being a treasury project. No local banking relationship to open, no buffer to size, no additional currency position to manage. It becomes a routing rule.",[18,2729,2731],{"id":2730},"why-do-onoff-ramp-liquidity-and-live-quotes-decide-the-outcome","Why do on\u002Foff-ramp liquidity and live quotes decide the outcome?",[11,2733,2734],{},"Stablecoin settlement is only as good as the last mile, and the last mile is an off-ramp: someone in Brazil converting USDC to reais and pushing a Pix transfer. That conversion needs real liquidity at the moment you need it, in the size you need.",[11,2736,2737],{},"This is where providers diverge and where indicative pricing quietly costs you money. An indicative rate is an estimate. You commit funds, the off-ramp fills at whatever the book gives it, and the receiver gets less than the quote. On small payouts you never notice. On a $500,000 payroll run it is a conversation with your CFO.",[11,2739,2740],{},"A live quote is different. It is a rate the provider will honor for a defined window, so the amount in the quote is the amount that lands. The test is simple: does the API return the exact rate, fee, and receive amount before you commit, and is that number binding?",[11,2742,2743,2744,275,2748,329],{},"Ask the other liquidity questions too. What is the largest single payout the corridor supports. What happens at month-end when everyone pays at once. Is there a fallback when the primary off-ramp is thin. We cover the full set in ",[133,2745,2747],{"href":2746},"\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","on\u002Foff-ramp liquidity and live quotes",[133,2749,2751],{"href":2750},"\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","how to choose an on\u002Foff-ramp provider",[18,2753,2755],{"id":2754},"what-the-real-corridors-look-like","What the real corridors look like",[11,2757,2758,2761,2762,329],{},[150,2759,2760],{},"US to Brazil."," USD converts to USDC, settles on-chain, converts to BRL, delivers over Pix. Pix runs 24\u002F7 and credits in seconds. The payout requires the recipient's Pix key or full bank details plus a CPF or CNPJ, and the registered name has to match the payout name or the rail rejects it. That rejection is routine and should arrive as a typed webhook, not a support email. Route-level detail in the ",[133,2763,2765],{"href":2764},"\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026","USDC to BRL guide",[11,2767,2768,2771,2772,329],{},[150,2769,2770],{},"US to Mexico."," Same shape, delivering over SPEI to a CLABE account. SPEI settles in seconds during banking hours and continues to operate outside them. See the ",[133,2773,2775],{"href":2774},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN guide",[11,2777,2778,2779,329],{},"Both beat a wire on speed by days and on cost by a factor that grows with volume. Both still fail on bad receiver data, which is why receiver verification belongs before the on-chain transfer, not after. An on-chain transfer is final once confirmed. Your recall window is the pre-check. That is the honest tradeoff, and we wrote it up in ",[133,2780,2781],{"href":238},"are stablecoin payments reversible",[18,2783,2785],{"id":2784},"where-does-compliance-sit-in-a-stablecoin-payout","Where does compliance sit in a stablecoin payout?",[11,2787,2788],{},"Inside the flow, running before money moves.",[11,2790,2791,2792,2796],{},"KYC on individual receivers, ",[133,2793,2795],{"href":2794},"\u002Fresources\u002Fmore\u002Fwhat-is-kyb","KYB"," on business receivers, sanctions screening on both sides, ongoing transaction monitoring, and travel rule data exchange where the corridor requires it. On a wire these checks happen inside each bank in the chain, invisibly, and a hit freezes money that is already in flight. On a stablecoin payout through a licensed provider, a screening hit blocks the payout and returns an error while your funds are still yours.",[11,2798,2799,2800,2803],{},"The rules are corridor-specific and moving. Brazil licenses virtual asset service providers under Central Bank Resolutions 519 through 521, effective February 2026. The EU has MiCA. The US has the GENIUS Act with Treasury rulemaking in progress. The ",[133,2801,2802],{"href":1663},"regulation tracker"," is where we keep the current state.",[18,2805,2807],{"id":2806},"where-stablecoin-settlement-is-the-wrong-call","Where stablecoin settlement is the wrong call",[11,2809,2810],{},"It is not the right rail for everything, and orchestration only works if you are honest about that.",[11,2812,2813,2814,2818],{},"Large treasury transfers between two G10 banks: use SWIFT. The wire is fine, the counterparty expects it, and 24 hours costs nothing. Corridors where the local off-ramp has thin liquidity: the quote will show it, and a wire may simply be better. Receivers whose finance team requires an MT103 for their own audit: send the wire, ideally through the same API so you keep one reconciliation model. ",[133,2815,2817],{"href":2816},"\u002Fpobo-cobo-swift","SWIFT POBO and COBO"," exists for exactly that case.",[11,2820,2821,2822,329],{},"A good orchestration layer routes to stablecoins where they win and to a bank rail where they do not. Rail choice is a per-transaction decision, not an identity. That routing decision is the whole difference between an orchestration platform and ",[133,2823,2825],{"href":2824},"\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","a plain payment gateway",[18,2827,2829],{"id":2828},"what-to-do-next","What to do next",[11,2831,2832],{},"Pull your last quarter of cross-border payouts. For each corridor, write down three numbers: the working capital you hold locally to service it, the average time from instruction to funds landing, and the total cost including FX spread. Then get a live quote for the same volumes over a stablecoin route.",[11,2834,2835,2836,2839,2840,2844,2845,329],{},"If the working capital number is large and the cost number is above one percent, the stablecoin path is worth a sandbox week. ",[133,2837,2838],{"href":1204},"See coverage by country",", read the ",[133,2841,2843],{"href":2842},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","orchestration evaluation checklist",", or ",[133,2846,2849],{"href":2847,"rel":2848},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fintroduction",[137],"start in the sandbox",[11,2851,2852],{},[1210,2853,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":2855},[2856,2857,2858,2859,2860,2861,2862,2863],{"id":2655,"depth":520,"text":2656},{"id":2680,"depth":520,"text":2681},{"id":2705,"depth":520,"text":2706},{"id":2730,"depth":520,"text":2731},{"id":2754,"depth":520,"text":2755},{"id":2784,"depth":520,"text":2785},{"id":2806,"depth":520,"text":2807},{"id":2828,"depth":520,"text":2829},"2026-09-16","Stablecoins are a settlement rail inside an orchestration strategy, not a replacement for banking. What changes: pre-funding, settlement time, FX visibility, and last-mile delivery over Pix and SPEI.",[2867,2870,2873,2876],{"q":2868,"a":2869},"Is stablecoin settlement instant?","The on-chain leg settles in seconds to a couple of minutes depending on the network. The full payout is as fast as the local rail at the end of it: seconds over Pix or SPEI, same business day over ACH, longer where the local rail is slower.",{"q":2871,"a":2872},"How is compliance handled for stablecoin payouts?","The same way it is for any regulated payout, and it runs before money moves. KYC on individual receivers, KYB on businesses, sanctions screening on both sides, transaction monitoring, and travel rule data exchange where the corridor requires it.",{"q":2874,"a":2875},"Do recipients need a crypto wallet?","No. In a payout flow the recipient gives you a bank account and receives local currency in it. The stablecoin is the settlement layer in the middle and never touches the recipient's experience.",{"q":2877,"a":2878},"What happens if the stablecoin depegs mid-transfer?","Exposure is measured in minutes, not days, because the asset is held only for the duration of the transfer. The larger risk in practice is off-ramp liquidity at payout time, which is why a locked quote before you commit matters more than the peg itself.",{"author":555},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts","---\ntitle: \"How stablecoins fit into payment orchestration for cross-border payouts\"\nseoTitle: \"How stablecoins fit into payment orchestration for cross-border payouts\"\ndescription: \"Stablecoins are a settlement rail inside an orchestration strategy, not a replacement for banking. What changes: pre-funding, settlement time, FX visibility, and last-mile delivery over Pix and SPEI.\"\ndate: \"2026-09-16\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is stablecoin settlement instant?\"\n    a: \"The on-chain leg settles in seconds to a couple of minutes depending on the network. The full payout is as fast as the local rail at the end of it: seconds over Pix or SPEI, same business day over ACH, longer where the local rail is slower.\"\n  - q: \"How is compliance handled for stablecoin payouts?\"\n    a: \"The same way it is for any regulated payout, and it runs before money moves. KYC on individual receivers, KYB on businesses, sanctions screening on both sides, transaction monitoring, and travel rule data exchange where the corridor requires it.\"\n  - q: \"Do recipients need a crypto wallet?\"\n    a: \"No. In a payout flow the recipient gives you a bank account and receives local currency in it. The stablecoin is the settlement layer in the middle and never touches the recipient's experience.\"\n  - q: \"What happens if the stablecoin depegs mid-transfer?\"\n    a: \"Exposure is measured in minutes, not days, because the asset is held only for the duration of the transfer. The larger risk in practice is off-ramp liquidity at payout time, which is why a locked quote before you commit matters more than the peg itself.\"\n---\n\nStablecoins are a settlement rail inside a [payment orchestration](\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration) strategy, not a replacement for banking. In a cross-border payout, the orchestration layer converts your dollars to USDC or USDT, moves that value on-chain in seconds, converts it to local currency at a quoted rate, and delivers it over the destination country's own rail, such as Pix in Brazil or SPEI in Mexico.\n\nThe recipient gets local currency in their bank account. They never see a wallet, a token, or a chain. That invisibility is the whole design.\n\n## What actually hurts about cross-border payouts\n\nThree problems, and stablecoin settlement addresses a different mechanism in each.\n\n**Pre-funding.** The only way to pay fast in a local market over traditional rails is to keep money there already. A local bank account in Brazil, funded in reais, drawn down as you pay. That capital is dead. It also carries FX risk, because you bought reais at one rate and will pay out over weeks at others.\n\n**Multi-day settlement.** A SWIFT wire is a message, not a movement. It passes through one or two correspondent banks, each updating its own ledger and taking its own fee. SWIFT gpi data says 92 percent reach the beneficiary bank within 24 hours, which is true and also not the number you care about. Reaching the bank is not being available to the recipient. Screening at the receiving bank adds a business day in most emerging-market corridors.\n\n**Opaque FX.** The receiving bank applies its own rate, typically 2 to 5 percent off mid-market for a corporate receiver. You find out what it was when the supplier emails to say the invoice came in short.\n\n## How does stablecoin settlement change each one?\n\n**Pre-funding goes away.** Value moves at payout time. There is no local balance to fund in advance, so the float stays in your treasury instead of sitting in a Brazilian bank earning nothing.\n\n**Settlement collapses to minutes.** The on-chain leg is seconds. The local leg is whatever the destination rail does, and Pix and SPEI both run 24\u002F7. A payout sent at 11pm on a Saturday lands at 11pm on a Saturday.\n\n**FX becomes a quote.** You see the rate and the fee before you commit funds, with the spread itemized separately from the flat fee rather than blended into one number you cannot decompose.\n\nWhat does not change: compliance, licensing, and the fact that the last mile is still a bank account. Anyone pitching stablecoins as a way around those is pitching a problem, not a product.\n\n## Why does \"no pre-funding\" change your working capital?\n\nThis is the part finance cares about and engineering usually skips.\n\nTake a marketplace paying out $2M a month into Brazil, on weekly cycles. Same total volume, two operating models.\n\n**Before, with a pre-funded local account.** To pay reliably you hold roughly two weeks of payout volume as a buffer, so about $1M sits in a BRL account at all times. You bought those reais at some rate and you are exposed to every move until you spend them. Topping the account up means a wire, which means 1 to 5 days of lead time, which means the buffer has to be big enough to cover the lag. If you expand to Mexico and Colombia, you do it again per country. Three countries, three buffers, roughly $2M to $3M of working capital doing nothing but waiting.\n\n**After, with stablecoin settlement.** You fund each payout run when you run it. There is no per-country buffer, because the rail does not require a local balance to draw from. That $1M to $3M goes back into the business, and the FX exposure shrinks from weeks to the length of a transfer.\n\nThe second-order effect is the one that compounds: adding a country stops being a treasury project. No local banking relationship to open, no buffer to size, no additional currency position to manage. It becomes a routing rule.\n\n## Why do on\u002Foff-ramp liquidity and live quotes decide the outcome?\n\nStablecoin settlement is only as good as the last mile, and the last mile is an off-ramp: someone in Brazil converting USDC to reais and pushing a Pix transfer. That conversion needs real liquidity at the moment you need it, in the size you need.\n\nThis is where providers diverge and where indicative pricing quietly costs you money. An indicative rate is an estimate. You commit funds, the off-ramp fills at whatever the book gives it, and the receiver gets less than the quote. On small payouts you never notice. On a $500,000 payroll run it is a conversation with your CFO.\n\nA live quote is different. It is a rate the provider will honor for a defined window, so the amount in the quote is the amount that lands. The test is simple: does the API return the exact rate, fee, and receive amount before you commit, and is that number binding?\n\nAsk the other liquidity questions too. What is the largest single payout the corridor supports. What happens at month-end when everyone pays at once. Is there a fallback when the primary off-ramp is thin. We cover the full set in [on\u002Foff-ramp liquidity and live quotes](\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes) and [how to choose an on\u002Foff-ramp provider](\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider).\n\n## What the real corridors look like\n\n**US to Brazil.** USD converts to USDC, settles on-chain, converts to BRL, delivers over Pix. Pix runs 24\u002F7 and credits in seconds. The payout requires the recipient's Pix key or full bank details plus a CPF or CNPJ, and the registered name has to match the payout name or the rail rejects it. That rejection is routine and should arrive as a typed webhook, not a support email. Route-level detail in the [USDC to BRL guide](\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026).\n\n**US to Mexico.** Same shape, delivering over SPEI to a CLABE account. SPEI settles in seconds during banking hours and continues to operate outside them. See the [USDC to MXN guide](\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026).\n\nBoth beat a wire on speed by days and on cost by a factor that grows with volume. Both still fail on bad receiver data, which is why receiver verification belongs before the on-chain transfer, not after. An on-chain transfer is final once confirmed. Your recall window is the pre-check. That is the honest tradeoff, and we wrote it up in [are stablecoin payments reversible](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible).\n\n## Where does compliance sit in a stablecoin payout?\n\nInside the flow, running before money moves.\n\nKYC on individual receivers, [KYB](\u002Fresources\u002Fmore\u002Fwhat-is-kyb) on business receivers, sanctions screening on both sides, ongoing transaction monitoring, and travel rule data exchange where the corridor requires it. On a wire these checks happen inside each bank in the chain, invisibly, and a hit freezes money that is already in flight. On a stablecoin payout through a licensed provider, a screening hit blocks the payout and returns an error while your funds are still yours.\n\nThe rules are corridor-specific and moving. Brazil licenses virtual asset service providers under Central Bank Resolutions 519 through 521, effective February 2026. The EU has MiCA. The US has the GENIUS Act with Treasury rulemaking in progress. The [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) is where we keep the current state.\n\n## Where stablecoin settlement is the wrong call\n\nIt is not the right rail for everything, and orchestration only works if you are honest about that.\n\nLarge treasury transfers between two G10 banks: use SWIFT. The wire is fine, the counterparty expects it, and 24 hours costs nothing. Corridors where the local off-ramp has thin liquidity: the quote will show it, and a wire may simply be better. Receivers whose finance team requires an MT103 for their own audit: send the wire, ideally through the same API so you keep one reconciliation model. [SWIFT POBO and COBO](\u002Fpobo-cobo-swift) exists for exactly that case.\n\nA good orchestration layer routes to stablecoins where they win and to a bank rail where they do not. Rail choice is a per-transaction decision, not an identity. That routing decision is the whole difference between an orchestration platform and [a plain payment gateway](\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway).\n\n## What to do next\n\nPull your last quarter of cross-border payouts. For each corridor, write down three numbers: the working capital you hold locally to service it, the average time from instruction to funds landing, and the total cost including FX spread. Then get a live quote for the same volumes over a stablecoin route.\n\nIf the working capital number is large and the cost number is above one percent, the stablecoin path is worth a sandbox week. [See coverage by country](\u002Fdocs\u002Fkb\u002Fsupported-countries), read the [orchestration evaluation checklist](\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":2639,"description":2865},"resources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts","TyBcLlJ8nTOZmB_0ORkl7nPDbW9BDbljs4s8ZO_9AQA",{"id":2886,"title":2887,"authors":6,"body":2888,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":3520,"description":3521,"extension":536,"faq":3522,"howto":3538,"isBlog":553,"isChangelog":553,"meta":3559,"navigation":556,"path":3560,"pillar":553,"products":6,"rawbody":3561,"role":6,"seo":3562,"seoTitle":3563,"stem":3564,"thumbnail":6,"updated":6,"__hash__":3565},"content\u002Fresources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins.md","How to accept bank transfers and settle in stablecoins using virtual accounts",{"type":8,"value":2889,"toc":3509},[2890,2893,2896,2900,2914,2918,2921,2932,2936,2939,2942,3034,3042,3046,3049,3096,3187,3231,3234,3238,3241,3326,3329,3340,3349,3353,3356,3383,3394,3398,3404,3466,3469,3472,3474,3480,3482,3501,3505],[11,2891,2892],{},"To accept bank transfers and settle in stablecoins, give each customer a virtual account: a bank account number in their name that converts every incoming deposit into USDC or USDT and sends it on-chain to a linked wallet. The payer sends an ordinary ACH, wire, or SWIFT transfer. The provider handles the conversion. The customer ends up holding stablecoins.",[11,2894,2895],{},"No checkout page. No crypto on the payer's side.",[18,2897,2899],{"id":2898},"key-takeaways","Key takeaways",[144,2901,2902,2905,2908,2911],{},[147,2903,2904],{},"There are two ways to take a bank transfer and settle in stablecoins: standing virtual account details, or one-time payment instructions with a memo code.",[147,2906,2907],{},"Virtual accounts win for repeat payers, foreign senders, and anyone who forgets memo codes (everyone).",[147,2909,2910],{},"The wallet you link decides which stablecoins and chains you can settle in. Pick it before you create the account.",[147,2912,2913],{},"Most of the settlement time is the bank leg. The on-chain leg takes seconds to minutes.",[18,2915,2917],{"id":2916},"how-do-virtual-accounts-turn-bank-deposits-into-stablecoins","How do virtual accounts turn bank deposits into stablecoins?",[11,2919,2920],{},"A virtual account turns bank deposits into stablecoins by pairing a bank account number with a destination wallet. When a deposit lands on the account number, the provider records it, converts the dollars into a stablecoin, and sends the stablecoin to the wallet in an on-chain transaction.",[11,2922,2923,2924,2928,2929,329],{},"That's the on-ramp, reduced to one object. The deeper walkthrough of approval states and deposit handling is in ",[133,2925,2927],{"href":2926},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","stablecoin virtual accounts explained",", and what happens on the blockchain at each step is in ",[133,2930,2931],{"href":200},"what happens on-chain in a stablecoin payment",[18,2933,2935],{"id":2934},"virtual-account-or-payment-instructions-which-one-should-you-use","Virtual account or payment instructions: which one should you use?",[11,2937,2938],{},"Use a virtual account when the same payer sends money more than once or pays from abroad. Use one-time payment instructions when a payer sends a single transfer and you don't want to wait for account approval.",[11,2940,2941],{},"With one-time instructions, you create a quote for a specific payment, then show the payer a shared bank account plus a memo code they must include so the deposit can be matched. With a virtual account, the payer gets bank details in your customer's own name, and the account number does the matching.",[23,2943,2944,2956],{},[26,2945,2946],{},[29,2947,2948,2950,2953],{},[32,2949],{},[32,2951,2952],{},"Virtual account",[32,2954,2955],{},"One-time payment instructions",[42,2957,2958,2969,2980,2991,3002,3013,3024],{},[29,2959,2960,2963,2966],{},[47,2961,2962],{},"What the payer gets",[47,2964,2965],{},"Routing and account number in your customer's name",[47,2967,2968],{},"Shared bank details plus a memo code",[29,2970,2971,2974,2977],{},[47,2972,2973],{},"Reusable",[47,2975,2976],{},"Yes, same details every time",[47,2978,2979],{},"No, one set per payment",[29,2981,2982,2985,2988],{},[47,2983,2984],{},"How a deposit is matched",[47,2986,2987],{},"By the receiving account number",[47,2989,2990],{},"By the memo code the payer types",[29,2992,2993,2996,2999],{},[47,2994,2995],{},"Setup",[47,2997,2998],{},"Account review before first use",[47,3000,3001],{},"Available immediately",[29,3003,3004,3007,3010],{},[47,3005,3006],{},"International SWIFT",[47,3008,3009],{},"Yes, on account types that support it",[47,3011,3012],{},"Not at BlindPay: SWIFT deposits require a virtual account",[29,3014,3015,3018,3021],{},[47,3016,3017],{},"Failure mode",[47,3019,3020],{},"Account rejected or approval delayed",[47,3022,3023],{},"Memo missing or mistyped, deposit waits to be matched",[29,3025,3026,3028,3031],{},[47,3027,2391],{},[47,3029,3030],{},"Recurring payers, payroll funding, B2B, foreign clients",[47,3032,3033],{},"Occasional one-off deposits",[11,3035,3036,3037,3041],{},"At BlindPay, the two paths are connected. Once a customer has an approved virtual account, ACH and wire payins show that account's own details and the memo code is ignored (",[133,3038,3040],{"href":3039},"\u002Fdocs\u002Fpayins","payins","). RTP deposits are the exception: they always use the shared memo-code account, because no virtual account carries an RTP rail.",[18,3043,3045],{"id":3044},"what-does-the-end-to-end-flow-look-like","What does the end-to-end flow look like?",[11,3047,3048],{},"The flow has six steps, and only the last two involve money.",[289,3050,3051,3079,3090],{},[147,3052,3053,3056,3057,3060,3061,3064,3065,1718,3068,1718,3071,3074,3075,498],{},[150,3054,3055],{},"Onboard and verify the customer."," KYC for individuals, KYB for businesses. At BlindPay, the customer's ",[485,3058,3059],{},"kyc_status"," must be ",[485,3062,3063],{},"approved"," before you can request an account, and business customers need fields like ",[485,3066,3067],{},"account_purpose",[485,3069,3070],{},"source_of_wealth",[485,3072,3073],{},"business_industry"," (a NAICS code), and at least one owner filled in (",[133,3076,3078],{"href":3077},"\u002Fdocs\u002Fvirtual-accounts-create","create a virtual account",[147,3080,3081,3084,3085,3089],{},[150,3082,3083],{},"Link a settlement wallet."," Add the ",[133,3086,3088],{"href":3087},"\u002Fdocs\u002Fblockchain-wallets","blockchain wallet"," where the stablecoins will land. It must belong to the same customer.",[147,3091,3092,3095],{},[150,3093,3094],{},"Create the virtual account."," One API call, with the settlement token and the wallet:",[3097,3098,3102],"pre",{"className":3099,"code":3100,"language":3101,"meta":519,"style":519},"language-bash shiki shiki-themes github-light","curl --request POST \\\n  --url https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\u002Fre_000000000000\u002Fvirtual-accounts \\\n  --header 'Authorization: Bearer YOUR_API_KEY' \\\n  --header 'Content-Type: application\u002Fjson' \\\n  --data '{\n  \"banking_partner\": \"cfsb\",\n  \"token\": \"USDC\",\n  \"blockchain_wallet_id\": \"bw_000000000000\"\n}'\n","bash",[485,3103,3104,3124,3134,3144,3154,3163,3169,3175,3181],{"__ignoreMap":519},[3105,3106,3109,3113,3117,3121],"span",{"class":3107,"line":3108},"line",1,[3105,3110,3112],{"class":3111},"s7eDp","curl",[3105,3114,3116],{"class":3115},"sYu0t"," --request",[3105,3118,3120],{"class":3119},"sYBdl"," POST",[3105,3122,3123],{"class":3115}," \\\n",[3105,3125,3126,3129,3132],{"class":3107,"line":520},[3105,3127,3128],{"class":3115},"  --url",[3105,3130,3131],{"class":3119}," https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\u002Fre_000000000000\u002Fvirtual-accounts",[3105,3133,3123],{"class":3115},[3105,3135,3136,3139,3142],{"class":3107,"line":1220},[3105,3137,3138],{"class":3115},"  --header",[3105,3140,3141],{"class":3119}," 'Authorization: Bearer YOUR_API_KEY'",[3105,3143,3123],{"class":3115},[3105,3145,3147,3149,3152],{"class":3107,"line":3146},4,[3105,3148,3138],{"class":3115},[3105,3150,3151],{"class":3119}," 'Content-Type: application\u002Fjson'",[3105,3153,3123],{"class":3115},[3105,3155,3157,3160],{"class":3107,"line":3156},5,[3105,3158,3159],{"class":3115},"  --data",[3105,3161,3162],{"class":3119}," '{\n",[3105,3164,3166],{"class":3107,"line":3165},6,[3105,3167,3168],{"class":3119},"  \"banking_partner\": \"cfsb\",\n",[3105,3170,3172],{"class":3107,"line":3171},7,[3105,3173,3174],{"class":3119},"  \"token\": \"USDC\",\n",[3105,3176,3178],{"class":3107,"line":3177},8,[3105,3179,3180],{"class":3119},"  \"blockchain_wallet_id\": \"bw_000000000000\"\n",[3105,3182,3184],{"class":3107,"line":3183},9,[3105,3185,3186],{"class":3119},"}'\n",[289,3188,3189,3209,3218],{"start":3146},[147,3190,3191,3194,3195,3198,3199,3202,3203,1567,3205,3208],{},[150,3192,3193],{},"Wait for approval."," Production accounts move from ",[485,3196,3197],{},"pending_review"," (compliance) to ",[485,3200,3201],{},"verifying"," (bank) to ",[485,3204,3063],{},[485,3206,3207],{},"virtualAccount.complete"," fires with the routing and account numbers. Development accounts are approved instantly.",[147,3210,3211,3214,3215,329],{},[150,3212,3213],{},"Receive the deposit."," The payer sends ACH, wire, or SWIFT. Each deposit creates a payin and fires ",[485,3216,3217],{},"payin.new",[147,3219,3220,3223,3224,275,3227,3230],{},[150,3221,3222],{},"Settle to the wallet."," The deposit converts and the stablecoins go on-chain to the linked wallet. The payin reaches ",[485,3225,3226],{},"completed",[485,3228,3229],{},"payin.complete"," fires.",[11,3232,3233],{},"After step 4, nothing else needs an API call. Every future deposit repeats steps 5 and 6 on its own.",[18,3235,3237],{"id":3236},"which-design-decisions-do-you-need-to-make","Which design decisions do you need to make?",[11,3239,3240],{},"Six decisions shape a stablecoin collection flow. Most depend on the provider, so the table shows what to ask any provider next to how BlindPay answers.",[23,3242,3243,3255],{},[26,3244,3245],{},[29,3246,3247,3250,3253],{},[32,3248,3249],{},"Decision",[32,3251,3252],{},"What to ask any provider",[32,3254,952],{},[42,3256,3257,3267,3282,3293,3304,3315],{},[29,3258,3259,3261,3264],{},[47,3260,1912],{},[47,3262,3263],{},"Do stablecoins settle to a wallet I control, or one you hold?",[47,3265,3266],{},"Virtual accounts settle to an external blockchain wallet the customer controls",[29,3268,3269,3272,3275],{},[47,3270,3271],{},"Which stablecoin",[47,3273,3274],{},"USDC, USDT, or both? Can I switch later?",[47,3276,3277,3278,3281],{},"USDC or USDT, and ",[485,3279,3280],{},"token"," can be updated on an existing account",[29,3283,3284,3287,3290],{},[47,3285,3286],{},"Which chain",[47,3288,3289],{},"Which networks can receive settlement?",[47,3291,3292],{},"USDC on Ethereum, Polygon, Base, Arbitrum, Stellar, and Solana. USDT needs a wallet on Polygon, Ethereum, or Solana",[29,3294,3295,3298,3301],{},[47,3296,3297],{},"Fees",[47,3299,3300],{},"Monthly cost per account? Per-deposit fee? Where does it show up?",[47,3302,3303],{},"$1.50 per month per account. Per-deposit fees below $100.00 go to your invoice; at $100.00 or more they're deducted from the delivered stablecoin",[29,3305,3306,3309,3312],{},[47,3307,3308],{},"Minimum deposit",[47,3310,3311],{},"Are small deposits ignored or processed?",[47,3313,3314],{},"Every deposit is processed, including $0.01 micro-deposits, and at least $0.01 is always delivered",[29,3316,3317,3320,3323],{},[47,3318,3319],{},"Settlement time",[47,3321,3322],{},"How long for each rail, and what restarts the clock?",[47,3324,3325],{},"ACH and wire deposits can take up to 5 business days to arrive; the on-chain leg takes seconds to minutes",[11,3327,3328],{},"Two of these are worth a second look.",[11,3330,3331,3334,3335,3339],{},[150,3332,3333],{},"Custody."," Settling to a wallet your customer controls means the stablecoins stop being the provider's liability the moment they land. It also means your customer is responsible for that wallet's keys. ",[133,3336,3338],{"href":3337},"\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained","Non-custodial payments explained"," covers the trade-off in full.",[11,3341,3342,3345,3346,3348],{},[150,3343,3344],{},"Token and chain."," They're linked. At BlindPay, choosing USDT means the wallet must be on Polygon, Ethereum, or Solana. Stellar wallets receive USDC only, and need a USDC trustline before they can. If you're unsure which token, ",[133,3347,177],{"href":176}," compares them. For speed and low network fees, Solana is a common pick: BlindPay payins, payouts, and virtual accounts all run on it.",[18,3350,3352],{"id":3351},"what-does-compliance-look-like","What does compliance look like?",[11,3354,3355],{},"Compliance happens at three points: when the customer is onboarded, when the account is approved, and when each deposit arrives.",[144,3357,3358,3364,3374],{},[147,3359,3360,3363],{},[150,3361,3362],{},"Customer onboarding."," KYC or KYB, plus sanctions screening. The provider has to know who the account belongs to.",[147,3365,3366,3369,3370,498],{},[150,3367,3368],{},"Account approval."," Banks want to know what the account is for. At BlindPay that means the purpose of the account, source of funds, and source of wealth, backed by documents like recent bank statements or financial statements (",[133,3371,3373],{"href":3372},"\u002Fdocs\u002Fkb\u002Fvirtual-accounts","virtual account requirements",[147,3375,3376,3379,3380,3382],{},[150,3377,3378],{},"Each deposit."," A deposit can be held for review. At BlindPay, a payin in review shows ",[485,3381,487],{}," and resumes when cleared.",[11,3384,3385,3386,3390,3391,3393],{},"Two rules apply beyond the first deposit. First, the money has to belong to the customer the account was issued to. Collecting for your customer's own clients through their account is nesting, which BlindPay does not allow (",[133,3387,3389],{"href":3388},"\u002Fdocs\u002Fkb\u002Fnested-payments","nested payments","). Second, when stablecoins move between providers, travel rule obligations can require originator and beneficiary information to travel with the transfer. How that applies depends on the jurisdiction and the wallets involved, so ask your provider how they handle it. The ",[133,3392,1664],{"href":1663}," follows the rules by market.",[18,3395,3397],{"id":3396},"what-does-this-look-like-for-a-payroll-platform","What does this look like for a payroll platform?",[11,3399,3400,3403],{},[150,3401,3402],{},"Illustrative example."," A contractor payroll platform has three US client companies. Each client is onboarded as a BlindPay customer, passes KYB, and gets its own virtual account settling USDC to its own wallet on Solana.",[23,3405,3406,3422],{},[26,3407,3408],{},[29,3409,3410,3413,3416,3419],{},[32,3411,3412],{},"Client",[32,3414,3415],{},"Funds payroll by",[32,3417,3418],{},"Deposit",[32,3420,3421],{},"What lands",[42,3423,3424,3438,3452],{},[29,3425,3426,3429,3432,3435],{},[47,3427,3428],{},"Client A",[47,3430,3431],{},"Domestic wire, Monday morning",[47,3433,3434],{},"$48,000.00",[47,3436,3437],{},"USDC in Client A's wallet, minus the deposit fee",[29,3439,3440,3443,3446,3449],{},[47,3441,3442],{},"Client B",[47,3444,3445],{},"ACH, twice a month",[47,3447,3448],{},"$12,500.00 each",[47,3450,3451],{},"USDC in Client B's wallet after each ACH settles",[29,3453,3454,3457,3460,3463],{},[47,3455,3456],{},"Client C",[47,3458,3459],{},"ACH from a payroll provider that verifies with a $0.01 test",[47,3461,3462],{},"$0.01, then $9,000.00",[47,3464,3465],{},"Two payins: at least $0.01 of USDC, then the full deposit minus fees",[11,3467,3468],{},"Nobody types a memo code. Every deposit arrives already labeled by the account it hit. The platform then pays each client's contractors from that client's wallet, over local rails in each contractor's country. (Amounts are illustrative; fees depend on your plan.)",[11,3470,3471],{},"Notice Client C's penny. That's an account-verification micro-deposit, and it shows up as its own payin. Reconcile it, don't flag it.",[18,3473,2407],{"id":2406},[11,3475,3476,3479],{},[133,3477,3478],{"href":1067},"BlindPay virtual accounts"," give each customer a US bank account in their own name that receives ACH, wire, and SWIFT and settles automatically to USDC or USDT in the customer's wallet. The same API pays out over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) to 100+ countries, with live quotes, no pre-funding, and KYC, KYB, and sanctions screening built into the flow.",[18,3481,2829],{"id":2828},[11,3483,3484,3485,3488,3489,275,3491,3493,3494,275,3498,3500],{},"Create a free development instance, add a Solana Devnet wallet, and create one virtual account with ",[485,3486,3487],{},"token: \"USDB\"",", BlindPay's test stablecoin (production accounts use USDC or USDT). It's approved instantly, and every test payin completes about 30 seconds after you create it, so you can wire up ",[485,3490,3217],{},[485,3492,3229],{}," handling before your first real customer applies. The ",[133,3495,3497],{"href":3496},"\u002Fdocs\u002Fquickstart-payin","payin quickstart",[133,3499,3078],{"href":3077}," have the full requests.",[11,3502,3503],{},[1210,3504,1212],{},[3506,3507,3508],"style",{},"html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}html pre.shiki code .sYu0t, html code.shiki .sYu0t{--shiki-default:#005CC5}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":519,"searchDepth":520,"depth":520,"links":3510},[3511,3512,3513,3514,3515,3516,3517,3518,3519],{"id":2898,"depth":520,"text":2899},{"id":2916,"depth":520,"text":2917},{"id":2934,"depth":520,"text":2935},{"id":3044,"depth":520,"text":3045},{"id":3236,"depth":520,"text":3237},{"id":3351,"depth":520,"text":3352},{"id":3396,"depth":520,"text":3397},{"id":2406,"depth":520,"text":2407},{"id":2828,"depth":520,"text":2829},"2026-08-18","Accept ACH, wire, and SWIFT and settle in USDC or USDT: the flow, the token, chain, and custody choices, and when a virtual account beats a memo code.",[3523,3526,3529,3532,3535],{"q":3524,"a":3525},"How long does settlement take when a virtual account converts to stablecoins?","Most of the time is on the bank side. Domestic wires typically settle the same business day and ACH in one to three business days, and BlindPay watches for ACH and wire deposits for up to 5 business days. Once the deposit lands, conversion and the on-chain transfer to the wallet take seconds to minutes depending on the network.",{"q":3527,"a":3528},"Which bank rails can pay into a stablecoin virtual account?","It depends on the provider and the account type. BlindPay US virtual accounts receive ACH, domestic wire, and SWIFT, with the exact mix set by the account type. SWIFT deposits from foreign banks require an approved virtual account, since there is no memo-code fallback for international wires.",{"q":3530,"a":3531},"Who holds the funds in a stablecoin virtual account?","The fiat lands at the provider's banking partner and is converted by the provider. The stablecoins then go to the wallet linked to the account. At BlindPay that is an external blockchain wallet the customer controls, so once the stablecoins land, the provider no longer holds them. Other providers may settle into a wallet they custody, so ask.",{"q":3533,"a":3534},"What happens if the payer sends the wrong amount?","With a virtual account, there is no expected amount. Whatever arrives becomes a payin and converts, from a $0.01 micro-deposit upward, and at least $0.01 of stablecoin always reaches the wallet. Matching that amount against an invoice, and chasing any shortfall, is a job for your own ledger rather than the account.",{"q":3536,"a":3537},"Can the same customer turn stablecoins back into fiat?","Yes. The same wallet that receives virtual account settlements can fund payouts to bank accounts. BlindPay pays out over Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), and other local rails to 100+ countries, with a quote that locks the rate and fees before the stablecoins move, and no pre-funding required.",{"name":3539,"steps":3540},"How to accept bank transfers and settle in stablecoins with a virtual account",[3541,3544,3547,3550,3553,3556],{"name":3542,"text":3543},"Onboard and verify the customer","Create the customer and complete KYC for individuals or KYB for businesses, including the compliance profile fields the banking partner reviews.",{"name":3545,"text":3546},"Link a settlement wallet","Add the blockchain wallet where converted stablecoins will land. Its network decides which stablecoins you can settle in.",{"name":3548,"text":3549},"Create the virtual account","Request the account with the settlement token and the wallet. It goes through compliance review and bank review before approval.",{"name":3551,"text":3552},"Share the account details","Once approved, give the payer the routing and account number, plus SWIFT details for foreign senders.",{"name":3554,"text":3555},"Receive the deposit","The payer sends ACH, wire, or SWIFT. Each deposit creates its own payin record and fires a webhook.",{"name":3557,"text":3558},"Settle to the wallet","The deposit converts to USDC or USDT and is sent on-chain to the linked wallet. A completion webhook confirms delivery.",{"author":555},"\u002Fresources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins","---\ntitle: \"How to accept bank transfers and settle in stablecoins using virtual accounts\"\nseoTitle: \"Accept ACH and wire, settle in USDC: how it works\"\ndescription: \"Accept ACH, wire, and SWIFT and settle in USDC or USDT: the flow, the token, chain, and custody choices, and when a virtual account beats a memo code.\"\ndate: \"2026-08-18\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to accept bank transfers and settle in stablecoins with a virtual account\"\n  steps:\n    - name: \"Onboard and verify the customer\"\n      text: \"Create the customer and complete KYC for individuals or KYB for businesses, including the compliance profile fields the banking partner reviews.\"\n    - name: \"Link a settlement wallet\"\n      text: \"Add the blockchain wallet where converted stablecoins will land. Its network decides which stablecoins you can settle in.\"\n    - name: \"Create the virtual account\"\n      text: \"Request the account with the settlement token and the wallet. It goes through compliance review and bank review before approval.\"\n    - name: \"Share the account details\"\n      text: \"Once approved, give the payer the routing and account number, plus SWIFT details for foreign senders.\"\n    - name: \"Receive the deposit\"\n      text: \"The payer sends ACH, wire, or SWIFT. Each deposit creates its own payin record and fires a webhook.\"\n    - name: \"Settle to the wallet\"\n      text: \"The deposit converts to USDC or USDT and is sent on-chain to the linked wallet. A completion webhook confirms delivery.\"\nfaq:\n  - q: \"How long does settlement take when a virtual account converts to stablecoins?\"\n    a: \"Most of the time is on the bank side. Domestic wires typically settle the same business day and ACH in one to three business days, and BlindPay watches for ACH and wire deposits for up to 5 business days. Once the deposit lands, conversion and the on-chain transfer to the wallet take seconds to minutes depending on the network.\"\n  - q: \"Which bank rails can pay into a stablecoin virtual account?\"\n    a: \"It depends on the provider and the account type. BlindPay US virtual accounts receive ACH, domestic wire, and SWIFT, with the exact mix set by the account type. SWIFT deposits from foreign banks require an approved virtual account, since there is no memo-code fallback for international wires.\"\n  - q: \"Who holds the funds in a stablecoin virtual account?\"\n    a: \"The fiat lands at the provider's banking partner and is converted by the provider. The stablecoins then go to the wallet linked to the account. At BlindPay that is an external blockchain wallet the customer controls, so once the stablecoins land, the provider no longer holds them. Other providers may settle into a wallet they custody, so ask.\"\n  - q: \"What happens if the payer sends the wrong amount?\"\n    a: \"With a virtual account, there is no expected amount. Whatever arrives becomes a payin and converts, from a $0.01 micro-deposit upward, and at least $0.01 of stablecoin always reaches the wallet. Matching that amount against an invoice, and chasing any shortfall, is a job for your own ledger rather than the account.\"\n  - q: \"Can the same customer turn stablecoins back into fiat?\"\n    a: \"Yes. The same wallet that receives virtual account settlements can fund payouts to bank accounts. BlindPay pays out over Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), and other local rails to 100+ countries, with a quote that locks the rate and fees before the stablecoins move, and no pre-funding required.\"\n---\n\nTo accept bank transfers and settle in stablecoins, give each customer a virtual account: a bank account number in their name that converts every incoming deposit into USDC or USDT and sends it on-chain to a linked wallet. The payer sends an ordinary ACH, wire, or SWIFT transfer. The provider handles the conversion. The customer ends up holding stablecoins.\n\nNo checkout page. No crypto on the payer's side.\n\n## Key takeaways\n\n- There are two ways to take a bank transfer and settle in stablecoins: standing virtual account details, or one-time payment instructions with a memo code.\n- Virtual accounts win for repeat payers, foreign senders, and anyone who forgets memo codes (everyone).\n- The wallet you link decides which stablecoins and chains you can settle in. Pick it before you create the account.\n- Most of the settlement time is the bank leg. The on-chain leg takes seconds to minutes.\n\n## How do virtual accounts turn bank deposits into stablecoins?\n\nA virtual account turns bank deposits into stablecoins by pairing a bank account number with a destination wallet. When a deposit lands on the account number, the provider records it, converts the dollars into a stablecoin, and sends the stablecoin to the wallet in an on-chain transaction.\n\nThat's the on-ramp, reduced to one object. The deeper walkthrough of approval states and deposit handling is in [stablecoin virtual accounts explained](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained), and what happens on the blockchain at each step is in [what happens on-chain in a stablecoin payment](\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment).\n\n## Virtual account or payment instructions: which one should you use?\n\nUse a virtual account when the same payer sends money more than once or pays from abroad. Use one-time payment instructions when a payer sends a single transfer and you don't want to wait for account approval.\n\nWith one-time instructions, you create a quote for a specific payment, then show the payer a shared bank account plus a memo code they must include so the deposit can be matched. With a virtual account, the payer gets bank details in your customer's own name, and the account number does the matching.\n\n| | Virtual account | One-time payment instructions |\n| --- | --- | --- |\n| What the payer gets | Routing and account number in your customer's name | Shared bank details plus a memo code |\n| Reusable | Yes, same details every time | No, one set per payment |\n| How a deposit is matched | By the receiving account number | By the memo code the payer types |\n| Setup | Account review before first use | Available immediately |\n| International SWIFT | Yes, on account types that support it | Not at BlindPay: SWIFT deposits require a virtual account |\n| Failure mode | Account rejected or approval delayed | Memo missing or mistyped, deposit waits to be matched |\n| Best for | Recurring payers, payroll funding, B2B, foreign clients | Occasional one-off deposits |\n\nAt BlindPay, the two paths are connected. Once a customer has an approved virtual account, ACH and wire payins show that account's own details and the memo code is ignored ([payins](\u002Fdocs\u002Fpayins)). RTP deposits are the exception: they always use the shared memo-code account, because no virtual account carries an RTP rail.\n\n## What does the end-to-end flow look like?\n\nThe flow has six steps, and only the last two involve money.\n\n1. **Onboard and verify the customer.** KYC for individuals, KYB for businesses. At BlindPay, the customer's `kyc_status` must be `approved` before you can request an account, and business customers need fields like `account_purpose`, `source_of_wealth`, `business_industry` (a NAICS code), and at least one owner filled in ([create a virtual account](\u002Fdocs\u002Fvirtual-accounts-create)).\n2. **Link a settlement wallet.** Add the [blockchain wallet](\u002Fdocs\u002Fblockchain-wallets) where the stablecoins will land. It must belong to the same customer.\n3. **Create the virtual account.** One API call, with the settlement token and the wallet:\n\n```bash\ncurl --request POST \\\n  --url https:\u002F\u002Fapi.blindpay.com\u002Fv1\u002Finstances\u002Fin_000000000000\u002Fcustomers\u002Fre_000000000000\u002Fvirtual-accounts \\\n  --header 'Authorization: Bearer YOUR_API_KEY' \\\n  --header 'Content-Type: application\u002Fjson' \\\n  --data '{\n  \"banking_partner\": \"cfsb\",\n  \"token\": \"USDC\",\n  \"blockchain_wallet_id\": \"bw_000000000000\"\n}'\n```\n\n4. **Wait for approval.** Production accounts move from `pending_review` (compliance) to `verifying` (bank) to `approved`, and `virtualAccount.complete` fires with the routing and account numbers. Development accounts are approved instantly.\n5. **Receive the deposit.** The payer sends ACH, wire, or SWIFT. Each deposit creates a payin and fires `payin.new`.\n6. **Settle to the wallet.** The deposit converts and the stablecoins go on-chain to the linked wallet. The payin reaches `completed` and `payin.complete` fires.\n\nAfter step 4, nothing else needs an API call. Every future deposit repeats steps 5 and 6 on its own.\n\n## Which design decisions do you need to make?\n\nSix decisions shape a stablecoin collection flow. Most depend on the provider, so the table shows what to ask any provider next to how BlindPay answers.\n\n| Decision | What to ask any provider | BlindPay |\n| --- | --- | --- |\n| Custody | Do stablecoins settle to a wallet I control, or one you hold? | Virtual accounts settle to an external blockchain wallet the customer controls |\n| Which stablecoin | USDC, USDT, or both? Can I switch later? | USDC or USDT, and `token` can be updated on an existing account |\n| Which chain | Which networks can receive settlement? | USDC on Ethereum, Polygon, Base, Arbitrum, Stellar, and Solana. USDT needs a wallet on Polygon, Ethereum, or Solana |\n| Fees | Monthly cost per account? Per-deposit fee? Where does it show up? | $1.50 per month per account. Per-deposit fees below $100.00 go to your invoice; at $100.00 or more they're deducted from the delivered stablecoin |\n| Minimum deposit | Are small deposits ignored or processed? | Every deposit is processed, including $0.01 micro-deposits, and at least $0.01 is always delivered |\n| Settlement time | How long for each rail, and what restarts the clock? | ACH and wire deposits can take up to 5 business days to arrive; the on-chain leg takes seconds to minutes |\n\nTwo of these are worth a second look.\n\n**Custody.** Settling to a wallet your customer controls means the stablecoins stop being the provider's liability the moment they land. It also means your customer is responsible for that wallet's keys. [Non-custodial payments explained](\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained) covers the trade-off in full.\n\n**Token and chain.** They're linked. At BlindPay, choosing USDT means the wallet must be on Polygon, Ethereum, or Solana. Stellar wallets receive USDC only, and need a USDC trustline before they can. If you're unsure which token, [USDC vs USDT for payments](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) compares them. For speed and low network fees, Solana is a common pick: BlindPay payins, payouts, and virtual accounts all run on it.\n\n## What does compliance look like?\n\nCompliance happens at three points: when the customer is onboarded, when the account is approved, and when each deposit arrives.\n\n- **Customer onboarding.** KYC or KYB, plus sanctions screening. The provider has to know who the account belongs to.\n- **Account approval.** Banks want to know what the account is for. At BlindPay that means the purpose of the account, source of funds, and source of wealth, backed by documents like recent bank statements or financial statements ([virtual account requirements](\u002Fdocs\u002Fkb\u002Fvirtual-accounts)).\n- **Each deposit.** A deposit can be held for review. At BlindPay, a payin in review shows `on_hold` and resumes when cleared.\n\nTwo rules apply beyond the first deposit. First, the money has to belong to the customer the account was issued to. Collecting for your customer's own clients through their account is nesting, which BlindPay does not allow ([nested payments](\u002Fdocs\u002Fkb\u002Fnested-payments)). Second, when stablecoins move between providers, travel rule obligations can require originator and beneficiary information to travel with the transfer. How that applies depends on the jurisdiction and the wallets involved, so ask your provider how they handle it. The [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) follows the rules by market.\n\n## What does this look like for a payroll platform?\n\n**Illustrative example.** A contractor payroll platform has three US client companies. Each client is onboarded as a BlindPay customer, passes KYB, and gets its own virtual account settling USDC to its own wallet on Solana.\n\n| Client | Funds payroll by | Deposit | What lands |\n| --- | --- | --- | --- |\n| Client A | Domestic wire, Monday morning | $48,000.00 | USDC in Client A's wallet, minus the deposit fee |\n| Client B | ACH, twice a month | $12,500.00 each | USDC in Client B's wallet after each ACH settles |\n| Client C | ACH from a payroll provider that verifies with a $0.01 test | $0.01, then $9,000.00 | Two payins: at least $0.01 of USDC, then the full deposit minus fees |\n\nNobody types a memo code. Every deposit arrives already labeled by the account it hit. The platform then pays each client's contractors from that client's wallet, over local rails in each contractor's country. (Amounts are illustrative; fees depend on your plan.)\n\nNotice Client C's penny. That's an account-verification micro-deposit, and it shows up as its own payin. Reconcile it, don't flag it.\n\n## Where does BlindPay fit?\n\n[BlindPay virtual accounts](\u002Fvirtual-accounts) give each customer a US bank account in their own name that receives ACH, wire, and SWIFT and settles automatically to USDC or USDT in the customer's wallet. The same API pays out over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO) to 100+ countries, with live quotes, no pre-funding, and KYC, KYB, and sanctions screening built into the flow.\n\n## What to do next\n\nCreate a free development instance, add a Solana Devnet wallet, and create one virtual account with `token: \"USDB\"`, BlindPay's test stablecoin (production accounts use USDC or USDT). It's approved instantly, and every test payin completes about 30 seconds after you create it, so you can wire up `payin.new` and `payin.complete` handling before your first real customer applies. The [payin quickstart](\u002Fdocs\u002Fquickstart-payin) and [create a virtual account](\u002Fdocs\u002Fvirtual-accounts-create) have the full requests.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":2887,"description":3521},"Accept ACH and wire, settle in USDC: how it works","resources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins","8WAAqot0BVq_miStLJv2jpJh_xooCByPAviwjrnSTbA",{"id":3567,"title":3568,"authors":6,"body":3569,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":4147,"description":4148,"extension":536,"faq":4149,"howto":6,"isBlog":553,"isChangelog":553,"meta":4165,"navigation":556,"path":4166,"pillar":553,"products":6,"rawbody":4167,"role":6,"seo":4168,"seoTitle":4169,"stem":4170,"thumbnail":6,"updated":6,"__hash__":4171},"content\u002Fresources\u002Fmore\u002Fhow-to-choose-a-blockchain-payment-api.md","How to choose a blockchain payment API: a technical buyer's checklist",{"type":8,"value":3570,"toc":4135},[3571,3574,3580,3586,3590,3593,3603,3607,3610,3627,3688,3692,3695,3698,3706,3767,3774,3778,3781,3785,3907,3915,3919,3922,3939,3943,3946,3960,3964,3967,3984,3988,3991,4019,4023,4118,4120,4131],[11,3572,3573],{},"A blockchain payment API lets your product move money over stablecoin networks through ordinary REST calls. You create quotes, payins, and payouts. The provider handles wallets, chains, conversion, and the bank rails at each end. Picking one comes down to seven checks, and most of them can be done with the docs and a sandbox key before anyone books a sales call.",[11,3575,3576,3577,3579],{},"This checklist is for the engineering lead or PM who will live with the integration for years. The commercial questions (pre-funding, settlement speed, contract terms) are covered in ",[133,3578,1185],{"href":1184},". This page is about the API surface itself: what you'll actually type, test, and debug.",[11,3581,3582,3583,3585],{},"Each section says why the criterion matters, what a good answer looks like, and how ",[133,3584,952],{"href":951}," handles it. The summary table is at the end.",[18,3587,3589],{"id":3588},"_1-which-languages-do-the-sdks-cover","1. Which languages do the SDKs cover?",[11,3591,3592],{},"SDKs decide how much glue code you write and how fast you notice a breaking change. A good answer is an official SDK in your backend language, versioned, and built from the same spec the API is validated against, so a field can't exist in one and not the other. Typed amounts and typed webhook payloads are a bonus that pays for itself the first time someone mixes up cents and dollars.",[11,3594,3595,3598,3599,329],{},[150,3596,3597],{},"BlindPay:"," five official SDKs (Node.js\u002FTypeScript, Python, Go, PHP, and Swift) wrap the same REST API. For any other language, generate a typed client from the OpenAPI spec. There is also a CLI and an MCP server for AI coding agents. How one spec keeps the SDKs in sync is covered in ",[133,3600,3602],{"href":3601},"\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks","stablecoin API SDKs",[18,3604,3606],{"id":3605},"_2-is-the-rest-api-documented-by-a-real-openapi-spec","2. Is the REST API documented by a real OpenAPI spec?",[11,3608,3609],{},"A downloadable, machine-readable spec lets you generate types, mock the API in tests, and diff versions in CI. Hand-written reference pages drift. Look for five things:",[144,3611,3612,3615,3618,3621,3624],{},[147,3613,3614],{},"An OpenAPI 3.x spec you can download without logging in",[147,3616,3617],{},"Idempotency on every mutating request, so a retry after a timeout can't create a second payout",[147,3619,3620],{},"Signed webhooks with a stable event ID you can deduplicate on",[147,3622,3623],{},"Amounts as integers in minor units, never floats",[147,3625,3626],{},"A sandbox that behaves like production, including failure states",[11,3628,3629,3631,3632,3635,3636,1718,3639,1718,3642,2844,3645,3648,3649,3652,3653,3657,3658,1718,3661,1567,3664,3667,3668,3670,3671,3675,3676,3679,3680,275,3684,329],{},[150,3630,3597],{}," the OpenAPI 3.1 spec downloads from ",[485,3633,3634],{},"https:\u002F\u002Fapi.blindpay.com\u002Fdoc",". Any ",[485,3637,3638],{},"POST",[485,3640,3641],{},"PUT",[485,3643,3644],{},"PATCH",[485,3646,3647],{},"DELETE"," accepts an ",[485,3650,3651],{},"Idempotency-Key"," header of up to 255 characters, and a retry only replays when the body is byte-identical (",[133,3654,3656],{"href":3655},"\u002Fdocs\u002Flearn\u002Fidempotency","idempotency","). Webhooks are signed with ",[485,3659,3660],{},"svix-id",[485,3662,3663],{},"svix-timestamp",[485,3665,3666],{},"svix-signature"," headers, and ",[485,3669,3660],{}," stays the same across redeliveries (",[133,3672,3674],{"href":3673},"\u002Fdocs\u002Flearn\u002Fwebhooks-verification","webhook verification","). Amounts are minor units: ",[485,3677,3678],{},"10000"," is $100.00. The practical side of both is in ",[133,3681,3683],{"href":3682},"\u002Fresources\u002Fmore\u002Fstablecoin-api-idempotency-keys","idempotency keys",[133,3685,3687],{"href":3686},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","webhooks and reconciliation",[18,3689,3691],{"id":3690},"_3-does-the-api-hide-the-blockchain-or-expose-it","3. Does the API hide the blockchain, or expose it?",[11,3693,3694],{},"This is the criterion most checklists skip, and it splits buyers into two groups.",[11,3696,3697],{},"A payroll, remittance, or B2B payments product wants bank-shaped building blocks: an account number in, a bank payout out, the chain invisible. A wallet, exchange, or treasury product wants to pick the chain and token, hold its own keys, and sign authorizations. An API built for only one group forces the other into workarounds. The good answer is both, on one engine, with no second contract or second set of keys.",[11,3699,3700,3702,3703,498],{},[150,3701,3597],{}," the docs come in two flavors of the same API. Both run on the same authentication, instances, and webhooks, and switching between them changes nothing about your account or key (",[133,3704,3705],{"href":2589},"introduction",[23,3707,3708,3721],{},[26,3709,3710],{},[29,3711,3712,3715,3718],{},[32,3713,3714],{},"Verb",[32,3716,3717],{},"Abstracted",[32,3719,3720],{},"Advanced",[42,3722,3723,3734,3745,3756],{},[29,3724,3725,3728,3731],{},[47,3726,3727],{},"Store",[47,3729,3730],{},"Value settles as stablecoin in the linked wallet",[47,3732,3733],{},"Managed wallet or external blockchain wallet",[29,3735,3736,3739,3742],{},[47,3737,3738],{},"Receive",[47,3740,3741],{},"Bank transfer in (payin)",[47,3743,3744],{},"On-ramp: fiat in, stablecoin delivered to a wallet",[29,3746,3747,3750,3753],{},[47,3748,3749],{},"Send",[47,3751,3752],{},"Payout to a bank account",[47,3754,3755],{},"Off-ramp: stablecoin pulled from a wallet, fiat out",[29,3757,3758,3761,3764],{},[47,3759,3760],{},"Transfer",[47,3762,3763],{},"Not applicable",[47,3765,3766],{},"Cross-chain stablecoin transfer",[11,3768,3769,3770,3773],{},"Advanced exposes the on-chain mechanics: ERC-20 ",[485,3771,3772],{},"approve"," on EVM chains, a signed XDR on Stellar, token delegation on Solana. Abstracted never asks you to sign anything.",[18,3775,3777],{"id":3776},"_4-which-networks-does-it-settle-on-and-who-picks-the-network","4. Which networks does it settle on, and who picks the network?",[11,3779,3780],{},"Network choice affects fees, confirmation time, which stablecoins are available (USDT dominates on Tron, for example), and which wallets your customers already hold. For the end user, though, it's mostly noise. A good API covers the major networks, gives you a testnet for each, and lets you keep the network out of the user's way in bank-to-bank flows.",[11,3782,3783],{},[150,3784,3597],{},[23,3786,3787,3799],{},[26,3788,3789],{},[29,3790,3791,3793,3796],{},[32,3792,60],{},[32,3794,3795],{},"Tokens",[32,3797,3798],{},"Testnet",[42,3800,3801,3814,3826,3838,3850,3862,3874,3886,3898],{},[29,3802,3803,3806,3809],{},[47,3804,3805],{},"Ethereum",[47,3807,3808],{},"USDC, USDT",[47,3810,3811],{},[485,3812,3813],{},"sepolia",[29,3815,3816,3819,3821],{},[47,3817,3818],{},"Polygon",[47,3820,3808],{},[47,3822,3823],{},[485,3824,3825],{},"polygon_amoy",[29,3827,3828,3831,3833],{},[47,3829,3830],{},"Base",[47,3832,2190],{},[47,3834,3835],{},[485,3836,3837],{},"base_sepolia",[29,3839,3840,3843,3845],{},[47,3841,3842],{},"Arbitrum",[47,3844,2190],{},[47,3846,3847],{},[485,3848,3849],{},"arbitrum_sepolia",[29,3851,3852,3855,3857],{},[47,3853,3854],{},"Tempo",[47,3856,3808],{},[47,3858,3859],{},[485,3860,3861],{},"tempo_testnet",[29,3863,3864,3867,3869],{},[47,3865,3866],{},"Arc",[47,3868,2190],{},[47,3870,3871],{},[485,3872,3873],{},"arc_testnet",[29,3875,3876,3879,3881],{},[47,3877,3878],{},"Solana",[47,3880,3808],{},[47,3882,3883],{},[485,3884,3885],{},"solana_devnet",[29,3887,3888,3891,3893],{},[47,3889,3890],{},"Stellar",[47,3892,2190],{},[47,3894,3895],{},[485,3896,3897],{},"stellar_testnet",[29,3899,3900,3903,3905],{},[47,3901,3902],{},"Tron",[47,3904,2194],{},[47,3906,413],{},[11,3908,3909,3910,3912,3913,329],{},"Tron has no testnet. Development instances use USDB, a test token that simulates transactions without real funds, on every testnet above (",[133,3911,497],{"href":496},"). USDC can move cross-chain between managed wallets through Circle's CCTP v2. What actually happens on each network between \"sent\" and \"confirmed\" is in ",[133,3914,2931],{"href":200},[18,3916,3918],{"id":3917},"_5-is-compliance-built-into-the-api-or-bolted-on","5. Is compliance built into the API or bolted on?",[11,3920,3921],{},"If KYC, KYB, and sanctions screening live with a separate vendor, you own the plumbing between them: status syncing, document uploads, re-verification, and the audit trail that links an identity to a payment. Built in means every payment object belongs to a verified customer and can't execute for an unverified one. Look for verification statuses in the API, a way to answer requests for information programmatically, and documented review states on payments.",[11,3923,3924,3926,3927,3931,3932,3934,3935,329],{},[150,3925,3597],{}," every payment flows through a customer that has completed KYC. You collect the data, BlindPay verifies it. Standard KYC takes about 60 seconds; KYB takes 3 hours to 1 business day because a person reviews it (",[133,3928,3930],{"href":3929},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times and SLAs","). Payments that need review sit in an ",[485,3933,487],{}," status you can see and react to. More on the automation side in ",[133,3936,3938],{"href":3937},"\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments","how to automate KYC and KYB",[18,3940,3942],{"id":3941},"_6-which-local-payout-rails-are-live-in-production","6. Which local payout rails are live in production?",[11,3944,3945],{},"The stablecoin leg is the easy part. The rail at the end decides whether the recipient gets paid in minutes or in a week. A good answer names each rail, publishes a settlement window and cut-off for each, and documents the required fields per rail. \"Coming soon\" doesn't count.",[11,3947,3948,3950,3951,3955,3956,329],{},[150,3949,3597],{}," Pix and TED in Brazil, SPEI in Mexico, Transfers in Argentina, ACH COP in Colombia, ACH, wire, and RTP in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations. Pix, SPEI, Transfers, and RTP are instant; wire, SEPA, and ACH COP take about 1 business day; ACH about 2; SWIFT about 5 (",[133,3952,3954],{"href":3953},"\u002Fdocs\u002Fbank-accounts","bank accounts","). The per-country breakdown is in ",[133,3957,3959],{"href":3958},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times","stablecoin payout settlement times",[18,3961,3963],{"id":3962},"_7-can-you-see-the-price-before-you-sign-and-is-there-a-volume-floor","7. Can you see the price before you sign, and is there a volume floor?",[11,3965,3966],{},"You'll model unit economics per corridor, so you need numbers you can reproduce. Watch for three things: a minimum monthly volume commitment, a pre-funding requirement (capital parked in the provider's accounts is a cost even when it isn't a line item), and a blended rate that hides the FX spread inside one number.",[11,3968,3969,3971,3972,3974,3975,3979,3980,329],{},[150,3970,3597],{}," plans are listed on the ",[133,3973,1688],{"href":967},". There is no setup fee and no monthly minimum, and development instances are free. Transaction fees vary by rail and corridor, so every payin, payout, and transfer quote itemizes the fee before you execute, and the fee is locked for the life of the quote (",[133,3976,3978],{"href":3977},"\u002Fdocs\u002Flearn\u002Fbilling","billing","). Payouts don't require pre-funding. For how to read a quote line by line, see ",[133,3981,3983],{"href":3982},"\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained","stablecoin API pricing",[18,3985,3987],{"id":3986},"what-should-you-ask-on-the-technical-evaluation-call","What should you ask on the technical evaluation call?",[11,3989,3990],{},"Three questions, and each one exposes a different weak spot.",[289,3992,3993,4007,4013],{},[147,3994,3995,3998,3999,4002,4003,4006],{},[150,3996,3997],{},"\"Show me a payout that failed at the receiving bank.\""," Which status did it land in, which webhook fired, and where did the money go? At BlindPay, a payout the bank rejects or returns ends ",[485,4000,4001],{},"refunded"," and the stablecoins go back to the wallet that funded it. A payout that ends ",[485,4004,4005],{},"failed",", for example after a rejected compliance check, does not refund on its own and needs a support follow-up. A vendor that can't draw that line clearly hasn't thought about it.",[147,4008,4009,4012],{},[150,4010,4011],{},"\"Can I have the OpenAPI spec and a sandbox key today?\""," If either requires a contract, your evaluation just got two weeks longer.",[147,4014,4015,4018],{},[150,4016,4017],{},"\"Which of your listed rails and networks are live in production for a company like mine, and which are beta?\""," Marketing pages list everything. Production access is often narrower, and it can depend on where your company and your customers are based.",[18,4020,4022],{"id":4021},"the-checklist-at-a-glance","The checklist at a glance",[23,4024,4025,4037],{},[26,4026,4027],{},[29,4028,4029,4032,4035],{},[32,4030,4031],{},"Criterion",[32,4033,4034],{},"What a good answer looks like",[32,4036,952],{},[42,4038,4039,4050,4064,4075,4086,4096,4107],{},[29,4040,4041,4044,4047],{},[47,4042,4043],{},"SDKs",[47,4045,4046],{},"Official SDKs in your language, generated from the spec",[47,4048,4049],{},"Node.js, Python, Go, PHP, Swift, plus CLI and MCP server",[29,4051,4052,4055,4058],{},[47,4053,4054],{},"API design",[47,4056,4057],{},"Public OpenAPI spec, idempotency, signed webhooks, minor units",[47,4059,4060,4061,4063],{},"OpenAPI 3.1, ",[485,4062,3651],{},", Svix-signed webhooks",[29,4065,4066,4069,4072],{},[47,4067,4068],{},"Abstraction",[47,4070,4071],{},"Bank-shaped and chain-level modes on one engine",[47,4073,4074],{},"Abstracted and Advanced flavors of one API",[29,4076,4077,4080,4083],{},[47,4078,4079],{},"Networks",[47,4081,4082],{},"EVM, Solana, Stellar, USDC and USDT, testnets",[47,4084,4085],{},"Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Solana, Stellar, Tron",[29,4087,4088,4090,4093],{},[47,4089,115],{},[47,4091,4092],{},"KYC, KYB, screening, and review states in the API",[47,4094,4095],{},"KYC in about 60 seconds, KYB in 3 hours to 1 business day",[29,4097,4098,4101,4104],{},[47,4099,4100],{},"Payout rails",[47,4102,4103],{},"Named rails with published settlement windows",[47,4105,4106],{},"Pix, TED, SPEI, Transfers, ACH COP, ACH, wire, RTP, SEPA, SWIFT (POBO\u002FCOBO)",[29,4108,4109,4112,4115],{},[47,4110,4111],{},"Pricing",[47,4113,4114],{},"Public plans, itemized quotes, no volume floor",[47,4116,4117],{},"Plans on \u002Fpricing, fee in every quote, no monthly minimum",[18,4119,2829],{"id":2828},[11,4121,4122,4123,4127,4128,4130],{},"Run the checklist against a live sandbox, not a slide deck. Create a free BlindPay development instance, download the spec, and push one payin and one payout through end to end with the ",[133,4124,4126],{"href":4125},"\u002Fdocs\u002Fquickstart-payout","payout quickstart",". Then force a failure (a payout quote for $777.00 returns ",[485,4129,4001],{}," in development) and watch what your webhook handler does with it. That hour tells you more than any vendor call.",[11,4132,4133],{},[1210,4134,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":4136},[4137,4138,4139,4140,4141,4142,4143,4144,4145,4146],{"id":3588,"depth":520,"text":3589},{"id":3605,"depth":520,"text":3606},{"id":3690,"depth":520,"text":3691},{"id":3776,"depth":520,"text":3777},{"id":3917,"depth":520,"text":3918},{"id":3941,"depth":520,"text":3942},{"id":3962,"depth":520,"text":3963},{"id":3986,"depth":520,"text":3987},{"id":4021,"depth":520,"text":4022},{"id":2828,"depth":520,"text":2829},"2026-09-25","Seven checks for a blockchain payment API: SDKs, OpenAPI quality, abstraction level, networks, built-in compliance, local payout rails, and pricing.",[4150,4153,4156,4159,4162],{"q":4151,"a":4152},"What is a blockchain payment API?","A blockchain payment API lets a product move money over stablecoin networks through ordinary REST calls. You create quotes, payins, and payouts; the provider handles wallets, chains, conversion between fiat and stablecoins, and the local bank rails at each end. Most business use is bank to bank, with the blockchain acting as the settlement layer in the middle.",{"q":4154,"a":4155},"Do I have to pick a blockchain to use a blockchain payment API?","Not if the API offers an abstracted mode. In BlindPay's Abstracted flavor you work with virtual accounts, payins, and bank payouts, and stablecoins settle in the linked wallet behind the scenes. Teams that want to choose the chain and token, hold their own keys, or move stablecoins cross-chain use the Advanced flavor of the same API.",{"q":4157,"a":4158},"Which blockchain networks should a payment API support?","At minimum, the major EVM chains, Solana, and Stellar, with both USDC and USDT where the network supports them, plus a testnet for each. BlindPay settles on Ethereum, Polygon, Tempo, and Solana (USDC and USDT), Base, Arbitrum, Arc, and Stellar (USDC), and Tron (USDT).",{"q":4160,"a":4161},"Should KYC and KYB be part of the payment API or a separate vendor?","Built in is easier to run. When verification lives in the same API, every payment is tied to a verified customer and cannot execute without one, and the audit trail joining identity to money movement already exists. A separate vendor means you build and maintain that join yourself, including status syncing and re-verification.",{"q":4163,"a":4164},"What is the most useful question to ask a blockchain payment API vendor?","Ask them to show a payout that failed at the receiving bank: which status it landed in, which webhook fired, and where the funds went. The answer tests failure handling, webhook design, and whether the custody model works the way the sales deck says, all in one demo.",{"author":555},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-blockchain-payment-api","---\ntitle: \"How to choose a blockchain payment API: a technical buyer's checklist\"\nseoTitle: \"How to choose a blockchain payment API: 7-point checklist\"\ndescription: \"Seven checks for a blockchain payment API: SDKs, OpenAPI quality, abstraction level, networks, built-in compliance, local payout rails, and pricing.\"\ndate: \"2026-09-25\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a blockchain payment API?\"\n    a: \"A blockchain payment API lets a product move money over stablecoin networks through ordinary REST calls. You create quotes, payins, and payouts; the provider handles wallets, chains, conversion between fiat and stablecoins, and the local bank rails at each end. Most business use is bank to bank, with the blockchain acting as the settlement layer in the middle.\"\n  - q: \"Do I have to pick a blockchain to use a blockchain payment API?\"\n    a: \"Not if the API offers an abstracted mode. In BlindPay's Abstracted flavor you work with virtual accounts, payins, and bank payouts, and stablecoins settle in the linked wallet behind the scenes. Teams that want to choose the chain and token, hold their own keys, or move stablecoins cross-chain use the Advanced flavor of the same API.\"\n  - q: \"Which blockchain networks should a payment API support?\"\n    a: \"At minimum, the major EVM chains, Solana, and Stellar, with both USDC and USDT where the network supports them, plus a testnet for each. BlindPay settles on Ethereum, Polygon, Tempo, and Solana (USDC and USDT), Base, Arbitrum, Arc, and Stellar (USDC), and Tron (USDT).\"\n  - q: \"Should KYC and KYB be part of the payment API or a separate vendor?\"\n    a: \"Built in is easier to run. When verification lives in the same API, every payment is tied to a verified customer and cannot execute without one, and the audit trail joining identity to money movement already exists. A separate vendor means you build and maintain that join yourself, including status syncing and re-verification.\"\n  - q: \"What is the most useful question to ask a blockchain payment API vendor?\"\n    a: \"Ask them to show a payout that failed at the receiving bank: which status it landed in, which webhook fired, and where the funds went. The answer tests failure handling, webhook design, and whether the custody model works the way the sales deck says, all in one demo.\"\n---\n\nA blockchain payment API lets your product move money over stablecoin networks through ordinary REST calls. You create quotes, payins, and payouts. The provider handles wallets, chains, conversion, and the bank rails at each end. Picking one comes down to seven checks, and most of them can be done with the docs and a sandbox key before anyone books a sales call.\n\nThis checklist is for the engineering lead or PM who will live with the integration for years. The commercial questions (pre-funding, settlement speed, contract terms) are covered in [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api). This page is about the API surface itself: what you'll actually type, test, and debug.\n\nEach section says why the criterion matters, what a good answer looks like, and how [BlindPay](\u002Fglobal-payments) handles it. The summary table is at the end.\n\n## 1. Which languages do the SDKs cover?\n\nSDKs decide how much glue code you write and how fast you notice a breaking change. A good answer is an official SDK in your backend language, versioned, and built from the same spec the API is validated against, so a field can't exist in one and not the other. Typed amounts and typed webhook payloads are a bonus that pays for itself the first time someone mixes up cents and dollars.\n\n**BlindPay:** five official SDKs (Node.js\u002FTypeScript, Python, Go, PHP, and Swift) wrap the same REST API. For any other language, generate a typed client from the OpenAPI spec. There is also a CLI and an MCP server for AI coding agents. How one spec keeps the SDKs in sync is covered in [stablecoin API SDKs](\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks).\n\n## 2. Is the REST API documented by a real OpenAPI spec?\n\nA downloadable, machine-readable spec lets you generate types, mock the API in tests, and diff versions in CI. Hand-written reference pages drift. Look for five things:\n\n- An OpenAPI 3.x spec you can download without logging in\n- Idempotency on every mutating request, so a retry after a timeout can't create a second payout\n- Signed webhooks with a stable event ID you can deduplicate on\n- Amounts as integers in minor units, never floats\n- A sandbox that behaves like production, including failure states\n\n**BlindPay:** the OpenAPI 3.1 spec downloads from `https:\u002F\u002Fapi.blindpay.com\u002Fdoc`. Any `POST`, `PUT`, `PATCH`, or `DELETE` accepts an `Idempotency-Key` header of up to 255 characters, and a retry only replays when the body is byte-identical ([idempotency](\u002Fdocs\u002Flearn\u002Fidempotency)). Webhooks are signed with `svix-id`, `svix-timestamp`, and `svix-signature` headers, and `svix-id` stays the same across redeliveries ([webhook verification](\u002Fdocs\u002Flearn\u002Fwebhooks-verification)). Amounts are minor units: `10000` is $100.00. The practical side of both is in [idempotency keys](\u002Fresources\u002Fmore\u002Fstablecoin-api-idempotency-keys) and [webhooks and reconciliation](\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation).\n\n## 3. Does the API hide the blockchain, or expose it?\n\nThis is the criterion most checklists skip, and it splits buyers into two groups.\n\nA payroll, remittance, or B2B payments product wants bank-shaped building blocks: an account number in, a bank payout out, the chain invisible. A wallet, exchange, or treasury product wants to pick the chain and token, hold its own keys, and sign authorizations. An API built for only one group forces the other into workarounds. The good answer is both, on one engine, with no second contract or second set of keys.\n\n**BlindPay:** the docs come in two flavors of the same API. Both run on the same authentication, instances, and webhooks, and switching between them changes nothing about your account or key ([introduction](\u002Fdocs\u002Fintroduction)).\n\n| Verb | Abstracted | Advanced |\n| --- | --- | --- |\n| Store | Value settles as stablecoin in the linked wallet | Managed wallet or external blockchain wallet |\n| Receive | Bank transfer in (payin) | On-ramp: fiat in, stablecoin delivered to a wallet |\n| Send | Payout to a bank account | Off-ramp: stablecoin pulled from a wallet, fiat out |\n| Transfer | Not applicable | Cross-chain stablecoin transfer |\n\nAdvanced exposes the on-chain mechanics: ERC-20 `approve` on EVM chains, a signed XDR on Stellar, token delegation on Solana. Abstracted never asks you to sign anything.\n\n## 4. Which networks does it settle on, and who picks the network?\n\nNetwork choice affects fees, confirmation time, which stablecoins are available (USDT dominates on Tron, for example), and which wallets your customers already hold. For the end user, though, it's mostly noise. A good API covers the major networks, gives you a testnet for each, and lets you keep the network out of the user's way in bank-to-bank flows.\n\n**BlindPay:**\n\n| Network | Tokens | Testnet |\n| --- | --- | --- |\n| Ethereum | USDC, USDT | `sepolia` |\n| Polygon | USDC, USDT | `polygon_amoy` |\n| Base | USDC | `base_sepolia` |\n| Arbitrum | USDC | `arbitrum_sepolia` |\n| Tempo | USDC, USDT | `tempo_testnet` |\n| Arc | USDC | `arc_testnet` |\n| Solana | USDC, USDT | `solana_devnet` |\n| Stellar | USDC | `stellar_testnet` |\n| Tron | USDT | None |\n\nTron has no testnet. Development instances use USDB, a test token that simulates transactions without real funds, on every testnet above ([supported chains](\u002Fdocs\u002Fkb\u002Fsupported-chains)). USDC can move cross-chain between managed wallets through Circle's CCTP v2. What actually happens on each network between \"sent\" and \"confirmed\" is in [what happens on-chain in a stablecoin payment](\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment).\n\n## 5. Is compliance built into the API or bolted on?\n\nIf KYC, KYB, and sanctions screening live with a separate vendor, you own the plumbing between them: status syncing, document uploads, re-verification, and the audit trail that links an identity to a payment. Built in means every payment object belongs to a verified customer and can't execute for an unverified one. Look for verification statuses in the API, a way to answer requests for information programmatically, and documented review states on payments.\n\n**BlindPay:** every payment flows through a customer that has completed KYC. You collect the data, BlindPay verifies it. Standard KYC takes about 60 seconds; KYB takes 3 hours to 1 business day because a person reviews it ([cut-off times and SLAs](\u002Fdocs\u002Fkb\u002Fcut-off-times)). Payments that need review sit in an `on_hold` status you can see and react to. More on the automation side in [how to automate KYC and KYB](\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments).\n\n## 6. Which local payout rails are live in production?\n\nThe stablecoin leg is the easy part. The rail at the end decides whether the recipient gets paid in minutes or in a week. A good answer names each rail, publishes a settlement window and cut-off for each, and documents the required fields per rail. \"Coming soon\" doesn't count.\n\n**BlindPay:** Pix and TED in Brazil, SPEI in Mexico, Transfers in Argentina, ACH COP in Colombia, ACH, wire, and RTP in the US, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations. Pix, SPEI, Transfers, and RTP are instant; wire, SEPA, and ACH COP take about 1 business day; ACH about 2; SWIFT about 5 ([bank accounts](\u002Fdocs\u002Fbank-accounts)). The per-country breakdown is in [stablecoin payout settlement times](\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times).\n\n## 7. Can you see the price before you sign, and is there a volume floor?\n\nYou'll model unit economics per corridor, so you need numbers you can reproduce. Watch for three things: a minimum monthly volume commitment, a pre-funding requirement (capital parked in the provider's accounts is a cost even when it isn't a line item), and a blended rate that hides the FX spread inside one number.\n\n**BlindPay:** plans are listed on the [pricing page](\u002Fpricing). There is no setup fee and no monthly minimum, and development instances are free. Transaction fees vary by rail and corridor, so every payin, payout, and transfer quote itemizes the fee before you execute, and the fee is locked for the life of the quote ([billing](\u002Fdocs\u002Flearn\u002Fbilling)). Payouts don't require pre-funding. For how to read a quote line by line, see [stablecoin API pricing](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained).\n\n## What should you ask on the technical evaluation call?\n\nThree questions, and each one exposes a different weak spot.\n\n1. **\"Show me a payout that failed at the receiving bank.\"** Which status did it land in, which webhook fired, and where did the money go? At BlindPay, a payout the bank rejects or returns ends `refunded` and the stablecoins go back to the wallet that funded it. A payout that ends `failed`, for example after a rejected compliance check, does not refund on its own and needs a support follow-up. A vendor that can't draw that line clearly hasn't thought about it.\n2. **\"Can I have the OpenAPI spec and a sandbox key today?\"** If either requires a contract, your evaluation just got two weeks longer.\n3. **\"Which of your listed rails and networks are live in production for a company like mine, and which are beta?\"** Marketing pages list everything. Production access is often narrower, and it can depend on where your company and your customers are based.\n\n## The checklist at a glance\n\n| Criterion | What a good answer looks like | BlindPay |\n| --- | --- | --- |\n| SDKs | Official SDKs in your language, generated from the spec | Node.js, Python, Go, PHP, Swift, plus CLI and MCP server |\n| API design | Public OpenAPI spec, idempotency, signed webhooks, minor units | OpenAPI 3.1, `Idempotency-Key`, Svix-signed webhooks |\n| Abstraction | Bank-shaped and chain-level modes on one engine | Abstracted and Advanced flavors of one API |\n| Networks | EVM, Solana, Stellar, USDC and USDT, testnets | Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Solana, Stellar, Tron |\n| Compliance | KYC, KYB, screening, and review states in the API | KYC in about 60 seconds, KYB in 3 hours to 1 business day |\n| Payout rails | Named rails with published settlement windows | Pix, TED, SPEI, Transfers, ACH COP, ACH, wire, RTP, SEPA, SWIFT (POBO\u002FCOBO) |\n| Pricing | Public plans, itemized quotes, no volume floor | Plans on \u002Fpricing, fee in every quote, no monthly minimum |\n\n## What to do next\n\nRun the checklist against a live sandbox, not a slide deck. Create a free BlindPay development instance, download the spec, and push one payin and one payout through end to end with the [payout quickstart](\u002Fdocs\u002Fquickstart-payout). Then force a failure (a payout quote for $777.00 returns `refunded` in development) and watch what your webhook handler does with it. That hour tells you more than any vendor call.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":3568,"description":4148},"How to choose a blockchain payment API: 7-point checklist","resources\u002Fmore\u002Fhow-to-choose-a-blockchain-payment-api","gEJOi09N3qkJE0NNC7QgZoQYLV9X8s7VY5E-P1Zh9iI",{"id":4173,"title":4174,"authors":6,"body":4175,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1226,"description":4517,"extension":536,"faq":4518,"howto":6,"isBlog":553,"isChangelog":553,"meta":4536,"navigation":556,"path":1184,"pillar":553,"products":6,"rawbody":4537,"role":6,"seo":4538,"seoTitle":4174,"stem":4539,"thumbnail":6,"updated":6,"__hash__":4540},"content\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api.md","How to choose a stablecoin API: the 6 questions that actually matter",{"type":8,"value":4176,"toc":4506},[4177,4180,4186,4190,4228,4232,4235,4238,4241,4245,4248,4251,4264,4268,4271,4274,4281,4285,4288,4291,4298,4302,4305,4308,4316,4320,4323,4326,4333,4337,4437,4441,4444,4452,4458,4468,4473,4484,4493,4502],[11,4178,4179],{},"Choosing a stablecoin API comes down to six questions: does it require pre-funding, does it automate compliance, which local payout rails does it actually cover, how fast do funds become spendable, how good is the developer experience, and is pricing transparent. Answer those six for each vendor and the shortlist writes itself.",[11,4181,4182,4183,329],{},"Most buyer's guides in this category list features. This one lists the questions a technical buyer should ask, why each one matters, and what a good answer looks like, in the order they tend to eliminate vendors. If you are still working out what the category is, start with ",[133,4184,4185],{"href":1283},"what a stablecoin API is",[18,4187,4189],{"id":4188},"the-six-criteria-at-a-glance","The six criteria at a glance",[289,4191,4192,4198,4204,4210,4216,4222],{},[147,4193,4194,4197],{},[150,4195,4196],{},"Pre-funding requirements."," Do you have to park capital in each destination currency before paying anyone?",[147,4199,4200,4203],{},[150,4201,4202],{},"Compliance and KYC\u002FKYB automation."," Do identity, sanctions, and travel rule checks run inside the API, under whose license?",[147,4205,4206,4209],{},[150,4207,4208],{},"Local payout rail coverage."," Which rails are live in production today, in which countries, in which direction?",[147,4211,4212,4215],{},[150,4213,4214],{},"Settlement speed."," When can the receiver actually spend the money?",[147,4217,4218,4221],{},[150,4219,4220],{},"Developer experience and SDK quality."," Is there a public sandbox, an OpenAPI spec, SDKs in your stack, and typed errors?",[147,4223,4224,4227],{},[150,4225,4226],{},"Pricing transparency."," Are fee and FX spread published and itemized, and can you see the receive amount before you commit?",[18,4229,4231],{"id":4230},"_1-does-the-provider-require-pre-funding","1. Does the provider require pre-funding?",[11,4233,4234],{},"Pre-funding matters because it is the single largest hidden cost in cross-border payouts, and it grows in lockstep with your volume.",[11,4236,4237],{},"A provider that settles through pre-funded balances requires you to deposit money in each destination currency before you can send a payment there. If you pay out the equivalent of $3 million a month across four currencies, a one-week float means roughly $700,000 permanently idle, exposed to FX moves, and unavailable for the rest of the business. Finance teams often do not see this as a vendor cost because it does not appear on the invoice.",[11,4239,4240],{},"A good answer is \"no, each transfer is funded when you send it.\" That means you hold your capital in one place, a virtual USD account or a stablecoin treasury wallet, and the provider converts and delivers on demand. Ask the question in writing, because some stablecoin platforms still run pre-funded local balances behind a modern API.",[18,4242,4244],{"id":4243},"_2-does-compliance-run-inside-the-api","2. Does compliance run inside the API?",[11,4246,4247],{},"Compliance automation matters because it determines whether you are connecting to a licensed program or building one yourself.",[11,4249,4250],{},"Every receiver of a cross-border payment has to be identified (KYC for individuals, KYB for businesses), screened against sanctions lists, and in many corridors covered by travel rule data exchange. A provider can either run those checks inside the API before funds move, under its own licenses and registrations, or give you tooling and expect you to hold the license and run the program.",[11,4252,4253,4254,4258,4259,4263],{},"A good answer names the license or registration in each market you pay into, confirms that checks run before money moves rather than after, and explains how the API surfaces a hold or rejection so your system can act on it. Read ",[133,4255,4257],{"href":4256},"\u002Fresources\u002Fmore\u002Fwhat-are-compliance-agents-in-fintech","what compliance agents are in fintech"," for what automated onboarding looks like when it works, and ",[133,4260,4262],{"href":4261},"\u002Fresources\u002Fmore\u002Fautomated-kyc-kyb-vs-manual-onboarding","automated KYC\u002FKYB vs manual onboarding"," for the time and cost gap between the two models.",[18,4265,4267],{"id":4266},"_3-which-local-payout-rails-are-live-in-production","3. Which local payout rails are live in production?",[11,4269,4270],{},"Rail coverage matters because nothing else on this list counts if the provider cannot reach your receivers' bank accounts.",[11,4272,4273],{},"\"Global coverage\" on a homepage usually means the provider can send a SWIFT wire anywhere, which every bank can also do. The question is whether the provider is connected to the local instant rail in each of your markets: Pix in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH and RTP in the United States, SEPA in Europe. Local rails are what make a payout land in seconds instead of days and cost a fraction of a wire.",[11,4275,4276,4277,4280],{},"A good answer is a list of exact rail and country pairs, live in production today, with direction (pay-in, pay-out, or both) and the settlement window per rail. Anything on a roadmap does not count. Check ",[133,4278,4279],{"href":1204},"coverage by country"," for how BlindPay publishes this.",[18,4282,4284],{"id":4283},"_4-how-fast-do-funds-become-spendable","4. How fast do funds become spendable?",[11,4286,4287],{},"Settlement speed matters because the number your receiver cares about is when they can spend the money, not when the API returned a 200.",[11,4289,4290],{},"Stablecoin transfers settle on-chain in seconds to minutes on any modern network. That part is fast everywhere and does not differentiate providers. The differences are in the local leg: Pix and SPEI settle in minutes, ACH and SEPA take one to two business days, SWIFT can take up to five. A provider that quotes \"instant settlement\" is usually describing the on-chain leg only.",[11,4292,4293,4294,4297],{},"A good answer gives you a settlement window per rail, distinguishes API acceptance from finality, and tells you which rails hold for compliance review before releasing. ",[133,4295,4296],{"href":2059},"SLAs and settlement finality"," explains why a 99.9 percent uptime figure says nothing about when money lands.",[18,4299,4301],{"id":4300},"_5-how-good-is-the-developer-experience","5. How good is the developer experience?",[11,4303,4304],{},"Developer experience matters because the sandbox and the error responses are what your engineers will live inside at two in the morning when a payout fails.",[11,4306,4307],{},"The checklist is concrete. A public sandbox you can use before talking to sales. An OpenAPI specification, so you can generate a client or feed it to an AI coding tool. Official SDKs in the languages your team writes. Webhooks with signed payloads and a documented event list. A typed error for every failure mode, so a compliance hold, an expired quote, and an invalid bank account are distinguishable in code. An idempotency key on write requests, so a retry never double-sends money.",[11,4309,4310,4311,4315],{},"A good answer is a link you can click today. If the sandbox requires a sales call, or the docs are a PDF, expect the integration to take weeks instead of days. ",[133,4312,4314],{"href":4313},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Sandbox vs production"," covers what a sandbox can and cannot tell you.",[18,4317,4319],{"id":4318},"_6-is-pricing-transparent","6. Is pricing transparent?",[11,4321,4322],{},"Pricing transparency matters because the FX spread usually costs more than every fee on the pricing page combined, and it is the one number most providers do not publish.",[11,4324,4325],{},"A stablecoin payout has several cost components: a flat or percentage fee, the FX spread between the commercial rate and the rate you get, network costs for the on-chain leg, and sometimes an issuer fee on redemption. A provider that shows one blended number hides which of those is moving when your effective rate changes next quarter.",[11,4327,4328,4329,4332],{},"A good answer is a published pricing page plus a quote response that shows the commercial rate, the provider's rate, the fee, and the receiver amount as separate fields, before you commit. Then run the same $10,000 payment through every vendor's sandbox for your top three corridors and compare what the receiver gets. ",[133,4330,4331],{"href":3982},"Stablecoin API pricing explained"," breaks down where the below-the-line costs hide.",[18,4334,4336],{"id":4335},"scorecard-the-six-questions-to-send-every-vendor","Scorecard: the six questions to send every vendor",[23,4338,4339,4353],{},[26,4340,4341],{},[29,4342,4343,4345,4348,4350],{},[32,4344,4031],{},[32,4346,4347],{},"Question to ask",[32,4349,4034],{},[32,4351,4352],{},"Red flag",[42,4354,4355,4369,4383,4397,4410,4423],{},[29,4356,4357,4360,4363,4366],{},[47,4358,4359],{},"Pre-funding",[47,4361,4362],{},"Do I need to hold a balance in the destination currency before sending?",[47,4364,4365],{},"No, each transfer is funded at send time",[47,4367,4368],{},"\"A small float\" that scales with volume",[29,4370,4371,4374,4377,4380],{},[47,4372,4373],{},"Compliance automation",[47,4375,4376],{},"Who holds the license in each market, and do KYC, KYB, and sanctions checks run before funds move?",[47,4378,4379],{},"Named licenses per market, checks in the API path, holds surfaced as statuses",[47,4381,4382],{},"\"You handle KYC on your side\"",[29,4384,4385,4388,4391,4394],{},[47,4386,4387],{},"Local payout rails",[47,4389,4390],{},"Which exact rail and country pairs are live in production today, in which direction?",[47,4392,4393],{},"A list with settlement window per rail",[47,4395,4396],{},"\"Global coverage\" with no rail names",[29,4398,4399,4401,4404,4407],{},[47,4400,424],{},[47,4402,4403],{},"When can the receiver spend the money on each rail?",[47,4405,4406],{},"Per-rail windows, finality distinguished from API acceptance",[47,4408,4409],{},"\"Instant\" with no rail qualifier",[29,4411,4412,4414,4417,4420],{},[47,4413,942],{},[47,4415,4416],{},"Is there a public sandbox, an OpenAPI spec, SDKs in my language, and signed webhooks?",[47,4418,4419],{},"Links you can open today",[47,4421,4422],{},"Sandbox behind a sales call",[29,4424,4425,4428,4431,4434],{},[47,4426,4427],{},"Pricing transparency",[47,4429,4430],{},"What does the receiver get on a $10,000 payment to my top three corridors?",[47,4432,4433],{},"Itemized quote with rate, spread, fee, and receive amount",[47,4435,4436],{},"One blended rate, quote only by email",[18,4438,4440],{"id":4439},"how-does-blindpay-score-on-the-six-criteria","How does BlindPay score on the six criteria?",[11,4442,4443],{},"Treat this as one entry in your evaluation, not the conclusion of it.",[11,4445,4446,4448,4449,4451],{},[150,4447,2664],{}," None. Each transfer is funded when you send it, from a ",[133,4450,1068],{"href":1067}," or a stablecoin wallet you control.",[11,4453,4454,4457],{},[150,4455,4456],{},"Compliance automation."," KYC, KYB, sanctions screening, and travel rule compliance run inside the API before money moves. Automated compliance agents handle standard individual onboarding in about a minute; business and enhanced cases go through review with a published turnaround.",[11,4459,4460,4463,4464,329],{},[150,4461,4462],{},"Local payout rails."," Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and domestic wire in the United States, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations. Direction and settlement window per rail are published in the ",[133,4465,4467],{"href":4466},"\u002Fdocs\u002Fkb\u002Fpayment-methods","payment methods reference",[11,4469,4470,4472],{},[150,4471,4214],{}," 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. Every payout carries per-step tracking so your system knows whether it is processing, on hold for review, or complete.",[11,4474,4475,4478,4479,4483],{},[150,4476,4477],{},"Developer experience."," REST API with an ",[133,4480,4482],{"href":3634,"rel":4481},[137],"OpenAPI spec",", SDKs for Node, Python, Go, PHP, and Swift, an MCP server for AI coding tools, signed webhooks for every state change, idempotency keys on writes, and a development instance you can use before talking to anyone.",[11,4485,4486,4488,4489,4492],{},[150,4487,4226],{}," ",[133,4490,4491],{"href":967},"Published plans"," and a quote response that returns the commercial rate, BlindPay's rate, the fee, and the receiver amount as separate fields, valid for five minutes, before you commit.",[11,4494,4495,4496,2844,4499,4501],{},"Where BlindPay is not the answer: it does not issue stablecoins, does not offer custody as a product, and is not a card acquirer. Corridor depth is strongest in the Americas. For a side-by-side with the other providers you are likely evaluating, read ",[133,4497,4498],{"href":1248},"the best stablecoin APIs for cross-border payments",[133,4500,2849],{"href":2589}," and run the scorecard yourself.",[11,4503,4504],{},[1210,4505,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":4507},[4508,4509,4510,4511,4512,4513,4514,4515,4516],{"id":4188,"depth":520,"text":4189},{"id":4230,"depth":520,"text":4231},{"id":4243,"depth":520,"text":4244},{"id":4266,"depth":520,"text":4267},{"id":4283,"depth":520,"text":4284},{"id":4300,"depth":520,"text":4301},{"id":4318,"depth":520,"text":4319},{"id":4335,"depth":520,"text":4336},{"id":4439,"depth":520,"text":4440},"Six criteria for evaluating a stablecoin API: pre-funding, compliance automation, local payout rails, settlement speed, developer experience, and pricing transparency, with a scorecard you can send to every vendor.",[4519,4522,4525,4528,4531,4533],{"q":4520,"a":4521},"What should I look for in a stablecoin API?","Six things: whether it requires pre-funding, whether KYC, KYB, and sanctions screening run inside the API, which local payout rails are live in production, how fast funds become spendable, the quality of the sandbox, SDKs, and error responses, and whether pricing and FX spread are published and itemized.",{"q":4523,"a":4524},"Why does pre-funding matter when choosing a stablecoin API?","Pre-funding is capital you must park in each destination currency before you can pay anyone there. It is dead money exposed to FX moves, and it scales with your volume. A provider that funds each transfer at send time removes that cost entirely.",{"q":4526,"a":4527},"How do I compare stablecoin API pricing?","Ask each provider for the exact amount the receiver gets on the same payment in your top three corridors. Fees, spread, and network costs all collapse into that one number, and it is the only figure that is comparable across vendors. A low advertised fee with a wide spread is not cheap.",{"q":4529,"a":4530},"Does a stablecoin API handle compliance for me?","It depends on the provider. Some run KYC, KYB, sanctions screening, and travel rule checks inside the API under their own licenses. Others give you tooling and expect you to run the program. Ask who holds the license in each market and whether checks run before funds move.",{"q":1781,"a":4532},"With a public sandbox, an OpenAPI spec, and an SDK in your language, a first payout typically takes a day or two of engineering. Without those, expect weeks. Production access adds compliance onboarding, usually a few business days.",{"q":4534,"a":4535},"Is the fastest stablecoin API always the best choice?","No. On-chain settlement is fast everywhere. What differs is the local payout leg and whether the provider covers your corridors at all. A provider that settles in seconds on Pix but has no Mexico rail is the wrong choice if half your volume goes to Mexico.",{"author":555},"---\ntitle: \"How to choose a stablecoin API: the 6 questions that actually matter\"\nseoTitle: \"How to choose a stablecoin API: the 6 questions that actually matter\"\ndescription: \"Six criteria for evaluating a stablecoin API: pre-funding, compliance automation, local payout rails, settlement speed, developer experience, and pricing transparency, with a scorecard you can send to every vendor.\"\ndate: \"2026-09-17\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What should I look for in a stablecoin API?\"\n    a: \"Six things: whether it requires pre-funding, whether KYC, KYB, and sanctions screening run inside the API, which local payout rails are live in production, how fast funds become spendable, the quality of the sandbox, SDKs, and error responses, and whether pricing and FX spread are published and itemized.\"\n  - q: \"Why does pre-funding matter when choosing a stablecoin API?\"\n    a: \"Pre-funding is capital you must park in each destination currency before you can pay anyone there. It is dead money exposed to FX moves, and it scales with your volume. A provider that funds each transfer at send time removes that cost entirely.\"\n  - q: \"How do I compare stablecoin API pricing?\"\n    a: \"Ask each provider for the exact amount the receiver gets on the same payment in your top three corridors. Fees, spread, and network costs all collapse into that one number, and it is the only figure that is comparable across vendors. A low advertised fee with a wide spread is not cheap.\"\n  - q: \"Does a stablecoin API handle compliance for me?\"\n    a: \"It depends on the provider. Some run KYC, KYB, sanctions screening, and travel rule checks inside the API under their own licenses. Others give you tooling and expect you to run the program. Ask who holds the license in each market and whether checks run before funds move.\"\n  - q: \"How long does it take to integrate a stablecoin API?\"\n    a: \"With a public sandbox, an OpenAPI spec, and an SDK in your language, a first payout typically takes a day or two of engineering. Without those, expect weeks. Production access adds compliance onboarding, usually a few business days.\"\n  - q: \"Is the fastest stablecoin API always the best choice?\"\n    a: \"No. On-chain settlement is fast everywhere. What differs is the local payout leg and whether the provider covers your corridors at all. A provider that settles in seconds on Pix but has no Mexico rail is the wrong choice if half your volume goes to Mexico.\"\n---\n\nChoosing a stablecoin API comes down to six questions: does it require pre-funding, does it automate compliance, which local payout rails does it actually cover, how fast do funds become spendable, how good is the developer experience, and is pricing transparent. Answer those six for each vendor and the shortlist writes itself.\n\nMost buyer's guides in this category list features. This one lists the questions a technical buyer should ask, why each one matters, and what a good answer looks like, in the order they tend to eliminate vendors. If you are still working out what the category is, start with [what a stablecoin API is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api).\n\n## The six criteria at a glance\n\n1. **Pre-funding requirements.** Do you have to park capital in each destination currency before paying anyone?\n2. **Compliance and KYC\u002FKYB automation.** Do identity, sanctions, and travel rule checks run inside the API, under whose license?\n3. **Local payout rail coverage.** Which rails are live in production today, in which countries, in which direction?\n4. **Settlement speed.** When can the receiver actually spend the money?\n5. **Developer experience and SDK quality.** Is there a public sandbox, an OpenAPI spec, SDKs in your stack, and typed errors?\n6. **Pricing transparency.** Are fee and FX spread published and itemized, and can you see the receive amount before you commit?\n\n## 1. Does the provider require pre-funding?\n\nPre-funding matters because it is the single largest hidden cost in cross-border payouts, and it grows in lockstep with your volume.\n\nA provider that settles through pre-funded balances requires you to deposit money in each destination currency before you can send a payment there. If you pay out the equivalent of $3 million a month across four currencies, a one-week float means roughly $700,000 permanently idle, exposed to FX moves, and unavailable for the rest of the business. Finance teams often do not see this as a vendor cost because it does not appear on the invoice.\n\nA good answer is \"no, each transfer is funded when you send it.\" That means you hold your capital in one place, a virtual USD account or a stablecoin treasury wallet, and the provider converts and delivers on demand. Ask the question in writing, because some stablecoin platforms still run pre-funded local balances behind a modern API.\n\n## 2. Does compliance run inside the API?\n\nCompliance automation matters because it determines whether you are connecting to a licensed program or building one yourself.\n\nEvery receiver of a cross-border payment has to be identified (KYC for individuals, KYB for businesses), screened against sanctions lists, and in many corridors covered by travel rule data exchange. A provider can either run those checks inside the API before funds move, under its own licenses and registrations, or give you tooling and expect you to hold the license and run the program.\n\nA good answer names the license or registration in each market you pay into, confirms that checks run before money moves rather than after, and explains how the API surfaces a hold or rejection so your system can act on it. Read [what compliance agents are in fintech](\u002Fresources\u002Fmore\u002Fwhat-are-compliance-agents-in-fintech) for what automated onboarding looks like when it works, and [automated KYC\u002FKYB vs manual onboarding](\u002Fresources\u002Fmore\u002Fautomated-kyc-kyb-vs-manual-onboarding) for the time and cost gap between the two models.\n\n## 3. Which local payout rails are live in production?\n\nRail coverage matters because nothing else on this list counts if the provider cannot reach your receivers' bank accounts.\n\n\"Global coverage\" on a homepage usually means the provider can send a SWIFT wire anywhere, which every bank can also do. The question is whether the provider is connected to the local instant rail in each of your markets: Pix in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH and RTP in the United States, SEPA in Europe. Local rails are what make a payout land in seconds instead of days and cost a fraction of a wire.\n\nA good answer is a list of exact rail and country pairs, live in production today, with direction (pay-in, pay-out, or both) and the settlement window per rail. Anything on a roadmap does not count. Check [coverage by country](\u002Fdocs\u002Fkb\u002Fsupported-countries) for how BlindPay publishes this.\n\n## 4. How fast do funds become spendable?\n\nSettlement speed matters because the number your receiver cares about is when they can spend the money, not when the API returned a 200.\n\nStablecoin transfers settle on-chain in seconds to minutes on any modern network. That part is fast everywhere and does not differentiate providers. The differences are in the local leg: Pix and SPEI settle in minutes, ACH and SEPA take one to two business days, SWIFT can take up to five. A provider that quotes \"instant settlement\" is usually describing the on-chain leg only.\n\nA good answer gives you a settlement window per rail, distinguishes API acceptance from finality, and tells you which rails hold for compliance review before releasing. [SLAs and settlement finality](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality) explains why a 99.9 percent uptime figure says nothing about when money lands.\n\n## 5. How good is the developer experience?\n\nDeveloper experience matters because the sandbox and the error responses are what your engineers will live inside at two in the morning when a payout fails.\n\nThe checklist is concrete. A public sandbox you can use before talking to sales. An OpenAPI specification, so you can generate a client or feed it to an AI coding tool. Official SDKs in the languages your team writes. Webhooks with signed payloads and a documented event list. A typed error for every failure mode, so a compliance hold, an expired quote, and an invalid bank account are distinguishable in code. An idempotency key on write requests, so a retry never double-sends money.\n\nA good answer is a link you can click today. If the sandbox requires a sales call, or the docs are a PDF, expect the integration to take weeks instead of days. [Sandbox vs production](\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production) covers what a sandbox can and cannot tell you.\n\n## 6. Is pricing transparent?\n\nPricing transparency matters because the FX spread usually costs more than every fee on the pricing page combined, and it is the one number most providers do not publish.\n\nA stablecoin payout has several cost components: a flat or percentage fee, the FX spread between the commercial rate and the rate you get, network costs for the on-chain leg, and sometimes an issuer fee on redemption. A provider that shows one blended number hides which of those is moving when your effective rate changes next quarter.\n\nA good answer is a published pricing page plus a quote response that shows the commercial rate, the provider's rate, the fee, and the receiver amount as separate fields, before you commit. Then run the same $10,000 payment through every vendor's sandbox for your top three corridors and compare what the receiver gets. [Stablecoin API pricing explained](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) breaks down where the below-the-line costs hide.\n\n## Scorecard: the six questions to send every vendor\n\n| Criterion | Question to ask | What a good answer looks like | Red flag |\n| --- | --- | --- | --- |\n| Pre-funding | Do I need to hold a balance in the destination currency before sending? | No, each transfer is funded at send time | \"A small float\" that scales with volume |\n| Compliance automation | Who holds the license in each market, and do KYC, KYB, and sanctions checks run before funds move? | Named licenses per market, checks in the API path, holds surfaced as statuses | \"You handle KYC on your side\" |\n| Local payout rails | Which exact rail and country pairs are live in production today, in which direction? | A list with settlement window per rail | \"Global coverage\" with no rail names |\n| Settlement speed | When can the receiver spend the money on each rail? | Per-rail windows, finality distinguished from API acceptance | \"Instant\" with no rail qualifier |\n| Developer experience | Is there a public sandbox, an OpenAPI spec, SDKs in my language, and signed webhooks? | Links you can open today | Sandbox behind a sales call |\n| Pricing transparency | What does the receiver get on a $10,000 payment to my top three corridors? | Itemized quote with rate, spread, fee, and receive amount | One blended rate, quote only by email |\n\n## How does BlindPay score on the six criteria?\n\nTreat this as one entry in your evaluation, not the conclusion of it.\n\n**Pre-funding.** None. Each transfer is funded when you send it, from a [virtual USD account](\u002Fvirtual-accounts) or a stablecoin wallet you control.\n\n**Compliance automation.** KYC, KYB, sanctions screening, and travel rule compliance run inside the API before money moves. Automated compliance agents handle standard individual onboarding in about a minute; business and enhanced cases go through review with a published turnaround.\n\n**Local payout rails.** Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH in Colombia, Transfers 3.0 in Argentina, ACH, RTP, and domestic wire in the United States, SEPA in Europe, and SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations. Direction and settlement window per rail are published in the [payment methods reference](\u002Fdocs\u002Fkb\u002Fpayment-methods).\n\n**Settlement speed.** 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. Every payout carries per-step tracking so your system knows whether it is processing, on hold for review, or complete.\n\n**Developer experience.** REST API with an [OpenAPI spec](https:\u002F\u002Fapi.blindpay.com\u002Fdoc), SDKs for Node, Python, Go, PHP, and Swift, an MCP server for AI coding tools, signed webhooks for every state change, idempotency keys on writes, and a development instance you can use before talking to anyone.\n\n**Pricing transparency.** [Published plans](\u002Fpricing) and a quote response that returns the commercial rate, BlindPay's rate, the fee, and the receiver amount as separate fields, valid for five minutes, before you commit.\n\nWhere BlindPay is not the answer: it does not issue stablecoins, does not offer custody as a product, and is not a card acquirer. Corridor depth is strongest in the Americas. For a side-by-side with the other providers you are likely evaluating, read [the best stablecoin APIs for cross-border payments](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026), or [start in the sandbox](\u002Fdocs\u002Fintroduction) and run the scorecard yourself.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":4174,"description":4517},"resources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","rrSHB8t0GzZm5Jsl5dRA0YgLynqvy0eS9wHpRlqpx38",{"id":4542,"title":4543,"authors":6,"body":4544,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":5194,"description":5195,"extension":536,"faq":5196,"howto":6,"isBlog":553,"isChangelog":553,"meta":5215,"navigation":556,"path":5216,"pillar":553,"products":6,"rawbody":5217,"role":6,"seo":5218,"seoTitle":5219,"stem":5220,"thumbnail":6,"updated":5194,"__hash__":5221},"content\u002Fresources\u002Fmore\u002Fhow-to-evaluate-a-wallet-integration-provider.md","How to evaluate a wallet integration provider: 12-point checklist",{"type":8,"value":4545,"toc":5184},[4546,4549,4556,4560,4563,4566,4602,4606,4609,4808,4815,4819,4822,4854,4858,4861,4923,4927,4935,5010,5013,5017,5020,5087,5090,5094,5097,5100,5153,5163,5166,5168,5171],[11,4547,4548],{},"To choose a wallet integration provider, rank candidates on five things first: the custody model and who can sign without you, chain and stablecoin coverage, local payout rails if money has to reach bank accounts, pricing transparency including pre-funding, and compliance coverage. Then test developer experience in a two-week proof of concept, not a sales demo.",[11,4550,4551,4552,4555],{},"This checklist covers both halves of a wallet stack: the wallet infrastructure that holds and signs, and the payments layer that connects wallets to bank accounts. Many teams evaluate the two separately and discover the gap between them in production. For the payments API alone, ",[133,4553,4554],{"href":4166},"how to choose a blockchain payment API"," goes deeper on SDKs, OpenAPI quality, and abstraction level.",[18,4557,4559],{"id":4558},"how-do-you-choose-a-wallet-integration-provider","How do you choose a wallet integration provider?",[11,4561,4562],{},"Start with the five criteria that are hardest to change after launch, and score the rest in a proof of concept. Custody, coverage, rails, pricing, and compliance shape your architecture and your licensing. Developer experience and support shape your roadmap.",[11,4564,4565],{},"The top five, in order:",[289,4567,4568,4579,4585,4590,4596],{},[147,4569,4570,4573,4574,4578],{},[150,4571,4572],{},"Custody model."," Who holds keys or key shares, and who can sign without you or your users. ",[133,4575,4577],{"href":4576},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets","Custodial vs non-custodial vs MPC wallets"," explains the options.",[147,4580,4581,4584],{},[150,4582,4583],{},"Chain and stablecoin coverage."," Which networks and tokens are live in production today, not on the roadmap.",[147,4586,4587,4589],{},[150,4588,4462],{}," If money has to reach bank accounts, which rails are live in which countries.",[147,4591,4592,4595],{},[150,4593,4594],{},"Pricing transparency and pre-funding."," Whether fees are itemized before execution, and whether you have to park a balance with the provider.",[147,4597,4598,4601],{},[150,4599,4600],{},"Compliance coverage."," Which checks run inside the product, and which licensed entity serves each market.",[18,4603,4605],{"id":4604},"the-12-point-evaluation-checklist","The 12-point evaluation checklist",[11,4607,4608],{},"Send the same twelve questions to every vendor on your shortlist and score the written answers. A good answer is specific and checkable. A weak answer is a promise.",[23,4610,4611,4625],{},[26,4612,4613],{},[29,4614,4615,4618,4620,4623],{},[32,4616,4617],{},"#",[32,4619,4031],{},[32,4621,4622],{},"What to ask",[32,4624,4034],{},[42,4626,4627,4640,4654,4668,4681,4700,4714,4728,4742,4761,4775,4789],{},[29,4628,4629,4632,4634,4637],{},[47,4630,4631],{},"1",[47,4633,1313],{},[47,4635,4636],{},"Who holds the keys or shares, and who can sign without us?",[47,4638,4639],{},"A diagram per product, with custodial and non-custodial products named separately",[29,4641,4642,4645,4648,4651],{},[47,4643,4644],{},"2",[47,4646,4647],{},"Chain coverage",[47,4649,4650],{},"Which chains are live in production, and which signature schemes do you support?",[47,4652,4653],{},"A published matrix of mainnets and matching testnets",[29,4655,4656,4659,4662,4665],{},[47,4657,4658],{},"3",[47,4660,4661],{},"Stablecoin coverage",[47,4663,4664],{},"Which tokens are supported on which chains?",[47,4666,4667],{},"A per-chain token list, with unsupported pairs rejected by a clear error",[29,4669,4670,4673,4675,4678],{},[47,4671,4672],{},"4",[47,4674,4387],{},[47,4676,4677],{},"Which rails are live, in which countries, in production?",[47,4679,4680],{},"Named rails such as Pix, SPEI, ACH, and SEPA, each marked live",[29,4682,4683,4686,4688,4691],{},[47,4684,4685],{},"5",[47,4687,942],{},[47,4689,4690],{},"Is there a REST API, a downloadable OpenAPI spec, SDKs, and a sandbox?",[47,4692,4693,4694,4699],{},"An ",[133,4695,4698],{"href":4696,"rel":4697},"https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0",[137],"OpenAPI 3.1"," spec, SDKs in several languages, and a sandbox with the same states as production",[29,4701,4702,4705,4708,4711],{},[47,4703,4704],{},"6",[47,4706,4707],{},"Pricing and pre-funding",[47,4709,4710],{},"How are fees charged, and must we pre-fund a balance?",[47,4712,4713],{},"Fees itemized in every quote; no pre-funding, or a clear reason for it",[29,4715,4716,4719,4722,4725],{},[47,4717,4718],{},"7",[47,4720,4721],{},"FX and live quotes",[47,4723,4724],{},"How is the rate set, and how long does a quote hold?",[47,4726,4727],{},"A firm quote with an expiry and a visible fee split before execution",[29,4729,4730,4733,4736,4739],{},[47,4731,4732],{},"8",[47,4734,4735],{},"Compliance coverage",[47,4737,4738],{},"Which checks run in the product: KYC, KYB, sanctions, address screening, KYT, Travel Rule?",[47,4740,4741],{},"Named checks with statuses in the API, plus the licensed entity per market",[29,4743,4744,4747,4750,4753],{},[47,4745,4746],{},"9",[47,4748,4749],{},"Security certifications and audits",[47,4751,4752],{},"Which SOC 2 report, which penetration tests, which contract audits?",[47,4754,2183,4755,4760],{},[133,4756,4759],{"href":4757,"rel":4758},"https:\u002F\u002Fwww.aicpa-cima.com\u002Ftopic\u002Faudit-assurance\u002Faudit-and-assurance-greater-than-soc-2",[137],"SOC 2"," Type 2 report under NDA and a recent pentest summary",[29,4762,4763,4766,4769,4772],{},[47,4764,4765],{},"10",[47,4767,4768],{},"Uptime and SLA",[47,4770,4771],{},"What exactly does the SLA measure?",[47,4773,4774],{},"A split between API uptime and settlement timing, and a status history",[29,4776,4777,4780,4783,4786],{},[47,4778,4779],{},"11",[47,4781,4782],{},"Support and migration path",[47,4784,4785],{},"Who answers during an incident, and how do we leave?",[47,4787,4788],{},"A named escalation path, plus key, address, and data export terms in the contract",[29,4790,4791,4794,4797,4800],{},[47,4792,4793],{},"12",[47,4795,4796],{},"AI-agent and MCP tooling",[47,4798,4799],{},"Can coding agents build against the API?",[47,4801,4693,4802,4807],{},[133,4803,4806],{"href":4804,"rel":4805},"https:\u002F\u002Fmodelcontextprotocol.io\u002F",[137],"MCP"," server, agent skills, and docs that load cleanly into an agent",[11,4809,4810,4811,4814],{},"Two items deserve extra time. On item 9, a SOC 2 Type 2 report covers how controls operated over a period, while a Type 1 covers a single date. On item 10, ",[133,4812,4813],{"href":2059},"stablecoin API SLAs"," explains why an API can report high uptime while money is still in flight.",[18,4816,4818],{"id":4817},"what-questions-should-you-ask-in-a-vendor-demo","What questions should you ask in a vendor demo?",[11,4820,4821],{},"Ask the vendor to show each answer live in the sandbox, and to follow up in writing. Demos are built around the happy path, so these ten questions go straight to the other paths:",[289,4823,4824,4827,4830,4833,4836,4839,4842,4845,4848,4851],{},[147,4825,4826],{},"Show me every way a transaction can leave our wallets without our approval.",[147,4828,4829],{},"Walk a failed payout from start to finish: which status, which webhook, and where do the funds end up?",[147,4831,4832],{},"What happens to our funds if you lose a banking partner tomorrow?",[147,4834,4835],{},"Which licensed entity serves each of our corridors, and where can we check it?",[147,4837,4838],{},"Show a quote: the rate, every fee, the expiry, and what happens when it expires.",[147,4840,4841],{},"Do we need to pre-fund a balance, and if so, who holds it and in whose name?",[147,4843,4844],{},"How do we prove a customer controls a wallet address before it receives funds?",[147,4846,4847],{},"What does address screening return, and what happens when an address is flagged?",[147,4849,4850],{},"How do we export our keys, addresses, and transaction history if we leave?",[147,4852,4853],{},"Who do we call during an incident, and how fast do they answer?",[18,4855,4857],{"id":4856},"what-red-flags-should-you-watch-for","What red flags should you watch for?",[11,4859,4860],{},"Red flags are answers that hide cost, custody, or failure behavior. None of them is disqualifying on its own, but each deserves a direct question before you sign:",[144,4862,4863,4873,4884,4890,4896,4902,4912],{},[147,4864,4865,4868,4869,4872],{},[150,4866,4867],{},"Hidden fees."," One blended rate, with no split between FX spread and transaction fee. ",[133,4870,4871],{"href":3982},"Stablecoin API pricing"," shows how to read a quote line by line.",[147,4874,4875,4878,4879,4883],{},[150,4876,4877],{},"Mandatory pre-funding."," A balance you must park with the provider before paying out, with no clear reason. ",[133,4880,4882],{"href":4881},"\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","What no pre-funding means"," covers the alternatives.",[147,4885,4886,4889],{},[150,4887,4888],{},"Unclear custody."," \"Non-custodial\" in the pitch, with no key or share diagram behind it.",[147,4891,4892,4895],{},[150,4893,4894],{},"No real sandbox."," A test environment that only returns success, so failure paths first show up in production.",[147,4897,4898,4901],{},[150,4899,4900],{},"No webhooks, or unsigned ones."," Polling-only status, or payloads you can't verify.",[147,4903,4904,4906,4907,4911],{},[150,4905,2676],{}," A rate set at settlement instead of quoted upfront. ",[133,4908,4910],{"href":4909},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","Stablecoin FX slippage"," explains the difference.",[147,4913,4914,4917,4918,329],{},[150,4915,4916],{},"Unverifiable licenses."," Registrations you can't find on a regulator's public register, such as FinCEN's ",[133,4919,4922],{"href":4920,"rel":4921},"https:\u002F\u002Fwww.fincen.gov\u002Fmsb-registrant-search",[137],"MSB registrant search",[18,4924,4926],{"id":4925},"how-do-different-provider-types-compare","How do different provider types compare?",[11,4928,4929,4930,4934],{},"Wallet integration touches four kinds of providers, and each is best at a different job. Most production stacks combine two of them, usually a wallet provider and a payments layer. ",[133,4931,4933],{"href":4932},"\u002Fresources\u002Fmore\u002Fwallet-api-vs-embedded-wallet-sdk-vs-white-label","Wallet API vs embedded SDK vs white-label"," covers how the wallet side plugs in.",[23,4936,4937,4953],{},[26,4938,4939],{},[29,4940,4941,4944,4947,4950],{},[32,4942,4943],{},"Provider type",[32,4945,4946],{},"Examples",[32,4948,4949],{},"Best at",[32,4951,4952],{},"Usually paired with",[42,4954,4955,4968,4982,4996],{},[29,4956,4957,4960,4962,4965],{},[47,4958,4959],{},"Payout and on\u002Foff-ramp infrastructure",[47,4961,952],{},[47,4963,4964],{},"Converting between bank money and stablecoins: virtual accounts, live quotes, local payouts",[47,4966,4967],{},"A wallet provider, or the customer's own wallet",[29,4969,4970,4973,4976,4979],{},[47,4971,4972],{},"Wallet infrastructure providers",[47,4974,4975],{},"Fireblocks, Circle wallets, Privy, Dfns, Utila",[47,4977,4978],{},"Key management, signing policies, embedded and treasury wallets",[47,4980,4981],{},"A payments layer for bank rails",[29,4983,4984,4987,4990,4993],{},[47,4985,4986],{},"Stablecoin issuers",[47,4988,4989],{},"Circle (USDC), Tether (USDT)",[47,4991,4992],{},"Issuing and redeeming the stablecoin itself",[47,4994,4995],{},"Ramps and payout providers for last-mile delivery",[29,4997,4998,5001,5004,5007],{},[47,4999,5000],{},"Exchanges and ramps",[47,5002,5003],{},"Centralized exchanges, consumer ramp apps",[47,5005,5006],{},"Trading liquidity and retail buying and selling",[47,5008,5009],{},"Wallets for storage and transfers",[11,5011,5012],{},"The categories overlap at the edges. Some wallet providers add fiat connectivity through partners, and some issuers run payout networks. Ask each vendor which job it does itself and which it hands to a partner.",[18,5014,5016],{"id":5015},"how-do-you-run-a-2-week-proof-of-concept","How do you run a 2-week proof of concept?",[11,5018,5019],{},"A proof of concept should run your real flows in the provider's sandbox for ten working days, against success criteria written on day one. The goal is a scorecard, not a feeling.",[289,5021,5022,5028,5034,5040,5046,5057,5063,5069,5075,5081],{},[147,5023,5024,5027],{},[150,5025,5026],{},"Day 1:"," get sandbox access and API keys, and write the success criteria with engineering, product, and compliance.",[147,5029,5030,5033],{},[150,5031,5032],{},"Day 2:"," create test customers and run KYC and KYB, including one rejection.",[147,5035,5036,5039],{},[150,5037,5038],{},"Day 3:"," create or link wallets on your main chain, and prove wallet ownership at registration.",[147,5041,5042,5045],{},[150,5043,5044],{},"Day 4:"," run a pay-in end to end, from bank deposit to stablecoins in the wallet.",[147,5047,5048,5051,5052,5056],{},[150,5049,5050],{},"Day 5:"," run a payout end to end: quote, wallet authorization, execution, and fiat delivery. ",[133,5053,5055],{"href":5054},"\u002Fresources\u002Fmore\u002Fhow-to-add-stablecoin-payments-to-your-wallet-integration","How to add stablecoin payments to your wallet integration"," has the steps.",[147,5058,5059,5062],{},[150,5060,5061],{},"Day 6:"," verify webhook signatures, replay duplicate events, and reconcile against your ledger.",[147,5064,5065,5068],{},[150,5066,5067],{},"Day 7:"," force failures: an expired quote, a failed payout, a refunded payout.",[147,5070,5071,5074],{},[150,5072,5073],{},"Day 8:"," add a second chain or a second payout rail.",[147,5076,5077,5080],{},[150,5078,5079],{},"Day 9:"," compliance and security review: the data collected, the checks visible in the API, the SOC 2 report.",[147,5082,5083,5086],{},[150,5084,5085],{},"Day 10:"," price the setup against your projected volume, score the checklist, and decide.",[11,5088,5089],{},"Success criteria worth writing down: every payment state reached in the sandbox, every failure path landing in the right order state, webhook signatures verified, pricing reproduced from quotes, and written answers to all twelve checklist items.",[18,5091,5093],{"id":5092},"when-is-blindpay-a-good-fit-and-when-is-it-not","When is BlindPay a good fit, and when is it not?",[11,5095,5096],{},"BlindPay fits teams that need wallets connected to bank accounts across borders, with the customer's funds staying in the customer's wallet until a payout executes. It doesn't fit teams that need key management, card acquiring, or a stablecoin of their own.",[11,5098,5099],{},"BlindPay is a good fit when you need:",[144,5101,5102,5108,5114,5120,5129,5138],{},[147,5103,5104,5107],{},[150,5105,5106],{},"Non-custodial cross-border stablecoin flows."," Payouts from external wallets pull only the quoted amount at execution, and BlindPay never holds those wallets' keys. Managed wallets, in beta, cover teams that prefer custody.",[147,5109,5110,5113],{},[150,5111,5112],{},"Virtual accounts."," US bank details per customer, with each deposit converted to USDC or USDT and settled to the linked wallet.",[147,5115,5116,5119],{},[150,5117,5118],{},"Local-currency payouts."," Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), TED, ACH Colombia, and Transfers 3.0. Cross-border wires run as SWIFT payments and collections on behalf of the customer, with UETR tracking and MT103 confirmations.",[147,5121,5122,5125,5126,5128],{},[150,5123,5124],{},"No pre-funding and no volume floor."," Plans are on the ",[133,5127,1688],{"href":967},", with no setup fee and no monthly minimum, and every quote itemizes its fees before execution.",[147,5130,5131,5134,5135,5137],{},[150,5132,5133],{},"Chain coverage."," Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, and Tron, per the ",[133,5136,497],{"href":496}," matrix.",[147,5139,5140,5143,5144,5147,5148,5152],{},[150,5141,5142],{},"Developer and agent tooling."," An OpenAPI 3.1 spec, ",[133,5145,4043],{"href":5146},"\u002Fdocs\u002Fsdks"," for Node.js, Python, Go, PHP, and Swift, an MCP server, agent skills, and a ",[133,5149,5151],{"href":5150},"\u002Fprompts","prompt library"," for coding agents.",[11,5154,5155,5156,5159,5160,5162],{},"BlindPay is registered with FinCEN as a money services business (",[133,5157,5158],{"href":504},"licenses","), and its ",[133,5161,510],{"href":509}," lists SOC 2 Type 2.",[11,5164,5165],{},"BlindPay is not the right fit when you need a stablecoin issuer, card acquiring, a consumer wallet app, or key-management infrastructure for end-user wallets. For those, pick a specialist, and use the table above to see where BlindPay can sit behind it.",[18,5167,2829],{"id":2828},[11,5169,5170],{},"Copy the 12-point table into a spreadsheet, send it to every vendor on your shortlist, including us, and book the two-week proof of concept with the two strongest written answers. Decide on the scorecard, not the demo.",[11,5172,5173,5174,5178,5179,5183],{},"If you're still defining scope, start with ",[133,5175,5177],{"href":5176},"\u002Fresources\u002Fmore\u002Fwhat-is-crypto-wallet-integration","what is crypto wallet integration",", then check your launch plan against the ",[133,5180,5182],{"href":5181},"\u002Fresources\u002Fmore\u002Fcrypto-wallet-compliance-checklist","crypto wallet compliance checklist"," before the first vendor call.",{"title":519,"searchDepth":520,"depth":520,"links":5185},[5186,5187,5188,5189,5190,5191,5192,5193],{"id":4558,"depth":520,"text":4559},{"id":4604,"depth":520,"text":4605},{"id":4817,"depth":520,"text":4818},{"id":4856,"depth":520,"text":4857},{"id":4925,"depth":520,"text":4926},{"id":5015,"depth":520,"text":5016},{"id":5092,"depth":520,"text":5093},{"id":2828,"depth":520,"text":2829},"2026-09-29","A 12-point checklist for choosing a wallet or stablecoin payments provider: custody, chains, rails, pricing, compliance, SOC 2, SLAs, and AI tooling.",[5197,5200,5203,5206,5209,5212],{"q":5198,"a":5199},"How do I choose a crypto wallet integration provider?","Rank candidates on five criteria first: the custody model and who can sign without you, chain and stablecoin coverage, local payout rails if money must reach bank accounts, pricing transparency including pre-funding, and compliance coverage. Then check developer experience, security reports, SLAs, and support in a two-week proof of concept on the provider's sandbox, not in a sales demo.",{"q":5201,"a":5202},"What is the most important criterion for a wallet provider?","The custody model, because it decides who can move the funds, what happens if the provider fails, and which licenses your own company may need. Ask for a diagram of who holds keys or key shares for each product, and who can sign a transaction without you or your users. Every other criterion is easier to fix later than custody.",{"q":5204,"a":5205},"What questions should I ask a wallet provider in a demo?","Ask them to show, not tell: who can sign from your wallets without your approval, a failed payout from start to finish, what happens to your funds if they lose a banking partner, how a quote is priced and how long it holds, and how you would leave. Ask for the answers in writing, with the contract clauses that back them.",{"q":5207,"a":5208},"What are red flags in a stablecoin infrastructure provider?","Fees that only appear as one blended rate, mandatory pre-funding with no clear reason, custody claims without a key diagram, a sandbox that only returns success, no signed webhooks, FX rates set at settlement instead of quoted upfront, and licenses you can't find on a regulator's public register. Any one of these deserves a direct question before you sign.",{"q":5210,"a":5211},"How long should a wallet provider proof of concept take?","Two weeks is enough for most teams. In ten working days you can onboard test customers, link or create wallets on your main chain, run a pay-in and a payout end to end, verify webhooks, force failures and refunds, and add a second chain or rail. Write the success criteria on day one, so the decision on day ten is a scorecard, not a debate.",{"q":5213,"a":5214},"Is BlindPay a wallet provider?","No. BlindPay is the payments layer that connects wallets to bank accounts: virtual accounts, on-ramps and off-ramps, live quotes, and local payouts. It links external wallets without holding their keys and offers managed wallets in beta. For key management across thousands of end-user wallets, pair a wallet infrastructure provider with BlindPay for the bank side.",{"author":555},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-a-wallet-integration-provider","---\ntitle: \"How to evaluate a wallet integration provider: 12-point checklist\"\nseoTitle: \"How to evaluate a wallet integration provider: 12 checks\"\ndescription: \"A 12-point checklist for choosing a wallet or stablecoin payments provider: custody, chains, rails, pricing, compliance, SOC 2, SLAs, and AI tooling.\"\ndate: \"2026-09-29\"\nupdated: \"2026-09-29\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"How do I choose a crypto wallet integration provider?\"\n    a: \"Rank candidates on five criteria first: the custody model and who can sign without you, chain and stablecoin coverage, local payout rails if money must reach bank accounts, pricing transparency including pre-funding, and compliance coverage. Then check developer experience, security reports, SLAs, and support in a two-week proof of concept on the provider's sandbox, not in a sales demo.\"\n  - q: \"What is the most important criterion for a wallet provider?\"\n    a: \"The custody model, because it decides who can move the funds, what happens if the provider fails, and which licenses your own company may need. Ask for a diagram of who holds keys or key shares for each product, and who can sign a transaction without you or your users. Every other criterion is easier to fix later than custody.\"\n  - q: \"What questions should I ask a wallet provider in a demo?\"\n    a: \"Ask them to show, not tell: who can sign from your wallets without your approval, a failed payout from start to finish, what happens to your funds if they lose a banking partner, how a quote is priced and how long it holds, and how you would leave. Ask for the answers in writing, with the contract clauses that back them.\"\n  - q: \"What are red flags in a stablecoin infrastructure provider?\"\n    a: \"Fees that only appear as one blended rate, mandatory pre-funding with no clear reason, custody claims without a key diagram, a sandbox that only returns success, no signed webhooks, FX rates set at settlement instead of quoted upfront, and licenses you can't find on a regulator's public register. Any one of these deserves a direct question before you sign.\"\n  - q: \"How long should a wallet provider proof of concept take?\"\n    a: \"Two weeks is enough for most teams. In ten working days you can onboard test customers, link or create wallets on your main chain, run a pay-in and a payout end to end, verify webhooks, force failures and refunds, and add a second chain or rail. Write the success criteria on day one, so the decision on day ten is a scorecard, not a debate.\"\n  - q: \"Is BlindPay a wallet provider?\"\n    a: \"No. BlindPay is the payments layer that connects wallets to bank accounts: virtual accounts, on-ramps and off-ramps, live quotes, and local payouts. It links external wallets without holding their keys and offers managed wallets in beta. For key management across thousands of end-user wallets, pair a wallet infrastructure provider with BlindPay for the bank side.\"\n---\n\nTo choose a wallet integration provider, rank candidates on five things first: the custody model and who can sign without you, chain and stablecoin coverage, local payout rails if money has to reach bank accounts, pricing transparency including pre-funding, and compliance coverage. Then test developer experience in a two-week proof of concept, not a sales demo.\n\nThis checklist covers both halves of a wallet stack: the wallet infrastructure that holds and signs, and the payments layer that connects wallets to bank accounts. Many teams evaluate the two separately and discover the gap between them in production. For the payments API alone, [how to choose a blockchain payment API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-blockchain-payment-api) goes deeper on SDKs, OpenAPI quality, and abstraction level.\n\n## How do you choose a wallet integration provider?\n\nStart with the five criteria that are hardest to change after launch, and score the rest in a proof of concept. Custody, coverage, rails, pricing, and compliance shape your architecture and your licensing. Developer experience and support shape your roadmap.\n\nThe top five, in order:\n\n1. **Custody model.** Who holds keys or key shares, and who can sign without you or your users. [Custodial vs non-custodial vs MPC wallets](\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets) explains the options.\n2. **Chain and stablecoin coverage.** Which networks and tokens are live in production today, not on the roadmap.\n3. **Local payout rails.** If money has to reach bank accounts, which rails are live in which countries.\n4. **Pricing transparency and pre-funding.** Whether fees are itemized before execution, and whether you have to park a balance with the provider.\n5. **Compliance coverage.** Which checks run inside the product, and which licensed entity serves each market.\n\n## The 12-point evaluation checklist\n\nSend the same twelve questions to every vendor on your shortlist and score the written answers. A good answer is specific and checkable. A weak answer is a promise.\n\n| # | Criterion | What to ask | What a good answer looks like |\n| --- | --- | --- | --- |\n| 1 | Custody model | Who holds the keys or shares, and who can sign without us? | A diagram per product, with custodial and non-custodial products named separately |\n| 2 | Chain coverage | Which chains are live in production, and which signature schemes do you support? | A published matrix of mainnets and matching testnets |\n| 3 | Stablecoin coverage | Which tokens are supported on which chains? | A per-chain token list, with unsupported pairs rejected by a clear error |\n| 4 | Local payout rails | Which rails are live, in which countries, in production? | Named rails such as Pix, SPEI, ACH, and SEPA, each marked live |\n| 5 | Developer experience | Is there a REST API, a downloadable OpenAPI spec, SDKs, and a sandbox? | An [OpenAPI 3.1](https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0) spec, SDKs in several languages, and a sandbox with the same states as production |\n| 6 | Pricing and pre-funding | How are fees charged, and must we pre-fund a balance? | Fees itemized in every quote; no pre-funding, or a clear reason for it |\n| 7 | FX and live quotes | How is the rate set, and how long does a quote hold? | A firm quote with an expiry and a visible fee split before execution |\n| 8 | Compliance coverage | Which checks run in the product: KYC, KYB, sanctions, address screening, KYT, Travel Rule? | Named checks with statuses in the API, plus the licensed entity per market |\n| 9 | Security certifications and audits | Which SOC 2 report, which penetration tests, which contract audits? | A [SOC 2](https:\u002F\u002Fwww.aicpa-cima.com\u002Ftopic\u002Faudit-assurance\u002Faudit-and-assurance-greater-than-soc-2) Type 2 report under NDA and a recent pentest summary |\n| 10 | Uptime and SLA | What exactly does the SLA measure? | A split between API uptime and settlement timing, and a status history |\n| 11 | Support and migration path | Who answers during an incident, and how do we leave? | A named escalation path, plus key, address, and data export terms in the contract |\n| 12 | AI-agent and MCP tooling | Can coding agents build against the API? | An [MCP](https:\u002F\u002Fmodelcontextprotocol.io\u002F) server, agent skills, and docs that load cleanly into an agent |\n\nTwo items deserve extra time. On item 9, a SOC 2 Type 2 report covers how controls operated over a period, while a Type 1 covers a single date. On item 10, [stablecoin API SLAs](\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality) explains why an API can report high uptime while money is still in flight.\n\n## What questions should you ask in a vendor demo?\n\nAsk the vendor to show each answer live in the sandbox, and to follow up in writing. Demos are built around the happy path, so these ten questions go straight to the other paths:\n\n1. Show me every way a transaction can leave our wallets without our approval.\n2. Walk a failed payout from start to finish: which status, which webhook, and where do the funds end up?\n3. What happens to our funds if you lose a banking partner tomorrow?\n4. Which licensed entity serves each of our corridors, and where can we check it?\n5. Show a quote: the rate, every fee, the expiry, and what happens when it expires.\n6. Do we need to pre-fund a balance, and if so, who holds it and in whose name?\n7. How do we prove a customer controls a wallet address before it receives funds?\n8. What does address screening return, and what happens when an address is flagged?\n9. How do we export our keys, addresses, and transaction history if we leave?\n10. Who do we call during an incident, and how fast do they answer?\n\n## What red flags should you watch for?\n\nRed flags are answers that hide cost, custody, or failure behavior. None of them is disqualifying on its own, but each deserves a direct question before you sign:\n\n- **Hidden fees.** One blended rate, with no split between FX spread and transaction fee. [Stablecoin API pricing](\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained) shows how to read a quote line by line.\n- **Mandatory pre-funding.** A balance you must park with the provider before paying out, with no clear reason. [What no pre-funding means](\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts) covers the alternatives.\n- **Unclear custody.** \"Non-custodial\" in the pitch, with no key or share diagram behind it.\n- **No real sandbox.** A test environment that only returns success, so failure paths first show up in production.\n- **No webhooks, or unsigned ones.** Polling-only status, or payloads you can't verify.\n- **Opaque FX.** A rate set at settlement instead of quoted upfront. [Stablecoin FX slippage](\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes) explains the difference.\n- **Unverifiable licenses.** Registrations you can't find on a regulator's public register, such as FinCEN's [MSB registrant search](https:\u002F\u002Fwww.fincen.gov\u002Fmsb-registrant-search).\n\n## How do different provider types compare?\n\nWallet integration touches four kinds of providers, and each is best at a different job. Most production stacks combine two of them, usually a wallet provider and a payments layer. [Wallet API vs embedded SDK vs white-label](\u002Fresources\u002Fmore\u002Fwallet-api-vs-embedded-wallet-sdk-vs-white-label) covers how the wallet side plugs in.\n\n| Provider type | Examples | Best at | Usually paired with |\n| --- | --- | --- | --- |\n| Payout and on\u002Foff-ramp infrastructure | BlindPay | Converting between bank money and stablecoins: virtual accounts, live quotes, local payouts | A wallet provider, or the customer's own wallet |\n| Wallet infrastructure providers | Fireblocks, Circle wallets, Privy, Dfns, Utila | Key management, signing policies, embedded and treasury wallets | A payments layer for bank rails |\n| Stablecoin issuers | Circle (USDC), Tether (USDT) | Issuing and redeeming the stablecoin itself | Ramps and payout providers for last-mile delivery |\n| Exchanges and ramps | Centralized exchanges, consumer ramp apps | Trading liquidity and retail buying and selling | Wallets for storage and transfers |\n\nThe categories overlap at the edges. Some wallet providers add fiat connectivity through partners, and some issuers run payout networks. Ask each vendor which job it does itself and which it hands to a partner.\n\n## How do you run a 2-week proof of concept?\n\nA proof of concept should run your real flows in the provider's sandbox for ten working days, against success criteria written on day one. The goal is a scorecard, not a feeling.\n\n1. **Day 1:** get sandbox access and API keys, and write the success criteria with engineering, product, and compliance.\n2. **Day 2:** create test customers and run KYC and KYB, including one rejection.\n3. **Day 3:** create or link wallets on your main chain, and prove wallet ownership at registration.\n4. **Day 4:** run a pay-in end to end, from bank deposit to stablecoins in the wallet.\n5. **Day 5:** run a payout end to end: quote, wallet authorization, execution, and fiat delivery. [How to add stablecoin payments to your wallet integration](\u002Fresources\u002Fmore\u002Fhow-to-add-stablecoin-payments-to-your-wallet-integration) has the steps.\n6. **Day 6:** verify webhook signatures, replay duplicate events, and reconcile against your ledger.\n7. **Day 7:** force failures: an expired quote, a failed payout, a refunded payout.\n8. **Day 8:** add a second chain or a second payout rail.\n9. **Day 9:** compliance and security review: the data collected, the checks visible in the API, the SOC 2 report.\n10. **Day 10:** price the setup against your projected volume, score the checklist, and decide.\n\nSuccess criteria worth writing down: every payment state reached in the sandbox, every failure path landing in the right order state, webhook signatures verified, pricing reproduced from quotes, and written answers to all twelve checklist items.\n\n## When is BlindPay a good fit, and when is it not?\n\nBlindPay fits teams that need wallets connected to bank accounts across borders, with the customer's funds staying in the customer's wallet until a payout executes. It doesn't fit teams that need key management, card acquiring, or a stablecoin of their own.\n\nBlindPay is a good fit when you need:\n\n- **Non-custodial cross-border stablecoin flows.** Payouts from external wallets pull only the quoted amount at execution, and BlindPay never holds those wallets' keys. Managed wallets, in beta, cover teams that prefer custody.\n- **Virtual accounts.** US bank details per customer, with each deposit converted to USDC or USDT and settled to the linked wallet.\n- **Local-currency payouts.** Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), TED, ACH Colombia, and Transfers 3.0. Cross-border wires run as SWIFT payments and collections on behalf of the customer, with UETR tracking and MT103 confirmations.\n- **No pre-funding and no volume floor.** Plans are on the [pricing page](\u002Fpricing), with no setup fee and no monthly minimum, and every quote itemizes its fees before execution.\n- **Chain coverage.** Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, and Tron, per the [supported chains](\u002Fdocs\u002Fkb\u002Fsupported-chains) matrix.\n- **Developer and agent tooling.** An OpenAPI 3.1 spec, [SDKs](\u002Fdocs\u002Fsdks) for Node.js, Python, Go, PHP, and Swift, an MCP server, agent skills, and a [prompt library](\u002Fprompts) for coding agents.\n\nBlindPay is registered with FinCEN as a money services business ([licenses](\u002Flicenses)), and its [security page](\u002Fsecurity) lists SOC 2 Type 2.\n\nBlindPay is not the right fit when you need a stablecoin issuer, card acquiring, a consumer wallet app, or key-management infrastructure for end-user wallets. For those, pick a specialist, and use the table above to see where BlindPay can sit behind it.\n\n## What to do next\n\nCopy the 12-point table into a spreadsheet, send it to every vendor on your shortlist, including us, and book the two-week proof of concept with the two strongest written answers. Decide on the scorecard, not the demo.\n\nIf you're still defining scope, start with [what is crypto wallet integration](\u002Fresources\u002Fmore\u002Fwhat-is-crypto-wallet-integration), then check your launch plan against the [crypto wallet compliance checklist](\u002Fresources\u002Fmore\u002Fcrypto-wallet-compliance-checklist) before the first vendor call.\n",{"title":4543,"description":5195},"How to evaluate a wallet integration provider: 12 checks","resources\u002Fmore\u002Fhow-to-evaluate-a-wallet-integration-provider","RqkG4zVVtPi95JAKMSmyb3ecj9LUmMaqEtpedGZIu_A",{"id":5223,"title":5224,"authors":6,"body":5225,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":5663,"description":5664,"extension":536,"faq":5665,"howto":6,"isBlog":553,"isChangelog":553,"meta":5680,"navigation":556,"path":5681,"pillar":553,"products":6,"rawbody":5682,"role":6,"seo":5683,"seoTitle":1233,"stem":5684,"thumbnail":6,"updated":6,"__hash__":5685},"content\u002Fresources\u002Fmore\u002Fis-stripe-a-stablecoin-api.md","Is Stripe a stablecoin API? What a payout API, Stripe, and Bridge each do",{"type":8,"value":5226,"toc":5653},[5227,5234,5237,5241,5244,5294,5297,5308,5312,5315,5352,5355,5362,5366,5369,5372,5390,5400,5404,5407,5444,5450,5454,5457,5474,5477,5481,5484,5502,5505,5509,5633,5639,5641,5649],[11,5228,5229,5230,5233],{},"Partly. Stripe lets eligible merchants accept stablecoin payments at checkout and hold stablecoin balances in Stripe financial accounts. Stripe also owns ",[133,5231,1019],{"href":1017,"rel":5232},[137],", which is a full stablecoin infrastructure API. But Stripe by itself is not a standalone cross-border stablecoin payout API, and if your job is \"pay people abroad in their local currency,\" you are really choosing between a dedicated payout API like BlindPay and Bridge.",[11,5235,5236],{},"This question comes up in almost every conversation we have with fintech teams. Makes sense. Stripe is the default payments vendor for most startups, so \"can Stripe just do this?\" is the right first question. Here is the honest answer, product by product.",[18,5238,5240],{"id":5239},"what-does-stripe-offer-with-stablecoins","What does Stripe offer with stablecoins?",[11,5242,5243],{},"Stripe has moved into stablecoins in two ways: its own products and the Bridge acquisition.",[23,5245,5246,5259],{},[26,5247,5248],{},[29,5249,5250,5253,5256],{},[32,5251,5252],{},"Stripe product",[32,5254,5255],{},"What it does",[32,5257,5258],{},"Who it's for",[42,5260,5261,5272,5283],{},[29,5262,5263,5266,5269],{},[47,5264,5265],{},"Stablecoin payments at checkout",[47,5267,5268],{},"Customers pay in USDC; the merchant settles in fiat",[47,5270,5271],{},"Existing Stripe merchants whose buyers hold stablecoins",[29,5273,5274,5277,5280],{},[47,5275,5276],{},"Stablecoin financial accounts",[47,5278,5279],{},"Hold a USD stablecoin balance inside Stripe",[47,5281,5282],{},"Businesses that want a dollar balance without a US bank",[29,5284,5285,5288,5291],{},[47,5286,5287],{},"Bridge (acquired in 2025)",[47,5289,5290],{},"Stablecoin issuance, wallets, conversion, virtual accounts, cards",[47,5292,5293],{},"Teams building stablecoin products, or launching their own stablecoin",[11,5295,5296],{},"Stripe's stablecoin features are gated by account eligibility and region, so check what your account can actually use before you plan around them.",[11,5298,5299,5300,5303,5304,5307],{},"What's interesting here is the direction. Almost everything on the Stripe side is about ",[150,5301,5302],{},"accepting"," money or ",[150,5305,5306],{},"holding"," it. Stripe's core payout rails are still cards and bank transfers. Paying 500 people across Latin America in reais and pesos, with a quote per payout, is a different product.",[18,5309,5311],{"id":5310},"what-does-bridge-add","What does Bridge add?",[11,5313,5314],{},"Bridge is where Stripe's stablecoin infrastructure actually lives. It is a general-purpose stablecoin API:",[144,5316,5317,5323,5329,5335,5340,5346],{},[147,5318,5319,5322],{},[150,5320,5321],{},"Issuance."," Launch your own branded stablecoin.",[147,5324,5325,5328],{},[150,5326,5327],{},"Wallets."," Provider-managed custodial wallets or self-custody.",[147,5330,5331,5334],{},[150,5332,5333],{},"Conversion."," Fiat to stablecoin and back.",[147,5336,5337,5339],{},[150,5338,5112],{}," Accounts in several currencies that receive fiat.",[147,5341,5342,5345],{},[150,5343,5344],{},"Cards."," Stablecoin-backed card programs.",[147,5347,5348,5351],{},[150,5349,5350],{},"Payout rails."," United States, Europe, the United Kingdom, Mexico, Brazil, and Colombia, over ACH, wire, SEPA, Faster Payments, SPEI, and Pix.",[11,5353,5354],{},"If you already run on Stripe and want stablecoin flows next to your card flows, Bridge keeps your vendor count at one. If you want to issue a stablecoin, Bridge is one of the few teams that does it as a service.",[11,5356,5357,5358,329],{},"Pricing goes through a sales process. Bridge has a sandbox and REST docs, with hosted KYC links for onboarding. For a direct capability breakdown, read ",[133,5359,5361],{"href":5360},"\u002Fcompare\u002Fbridge","BlindPay vs Bridge",[18,5363,5365],{"id":5364},"so-what-is-a-stablecoin-api-exactly","So what is a \"stablecoin API,\" exactly?",[11,5367,5368],{},"A stablecoin API moves money through code with stablecoins as the settlement layer: onboard a customer with KYC or KYB, get funds in (a bank transfer or a stablecoin), lock a quote, and deliver local currency to a bank account over the destination country's rail. The sender and receiver never touch crypto unless they want to.",[11,5370,5371],{},"By that definition:",[144,5373,5374,5380,5385],{},[147,5375,5376,5379],{},[150,5377,5378],{},"A payout API"," like BlindPay is a stablecoin API focused on the last mile: stablecoins in, local currency out.",[147,5381,5382,5384],{},[150,5383,998],{}," is a payments platform with stablecoin features.",[147,5386,5387,5389],{},[150,5388,1019],{}," is a stablecoin infrastructure API with a broad surface.",[11,5391,5392,5393,5395,5396,329],{},"For the full category definition, read ",[133,5394,4185],{"href":1283},", and for how it differs from checkout tools, read ",[133,5397,5399],{"href":5398},"\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-crypto-payment-gateway","stablecoin API vs crypto payment gateway",[18,5401,5403],{"id":5402},"when-is-a-dedicated-payout-api-a-better-fit","When is a dedicated payout API a better fit?",[11,5405,5406],{},"A dedicated payout API wins when the job is narrow and the details matter:",[144,5408,5409,5415,5423,5429,5435],{},[147,5410,5411,5414],{},[150,5412,5413],{},"Corridor depth."," Argentina over Transfers 3.0, Colombia over ACH, Brazil over Pix, PIX Safe, and TED, Mexico over SPEI, plus SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations on every wire.",[147,5416,5417,5419,5420,5422],{},[150,5418,2440],{}," Fund each payout when you send it, from your own stablecoin wallet or a ",[133,5421,1068],{"href":1067},", instead of topping up a balance in advance.",[147,5424,5425,5428],{},[150,5426,5427],{},"A binding quote."," Rate, fee, and exact receive amount locked for five minutes before you commit.",[147,5430,5431,5434],{},[150,5432,5433],{},"Published pricing."," Know the cost of a payout before you talk to anyone.",[147,5436,5437,5440,5441,5443],{},[150,5438,5439],{},"Compliance inside the API."," KYC, KYB, and sanctions screening run before money moves, and a hold shows up as an ",[485,5442,487],{}," status instead of a silent delay.",[11,5445,5446,5447,5449],{},"That is the job ",[133,5448,952],{"href":951}," is built for. It is not a card acquirer and it doesn't issue stablecoins, so it doesn't replace Stripe. It sits next to it.",[18,5451,5453],{"id":5452},"when-is-stripe-plus-bridge-the-right-answer","When is Stripe plus Bridge the right answer?",[11,5455,5456],{},"Be fair about it. Stripe plus Bridge is a strong choice when:",[144,5458,5459,5462,5465,5468,5471],{},[147,5460,5461],{},"You already process cards on Stripe and want one vendor, one dashboard, one contract.",[147,5463,5464],{},"Your product needs stablecoin checkout next to cards.",[147,5466,5467],{},"You want to issue a branded stablecoin.",[147,5469,5470],{},"Your payout countries are inside Bridge's rail list and you're fine with a custodial wallet model.",[147,5472,5473],{},"You'd rather negotiate pricing with sales than read it off a page.",[11,5475,5476],{},"No reason to add a vendor if that list describes you.",[18,5478,5480],{"id":5479},"a-common-setup-stripe-in-blindpay-out","A common setup: Stripe in, BlindPay out",[11,5482,5483],{},"A lot of teams we work with end up here:",[289,5485,5486,5491,5496],{},[147,5487,5488,5490],{},[150,5489,998],{}," handles card acceptance from customers.",[147,5492,5493,5495],{},[150,5494,952],{}," handles payouts to sellers, contractors, or suppliers abroad, in their local currency.",[147,5497,5498,5501],{},[150,5499,5500],{},"Virtual USD accounts"," on BlindPay collect USD from foreign customers by ACH, wire, or SWIFT and convert it to USDC or USDT automatically.",[11,5503,5504],{},"Two vendors, zero overlap. Each one does the part it's built for.",[18,5506,5508],{"id":5507},"how-do-they-compare-at-a-glance","How do they compare at a glance?",[23,5510,5511,5523],{},[26,5512,5513],{},[29,5514,5515,5517,5519,5521],{},[32,5516],{},[32,5518,952],{},[32,5520,998],{},[32,5522,1019],{},[42,5524,5525,5539,5552,5564,5578,5592,5605,5620],{},[29,5526,5527,5530,5533,5536],{},[47,5528,5529],{},"Primary job",[47,5531,5532],{},"Stablecoin payouts and collections",[47,5534,5535],{},"Card and bank payments",[47,5537,5538],{},"Stablecoin infrastructure",[29,5540,5541,5544,5546,5549],{},[47,5542,5543],{},"Stablecoin checkout",[47,5545,958],{},[47,5547,5548],{},"Yes, for eligible merchants",[47,5550,5551],{},"Via Stripe",[29,5553,5554,5557,5559,5561],{},[47,5555,5556],{},"Issue your own stablecoin",[47,5558,958],{},[47,5560,958],{},[47,5562,5563],{},"Yes",[29,5565,5566,5569,5572,5575],{},[47,5567,5568],{},"Stablecoin-settled payouts in LATAM",[47,5570,5571],{},"Brazil, Mexico, Colombia, Argentina",[47,5573,5574],{},"Not a core product",[47,5576,5577],{},"Mexico, Brazil, Colombia",[29,5579,5580,5583,5586,5589],{},[47,5581,5582],{},"SWIFT to 100+ countries",[47,5584,5585],{},"Yes (POBO\u002FCOBO)",[47,5587,5588],{},"Not stablecoin-settled",[47,5590,5591],{},"Not listed on public pages",[29,5593,5594,5596,5599,5602],{},[47,5595,4359],{},[47,5597,5598],{},"Not required",[47,5600,5601],{},"Balance held in Stripe",[47,5603,5604],{},"Funded per flow",[29,5606,5607,5609,5614,5617],{},[47,5608,4111],{},[47,5610,5611],{},[133,5612,5613],{"href":967},"Published",[47,5615,5616],{},"Public for core products",[47,5618,5619],{},"Through sales",[29,5621,5622,5624,5627,5630],{},[47,5623,4043],{},[47,5625,5626],{},"Node, Python, Go, PHP, Swift",[47,5628,5629],{},"Many languages",[47,5631,5632],{},"REST API and docs",[11,5634,5635,5636,329],{},"Products change often. Treat the table as a snapshot and confirm on each provider's site. For a five-way comparison including Circle and Fireblocks, read the ",[133,5637,5638],{"href":1248},"best stablecoin APIs for cross-border payments",[18,5640,2829],{"id":2828},[11,5642,5643,5644,2844,5646,5648],{},"Write down your top three payout corridors and your monthly volume in each. Check whether Stripe's stablecoin features are even enabled on your account. Then run the same $10,000 test payout through each sandbox you're considering and compare one number: what the receiver actually gets. If you want to see ours, create a development instance and run the ",[133,5645,4126],{"href":4125},[133,5647,1190],{"href":1189}," with one corridor.",[11,5650,5651],{},[1210,5652,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":5654},[5655,5656,5657,5658,5659,5660,5661,5662],{"id":5239,"depth":520,"text":5240},{"id":5310,"depth":520,"text":5311},{"id":5364,"depth":520,"text":5365},{"id":5402,"depth":520,"text":5403},{"id":5452,"depth":520,"text":5453},{"id":5479,"depth":520,"text":5480},{"id":5507,"depth":520,"text":5508},{"id":2828,"depth":520,"text":2829},"2026-07-09","Partly. Stripe offers stablecoin checkout and balances, and owns Bridge, a stablecoin infrastructure API. What each covers for cross-border payouts.",[5666,5668,5671,5674,5677],{"q":1233,"a":5667},"Partly. Stripe lets eligible merchants accept stablecoin payments at checkout and hold stablecoin balances in financial accounts. It also owns Bridge, a full stablecoin infrastructure API for issuance, wallets, conversion, and virtual accounts. Stripe on its own is not a standalone cross-border stablecoin payout API.",{"q":5669,"a":5670},"What is the difference between Stripe and Bridge?","Stripe is a card and bank payments platform that has added stablecoin features for its merchants. Bridge, acquired by Stripe in 2025, is a separate stablecoin infrastructure API: stablecoin issuance, custodial and self-custody wallets, fiat-to-stablecoin conversion, virtual accounts, and cards, with payout rails in the US, Europe, the UK, Mexico, Brazil, and Colombia.",{"q":5672,"a":5673},"Can I send cross-border payouts in stablecoins with Stripe?","Depends on your account, region, and the product. Stripe's stablecoin features are gated by eligibility, and its core payout rails are cards and bank transfers. For stablecoin-settled payouts to bank accounts in local currency, teams usually use Bridge or a dedicated payout API such as BlindPay.",{"q":5675,"a":5676},"When is a dedicated stablecoin payout API a better fit than Stripe?","When the job is paying people abroad in local currency, in corridors like Brazil, Mexico, Colombia, and Argentina, without pre-funding, with a quoted receive amount before you commit, and with published pricing. That is the problem a payout API like BlindPay is built for.",{"q":5678,"a":5679},"Can I use Stripe and BlindPay together?","Yes. Many teams keep Stripe for card acceptance and use BlindPay for cross-border payouts and USD collection through virtual accounts. The two do not overlap on the payout side.",{"author":555},"\u002Fresources\u002Fmore\u002Fis-stripe-a-stablecoin-api","---\ntitle: \"Is Stripe a stablecoin API? What a payout API, Stripe, and Bridge each do\"\nseoTitle: \"Is Stripe a stablecoin API?\"\ndescription: \"Partly. Stripe offers stablecoin checkout and balances, and owns Bridge, a stablecoin infrastructure API. What each covers for cross-border payouts.\"\ndate: \"2026-07-09\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is Stripe a stablecoin API?\"\n    a: \"Partly. Stripe lets eligible merchants accept stablecoin payments at checkout and hold stablecoin balances in financial accounts. It also owns Bridge, a full stablecoin infrastructure API for issuance, wallets, conversion, and virtual accounts. Stripe on its own is not a standalone cross-border stablecoin payout API.\"\n  - q: \"What is the difference between Stripe and Bridge?\"\n    a: \"Stripe is a card and bank payments platform that has added stablecoin features for its merchants. Bridge, acquired by Stripe in 2025, is a separate stablecoin infrastructure API: stablecoin issuance, custodial and self-custody wallets, fiat-to-stablecoin conversion, virtual accounts, and cards, with payout rails in the US, Europe, the UK, Mexico, Brazil, and Colombia.\"\n  - q: \"Can I send cross-border payouts in stablecoins with Stripe?\"\n    a: \"Depends on your account, region, and the product. Stripe's stablecoin features are gated by eligibility, and its core payout rails are cards and bank transfers. For stablecoin-settled payouts to bank accounts in local currency, teams usually use Bridge or a dedicated payout API such as BlindPay.\"\n  - q: \"When is a dedicated stablecoin payout API a better fit than Stripe?\"\n    a: \"When the job is paying people abroad in local currency, in corridors like Brazil, Mexico, Colombia, and Argentina, without pre-funding, with a quoted receive amount before you commit, and with published pricing. That is the problem a payout API like BlindPay is built for.\"\n  - q: \"Can I use Stripe and BlindPay together?\"\n    a: \"Yes. Many teams keep Stripe for card acceptance and use BlindPay for cross-border payouts and USD collection through virtual accounts. The two do not overlap on the payout side.\"\n---\n\nPartly. Stripe lets eligible merchants accept stablecoin payments at checkout and hold stablecoin balances in Stripe financial accounts. Stripe also owns [Bridge](https:\u002F\u002Fwww.bridge.xyz), which is a full stablecoin infrastructure API. But Stripe by itself is not a standalone cross-border stablecoin payout API, and if your job is \"pay people abroad in their local currency,\" you are really choosing between a dedicated payout API like BlindPay and Bridge.\n\nThis question comes up in almost every conversation we have with fintech teams. Makes sense. Stripe is the default payments vendor for most startups, so \"can Stripe just do this?\" is the right first question. Here is the honest answer, product by product.\n\n## What does Stripe offer with stablecoins?\n\nStripe has moved into stablecoins in two ways: its own products and the Bridge acquisition.\n\n| Stripe product | What it does | Who it's for |\n| --- | --- | --- |\n| Stablecoin payments at checkout | Customers pay in USDC; the merchant settles in fiat | Existing Stripe merchants whose buyers hold stablecoins |\n| Stablecoin financial accounts | Hold a USD stablecoin balance inside Stripe | Businesses that want a dollar balance without a US bank |\n| Bridge (acquired in 2025) | Stablecoin issuance, wallets, conversion, virtual accounts, cards | Teams building stablecoin products, or launching their own stablecoin |\n\nStripe's stablecoin features are gated by account eligibility and region, so check what your account can actually use before you plan around them.\n\nWhat's interesting here is the direction. Almost everything on the Stripe side is about **accepting** money or **holding** it. Stripe's core payout rails are still cards and bank transfers. Paying 500 people across Latin America in reais and pesos, with a quote per payout, is a different product.\n\n## What does Bridge add?\n\nBridge is where Stripe's stablecoin infrastructure actually lives. It is a general-purpose stablecoin API:\n\n- **Issuance.** Launch your own branded stablecoin.\n- **Wallets.** Provider-managed custodial wallets or self-custody.\n- **Conversion.** Fiat to stablecoin and back.\n- **Virtual accounts.** Accounts in several currencies that receive fiat.\n- **Cards.** Stablecoin-backed card programs.\n- **Payout rails.** United States, Europe, the United Kingdom, Mexico, Brazil, and Colombia, over ACH, wire, SEPA, Faster Payments, SPEI, and Pix.\n\nIf you already run on Stripe and want stablecoin flows next to your card flows, Bridge keeps your vendor count at one. If you want to issue a stablecoin, Bridge is one of the few teams that does it as a service.\n\nPricing goes through a sales process. Bridge has a sandbox and REST docs, with hosted KYC links for onboarding. For a direct capability breakdown, read [BlindPay vs Bridge](\u002Fcompare\u002Fbridge).\n\n## So what is a \"stablecoin API,\" exactly?\n\nA stablecoin API moves money through code with stablecoins as the settlement layer: onboard a customer with KYC or KYB, get funds in (a bank transfer or a stablecoin), lock a quote, and deliver local currency to a bank account over the destination country's rail. The sender and receiver never touch crypto unless they want to.\n\nBy that definition:\n\n- **A payout API** like BlindPay is a stablecoin API focused on the last mile: stablecoins in, local currency out.\n- **Stripe** is a payments platform with stablecoin features.\n- **Bridge** is a stablecoin infrastructure API with a broad surface.\n\nFor the full category definition, read [what a stablecoin API is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api), and for how it differs from checkout tools, read [stablecoin API vs crypto payment gateway](\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-crypto-payment-gateway).\n\n## When is a dedicated payout API a better fit?\n\nA dedicated payout API wins when the job is narrow and the details matter:\n\n- **Corridor depth.** Argentina over Transfers 3.0, Colombia over ACH, Brazil over Pix, PIX Safe, and TED, Mexico over SPEI, plus SWIFT (POBO\u002FCOBO) to 100+ countries with UETR tracking and MT103 confirmations on every wire.\n- **No pre-funding.** Fund each payout when you send it, from your own stablecoin wallet or a [virtual USD account](\u002Fvirtual-accounts), instead of topping up a balance in advance.\n- **A binding quote.** Rate, fee, and exact receive amount locked for five minutes before you commit.\n- **Published pricing.** Know the cost of a payout before you talk to anyone.\n- **Compliance inside the API.** KYC, KYB, and sanctions screening run before money moves, and a hold shows up as an `on_hold` status instead of a silent delay.\n\nThat is the job [BlindPay](\u002Fglobal-payments) is built for. It is not a card acquirer and it doesn't issue stablecoins, so it doesn't replace Stripe. It sits next to it.\n\n## When is Stripe plus Bridge the right answer?\n\nBe fair about it. Stripe plus Bridge is a strong choice when:\n\n- You already process cards on Stripe and want one vendor, one dashboard, one contract.\n- Your product needs stablecoin checkout next to cards.\n- You want to issue a branded stablecoin.\n- Your payout countries are inside Bridge's rail list and you're fine with a custodial wallet model.\n- You'd rather negotiate pricing with sales than read it off a page.\n\nNo reason to add a vendor if that list describes you.\n\n## A common setup: Stripe in, BlindPay out\n\nA lot of teams we work with end up here:\n\n1. **Stripe** handles card acceptance from customers.\n2. **BlindPay** handles payouts to sellers, contractors, or suppliers abroad, in their local currency.\n3. **Virtual USD accounts** on BlindPay collect USD from foreign customers by ACH, wire, or SWIFT and convert it to USDC or USDT automatically.\n\nTwo vendors, zero overlap. Each one does the part it's built for.\n\n## How do they compare at a glance?\n\n|  | BlindPay | Stripe | Bridge |\n| --- | --- | --- | --- |\n| Primary job | Stablecoin payouts and collections | Card and bank payments | Stablecoin infrastructure |\n| Stablecoin checkout | No | Yes, for eligible merchants | Via Stripe |\n| Issue your own stablecoin | No | No | Yes |\n| Stablecoin-settled payouts in LATAM | Brazil, Mexico, Colombia, Argentina | Not a core product | Mexico, Brazil, Colombia |\n| SWIFT to 100+ countries | Yes (POBO\u002FCOBO) | Not stablecoin-settled | Not listed on public pages |\n| Pre-funding | Not required | Balance held in Stripe | Funded per flow |\n| Pricing | [Published](\u002Fpricing) | Public for core products | Through sales |\n| SDKs | Node, Python, Go, PHP, Swift | Many languages | REST API and docs |\n\nProducts change often. Treat the table as a snapshot and confirm on each provider's site. For a five-way comparison including Circle and Fireblocks, read the [best stablecoin APIs for cross-border payments](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026).\n\n## What to do next\n\nWrite down your top three payout corridors and your monthly volume in each. Check whether Stripe's stablecoin features are even enabled on your account. Then run the same $10,000 test payout through each sandbox you're considering and compare one number: what the receiver actually gets. If you want to see ours, create a development instance and run the [payout quickstart](\u002Fdocs\u002Fquickstart-payout), or [talk to us](\u002Fcontact) with one corridor.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5224,"description":5664},"resources\u002Fmore\u002Fis-stripe-a-stablecoin-api","vwuNdtgLdyjyB1r5cfPIfcVnHfmnzWLTM9f7L4FWMyo",{"id":5687,"title":5688,"authors":6,"body":5689,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1768,"description":5837,"extension":536,"faq":5838,"howto":6,"isBlog":553,"isChangelog":553,"meta":5851,"navigation":556,"path":5852,"pillar":553,"products":6,"rawbody":5853,"role":6,"seo":5854,"seoTitle":5688,"stem":5855,"thumbnail":6,"updated":1787,"__hash__":5856},"content\u002Fresources\u002Fmore\u002Fis-xrp-a-stablecoin.md","Is XRP a stablecoin? No, and here is the difference",{"type":8,"value":5690,"toc":5829},[5691,5694,5703,5707,5710,5713,5716,5720,5723,5743,5751,5755,5763,5768,5772,5775,5792,5799,5803,5806,5812,5816,5825],[11,5692,5693],{},"No, XRP is not a stablecoin. XRP is a free-floating cryptocurrency: its price is set by market supply and demand and can move sharply in a day. A stablecoin is the opposite by design, pegged to a fixed value (almost always one US dollar) and backed by reserves that make the peg credible. XRP has no peg and no reserves backing a fixed price.",[11,5695,5696,5697,5702],{},"The confusion is understandable, and it spiked when Ripple, the company most associated with XRP, launched an actual stablecoin. As of 2026, XRP remains one of the largest cryptocurrencies by market value according to public trackers like ",[133,5698,5701],{"href":5699,"rel":5700},"https:\u002F\u002Fcoinmarketcap.com\u002F",[137],"CoinMarketCap",", while stablecoins as a category exceed 200 billion dollars in circulating supply. They are different tools.",[18,5704,5706],{"id":5705},"what-is-xrp-then","What is XRP, then?",[11,5708,5709],{},"XRP is the native asset of the XRP Ledger, a blockchain launched in 2012 and designed for fast, cheap transfers. Transactions settle in a few seconds for fractions of a cent. Ripple has long promoted XRP as a bridge asset for cross-border payments: convert currency A into XRP, move it, convert into currency B.",[11,5711,5712],{},"The mechanism works, but it carries a property no treasurer wants: the bridge asset's price floats. Between the moment funds enter XRP and the moment they leave, the amount of value can change. Payments infrastructure exists to remove uncertainty, not add it.",[11,5714,5715],{},"Put numbers on it: XRP has moved more than 10 percent in a single day many times in its history, and double-digit weekly swings are routine in crypto markets. A 100,000 dollar payout bridged through an asset that moves 2 percent during processing is a 2,000 dollar surprise, in either direction. A stablecoin's designed daily move is zero, and its worst recorded deviations (a few cents, for days, during banking crises) are smaller than a floating asset's normal afternoon.",[18,5717,5719],{"id":5718},"what-makes-something-a-stablecoin","What makes something a stablecoin?",[11,5721,5722],{},"Three things, all absent in XRP:",[144,5724,5725,5731,5737],{},[147,5726,5727,5730],{},[150,5728,5729],{},"A peg."," The token targets a fixed value, one US dollar for USDC and USDT.",[147,5732,5733,5736],{},[150,5734,5735],{},"Reserves."," The issuer holds assets (cash, short-term US Treasuries) matching the tokens in circulation.",[147,5738,5739,5742],{},[150,5740,5741],{},"Redemption."," Holders can redeem tokens for the underlying dollars, which is what keeps the market price at the peg.",[11,5744,5745,5746,5748,5749,498],{},"Our ",[133,5747,1280],{"href":1279}," guide covers the mechanics in depth, and regulation now formalizes these properties: frameworks like MiCA and the US GENIUS Act define payment stablecoins by exactly these requirements (see the ",[133,5750,2802],{"href":1663},[18,5752,5754],{"id":5753},"what-is-rlusd-ripples-actual-stablecoin","What is RLUSD, Ripple's actual stablecoin?",[11,5756,5757,5762],{},[133,5758,5761],{"href":5759,"rel":5760},"https:\u002F\u002Fripple.com\u002Fsolutions\u002Fstablecoin\u002F",[137],"RLUSD (Ripple USD)"," is a dollar stablecoin Ripple launched in December 2024, issued under a New York Department of Financial Services trust charter and backed by dollar deposits and US Treasuries. It runs on both the XRP Ledger and Ethereum.",[11,5764,5765,5766,329],{},"RLUSD is the clearest evidence for this article's answer: if XRP were a stablecoin, Ripple would not have needed to launch one. XRP is the floating network asset; RLUSD is the pegged payment asset. In payments practice, RLUSD is a small newcomer next to USDC and USDT, whose tradeoffs we compare in ",[133,5767,177],{"href":176},[18,5769,5771],{"id":5770},"why-does-the-difference-matter-for-payments","Why does the difference matter for payments?",[11,5773,5774],{},"Take a real flow: a US business pays a contractor in Brazil.",[144,5776,5777,5783],{},[147,5778,5779,5782],{},[150,5780,5781],{},"Through a floating asset:"," dollars buy XRP, XRP moves, XRP sells for reais. Two market trades, price exposure in between, and unpredictable slippage on size.",[147,5784,5785,5788,5789,5791],{},[150,5786,5787],{},"Through a stablecoin:"," dollars become USDC one-to-one, USDC moves, USDC converts to reais at a quoted FX rate and pays out over Pix in seconds. The only variable is the fiat exchange rate, which is quoted upfront, as on our live ",[133,5790,1073],{"href":1072}," page.",[11,5793,5794,5795,5798],{},"Predictability is the product. That is why business payment infrastructure standardized on stablecoins, and why the interesting questions are now about providers and rails rather than bridge assets: our ",[133,5796,5797],{"href":516},"stablecoin payments guide"," covers exactly that ground.",[18,5800,5802],{"id":5801},"do-banks-and-payment-companies-actually-use-xrp","Do banks and payment companies actually use XRP?",[11,5804,5805],{},"Ripple's enterprise product history is instructive. Its early bank partnerships mostly used Ripple's messaging and settlement software without touching XRP at all. The XRP-based product (on-demand liquidity, since folded into Ripple Payments) found real use in some remittance corridors, but adoption stayed narrow while stablecoin payment volume grew into the trillions per year. By 2024 Ripple itself entered the stablecoin market with RLUSD, and in 2025 pursued a US national bank charter for its stablecoin business.",[11,5807,5808,5809,329],{},"The market's verdict is visible in that sequence: institutions wanted the always-on settlement rails, but they wanted them denominated in something that does not move. That something turned out to be the fully reserved dollar token, and today the practical infrastructure question is not \"which bridge asset\" but \"which provider and rails\", the subject of our ",[133,5810,5811],{"href":916},"stablecoin API provider comparison",[18,5813,5815],{"id":5814},"how-does-blindpay-fit-in","How does BlindPay fit in?",[11,5817,5818,5820,5821,5824],{},[133,5819,952],{"href":951}," is a stablecoin API for global payments: businesses convert USDC and USDT to local fiat over rails like Pix, SPEI, ACH, and wire in 100+ countries, with compliance built in and ",[133,5822,5823],{"href":967},"flat published pricing",". No floating bridge assets anywhere in the flow, which is precisely the point.",[11,5826,5827],{},[1210,5828,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":5830},[5831,5832,5833,5834,5835,5836],{"id":5705,"depth":520,"text":5706},{"id":5718,"depth":520,"text":5719},{"id":5753,"depth":520,"text":5754},{"id":5770,"depth":520,"text":5771},{"id":5801,"depth":520,"text":5802},{"id":5814,"depth":520,"text":5815},"XRP is not a stablecoin: its price floats freely with the market. Ripple's actual stablecoin is RLUSD. Here is how the two differ and why it matters.",[5839,5842,5845,5848],{"q":5840,"a":5841},"Is XRP a stablecoin?","No. XRP is a free-floating cryptocurrency whose price moves with supply and demand. A stablecoin is pegged to a fixed value, usually one US dollar, and backed by reserves. XRP has neither a peg nor reserves.",{"q":5843,"a":5844},"What is Ripple's stablecoin?","RLUSD (Ripple USD), launched by Ripple in late 2024. It is a dollar-pegged, reserve-backed stablecoin issued under a New York trust charter, and it is a separate asset from XRP.",{"q":5846,"a":5847},"Why do people confuse XRP with stablecoins?","Both are marketed for payments and settlement. XRP is used as a bridge asset in some cross-border flows, which sounds similar to how stablecoins are used, but XRP's price can change during the transfer while a stablecoin's cannot.",{"q":5849,"a":5850},"Which is better for payments, XRP or a stablecoin?","For holding and moving a known amount of value, stablecoins. Price stability is the property that makes a payment asset predictable; a floating asset adds exchange-rate risk to every minute it is held.",{"author":555},"\u002Fresources\u002Fmore\u002Fis-xrp-a-stablecoin","---\ntitle: \"Is XRP a stablecoin? No, and here is the difference\"\nseoTitle: \"Is XRP a stablecoin? No, and here is the difference\"\ndescription: \"XRP is not a stablecoin: its price floats freely with the market. Ripple's actual stablecoin is RLUSD. Here is how the two differ and why it matters.\"\ndate: \"2026-08-15\"\nupdated: \"2026-09-01\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is XRP a stablecoin?\"\n    a: \"No. XRP is a free-floating cryptocurrency whose price moves with supply and demand. A stablecoin is pegged to a fixed value, usually one US dollar, and backed by reserves. XRP has neither a peg nor reserves.\"\n  - q: \"What is Ripple's stablecoin?\"\n    a: \"RLUSD (Ripple USD), launched by Ripple in late 2024. It is a dollar-pegged, reserve-backed stablecoin issued under a New York trust charter, and it is a separate asset from XRP.\"\n  - q: \"Why do people confuse XRP with stablecoins?\"\n    a: \"Both are marketed for payments and settlement. XRP is used as a bridge asset in some cross-border flows, which sounds similar to how stablecoins are used, but XRP's price can change during the transfer while a stablecoin's cannot.\"\n  - q: \"Which is better for payments, XRP or a stablecoin?\"\n    a: \"For holding and moving a known amount of value, stablecoins. Price stability is the property that makes a payment asset predictable; a floating asset adds exchange-rate risk to every minute it is held.\"\n---\n\nNo, XRP is not a stablecoin. XRP is a free-floating cryptocurrency: its price is set by market supply and demand and can move sharply in a day. A stablecoin is the opposite by design, pegged to a fixed value (almost always one US dollar) and backed by reserves that make the peg credible. XRP has no peg and no reserves backing a fixed price.\n\nThe confusion is understandable, and it spiked when Ripple, the company most associated with XRP, launched an actual stablecoin. As of 2026, XRP remains one of the largest cryptocurrencies by market value according to public trackers like [CoinMarketCap](https:\u002F\u002Fcoinmarketcap.com\u002F), while stablecoins as a category exceed 200 billion dollars in circulating supply. They are different tools.\n\n## What is XRP, then?\n\nXRP is the native asset of the XRP Ledger, a blockchain launched in 2012 and designed for fast, cheap transfers. Transactions settle in a few seconds for fractions of a cent. Ripple has long promoted XRP as a bridge asset for cross-border payments: convert currency A into XRP, move it, convert into currency B.\n\nThe mechanism works, but it carries a property no treasurer wants: the bridge asset's price floats. Between the moment funds enter XRP and the moment they leave, the amount of value can change. Payments infrastructure exists to remove uncertainty, not add it.\n\nPut numbers on it: XRP has moved more than 10 percent in a single day many times in its history, and double-digit weekly swings are routine in crypto markets. A 100,000 dollar payout bridged through an asset that moves 2 percent during processing is a 2,000 dollar surprise, in either direction. A stablecoin's designed daily move is zero, and its worst recorded deviations (a few cents, for days, during banking crises) are smaller than a floating asset's normal afternoon.\n\n## What makes something a stablecoin?\n\nThree things, all absent in XRP:\n\n- **A peg.** The token targets a fixed value, one US dollar for USDC and USDT.\n- **Reserves.** The issuer holds assets (cash, short-term US Treasuries) matching the tokens in circulation.\n- **Redemption.** Holders can redeem tokens for the underlying dollars, which is what keeps the market price at the peg.\n\nOur [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin) guide covers the mechanics in depth, and regulation now formalizes these properties: frameworks like MiCA and the US GENIUS Act define payment stablecoins by exactly these requirements (see the [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026)).\n\n## What is RLUSD, Ripple's actual stablecoin?\n\n[RLUSD (Ripple USD)](https:\u002F\u002Fripple.com\u002Fsolutions\u002Fstablecoin\u002F) is a dollar stablecoin Ripple launched in December 2024, issued under a New York Department of Financial Services trust charter and backed by dollar deposits and US Treasuries. It runs on both the XRP Ledger and Ethereum.\n\nRLUSD is the clearest evidence for this article's answer: if XRP were a stablecoin, Ripple would not have needed to launch one. XRP is the floating network asset; RLUSD is the pegged payment asset. In payments practice, RLUSD is a small newcomer next to USDC and USDT, whose tradeoffs we compare in [USDC vs USDT for payments](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments).\n\n## Why does the difference matter for payments?\n\nTake a real flow: a US business pays a contractor in Brazil.\n\n- **Through a floating asset:** dollars buy XRP, XRP moves, XRP sells for reais. Two market trades, price exposure in between, and unpredictable slippage on size.\n- **Through a stablecoin:** dollars become USDC one-to-one, USDC moves, USDC converts to reais at a quoted FX rate and pays out over Pix in seconds. The only variable is the fiat exchange rate, which is quoted upfront, as on our live [USDC to BRL](\u002Fusdc-to-brl) page.\n\nPredictability is the product. That is why business payment infrastructure standardized on stablecoins, and why the interesting questions are now about providers and rails rather than bridge assets: our [stablecoin payments guide](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide) covers exactly that ground.\n\n## Do banks and payment companies actually use XRP?\n\nRipple's enterprise product history is instructive. Its early bank partnerships mostly used Ripple's messaging and settlement software without touching XRP at all. The XRP-based product (on-demand liquidity, since folded into Ripple Payments) found real use in some remittance corridors, but adoption stayed narrow while stablecoin payment volume grew into the trillions per year. By 2024 Ripple itself entered the stablecoin market with RLUSD, and in 2025 pursued a US national bank charter for its stablecoin business.\n\nThe market's verdict is visible in that sequence: institutions wanted the always-on settlement rails, but they wanted them denominated in something that does not move. That something turned out to be the fully reserved dollar token, and today the practical infrastructure question is not \"which bridge asset\" but \"which provider and rails\", the subject of our [stablecoin API provider comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026).\n\n## How does BlindPay fit in?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API for global payments: businesses convert USDC and USDT to local fiat over rails like Pix, SPEI, ACH, and wire in 100+ countries, with compliance built in and [flat published pricing](\u002Fpricing). No floating bridge assets anywhere in the flow, which is precisely the point.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5688,"description":5837},"resources\u002Fmore\u002Fis-xrp-a-stablecoin","8VOUj8Tc7U1f7bsgW-cJicRVGyX7QYhB_WdPYLoZimM",{"id":5858,"title":5859,"authors":6,"body":5860,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":5968,"description":5969,"extension":536,"faq":5970,"howto":6,"isBlog":553,"isChangelog":553,"meta":5989,"navigation":556,"path":3982,"pillar":553,"products":6,"rawbody":5990,"role":6,"seo":5991,"seoTitle":5859,"stem":5992,"thumbnail":6,"updated":6,"__hash__":5993},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained.md","Stablecoin API pricing: mint fees, spread, and what you actually pay",{"type":8,"value":5861,"toc":5961},[5862,5865,5869,5878,5884,5887,5890,5893,5896,5900,5908,5911,5918,5922,5925,5928,5932,5935,5942,5946,5949],[11,5863,5864],{},"A mint fee of zero looks generous until the redemption fee shows up three lines down the same schedule. Zero Hash's own fee schedule is the clearest public example of why a headline rate and the actual invoice rarely match.",[18,5866,5868],{"id":5867},"stablecoin-api-pricing-comes-in-three-shapes","Stablecoin API pricing comes in three shapes",[11,5870,5871,5872,5877],{},"A 2026 comparison of major providers, a support-article listicle rather than an industry report or any single company's own pricing page, groups ",[133,5873,5876],{"href":5874,"rel":5875},"https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15232572-best-stablecoin-settlement-apis-2026-sla-guarantees-audit-trails-and-reconciliation-compared",[137],"stablecoin API pricing into three shapes",": volume-tiered take rate, per-transaction-plus-gas, and flat enterprise contract.",[11,5879,5880,5881,5883],{},"BlindPay publishes itemized quotes per corridor instead of a blended rate or a sales-only contract; see the ",[133,5882,1688],{"href":967}," for the current numbers.",[11,5885,5886],{},"Volume-tiered take rate is what most consumer-facing platforms use: a percentage per transaction that compresses as monthly volume grows. This shape rewards scale and punishes small integrations, since a low-volume developer pays near the top of a provider's published range while a large one negotiates down.",[11,5888,5889],{},"Circle prices closer to a flat per-call fee, with network gas passed through separately as its own line, a shape usually called per-transaction-plus-gas. The effective rate depends on network congestion as much as on the provider's own pricing sheet, and it can swing week to week for reasons that have nothing to do with the integration itself.",[11,5891,5892],{},"Flat enterprise contract is the shape Eco, BVNK, and Fireblocks lean toward for larger customers: a negotiated monthly or annual fee independent of transaction count, with the number only surfacing after a sales conversation, which makes it the least useful shape for a developer trying to compare options early.",[11,5894,5895],{},"None of these is objectively cheaper. A high-volume payments company probably wants the tiered rate because it compresses with scale. A team running unpredictable, spiky volume through a handful of chains might prefer the gas-plus-fee model because it doesn't punish quiet months. What matters is knowing which shape is being quoted before comparing it to anything else: a 0.3 percent take rate and a \"$0.02 per call plus gas\" quote aren't the same kind of number, and they don't compress the same way as volume grows.",[18,5897,5899],{"id":5898},"why-does-minting-cost-nothing-but-redeeming-cost-something","Why does minting cost nothing but redeeming cost something?",[11,5901,5902,5907],{},[133,5903,5906],{"href":5904,"rel":5905},"https:\u002F\u002Fdocs.zerohash.com\u002Fdocs\u002Fissuer-fees",[137],"Zero Hash's documentation"," lists 0 basis points to mint across seven supported stablecoins: DAI, TUSD, USDC, USDT, USDP, PYUSD, and RLUSD. Minting, in plain terms, is depositing fiat and receiving stablecoin back. It's free at the issuer level across the board.",[11,5909,5910],{},"Burning is the reverse: converting the stablecoin back into fiat, and that's where the fee shows up. Zero Hash charges 5 basis points specifically on USDC redemption, across every network it supports. The platform sitting on top of Zero Hash can then layer its own spread on top of that issuer fee, the docs' own worked examples run anywhere from 10 to 50 basis points depending on the scenario, and can choose whether to pass the issuer fee to the end customer or absorb it.",[11,5912,5913,5914,5917],{},"An issuer wants stablecoin supply to grow, so there's no reason to tax the deposit side. Redemption is the step that actually costs money to process on the issuer's end, since it means converting the token back to fiat and moving real dollars, so that's where the fee sits. Comparing only the mint-side rate a provider quotes means comparing the free half of the transaction and ignoring the half that actually costs something. This is the same asymmetry that makes ",[133,5915,5916],{"href":1283},"stablecoin API"," pricing pages harder to read than they look: the number on the landing page is usually the cheap half of the flow.",[18,5919,5921],{"id":5920},"what-should-a-quote-response-actually-itemize","What should a quote response actually itemize?",[11,5923,5924],{},"Zero Hash's quote response returns issuer_fee_rate, issuer_fee_amount, spread_notional, and spread_bps as four separate fields. That's the standard worth asking every provider to match: it's the only way to tell what's actually changing when a rate moves. If a provider raises its take rate next quarter, an itemized quote shows whether that's the issuer fee moving (out of the platform's control) or the platform's own spread widening (very much in its control).",[11,5926,5927],{},"One blended rate doesn't automatically mean overcharging. It might be cheaper. But that's not verifiable from the API response alone, and there's no way to build alerting or reconciliation against a number that can't be decomposed. Zero Hash's docs also note that the only supported settlement_type is \"STANDARD,\" described as instant settlement, so at least on that provider there's no separate tier to price against: the itemization is about fees more than settlement speed.",[18,5929,5931],{"id":5930},"how-do-you-compare-two-providers-on-the-same-corridor-same-day","How do you compare two providers on the same corridor, same day?",[11,5933,5934],{},"Almost nobody publishes a dated, reproducible quote for a specific corridor and a specific amount. Pricing pages show ranges, sales calls produce numbers that expire the moment the call ends, and aggregator comparisons average across providers in ways that erase exactly the detail that matters for a given integration. Conduit's FX pricing is sometimes cited around 10 basis points in industry writeups, and even that number comes through a third-party aggregator rather than a dated quote that could be reproduced directly. That figure could not be independently verified against Conduit's own current pricing documentation, which is itself the point: transparent, reproducible pricing is rare enough in this space that even finding a citable number takes real digging.",[11,5936,5937,5938,5941],{},"A real comparison holds the same notional amount, the same day (FX and spread both move daily), the same network the transfer settles on (gas depends on chain and congestion), and itemized fees rather than a blended total. Without holding all four constant, the comparison is really between marketing copy from different months. The ",[133,5939,5940],{"href":916},"best stablecoin APIs comparison"," applies this same standard across providers side by side.",[18,5943,5945],{"id":5944},"get-an-itemized-quote-instead-of-a-headline-rate","Get an itemized quote instead of a headline rate",[11,5947,5948],{},"A BlindPay quote splits the FX spread from the payout fee into two numbers, showing what the conversion costs and what the transfer costs separately, and which one moved when a rate changes. There's no pre-funding requirement sitting underneath any of it, either: no capital needs to sit parked in a destination account before a payout clears, which erases trapped capital as a cost, something a lot of pricing comparisons skip because it never shows up as a line item at all.",[11,5950,5951,5952,5954,5955,5958,5959,329],{},"For a corridor like ",[133,5953,1073],{"href":1072},", or for payin and payout flows more broadly, the ",[133,5956,5957],{"href":2589},"getting started guide"," walks through what a live quote actually returns, field by field. Pull a same-day quote against the real volume and corridor before trusting any published rate, including this one, and to get the fees broken out against a real amount, ",[133,5960,1190],{"href":1189},{"title":519,"searchDepth":520,"depth":520,"links":5962},[5963,5964,5965,5966,5967],{"id":5867,"depth":520,"text":5868},{"id":5898,"depth":520,"text":5899},{"id":5920,"depth":520,"text":5921},{"id":5930,"depth":520,"text":5931},{"id":5944,"depth":520,"text":5945},"2026-08-31","The basis-point figure on a stablecoin provider's pricing page rarely matches the invoice, because mint fees, burn fees, spread, and issuer fees usually live below the line the marketing page shows.",[5971,5974,5977,5980,5983,5986],{"q":5972,"a":5973},"What pricing models do stablecoin API providers actually use?","A volume-tiered take rate charges a percentage of each transaction that compresses as monthly volume grows. Per-transaction-plus-gas charges a flat or small fee per call and passes network gas through separately, so cost swings with whichever chain a transfer settles on. A flat enterprise contract sets a negotiated monthly or annual fee regardless of volume, common with larger platforms serving bigger institutional clients. Which one is cheapest depends entirely on volume and how predictable the bill needs to be.",{"q":5975,"a":5976},"What does Zero Hash charge to mint versus redeem a stablecoin?","Zero Hash's published fee schedule shows exactly this asymmetry: minting, turning fiat into stablecoin, costs 0 basis points across the seven stablecoins it lists, while turning USDC back into fiat costs 5 basis points on every network Zero Hash supports. An issuer wants stablecoin supply to grow, so minting carries no built-in friction. Redemption is the step that costs the issuer money to process, since it means converting the token back into real dollars, and that's where the fee sits.",{"q":5978,"a":5979},"Which fields does Zero Hash break out in a quote response?","Zero Hash's API returns issuer_fee_rate, issuer_fee_amount, spread_notional, and spread_bps as four distinct fields in every quote, rather than folding everything into one blended rate. A single blended number doesn't show whether a rate move next quarter comes from the issuer fee, which the platform doesn't control, or from the platform's own spread, which it does. That distinction is invisible without the itemized breakdown.",{"q":5981,"a":5982},"What four variables need to match before comparing two providers' pricing?","Hold the notional amount, the day (FX and spread move daily), the settlement network (gas depends on chain and congestion), and the fee breakdown constant, then compare itemized numbers rather than blended totals. Almost no provider publishes a dated quote that could be reproduced later, which is what makes this hard rather than just inconvenient. Ask each provider for a live quote against the same amount and pair on the same day, and insist on separate issuer fee, spread, and network cost figures before comparing the total.",{"q":5984,"a":5985},"Is a lower advertised basis-point rate always the cheaper option?","A provider advertising 20 basis points but charging a separate redemption fee, a wider spread on the FX leg, and gas as a pass-through can land above a provider quoting 40 basis points all-in with nothing else attached. The headline number alone doesn't show which one that is. Request the itemized breakdown for the actual corridor and volume before comparing totals.",{"q":5987,"a":5988},"Does BlindPay require pre-funding before it will quote or settle a payment?","BlindPay returns a live FX quote with the spread and payout fee itemized separately and settles without requiring capital held in advance in a destination account. That's a structural difference from providers that need funds pre-positioned in local accounts before a payout can clear.",{},"---\ntitle: \"Stablecoin API pricing: mint fees, spread, and what you actually pay\"\nseoTitle: \"Stablecoin API pricing: mint fees, spread, and what you actually pay\"\ndescription: \"The basis-point figure on a stablecoin provider's pricing page rarely matches the invoice, because mint fees, burn fees, spread, and issuer fees usually live below the line the marketing page shows.\"\ndate: \"2026-08-31\"\ncategory: \"stablecoins\"\nfaq:\n  - q: \"What pricing models do stablecoin API providers actually use?\"\n    a: \"A volume-tiered take rate charges a percentage of each transaction that compresses as monthly volume grows. Per-transaction-plus-gas charges a flat or small fee per call and passes network gas through separately, so cost swings with whichever chain a transfer settles on. A flat enterprise contract sets a negotiated monthly or annual fee regardless of volume, common with larger platforms serving bigger institutional clients. Which one is cheapest depends entirely on volume and how predictable the bill needs to be.\"\n  - q: \"What does Zero Hash charge to mint versus redeem a stablecoin?\"\n    a: \"Zero Hash's published fee schedule shows exactly this asymmetry: minting, turning fiat into stablecoin, costs 0 basis points across the seven stablecoins it lists, while turning USDC back into fiat costs 5 basis points on every network Zero Hash supports. An issuer wants stablecoin supply to grow, so minting carries no built-in friction. Redemption is the step that costs the issuer money to process, since it means converting the token back into real dollars, and that's where the fee sits.\"\n  - q: \"Which fields does Zero Hash break out in a quote response?\"\n    a: \"Zero Hash's API returns issuer_fee_rate, issuer_fee_amount, spread_notional, and spread_bps as four distinct fields in every quote, rather than folding everything into one blended rate. A single blended number doesn't show whether a rate move next quarter comes from the issuer fee, which the platform doesn't control, or from the platform's own spread, which it does. That distinction is invisible without the itemized breakdown.\"\n  - q: \"What four variables need to match before comparing two providers' pricing?\"\n    a: \"Hold the notional amount, the day (FX and spread move daily), the settlement network (gas depends on chain and congestion), and the fee breakdown constant, then compare itemized numbers rather than blended totals. Almost no provider publishes a dated quote that could be reproduced later, which is what makes this hard rather than just inconvenient. Ask each provider for a live quote against the same amount and pair on the same day, and insist on separate issuer fee, spread, and network cost figures before comparing the total.\"\n  - q: \"Is a lower advertised basis-point rate always the cheaper option?\"\n    a: \"A provider advertising 20 basis points but charging a separate redemption fee, a wider spread on the FX leg, and gas as a pass-through can land above a provider quoting 40 basis points all-in with nothing else attached. The headline number alone doesn't show which one that is. Request the itemized breakdown for the actual corridor and volume before comparing totals.\"\n  - q: \"Does BlindPay require pre-funding before it will quote or settle a payment?\"\n    a: \"BlindPay returns a live FX quote with the spread and payout fee itemized separately and settles without requiring capital held in advance in a destination account. That's a structural difference from providers that need funds pre-positioned in local accounts before a payout can clear.\"\n---\n\nA mint fee of zero looks generous until the redemption fee shows up three lines down the same schedule. Zero Hash's own fee schedule is the clearest public example of why a headline rate and the actual invoice rarely match.\n\n## Stablecoin API pricing comes in three shapes\n\nA 2026 comparison of major providers, a support-article listicle rather than an industry report or any single company's own pricing page, groups [stablecoin API pricing into three shapes](https:\u002F\u002Feco.com\u002Fsupport\u002Fen\u002Farticles\u002F15232572-best-stablecoin-settlement-apis-2026-sla-guarantees-audit-trails-and-reconciliation-compared): volume-tiered take rate, per-transaction-plus-gas, and flat enterprise contract.\n\nBlindPay publishes itemized quotes per corridor instead of a blended rate or a sales-only contract; see the [pricing page](\u002Fpricing) for the current numbers.\n\nVolume-tiered take rate is what most consumer-facing platforms use: a percentage per transaction that compresses as monthly volume grows. This shape rewards scale and punishes small integrations, since a low-volume developer pays near the top of a provider's published range while a large one negotiates down.\n\nCircle prices closer to a flat per-call fee, with network gas passed through separately as its own line, a shape usually called per-transaction-plus-gas. The effective rate depends on network congestion as much as on the provider's own pricing sheet, and it can swing week to week for reasons that have nothing to do with the integration itself.\n\nFlat enterprise contract is the shape Eco, BVNK, and Fireblocks lean toward for larger customers: a negotiated monthly or annual fee independent of transaction count, with the number only surfacing after a sales conversation, which makes it the least useful shape for a developer trying to compare options early.\n\nNone of these is objectively cheaper. A high-volume payments company probably wants the tiered rate because it compresses with scale. A team running unpredictable, spiky volume through a handful of chains might prefer the gas-plus-fee model because it doesn't punish quiet months. What matters is knowing which shape is being quoted before comparing it to anything else: a 0.3 percent take rate and a \"$0.02 per call plus gas\" quote aren't the same kind of number, and they don't compress the same way as volume grows.\n\n## Why does minting cost nothing but redeeming cost something?\n\n[Zero Hash's documentation](https:\u002F\u002Fdocs.zerohash.com\u002Fdocs\u002Fissuer-fees) lists 0 basis points to mint across seven supported stablecoins: DAI, TUSD, USDC, USDT, USDP, PYUSD, and RLUSD. Minting, in plain terms, is depositing fiat and receiving stablecoin back. It's free at the issuer level across the board.\n\nBurning is the reverse: converting the stablecoin back into fiat, and that's where the fee shows up. Zero Hash charges 5 basis points specifically on USDC redemption, across every network it supports. The platform sitting on top of Zero Hash can then layer its own spread on top of that issuer fee, the docs' own worked examples run anywhere from 10 to 50 basis points depending on the scenario, and can choose whether to pass the issuer fee to the end customer or absorb it.\n\nAn issuer wants stablecoin supply to grow, so there's no reason to tax the deposit side. Redemption is the step that actually costs money to process on the issuer's end, since it means converting the token back to fiat and moving real dollars, so that's where the fee sits. Comparing only the mint-side rate a provider quotes means comparing the free half of the transaction and ignoring the half that actually costs something. This is the same asymmetry that makes [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) pricing pages harder to read than they look: the number on the landing page is usually the cheap half of the flow.\n\n## What should a quote response actually itemize?\n\nZero Hash's quote response returns issuer_fee_rate, issuer_fee_amount, spread_notional, and spread_bps as four separate fields. That's the standard worth asking every provider to match: it's the only way to tell what's actually changing when a rate moves. If a provider raises its take rate next quarter, an itemized quote shows whether that's the issuer fee moving (out of the platform's control) or the platform's own spread widening (very much in its control).\n\nOne blended rate doesn't automatically mean overcharging. It might be cheaper. But that's not verifiable from the API response alone, and there's no way to build alerting or reconciliation against a number that can't be decomposed. Zero Hash's docs also note that the only supported settlement_type is \"STANDARD,\" described as instant settlement, so at least on that provider there's no separate tier to price against: the itemization is about fees more than settlement speed.\n\n## How do you compare two providers on the same corridor, same day?\n\nAlmost nobody publishes a dated, reproducible quote for a specific corridor and a specific amount. Pricing pages show ranges, sales calls produce numbers that expire the moment the call ends, and aggregator comparisons average across providers in ways that erase exactly the detail that matters for a given integration. Conduit's FX pricing is sometimes cited around 10 basis points in industry writeups, and even that number comes through a third-party aggregator rather than a dated quote that could be reproduced directly. That figure could not be independently verified against Conduit's own current pricing documentation, which is itself the point: transparent, reproducible pricing is rare enough in this space that even finding a citable number takes real digging.\n\nA real comparison holds the same notional amount, the same day (FX and spread both move daily), the same network the transfer settles on (gas depends on chain and congestion), and itemized fees rather than a blended total. Without holding all four constant, the comparison is really between marketing copy from different months. The [best stablecoin APIs comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026) applies this same standard across providers side by side.\n\n## Get an itemized quote instead of a headline rate\n\nA BlindPay quote splits the FX spread from the payout fee into two numbers, showing what the conversion costs and what the transfer costs separately, and which one moved when a rate changes. There's no pre-funding requirement sitting underneath any of it, either: no capital needs to sit parked in a destination account before a payout clears, which erases trapped capital as a cost, something a lot of pricing comparisons skip because it never shows up as a line item at all.\n\nFor a corridor like [USDC to BRL](\u002Fusdc-to-brl), or for payin and payout flows more broadly, the [getting started guide](\u002Fdocs\u002Fintroduction) walks through what a live quote actually returns, field by field. Pull a same-day quote against the real volume and corridor before trusting any published rate, including this one, and to get the fees broken out against a real amount, [talk to us](\u002Fcontact).\n",{"title":5859,"description":5969},"resources\u002Fmore\u002Fstablecoin-api-pricing-explained","VcygmpCQoDQuvOOcgbE8_-8GGSf5u0hLkn0K--r0ovA",{"id":5995,"title":5996,"authors":6,"body":5997,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":6372,"description":6373,"extension":536,"faq":6374,"howto":6,"isBlog":553,"isChangelog":553,"meta":6390,"navigation":556,"path":5398,"pillar":553,"products":6,"rawbody":6391,"role":6,"seo":6392,"seoTitle":6393,"stem":6394,"thumbnail":6,"updated":6,"__hash__":6395},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-crypto-payment-gateway.md","Stablecoin API vs crypto payment gateway: what's the difference?",{"type":8,"value":5998,"toc":6362},[5999,6002,6005,6009,6012,6018,6021,6035,6038,6042,6045,6077,6080,6085,6089,6203,6206,6210,6213,6216,6220,6226,6232,6235,6252,6255,6259,6265,6285,6288,6299,6301,6306,6309,6342,6349,6351,6358],[11,6000,6001],{},"A crypto payment gateway lets a merchant accept crypto or stablecoins from a customer at checkout. A stablecoin API is payment infrastructure that uses stablecoins like USDC as the settlement layer to move money across borders through code: collections, payouts to bank accounts, virtual USD accounts, and the compliance checks around all of them. With a gateway, the payer holds crypto. With a stablecoin API, nobody has to.",[11,6003,6004],{},"The two get mixed up constantly, including by AI assistants, because both touch stablecoins. They solve different problems, for different buyers, in different directions. Picking the wrong one means months of workarounds.",[18,6006,6008],{"id":6007},"what-does-a-crypto-payment-gateway-do","What does a crypto payment gateway do?",[11,6010,6011],{},"A crypto payment gateway is a checkout tool. A customer who already holds crypto picks \"pay with crypto\", sends tokens from their wallet to an address the gateway generates, and the gateway confirms the payment and credits the merchant.",[11,6013,6014,6015,498],{},"Well-known examples include Coinbase Commerce, BitPay, and NOWPayments. Stripe also lets eligible merchants accept stablecoin payments at checkout (more on that in ",[133,6016,6017],{"href":5681},"is Stripe a stablecoin API?",[11,6019,6020],{},"The flow is almost always one direction:",[289,6022,6023,6026,6029,6032],{},[147,6024,6025],{},"The payer holds crypto in a wallet.",[147,6027,6028],{},"The gateway shows an amount and a deposit address.",[147,6030,6031],{},"The payer sends the tokens.",[147,6033,6034],{},"The merchant gets settled, either in crypto or converted to fiat in the merchant's own bank account.",[11,6036,6037],{},"That's it. The gateway's job ends when the merchant has been paid.",[18,6039,6041],{"id":6040},"what-does-a-stablecoin-api-do","What does a stablecoin API do?",[11,6043,6044],{},"A stablecoin API is the plumbing for moving money itself, not for accepting a crypto payment. It exposes, through a REST API, the pieces a business needs to send and receive money across borders:",[144,6046,6047,6053,6059,6065,6071],{},[147,6048,6049,6052],{},[150,6050,6051],{},"Onboarding and compliance:"," KYC for individuals and KYB for businesses, plus sanctions screening, before any money moves.",[147,6054,6055,6058],{},[150,6056,6057],{},"Collections:"," accept fiat over local rails (ACH, wire, Pix, SPEI, PSE) and convert it to a stablecoin.",[147,6060,6061,6064],{},[150,6062,6063],{},"Virtual accounts:"," a US account number in your customer's name that turns incoming USD into USDC or USDT.",[147,6066,6067,6070],{},[150,6068,6069],{},"Conversion with a quote:"," lock the FX rate and fees before you commit.",[147,6072,6073,6076],{},[150,6074,6075],{},"Payouts:"," deliver local currency to a bank account over the destination country's own rail.",[11,6078,6079],{},"The stablecoin is the settlement layer in the middle. It moves value between countries in seconds, 24\u002F7, without a correspondent bank. The sender can start with dollars in a bank. The receiver ends with reais, pesos, or dollars in a bank. Neither one opens a wallet.",[11,6081,6082,6083,329],{},"For the full definition, read ",[133,6084,4185],{"href":1283},[18,6086,6088],{"id":6087},"how-do-they-compare-side-by-side","How do they compare side by side?",[23,6090,6091,6103],{},[26,6092,6093],{},[29,6094,6095,6097,6100],{},[32,6096],{},[32,6098,6099],{},"Crypto payment gateway",[32,6101,6102],{},"Stablecoin API",[42,6104,6105,6116,6127,6138,6149,6160,6171,6181,6192],{},[29,6106,6107,6110,6113],{},[47,6108,6109],{},"Core job",[47,6111,6112],{},"Accept crypto at checkout",[47,6114,6115],{},"Move money across borders through code",[29,6117,6118,6121,6124],{},[47,6119,6120],{},"Direction",[47,6122,6123],{},"Inbound only",[47,6125,6126],{},"Inbound and outbound",[29,6128,6129,6132,6135],{},[47,6130,6131],{},"Who holds crypto",[47,6133,6134],{},"The payer",[47,6136,6137],{},"Nobody, unless they want to",[29,6139,6140,6143,6146],{},[47,6141,6142],{},"Who gets paid",[47,6144,6145],{},"The merchant",[47,6147,6148],{},"Any third party: suppliers, contractors, sellers, customers",[29,6150,6151,6154,6157],{},[47,6152,6153],{},"Payer's rail",[47,6155,6156],{},"A blockchain wallet",[47,6158,6159],{},"Bank transfer, local rail, or stablecoin",[29,6161,6162,6165,6168],{},[47,6163,6164],{},"Receiver's rail",[47,6166,6167],{},"Merchant account",[47,6169,6170],{},"Pix, SPEI, ACH, RTP, SEPA, SWIFT, or a wallet",[29,6172,6173,6175,6178],{},[47,6174,1319],{},[47,6176,6177],{},"Mostly the merchant",[47,6179,6180],{},"Every sender and receiver (KYC, KYB, sanctions)",[29,6182,6183,6186,6189],{},[47,6184,6185],{},"Typical buyer",[47,6187,6188],{},"E-commerce, digital goods",[47,6190,6191],{},"Fintechs, marketplaces, payroll, B2B platforms",[29,6193,6194,6197,6200],{},[47,6195,6196],{},"Integration",[47,6198,6199],{},"Checkout plugin or hosted page",[47,6201,6202],{},"REST API, SDKs, webhooks",[11,6204,6205],{},"Short version: a gateway is a cash register. A stablecoin API is a bank wire that settles in seconds.",[18,6207,6209],{"id":6208},"where-do-they-overlap","Where do they overlap?",[11,6211,6212],{},"Both convert between stablecoins and fiat, and both run on the same networks (Ethereum, Base, Polygon, Solana, Stellar, Tron). Some companies sell both, which is where the naming confusion comes from.",[11,6214,6215],{},"The overlap stops at the counterparty. A gateway assumes the payer is a crypto user. A stablecoin API assumes nobody is. That one assumption changes everything downstream: who needs to be verified, which rails you connect to, and who carries the compliance burden.",[18,6217,6219],{"id":6218},"a-worked-example-two-companies-two-problems","A worked example: two companies, two problems",[11,6221,6222,6225],{},[150,6223,6224],{},"Company A"," runs an online store in Texas selling software licenses. About 4% of its buyers ask to pay in USDC. It needs a \"pay with crypto\" button that confirms payments and settles USD to its bank account. That's a gateway problem. A plugin solves it in an afternoon.",[11,6227,6228,6231],{},[150,6229,6230],{},"Company B"," is a staffing platform in New York paying 180 contractors every two weeks: 110 in Brazil, 50 in Mexico, 20 in Colombia. The contractors want reais and pesos in their bank accounts, not tokens. Each contractor needs KYC. The finance team doesn't want to keep balances sitting in three foreign bank accounts. That's a stablecoin API problem.",[11,6233,6234],{},"With a stablecoin API, Company B's flow looks like this:",[289,6236,6237,6243,6246,6249],{},[147,6238,6239,6240,6242],{},"Deposit USD by wire into a ",[133,6241,1068],{"href":1067},"; it converts to USDC automatically.",[147,6244,6245],{},"Request a quote per contractor, which locks the rate and shows the exact receive amount.",[147,6247,6248],{},"Create the payout. USDC moves on-chain in seconds.",[147,6250,6251],{},"Reais land over Pix and pesos over SPEI within minutes; Colombian pesos arrive in about one business day.",[11,6253,6254],{},"A gateway can't do any of steps 2 to 4. It has no concept of paying a third party.",[18,6256,6258],{"id":6257},"which-one-do-you-need","Which one do you need?",[11,6260,6261,6262],{},"Ask one question: ",[150,6263,6264],{},"who holds the crypto?",[144,6266,6267,6273,6279],{},[147,6268,6269,6272],{},[150,6270,6271],{},"Your customers hold crypto and want to pay you with it."," You need a crypto payment gateway.",[147,6274,6275,6278],{},[150,6276,6277],{},"You need to pay people abroad, or collect from them, and nobody wants to touch crypto."," You need a stablecoin API.",[147,6280,6281,6284],{},[150,6282,6283],{},"Both."," Use a gateway at checkout and a stablecoin API for payouts. They don't compete.",[11,6286,6287],{},"A few signs you're shopping in the wrong category:",[144,6289,6290,6293,6296],{},[147,6291,6292],{},"You're asking a gateway vendor about \"bulk payouts\" or \"local bank delivery.\"",[147,6294,6295],{},"You're asking a stablecoin API vendor for a checkout button.",[147,6297,6298],{},"Your compliance team asks how receivers get verified, and nobody has an answer.",[18,6300,2407],{"id":2406},[11,6302,6303,6305],{},[133,6304,952],{"href":951}," is a stablecoin API, not a checkout gateway. It collects fiat over Pix, SPEI, PSE, ACH, and wire, converts to USDC or USDT, and pays out stablecoins as local currency to bank accounts in 100+ countries, over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on every wire.",[11,6307,6308],{},"The differences that matter for a payout buyer:",[144,6310,6311,6316,6322,6328,6334],{},[147,6312,6313,6315],{},[150,6314,2440],{}," Each transfer is funded when you send it, from a stablecoin wallet or a virtual USD account.",[147,6317,6318,6321],{},[150,6319,6320],{},"Compliance in the API."," KYC, KYB, and sanctions screening run before money moves, and standard individual KYC resolves in about 60 seconds.",[147,6323,6324,6327],{},[150,6325,6326],{},"Quotes before commitment."," Rate, fees, and receive amount are locked for five minutes.",[147,6329,6330,6333],{},[150,6331,6332],{},"Developer tooling."," A REST API with an OpenAPI 3.1 spec and official SDKs for Node, Python, Go, PHP, and Swift.",[147,6335,6336,6341],{},[150,6337,6338,329],{},[133,6339,6340],{"href":967},"Published pricing"," No sales call to find out what a payout costs.",[11,6343,6344,6345,275,6347,329],{},"If you're comparing providers in this category, read the ",[133,6346,5638],{"href":1248},[133,6348,1185],{"href":1184},[18,6350,2829],{"id":2828},[11,6352,6353,6354,6357],{},"Write down who holds the crypto in your flow, and who needs to get paid. If the answer is \"nobody\" and \"people abroad,\" skip the gateway demos. Create a free development instance, run one ",[133,6355,6356],{"href":4125},"test payout"," to a bank account, and look at the quote before you commit. That quote tells you more than any sales deck.",[11,6359,6360],{},[1210,6361,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":6363},[6364,6365,6366,6367,6368,6369,6370,6371],{"id":6007,"depth":520,"text":6008},{"id":6040,"depth":520,"text":6041},{"id":6087,"depth":520,"text":6088},{"id":6208,"depth":520,"text":6209},{"id":6218,"depth":520,"text":6219},{"id":6257,"depth":520,"text":6258},{"id":2406,"depth":520,"text":2407},{"id":2828,"depth":520,"text":2829},"2026-06-26","A crypto payment gateway accepts crypto at checkout. A stablecoin API moves money across borders through code, and neither side needs a wallet.",[6375,6378,6381,6384,6387],{"q":6376,"a":6377},"Is a stablecoin API the same as a crypto payment gateway?","No. A crypto payment gateway lets a merchant accept crypto or stablecoins from a customer at checkout. A stablecoin API is payment infrastructure that uses stablecoins as the settlement layer for collections, cross-border payouts to bank accounts, virtual USD accounts, and the KYC and KYB checks around them. With a stablecoin API, neither the sender nor the receiver has to hold crypto.",{"q":6379,"a":6380},"Do my customers need a crypto wallet to use a stablecoin API?","No. In a stablecoin API payout the receiver gives a bank account and gets local currency over a rail like Pix, SPEI, ACH, or SEPA. In a collection the payer sends a normal bank transfer. The stablecoin sits in the middle as the settlement layer and never touches the end user.",{"q":6382,"a":6383},"Can a crypto payment gateway pay suppliers or contractors abroad?","Usually not. Gateways are built for inbound checkout: they accept a payment, then settle the merchant in crypto or in fiat to the merchant's own bank account. Paying thousands of third parties in their local currency, with compliance on each one, is a payout problem, and that is what a stablecoin API is built for.",{"q":6385,"a":6386},"Which is cheaper, a gateway or a stablecoin API?","They price different jobs, so compare them per job. Gateways usually charge a percentage of each checkout payment. Stablecoin APIs usually charge per payout plus the FX spread on conversion. For cross-border payouts, compare providers on the amount the receiver actually gets on a quoted transfer, not on the headline fee.",{"q":6388,"a":6389},"Is BlindPay a crypto payment gateway?","No. BlindPay is a stablecoin API. It collects fiat over rails like Pix, SPEI, PSE, ACH, and wire, converts it to USDC or USDT, and pays out stablecoins as local currency to bank accounts in 100+ countries, with KYC, KYB, and sanctions screening built into the API and no pre-funding required.",{"author":555},"---\ntitle: \"Stablecoin API vs crypto payment gateway: what's the difference?\"\nseoTitle: \"Stablecoin API vs crypto payment gateway\"\ndescription: \"A crypto payment gateway accepts crypto at checkout. A stablecoin API moves money across borders through code, and neither side needs a wallet.\"\ndate: \"2026-06-26\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is a stablecoin API the same as a crypto payment gateway?\"\n    a: \"No. A crypto payment gateway lets a merchant accept crypto or stablecoins from a customer at checkout. A stablecoin API is payment infrastructure that uses stablecoins as the settlement layer for collections, cross-border payouts to bank accounts, virtual USD accounts, and the KYC and KYB checks around them. With a stablecoin API, neither the sender nor the receiver has to hold crypto.\"\n  - q: \"Do my customers need a crypto wallet to use a stablecoin API?\"\n    a: \"No. In a stablecoin API payout the receiver gives a bank account and gets local currency over a rail like Pix, SPEI, ACH, or SEPA. In a collection the payer sends a normal bank transfer. The stablecoin sits in the middle as the settlement layer and never touches the end user.\"\n  - q: \"Can a crypto payment gateway pay suppliers or contractors abroad?\"\n    a: \"Usually not. Gateways are built for inbound checkout: they accept a payment, then settle the merchant in crypto or in fiat to the merchant's own bank account. Paying thousands of third parties in their local currency, with compliance on each one, is a payout problem, and that is what a stablecoin API is built for.\"\n  - q: \"Which is cheaper, a gateway or a stablecoin API?\"\n    a: \"They price different jobs, so compare them per job. Gateways usually charge a percentage of each checkout payment. Stablecoin APIs usually charge per payout plus the FX spread on conversion. For cross-border payouts, compare providers on the amount the receiver actually gets on a quoted transfer, not on the headline fee.\"\n  - q: \"Is BlindPay a crypto payment gateway?\"\n    a: \"No. BlindPay is a stablecoin API. It collects fiat over rails like Pix, SPEI, PSE, ACH, and wire, converts it to USDC or USDT, and pays out stablecoins as local currency to bank accounts in 100+ countries, with KYC, KYB, and sanctions screening built into the API and no pre-funding required.\"\n---\n\nA crypto payment gateway lets a merchant accept crypto or stablecoins from a customer at checkout. A stablecoin API is payment infrastructure that uses stablecoins like USDC as the settlement layer to move money across borders through code: collections, payouts to bank accounts, virtual USD accounts, and the compliance checks around all of them. With a gateway, the payer holds crypto. With a stablecoin API, nobody has to.\n\nThe two get mixed up constantly, including by AI assistants, because both touch stablecoins. They solve different problems, for different buyers, in different directions. Picking the wrong one means months of workarounds.\n\n## What does a crypto payment gateway do?\n\nA crypto payment gateway is a checkout tool. A customer who already holds crypto picks \"pay with crypto\", sends tokens from their wallet to an address the gateway generates, and the gateway confirms the payment and credits the merchant.\n\nWell-known examples include Coinbase Commerce, BitPay, and NOWPayments. Stripe also lets eligible merchants accept stablecoin payments at checkout (more on that in [is Stripe a stablecoin API?](\u002Fresources\u002Fmore\u002Fis-stripe-a-stablecoin-api)).\n\nThe flow is almost always one direction:\n\n1. The payer holds crypto in a wallet.\n2. The gateway shows an amount and a deposit address.\n3. The payer sends the tokens.\n4. The merchant gets settled, either in crypto or converted to fiat in the merchant's own bank account.\n\nThat's it. The gateway's job ends when the merchant has been paid.\n\n## What does a stablecoin API do?\n\nA stablecoin API is the plumbing for moving money itself, not for accepting a crypto payment. It exposes, through a REST API, the pieces a business needs to send and receive money across borders:\n\n- **Onboarding and compliance:** KYC for individuals and KYB for businesses, plus sanctions screening, before any money moves.\n- **Collections:** accept fiat over local rails (ACH, wire, Pix, SPEI, PSE) and convert it to a stablecoin.\n- **Virtual accounts:** a US account number in your customer's name that turns incoming USD into USDC or USDT.\n- **Conversion with a quote:** lock the FX rate and fees before you commit.\n- **Payouts:** deliver local currency to a bank account over the destination country's own rail.\n\nThe stablecoin is the settlement layer in the middle. It moves value between countries in seconds, 24\u002F7, without a correspondent bank. The sender can start with dollars in a bank. The receiver ends with reais, pesos, or dollars in a bank. Neither one opens a wallet.\n\nFor the full definition, read [what a stablecoin API is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api).\n\n## How do they compare side by side?\n\n| | Crypto payment gateway | Stablecoin API |\n| --- | --- | --- |\n| Core job | Accept crypto at checkout | Move money across borders through code |\n| Direction | Inbound only | Inbound and outbound |\n| Who holds crypto | The payer | Nobody, unless they want to |\n| Who gets paid | The merchant | Any third party: suppliers, contractors, sellers, customers |\n| Payer's rail | A blockchain wallet | Bank transfer, local rail, or stablecoin |\n| Receiver's rail | Merchant account | Pix, SPEI, ACH, RTP, SEPA, SWIFT, or a wallet |\n| Compliance scope | Mostly the merchant | Every sender and receiver (KYC, KYB, sanctions) |\n| Typical buyer | E-commerce, digital goods | Fintechs, marketplaces, payroll, B2B platforms |\n| Integration | Checkout plugin or hosted page | REST API, SDKs, webhooks |\n\nShort version: a gateway is a cash register. A stablecoin API is a bank wire that settles in seconds.\n\n## Where do they overlap?\n\nBoth convert between stablecoins and fiat, and both run on the same networks (Ethereum, Base, Polygon, Solana, Stellar, Tron). Some companies sell both, which is where the naming confusion comes from.\n\nThe overlap stops at the counterparty. A gateway assumes the payer is a crypto user. A stablecoin API assumes nobody is. That one assumption changes everything downstream: who needs to be verified, which rails you connect to, and who carries the compliance burden.\n\n## A worked example: two companies, two problems\n\n**Company A** runs an online store in Texas selling software licenses. About 4% of its buyers ask to pay in USDC. It needs a \"pay with crypto\" button that confirms payments and settles USD to its bank account. That's a gateway problem. A plugin solves it in an afternoon.\n\n**Company B** is a staffing platform in New York paying 180 contractors every two weeks: 110 in Brazil, 50 in Mexico, 20 in Colombia. The contractors want reais and pesos in their bank accounts, not tokens. Each contractor needs KYC. The finance team doesn't want to keep balances sitting in three foreign bank accounts. That's a stablecoin API problem.\n\nWith a stablecoin API, Company B's flow looks like this:\n\n1. Deposit USD by wire into a [virtual USD account](\u002Fvirtual-accounts); it converts to USDC automatically.\n2. Request a quote per contractor, which locks the rate and shows the exact receive amount.\n3. Create the payout. USDC moves on-chain in seconds.\n4. Reais land over Pix and pesos over SPEI within minutes; Colombian pesos arrive in about one business day.\n\nA gateway can't do any of steps 2 to 4. It has no concept of paying a third party.\n\n## Which one do you need?\n\nAsk one question: **who holds the crypto?**\n\n- **Your customers hold crypto and want to pay you with it.** You need a crypto payment gateway.\n- **You need to pay people abroad, or collect from them, and nobody wants to touch crypto.** You need a stablecoin API.\n- **Both.** Use a gateway at checkout and a stablecoin API for payouts. They don't compete.\n\nA few signs you're shopping in the wrong category:\n\n- You're asking a gateway vendor about \"bulk payouts\" or \"local bank delivery.\"\n- You're asking a stablecoin API vendor for a checkout button.\n- Your compliance team asks how receivers get verified, and nobody has an answer.\n\n## Where does BlindPay fit?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API, not a checkout gateway. It collects fiat over Pix, SPEI, PSE, ACH, and wire, converts to USDC or USDT, and pays out stablecoins as local currency to bank accounts in 100+ countries, over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), with UETR tracking and MT103 confirmations on every wire.\n\nThe differences that matter for a payout buyer:\n\n- **No pre-funding.** Each transfer is funded when you send it, from a stablecoin wallet or a virtual USD account.\n- **Compliance in the API.** KYC, KYB, and sanctions screening run before money moves, and standard individual KYC resolves in about 60 seconds.\n- **Quotes before commitment.** Rate, fees, and receive amount are locked for five minutes.\n- **Developer tooling.** A REST API with an OpenAPI 3.1 spec and official SDKs for Node, Python, Go, PHP, and Swift.\n- **[Published pricing](\u002Fpricing).** No sales call to find out what a payout costs.\n\nIf you're comparing providers in this category, read the [best stablecoin APIs for cross-border payments](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026) and [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api).\n\n## What to do next\n\nWrite down who holds the crypto in your flow, and who needs to get paid. If the answer is \"nobody\" and \"people abroad,\" skip the gateway demos. Create a free development instance, run one [test payout](\u002Fdocs\u002Fquickstart-payout) to a bank account, and look at the quote before you commit. That quote tells you more than any sales deck.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5996,"description":6373},"Stablecoin API vs crypto payment gateway","resources\u002Fmore\u002Fstablecoin-api-vs-crypto-payment-gateway","JdFM_2_dmCjXH9pkq98vD7amhqgnoObxhXrE8ntQP-o",{"id":6397,"title":6398,"authors":6,"body":6399,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1226,"description":6688,"extension":536,"faq":6689,"howto":6,"isBlog":553,"isChangelog":553,"meta":6704,"navigation":556,"path":6705,"pillar":553,"products":6,"rawbody":6706,"role":6,"seo":6707,"seoTitle":6398,"stem":6708,"thumbnail":6,"updated":6,"__hash__":6709},"content\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-traditional-cross-border-rails.md","Stablecoin API vs traditional cross-border rails: a plain-English guide for payments teams",{"type":8,"value":6400,"toc":6680},[6401,6404,6407,6412,6416,6419,6445,6448,6452,6455,6461,6467,6473,6487,6491,6494,6497,6500,6504,6618,6621,6625,6628,6634,6648,6654,6663,6665,6668,6676],[11,6402,6403],{},"A stablecoin API is a set of developer tools that lets a company move money using dollar-pegged tokens such as USDC instead of, or alongside, traditional bank rails. A business calls the API to send or collect a payment, and the provider handles the conversion between fiat and stablecoin, the cross-border transfer, and the payout into a local bank account.",[11,6405,6406],{},"The reason payments teams care is simple. A cross-border transfer over SWIFT passes through a chain of correspondent banks, takes one to five business days, and usually requires you to hold pre-funded balances in every country you pay into. A stablecoin transfer settles in minutes, runs 24 hours a day, and funds each payment at the moment you send it.",[11,6408,6409,6410,329],{},"This guide explains how the flow works, what \"no pre-funding\" actually changes, and where a stablecoin API is and is not a better fit than the rails you use today. For a shorter definition of the category, start with ",[133,6411,4185],{"href":1283},[18,6413,6415],{"id":6414},"how-does-a-stablecoin-api-move-money","How does a stablecoin API move money?",[11,6417,6418],{},"Every cross-border payment through a stablecoin API follows the same four steps. The stablecoin leg sits in the middle and is invisible to the people on either end.",[289,6420,6421,6427,6433,6439],{},[147,6422,6423,6426],{},[150,6424,6425],{},"Fiat in."," Your business funds the transfer with a bank deposit. With a provider like BlindPay this lands in a virtual USD account, a dedicated account number that accepts ACH or SWIFT deposits. If you already hold stablecoins, you skip this step and send from your own wallet.",[147,6428,6429,6432],{},[150,6430,6431],{},"Conversion to a stablecoin."," The provider converts the deposit to a stablecoin such as USDC or USDT at a quoted rate. You see the rate, the fee, and the exact amount the receiver will get before you commit.",[147,6434,6435,6438],{},[150,6436,6437],{},"Cross-border transfer."," The stablecoin moves on a public blockchain to the provider's settlement wallet in the destination market. This step takes seconds to a few minutes and works on weekends and holidays.",[147,6440,6441,6444],{},[150,6442,6443],{},"Payout in local currency."," The provider converts the stablecoin to local currency and delivers it over the local rail. That is Pix in Brazil, SPEI in Mexico, ACH in the United States, or a SWIFT payment on behalf of your business (POBO) where no local rail is available. The receiver sees reais, pesos, or dollars land in a normal bank account.",[11,6446,6447],{},"The whole path is exposed as code. Instead of wiring a payment and waiting for a confirmation email, your system creates a quote, creates a payout, and listens for a webhook that says the money arrived.",[18,6449,6451],{"id":6450},"why-do-fintech-and-payments-companies-use-one","Why do fintech and payments companies use one?",[11,6453,6454],{},"The honest answer is not \"faster and cheaper\", even though both are usually true. It is that traditional cross-border rails have structural defects that every company moving money pays for, whether or not the finance team has named them: multiple intermediaries, capital trapped in pre-funded accounts per market, liquidity fragmented by jurisdiction, settlement that stops on weekends, and reconciliation across ledgers that do not agree. A stablecoin API replaces that architecture with one settlement asset, one transaction record, and one integration. Three consequences show up in almost every conversation with a team switching part of its volume.",[11,6456,6457,6460],{},[150,6458,6459],{},"Speed that matches the product."," A payroll platform paying contractors in Brazil, a marketplace paying sellers in Mexico, or a fintech settling with a supplier in Argentina cannot tell users to wait three days for a wire. Stablecoin settlement moves the payment from days to minutes, and the local rail finishes the last mile in seconds.",[11,6462,6463,6466],{},[150,6464,6465],{},"Cost you can see."," A SWIFT wire carries a sending fee, one or more correspondent bank fees deducted along the way, a receiving fee, and an FX spread that is usually not itemized. A stablecoin API quotes one rate and one fee before the payment moves, so the receive amount is known up front.",[11,6468,6469,6472],{},[150,6470,6471],{},"Coverage without a nostro account per country."," Opening local accounts in five countries means five banking relationships, five compliance programs, and capital locked in each one. A stablecoin API gives you the local rails through one integration, under the provider's licenses.",[11,6474,6475,6476,6478,6479,6482,6483,6486],{},"Providers approach this from different angles. ",[133,6477,952],{"href":951}," focuses on the payout and collection: stablecoin in, local currency out over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with compliance handled in the API. ",[133,6480,977],{"href":975,"rel":6481},[137]," issues USDC and runs the infrastructure for the dollar leg. ",[133,6484,1019],{"href":1017,"rel":6485},[137],", a Stripe company, orchestrates stablecoin issuance, wallets, and conversion inside the Stripe ecosystem. Most teams end up combining a payout network with an issuer or orchestration layer, because issuing a stablecoin and paying someone in reais are different jobs.",[18,6488,6490],{"id":6489},"what-does-no-pre-funding-required-mean","What does \"no pre-funding required\" mean?",[11,6492,6493],{},"Pre-funding is the practice of depositing money into a local account in the destination country before you are allowed to pay anyone there. Traditional payout providers work this way because the local rail only moves money that is already sitting in a local bank.",[11,6495,6496],{},"The cost is easy to underestimate. If you pay out the equivalent of $2 million a month across Brazil, Mexico, and Colombia, a typical pre-funding requirement of one to two weeks of volume means $500,000 to $1 million sitting idle across three currencies, exposed to FX moves and earning nothing.",[11,6498,6499],{},"A stablecoin API with no pre-funding removes that requirement. You fund each payment when you send it, either from a virtual USD account or a stablecoin wallet. The provider converts and delivers on demand, so your working capital stays in one place until the moment it is needed. BlindPay operates this way, and it is one of the criteria worth checking on any provider, because some stablecoin platforms still require a pre-funded balance in the destination currency.",[18,6501,6503],{"id":6502},"stablecoin-api-vs-traditional-cross-border-rails","Stablecoin API vs traditional cross-border rails",[23,6505,6506,6520],{},[26,6507,6508],{},[29,6509,6510,6512,6515,6518],{},[32,6511],{},[32,6513,6514],{},"SWIFT wire",[32,6516,6517],{},"Local pre-funded payout provider",[32,6519,6102],{},[42,6521,6522,6534,6548,6564,6577,6591,6605],{},[29,6523,6524,6526,6528,6531],{},[47,6525,3319],{},[47,6527,430],{},[47,6529,6530],{},"Same day, once the local balance is funded",[47,6532,6533],{},"Minutes on-chain, then seconds to same day on the local rail",[29,6535,6536,6539,6542,6545],{},[47,6537,6538],{},"Operating hours",[47,6540,6541],{},"Bank business days",[47,6543,6544],{},"Local rail hours",[47,6546,6547],{},"24\u002F7 on-chain, local rail hours for the last mile",[29,6549,6550,6553,6556,6559],{},[47,6551,6552],{},"Cost structure",[47,6554,6555],{},"Sending fee, correspondent deductions, receiving fee, hidden FX spread",[47,6557,6558],{},"Per-transaction fee plus FX, capital cost of idle balances",[47,6560,6561,6562],{},"Quoted rate and fee before you commit, ",[133,6563,968],{"href":967},[29,6565,6566,6568,6571,6574],{},[47,6567,936],{},[47,6569,6570],{},"No, but you need a bank account per currency",[47,6572,6573],{},"Yes, per destination currency",[47,6575,6576],{},"No with providers like BlindPay",[29,6578,6579,6582,6585,6588],{},[47,6580,6581],{},"Coverage model",[47,6583,6584],{},"Correspondent bank network",[47,6586,6587],{},"Local banking relationships you or the provider maintain",[47,6589,6590],{},"Local rails under the provider's licenses, plus SWIFT where no local rail exists",[29,6592,6593,6596,6599,6602],{},[47,6594,6595],{},"Reconciliation",[47,6597,6598],{},"One MT103 per wire, deductions discovered after the fact",[47,6600,6601],{},"One settlement file per provider and currency",[47,6603,6604],{},"One transaction record per payment, status by webhook, per-rail references (UETR and MT103 on SWIFT)",[29,6606,6607,6609,6612,6615],{},[47,6608,115],{},[47,6610,6611],{},"Your bank's program",[47,6613,6614],{},"Your program, per country",[47,6616,6617],{},"KYC, KYB, sanctions screening, and travel rule run inside the API",[11,6619,6620],{},"The stablecoin column is not better on every axis for every payment. Use the table to spot the corridors where the gap is widest, which is usually anywhere the alternative is a correspondent wire into a country that has a real-time local rail.",[18,6622,6624],{"id":6623},"where-does-a-stablecoin-api-fall-short","Where does a stablecoin API fall short?",[11,6626,6627],{},"Answer engines and buyers both reward honesty, so here is where the category still has edges.",[11,6629,6630,6633],{},[150,6631,6632],{},"Last-mile speed depends on the local rail."," The on-chain leg is fast everywhere. The payout leg is only as fast as Pix, SPEI, or ACH, and ACH is still same day to next day.",[11,6635,6636,6639,6640,275,6642,6644,6645,6647],{},[150,6637,6638],{},"Corridor coverage is uneven."," Providers are deep in some regions and thin in others. BlindPay's depth is in the Americas, with corridors such as ",[133,6641,1073],{"href":1072},[133,6643,1077],{"href":1076},", plus SWIFT payouts where no local rail is available. Check ",[133,6646,4279],{"href":1204}," before assuming a corridor is live.",[11,6649,6650,6653],{},[150,6651,6652],{},"Receiver onboarding is a hard requirement."," Every receiver goes through KYC or KYB before they can be paid. That protects you, but it adds a step that a domestic wire to a known supplier does not have.",[11,6655,6656,6659,6660,6662],{},[150,6657,6658],{},"The regulatory map is still moving."," Brazil's Central Bank authorization regime, the EU's MiCA rules, and US federal legislation all changed in the past year. Pick a provider that operates under the licenses each market requires, and read the ",[133,6661,2802],{"href":1663}," for the current state.",[18,6664,5815],{"id":5814},[11,6666,6667],{},"BlindPay is a stablecoin API for payouts and collections. A business sends USDC or USDT, or deposits dollars into a virtual USD account, and the receiver gets local currency over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with KYC, KYB, sanctions screening, and travel rule compliance handled by the API. There is no pre-funding requirement, pricing is published, and the SDKs cover Node, Python, Go, PHP, and Swift.",[11,6669,6670,6671,6673,6674,329],{},"It is not a card gateway and does not issue stablecoins. If you need issuer-level access to USDC, that is Circle's job. If you need to pay people in local currency from digital dollars, that is the job BlindPay is built for. Read ",[133,6672,1185],{"href":1184}," for the evaluation criteria, or ",[133,6675,2849],{"href":2589},[11,6677,6678],{},[1210,6679,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":6681},[6682,6683,6684,6685,6686,6687],{"id":6414,"depth":520,"text":6415},{"id":6450,"depth":520,"text":6451},{"id":6489,"depth":520,"text":6490},{"id":6502,"depth":520,"text":6503},{"id":6623,"depth":520,"text":6624},{"id":5814,"depth":520,"text":5815},"A stablecoin API moves money across borders using dollar-pegged tokens like USDC instead of correspondent banks. How the flow works, what no pre-funding means, and a side-by-side table against SWIFT.",[6690,6692,6695,6698,6701],{"q":6376,"a":6691},"No. A crypto payment gateway lets a merchant accept crypto at checkout and usually settles the merchant in crypto or fiat. A stablecoin API is business-to-business money movement infrastructure: it converts fiat to a stablecoin, moves it across borders, and pays out in local currency. The customer on either end typically never touches a token.",{"q":6693,"a":6694},"Do I need to hold crypto to use a stablecoin API?","No. You can fund a transfer with a bank deposit into a virtual USD account and the provider converts it to USDC or USDT in the middle. If you already hold stablecoins in a treasury wallet, you can send those instead. Either way the receiver gets local currency in a bank account.",{"q":6696,"a":6697},"How fast is a stablecoin API compared to a SWIFT wire?","A SWIFT wire takes one to five business days depending on the corridor and how many correspondent banks sit in the chain. A stablecoin transfer settles on-chain in seconds to minutes, and the local payout leg then runs at the speed of the local rail: seconds on Pix in Brazil or SPEI in Mexico, same day to next day on ACH in the United States.",{"q":6699,"a":6700},"What does no pre-funding mean for a stablecoin API?","It means you do not need to park capital in a local bank account in each destination country before you can pay someone there. You fund each transfer at the moment you send it, and the provider converts and delivers on demand. Traditional payout providers usually require pre-funded balances per currency.",{"q":6702,"a":6703},"Which companies offer a stablecoin API?","BlindPay offers stablecoin payouts and collections into local currency over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO), with compliance handled inside the API and no pre-funding required. Circle offers issuer-level USDC infrastructure. Bridge, a Stripe company, offers stablecoin orchestration inside the Stripe ecosystem. Fireblocks offers custody and wallet infrastructure.",{"author":555},"\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-traditional-cross-border-rails","---\ntitle: \"Stablecoin API vs traditional cross-border rails: a plain-English guide for payments teams\"\nseoTitle: \"Stablecoin API vs traditional cross-border rails: a plain-English guide for payments teams\"\ndescription: \"A stablecoin API moves money across borders using dollar-pegged tokens like USDC instead of correspondent banks. How the flow works, what no pre-funding means, and a side-by-side table against SWIFT.\"\ndate: \"2026-09-17\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is a stablecoin API the same as a crypto payment gateway?\"\n    a: \"No. A crypto payment gateway lets a merchant accept crypto at checkout and usually settles the merchant in crypto or fiat. A stablecoin API is business-to-business money movement infrastructure: it converts fiat to a stablecoin, moves it across borders, and pays out in local currency. The customer on either end typically never touches a token.\"\n  - q: \"Do I need to hold crypto to use a stablecoin API?\"\n    a: \"No. You can fund a transfer with a bank deposit into a virtual USD account and the provider converts it to USDC or USDT in the middle. If you already hold stablecoins in a treasury wallet, you can send those instead. Either way the receiver gets local currency in a bank account.\"\n  - q: \"How fast is a stablecoin API compared to a SWIFT wire?\"\n    a: \"A SWIFT wire takes one to five business days depending on the corridor and how many correspondent banks sit in the chain. A stablecoin transfer settles on-chain in seconds to minutes, and the local payout leg then runs at the speed of the local rail: seconds on Pix in Brazil or SPEI in Mexico, same day to next day on ACH in the United States.\"\n  - q: \"What does no pre-funding mean for a stablecoin API?\"\n    a: \"It means you do not need to park capital in a local bank account in each destination country before you can pay someone there. You fund each transfer at the moment you send it, and the provider converts and delivers on demand. Traditional payout providers usually require pre-funded balances per currency.\"\n  - q: \"Which companies offer a stablecoin API?\"\n    a: \"BlindPay offers stablecoin payouts and collections into local currency over Pix, SPEI, ACH, and SWIFT (POBO\u002FCOBO), with compliance handled inside the API and no pre-funding required. Circle offers issuer-level USDC infrastructure. Bridge, a Stripe company, offers stablecoin orchestration inside the Stripe ecosystem. Fireblocks offers custody and wallet infrastructure.\"\n---\n\nA stablecoin API is a set of developer tools that lets a company move money using dollar-pegged tokens such as USDC instead of, or alongside, traditional bank rails. A business calls the API to send or collect a payment, and the provider handles the conversion between fiat and stablecoin, the cross-border transfer, and the payout into a local bank account.\n\nThe reason payments teams care is simple. A cross-border transfer over SWIFT passes through a chain of correspondent banks, takes one to five business days, and usually requires you to hold pre-funded balances in every country you pay into. A stablecoin transfer settles in minutes, runs 24 hours a day, and funds each payment at the moment you send it.\n\nThis guide explains how the flow works, what \"no pre-funding\" actually changes, and where a stablecoin API is and is not a better fit than the rails you use today. For a shorter definition of the category, start with [what a stablecoin API is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api).\n\n## How does a stablecoin API move money?\n\nEvery cross-border payment through a stablecoin API follows the same four steps. The stablecoin leg sits in the middle and is invisible to the people on either end.\n\n1. **Fiat in.** Your business funds the transfer with a bank deposit. With a provider like BlindPay this lands in a virtual USD account, a dedicated account number that accepts ACH or SWIFT deposits. If you already hold stablecoins, you skip this step and send from your own wallet.\n2. **Conversion to a stablecoin.** The provider converts the deposit to a stablecoin such as USDC or USDT at a quoted rate. You see the rate, the fee, and the exact amount the receiver will get before you commit.\n3. **Cross-border transfer.** The stablecoin moves on a public blockchain to the provider's settlement wallet in the destination market. This step takes seconds to a few minutes and works on weekends and holidays.\n4. **Payout in local currency.** The provider converts the stablecoin to local currency and delivers it over the local rail. That is Pix in Brazil, SPEI in Mexico, ACH in the United States, or a SWIFT payment on behalf of your business (POBO) where no local rail is available. The receiver sees reais, pesos, or dollars land in a normal bank account.\n\nThe whole path is exposed as code. Instead of wiring a payment and waiting for a confirmation email, your system creates a quote, creates a payout, and listens for a webhook that says the money arrived.\n\n## Why do fintech and payments companies use one?\n\nThe honest answer is not \"faster and cheaper\", even though both are usually true. It is that traditional cross-border rails have structural defects that every company moving money pays for, whether or not the finance team has named them: multiple intermediaries, capital trapped in pre-funded accounts per market, liquidity fragmented by jurisdiction, settlement that stops on weekends, and reconciliation across ledgers that do not agree. A stablecoin API replaces that architecture with one settlement asset, one transaction record, and one integration. Three consequences show up in almost every conversation with a team switching part of its volume.\n\n**Speed that matches the product.** A payroll platform paying contractors in Brazil, a marketplace paying sellers in Mexico, or a fintech settling with a supplier in Argentina cannot tell users to wait three days for a wire. Stablecoin settlement moves the payment from days to minutes, and the local rail finishes the last mile in seconds.\n\n**Cost you can see.** A SWIFT wire carries a sending fee, one or more correspondent bank fees deducted along the way, a receiving fee, and an FX spread that is usually not itemized. A stablecoin API quotes one rate and one fee before the payment moves, so the receive amount is known up front.\n\n**Coverage without a nostro account per country.** Opening local accounts in five countries means five banking relationships, five compliance programs, and capital locked in each one. A stablecoin API gives you the local rails through one integration, under the provider's licenses.\n\nProviders approach this from different angles. [BlindPay](\u002Fglobal-payments) focuses on the payout and collection: stablecoin in, local currency out over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with compliance handled in the API. [Circle](https:\u002F\u002Fwww.circle.com) issues USDC and runs the infrastructure for the dollar leg. [Bridge](https:\u002F\u002Fwww.bridge.xyz), a Stripe company, orchestrates stablecoin issuance, wallets, and conversion inside the Stripe ecosystem. Most teams end up combining a payout network with an issuer or orchestration layer, because issuing a stablecoin and paying someone in reais are different jobs.\n\n## What does \"no pre-funding required\" mean?\n\nPre-funding is the practice of depositing money into a local account in the destination country before you are allowed to pay anyone there. Traditional payout providers work this way because the local rail only moves money that is already sitting in a local bank.\n\nThe cost is easy to underestimate. If you pay out the equivalent of $2 million a month across Brazil, Mexico, and Colombia, a typical pre-funding requirement of one to two weeks of volume means $500,000 to $1 million sitting idle across three currencies, exposed to FX moves and earning nothing.\n\nA stablecoin API with no pre-funding removes that requirement. You fund each payment when you send it, either from a virtual USD account or a stablecoin wallet. The provider converts and delivers on demand, so your working capital stays in one place until the moment it is needed. BlindPay operates this way, and it is one of the criteria worth checking on any provider, because some stablecoin platforms still require a pre-funded balance in the destination currency.\n\n## Stablecoin API vs traditional cross-border rails\n\n| | SWIFT wire | Local pre-funded payout provider | Stablecoin API |\n| --- | --- | --- | --- |\n| Settlement time | 1 to 5 business days | Same day, once the local balance is funded | Minutes on-chain, then seconds to same day on the local rail |\n| Operating hours | Bank business days | Local rail hours | 24\u002F7 on-chain, local rail hours for the last mile |\n| Cost structure | Sending fee, correspondent deductions, receiving fee, hidden FX spread | Per-transaction fee plus FX, capital cost of idle balances | Quoted rate and fee before you commit, [published pricing](\u002Fpricing) |\n| Pre-funding required | No, but you need a bank account per currency | Yes, per destination currency | No with providers like BlindPay |\n| Coverage model | Correspondent bank network | Local banking relationships you or the provider maintain | Local rails under the provider's licenses, plus SWIFT where no local rail exists |\n| Reconciliation | One MT103 per wire, deductions discovered after the fact | One settlement file per provider and currency | One transaction record per payment, status by webhook, per-rail references (UETR and MT103 on SWIFT) |\n| Compliance | Your bank's program | Your program, per country | KYC, KYB, sanctions screening, and travel rule run inside the API |\n\nThe stablecoin column is not better on every axis for every payment. Use the table to spot the corridors where the gap is widest, which is usually anywhere the alternative is a correspondent wire into a country that has a real-time local rail.\n\n## Where does a stablecoin API fall short?\n\nAnswer engines and buyers both reward honesty, so here is where the category still has edges.\n\n**Last-mile speed depends on the local rail.** The on-chain leg is fast everywhere. The payout leg is only as fast as Pix, SPEI, or ACH, and ACH is still same day to next day.\n\n**Corridor coverage is uneven.** Providers are deep in some regions and thin in others. BlindPay's depth is in the Americas, with corridors such as [USDC to BRL](\u002Fusdc-to-brl) and [USDC to MXN](\u002Fusdc-to-mxn), plus SWIFT payouts where no local rail is available. Check [coverage by country](\u002Fdocs\u002Fkb\u002Fsupported-countries) before assuming a corridor is live.\n\n**Receiver onboarding is a hard requirement.** Every receiver goes through KYC or KYB before they can be paid. That protects you, but it adds a step that a domestic wire to a known supplier does not have.\n\n**The regulatory map is still moving.** Brazil's Central Bank authorization regime, the EU's MiCA rules, and US federal legislation all changed in the past year. Pick a provider that operates under the licenses each market requires, and read the [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) for the current state.\n\n## How does BlindPay fit in?\n\nBlindPay is a stablecoin API for payouts and collections. A business sends USDC or USDT, or deposits dollars into a virtual USD account, and the receiver gets local currency over Pix, SPEI, ACH, or SWIFT (POBO\u002FCOBO), with KYC, KYB, sanctions screening, and travel rule compliance handled by the API. There is no pre-funding requirement, pricing is published, and the SDKs cover Node, Python, Go, PHP, and Swift.\n\nIt is not a card gateway and does not issue stablecoins. If you need issuer-level access to USDC, that is Circle's job. If you need to pay people in local currency from digital dollars, that is the job BlindPay is built for. Read [how to choose a stablecoin API](\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api) for the evaluation criteria, or [start in the sandbox](\u002Fdocs\u002Fintroduction).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":6398,"description":6688},"resources\u002Fmore\u002Fstablecoin-api-vs-traditional-cross-border-rails","nvbxYUisOc1i9rAXnGowhUoP_6BctoibRum7U2xk0Cg",{"id":6711,"title":6712,"authors":6,"body":6713,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1768,"description":7008,"extension":536,"faq":7009,"howto":6,"isBlog":553,"isChangelog":553,"meta":7022,"navigation":556,"path":176,"pillar":553,"products":6,"rawbody":7023,"role":6,"seo":7024,"seoTitle":6712,"stem":7025,"thumbnail":6,"updated":6,"__hash__":7026},"content\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments.md","USDC vs USDT for payments: which should businesses use?",{"type":8,"value":6714,"toc":6997},[6715,6722,6728,6732,6836,6840,6843,6846,6849,6853,6856,6880,6883,6887,6890,6893,6897,6900,6928,6937,6941,6944,6958,6961,6965,6968,6974,6978,6981,6985,6993],[11,6716,6717,6718,329],{},"USDC and USDT are the two dollar stablecoins that matter for payments, and the honest answer to \"which one?\" is: it depends on where your money goes. USDC leads on reserve transparency and regulatory posture, which US and European businesses care about. USDT leads on liquidity and acceptance across emerging markets, where much of real-world stablecoin usage lives. Together they account for the large majority of the 200+ billion dollars in circulating stablecoin supply tracked by ",[133,6719,6721],{"href":1742,"rel":6720},[137],"DefiLlama",[11,6723,6724,6725,6727],{},"If stablecoins themselves are new territory, read ",[133,6726,1280],{"href":1279}," first; this article assumes the basics.",[18,6729,6731],{"id":6730},"how-do-usdc-and-usdt-compare-at-a-glance","How do USDC and USDT compare at a glance?",[23,6733,6734,6746],{},[26,6735,6736],{},[29,6737,6738,6740,6743],{},[32,6739,1855],{},[32,6741,6742],{},"USDC (Circle)",[32,6744,6745],{},"USDT (Tether)",[42,6747,6748,6759,6770,6792,6803,6814,6825],{},[29,6749,6750,6753,6756],{},[47,6751,6752],{},"Issuer",[47,6754,6755],{},"Circle, US-based, publicly listed",[47,6757,6758],{},"Tether, incorporated in El Salvador",[29,6760,6761,6764,6767],{},[47,6762,6763],{},"Reserves",[47,6765,6766],{},"Cash and short-term US Treasuries, largely in a regulated government money market fund",[47,6768,6769],{},"Mostly US Treasuries plus other assets, including bitcoin and secured loans",[29,6771,6772,6775,6784],{},[47,6773,6774],{},"Attestations",[47,6776,6777,6778,6783],{},"Monthly, by an independent accounting firm (",[133,6779,6782],{"href":6780,"rel":6781},"https:\u002F\u002Fwww.circle.com\u002Ftransparency",[137],"circle.com\u002Ftransparency",")",[47,6785,6786,6787,6783],{},"Quarterly (",[133,6788,6791],{"href":6789,"rel":6790},"https:\u002F\u002Ftether.to\u002Fen\u002Ftransparency\u002F",[137],"tether.to\u002Ftransparency",[29,6793,6794,6797,6800],{},[47,6795,6796],{},"Circulating supply",[47,6798,6799],{},"Second largest",[47,6801,6802],{},"Largest by a wide margin",[29,6804,6805,6808,6811],{},[47,6806,6807],{},"Liquidity depth",[47,6809,6810],{},"Strongest in US and European venues",[47,6812,6813],{},"Strongest globally, dominant in emerging markets",[29,6815,6816,6819,6822],{},[47,6817,6818],{},"Regulatory posture",[47,6820,6821],{},"Aligned early with US and EU frameworks; MiCA-authorized issuance in the EU",[47,6823,6824],{},"Historically offshore; has faced US regulatory settlements over past disclosures",[29,6826,6827,6830,6833],{},[47,6828,6829],{},"Typical strength",[47,6831,6832],{},"Compliance-sensitive flows, US corridors",[47,6834,6835],{},"Emerging-market corridors, deepest market acceptance",[18,6837,6839],{"id":6838},"what-do-the-numbers-look-like-in-2026","What do the numbers look like in 2026?",[11,6841,6842],{},"Scale first: USDT remains the largest stablecoin, with circulating supply well above 100 billion dollars, roughly twice USDC's, and it consistently ranks as the most traded asset in all of crypto. USDC leads in a different column: regulated venues, US trading pairs, and on-chain payment integrations in US and European fintech.",[11,6844,6845],{},"Geography splits the same way. Public blockchain data shows Tron, where USDT dominates, carrying the majority of small retail-sized stablecoin transfers, the signature of emerging-market usage: remittances, savings, and merchant payments across Latin America, Africa, and Asia. USDC's share concentrates on Ethereum and Base, where US institutional and fintech flows live.",[11,6847,6848],{},"Neither dataset declares a winner. They describe two markets: USDT owns the global street, USDC owns the regulated stack. A payments business usually needs to touch both.",[18,6850,6852],{"id":6851},"why-do-compliance-focused-businesses-lean-toward-usdc","Why do compliance-focused businesses lean toward USDC?",[11,6854,6855],{},"Three reasons come up consistently:",[144,6857,6858,6864,6874],{},[147,6859,6860,6863],{},[150,6861,6862],{},"Reserve visibility."," Monthly third-party attestations with a simple reserve composition (cash plus short-term Treasuries) are easy for a finance or compliance team to underwrite.",[147,6865,6866,6869,6870,6873],{},[150,6867,6868],{},"Regulatory alignment."," Circle pursued regulation early: US state licenses, EU authorization under MiCA, and public-company reporting since its 2025 listing. For companies whose own regulators ask questions about counterparties, this shortens the conversation. Our ",[133,6871,6872],{"href":171},"MiCA guide"," covers what authorized issuance means in practice.",[147,6875,6876,6879],{},[150,6877,6878],{},"Banking compatibility."," Banks and auditors are more familiar with USDC's structure, which matters when stablecoin flows touch audited financial statements.",[11,6881,6882],{},"The cost of that posture showed once: in March 2023, a portion of USDC reserves sat at a failing US bank and the token briefly traded below one dollar before recovering fully within days. The lesson was about bank concentration, not backing, and Circle restructured reserve custody afterward.",[18,6884,6886],{"id":6885},"why-does-usdt-dominate-emerging-markets","Why does USDT dominate emerging markets?",[11,6888,6889],{},"USDT got there first and built liquidity where dollar demand is strongest. In Latin America, Africa, South Asia, and Southeast Asia, USDT is often the default digital dollar: more local exchange pairs, more P2P volume, more counterparties that quote in it. For payment flows into these regions, USDT frequently has tighter effective spreads simply because more of it changes hands.",[11,6891,6892],{},"Tether's history includes real blemishes: US regulators fined it in 2021 over historical misstatements about reserves, and its attestations are quarterly rather than monthly. Its scale is also its argument: USDT has held its peg through repeated market crises while remaining the most traded crypto asset in the world.",[18,6894,6896],{"id":6895},"which-one-should-a-payments-business-actually-use","Which one should a payments business actually use?",[11,6898,6899],{},"Both, routed by corridor. The practical pattern we see:",[144,6901,6902,6911,6922],{},[147,6903,6904,6907,6908,6910],{},[150,6905,6906],{},"US collections and compliance-heavy flows: USDC."," Incoming ACH and wire transfers through ",[133,6909,1570],{"href":1067}," settle naturally as USDC.",[147,6912,6913,6916,6917,6919,6920,329],{},[150,6914,6915],{},"Emerging-market payouts: whichever the corridor favors."," A payout to Brazil works identically from USDC or USDT; the receiver gets reais over Pix either way. Compare live rates: ",[133,6918,1073],{"href":1072}," vs ",[133,6921,1684],{"href":1683},[147,6923,6924,6927],{},[150,6925,6926],{},"Treasury: hold what you can underwrite."," Many businesses hold USDC as the treasury asset and convert to USDT only at the moment a corridor needs it.",[11,6929,6930,6931,6933,6934,329],{},"The deciding factor is rarely the token; it is whether your ",[133,6932,5916],{"href":1283}," supports both and lets you switch per corridor without new integrations. That flexibility is a line item in our ",[133,6935,6936],{"href":916},"provider comparison",[18,6938,6940],{"id":6939},"how-do-their-track-records-under-stress-compare","How do their track records under stress compare?",[11,6942,6943],{},"Both tokens have been tested, and both recovered, but the failure modes differ:",[144,6945,6946,6952],{},[147,6947,6948,6951],{},[150,6949,6950],{},"USDC, March 2023."," Roughly 8 percent of reserves sat at Silicon Valley Bank when it failed. USDC traded as low as about 87 cents over a weekend, then returned to the peg within days once US authorities guaranteed deposits. The reserves were real; the risk was bank concentration, and Circle moved reserve custody primarily into a regulated government money market fund and global systemically important banks afterward.",[147,6953,6954,6957],{},[150,6955,6956],{},"USDT, repeatedly since 2017."," USDT has seen brief discounts during market panics, including 2018 solvency rumors and the 2022 Terra collapse, when it processed billions in redemptions within days and returned to the peg each time. Its historical issue was disclosure, not redemption: US regulators fined Tether in 2021 for past misstatements about reserve composition.",[11,6959,6960],{},"The practical read: USDC's risk is concentrated and visible (US banking system exposure), USDT's is structural and reputational (broader reserve mix, lighter disclosure cadence). Businesses that must explain their choices to auditors usually find USDC's story easier to tell; businesses optimizing for market depth in emerging corridors keep using USDT through every news cycle.",[18,6962,6964],{"id":6963},"how-does-chain-support-differ-in-practice","How does chain support differ in practice?",[11,6966,6967],{},"Both tokens exist on many blockchains, but their centers of gravity differ. USDC issues natively on Ethereum, Base, Solana, Polygon, Arbitrum, and other US-favored networks, with Circle's cross-chain transfer protocol moving native USDC between them. USDT's largest deployment by far is on Tron, which dominates emerging-market P2P flows because transfers cost fractions of a cent, alongside major supply on Ethereum and Solana.",[11,6969,6970,6971,6973],{},"For payments this matters twice. First, the counterparty side: an exchange or OTC desk in Lagos or São Paulo most likely quotes USDT on Tron. Second, the cost side: network fees on the wrong chain can exceed the payment fee itself. A good ",[133,6972,5916],{"href":1283}," abstracts chain selection entirely, which removes this whole decision from your integration.",[18,6975,6977],{"id":6976},"what-about-the-other-stablecoins","What about the other stablecoins?",[11,6979,6980],{},"PYUSD (PayPal), RLUSD (Ripple), and bank-issued tokens are growing but remain a small fraction of payment volume. Yield-bearing dollar tokens are treated differently by regulators and are generally unsuitable as a payment leg. For business payments in 2026, USDC and USDT cover nearly every corridor that matters; new entrants earn their place corridor by corridor.",[18,6982,6984],{"id":6983},"how-does-blindpay-handle-usdc-and-usdt","How does BlindPay handle USDC and USDT?",[11,6986,6987,6989,6990,6992],{},[133,6988,952],{"href":951}," supports both tokens through one API: convert USDC or USDT to local fiat and pay out over Pix, SPEI, ACH, and wire in 100+ countries, or collect fiat that settles as stablecoins, with KYC and sanctions screening on every flow and flat ",[133,6991,968],{"href":967},". Live corridor quotes are public, so you can compare the effective rate per token before moving anything.",[11,6994,6995],{},[1210,6996,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":6998},[6999,7000,7001,7002,7003,7004,7005,7006,7007],{"id":6730,"depth":520,"text":6731},{"id":6838,"depth":520,"text":6839},{"id":6851,"depth":520,"text":6852},{"id":6885,"depth":520,"text":6886},{"id":6895,"depth":520,"text":6896},{"id":6939,"depth":520,"text":6940},{"id":6963,"depth":520,"text":6964},{"id":6976,"depth":520,"text":6977},{"id":6983,"depth":520,"text":6984},"USDC offers stronger reserve transparency and US regulatory posture; USDT offers deeper liquidity in emerging markets. Most payment flows should support both.",[7010,7013,7016,7019],{"q":7011,"a":7012},"Is USDC or USDT better for business payments?","Neither is better everywhere. USDC is generally preferred by US and European businesses for reserve transparency and regulatory alignment. USDT has deeper liquidity and wider acceptance in emerging markets. Payment infrastructure should support both so each corridor can use what works locally.",{"q":7014,"a":7015},"Are USDC and USDT both fully backed?","Both issuers report full reserves. Circle publishes monthly attestations of USDC reserves held in cash and short-term US Treasuries. Tether publishes quarterly attestations for USDT. The frequency and the historical track record of disclosure differ, which is a core part of the comparison.",{"q":7017,"a":7018},"Do USDC and USDT trade at different prices?","Both target one US dollar and normally trade within a fraction of a cent of it. Brief deviations happen under stress: USDC dipped in March 2023 during a US banking failure and recovered within days; USDT has seen similar short-lived discounts in past market events.",{"q":7020,"a":7021},"Can I convert USDT to local currency like Brazilian reais?","Yes. Stablecoin payment providers convert USDT or USDC to local fiat and deliver over local rails, for example a Pix transfer in Brazil, without the receiver touching crypto.",{"author":555},"---\ntitle: \"USDC vs USDT for payments: which should businesses use?\"\nseoTitle: \"USDC vs USDT for payments: which should businesses use?\"\ndescription: \"USDC offers stronger reserve transparency and US regulatory posture; USDT offers deeper liquidity in emerging markets. Most payment flows should support both.\"\ndate: \"2026-08-15\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"Is USDC or USDT better for business payments?\"\n    a: \"Neither is better everywhere. USDC is generally preferred by US and European businesses for reserve transparency and regulatory alignment. USDT has deeper liquidity and wider acceptance in emerging markets. Payment infrastructure should support both so each corridor can use what works locally.\"\n  - q: \"Are USDC and USDT both fully backed?\"\n    a: \"Both issuers report full reserves. Circle publishes monthly attestations of USDC reserves held in cash and short-term US Treasuries. Tether publishes quarterly attestations for USDT. The frequency and the historical track record of disclosure differ, which is a core part of the comparison.\"\n  - q: \"Do USDC and USDT trade at different prices?\"\n    a: \"Both target one US dollar and normally trade within a fraction of a cent of it. Brief deviations happen under stress: USDC dipped in March 2023 during a US banking failure and recovered within days; USDT has seen similar short-lived discounts in past market events.\"\n  - q: \"Can I convert USDT to local currency like Brazilian reais?\"\n    a: \"Yes. Stablecoin payment providers convert USDT or USDC to local fiat and deliver over local rails, for example a Pix transfer in Brazil, without the receiver touching crypto.\"\n---\n\nUSDC and USDT are the two dollar stablecoins that matter for payments, and the honest answer to \"which one?\" is: it depends on where your money goes. USDC leads on reserve transparency and regulatory posture, which US and European businesses care about. USDT leads on liquidity and acceptance across emerging markets, where much of real-world stablecoin usage lives. Together they account for the large majority of the 200+ billion dollars in circulating stablecoin supply tracked by [DefiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins).\n\nIf stablecoins themselves are new territory, read [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin) first; this article assumes the basics.\n\n## How do USDC and USDT compare at a glance?\n\n| Dimension | USDC (Circle) | USDT (Tether) |\n|---|---|---|\n| Issuer | Circle, US-based, publicly listed | Tether, incorporated in El Salvador |\n| Reserves | Cash and short-term US Treasuries, largely in a regulated government money market fund | Mostly US Treasuries plus other assets, including bitcoin and secured loans |\n| Attestations | Monthly, by an independent accounting firm ([circle.com\u002Ftransparency](https:\u002F\u002Fwww.circle.com\u002Ftransparency)) | Quarterly ([tether.to\u002Ftransparency](https:\u002F\u002Ftether.to\u002Fen\u002Ftransparency\u002F)) |\n| Circulating supply | Second largest | Largest by a wide margin |\n| Liquidity depth | Strongest in US and European venues | Strongest globally, dominant in emerging markets |\n| Regulatory posture | Aligned early with US and EU frameworks; MiCA-authorized issuance in the EU | Historically offshore; has faced US regulatory settlements over past disclosures |\n| Typical strength | Compliance-sensitive flows, US corridors | Emerging-market corridors, deepest market acceptance |\n\n## What do the numbers look like in 2026?\n\nScale first: USDT remains the largest stablecoin, with circulating supply well above 100 billion dollars, roughly twice USDC's, and it consistently ranks as the most traded asset in all of crypto. USDC leads in a different column: regulated venues, US trading pairs, and on-chain payment integrations in US and European fintech.\n\nGeography splits the same way. Public blockchain data shows Tron, where USDT dominates, carrying the majority of small retail-sized stablecoin transfers, the signature of emerging-market usage: remittances, savings, and merchant payments across Latin America, Africa, and Asia. USDC's share concentrates on Ethereum and Base, where US institutional and fintech flows live.\n\nNeither dataset declares a winner. They describe two markets: USDT owns the global street, USDC owns the regulated stack. A payments business usually needs to touch both.\n\n## Why do compliance-focused businesses lean toward USDC?\n\nThree reasons come up consistently:\n\n- **Reserve visibility.** Monthly third-party attestations with a simple reserve composition (cash plus short-term Treasuries) are easy for a finance or compliance team to underwrite.\n- **Regulatory alignment.** Circle pursued regulation early: US state licenses, EU authorization under MiCA, and public-company reporting since its 2025 listing. For companies whose own regulators ask questions about counterparties, this shortens the conversation. Our [MiCA guide](\u002Fresources\u002Fmore\u002Fmica-stablecoin-rules-explained) covers what authorized issuance means in practice.\n- **Banking compatibility.** Banks and auditors are more familiar with USDC's structure, which matters when stablecoin flows touch audited financial statements.\n\nThe cost of that posture showed once: in March 2023, a portion of USDC reserves sat at a failing US bank and the token briefly traded below one dollar before recovering fully within days. The lesson was about bank concentration, not backing, and Circle restructured reserve custody afterward.\n\n## Why does USDT dominate emerging markets?\n\nUSDT got there first and built liquidity where dollar demand is strongest. In Latin America, Africa, South Asia, and Southeast Asia, USDT is often the default digital dollar: more local exchange pairs, more P2P volume, more counterparties that quote in it. For payment flows into these regions, USDT frequently has tighter effective spreads simply because more of it changes hands.\n\nTether's history includes real blemishes: US regulators fined it in 2021 over historical misstatements about reserves, and its attestations are quarterly rather than monthly. Its scale is also its argument: USDT has held its peg through repeated market crises while remaining the most traded crypto asset in the world.\n\n## Which one should a payments business actually use?\n\nBoth, routed by corridor. The practical pattern we see:\n\n- **US collections and compliance-heavy flows: USDC.** Incoming ACH and wire transfers through [virtual accounts](\u002Fvirtual-accounts) settle naturally as USDC.\n- **Emerging-market payouts: whichever the corridor favors.** A payout to Brazil works identically from USDC or USDT; the receiver gets reais over Pix either way. Compare live rates: [USDC to BRL](\u002Fusdc-to-brl) vs [USDT to BRL](\u002Fusdt-to-brl).\n- **Treasury: hold what you can underwrite.** Many businesses hold USDC as the treasury asset and convert to USDT only at the moment a corridor needs it.\n\nThe deciding factor is rarely the token; it is whether your [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) supports both and lets you switch per corridor without new integrations. That flexibility is a line item in our [provider comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026).\n\n## How do their track records under stress compare?\n\nBoth tokens have been tested, and both recovered, but the failure modes differ:\n\n- **USDC, March 2023.** Roughly 8 percent of reserves sat at Silicon Valley Bank when it failed. USDC traded as low as about 87 cents over a weekend, then returned to the peg within days once US authorities guaranteed deposits. The reserves were real; the risk was bank concentration, and Circle moved reserve custody primarily into a regulated government money market fund and global systemically important banks afterward.\n- **USDT, repeatedly since 2017.** USDT has seen brief discounts during market panics, including 2018 solvency rumors and the 2022 Terra collapse, when it processed billions in redemptions within days and returned to the peg each time. Its historical issue was disclosure, not redemption: US regulators fined Tether in 2021 for past misstatements about reserve composition.\n\nThe practical read: USDC's risk is concentrated and visible (US banking system exposure), USDT's is structural and reputational (broader reserve mix, lighter disclosure cadence). Businesses that must explain their choices to auditors usually find USDC's story easier to tell; businesses optimizing for market depth in emerging corridors keep using USDT through every news cycle.\n\n## How does chain support differ in practice?\n\nBoth tokens exist on many blockchains, but their centers of gravity differ. USDC issues natively on Ethereum, Base, Solana, Polygon, Arbitrum, and other US-favored networks, with Circle's cross-chain transfer protocol moving native USDC between them. USDT's largest deployment by far is on Tron, which dominates emerging-market P2P flows because transfers cost fractions of a cent, alongside major supply on Ethereum and Solana.\n\nFor payments this matters twice. First, the counterparty side: an exchange or OTC desk in Lagos or São Paulo most likely quotes USDT on Tron. Second, the cost side: network fees on the wrong chain can exceed the payment fee itself. A good [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) abstracts chain selection entirely, which removes this whole decision from your integration.\n\n## What about the other stablecoins?\n\nPYUSD (PayPal), RLUSD (Ripple), and bank-issued tokens are growing but remain a small fraction of payment volume. Yield-bearing dollar tokens are treated differently by regulators and are generally unsuitable as a payment leg. For business payments in 2026, USDC and USDT cover nearly every corridor that matters; new entrants earn their place corridor by corridor.\n\n## How does BlindPay handle USDC and USDT?\n\n[BlindPay](\u002Fglobal-payments) supports both tokens through one API: convert USDC or USDT to local fiat and pay out over Pix, SPEI, ACH, and wire in 100+ countries, or collect fiat that settles as stablecoins, with KYC and sanctions screening on every flow and flat [published pricing](\u002Fpricing). Live corridor quotes are public, so you can compare the effective rate per token before moving anything.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":6712,"description":7008},"resources\u002Fmore\u002Fusdc-vs-usdt-for-payments","NXzcdedGgYDjVYtqU7JnnRi3a0isnK8KpltY9xliaLk",{"id":7028,"title":7029,"authors":6,"body":7030,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":7462,"description":7463,"extension":536,"faq":7464,"howto":6,"isBlog":553,"isChangelog":553,"meta":7483,"navigation":556,"path":4932,"pillar":553,"products":6,"rawbody":7484,"role":6,"seo":7485,"seoTitle":7486,"stem":7487,"thumbnail":6,"updated":7462,"__hash__":7488},"content\u002Fresources\u002Fmore\u002Fwallet-api-vs-embedded-wallet-sdk-vs-white-label.md","Wallet API vs embedded SDK vs white-label: which fits?",{"type":8,"value":7031,"toc":7451},[7032,7035,7045,7049,7052,7102,7106,7109,7116,7119,7130,7133,7137,7140,7158,7161,7172,7175,7179,7182,7185,7196,7199,7203,7206,7306,7310,7313,7356,7360,7363,7366,7374,7384,7391,7395,7398,7439,7441,7444],[11,7033,7034],{},"Choose a wallet API if you have engineers and need full control of the product, an embedded wallet SDK if you want wallets inside a consumer app without building key flows, and a white-label wallet if speed to launch matters more than control. Most teams land on an API or an SDK, and plenty use both.",[11,7036,7037,7038,7041,7042,7044],{},"All three are forms of ",[150,7039,7040],{},"wallet as a service (WaaS)",": hosted wallet infrastructure where the provider runs key management, signing, and chain connectivity. What changes is how much of the product you build around it. If you're earlier in the project, ",[133,7043,5177],{"href":5176}," covers the components first.",[18,7046,7048],{"id":7047},"wallet-api-embedded-sdk-or-white-label-which-should-you-choose","Wallet API, embedded SDK, or white-label: which should you choose?",[11,7050,7051],{},"The choice comes down to two questions: who signs transactions, and how much of the interface you want to own. If your backend signs, use an API. If your users sign inside your app, use an SDK. If you want someone else to own the whole app for now, use white-label.",[23,7053,7054,7067],{},[26,7055,7056],{},[29,7057,7058,7061,7064],{},[32,7059,7060],{},"Choose",[32,7062,7063],{},"When",[32,7065,7066],{},"Avoid when",[42,7068,7069,7080,7091],{},[29,7070,7071,7074,7077],{},[47,7072,7073],{},"Wallet API",[47,7075,7076],{},"Your backend moves funds, you need custom flows, and you have engineers to build the interface",[47,7078,7079],{},"You need a consumer wallet live before you can staff the work",[29,7081,7082,7085,7088],{},[47,7083,7084],{},"Embedded SDK",[47,7086,7087],{},"Your users sign their own transactions inside your web or mobile app",[47,7089,7090],{},"You need deep control over key flows or unusual chains the SDK doesn't cover",[29,7092,7093,7096,7099],{},[47,7094,7095],{},"White-label",[47,7097,7098],{},"You're testing demand, or the wallet is a side feature",[47,7100,7101],{},"The wallet is the core of your product and roadmap",[18,7103,7105],{"id":7104},"what-is-a-wallet-api-and-when-does-it-fit","What is a wallet API and when does it fit?",[11,7107,7108],{},"A wallet API is a set of server-side endpoints for creating wallets, reading balances, requesting signatures, and receiving webhooks about on-chain activity. Your backend calls the provider, the provider signs under policies you configure, and you build every screen the user sees.",[11,7110,7111,7112,7115],{},"Providers usually protect keys behind a wallet API with MPC or a ",[150,7113,7114],{},"hardware security module (HSM)",", a tamper-resistant device that stores keys and signs without exposing them. You never handle raw keys. You do own the policy engine configuration: which destinations are allowed, which amounts need a second approver, and which API keys can request a signature.",[11,7117,7118],{},"A wallet API fits when:",[144,7120,7121,7124,7127],{},[147,7122,7123],{},"Your backend initiates transfers: payouts, treasury moves, fee collection, refunds.",[147,7125,7126],{},"You need custom flows that no prebuilt UI supports.",[147,7128,7129],{},"You serve businesses, not consumers, and signing happens under company policy rather than a user's thumb.",[11,7131,7132],{},"Your responsibility is larger than it looks. API credentials become the keys to the kingdom, so they need rotation, scoping, and monitoring. Retries need idempotency so a network blip doesn't sign a transfer twice. And every state a transaction can be in needs a screen.",[18,7134,7136],{"id":7135},"what-is-an-embedded-wallet-sdk-and-when-does-it-fit","What is an embedded wallet SDK and when does it fit?",[11,7138,7139],{},"An embedded wallet SDK is a client library that creates a wallet for each user inside your web or mobile app. The user logs in with an email, a social account, or a passkey, and the SDK handles key creation, storage, and signing prompts. Nobody installs a separate wallet app.",[11,7141,7142,7143,7148,7149,7154,7155,7157],{},"Under the hood, embedded wallets usually split the key into MPC shares between the user's device and the provider, or keep it in the device's secure hardware. Passkey login builds on the ",[133,7144,7147],{"href":7145,"rel":7146},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fwebauthn-3\u002F",[137],"W3C WebAuthn standard",". Some SDKs deploy a smart-contract account for each user, following ",[133,7150,7153],{"href":7151,"rel":7152},"https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-4337",[137],"ERC-4337",", which adds features like sponsored gas and spending limits. ",[133,7156,4577],{"href":4576}," explains how the share split decides who controls the funds.",[11,7159,7160],{},"An embedded SDK fits when:",[144,7162,7163,7166,7169],{},[147,7164,7165],{},"Your users are consumers or small businesses who have never used a crypto wallet.",[147,7167,7168],{},"Users sign their own transactions, and you want the prompt inside your interface.",[147,7170,7171],{},"You want wallets tied to your existing login instead of a recovery phrase.",[11,7173,7174],{},"Check four things before you commit: platform coverage (web, iOS, Android, React Native), how far the prebuilt UI can be customized, which chains and signature schemes are supported, and whether users can export their key if you ever change providers.",[18,7176,7178],{"id":7177},"what-is-a-white-label-wallet-and-when-does-it-fit","What is a white-label wallet and when does it fit?",[11,7180,7181],{},"A white-label wallet is a finished wallet application that the provider runs and you brand as your own. You configure logos, colors, supported assets, and sometimes fees. The provider owns the code, the release schedule, and usually much of the user data.",[11,7183,7184],{},"A white-label wallet fits when:",[144,7186,7187,7190,7193],{},[147,7188,7189],{},"You're running a pilot to see whether your users want a wallet at all.",[147,7191,7192],{},"The wallet is a side feature, not the product.",[147,7194,7195],{},"You have no engineering capacity for wallet work this year.",[11,7197,7198],{},"The trade-off shows up later. Features you need wait on the provider's roadmap. User data may live in the provider's systems under its terms. And moving users to your own wallet means new addresses for every one of them, which is a support campaign, not a deploy.",[18,7200,7202],{"id":7201},"how-do-the-three-models-compare","How do the three models compare?",[11,7204,7205],{},"The three models trade control for speed. A wallet API gives the most control and the most work, a white-label wallet the least of both, and an embedded SDK sits in the middle. There is no reliable public benchmark for launch times, so the table describes relative effort.",[23,7207,7208,7220],{},[26,7209,7210],{},[29,7211,7212,7214,7216,7218],{},[32,7213],{},[32,7215,7073],{},[32,7217,7084],{},[32,7219,7095],{},[42,7221,7222,7236,7250,7264,7278,7292],{},[29,7223,7224,7227,7230,7233],{},[47,7225,7226],{},"Control over UX and data",[47,7228,7229],{},"Full",[47,7231,7232],{},"Your app, with prebuilt wallet flows",[47,7234,7235],{},"Branding and configuration",[29,7237,7238,7241,7244,7247],{},[47,7239,7240],{},"Time to launch",[47,7242,7243],{},"Longest",[47,7245,7246],{},"Medium",[47,7248,7249],{},"Shortest",[29,7251,7252,7255,7258,7261],{},[47,7253,7254],{},"Engineering effort",[47,7256,7257],{},"High: backend, policies, every screen",[47,7259,7260],{},"Medium: app integration, login, states",[47,7262,7263],{},"Low: configuration and support",[29,7265,7266,7269,7272,7275],{},[47,7267,7268],{},"Security responsibility",[47,7270,7271],{},"Shared: provider protects keys, you own policies and credentials",[47,7273,7274],{},"Shared: provider owns key flows, you own the app and session security",[47,7276,7277],{},"Mostly the provider",[29,7279,7280,7283,7286,7289],{},[47,7281,7282],{},"Vendor lock-in",[47,7284,7285],{},"Medium: addresses and policies tie you in",[47,7287,7288],{},"Medium to high: user keys live in the provider's scheme",[47,7290,7291],{},"High: the whole product lives with the provider",[29,7293,7294,7297,7300,7303],{},[47,7295,7296],{},"Cost drivers",[47,7298,7299],{},"Platform fee, per-wallet or per-transaction fees, gas",[47,7301,7302],{},"Monthly active wallets, per-transaction fees, gas sponsorship",[47,7304,7305],{},"Licensing or revenue share, per-user fees",[18,7307,7309],{"id":7308},"which-model-fits-five-yesno-questions","Which model fits? Five yes\u002Fno questions",[11,7311,7312],{},"Answer these in order. Each answer either points to a model or sends you to the next question.",[289,7314,7315,7321,7327,7339,7345],{},[147,7316,7317,7320],{},[150,7318,7319],{},"Do you need a wallet in front of users before you can staff wallet engineering?"," Yes: start with a white-label pilot, and plan the migration now. No: go to question 2.",[147,7322,7323,7326],{},[150,7324,7325],{},"Will end users sign transactions themselves inside your app?"," No, your backend moves the funds: use a wallet API. Yes: go to question 3.",[147,7328,7329,7332,7333,7338],{},[150,7330,7331],{},"Do most of your users already have their own wallets?"," Yes: let them connect those wallets through the standard ",[133,7334,7337],{"href":7335,"rel":7336},"https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-1193",[137],"EIP-1193 provider interface",", and skip the wallet vendor for them. No: use an embedded SDK.",[147,7340,7341,7344],{},[150,7342,7343],{},"Does your company also move its own funds, such as treasury, fees, or payouts?"," Yes: add a wallet API with approval policies next to the SDK. No: the SDK alone may be enough.",[147,7346,7347,7350,7351,7355],{},[150,7348,7349],{},"Does money have to reach bank accounts?"," Yes: add a payments layer for on-ramps and off-ramps. No wallet model solves that on its own. ",[133,7352,7354],{"href":7353},"\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","What is a crypto on-ramp and off-ramp"," explains the pieces.",[18,7357,7359],{"id":7358},"how-do-wallet-infrastructure-and-payments-infrastructure-work-together","How do wallet infrastructure and payments infrastructure work together?",[11,7361,7362],{},"Wallet infrastructure holds and signs. Payments infrastructure connects the wallet to bank accounts. They're separate layers, and keeping them separate lets you change one without rebuilding the other.",[11,7364,7365],{},"A typical stack looks like this:",[3097,7367,7372],{"className":7368,"code":7370,"language":7371,"meta":519},[7369],"language-text","1. Your app            login, balances, business logic\n        |\n2. Wallet provider     creates wallets, holds or splits keys, signs under your policies\n        |              (for example Privy, Dfns, Circle wallets, Fireblocks, or Utila)\n        |\n3. BlindPay            virtual accounts, quotes, on-ramp and off-ramp, payouts\n        |\n4. Local rails         Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), TED, ACH Colombia\n","text",[485,7373,7370],{"__ignoreMap":519},[11,7375,7376,7377,7379,7380,7383],{},"Here's how the layers meet. The wallet address your provider creates is registered with BlindPay as a ",[133,7378,3088],{"href":3087},". A ",[133,7381,7382],{"href":2926},"virtual account"," gives the customer US bank details, and each deposit converts to USDC or USDT and lands at that address. For a payout, the wallet authorizes the quoted amount, and BlindPay converts it and pays out on the local rail.",[11,7385,7386,7387,7390],{},"BlindPay is not the wallet provider in this picture. It never holds the keys to that wallet, and the wallet provider never has to touch a bank. The integration model only changes who signs the payout authorization: the user in an embedded wallet, or your backend under policy with a wallet API. Nothing has to be pre-funded for an external-wallet payout, as ",[133,7388,7389],{"href":4881},"what no pre-funding means"," explains.",[18,7392,7394],{"id":7393},"what-mistakes-do-teams-make-when-choosing-an-integration-model","What mistakes do teams make when choosing an integration model?",[11,7396,7397],{},"Most mistakes come from choosing on the demo instead of on the key architecture and the exit. Five that come up again and again:",[289,7399,7400,7406,7412,7423,7429],{},[147,7401,7402,7405],{},[150,7403,7404],{},"Picking on UI polish."," A smooth demo says nothing about who can sign without the user. Ask for the key and share diagram first.",[147,7407,7408,7411],{},[150,7409,7410],{},"Ignoring chain coverage until chain two."," Ethereum and Tron sign with ECDSA, Solana and Stellar with Ed25519. A provider that supports one scheme well may not support the other, and your second chain becomes a second vendor.",[147,7413,7414,7417,7418,7422],{},[150,7415,7416],{},"Treating the wallet as the payments stack."," A wallet holds stablecoins. It doesn't collect ACH deposits, run KYC, or pay out over Pix. Budget the payments layer from the start (",[133,7419,7421],{"href":7420},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","build vs buy"," shows what that layer contains).",[147,7424,7425,7428],{},[150,7426,7427],{},"No exit plan."," Key export, address export, and transaction history export belong in the contract before launch, not after a price increase.",[147,7430,7431,7434,7435,7438],{},[150,7432,7433],{},"Leaving compliance for later."," User verification and wallet address screening need hooks in the first version. Retrofitting them means re-onboarding users. ",[133,7436,7437],{"href":3937},"How to automate KYC and KYB"," covers the verification side.",[18,7440,2829],{"id":2828},[11,7442,7443],{},"Run the five questions above with your product and engineering leads in one meeting, and write down the model for each flow: end users, treasury, and payouts. Then ask each shortlisted provider the same thing: who can sign without the user, and how do we leave?",[11,7445,7446,7447,7450],{},"If bank accounts are in scope, check the ",[133,7448,7449],{"href":3087},"blockchain wallet docs"," to see how a wallet from any of these models links to payins and payouts.",{"title":519,"searchDepth":520,"depth":520,"links":7452},[7453,7454,7455,7456,7457,7458,7459,7460,7461],{"id":7047,"depth":520,"text":7048},{"id":7104,"depth":520,"text":7105},{"id":7135,"depth":520,"text":7136},{"id":7177,"depth":520,"text":7178},{"id":7201,"depth":520,"text":7202},{"id":7308,"depth":520,"text":7309},{"id":7358,"depth":520,"text":7359},{"id":7393,"depth":520,"text":7394},{"id":2828,"depth":520,"text":2829},"2026-08-26","Compare the three wallet integration models on control, launch time, engineering effort, security, lock-in, and cost, with a five-question decision tree.",[7465,7468,7471,7474,7477,7480],{"q":7466,"a":7467},"What is wallet as a service (WaaS)?","Wallet as a service is hosted wallet infrastructure sold to businesses. The provider runs key management, signing, chain connectivity, and balance tracking, and exposes them through a backend API, a client SDK, or both. The business builds its product on top without operating key storage or blockchain nodes itself. White-label wallets are sometimes sold under the same name.",{"q":7469,"a":7470},"What is the difference between an embedded wallet and a wallet API?","An embedded wallet SDK runs inside your web or mobile app and creates a wallet for each user, who signs transactions in your interface after logging in with email, social, or a passkey. A wallet API runs on your server, and your backend creates wallets and requests signatures under policies you set. Consumer apps lean on SDKs. Treasury and payout flows lean on APIs.",{"q":7472,"a":7473},"Is a white-label crypto wallet a good idea?","A white-label wallet is a good idea for a pilot or a non-core feature, because it is the fastest way to put a branded wallet in front of users. It is a weaker choice when the wallet is central to your product, since the provider controls the roadmap, much of the user data, and how hard it is to leave.",{"q":7475,"a":7476},"Can I use more than one wallet integration model?","Yes, and many products do. A common setup is an embedded SDK for end users who sign their own transactions, plus a wallet API with approval policies for the company's treasury and payout wallets. The two models can come from the same provider or from different ones, as long as your backend tracks which addresses belong to which flow.",{"q":7478,"a":7479},"Which wallet integration model is fastest to launch?","White-label is fastest, because the provider ships the whole application and you mostly configure branding. An embedded SDK is next, since the provider supplies login, key, and signing flows while you build the rest of the app. A wallet API takes the most engineering, because your team builds every screen, policy, and state transition around the provider's endpoints.",{"q":7481,"a":7482},"Does the wallet model affect payouts to bank accounts?","Not directly. No wallet model on its own converts stablecoins into bank money. That needs an off-ramp with banking partners and local rails. The wallet model only changes who signs the authorization for a payout: the user in an embedded wallet, or your backend under policy with a wallet API. The payments integration can stay the same.",{"author":555},"---\ntitle: \"Wallet API vs embedded SDK vs white-label: which fits?\"\nseoTitle: \"Wallet API vs embedded wallet SDK vs white-label wallet\"\ndescription: \"Compare the three wallet integration models on control, launch time, engineering effort, security, lock-in, and cost, with a five-question decision tree.\"\ndate: \"2026-08-26\"\nupdated: \"2026-08-26\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is wallet as a service (WaaS)?\"\n    a: \"Wallet as a service is hosted wallet infrastructure sold to businesses. The provider runs key management, signing, chain connectivity, and balance tracking, and exposes them through a backend API, a client SDK, or both. The business builds its product on top without operating key storage or blockchain nodes itself. White-label wallets are sometimes sold under the same name.\"\n  - q: \"What is the difference between an embedded wallet and a wallet API?\"\n    a: \"An embedded wallet SDK runs inside your web or mobile app and creates a wallet for each user, who signs transactions in your interface after logging in with email, social, or a passkey. A wallet API runs on your server, and your backend creates wallets and requests signatures under policies you set. Consumer apps lean on SDKs. Treasury and payout flows lean on APIs.\"\n  - q: \"Is a white-label crypto wallet a good idea?\"\n    a: \"A white-label wallet is a good idea for a pilot or a non-core feature, because it is the fastest way to put a branded wallet in front of users. It is a weaker choice when the wallet is central to your product, since the provider controls the roadmap, much of the user data, and how hard it is to leave.\"\n  - q: \"Can I use more than one wallet integration model?\"\n    a: \"Yes, and many products do. A common setup is an embedded SDK for end users who sign their own transactions, plus a wallet API with approval policies for the company's treasury and payout wallets. The two models can come from the same provider or from different ones, as long as your backend tracks which addresses belong to which flow.\"\n  - q: \"Which wallet integration model is fastest to launch?\"\n    a: \"White-label is fastest, because the provider ships the whole application and you mostly configure branding. An embedded SDK is next, since the provider supplies login, key, and signing flows while you build the rest of the app. A wallet API takes the most engineering, because your team builds every screen, policy, and state transition around the provider's endpoints.\"\n  - q: \"Does the wallet model affect payouts to bank accounts?\"\n    a: \"Not directly. No wallet model on its own converts stablecoins into bank money. That needs an off-ramp with banking partners and local rails. The wallet model only changes who signs the authorization for a payout: the user in an embedded wallet, or your backend under policy with a wallet API. The payments integration can stay the same.\"\n---\n\nChoose a wallet API if you have engineers and need full control of the product, an embedded wallet SDK if you want wallets inside a consumer app without building key flows, and a white-label wallet if speed to launch matters more than control. Most teams land on an API or an SDK, and plenty use both.\n\nAll three are forms of **wallet as a service (WaaS)**: hosted wallet infrastructure where the provider runs key management, signing, and chain connectivity. What changes is how much of the product you build around it. If you're earlier in the project, [what is crypto wallet integration](\u002Fresources\u002Fmore\u002Fwhat-is-crypto-wallet-integration) covers the components first.\n\n## Wallet API, embedded SDK, or white-label: which should you choose?\n\nThe choice comes down to two questions: who signs transactions, and how much of the interface you want to own. If your backend signs, use an API. If your users sign inside your app, use an SDK. If you want someone else to own the whole app for now, use white-label.\n\n| Choose | When | Avoid when |\n| --- | --- | --- |\n| Wallet API | Your backend moves funds, you need custom flows, and you have engineers to build the interface | You need a consumer wallet live before you can staff the work |\n| Embedded SDK | Your users sign their own transactions inside your web or mobile app | You need deep control over key flows or unusual chains the SDK doesn't cover |\n| White-label | You're testing demand, or the wallet is a side feature | The wallet is the core of your product and roadmap |\n\n## What is a wallet API and when does it fit?\n\nA wallet API is a set of server-side endpoints for creating wallets, reading balances, requesting signatures, and receiving webhooks about on-chain activity. Your backend calls the provider, the provider signs under policies you configure, and you build every screen the user sees.\n\nProviders usually protect keys behind a wallet API with MPC or a **hardware security module (HSM)**, a tamper-resistant device that stores keys and signs without exposing them. You never handle raw keys. You do own the policy engine configuration: which destinations are allowed, which amounts need a second approver, and which API keys can request a signature.\n\nA wallet API fits when:\n\n- Your backend initiates transfers: payouts, treasury moves, fee collection, refunds.\n- You need custom flows that no prebuilt UI supports.\n- You serve businesses, not consumers, and signing happens under company policy rather than a user's thumb.\n\nYour responsibility is larger than it looks. API credentials become the keys to the kingdom, so they need rotation, scoping, and monitoring. Retries need idempotency so a network blip doesn't sign a transfer twice. And every state a transaction can be in needs a screen.\n\n## What is an embedded wallet SDK and when does it fit?\n\nAn embedded wallet SDK is a client library that creates a wallet for each user inside your web or mobile app. The user logs in with an email, a social account, or a passkey, and the SDK handles key creation, storage, and signing prompts. Nobody installs a separate wallet app.\n\nUnder the hood, embedded wallets usually split the key into MPC shares between the user's device and the provider, or keep it in the device's secure hardware. Passkey login builds on the [W3C WebAuthn standard](https:\u002F\u002Fwww.w3.org\u002FTR\u002Fwebauthn-3\u002F). Some SDKs deploy a smart-contract account for each user, following [ERC-4337](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-4337), which adds features like sponsored gas and spending limits. [Custodial vs non-custodial vs MPC wallets](\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets) explains how the share split decides who controls the funds.\n\nAn embedded SDK fits when:\n\n- Your users are consumers or small businesses who have never used a crypto wallet.\n- Users sign their own transactions, and you want the prompt inside your interface.\n- You want wallets tied to your existing login instead of a recovery phrase.\n\nCheck four things before you commit: platform coverage (web, iOS, Android, React Native), how far the prebuilt UI can be customized, which chains and signature schemes are supported, and whether users can export their key if you ever change providers.\n\n## What is a white-label wallet and when does it fit?\n\nA white-label wallet is a finished wallet application that the provider runs and you brand as your own. You configure logos, colors, supported assets, and sometimes fees. The provider owns the code, the release schedule, and usually much of the user data.\n\nA white-label wallet fits when:\n\n- You're running a pilot to see whether your users want a wallet at all.\n- The wallet is a side feature, not the product.\n- You have no engineering capacity for wallet work this year.\n\nThe trade-off shows up later. Features you need wait on the provider's roadmap. User data may live in the provider's systems under its terms. And moving users to your own wallet means new addresses for every one of them, which is a support campaign, not a deploy.\n\n## How do the three models compare?\n\nThe three models trade control for speed. A wallet API gives the most control and the most work, a white-label wallet the least of both, and an embedded SDK sits in the middle. There is no reliable public benchmark for launch times, so the table describes relative effort.\n\n| | Wallet API | Embedded SDK | White-label |\n| --- | --- | --- | --- |\n| Control over UX and data | Full | Your app, with prebuilt wallet flows | Branding and configuration |\n| Time to launch | Longest | Medium | Shortest |\n| Engineering effort | High: backend, policies, every screen | Medium: app integration, login, states | Low: configuration and support |\n| Security responsibility | Shared: provider protects keys, you own policies and credentials | Shared: provider owns key flows, you own the app and session security | Mostly the provider |\n| Vendor lock-in | Medium: addresses and policies tie you in | Medium to high: user keys live in the provider's scheme | High: the whole product lives with the provider |\n| Cost drivers | Platform fee, per-wallet or per-transaction fees, gas | Monthly active wallets, per-transaction fees, gas sponsorship | Licensing or revenue share, per-user fees |\n\n## Which model fits? Five yes\u002Fno questions\n\nAnswer these in order. Each answer either points to a model or sends you to the next question.\n\n1. **Do you need a wallet in front of users before you can staff wallet engineering?** Yes: start with a white-label pilot, and plan the migration now. No: go to question 2.\n2. **Will end users sign transactions themselves inside your app?** No, your backend moves the funds: use a wallet API. Yes: go to question 3.\n3. **Do most of your users already have their own wallets?** Yes: let them connect those wallets through the standard [EIP-1193 provider interface](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-1193), and skip the wallet vendor for them. No: use an embedded SDK.\n4. **Does your company also move its own funds, such as treasury, fees, or payouts?** Yes: add a wallet API with approval policies next to the SDK. No: the SDK alone may be enough.\n5. **Does money have to reach bank accounts?** Yes: add a payments layer for on-ramps and off-ramps. No wallet model solves that on its own. [What is a crypto on-ramp and off-ramp](\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp) explains the pieces.\n\n## How do wallet infrastructure and payments infrastructure work together?\n\nWallet infrastructure holds and signs. Payments infrastructure connects the wallet to bank accounts. They're separate layers, and keeping them separate lets you change one without rebuilding the other.\n\nA typical stack looks like this:\n\n```text\n1. Your app            login, balances, business logic\n        |\n2. Wallet provider     creates wallets, holds or splits keys, signs under your policies\n        |              (for example Privy, Dfns, Circle wallets, Fireblocks, or Utila)\n        |\n3. BlindPay            virtual accounts, quotes, on-ramp and off-ramp, payouts\n        |\n4. Local rails         Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), TED, ACH Colombia\n```\n\nHere's how the layers meet. The wallet address your provider creates is registered with BlindPay as a [blockchain wallet](\u002Fdocs\u002Fblockchain-wallets). A [virtual account](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained) gives the customer US bank details, and each deposit converts to USDC or USDT and lands at that address. For a payout, the wallet authorizes the quoted amount, and BlindPay converts it and pays out on the local rail.\n\nBlindPay is not the wallet provider in this picture. It never holds the keys to that wallet, and the wallet provider never has to touch a bank. The integration model only changes who signs the payout authorization: the user in an embedded wallet, or your backend under policy with a wallet API. Nothing has to be pre-funded for an external-wallet payout, as [what no pre-funding means](\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts) explains.\n\n## What mistakes do teams make when choosing an integration model?\n\nMost mistakes come from choosing on the demo instead of on the key architecture and the exit. Five that come up again and again:\n\n1. **Picking on UI polish.** A smooth demo says nothing about who can sign without the user. Ask for the key and share diagram first.\n2. **Ignoring chain coverage until chain two.** Ethereum and Tron sign with ECDSA, Solana and Stellar with Ed25519. A provider that supports one scheme well may not support the other, and your second chain becomes a second vendor.\n3. **Treating the wallet as the payments stack.** A wallet holds stablecoins. It doesn't collect ACH deposits, run KYC, or pay out over Pix. Budget the payments layer from the start ([build vs buy](\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments) shows what that layer contains).\n4. **No exit plan.** Key export, address export, and transaction history export belong in the contract before launch, not after a price increase.\n5. **Leaving compliance for later.** User verification and wallet address screening need hooks in the first version. Retrofitting them means re-onboarding users. [How to automate KYC and KYB](\u002Fresources\u002Fmore\u002Fhow-to-automate-kyc-kyb-stablecoin-payments) covers the verification side.\n\n## What to do next\n\nRun the five questions above with your product and engineering leads in one meeting, and write down the model for each flow: end users, treasury, and payouts. Then ask each shortlisted provider the same thing: who can sign without the user, and how do we leave?\n\nIf bank accounts are in scope, check the [blockchain wallet docs](\u002Fdocs\u002Fblockchain-wallets) to see how a wallet from any of these models links to payins and payouts.\n",{"title":7029,"description":7463},"Wallet API vs embedded wallet SDK vs white-label wallet","resources\u002Fmore\u002Fwallet-api-vs-embedded-wallet-sdk-vs-white-label","RtDTCwp3aULyNOmq4llwlZyA5m3QntiDJhhF3En0P-s",{"id":7490,"title":7491,"authors":6,"body":7492,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":7905,"description":7906,"extension":536,"faq":7907,"howto":7923,"isBlog":553,"isChangelog":553,"meta":7941,"navigation":556,"path":200,"pillar":553,"products":6,"rawbody":7942,"role":6,"seo":7943,"seoTitle":7944,"stem":7945,"thumbnail":6,"updated":6,"__hash__":7946},"content\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment.md","What happens on-chain in a stablecoin payment? A step-by-step walkthrough",{"type":8,"value":7493,"toc":7894},[7494,7497,7505,7508,7512,7515,7521,7525,7531,7538,7544,7549,7553,7556,7563,7568,7572,7575,7578,7655,7662,7683,7689,7693,7705,7708,7737,7740,7746,7750,7756,7765,7768,7772,7775,7863,7866,7870,7876,7879,7881,7890],[11,7495,7496],{},"A stablecoin payment works in four moves. A bank transfer lands in a virtual account, it's converted into USDC or USDT, the stablecoins settle on-chain to the customer's linked wallet, and for a payout they're converted back into local currency and sent over a rail like Pix or SPEI. The blockchain handles only the middle: a couple of short transactions, each confirmed in seconds to minutes, each with a public receipt.",[11,7498,7499,7500,7504],{},"The end-to-end version, with bank cut-offs and payout timing, is in ",[133,7501,7503],{"href":7502},"\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works","how a stablecoin payment works",". This walkthrough zooms in on the part most explainers skip: what the blockchain is actually doing at each step, and what an operations team can see while it happens.",[11,7506,7507],{},"No code required. If you can read a bank statement, you can follow this.",[18,7509,7511],{"id":7510},"what-does-the-whole-flow-look-like","What does the whole flow look like?",[11,7513,7514],{},"Picture a line of five boxes, left to right. The first and last are bank accounts. The three in the middle are the payment provider's conversion step, the customer's wallet, and the provider's conversion step again. Money enters on the left as dollars, becomes a stablecoin for the middle stretch, and leaves on the right as local currency. Only two arrows in the whole picture are on-chain: the delivery into the wallet, and the pull out of it.",[3097,7516,7519],{"className":7517,"code":7518,"language":7371},[7369],"[Payer's bank]\n     |  1. ACH, wire, or RTP deposit            (bank rail)\n     v\n[Virtual account in the customer's name]\n     |  2. dollars convert to USDC or USDT      (provider)\n     v\n[Customer's linked wallet]  \u003C-- 3. on-chain delivery, tx hash #1\n     |\n     |  4. wallet authorizes the payout amount\n     |     and the stablecoins are pulled        on-chain, tx hash #2\n     v\n[Provider's off-ramp]\n     |  5. stablecoins convert to local currency (provider)\n     v\n[Recipient's bank, paid over Pix or SPEI]       (bank rail)\n",[485,7520,7518],{"__ignoreMap":519},[18,7522,7524],{"id":7523},"step-1-a-bank-transfer-lands-in-a-virtual-account","Step 1: A bank transfer lands in a virtual account",[11,7526,7527,7528,498],{},"A virtual account is a real bank account number, routing and account, issued in your customer's name. Anyone can pay it like any other account. At BlindPay, each virtual account belongs to one customer and settles to one linked wallet, and a customer can hold more than one (",[133,7529,1570],{"href":7530},"\u002Fdocs\u002Fvirtual-accounts",[11,7532,7533,7534,7537],{},"Why that matters for reconciliation: every deposit into the account creates its own payin record. You match money to customers by account, not by hoping the payer typed a reference code correctly. Without a virtual account, a US payin returns BlindPay's bank details plus a ",[485,7535,7536],{},"memo_code"," the payer has to include.",[11,7539,7540,7543],{},[150,7541,7542],{},"On-chain so far:"," nothing. This step is pure banking. ACH and wire deposits can take up to five business days to arrive; RTP arrives in seconds.",[11,7545,7546,7547,329],{},"The approval flow and fees are covered in ",[133,7548,2927],{"href":2926},[18,7550,7552],{"id":7551},"step-2-the-deposit-converts-into-usdc-or-usdt","Step 2: The deposit converts into USDC or USDT",[11,7554,7555],{},"Once the deposit clears, the provider converts the dollars into a stablecoin at the rate locked in the quote. USDC is issued by Circle and USDT by Tether; both are designed to be redeemable one-for-one for US dollars through their issuers.",[11,7557,7558,7559,498],{},"New tokens come from one of two places. Either the issuer mints them against fresh dollars, or the provider sends tokens it already holds. BlindPay's docs describe exactly that: once the deposit is confirmed, BlindPay mints or transfers the equivalent stablecoin amount to the destination wallet (",[133,7560,7562],{"href":7561},"\u002Fdocs\u002Foverview","overview",[11,7564,7565,7567],{},[150,7566,7542],{}," possibly a mint on the issuer's side. Your customer doesn't see it and doesn't need to.",[18,7569,7571],{"id":7570},"step-3-stablecoins-settle-to-the-linked-wallet","Step 3: Stablecoins settle to the linked wallet",[11,7573,7574],{},"This is the first on-chain moment your team can actually look at. One transfer moves the stablecoins from the provider to the wallet linked to the virtual account.",[11,7576,7577],{},"A transfer \"confirms\" when a block containing it is added to the chain. It's final when the network guarantees that block can't be undone. How long that takes depends on the network:",[23,7579,7580,7592],{},[26,7581,7582],{},[29,7583,7584,7586,7589],{},[32,7585,60],{},[32,7587,7588],{},"New block roughly every",[32,7590,7591],{},"Practical finality",[42,7593,7594,7604,7614,7624,7634,7645],{},[29,7595,7596,7598,7601],{},[47,7597,3890],{},[47,7599,7600],{},"5 seconds",[47,7602,7603],{},"At ledger close, about 5 seconds",[29,7605,7606,7608,7611],{},[47,7607,3878],{},[47,7609,7610],{},"0.4 seconds",[47,7612,7613],{},"About 13 seconds",[29,7615,7616,7618,7621],{},[47,7617,3902],{},[47,7619,7620],{},"3 seconds",[47,7622,7623],{},"About a minute",[29,7625,7626,7628,7631],{},[47,7627,3818],{},[47,7629,7630],{},"2 seconds",[47,7632,7633],{},"Seconds",[29,7635,7636,7639,7642],{},[47,7637,7638],{},"Base, Arbitrum",[47,7640,7641],{},"2 seconds or less",[47,7643,7644],{},"Seconds for the sequencer, minutes to settle on Ethereum",[29,7646,7647,7649,7652],{},[47,7648,3805],{},[47,7650,7651],{},"12 seconds",[47,7653,7654],{},"About 13 minutes",[11,7656,7657,7658,7661],{},"Every confirmed transfer has a ",[150,7659,7660],{},"transaction hash",", a unique ID anyone can paste into a block explorer to see the amount, the sending and receiving addresses, and the time. It's a receipt no one can edit.",[11,7663,7664,7667,7668,7670,7671,7674,7675,7678,7679,7682],{},[150,7665,7666],{},"What BlindPay shows you:"," the payin fires ",[485,7669,3229],{}," once the stablecoins land, and the hash appears in the payin's ",[485,7672,7673],{},"tracking_complete"," object. One gotcha from the ",[133,7676,7677],{"href":3039},"payins docs",": during a gas spike, a broadcast transaction can be replaced by another one, so the final hash may differ from the first one you saw. Treat the payin ",[485,7680,7681],{},"status"," as the source of truth, not a specific hash.",[11,7684,7685,7686,329],{},"The wallet itself comes in two kinds. An external wallet is controlled by your customer. A managed wallet is custodied by BlindPay (in beta). Why that choice matters for risk is in ",[133,7687,7688],{"href":3337},"non-custodial payments",[18,7690,7692],{"id":7691},"step-4-the-wallet-authorizes-the-payout","Step 4: The wallet authorizes the payout",[11,7694,7695,7696,7700,7701,329],{},"Paying someone starts with a quote: the rate, the fee, and exactly how much local currency arrives. At BlindPay a payout quote lasts five minutes (",[133,7697,7699],{"href":7698},"\u002Fdocs\u002Fpayout-quotes","payout quotes","). How to read one is in ",[133,7702,7704],{"href":7703},"\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained","stablecoin API quotes explained",[11,7706,7707],{},"Then the wallet has to let the stablecoins go. How depends on the wallet:",[144,7709,7710,7716,7725,7731],{},[147,7711,7712,7715],{},[150,7713,7714],{},"Managed wallet:"," nothing to sign. BlindPay moves the funds.",[147,7717,7718,7721,7722,7724],{},[150,7719,7720],{},"External wallet on an EVM chain"," (Ethereum, Base, Polygon, Arbitrum): the wallet signs an ERC-20 ",[485,7723,3772],{}," for the exact quoted amount.",[147,7726,7727,7730],{},[150,7728,7729],{},"External wallet on Stellar:"," a signed XDR transaction.",[147,7732,7733,7736],{},[150,7734,7735],{},"External wallet on Solana:"," a token delegation, prepared, signed, and submitted.",[11,7738,7739],{},"After authorization, BlindPay pulls exactly that amount. Not a cent more.",[11,7741,7742,7745],{},[150,7743,7744],{},"On-chain:"," the approval (on EVM chains) and the transfer out of the wallet. If an external wallet signs the approval, that wallet pays the network fee for it in the chain's native token.",[18,7747,7749],{"id":7748},"step-5-stablecoins-convert-back-and-pay-out-locally","Step 5: Stablecoins convert back and pay out locally",[11,7751,7752,7753,498],{},"The off-ramp converts the stablecoins into local currency and sends them over the recipient's rail. Pix in Brazil, SPEI in Mexico, Transfers in Argentina, and RTP in the US are instant. Wire and SEPA take about one business day, ACH about two, and SWIFT (POBO\u002FCOBO) about five (",[133,7754,7755],{"href":3958},"settlement times by rail",[11,7757,7758,7760,7761,7764],{},[150,7759,7744],{}," done. From here it's banking again, and ",[485,7762,7763],{},"payout.complete"," fires when the recipient's bank confirms.",[11,7766,7767],{},"That's the whole trip. On-chain time is usually minutes. The bank legs are what take hours or days.",[18,7769,7771],{"id":7770},"what-happens-if-a-payment-fails-partway-through","What happens if a payment fails partway through?",[11,7773,7774],{},"Failures cluster at the bank edges, not on-chain. Here's the map:",[23,7776,7777,7790],{},[26,7778,7779],{},[29,7780,7781,7784,7787],{},[32,7782,7783],{},"Where it stops",[32,7785,7786],{},"What happened on-chain",[32,7788,7789],{},"What you see at BlindPay",[42,7791,7792,7803,7813,7824,7837,7850],{},[29,7793,7794,7797,7800],{},[47,7795,7796],{},"Deposit never arrives",[47,7798,7799],{},"Nothing",[47,7801,7802],{},"The payin fails. Pix and SPEI payins wait up to 30 minutes first",[29,7804,7805,7808,7810],{},[47,7806,7807],{},"Quote expires before execution",[47,7809,7799],{},[47,7811,7812],{},"Request a new quote",[29,7814,7815,7818,7821],{},[47,7816,7817],{},"Delivery transaction replaced in a gas spike",[47,7819,7820],{},"The replacement lands",[47,7822,7823],{},"Resolved automatically; the hash may change",[29,7825,7826,7829,7832],{},[47,7827,7828],{},"Held for compliance review",[47,7830,7831],{},"For US payouts, the stablecoins are usually already collected",[47,7833,7834,7836],{},[485,7835,487],{}," until review clears. An unanswered request for information can lead to a refund to the sender",[29,7838,7839,7842,7845],{},[47,7840,7841],{},"Receiving bank rejects or returns the payout",[47,7843,7844],{},"A refund transfer back to the wallet",[47,7846,7847,7849],{},[485,7848,4001],{},": stablecoins return to the wallet that authorized them",[29,7851,7852,7855,7858],{},[47,7853,7854],{},"Payout rejected in compliance review",[47,7856,7857],{},"The stablecoins may already be collected",[47,7859,7860,7862],{},[485,7861,4005],{},", no automatic refund; contact support",[11,7864,7865],{},"A confirmed on-chain transfer can't be reversed by anyone. That's why the destination and amount are locked in the quote before anything moves.",[18,7867,7869],{"id":7868},"what-does-this-mean-for-a-business-that-never-wants-to-touch-a-wallet","What does this mean for a business that never wants to touch a wallet?",[11,7871,7872,7873,7875],{},"It means it doesn't have to. Everything above can run behind a bank-shaped API. In ",[133,7874,952],{"href":951},"'s Abstracted flavor, you issue virtual accounts, receive payins, and send payouts to bank accounts. The stablecoins settle in the linked wallet in the background, and no one on your team picks a chain, holds a key, or signs a transaction.",[11,7877,7878],{},"Teams that want the chain-level controls from steps 3 and 4 use the Advanced flavor of the same API. Same keys, same webhooks.",[18,7880,2829],{"id":2828},[11,7882,7883,7884,7886,7887,7889],{},"Watch one payment cross the chain yourself. Create a free development instance, where payins auto-complete about 30 seconds after you create them and settle in a test token called USDB. Then open the transaction hash from ",[485,7885,7673],{}," in a testnet block explorer. The ",[133,7888,3497],{"href":3496}," walks through it step by step.",[11,7891,7892],{},[1210,7893,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":7895},[7896,7897,7898,7899,7900,7901,7902,7903,7904],{"id":7510,"depth":520,"text":7511},{"id":7523,"depth":520,"text":7524},{"id":7551,"depth":520,"text":7552},{"id":7570,"depth":520,"text":7571},{"id":7691,"depth":520,"text":7692},{"id":7748,"depth":520,"text":7749},{"id":7770,"depth":520,"text":7771},{"id":7868,"depth":520,"text":7869},{"id":2828,"depth":520,"text":2829},"2026-08-13","A stablecoin payment in five steps: bank deposit, conversion to USDC or USDT, on-chain delivery to a wallet, payout authorization, and local currency out.",[7908,7911,7914,7917,7920],{"q":7909,"a":7910},"How do stablecoin payments work?","In four moves. A bank transfer arrives in a virtual account, it is converted into USDC or USDT, the stablecoins settle on-chain to the customer's linked wallet, and for a payout they are converted back to local currency and sent over a local rail like Pix or SPEI. The blockchain only handles the middle: short on-chain transfers that confirm in seconds to minutes and leave a public receipt.",{"q":7912,"a":7913},"What happens if a stablecoin payment fails partway through?","It depends on the step. If the deposit never arrives, the payin fails and nothing moves on-chain. If a payout quote expires before execution, request a new one; no funds moved. If the receiving bank rejects or returns a payout, BlindPay marks it refunded and sends the stablecoins back to the wallet that authorized it. A payout that ends failed, for example after a rejected compliance check, does not refund automatically and needs a follow-up with support.",{"q":7915,"a":7916},"Which stablecoins are supported?","USDC and USDT. At BlindPay, Ethereum, Polygon, and Solana support both. Base, Arbitrum, and Stellar support USDC, and Tron supports USDT only.",{"q":7918,"a":7919},"Do I need to hold cryptocurrency myself?","No. A business can receive bank transfers into virtual accounts and pay out to bank accounts without ever opening a wallet app or choosing a chain. The stablecoins settle in a linked wallet behind the scenes. Teams that do want to hold their own stablecoins can link an external wallet they control.",{"q":7921,"a":7922},"How long does the on-chain part of a stablecoin payment take?","Seconds to a few minutes, depending on the network. Stellar closes a ledger about every five seconds, and Solana finalizes in about 13 seconds. Ethereum takes around 13 minutes to reach full finality. The bank legs at each end almost always take longer than the blockchain does.",{"name":7924,"steps":7925},"How a stablecoin payment moves from a bank deposit to a local payout",[7926,7929,7932,7935,7938],{"name":7927,"text":7928},"A bank transfer lands in a virtual account","The payer sends an ACH, wire, or RTP transfer to a bank account issued in the customer's name. Each deposit creates its own payin record.",{"name":7930,"text":7931},"The deposit converts into USDC or USDT","Once the deposit clears, the provider converts the dollars into a stablecoin at the rate locked in the quote.",{"name":7933,"text":7934},"Stablecoins settle to the linked wallet","One on-chain transfer delivers the stablecoins to the wallet linked to the virtual account. The transaction hash is the public receipt.",{"name":7936,"text":7937},"The wallet authorizes a payout","For a payout, a quote locks the rate and fees, and the wallet authorizes the exact amount. Managed wallets need no signature.",{"name":7939,"text":7940},"Stablecoins convert back and pay out locally","The provider pulls the authorized amount, converts it to local currency, and sends it over a rail like Pix or SPEI.",{"author":555},"---\ntitle: \"What happens on-chain in a stablecoin payment? A step-by-step walkthrough\"\nseoTitle: \"How stablecoin payments work on-chain, step by step\"\ndescription: \"A stablecoin payment in five steps: bank deposit, conversion to USDC or USDT, on-chain delivery to a wallet, payout authorization, and local currency out.\"\ndate: \"2026-08-13\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How a stablecoin payment moves from a bank deposit to a local payout\"\n  steps:\n    - name: \"A bank transfer lands in a virtual account\"\n      text: \"The payer sends an ACH, wire, or RTP transfer to a bank account issued in the customer's name. Each deposit creates its own payin record.\"\n    - name: \"The deposit converts into USDC or USDT\"\n      text: \"Once the deposit clears, the provider converts the dollars into a stablecoin at the rate locked in the quote.\"\n    - name: \"Stablecoins settle to the linked wallet\"\n      text: \"One on-chain transfer delivers the stablecoins to the wallet linked to the virtual account. The transaction hash is the public receipt.\"\n    - name: \"The wallet authorizes a payout\"\n      text: \"For a payout, a quote locks the rate and fees, and the wallet authorizes the exact amount. Managed wallets need no signature.\"\n    - name: \"Stablecoins convert back and pay out locally\"\n      text: \"The provider pulls the authorized amount, converts it to local currency, and sends it over a rail like Pix or SPEI.\"\nfaq:\n  - q: \"How do stablecoin payments work?\"\n    a: \"In four moves. A bank transfer arrives in a virtual account, it is converted into USDC or USDT, the stablecoins settle on-chain to the customer's linked wallet, and for a payout they are converted back to local currency and sent over a local rail like Pix or SPEI. The blockchain only handles the middle: short on-chain transfers that confirm in seconds to minutes and leave a public receipt.\"\n  - q: \"What happens if a stablecoin payment fails partway through?\"\n    a: \"It depends on the step. If the deposit never arrives, the payin fails and nothing moves on-chain. If a payout quote expires before execution, request a new one; no funds moved. If the receiving bank rejects or returns a payout, BlindPay marks it refunded and sends the stablecoins back to the wallet that authorized it. A payout that ends failed, for example after a rejected compliance check, does not refund automatically and needs a follow-up with support.\"\n  - q: \"Which stablecoins are supported?\"\n    a: \"USDC and USDT. At BlindPay, Ethereum, Polygon, and Solana support both. Base, Arbitrum, and Stellar support USDC, and Tron supports USDT only.\"\n  - q: \"Do I need to hold cryptocurrency myself?\"\n    a: \"No. A business can receive bank transfers into virtual accounts and pay out to bank accounts without ever opening a wallet app or choosing a chain. The stablecoins settle in a linked wallet behind the scenes. Teams that do want to hold their own stablecoins can link an external wallet they control.\"\n  - q: \"How long does the on-chain part of a stablecoin payment take?\"\n    a: \"Seconds to a few minutes, depending on the network. Stellar closes a ledger about every five seconds, and Solana finalizes in about 13 seconds. Ethereum takes around 13 minutes to reach full finality. The bank legs at each end almost always take longer than the blockchain does.\"\n---\n\nA stablecoin payment works in four moves. A bank transfer lands in a virtual account, it's converted into USDC or USDT, the stablecoins settle on-chain to the customer's linked wallet, and for a payout they're converted back into local currency and sent over a rail like Pix or SPEI. The blockchain handles only the middle: a couple of short transactions, each confirmed in seconds to minutes, each with a public receipt.\n\nThe end-to-end version, with bank cut-offs and payout timing, is in [how a stablecoin payment works](\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works). This walkthrough zooms in on the part most explainers skip: what the blockchain is actually doing at each step, and what an operations team can see while it happens.\n\nNo code required. If you can read a bank statement, you can follow this.\n\n## What does the whole flow look like?\n\nPicture a line of five boxes, left to right. The first and last are bank accounts. The three in the middle are the payment provider's conversion step, the customer's wallet, and the provider's conversion step again. Money enters on the left as dollars, becomes a stablecoin for the middle stretch, and leaves on the right as local currency. Only two arrows in the whole picture are on-chain: the delivery into the wallet, and the pull out of it.\n\n```\n[Payer's bank]\n     |  1. ACH, wire, or RTP deposit            (bank rail)\n     v\n[Virtual account in the customer's name]\n     |  2. dollars convert to USDC or USDT      (provider)\n     v\n[Customer's linked wallet]  \u003C-- 3. on-chain delivery, tx hash #1\n     |\n     |  4. wallet authorizes the payout amount\n     |     and the stablecoins are pulled        on-chain, tx hash #2\n     v\n[Provider's off-ramp]\n     |  5. stablecoins convert to local currency (provider)\n     v\n[Recipient's bank, paid over Pix or SPEI]       (bank rail)\n```\n\n## Step 1: A bank transfer lands in a virtual account\n\nA virtual account is a real bank account number, routing and account, issued in your customer's name. Anyone can pay it like any other account. At BlindPay, each virtual account belongs to one customer and settles to one linked wallet, and a customer can hold more than one ([virtual accounts](\u002Fdocs\u002Fvirtual-accounts)).\n\nWhy that matters for reconciliation: every deposit into the account creates its own payin record. You match money to customers by account, not by hoping the payer typed a reference code correctly. Without a virtual account, a US payin returns BlindPay's bank details plus a `memo_code` the payer has to include.\n\n**On-chain so far:** nothing. This step is pure banking. ACH and wire deposits can take up to five business days to arrive; RTP arrives in seconds.\n\nThe approval flow and fees are covered in [stablecoin virtual accounts explained](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained).\n\n## Step 2: The deposit converts into USDC or USDT\n\nOnce the deposit clears, the provider converts the dollars into a stablecoin at the rate locked in the quote. USDC is issued by Circle and USDT by Tether; both are designed to be redeemable one-for-one for US dollars through their issuers.\n\nNew tokens come from one of two places. Either the issuer mints them against fresh dollars, or the provider sends tokens it already holds. BlindPay's docs describe exactly that: once the deposit is confirmed, BlindPay mints or transfers the equivalent stablecoin amount to the destination wallet ([overview](\u002Fdocs\u002Foverview)).\n\n**On-chain so far:** possibly a mint on the issuer's side. Your customer doesn't see it and doesn't need to.\n\n## Step 3: Stablecoins settle to the linked wallet\n\nThis is the first on-chain moment your team can actually look at. One transfer moves the stablecoins from the provider to the wallet linked to the virtual account.\n\nA transfer \"confirms\" when a block containing it is added to the chain. It's final when the network guarantees that block can't be undone. How long that takes depends on the network:\n\n| Network | New block roughly every | Practical finality |\n| --- | --- | --- |\n| Stellar | 5 seconds | At ledger close, about 5 seconds |\n| Solana | 0.4 seconds | About 13 seconds |\n| Tron | 3 seconds | About a minute |\n| Polygon | 2 seconds | Seconds |\n| Base, Arbitrum | 2 seconds or less | Seconds for the sequencer, minutes to settle on Ethereum |\n| Ethereum | 12 seconds | About 13 minutes |\n\nEvery confirmed transfer has a **transaction hash**, a unique ID anyone can paste into a block explorer to see the amount, the sending and receiving addresses, and the time. It's a receipt no one can edit.\n\n**What BlindPay shows you:** the payin fires `payin.complete` once the stablecoins land, and the hash appears in the payin's `tracking_complete` object. One gotcha from the [payins docs](\u002Fdocs\u002Fpayins): during a gas spike, a broadcast transaction can be replaced by another one, so the final hash may differ from the first one you saw. Treat the payin `status` as the source of truth, not a specific hash.\n\nThe wallet itself comes in two kinds. An external wallet is controlled by your customer. A managed wallet is custodied by BlindPay (in beta). Why that choice matters for risk is in [non-custodial payments](\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained).\n\n## Step 4: The wallet authorizes the payout\n\nPaying someone starts with a quote: the rate, the fee, and exactly how much local currency arrives. At BlindPay a payout quote lasts five minutes ([payout quotes](\u002Fdocs\u002Fpayout-quotes)). How to read one is in [stablecoin API quotes explained](\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained).\n\nThen the wallet has to let the stablecoins go. How depends on the wallet:\n\n- **Managed wallet:** nothing to sign. BlindPay moves the funds.\n- **External wallet on an EVM chain** (Ethereum, Base, Polygon, Arbitrum): the wallet signs an ERC-20 `approve` for the exact quoted amount.\n- **External wallet on Stellar:** a signed XDR transaction.\n- **External wallet on Solana:** a token delegation, prepared, signed, and submitted.\n\nAfter authorization, BlindPay pulls exactly that amount. Not a cent more.\n\n**On-chain:** the approval (on EVM chains) and the transfer out of the wallet. If an external wallet signs the approval, that wallet pays the network fee for it in the chain's native token.\n\n## Step 5: Stablecoins convert back and pay out locally\n\nThe off-ramp converts the stablecoins into local currency and sends them over the recipient's rail. Pix in Brazil, SPEI in Mexico, Transfers in Argentina, and RTP in the US are instant. Wire and SEPA take about one business day, ACH about two, and SWIFT (POBO\u002FCOBO) about five ([settlement times by rail](\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times)).\n\n**On-chain:** done. From here it's banking again, and `payout.complete` fires when the recipient's bank confirms.\n\nThat's the whole trip. On-chain time is usually minutes. The bank legs are what take hours or days.\n\n## What happens if a payment fails partway through?\n\nFailures cluster at the bank edges, not on-chain. Here's the map:\n\n| Where it stops | What happened on-chain | What you see at BlindPay |\n| --- | --- | --- |\n| Deposit never arrives | Nothing | The payin fails. Pix and SPEI payins wait up to 30 minutes first |\n| Quote expires before execution | Nothing | Request a new quote |\n| Delivery transaction replaced in a gas spike | The replacement lands | Resolved automatically; the hash may change |\n| Held for compliance review | For US payouts, the stablecoins are usually already collected | `on_hold` until review clears. An unanswered request for information can lead to a refund to the sender |\n| Receiving bank rejects or returns the payout | A refund transfer back to the wallet | `refunded`: stablecoins return to the wallet that authorized them |\n| Payout rejected in compliance review | The stablecoins may already be collected | `failed`, no automatic refund; contact support |\n\nA confirmed on-chain transfer can't be reversed by anyone. That's why the destination and amount are locked in the quote before anything moves.\n\n## What does this mean for a business that never wants to touch a wallet?\n\nIt means it doesn't have to. Everything above can run behind a bank-shaped API. In [BlindPay](\u002Fglobal-payments)'s Abstracted flavor, you issue virtual accounts, receive payins, and send payouts to bank accounts. The stablecoins settle in the linked wallet in the background, and no one on your team picks a chain, holds a key, or signs a transaction.\n\nTeams that want the chain-level controls from steps 3 and 4 use the Advanced flavor of the same API. Same keys, same webhooks.\n\n## What to do next\n\nWatch one payment cross the chain yourself. Create a free development instance, where payins auto-complete about 30 seconds after you create them and settle in a test token called USDB. Then open the transaction hash from `tracking_complete` in a testnet block explorer. The [payin quickstart](\u002Fdocs\u002Fquickstart-payin) walks through it step by step.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":7491,"description":7906},"How stablecoin payments work on-chain, step by step","resources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment","5Ji2v8Q-vLFpzu8DvvAPRnYqgaxejE8LSBJlH5UCaEs",{"id":7948,"title":7949,"authors":6,"body":7950,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1787,"description":8032,"extension":536,"faq":8033,"howto":6,"isBlog":553,"isChangelog":553,"meta":8045,"navigation":556,"path":8046,"pillar":553,"products":6,"rawbody":8047,"role":6,"seo":8048,"seoTitle":7949,"stem":8049,"thumbnail":6,"updated":1787,"__hash__":8050},"content\u002Fresources\u002Fmore\u002Fwhat-is-usdc.md","What is USDC? The dollar-pegged stablecoin explained",{"type":8,"value":7951,"toc":8025},[7952,7955,7958,7962,7969,7972,7976,7979,7982,7986,7993,7997,8002,8007,8009,8021],[11,7953,7954],{},"USDC is a stablecoin: a digital dollar issued by Circle, backed 1:1 by cash and short-term US Treasuries, and redeemable for US dollars on demand. It runs on multiple blockchains, moves value in minutes instead of days, and settles into ordinary bank accounts once it passes through a payment provider.",[11,7956,7957],{},"USDC exists to solve one problem: dollars are the world's reserve currency, but moving them across borders through banks is slow and expensive. USDC gives businesses a dollar-denominated asset that transfers over the internet at any hour, then converts back to local currency through providers that plug into bank rails.",[18,7959,7961],{"id":7960},"what-backs-usdc","What backs USDC?",[11,7963,7964,7965,329],{},"Circle states plainly on its transparency page that \"USDC is a digital dollar backed 100% by highly liquid cash and cash-equivalent assets and is always redeemable 1:1 for US dollars.\" The bulk of reserves sit in the Circle Reserve Fund, an SEC-registered money market fund holding cash, short-dated US Treasuries, and overnight Treasury repurchase agreements. The remainder sits as cash at large banks. A Big Four accounting firm, currently Deloitte & Touche, provides a monthly third-party attestation confirming reserve value exceeds circulating supply. Full detail is on ",[133,7966,7968],{"href":6780,"rel":7967},[137],"Circle's transparency page",[11,7970,7971],{},"That structure matters more than it sounds. A stablecoin backed by risky or illiquid assets can fail to redeem at par under stress. One backed by cash and short-dated government debt can, in principle, always pay out. Reserve composition is the first thing to check with any stablecoin, not an afterthought.",[18,7973,7975],{"id":7974},"how-does-usdc-keep-its-dollar-peg","How does USDC keep its dollar peg?",[11,7977,7978],{},"The peg holds through redemption, not through a trading mechanism. Authorized institutions can mint new USDC by sending Circle dollars, and redeem USDC for dollars at any time. That direct convertibility is what keeps the market price near one dollar: if USDC ever traded meaningfully below a dollar, arbitrageurs would buy it cheap and redeem at par, closing the gap.",[11,7980,7981],{},"The peg is not unbreakable. In March 2023, Circle disclosed that part of USDC's reserves, about 3.3 billion dollars, sat at Silicon Valley Bank when regulators closed it. USDC traded as low as 87 cents on some exchanges over a weekend before US regulators guaranteed depositors and the peg recovered within days. The episode is a real data point on reserve risk, not just a marketing footnote, and it is why reserve transparency and redemption speed are the two variables worth watching for any issuer.",[18,7983,7985],{"id":7984},"where-does-usdc-run-and-how-do-you-move-it","Where does USDC run, and how do you move it?",[11,7987,7988,7989,7992],{},"USDC exists natively on more than a dozen blockchains, including Ethereum, Solana, Base, and Polygon, plus others. Each network has different transaction costs and speeds; sending USDC on the wrong network to an address that expects another network is a common way to lose funds, which is one reason most businesses never touch a wallet directly and instead move USDC through a provider. Our guide to ",[133,7990,7991],{"href":1283},"what a stablecoin API does"," covers how that abstraction works.",[18,7994,7996],{"id":7995},"what-is-usdc-used-for-in-payments","What is USDC used for in payments?",[11,7998,7999,8000,329],{},"For businesses, USDC is mostly plumbing, not a product. It shows up in three patterns: cross-border payouts, where a company converts fiat to USDC, sends it in minutes, and a local provider converts it back to reais, pesos, or another currency over rails like Pix or SPEI; dollar collection, where a company outside the US receives US bank transfers that settle as USDC automatically; and treasury movement, shifting working capital between entities same-day instead of pre-funding accounts in every country. The mechanics of that first pattern are covered in our ",[133,8001,5797],{"href":516},[11,8003,8004,8005,329],{},"USDC also competes with USDT (Tether) for payment volume; USDC tends to be preferred by US-regulated businesses for its reserve transparency, while USDT has broader liquidity in some markets. Regulation is converging on requiring exactly the disclosures Circle already publishes: the EU's MiCA and the US GENIUS Act both mandate reserve backing and redemption rights for payment stablecoins, tracked in our ",[133,8006,2802],{"href":1663},[18,8008,5815],{"id":5814},[11,8010,8011,8013,8014,8016,8017,329],{},[133,8012,952],{"href":951}," moves USDC (and USDT) between fiat currencies and local bank rails: Pix in Brazil, SPEI in Mexico, ACH and wire in the US, and more across 100+ countries. A business never has to hold a wallet or manage a blockchain node; BlindPay handles conversion, compliance, and delivery behind one API call. Live rates are public, for example ",[133,8015,1073],{"href":1072},", and the full picture of what the API covers is in our ",[133,8018,8020],{"href":8019},"\u002Fresources\u002Fmore","more resources hub",[11,8022,8023],{},[1210,8024,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":8026},[8027,8028,8029,8030,8031],{"id":7960,"depth":520,"text":7961},{"id":7974,"depth":520,"text":7975},{"id":7984,"depth":520,"text":7985},{"id":7995,"depth":520,"text":7996},{"id":5814,"depth":520,"text":5815},"USDC is a dollar-pegged stablecoin issued by Circle, backed 1:1 by cash and short-term Treasuries and redeemable for US dollars. How it works and where it's used.",[8034,8037,8040,8043],{"q":8035,"a":8036},"What is USDC backed by?","Cash and cash-equivalent assets, mostly short-dated US Treasuries held through a registered money market fund, plus cash at major banks. Circle states USDC is backed 100 percent by these assets and redeemable 1:1 for US dollars.",{"q":8038,"a":8039},"Who issues USDC?","Circle, a US financial technology company. Circle mints USDC when someone deposits dollars and burns it when someone redeems for dollars, and publishes monthly third-party attestations of the reserves.",{"q":8041,"a":8042},"Is USDC the same as a US dollar?","No. USDC is a digital token that represents a claim on a dollar held in reserve. It moves like a dollar in value and is redeemable for one, but it lives on a blockchain and settles differently than a bank transfer.",{"q":542,"a":8044},"It can move slightly off one dollar for short periods, most visibly during the March 2023 banking crisis when part of Circle's reserves were briefly stuck at a failed bank. The peg recovered once redemptions resumed. Reserve quality and redemption access are what keep the peg tight.",{"author":555},"\u002Fresources\u002Fmore\u002Fwhat-is-usdc","---\ntitle: \"What is USDC? The dollar-pegged stablecoin explained\"\nseoTitle: \"What is USDC? The dollar-pegged stablecoin explained\"\ndescription: \"USDC is a dollar-pegged stablecoin issued by Circle, backed 1:1 by cash and short-term Treasuries and redeemable for US dollars. How it works and where it's used.\"\ndate: \"2026-09-01\"\nauthor: \"BlindPay Team\"\nupdated: \"2026-09-01\"\ncategory: \"stablecoins\"\nfaq:\n  - q: \"What is USDC backed by?\"\n    a: \"Cash and cash-equivalent assets, mostly short-dated US Treasuries held through a registered money market fund, plus cash at major banks. Circle states USDC is backed 100 percent by these assets and redeemable 1:1 for US dollars.\"\n  - q: \"Who issues USDC?\"\n    a: \"Circle, a US financial technology company. Circle mints USDC when someone deposits dollars and burns it when someone redeems for dollars, and publishes monthly third-party attestations of the reserves.\"\n  - q: \"Is USDC the same as a US dollar?\"\n    a: \"No. USDC is a digital token that represents a claim on a dollar held in reserve. It moves like a dollar in value and is redeemable for one, but it lives on a blockchain and settles differently than a bank transfer.\"\n  - q: \"Can USDC lose its peg?\"\n    a: \"It can move slightly off one dollar for short periods, most visibly during the March 2023 banking crisis when part of Circle's reserves were briefly stuck at a failed bank. The peg recovered once redemptions resumed. Reserve quality and redemption access are what keep the peg tight.\"\n---\n\nUSDC is a stablecoin: a digital dollar issued by Circle, backed 1:1 by cash and short-term US Treasuries, and redeemable for US dollars on demand. It runs on multiple blockchains, moves value in minutes instead of days, and settles into ordinary bank accounts once it passes through a payment provider.\n\nUSDC exists to solve one problem: dollars are the world's reserve currency, but moving them across borders through banks is slow and expensive. USDC gives businesses a dollar-denominated asset that transfers over the internet at any hour, then converts back to local currency through providers that plug into bank rails.\n\n## What backs USDC?\n\nCircle states plainly on its transparency page that \"USDC is a digital dollar backed 100% by highly liquid cash and cash-equivalent assets and is always redeemable 1:1 for US dollars.\" The bulk of reserves sit in the Circle Reserve Fund, an SEC-registered money market fund holding cash, short-dated US Treasuries, and overnight Treasury repurchase agreements. The remainder sits as cash at large banks. A Big Four accounting firm, currently Deloitte & Touche, provides a monthly third-party attestation confirming reserve value exceeds circulating supply. Full detail is on [Circle's transparency page](https:\u002F\u002Fwww.circle.com\u002Ftransparency).\n\nThat structure matters more than it sounds. A stablecoin backed by risky or illiquid assets can fail to redeem at par under stress. One backed by cash and short-dated government debt can, in principle, always pay out. Reserve composition is the first thing to check with any stablecoin, not an afterthought.\n\n## How does USDC keep its dollar peg?\n\nThe peg holds through redemption, not through a trading mechanism. Authorized institutions can mint new USDC by sending Circle dollars, and redeem USDC for dollars at any time. That direct convertibility is what keeps the market price near one dollar: if USDC ever traded meaningfully below a dollar, arbitrageurs would buy it cheap and redeem at par, closing the gap.\n\nThe peg is not unbreakable. In March 2023, Circle disclosed that part of USDC's reserves, about 3.3 billion dollars, sat at Silicon Valley Bank when regulators closed it. USDC traded as low as 87 cents on some exchanges over a weekend before US regulators guaranteed depositors and the peg recovered within days. The episode is a real data point on reserve risk, not just a marketing footnote, and it is why reserve transparency and redemption speed are the two variables worth watching for any issuer.\n\n## Where does USDC run, and how do you move it?\n\nUSDC exists natively on more than a dozen blockchains, including Ethereum, Solana, Base, and Polygon, plus others. Each network has different transaction costs and speeds; sending USDC on the wrong network to an address that expects another network is a common way to lose funds, which is one reason most businesses never touch a wallet directly and instead move USDC through a provider. Our guide to [what a stablecoin API does](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) covers how that abstraction works.\n\n## What is USDC used for in payments?\n\nFor businesses, USDC is mostly plumbing, not a product. It shows up in three patterns: cross-border payouts, where a company converts fiat to USDC, sends it in minutes, and a local provider converts it back to reais, pesos, or another currency over rails like Pix or SPEI; dollar collection, where a company outside the US receives US bank transfers that settle as USDC automatically; and treasury movement, shifting working capital between entities same-day instead of pre-funding accounts in every country. The mechanics of that first pattern are covered in our [stablecoin payments guide](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide).\n\nUSDC also competes with USDT (Tether) for payment volume; USDC tends to be preferred by US-regulated businesses for its reserve transparency, while USDT has broader liquidity in some markets. Regulation is converging on requiring exactly the disclosures Circle already publishes: the EU's MiCA and the US GENIUS Act both mandate reserve backing and redemption rights for payment stablecoins, tracked in our [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026).\n\n## How does BlindPay fit in?\n\n[BlindPay](\u002Fglobal-payments) moves USDC (and USDT) between fiat currencies and local bank rails: Pix in Brazil, SPEI in Mexico, ACH and wire in the US, and more across 100+ countries. A business never has to hold a wallet or manage a blockchain node; BlindPay handles conversion, compliance, and delivery behind one API call. Live rates are public, for example [USDC to BRL](\u002Fusdc-to-brl), and the full picture of what the API covers is in our [more resources hub](\u002Fresources\u002Fmore).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":7949,"description":8032},"resources\u002Fmore\u002Fwhat-is-usdc","xKNEh3YfQVruQCqOw6JAOoYxYb2Q-fGqejJrGCTE9x0",{"id":8052,"title":8053,"authors":6,"body":8054,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1768,"description":8315,"extension":536,"faq":8316,"howto":6,"isBlog":553,"isChangelog":553,"meta":8327,"navigation":556,"path":1283,"pillar":553,"products":6,"rawbody":8328,"role":6,"seo":8329,"seoTitle":8053,"stem":8330,"thumbnail":6,"updated":1787,"__hash__":8331},"content\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api.md","What is a stablecoin API? Infrastructure explained",{"type":8,"value":8055,"toc":8305},[8056,8059,8066,8070,8073,8101,8107,8111,8114,8117,8150,8154,8157,8174,8179,8182,8186,8192,8195,8198,8202,8246,8250,8253,8273,8276,8280,8283,8286,8288,8301],[11,8057,8058],{},"A stablecoin API is a software interface that lets businesses move money using stablecoins without building crypto infrastructure themselves. One integration exposes the whole flow as code: accept fiat, convert to digital dollars, move value across borders in minutes, and pay out in local currency over rails like Pix, SPEI, ACH, and wire.",[11,8060,8061,8062,8065],{},"The category exists because the underlying demand is large and the plumbing is hard. Stablecoins settle trillions of dollars in transfer volume per year, with circulating supply above 200 billion dollars according to public trackers like ",[133,8063,6721],{"href":1742,"rel":8064},[137],". Almost none of the businesses driving that volume want to manage wallets, blockchain nodes, exchange accounts, and money transmission licenses. The API layer packages all of it.",[18,8067,8069],{"id":8068},"what-does-a-stablecoin-api-abstract-away","What does a stablecoin API abstract away?",[11,8071,8072],{},"Behind a single \"create payout\" call, a stablecoin API is doing four jobs:",[144,8074,8075,8081,8089,8095],{},[147,8076,8077,8080],{},[150,8078,8079],{},"Wallets and custody."," Creating and securing blockchain wallets, managing keys, and choosing networks. Sending USDC on the wrong chain to the wrong address loses money; the API layer removes that entire class of error.",[147,8082,8083,8085,8086,8088],{},[150,8084,5333],{}," Quoting and executing fiat-to-stablecoin and stablecoin-to-fiat conversions at a known rate. Providers publish or expose the FX rate and fee, for example a live ",[133,8087,1073],{"href":1072}," quote.",[147,8090,8091,8094],{},[150,8092,8093],{},"Local rails."," Delivering and collecting money over each country's banking system: Pix in Brazil, SPEI in Mexico, ACH and wire in the US. Each rail has its own formats, hours, and failure modes.",[147,8096,8097,8100],{},[150,8098,8099],{},"Compliance."," KYC and KYB on receivers, sanctions screening, transaction monitoring, and travel rule data exchange. This is a legal requirement in essentially every market and the hardest part to build alone.",[11,8102,8103,8104,8106],{},"If a provider offers only some of these, you are still building the rest. The evaluation checklist in our ",[133,8105,5940],{"href":916}," covers who does what.",[18,8108,8110],{"id":8109},"why-are-businesses-adopting-stablecoin-apis","Why are businesses adopting stablecoin APIs?",[11,8112,8113],{},"The pattern behind most adoption is the same: money needs to cross a border, and the traditional route is slow and expensive. An international wire takes 3 to 5 business days and passes through correspondent banks that each take a cut. A stablecoin transfer settles in minutes at any hour, and local delivery on a fast rail like Pix takes seconds.",[11,8115,8116],{},"Concrete use cases:",[144,8118,8119,8129,8138,8144],{},[147,8120,8121,8124,8125,8128],{},[150,8122,8123],{},"Global payouts."," Marketplaces and platforms paying contractors, sellers, or partners across Latin America and beyond. See our guide to ",[133,8126,8127],{"href":516},"stablecoin payments"," for the full flow.",[147,8130,8131,8134,8135,8137],{},[150,8132,8133],{},"Dollar collection."," A company outside the US invoices with US banking details through ",[133,8136,1570],{"href":1067},"; incoming ACH or wire transfers settle as USDC automatically.",[147,8139,8140,8143],{},[150,8141,8142],{},"Treasury movement."," Moving working capital between countries same-day instead of pre-funding local accounts.",[147,8145,8146,8149],{},[150,8147,8148],{},"Embedded finance."," Fintechs offering dollar balances or cross-border transfers inside their own product, with the stablecoin provider as the engine.",[18,8151,8153],{"id":8152},"what-does-a-typical-payment-flow-look-like","What does a typical payment flow look like?",[11,8155,8156],{},"A payout from a US business to a contractor in Brazil, through a stablecoin API:",[289,8158,8159,8162,8165,8168,8171],{},[147,8160,8161],{},"The business calls the API with the receiver, amount, and currency.",[147,8163,8164],{},"The provider runs compliance checks on the receiver (KYC status, sanctions screening).",[147,8166,8167],{},"The business funds the payout in USDC, or fiat that the provider converts.",[147,8169,8170],{},"The provider converts USDC to reais at the quoted rate and sends a Pix transfer.",[147,8172,8173],{},"The contractor's bank account is credited in seconds. Webhooks report each state change.",[11,8175,8176,8177,329],{},"The contractor never sees a wallet or a token. That invisibility is the point: stablecoins are the settlement layer, not the user experience. If the concepts here are new, start with ",[133,8178,1280],{"href":1279},[11,8180,8181],{},"The unhappy paths matter as much as the happy one. A production-grade API surfaces every failure as a typed state you can handle in code: a receiver who fails sanctions screening before funds move, a Pix key whose registered name does not match the payout name, a transfer held for a compliance information request. Each of these is routine in real payment operations, and the difference between providers shows in whether the API tells you what happened and what to do next, or leaves you emailing support.",[18,8183,8185],{"id":8184},"should-you-build-or-buy-stablecoin-infrastructure","Should you build or buy stablecoin infrastructure?",[11,8187,8188,8189,498],{},"Building in-house means: wallet security and key management, integrations with exchanges or OTC desks for conversion, banking partners in every payout country, licensing or agent relationships for money transmission, and a compliance program (KYC, AML, travel rule) that regulators will examine. Teams that have done it typically describe 12+ months and a dedicated crew before the first dollar moves, and the compliance surface never stops growing as rules like MiCA and the GENIUS Act come into force (tracked in our ",[133,8190,8191],{"href":1663},"stablecoin regulation guide",[11,8193,8194],{},"Buying means one API integration, typically live in days against a sandbox, with the provider carrying the licenses, banking relationships, and compliance program. The tradeoffs are provider fees and dependency on the provider's coverage map, which is why coverage and pricing transparency belong at the top of the evaluation.",[11,8196,8197],{},"For most companies whose product is not payments infrastructure itself, buying wins. The exceptions are companies at very large scale or with unusual corridor needs.",[18,8199,8201],{"id":8200},"what-should-you-evaluate-in-a-stablecoin-api","What should you evaluate in a stablecoin API?",[144,8203,8204,8210,8216,8221,8231,8236],{},[147,8205,8206,8209],{},[150,8207,8208],{},"Coverage."," Which countries, currencies, and rails. A provider strong in Europe may not deliver over Pix or SPEI at all.",[147,8211,8212,8215],{},[150,8213,8214],{},"Compliance scope."," Who runs KYC and sanctions screening, and who holds the regulatory relationships. If the answer is \"you do\", the integration is much bigger than the API docs suggest.",[147,8217,8218,8220],{},[150,8219,4572],{}," Whether funds sit in provider-managed wallets, your own wallets, or regulated third-party custody, and what happens to funds in flight if the provider fails.",[147,8222,8223,8226,8227,8230],{},[150,8224,8225],{},"Pricing."," Flat fee, percentage, and the FX spread, which matters most. Compare the total amount received, not the quoted fee: a low fee can hide a poor rate. Published pricing, like ",[133,8228,8229],{"href":967},"BlindPay's",", makes this comparable.",[147,8232,8233,8235],{},[150,8234,4477],{}," Sandbox quality, API reference, webhooks, idempotency, and error semantics. You find out about the bad ones in production.",[147,8237,8238,8241,8242,8245],{},[150,8239,8240],{},"Stablecoin support."," At minimum USDC and USDT, since ",[133,8243,8244],{"href":176},"each dominates in different regions",", plus the chains your counterparties actually use.",[18,8247,8249],{"id":8248},"what-does-a-stablecoin-api-cost","What does a stablecoin API cost?",[11,8251,8252],{},"Pricing has three components, and comparing providers means comparing all three:",[144,8254,8255,8261,8267],{},[147,8256,8257,8260],{},[150,8258,8259],{},"Transaction fees."," A flat fee, a percentage, or both, per payout or collection. Flat fees favor large transfers; percentages favor small ones.",[147,8262,8263,8266],{},[150,8264,8265],{},"FX spread."," The gap between the mid-market rate and the rate you receive on conversion. This is where opaque providers make their real margin, and why the comparison metric should always be the total amount received, not the advertised fee.",[147,8268,8269,8272],{},[150,8270,8271],{},"Fixed costs."," Monthly minimums, account fees, or committed volume tiers, common at the enterprise end of the market.",[11,8274,8275],{},"Two practical tests: does the provider publish pricing without a sales call, and does the API return the exact rate and fee in the quote before you commit funds? Providers confident in their pricing do both.",[18,8277,8279],{"id":8278},"how-long-does-integration-take","How long does integration take?",[11,8281,8282],{},"For an API-first provider, the typical path is: sandbox account on day one, first test payout the same week, production keys after business verification (KYB), and live corridor traffic in 2 to 4 weeks total. The long pole is usually your own compliance onboarding as a customer, not the code.",[11,8284,8285],{},"Signals that the estimate will hold: a public sandbox with realistic test data, webhooks for every state transition (created, processing, completed, failed), idempotency keys on money-moving endpoints, and API references with real request and response examples. Signals that it will not: PDF documentation and an integration that starts with a scheduled call.",[18,8287,5815],{"id":5814},[11,8289,8290,8292,8293,8296,8297,8300],{},[133,8291,952],{"href":951}," is a stablecoin API for global payments. It covers the four jobs above in one integration: managed wallets, published FX quotes, payouts over Pix, SPEI, ACH, and wire in 100+ countries, collections through ",[133,8294,8295],{"href":1067},"virtual US accounts"," that settle as stablecoins, and KYC, sanctions screening, and travel rule compliance built into every flow. Pricing is flat and public, and a full sandbox is available before any commitment: ",[133,8298,8299],{"href":1189},"talk to the team"," or explore the docs to see the API shape.",[11,8302,8303],{},[1210,8304,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":8306},[8307,8308,8309,8310,8311,8312,8313,8314],{"id":8068,"depth":520,"text":8069},{"id":8109,"depth":520,"text":8110},{"id":8152,"depth":520,"text":8153},{"id":8184,"depth":520,"text":8185},{"id":8200,"depth":520,"text":8201},{"id":8248,"depth":520,"text":8249},{"id":8278,"depth":520,"text":8279},{"id":5814,"depth":520,"text":5815},"A stablecoin API lets businesses move money with stablecoins through code: wallets, conversion, local payout rails, and compliance behind one integration.",[8317,8319,8321,8324],{"q":6041,"a":8318},"It exposes stablecoin money movement as software: create a payout or collection with an API call, and the provider handles wallets, currency conversion, blockchain transfers, local bank rails, and compliance checks behind the scenes.",{"q":6693,"a":8320},"No. Most businesses send or receive regular fiat on their side. The provider converts between fiat and stablecoins in the middle, so the stablecoin leg is invisible to customers and counterparties.",{"q":8322,"a":8323},"How is a stablecoin API different from a payment gateway like Stripe?","A card gateway processes card payments inside the banking system. A stablecoin API uses stablecoins as the settlement layer between currencies and countries, which makes cross-border transfers faster and cheaper, then delivers funds over local bank rails.",{"q":8325,"a":8326},"What should I evaluate in a stablecoin API provider?","Coverage (countries, rails, currencies), compliance scope (KYC, sanctions screening, travel rule), custody model, pricing transparency including FX spread, and developer experience: sandbox, docs, and webhooks.",{"author":555},"---\ntitle: \"What is a stablecoin API? Infrastructure explained\"\nseoTitle: \"What is a stablecoin API? Infrastructure explained\"\ndescription: \"A stablecoin API lets businesses move money with stablecoins through code: wallets, conversion, local payout rails, and compliance behind one integration.\"\ndate: \"2026-08-15\"\nupdated: \"2026-09-01\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What does a stablecoin API do?\"\n    a: \"It exposes stablecoin money movement as software: create a payout or collection with an API call, and the provider handles wallets, currency conversion, blockchain transfers, local bank rails, and compliance checks behind the scenes.\"\n  - q: \"Do I need to hold crypto to use a stablecoin API?\"\n    a: \"No. Most businesses send or receive regular fiat on their side. The provider converts between fiat and stablecoins in the middle, so the stablecoin leg is invisible to customers and counterparties.\"\n  - q: \"How is a stablecoin API different from a payment gateway like Stripe?\"\n    a: \"A card gateway processes card payments inside the banking system. A stablecoin API uses stablecoins as the settlement layer between currencies and countries, which makes cross-border transfers faster and cheaper, then delivers funds over local bank rails.\"\n  - q: \"What should I evaluate in a stablecoin API provider?\"\n    a: \"Coverage (countries, rails, currencies), compliance scope (KYC, sanctions screening, travel rule), custody model, pricing transparency including FX spread, and developer experience: sandbox, docs, and webhooks.\"\n---\n\nA stablecoin API is a software interface that lets businesses move money using stablecoins without building crypto infrastructure themselves. One integration exposes the whole flow as code: accept fiat, convert to digital dollars, move value across borders in minutes, and pay out in local currency over rails like Pix, SPEI, ACH, and wire.\n\nThe category exists because the underlying demand is large and the plumbing is hard. Stablecoins settle trillions of dollars in transfer volume per year, with circulating supply above 200 billion dollars according to public trackers like [DefiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins). Almost none of the businesses driving that volume want to manage wallets, blockchain nodes, exchange accounts, and money transmission licenses. The API layer packages all of it.\n\n## What does a stablecoin API abstract away?\n\nBehind a single \"create payout\" call, a stablecoin API is doing four jobs:\n\n- **Wallets and custody.** Creating and securing blockchain wallets, managing keys, and choosing networks. Sending USDC on the wrong chain to the wrong address loses money; the API layer removes that entire class of error.\n- **Conversion.** Quoting and executing fiat-to-stablecoin and stablecoin-to-fiat conversions at a known rate. Providers publish or expose the FX rate and fee, for example a live [USDC to BRL](\u002Fusdc-to-brl) quote.\n- **Local rails.** Delivering and collecting money over each country's banking system: Pix in Brazil, SPEI in Mexico, ACH and wire in the US. Each rail has its own formats, hours, and failure modes.\n- **Compliance.** KYC and KYB on receivers, sanctions screening, transaction monitoring, and travel rule data exchange. This is a legal requirement in essentially every market and the hardest part to build alone.\n\nIf a provider offers only some of these, you are still building the rest. The evaluation checklist in our [best stablecoin APIs comparison](\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026) covers who does what.\n\n## Why are businesses adopting stablecoin APIs?\n\nThe pattern behind most adoption is the same: money needs to cross a border, and the traditional route is slow and expensive. An international wire takes 3 to 5 business days and passes through correspondent banks that each take a cut. A stablecoin transfer settles in minutes at any hour, and local delivery on a fast rail like Pix takes seconds.\n\nConcrete use cases:\n\n- **Global payouts.** Marketplaces and platforms paying contractors, sellers, or partners across Latin America and beyond. See our guide to [stablecoin payments](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide) for the full flow.\n- **Dollar collection.** A company outside the US invoices with US banking details through [virtual accounts](\u002Fvirtual-accounts); incoming ACH or wire transfers settle as USDC automatically.\n- **Treasury movement.** Moving working capital between countries same-day instead of pre-funding local accounts.\n- **Embedded finance.** Fintechs offering dollar balances or cross-border transfers inside their own product, with the stablecoin provider as the engine.\n\n## What does a typical payment flow look like?\n\nA payout from a US business to a contractor in Brazil, through a stablecoin API:\n\n1. The business calls the API with the receiver, amount, and currency.\n2. The provider runs compliance checks on the receiver (KYC status, sanctions screening).\n3. The business funds the payout in USDC, or fiat that the provider converts.\n4. The provider converts USDC to reais at the quoted rate and sends a Pix transfer.\n5. The contractor's bank account is credited in seconds. Webhooks report each state change.\n\nThe contractor never sees a wallet or a token. That invisibility is the point: stablecoins are the settlement layer, not the user experience. If the concepts here are new, start with [what is a stablecoin](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin).\n\nThe unhappy paths matter as much as the happy one. A production-grade API surfaces every failure as a typed state you can handle in code: a receiver who fails sanctions screening before funds move, a Pix key whose registered name does not match the payout name, a transfer held for a compliance information request. Each of these is routine in real payment operations, and the difference between providers shows in whether the API tells you what happened and what to do next, or leaves you emailing support.\n\n## Should you build or buy stablecoin infrastructure?\n\nBuilding in-house means: wallet security and key management, integrations with exchanges or OTC desks for conversion, banking partners in every payout country, licensing or agent relationships for money transmission, and a compliance program (KYC, AML, travel rule) that regulators will examine. Teams that have done it typically describe 12+ months and a dedicated crew before the first dollar moves, and the compliance surface never stops growing as rules like MiCA and the GENIUS Act come into force (tracked in our [stablecoin regulation guide](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026)).\n\nBuying means one API integration, typically live in days against a sandbox, with the provider carrying the licenses, banking relationships, and compliance program. The tradeoffs are provider fees and dependency on the provider's coverage map, which is why coverage and pricing transparency belong at the top of the evaluation.\n\nFor most companies whose product is not payments infrastructure itself, buying wins. The exceptions are companies at very large scale or with unusual corridor needs.\n\n## What should you evaluate in a stablecoin API?\n\n- **Coverage.** Which countries, currencies, and rails. A provider strong in Europe may not deliver over Pix or SPEI at all.\n- **Compliance scope.** Who runs KYC and sanctions screening, and who holds the regulatory relationships. If the answer is \"you do\", the integration is much bigger than the API docs suggest.\n- **Custody model.** Whether funds sit in provider-managed wallets, your own wallets, or regulated third-party custody, and what happens to funds in flight if the provider fails.\n- **Pricing.** Flat fee, percentage, and the FX spread, which matters most. Compare the total amount received, not the quoted fee: a low fee can hide a poor rate. Published pricing, like [BlindPay's](\u002Fpricing), makes this comparable.\n- **Developer experience.** Sandbox quality, API reference, webhooks, idempotency, and error semantics. You find out about the bad ones in production.\n- **Stablecoin support.** At minimum USDC and USDT, since [each dominates in different regions](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments), plus the chains your counterparties actually use.\n\n## What does a stablecoin API cost?\n\nPricing has three components, and comparing providers means comparing all three:\n\n- **Transaction fees.** A flat fee, a percentage, or both, per payout or collection. Flat fees favor large transfers; percentages favor small ones.\n- **FX spread.** The gap between the mid-market rate and the rate you receive on conversion. This is where opaque providers make their real margin, and why the comparison metric should always be the total amount received, not the advertised fee.\n- **Fixed costs.** Monthly minimums, account fees, or committed volume tiers, common at the enterprise end of the market.\n\nTwo practical tests: does the provider publish pricing without a sales call, and does the API return the exact rate and fee in the quote before you commit funds? Providers confident in their pricing do both.\n\n## How long does integration take?\n\nFor an API-first provider, the typical path is: sandbox account on day one, first test payout the same week, production keys after business verification (KYB), and live corridor traffic in 2 to 4 weeks total. The long pole is usually your own compliance onboarding as a customer, not the code.\n\nSignals that the estimate will hold: a public sandbox with realistic test data, webhooks for every state transition (created, processing, completed, failed), idempotency keys on money-moving endpoints, and API references with real request and response examples. Signals that it will not: PDF documentation and an integration that starts with a scheduled call.\n\n## How does BlindPay fit in?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API for global payments. It covers the four jobs above in one integration: managed wallets, published FX quotes, payouts over Pix, SPEI, ACH, and wire in 100+ countries, collections through [virtual US accounts](\u002Fvirtual-accounts) that settle as stablecoins, and KYC, sanctions screening, and travel rule compliance built into every flow. Pricing is flat and public, and a full sandbox is available before any commitment: [talk to the team](\u002Fcontact) or explore the docs to see the API shape.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":8053,"description":8315},"resources\u002Fmore\u002Fwhat-is-a-stablecoin-api","gdPPS5soNq5VQXxpuJ0CJA85CjY7AwPTZVWLEUADNPE",{"id":8333,"title":8334,"authors":6,"body":8335,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":1768,"description":8647,"extension":536,"faq":8648,"howto":6,"isBlog":553,"isChangelog":553,"meta":8661,"navigation":556,"path":1279,"pillar":553,"products":6,"rawbody":8662,"role":6,"seo":8663,"seoTitle":8334,"stem":8664,"thumbnail":6,"updated":6,"__hash__":8665},"content\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin.md","What is a stablecoin? Definition, types, and how they work",{"type":8,"value":8336,"toc":8634},[8337,8340,8347,8351,8354,8368,8372,8375,8395,8402,8406,8411,8414,8419,8423,8426,8464,8467,8471,8474,8477,8481,8510,8514,8517,8528,8537,8541,8544,8563,8566,8570,8573,8602,8606,8612,8615,8617,8630],[11,8338,8339],{},"A stablecoin is a digital token designed to hold a constant value, almost always one US dollar. Unlike Bitcoin or Ether, whose prices float freely, a stablecoin is built to be boring: a dollar today, a dollar tomorrow, a dollar next year.",[11,8341,8342,8343,8346],{},"That stability is what makes stablecoins useful for payments. Circulating stablecoin supply has grown past 200 billion dollars, according to public trackers such as ",[133,8344,6721],{"href":1742,"rel":8345},[137],", and stablecoins now settle trillions of dollars in transfer volume per year. Most of that activity is not speculation. It is money movement: businesses paying suppliers, workers receiving salaries, and companies holding digital dollars in markets where local currency loses value.",[18,8348,8350],{"id":8349},"how-does-a-stablecoin-keep-its-value","How does a stablecoin keep its value?",[11,8352,8353],{},"The dominant model is simple: for every token in circulation, the issuer holds one dollar of reserves, typically cash and short-term US Treasuries. When a customer deposits dollars, the issuer mints new tokens. When a customer redeems tokens, the issuer burns them and returns dollars. As long as reserves match supply and redemption works, arbitrage keeps the market price pinned to one dollar.",[11,8355,8356,8357,8360,8361,8365,8366,329],{},"Trust depends on proof. Serious issuers publish regular reserve reports. ",[133,8358,977],{"href":6780,"rel":8359},[137],", the issuer of USDC, publishes monthly attestations from an independent accounting firm. ",[133,8362,8364],{"href":6789,"rel":8363},[137],"Tether",", the issuer of USDT, publishes quarterly attestations. Regulation increasingly turns this from good practice into law: reserve, redemption, and disclosure requirements are now written into frameworks like the EU's MiCA and the US GENIUS Act, which we cover in our ",[133,8367,1664],{"href":1663},[18,8369,8371],{"id":8370},"what-types-of-stablecoins-exist","What types of stablecoins exist?",[11,8373,8374],{},"Three structures cover almost everything in circulation:",[144,8376,8377,8383,8389],{},[147,8378,8379,8382],{},[150,8380,8381],{},"Fiat-backed stablecoins."," Reserves are held in cash and cash equivalents at banks and custodians. USDC and USDT both work this way, and together they account for the large majority of stablecoin supply. This is the model regulators have chosen to formalize, and the only model widely used for business payments.",[147,8384,8385,8388],{},[150,8386,8387],{},"Crypto-collateralized stablecoins."," The token is backed by other crypto assets locked in smart contracts, with more collateral than issued value to absorb price swings. DAI is the best-known example. These are transparent by design but more complex, and their supply is small compared to fiat-backed coins.",[147,8390,8391,8394],{},[150,8392,8393],{},"Algorithmic stablecoins."," These tried to hold a peg through supply algorithms rather than full reserves. The model failed badly: TerraUSD collapsed in May 2022 and erased tens of billions of dollars of value. Modern regulation, including MiCA, effectively excludes unbacked algorithmic designs from operating as payment stablecoins.",[11,8396,8397,8398,8401],{},"There is also a growing category of ",[150,8399,8400],{},"yield-bearing dollar tokens"," that pass reserve interest to holders. Regulators generally treat these differently from payment stablecoins, and most payment flows avoid them.",[18,8403,8405],{"id":8404},"which-stablecoins-matter-for-payments","Which stablecoins matter for payments?",[11,8407,8408,8409,329],{},"Two tokens dominate: USDT (Tether) is the largest by circulation and dominates trading volume, especially outside the US. USDC (Circle) is generally preferred by US businesses for its reserve transparency and regulatory posture. The practical differences, chain support, liquidity, and compliance considerations are covered in our comparison of ",[133,8410,177],{"href":176},[11,8412,8413],{},"Both run on multiple blockchains, including Ethereum, Base, Polygon, Arbitrum, Solana, and Tron. The network affects transfer cost and speed, but a properly backed dollar token is worth one dollar on any of them.",[11,8415,8416,8417],{},"One common confusion is worth clearing up: not every large crypto asset is a stablecoin. XRP, for example, is a floating asset, not a pegged one. We explain the distinction in ",[133,8418,5840],{"href":5852},[18,8420,8422],{"id":8421},"how-did-stablecoins-get-here","How did stablecoins get here?",[11,8424,8425],{},"A short timeline explains why the category looks the way it does:",[144,8427,8428,8434,8440,8446,8452,8458],{},[147,8429,8430,8433],{},[150,8431,8432],{},"2014."," Tether launches the first widely used dollar token, initially on a Bitcoin sidechain, to give crypto traders a stable unit between trades.",[147,8435,8436,8439],{},[150,8437,8438],{},"2018."," Circle and Coinbase launch USDC with a compliance-first posture: US licensing, monthly attestations, and reserves in cash and Treasuries.",[147,8441,8442,8445],{},[150,8443,8444],{},"2020 to 2021."," Supply grows tenfold as stablecoins become the settlement layer of crypto markets, and the first serious payment use cases appear in emerging markets.",[147,8447,8448,8451],{},[150,8449,8450],{},"May 2022."," TerraUSD, an algorithmic stablecoin with no full reserves, collapses from 18 billion dollars to nearly zero in a week. The failure reshapes both the market and the coming regulation: full reserves or nothing.",[147,8453,8454,8457],{},[150,8455,8456],{},"2023 to 2025."," Regulation arrives. The EU adopts MiCA, the US passes the GENIUS Act, and Brazil, Japan, Singapore, and the UAE build licensing regimes. Stablecoins become a regulated payments product rather than a crypto curiosity.",[147,8459,8460,8463],{},[150,8461,8462],{},"2026."," Supply exceeds 200 billion dollars, banks pilot their own tokens, and businesses adopt stablecoin rails through APIs rather than exchanges.",[11,8465,8466],{},"The pattern across the timeline: every crisis removed a weak design, and every regulation locked in the strong one. What survived is the fully reserved, redeemable, attested dollar token.",[18,8468,8470],{"id":8469},"how-is-a-stablecoin-different-from-bank-money-and-cbdcs","How is a stablecoin different from bank money and CBDCs?",[11,8472,8473],{},"A dollar in a bank account is a claim on that bank, moved through systems like ACH that run on banking hours. A stablecoin is a claim on the issuer's reserves, moved on public blockchains that run continuously. In practice the differences that matter are hours (24\u002F7 vs banking days), speed (minutes vs days for cross-border), programmability (API-native vs portal-native), and counterparty (issuer reserves vs bank balance sheet).",[11,8475,8476],{},"A central bank digital currency (CBDC) would be a direct claim on the central bank. Despite years of pilots, no major economy has launched a retail CBDC at scale, and the US has moved in the opposite direction, formalizing private stablecoin issuance through the GENIUS Act instead. For the foreseeable future, regulated private stablecoins are the digital dollar that actually ships.",[18,8478,8480],{"id":8479},"what-are-stablecoins-used-for","What are stablecoins used for?",[144,8482,8483,8492,8498,8504],{},[147,8484,8485,8488,8489,8491],{},[150,8486,8487],{},"Cross-border payments."," A stablecoin transfer settles in seconds to minutes, at any hour, on any day, without correspondent banks. A payment that takes 3 to 5 business days by international wire can arrive the same day when it moves as a stablecoin and pays out over a fast local rail like Pix in Brazil. This is the core of ",[133,8490,8127],{"href":516}," as a business practice.",[147,8493,8494,8497],{},[150,8495,8496],{},"Dollar access and savings."," People and companies in high-inflation economies hold digital dollars without a US bank account. This is one of the largest real-world uses in Latin America, Africa, and parts of Asia.",[147,8499,8500,8503],{},[150,8501,8502],{},"Market settlement."," Stablecoins are the cash leg of most crypto trading, which is where their liquidity depth comes from.",[147,8505,8506,8509],{},[150,8507,8508],{},"Programmable treasury."," Because stablecoins are software objects, payouts, conversions, and sweeps can be automated through an API rather than a banking portal.",[18,8511,8513],{"id":8512},"how-do-businesses-use-stablecoins-without-holding-crypto","How do businesses use stablecoins without holding crypto?",[11,8515,8516],{},"Most businesses that benefit from stablecoins never touch a token directly. They use infrastructure providers that handle the crypto leg in the middle:",[289,8518,8519,8522,8525],{},[147,8520,8521],{},"Money enters as regular fiat, for example a Pix transfer in Brazil or an ACH transfer in the US, and is converted to stablecoins.",[147,8523,8524],{},"The stablecoins move across a blockchain in minutes.",[147,8526,8527],{},"On the other side, the stablecoins convert to local currency and pay out over the local rail.",[11,8529,8530,8531,8533,8534,8536],{},"The sender sees a normal bank payment out. The receiver sees a normal bank payment in. The stablecoin leg supplies the speed and reach. Providers expose this as a ",[133,8532,5916],{"href":1283},", and products like ",[133,8535,1570],{"href":1067}," let a business receive US bank transfers that settle directly as USDC.",[18,8538,8540],{"id":8539},"what-does-it-cost-to-move-money-with-stablecoins","What does it cost to move money with stablecoins?",[11,8542,8543],{},"Three costs stack in a stablecoin payment, and all three are usually smaller than their traditional equivalents:",[144,8545,8546,8552,8557],{},[147,8547,8548,8551],{},[150,8549,8550],{},"Network fees."," The blockchain transfer itself: fractions of a cent on networks like Tron, Base, or Solana, a few cents to a few dollars on Ethereum depending on congestion. Fixed per transfer regardless of amount, which makes large transfers extremely cheap to move.",[147,8553,8554,8556],{},[150,8555,5333],{}," The FX rate and fee when stablecoins become local currency or the reverse. This is the meaningful cost in a cross-border flow, and it is where providers differ most: an opaque rate can hide more margin than any stated fee. Always compare the total amount received.",[147,8558,8559,8562],{},[150,8560,8561],{},"Provider fees."," Flat or percentage fees per payout or collection, published upfront by transparent providers.",[11,8564,8565],{},"Compare that stack to an international wire: 25 to 50 dollars in bank fees, correspondent deductions along the way, an FX margin frequently above 2 percent, and days of waiting. The stablecoin route compresses all of it into one quoted conversion and a settlement measured in minutes.",[18,8567,8569],{"id":8568},"what-are-the-risks-of-stablecoins","What are the risks of stablecoins?",[11,8571,8572],{},"An honest list, because the risks are real and manageable:",[144,8574,8575,8581,8587,8596],{},[147,8576,8577,8580],{},[150,8578,8579],{},"Issuer risk."," The token is only as good as the reserves behind it. Prefer issuers with frequent independent attestations and clear redemption rights.",[147,8582,8583,8586],{},[150,8584,8585],{},"Depeg events."," Even well-run stablecoins can trade briefly below one dollar during stress. USDC dipped in March 2023 when a reserve bank failed, then recovered fully within days. Structure matters more than headlines: the reserves were there.",[147,8588,8589,8592,8593,8595],{},[150,8590,8591],{},"Regulatory change."," Rules are tightening in most major markets. That is mostly good for payment users, since it standardizes reserves and redemption, but it means issuer and provider choices should track the rules. Our ",[133,8594,2802],{"href":1663}," follows the main regimes.",[147,8597,8598,8601],{},[150,8599,8600],{},"Operational risk."," Sending tokens on the wrong network or to a wrong address can lose funds. Using a provider with compliance checks and managed wallets removes most of this class of error.",[18,8603,8605],{"id":8604},"how-are-stablecoins-regulated","How are stablecoins regulated?",[11,8607,8608,8609,8611],{},"The short version: payment stablecoins are becoming a licensed, reserve-regulated product category worldwide. The EU's MiCA regime requires authorization, full reserves, and redemption at par, explained in our ",[133,8610,6872],{"href":171},". The US GENIUS Act establishes federal requirements for payment stablecoin issuers. Brazil regulates stablecoin service providers through its central bank framework for virtual asset service providers. Japan limits issuance to licensed entities such as banks and trust companies.",[11,8613,8614],{},"For a business, the practical consequence is that compliance lives at the provider layer: the provider that converts and moves your funds should run KYC, sanctions screening, and travel rule compliance on every transfer.",[18,8616,5815],{"id":5814},[11,8618,8619,8621,8622,8624,8625,1567,8627,8629],{},[133,8620,952],{"href":951}," is a stablecoin API for global payments. Businesses use it to convert USDC and USDT to local fiat and pay out over local rails like Pix, SPEI, ACH, and wire in 100+ countries, with KYC and compliance built into every flow, plus ",[133,8623,8295],{"href":1067}," that turn incoming bank transfers into stablecoins automatically. Live conversion rates are public, for example ",[133,8626,1073],{"href":1072},[133,8628,1201],{"href":967}," is flat and published. The point of the product is the theme of this article: your customers and counterparties see normal bank money, and the stablecoin layer does the work invisibly.",[11,8631,8632],{},[1210,8633,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":8635},[8636,8637,8638,8639,8640,8641,8642,8643,8644,8645,8646],{"id":8349,"depth":520,"text":8350},{"id":8370,"depth":520,"text":8371},{"id":8404,"depth":520,"text":8405},{"id":8421,"depth":520,"text":8422},{"id":8469,"depth":520,"text":8470},{"id":8479,"depth":520,"text":8480},{"id":8512,"depth":520,"text":8513},{"id":8539,"depth":520,"text":8540},{"id":8568,"depth":520,"text":8569},{"id":8604,"depth":520,"text":8605},{"id":5814,"depth":520,"text":5815},"A stablecoin is a digital token designed to hold a fixed value, usually one US dollar. Learn how they stay stable, the main types, and what they are used for.",[8649,8652,8655,8658],{"q":8650,"a":8651},"What is a stablecoin in simple terms?","A stablecoin is a digital token built to always be worth a fixed amount, almost always one US dollar. The issuer holds reserves such as cash and short-term US Treasuries so that every token can be redeemed for a dollar.",{"q":8653,"a":8654},"What is the difference between a stablecoin and Bitcoin?","Bitcoin's price floats freely with supply and demand, so it can move sharply in a day. A stablecoin is designed not to move: its value is pegged to an asset like the US dollar and backed by reserves, which makes it useful for payments rather than speculation.",{"q":8656,"a":8657},"Are stablecoins safe?","It depends on the issuer and the structure. Fully reserved, regulated stablecoins that publish independent attestations, such as USDC, have maintained their peg through market stress. Algorithmic stablecoins without full reserves have failed, most famously TerraUSD in 2022.",{"q":8659,"a":8660},"What are stablecoins actually used for?","The main uses are cross-border payments, dollar savings in high-inflation economies, and settlement in crypto markets. Businesses use stablecoins as fast, low-cost rails between currencies, often without holding them directly.",{"author":555},"---\ntitle: \"What is a stablecoin? Definition, types, and how they work\"\nseoTitle: \"What is a stablecoin? Definition, types, and how they work\"\ndescription: \"A stablecoin is a digital token designed to hold a fixed value, usually one US dollar. Learn how they stay stable, the main types, and what they are used for.\"\ndate: \"2026-08-15\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a stablecoin in simple terms?\"\n    a: \"A stablecoin is a digital token built to always be worth a fixed amount, almost always one US dollar. The issuer holds reserves such as cash and short-term US Treasuries so that every token can be redeemed for a dollar.\"\n  - q: \"What is the difference between a stablecoin and Bitcoin?\"\n    a: \"Bitcoin's price floats freely with supply and demand, so it can move sharply in a day. A stablecoin is designed not to move: its value is pegged to an asset like the US dollar and backed by reserves, which makes it useful for payments rather than speculation.\"\n  - q: \"Are stablecoins safe?\"\n    a: \"It depends on the issuer and the structure. Fully reserved, regulated stablecoins that publish independent attestations, such as USDC, have maintained their peg through market stress. Algorithmic stablecoins without full reserves have failed, most famously TerraUSD in 2022.\"\n  - q: \"What are stablecoins actually used for?\"\n    a: \"The main uses are cross-border payments, dollar savings in high-inflation economies, and settlement in crypto markets. Businesses use stablecoins as fast, low-cost rails between currencies, often without holding them directly.\"\n---\n\nA stablecoin is a digital token designed to hold a constant value, almost always one US dollar. Unlike Bitcoin or Ether, whose prices float freely, a stablecoin is built to be boring: a dollar today, a dollar tomorrow, a dollar next year.\n\nThat stability is what makes stablecoins useful for payments. Circulating stablecoin supply has grown past 200 billion dollars, according to public trackers such as [DefiLlama](https:\u002F\u002Fdefillama.com\u002Fstablecoins), and stablecoins now settle trillions of dollars in transfer volume per year. Most of that activity is not speculation. It is money movement: businesses paying suppliers, workers receiving salaries, and companies holding digital dollars in markets where local currency loses value.\n\n## How does a stablecoin keep its value?\n\nThe dominant model is simple: for every token in circulation, the issuer holds one dollar of reserves, typically cash and short-term US Treasuries. When a customer deposits dollars, the issuer mints new tokens. When a customer redeems tokens, the issuer burns them and returns dollars. As long as reserves match supply and redemption works, arbitrage keeps the market price pinned to one dollar.\n\nTrust depends on proof. Serious issuers publish regular reserve reports. [Circle](https:\u002F\u002Fwww.circle.com\u002Ftransparency), the issuer of USDC, publishes monthly attestations from an independent accounting firm. [Tether](https:\u002F\u002Ftether.to\u002Fen\u002Ftransparency\u002F), the issuer of USDT, publishes quarterly attestations. Regulation increasingly turns this from good practice into law: reserve, redemption, and disclosure requirements are now written into frameworks like the EU's MiCA and the US GENIUS Act, which we cover in our [stablecoin regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026).\n\n## What types of stablecoins exist?\n\nThree structures cover almost everything in circulation:\n\n- **Fiat-backed stablecoins.** Reserves are held in cash and cash equivalents at banks and custodians. USDC and USDT both work this way, and together they account for the large majority of stablecoin supply. This is the model regulators have chosen to formalize, and the only model widely used for business payments.\n- **Crypto-collateralized stablecoins.** The token is backed by other crypto assets locked in smart contracts, with more collateral than issued value to absorb price swings. DAI is the best-known example. These are transparent by design but more complex, and their supply is small compared to fiat-backed coins.\n- **Algorithmic stablecoins.** These tried to hold a peg through supply algorithms rather than full reserves. The model failed badly: TerraUSD collapsed in May 2022 and erased tens of billions of dollars of value. Modern regulation, including MiCA, effectively excludes unbacked algorithmic designs from operating as payment stablecoins.\n\nThere is also a growing category of **yield-bearing dollar tokens** that pass reserve interest to holders. Regulators generally treat these differently from payment stablecoins, and most payment flows avoid them.\n\n## Which stablecoins matter for payments?\n\nTwo tokens dominate: USDT (Tether) is the largest by circulation and dominates trading volume, especially outside the US. USDC (Circle) is generally preferred by US businesses for its reserve transparency and regulatory posture. The practical differences, chain support, liquidity, and compliance considerations are covered in our comparison of [USDC vs USDT for payments](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments).\n\nBoth run on multiple blockchains, including Ethereum, Base, Polygon, Arbitrum, Solana, and Tron. The network affects transfer cost and speed, but a properly backed dollar token is worth one dollar on any of them.\n\nOne common confusion is worth clearing up: not every large crypto asset is a stablecoin. XRP, for example, is a floating asset, not a pegged one. We explain the distinction in [Is XRP a stablecoin?](\u002Fresources\u002Fmore\u002Fis-xrp-a-stablecoin)\n\n## How did stablecoins get here?\n\nA short timeline explains why the category looks the way it does:\n\n- **2014.** Tether launches the first widely used dollar token, initially on a Bitcoin sidechain, to give crypto traders a stable unit between trades.\n- **2018.** Circle and Coinbase launch USDC with a compliance-first posture: US licensing, monthly attestations, and reserves in cash and Treasuries.\n- **2020 to 2021.** Supply grows tenfold as stablecoins become the settlement layer of crypto markets, and the first serious payment use cases appear in emerging markets.\n- **May 2022.** TerraUSD, an algorithmic stablecoin with no full reserves, collapses from 18 billion dollars to nearly zero in a week. The failure reshapes both the market and the coming regulation: full reserves or nothing.\n- **2023 to 2025.** Regulation arrives. The EU adopts MiCA, the US passes the GENIUS Act, and Brazil, Japan, Singapore, and the UAE build licensing regimes. Stablecoins become a regulated payments product rather than a crypto curiosity.\n- **2026.** Supply exceeds 200 billion dollars, banks pilot their own tokens, and businesses adopt stablecoin rails through APIs rather than exchanges.\n\nThe pattern across the timeline: every crisis removed a weak design, and every regulation locked in the strong one. What survived is the fully reserved, redeemable, attested dollar token.\n\n## How is a stablecoin different from bank money and CBDCs?\n\nA dollar in a bank account is a claim on that bank, moved through systems like ACH that run on banking hours. A stablecoin is a claim on the issuer's reserves, moved on public blockchains that run continuously. In practice the differences that matter are hours (24\u002F7 vs banking days), speed (minutes vs days for cross-border), programmability (API-native vs portal-native), and counterparty (issuer reserves vs bank balance sheet).\n\nA central bank digital currency (CBDC) would be a direct claim on the central bank. Despite years of pilots, no major economy has launched a retail CBDC at scale, and the US has moved in the opposite direction, formalizing private stablecoin issuance through the GENIUS Act instead. For the foreseeable future, regulated private stablecoins are the digital dollar that actually ships.\n\n## What are stablecoins used for?\n\n- **Cross-border payments.** A stablecoin transfer settles in seconds to minutes, at any hour, on any day, without correspondent banks. A payment that takes 3 to 5 business days by international wire can arrive the same day when it moves as a stablecoin and pays out over a fast local rail like Pix in Brazil. This is the core of [stablecoin payments](\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide) as a business practice.\n- **Dollar access and savings.** People and companies in high-inflation economies hold digital dollars without a US bank account. This is one of the largest real-world uses in Latin America, Africa, and parts of Asia.\n- **Market settlement.** Stablecoins are the cash leg of most crypto trading, which is where their liquidity depth comes from.\n- **Programmable treasury.** Because stablecoins are software objects, payouts, conversions, and sweeps can be automated through an API rather than a banking portal.\n\n## How do businesses use stablecoins without holding crypto?\n\nMost businesses that benefit from stablecoins never touch a token directly. They use infrastructure providers that handle the crypto leg in the middle:\n\n1. Money enters as regular fiat, for example a Pix transfer in Brazil or an ACH transfer in the US, and is converted to stablecoins.\n2. The stablecoins move across a blockchain in minutes.\n3. On the other side, the stablecoins convert to local currency and pay out over the local rail.\n\nThe sender sees a normal bank payment out. The receiver sees a normal bank payment in. The stablecoin leg supplies the speed and reach. Providers expose this as a [stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api), and products like [virtual accounts](\u002Fvirtual-accounts) let a business receive US bank transfers that settle directly as USDC.\n\n## What does it cost to move money with stablecoins?\n\nThree costs stack in a stablecoin payment, and all three are usually smaller than their traditional equivalents:\n\n- **Network fees.** The blockchain transfer itself: fractions of a cent on networks like Tron, Base, or Solana, a few cents to a few dollars on Ethereum depending on congestion. Fixed per transfer regardless of amount, which makes large transfers extremely cheap to move.\n- **Conversion.** The FX rate and fee when stablecoins become local currency or the reverse. This is the meaningful cost in a cross-border flow, and it is where providers differ most: an opaque rate can hide more margin than any stated fee. Always compare the total amount received.\n- **Provider fees.** Flat or percentage fees per payout or collection, published upfront by transparent providers.\n\nCompare that stack to an international wire: 25 to 50 dollars in bank fees, correspondent deductions along the way, an FX margin frequently above 2 percent, and days of waiting. The stablecoin route compresses all of it into one quoted conversion and a settlement measured in minutes.\n\n## What are the risks of stablecoins?\n\nAn honest list, because the risks are real and manageable:\n\n- **Issuer risk.** The token is only as good as the reserves behind it. Prefer issuers with frequent independent attestations and clear redemption rights.\n- **Depeg events.** Even well-run stablecoins can trade briefly below one dollar during stress. USDC dipped in March 2023 when a reserve bank failed, then recovered fully within days. Structure matters more than headlines: the reserves were there.\n- **Regulatory change.** Rules are tightening in most major markets. That is mostly good for payment users, since it standardizes reserves and redemption, but it means issuer and provider choices should track the rules. Our [regulation tracker](\u002Fresources\u002Fmore\u002Fstablecoin-regulation-tracker-2026) follows the main regimes.\n- **Operational risk.** Sending tokens on the wrong network or to a wrong address can lose funds. Using a provider with compliance checks and managed wallets removes most of this class of error.\n\n## How are stablecoins regulated?\n\nThe short version: payment stablecoins are becoming a licensed, reserve-regulated product category worldwide. The EU's MiCA regime requires authorization, full reserves, and redemption at par, explained in our [MiCA guide](\u002Fresources\u002Fmore\u002Fmica-stablecoin-rules-explained). The US GENIUS Act establishes federal requirements for payment stablecoin issuers. Brazil regulates stablecoin service providers through its central bank framework for virtual asset service providers. Japan limits issuance to licensed entities such as banks and trust companies.\n\nFor a business, the practical consequence is that compliance lives at the provider layer: the provider that converts and moves your funds should run KYC, sanctions screening, and travel rule compliance on every transfer.\n\n## How does BlindPay fit in?\n\n[BlindPay](\u002Fglobal-payments) is a stablecoin API for global payments. Businesses use it to convert USDC and USDT to local fiat and pay out over local rails like Pix, SPEI, ACH, and wire in 100+ countries, with KYC and compliance built into every flow, plus [virtual US accounts](\u002Fvirtual-accounts) that turn incoming bank transfers into stablecoins automatically. Live conversion rates are public, for example [USDC to BRL](\u002Fusdc-to-brl), and [pricing](\u002Fpricing) is flat and published. The point of the product is the theme of this article: your customers and counterparties see normal bank money, and the stablecoin layer does the work invisibly.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":8334,"description":8647},"resources\u002Fmore\u002Fwhat-is-a-stablecoin","3xBCVPnBqr-3Yjf9IYJAyvCIdfFWic7yGJJ9_fZaXAA",{"id":8667,"title":8668,"authors":6,"body":8669,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":9086,"description":9087,"extension":536,"faq":9088,"howto":6,"isBlog":553,"isChangelog":553,"meta":9104,"navigation":556,"path":9105,"pillar":553,"products":6,"rawbody":9106,"role":6,"seo":9107,"seoTitle":9108,"stem":9109,"thumbnail":6,"updated":9086,"__hash__":9110},"content\u002Fresources\u002Fmore\u002Fwhat-is-an-off-ramp-wallet.md","What is an off-ramp wallet? A deposit address that pays out to a bank account",{"type":8,"value":8670,"toc":9077},[8671,8674,8680,8684,8687,8713,8716,8720,8728,8834,8837,8841,8844,8847,8861,8868,8876,8880,8950,8958,8962,8965,8991,9002,9006,9058,9062,9065,9072],[11,8672,8673],{},"An off-ramp wallet is a blockchain deposit address tied to one bank account. Every USDC or USDT deposit it receives converts to fiat and pays out to that bank account on its own, with no quote call and no payout call. You share the address with whoever pays you, and the money shows up as a bank transfer.",[11,8675,8676,8677,8679],{},"Think of it as the reverse of a virtual account. A ",[133,8678,7382],{"href":2926}," turns incoming fiat into stablecoin. An off-ramp wallet turns incoming stablecoin into fiat.",[18,8681,8683],{"id":8682},"how-does-an-off-ramp-wallet-work","How does an off-ramp wallet work?",[11,8685,8686],{},"Four steps, and only the first needs code:",[289,8688,8689,8695,8701,8707],{},[147,8690,8691,8694],{},[150,8692,8693],{},"Create it on a bank account."," The receiver is onboarded (KYC or KYB), their bank account is added, and the off-ramp wallet is created on that account for one network. The bank account becomes the permanent payout destination.",[147,8696,8697,8700],{},[150,8698,8699],{},"Share the deposit address."," The address goes to whoever pays: a client, an exchange withdrawal, another company's treasury system.",[147,8702,8703,8706],{},[150,8704,8705],{},"The deposit lands."," Someone sends USDC or USDT to the address on the right network.",[147,8708,8709,8712],{},[150,8710,8711],{},"Conversion and payout run automatically."," The provider converts the stablecoin and sends fiat to the linked bank account over the local rail. You track it through the same payout statuses and webhooks as any other payout.",[11,8714,8715],{},"That's the whole thing. No quote to request, no rate to confirm, no on-chain approval to sign.",[18,8717,8719],{"id":8718},"which-networks-and-stablecoins-does-an-off-ramp-wallet-accept","Which networks and stablecoins does an off-ramp wallet accept?",[11,8721,8722,8723,8727],{},"It depends on the provider. BlindPay's ",[133,8724,8726],{"href":8725},"\u002Fdocs\u002Fofframp-wallets","offramp wallets"," accept these:",[23,8729,8730,8744],{},[26,8731,8732],{},[29,8733,8734,8736,8739,8741],{},[32,8735,60],{},[32,8737,8738],{},"Stablecoins",[32,8740,3308],{},[32,8742,8743],{},"Additional fee per deposit",[42,8745,8746,8759,8769,8779,8789,8799,8810,8822],{},[29,8747,8748,8750,8753,8756],{},[47,8749,3818],{},[47,8751,8752],{},"USDC and USDT",[47,8754,8755],{},"No fixed minimum",[47,8757,8758],{},"0",[29,8760,8761,8763,8765,8767],{},[47,8762,3830],{},[47,8764,2190],{},[47,8766,8755],{},[47,8768,8758],{},[29,8770,8771,8773,8775,8777],{},[47,8772,3842],{},[47,8774,2190],{},[47,8776,8755],{},[47,8778,8758],{},[29,8780,8781,8783,8785,8787],{},[47,8782,3854],{},[47,8784,2190],{},[47,8786,8755],{},[47,8788,8758],{},[29,8790,8791,8793,8795,8797],{},[47,8792,3866],{},[47,8794,2190],{},[47,8796,8755],{},[47,8798,8758],{},[29,8800,8801,8803,8805,8807],{},[47,8802,3805],{},[47,8804,2190],{},[47,8806,8755],{},[47,8808,8809],{},"1 USDC",[29,8811,8812,8814,8816,8819],{},[47,8813,3878],{},[47,8815,2190],{},[47,8817,8818],{},"50 USDC",[47,8820,8821],{},"0.50 USDC",[29,8823,8824,8826,8828,8831],{},[47,8825,3902],{},[47,8827,2194],{},[47,8829,8830],{},"200 USDT",[47,8832,8833],{},"15 USDT",[11,8835,8836],{},"\"No fixed minimum\" means the deposit only has to cover its own fees. The network is part of the address. A USDC transfer sent on the wrong chain is a different asset in the wrong place, so tell senders the network, not just the address.",[18,8838,8840],{"id":8839},"what-does-an-off-ramp-wallet-cost","What does an off-ramp wallet cost?",[11,8842,8843],{},"Three fees stack on each deposit: the chain's additional fee from the table above, a percentage fee, and the bank transfer fee for the payout rail. The percentage and bank transfer fees depend on your pricing.",[11,8845,8846],{},"BlindPay's docs work through one example: 100 USDT sent on Tron, paid out over ACH.",[289,8848,8849,8852,8855,8858],{},[147,8850,8851],{},"Convert: 100 USDT = $100.00 (USDT deposits convert at a flat 1:1 with no market spread; USDC uses the live market rate)",[147,8853,8854],{},"Additional fee: 15 USDT = $15.00",[147,8856,8857],{},"Percentage fee: 0.1 percent of $100.00 = $0.10",[147,8859,8860],{},"Bank transfer fee: $0.40 (ACH)",[11,8862,8863,8864,8867],{},"The bank account receives ",[150,8865,8866],{},"$84.50",". Send the same 100 USDT on Polygon, with the same example percentage and ACH fees, and it receives $99.50. Same payment, same bank, $15 apart, all of it from the network choice.",[11,8869,8870,8871,8875],{},"That's the flat-fee lesson from ",[133,8872,8874],{"href":8873},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-fees-explained","off-ramp fees explained"," in miniature. Fixed costs punish small deposits, so pick the network by the size of the payments it will carry.",[18,8877,8879],{"id":8878},"when-should-you-use-an-off-ramp-wallet-instead-of-a-payout-call","When should you use an off-ramp wallet instead of a payout call?",[23,8881,8882,8894],{},[26,8883,8884],{},[29,8885,8886,8888,8891],{},[32,8887],{},[32,8889,8890],{},"Off-ramp wallet",[32,8892,8893],{},"Quote and payout call",[42,8895,8896,8907,8918,8929,8940],{},[29,8897,8898,8901,8904],{},[47,8899,8900],{},"Who starts it",[47,8902,8903],{},"Anyone who can send an on-chain transfer",[47,8905,8906],{},"Your integration, through the API",[29,8908,8909,8912,8915],{},[47,8910,8911],{},"Rate",[47,8913,8914],{},"Market rate when the deposit lands",[47,8916,8917],{},"Locked in the quote, 5 minutes by default",[29,8919,8920,8923,8926],{},[47,8921,8922],{},"On-chain approval",[47,8924,8925],{},"None; the sender just transfers",[47,8927,8928],{},"Needed for external wallets (for example, an ERC-20 approve)",[29,8930,8931,8934,8937],{},[47,8932,8933],{},"Destination",[47,8935,8936],{},"One fixed bank account",[47,8938,8939],{},"Any approved bank account per payout",[29,8941,8942,8944,8947],{},[47,8943,2391],{},[47,8945,8946],{},"Third-party payers, exchange withdrawals, recurring settlement to one account",[47,8948,8949],{},"Payouts to many recipients, payments that need a known amount",[11,8951,8952,8953,8957],{},"The deciding question: who controls the send? If it's you, a payout call gives you a locked rate and an exact delivered amount. If it's someone else, or a system that can only make a plain transfer, an off-ramp wallet removes the coordination entirely. A marketplace seller who gets paid by buyers in USDC is the textbook case; the ",[133,8954,8956],{"href":8955},"\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","LatAm marketplace payouts guide"," shows the wider flow.",[18,8959,8961],{"id":8960},"what-can-go-wrong-with-an-off-ramp-wallet","What can go wrong with an off-ramp wallet?",[11,8963,8964],{},"Four things, all avoidable:",[144,8966,8967,8973,8979,8985],{},[147,8968,8969,8972],{},[150,8970,8971],{},"Deposits below the fees."," On BlindPay, a deposit smaller than its total fees isn't converted. No payout is created, the funds stay at the deposit address, and no webhook fires. Watch for them.",[147,8974,8975,8978],{},[150,8976,8977],{},"Wrong network or token."," USDC isn't deployed on Tron, and USDT isn't accepted on Base, Arbitrum, or Stellar. Publish the network next to the address every time.",[147,8980,8981,8984],{},[150,8982,8983],{},"One wallet per bank account per network."," Creating a second one for the same bank account and network fails. Save the address from the first response.",[147,8986,8987,8990],{},[150,8988,8989],{},"Rate exposure."," USDC deposits convert at the rate when they land. If the delivered amount must be exact, use a quote instead.",[11,8992,8993,8994,8998,8999,9001],{},"Once a payout exists, it follows the normal lifecycle: processing, then completed, failed, or refunded. ",[133,8995,8997],{"href":8996},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained","Stablecoin payout statuses explained"," covers each state, and ",[133,9000,3687],{"href":3686}," covers matching deposits to payouts.",[18,9003,9005],{"id":9004},"what-terms-come-up-around-off-ramps","What terms come up around off-ramps?",[144,9007,9008,9014,9024,9030,9036,9042,9052],{},[147,9009,9010,9013],{},[150,9011,9012],{},"On-ramp:"," a service that converts fiat into stablecoins.",[147,9015,9016,9019,9020,329],{},[150,9017,9018],{},"Off-ramp:"," a service that converts stablecoins into fiat and pays it to a bank account; more in ",[133,9021,9023],{"href":9022},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","what is a stablecoin off-ramp",[147,9025,9026,9029],{},[150,9027,9028],{},"Deposit address:"," the blockchain address a sender transfers stablecoins to, valid on one network.",[147,9031,9032,9035],{},[150,9033,9034],{},"Non-custodial settlement:"," a payout where funds stay in the sender's own wallet until the moment the payout executes.",[147,9037,9038,9041],{},[150,9039,9040],{},"Pre-funding:"," keeping a balance parked with a provider or in the destination country before you can pay out.",[147,9043,9044,9047,9048,329],{},[150,9045,9046],{},"VASP:"," a virtual asset service provider, the regulatory category for businesses that exchange or transfer crypto for others; see ",[133,9049,9051],{"href":9050},"\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp","what is a VASP",[147,9053,9054,9057],{},[150,9055,9056],{},"Travel rule:"," the requirement that providers pass sender and receiver information along with a transfer above set thresholds.",[18,9059,9061],{"id":9060},"how-do-you-set-one-up-on-blindpay","How do you set one up on BlindPay?",[11,9063,9064],{},"Create a customer, add their bank account, then create the offramp wallet on that bank account with the network you want. The response returns the deposit address. On development instances the wallets live on testnets (Tron has none) and receive USDB, BlindPay's test stablecoin, with no additional fee, so you can test the full deposit-to-payout loop before going live.",[11,9066,9067,9068,9071],{},"Read the ",[133,9069,9070],{"href":8725},"offramp wallets reference",", then create one in the sandbox and send it a test deposit.",[11,9073,9074],{},[1210,9075,9076],{},"This article is for general information only and is not financial advice.",{"title":519,"searchDepth":520,"depth":520,"links":9078},[9079,9080,9081,9082,9083,9084,9085],{"id":8682,"depth":520,"text":8683},{"id":8718,"depth":520,"text":8719},{"id":8839,"depth":520,"text":8840},{"id":8878,"depth":520,"text":8879},{"id":8960,"depth":520,"text":8961},{"id":9004,"depth":520,"text":9005},{"id":9060,"depth":520,"text":9061},"2026-09-14","An off-ramp wallet turns every USDC or USDT deposit into fiat paid to a linked bank account, with no quote or payout call. How it works, fees, minimums.",[9089,9092,9095,9098,9101],{"q":9090,"a":9091},"What is an off-ramp wallet?","A blockchain deposit address tied to one bank account. Every USDC or USDT deposit it receives is converted to fiat and paid out to that bank account automatically, with no quote or payout call from the integrator. It works like a standing instruction: whatever lands at the address becomes a bank transfer.",{"q":9093,"a":9094},"Do I need a crypto wallet to use an off-ramp?","Not your own. Whoever sends the stablecoin needs a wallet or an exchange account to send from, but the receiver only needs a bank account. With an off-ramp wallet, the provider creates the deposit address and the receiver just sees local currency arrive over Pix, SPEI, ACH, or another local rail.",{"q":9096,"a":9097},"What happens if a deposit is below the off-ramp wallet minimum?","On BlindPay, a deposit that doesn't cover its fees isn't converted. No payout is created, and the funds stay at the deposit address instead of refunding automatically. No API error or webhook fires, because no API call triggered the deposit, so monitor for small deposits and recover them manually.",{"q":9099,"a":9100},"How is an off-ramp wallet different from a payout API call?","A payout call starts with a quote: the rate and fees lock for a few minutes, then the provider pulls the stablecoin from your wallet. An off-ramp wallet is push-based: anyone sends to the address, and conversion runs at the rate when the deposit lands. Use payout calls when you need a locked rate before sending, and an off-ramp wallet when the sender can only make a plain on-chain transfer.",{"q":9102,"a":9103},"How long does an off-ramp wallet take to pay out?","The on-chain deposit confirms in seconds to minutes, depending on the network. The payout then follows the local rail: Pix, SPEI, and Argentina's Transfers land in minutes, while ACH, wire, and SEPA take about 1 to 2 business days.",{"author":555},"\u002Fresources\u002Fmore\u002Fwhat-is-an-off-ramp-wallet","---\ntitle: \"What is an off-ramp wallet? A deposit address that pays out to a bank account\"\nseoTitle: \"What is an off-ramp wallet? Deposit address to bank payout\"\ndescription: \"An off-ramp wallet turns every USDC or USDT deposit into fiat paid to a linked bank account, with no quote or payout call. How it works, fees, minimums.\"\ndate: \"2026-09-14\"\nupdated: \"2026-09-14\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is an off-ramp wallet?\"\n    a: \"A blockchain deposit address tied to one bank account. Every USDC or USDT deposit it receives is converted to fiat and paid out to that bank account automatically, with no quote or payout call from the integrator. It works like a standing instruction: whatever lands at the address becomes a bank transfer.\"\n  - q: \"Do I need a crypto wallet to use an off-ramp?\"\n    a: \"Not your own. Whoever sends the stablecoin needs a wallet or an exchange account to send from, but the receiver only needs a bank account. With an off-ramp wallet, the provider creates the deposit address and the receiver just sees local currency arrive over Pix, SPEI, ACH, or another local rail.\"\n  - q: \"What happens if a deposit is below the off-ramp wallet minimum?\"\n    a: \"On BlindPay, a deposit that doesn't cover its fees isn't converted. No payout is created, and the funds stay at the deposit address instead of refunding automatically. No API error or webhook fires, because no API call triggered the deposit, so monitor for small deposits and recover them manually.\"\n  - q: \"How is an off-ramp wallet different from a payout API call?\"\n    a: \"A payout call starts with a quote: the rate and fees lock for a few minutes, then the provider pulls the stablecoin from your wallet. An off-ramp wallet is push-based: anyone sends to the address, and conversion runs at the rate when the deposit lands. Use payout calls when you need a locked rate before sending, and an off-ramp wallet when the sender can only make a plain on-chain transfer.\"\n  - q: \"How long does an off-ramp wallet take to pay out?\"\n    a: \"The on-chain deposit confirms in seconds to minutes, depending on the network. The payout then follows the local rail: Pix, SPEI, and Argentina's Transfers land in minutes, while ACH, wire, and SEPA take about 1 to 2 business days.\"\n---\n\nAn off-ramp wallet is a blockchain deposit address tied to one bank account. Every USDC or USDT deposit it receives converts to fiat and pays out to that bank account on its own, with no quote call and no payout call. You share the address with whoever pays you, and the money shows up as a bank transfer.\n\nThink of it as the reverse of a virtual account. A [virtual account](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained) turns incoming fiat into stablecoin. An off-ramp wallet turns incoming stablecoin into fiat.\n\n## How does an off-ramp wallet work?\n\nFour steps, and only the first needs code:\n\n1. **Create it on a bank account.** The receiver is onboarded (KYC or KYB), their bank account is added, and the off-ramp wallet is created on that account for one network. The bank account becomes the permanent payout destination.\n2. **Share the deposit address.** The address goes to whoever pays: a client, an exchange withdrawal, another company's treasury system.\n3. **The deposit lands.** Someone sends USDC or USDT to the address on the right network.\n4. **Conversion and payout run automatically.** The provider converts the stablecoin and sends fiat to the linked bank account over the local rail. You track it through the same payout statuses and webhooks as any other payout.\n\nThat's the whole thing. No quote to request, no rate to confirm, no on-chain approval to sign.\n\n## Which networks and stablecoins does an off-ramp wallet accept?\n\nIt depends on the provider. BlindPay's [offramp wallets](\u002Fdocs\u002Fofframp-wallets) accept these:\n\n| Network | Stablecoins | Minimum deposit | Additional fee per deposit |\n| --- | --- | --- | --- |\n| Polygon | USDC and USDT | No fixed minimum | 0 |\n| Base | USDC | No fixed minimum | 0 |\n| Arbitrum | USDC | No fixed minimum | 0 |\n| Tempo | USDC | No fixed minimum | 0 |\n| Arc | USDC | No fixed minimum | 0 |\n| Ethereum | USDC | No fixed minimum | 1 USDC |\n| Solana | USDC | 50 USDC | 0.50 USDC |\n| Tron | USDT | 200 USDT | 15 USDT |\n\n\"No fixed minimum\" means the deposit only has to cover its own fees. The network is part of the address. A USDC transfer sent on the wrong chain is a different asset in the wrong place, so tell senders the network, not just the address.\n\n## What does an off-ramp wallet cost?\n\nThree fees stack on each deposit: the chain's additional fee from the table above, a percentage fee, and the bank transfer fee for the payout rail. The percentage and bank transfer fees depend on your pricing.\n\nBlindPay's docs work through one example: 100 USDT sent on Tron, paid out over ACH.\n\n1. Convert: 100 USDT = $100.00 (USDT deposits convert at a flat 1:1 with no market spread; USDC uses the live market rate)\n2. Additional fee: 15 USDT = $15.00\n3. Percentage fee: 0.1 percent of $100.00 = $0.10\n4. Bank transfer fee: $0.40 (ACH)\n\nThe bank account receives **$84.50**. Send the same 100 USDT on Polygon, with the same example percentage and ACH fees, and it receives $99.50. Same payment, same bank, $15 apart, all of it from the network choice.\n\nThat's the flat-fee lesson from [off-ramp fees explained](\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-fees-explained) in miniature. Fixed costs punish small deposits, so pick the network by the size of the payments it will carry.\n\n## When should you use an off-ramp wallet instead of a payout call?\n\n| | Off-ramp wallet | Quote and payout call |\n| --- | --- | --- |\n| Who starts it | Anyone who can send an on-chain transfer | Your integration, through the API |\n| Rate | Market rate when the deposit lands | Locked in the quote, 5 minutes by default |\n| On-chain approval | None; the sender just transfers | Needed for external wallets (for example, an ERC-20 approve) |\n| Destination | One fixed bank account | Any approved bank account per payout |\n| Best for | Third-party payers, exchange withdrawals, recurring settlement to one account | Payouts to many recipients, payments that need a known amount |\n\nThe deciding question: who controls the send? If it's you, a payout call gives you a locked rate and an exact delivered amount. If it's someone else, or a system that can only make a plain transfer, an off-ramp wallet removes the coordination entirely. A marketplace seller who gets paid by buyers in USDC is the textbook case; the [LatAm marketplace payouts guide](\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam) shows the wider flow.\n\n## What can go wrong with an off-ramp wallet?\n\nFour things, all avoidable:\n\n- **Deposits below the fees.** On BlindPay, a deposit smaller than its total fees isn't converted. No payout is created, the funds stay at the deposit address, and no webhook fires. Watch for them.\n- **Wrong network or token.** USDC isn't deployed on Tron, and USDT isn't accepted on Base, Arbitrum, or Stellar. Publish the network next to the address every time.\n- **One wallet per bank account per network.** Creating a second one for the same bank account and network fails. Save the address from the first response.\n- **Rate exposure.** USDC deposits convert at the rate when they land. If the delivered amount must be exact, use a quote instead.\n\nOnce a payout exists, it follows the normal lifecycle: processing, then completed, failed, or refunded. [Stablecoin payout statuses explained](\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained) covers each state, and [webhooks and reconciliation](\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation) covers matching deposits to payouts.\n\n## What terms come up around off-ramps?\n\n- **On-ramp:** a service that converts fiat into stablecoins.\n- **Off-ramp:** a service that converts stablecoins into fiat and pays it to a bank account; more in [what is a stablecoin off-ramp](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp).\n- **Deposit address:** the blockchain address a sender transfers stablecoins to, valid on one network.\n- **Non-custodial settlement:** a payout where funds stay in the sender's own wallet until the moment the payout executes.\n- **Pre-funding:** keeping a balance parked with a provider or in the destination country before you can pay out.\n- **VASP:** a virtual asset service provider, the regulatory category for businesses that exchange or transfer crypto for others; see [what is a VASP](\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp).\n- **Travel rule:** the requirement that providers pass sender and receiver information along with a transfer above set thresholds.\n\n## How do you set one up on BlindPay?\n\nCreate a customer, add their bank account, then create the offramp wallet on that bank account with the network you want. The response returns the deposit address. On development instances the wallets live on testnets (Tron has none) and receive USDB, BlindPay's test stablecoin, with no additional fee, so you can test the full deposit-to-payout loop before going live.\n\nRead the [offramp wallets reference](\u002Fdocs\u002Fofframp-wallets), then create one in the sandbox and send it a test deposit.\n\n*This article is for general information only and is not financial advice.*\n",{"title":8668,"description":9087},"What is an off-ramp wallet? Deposit address to bank payout","resources\u002Fmore\u002Fwhat-is-an-off-ramp-wallet","5gbyENfAsi_cnmPS_RM5nf4I7Qq1oAS6x0B2UoRhtnM",{"id":9112,"title":9113,"authors":6,"body":9114,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":9661,"description":9662,"extension":536,"faq":9663,"howto":6,"isBlog":553,"isChangelog":553,"meta":9680,"navigation":556,"path":5176,"pillar":553,"products":6,"rawbody":9681,"role":6,"seo":9682,"seoTitle":9113,"stem":9683,"thumbnail":6,"updated":9661,"__hash__":9684},"content\u002Fresources\u002Fmore\u002Fwhat-is-crypto-wallet-integration.md","What is crypto wallet integration? A developer's guide",{"type":8,"value":9115,"toc":9650},[9116,9119,9122,9126,9129,9132,9141,9145,9148,9206,9220,9226,9230,9233,9315,9318,9338,9341,9345,9348,9354,9360,9366,9435,9438,9442,9457,9466,9478,9482,9485,9516,9523,9525,9528,9534,9547,9550,9554,9636,9638,9641],[11,9117,9118],{},"Crypto wallet integration is the work of adding blockchain wallet functions to a product you already run: creating or connecting wallets, deciding who holds the private keys, signing transactions, reading balances, and screening transfers before they move. Most teams don't build this layer themselves. They plug in a wallet provider through an API, an embedded SDK, or a white-label app.",[11,9120,9121],{},"This guide is for developers and product managers at the start of that project. It assumes you know REST APIs and webhooks, and not much about blockchains.",[18,9123,9125],{"id":9124},"what-is-crypto-wallet-integration","What is crypto wallet integration?",[11,9127,9128],{},"Crypto wallet integration connects your application to wallets on one or more blockchains, so your users can hold, send, and receive digital assets inside your product. In practice it means wiring four things into your stack: a way to create or link wallets, a way to control their keys, a way to sign and broadcast transactions, and a way to watch what happens on-chain.",[11,9130,9131],{},"A crypto wallet doesn't contain coins. A wallet is a private key plus the public address derived from it. The tokens live on the blockchain's ledger, and whoever controls the private key can move whatever that address holds. That one fact drives most design decisions in a wallet integration: who holds the key, who can sign, and what happens when a key is lost.",[11,9133,9134,9135,9140],{},"For fintech products the asset is usually a stablecoin, a token that tracks a currency like the US dollar. USDC and USDT are the two largest. Stablecoins are tokens issued on existing chains: on Ethereum, Polygon, Base, and Arbitrum they follow the ",[133,9136,9139],{"href":9137,"rel":9138},"https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-20",[137],"ERC-20 token standard",", and on Solana, Stellar, and Tron they follow each network's own token model.",[18,9142,9144],{"id":9143},"what-can-a-wallet-integration-do-inside-a-fintech-product","What can a wallet integration do inside a fintech product?",[11,9146,9147],{},"A wallet integration gives a product four capabilities: store a balance, send it, receive it, and convert it to and from local currency. Most fintech use cases combine those four, applied to stablecoins rather than volatile crypto assets.",[23,9149,9150,9163],{},[26,9151,9152],{},[29,9153,9154,9157,9160],{},[32,9155,9156],{},"Capability",[32,9158,9159],{},"What it means",[32,9161,9162],{},"Example in a product",[42,9164,9165,9175,9185,9195],{},[29,9166,9167,9169,9172],{},[47,9168,3727],{},[47,9170,9171],{},"Hold a stablecoin balance at a wallet address",[47,9173,9174],{},"A dollar balance for a freelancer in Argentina",[29,9176,9177,9179,9182],{},[47,9178,3749],{},[47,9180,9181],{},"Sign and broadcast a transfer to another address",[47,9183,9184],{},"Paying a supplier's wallet in USDT",[29,9186,9187,9189,9192],{},[47,9188,3738],{},[47,9190,9191],{},"Detect incoming transfers and credit them",[47,9193,9194],{},"A marketplace collecting USDC from buyers",[29,9196,9197,9200,9203],{},[47,9198,9199],{},"Convert",[47,9201,9202],{},"Turn bank money into stablecoins and back",[47,9204,9205],{},"Payroll funded by ACH, paid out over Pix",[11,9207,9208,9209,9212,9213,9215,9216,9219],{},"The fourth capability is the one teams underestimate. Converting bank money into stablecoins is called an ",[150,9210,9211],{},"on-ramp",". Converting stablecoins back into bank money is called an ",[150,9214,2168],{},". A wallet does neither on its own: it holds tokens and never touches a bank account. On-ramps and off-ramps need banking partners, liquidity, and licenses, which is why they usually come from a separate provider. ",[133,9217,9218],{"href":1283},"What is a stablecoin API"," explains that layer.",[11,9221,9222,9223,9225],{},"Multi-chain support adds another dimension. The same stablecoin exists on several networks, and each network has its own address format, fees, and confirmation times. A user who sends USDC on Solana to an address your product only watches on Ethereum has sent it somewhere your system will never see. ",[133,9224,201],{"href":200}," walks through what each network does during a transfer.",[18,9227,9229],{"id":9228},"what-are-the-main-components-of-a-wallet-integration","What are the main components of a wallet integration?",[11,9231,9232],{},"A wallet integration has six components: key management, chain connectivity, transaction signing, balance and transaction monitoring, compliance hooks, and the user interface. A wallet provider usually covers the first four. Compliance and the interface stay with you, even when a vendor supplies parts of them.",[23,9234,9235,9247],{},[26,9236,9237],{},[29,9238,9239,9242,9244],{},[32,9240,9241],{},"Component",[32,9243,5255],{},[32,9245,9246],{},"Usually provided by",[42,9248,9249,9260,9271,9282,9293,9304],{},[29,9250,9251,9254,9257],{},[47,9252,9253],{},"Key management",[47,9255,9256],{},"Generates, stores, and protects private keys, or splits them into shares",[47,9258,9259],{},"Wallet provider, or the user's own device",[29,9261,9262,9265,9268],{},[47,9263,9264],{},"Chain connectivity",[47,9266,9267],{},"Reads blockchain state and broadcasts transactions through RPC nodes",[47,9269,9270],{},"Wallet provider or a node provider",[29,9272,9273,9276,9279],{},[47,9274,9275],{},"Transaction signing",[47,9277,9278],{},"Produces the signature that authorizes a transfer, under rules you set",[47,9280,9281],{},"Wallet provider, with your policies",[29,9283,9284,9287,9290],{},[47,9285,9286],{},"Balance and transaction monitoring",[47,9288,9289],{},"Tracks balances, incoming transfers, and confirmations, then emits webhooks",[47,9291,9292],{},"Wallet provider or an indexer",[29,9294,9295,9298,9301],{},[47,9296,9297],{},"Compliance hooks",[47,9299,9300],{},"Verifies users, screens wallet addresses, monitors transactions",[47,9302,9303],{},"You, plus compliance vendors",[29,9305,9306,9309,9312],{},[47,9307,9308],{},"User interface",[47,9310,9311],{},"Shows balances, addresses, confirmations, and errors",[47,9313,9314],{},"You",[11,9316,9317],{},"Three terms from that table, defined once:",[144,9319,9320,9326,9332],{},[147,9321,9322,9325],{},[150,9323,9324],{},"RPC node",": a server that exposes a blockchain's data and accepts new transactions over an API. Every balance read and every broadcast goes through one.",[147,9327,9328,9331],{},[150,9329,9330],{},"Signing policy",": rules that decide whether a transaction may be signed, such as amount limits, allowlisted destinations, or a second approver.",[147,9333,9334,9337],{},[150,9335,9336],{},"Confirmation",": the point at which a transaction is included in a block. Finality, the point after which it can't be reversed, arrives later on some chains.",[11,9339,9340],{},"Key management is where the risk concentrates. A leaked key means lost funds with no chargeback. A lost key means a balance nobody can move. That's why the custody decision comes before any code.",[18,9342,9344],{"id":9343},"what-are-the-three-ways-to-integrate-a-wallet","What are the three ways to integrate a wallet?",[11,9346,9347],{},"There are three integration models: a wallet API, an embedded wallet SDK, and a white-label wallet. They differ in how much of the product you build yourself, and how much control you keep over keys, user experience, and data.",[11,9349,2183,9350,9353],{},[150,9351,9352],{},"wallet API"," is a set of backend endpoints for creating wallets, reading balances, and requesting signatures. Your server calls the provider, and you build every screen. A wallet API gives the most control and takes the most engineering.",[11,9355,4693,9356,9359],{},[150,9357,9358],{},"embedded wallet SDK"," is a client library that creates a wallet for each user inside your web or mobile app, often tied to an email, social, or passkey login. The user never installs a separate wallet app. You get prebuilt onboarding and signing flows, with less control over how they look and behave.",[11,9361,2183,9362,9365],{},[150,9363,9364],{},"white-label wallet"," is a complete wallet application, branded as yours and run by the provider. A white-label wallet is the fastest route to launch and gives the least control over the product and the roadmap.",[23,9367,9368,9380],{},[26,9369,9370],{},[29,9371,9372,9374,9376,9378],{},[32,9373],{},[32,9375,7073],{},[32,9377,7084],{},[32,9379,7095],{},[42,9381,9382,9396,9410,9422],{},[29,9383,9384,9387,9390,9393],{},[47,9385,9386],{},"Control",[47,9388,9389],{},"Full control of UX and data",[47,9391,9392],{},"Your app, prebuilt wallet flows",[47,9394,9395],{},"Branding and configuration only",[29,9397,9398,9401,9404,9407],{},[47,9399,9400],{},"Speed to launch",[47,9402,9403],{},"Slowest",[47,9405,9406],{},"Middle",[47,9408,9409],{},"Fastest",[29,9411,9412,9414,9417,9420],{},[47,9413,7268],{},[47,9415,9416],{},"Shared: you own policies and backend security",[47,9418,9419],{},"Shared: provider owns key flows, you own the app",[47,9421,7277],{},[29,9423,9424,9426,9429,9432],{},[47,9425,2391],{},[47,9427,9428],{},"Fintechs with an engineering team and custom flows",[47,9430,9431],{},"Consumer apps that want wallets without wallet apps",[47,9433,9434],{},"Teams testing demand before investing",[11,9436,9437],{},"Many products mix models: an embedded SDK for end users, and a wallet API for the company's own treasury wallets.",[18,9439,9441],{"id":9440},"who-holds-the-private-keys","Who holds the private keys?",[11,9443,9444,9445,9448,9449,9452,9453,9456],{},"Every wallet integration picks a custody model, and there are three. In a ",[150,9446,9447],{},"custodial"," model the provider or your company holds the keys. In a ",[150,9450,9451],{},"non-custodial"," model only the user holds them. In an ",[150,9454,9455],{},"MPC"," model the key is split into shares held by different parties, and no single party can sign alone.",[11,9458,9459,9460,9465],{},"MPC stands for multi-party computation, a family of cryptographic techniques that let several parties produce one valid signature without ever assembling the full key. NIST runs a ",[133,9461,9464],{"href":9462,"rel":9463},"https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fthreshold-cryptography",[137],"Multi-Party Threshold Cryptography project"," to standardize these schemes. MPC is a key-management technique more than a custody model: who holds the shares decides whether an MPC wallet is custodial.",[11,9467,9468,9469,9474,9475,9477],{},"The custody choice has legal weight. FinCEN's ",[133,9470,9473],{"href":9471,"rel":9472},"https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-certain-business-models",[137],"2019 guidance on convertible virtual currency"," (FIN-2019-G001) treats hosted wallet providers, which receive, store, and transmit value on behalf of account holders, as money transmitters. A person using an unhosted wallet to buy goods or services for themselves is not one. Rules differ by country, so confirm your model with counsel. ",[133,9476,3338],{"href":3337}," covers the same question for payment providers.",[18,9479,9481],{"id":9480},"how-long-does-a-wallet-integration-take-and-what-does-it-cost","How long does a wallet integration take and what does it cost?",[11,9483,9484],{},"There's no reliable public benchmark for wallet integration timelines or costs, and vendor quotes depend on volume and contract terms. What drives both is predictable, though. Five factors set the scope:",[289,9486,9487,9493,9499,9505,9510],{},[147,9488,9489,9492],{},[150,9490,9491],{},"Authentication model."," Tying wallets to your existing login (email, passkeys, social) takes more work than a standalone wallet, and it decides how account recovery works.",[147,9494,9495,9498],{},[150,9496,9497],{},"Number of chains."," Each chain adds an address format, a fee model, confirmation logic, and test coverage. One or two chains keep the first release small.",[147,9500,9501,9504],{},[150,9502,9503],{},"Custody choice."," Custodial and MPC setups need signing policies, approval flows, and operating procedures. Non-custodial setups need recovery and support flows for users who lose access.",[147,9506,9507,9509],{},[150,9508,8214],{}," User verification, address screening, transaction monitoring, and the Travel Rule each add an integration and a review queue. Moving money for others also raises the licensing question.",[147,9511,9512,9515],{},[150,9513,9514],{},"Fiat connectivity."," On-ramps and off-ramps add banking rails, quotes, and payout states on top of the wallet work.",[11,9517,9518,9519,9522],{},"On cost, expect a mix of platform fees, per-wallet or per-transaction fees from the wallet provider, network gas fees on every on-chain transaction, and conversion fees whenever money crosses between bank accounts and stablecoins. Ask each vendor for pricing in writing against your own projected volume. ",[133,9520,9521],{"href":7420},"Build vs buy"," walks through what the in-house version costs in people and time.",[18,9524,2407],{"id":2406},[11,9526,9527],{},"BlindPay is the payments layer around a wallet, not the wallet itself. It connects wallets to bank accounts: virtual accounts that turn bank deposits into USDC or USDT, on-ramps and off-ramps, live quotes, and payouts to local rails. It works alongside wallet infrastructure providers such as Fireblocks, Circle, Privy, Dfns, and Utila instead of replacing them.",[11,9529,9530,9531,9533],{},"A customer's existing wallet is registered with BlindPay as a ",[133,9532,3088],{"href":3087},", either by signing a message or by submitting the address directly. From there:",[144,9535,9536,9541,9544],{},[147,9537,2183,9538,9540],{},[133,9539,7382],{"href":2926}," gives the customer US bank details. Each deposit converts to USDC or USDT and settles to the linked wallet, and each deposit is tracked as a payin.",[147,9542,9543],{},"A payout pulls stablecoins from that wallet only after the customer authorizes the quoted amount, then sends local currency over Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), and other rails. BlindPay never holds the keys to an external wallet, so that payout flow is non-custodial.",[147,9545,9546],{},"For teams that don't want to run signing, BlindPay also offers managed wallets, in beta, which it custodies on the customer's behalf.",[11,9548,9549],{},"BlindPay is registered with FinCEN as a money services business. It is not a stablecoin issuer, a card acquirer, a consumer wallet app, or a key-management platform. If your main need is key custody for thousands of end users, a wallet infrastructure provider is the right first call, and BlindPay can sit behind it for the bank side.",[18,9551,9553],{"id":9552},"glossary-8-terms-youll-see-in-every-wallet-integration","Glossary: 8 terms you'll see in every wallet integration",[23,9555,9556,9566],{},[26,9557,9558],{},[29,9559,9560,9563],{},[32,9561,9562],{},"Term",[32,9564,9565],{},"Plain-language definition",[42,9567,9568,9576,9584,9592,9600,9608,9620,9628],{},[29,9569,9570,9573],{},[47,9571,9572],{},"Private key",[47,9574,9575],{},"The secret number that authorizes transfers from a wallet address",[29,9577,9578,9581],{},[47,9579,9580],{},"Wallet address",[47,9582,9583],{},"The public identifier that receives tokens, derived from the key",[29,9585,9586,9589],{},[47,9587,9588],{},"Custodial wallet",[47,9590,9591],{},"A wallet whose keys a company holds on the user's behalf",[29,9593,9594,9597],{},[47,9595,9596],{},"Non-custodial wallet",[47,9598,9599],{},"A wallet whose keys only the user holds",[29,9601,9602,9605],{},[47,9603,9604],{},"MPC wallet",[47,9606,9607],{},"A wallet whose key is split into shares, so no single party can sign alone",[29,9609,9610,9613],{},[47,9611,9612],{},"Account abstraction",[47,9614,9615,9616,9619],{},"A wallet that is a smart contract with programmable rules; ",[133,9617,7153],{"href":7151,"rel":9618},[137]," is the main Ethereum standard",[29,9621,9622,9625],{},[47,9623,9624],{},"On-ramp and off-ramp",[47,9626,9627],{},"Converting bank money into stablecoins, and stablecoins back into bank money",[29,9629,9630,9633],{},[47,9631,9632],{},"KYT",[47,9634,9635],{},"Know your transaction: monitoring transfers and wallet addresses for risk",[18,9637,2829],{"id":2828},[11,9639,9640],{},"Write down three answers before you talk to vendors: which chains and stablecoins you need at launch, who should hold the keys, and whether money has to reach bank accounts. Those three choices narrow the vendor list faster than any feature comparison.",[11,9642,9643,9644,9646,9647,9649],{},"If bank accounts are part of the answer, read ",[133,9645,7503],{"href":7502}," end to end. Then open the ",[133,9648,7449],{"href":3087}," to see what linking an existing wallet to payins and payouts takes.",{"title":519,"searchDepth":520,"depth":520,"links":9651},[9652,9653,9654,9655,9656,9657,9658,9659,9660],{"id":9124,"depth":520,"text":9125},{"id":9143,"depth":520,"text":9144},{"id":9228,"depth":520,"text":9229},{"id":9343,"depth":520,"text":9344},{"id":9440,"depth":520,"text":9441},{"id":9480,"depth":520,"text":9481},{"id":2406,"depth":520,"text":2407},{"id":9552,"depth":520,"text":9553},{"id":2828,"depth":520,"text":2829},"2026-08-17","Crypto wallet integration adds wallets, key custody, signing, and compliance to an app. The six components, three integration models, and cost drivers.",[9664,9666,9668,9671,9674,9677],{"q":9125,"a":9665},"Crypto wallet integration adds blockchain wallet functions to an existing app: creating or linking wallets, controlling the private keys, signing transactions, tracking balances, and screening transfers. Most teams plug in a wallet provider through a wallet API, an embedded SDK, or a white-label app instead of building key management themselves.",{"q":9229,"a":9667},"Six components: key management, chain connectivity through RPC nodes, transaction signing under policies you define, balance and transaction monitoring, compliance hooks such as address screening, and the user interface. A wallet provider usually covers the first four. Compliance decisions and the interface stay with your team, even when vendors supply parts of them.",{"q":9669,"a":9670},"Do I need a license to add crypto wallets to my app?","It depends on the custody model and the country. In the US, FinCEN's 2019 guidance treats hosted wallet providers that store and transmit value for users as money transmitters, while a person using an unhosted wallet for their own purchases is not one. Working with a registered provider can change your exposure. Confirm your setup with counsel.",{"q":9672,"a":9673},"Which blockchains should a wallet integration support first?","Start with the networks your first customers and counterparties already use, and keep the first release to one or two chains. Each extra chain adds an address format, a fee model, confirmation logic, and test coverage. Ask your first ten customers which network and stablecoin they hold today, and build for that.",{"q":9675,"a":9676},"Can I add stablecoin payments without building a wallet?","Yes. A payments API with virtual accounts and payouts can convert bank deposits into stablecoins, deliver them to a wallet, and pay out to bank accounts. The customer can use a wallet they already have, or a managed wallet the provider custodies. A wallet still exists somewhere in the flow. You just don't have to build it.",{"q":9678,"a":9679},"Does BlindPay provide crypto wallets?","BlindPay is the payments layer, not a wallet provider. It links a customer's existing wallet to payins and payouts without holding its keys, and offers managed wallets in beta for teams that want BlindPay to custody the balance. For key management at scale, BlindPay works alongside wallet infrastructure providers such as Fireblocks, Circle, and Privy.",{"author":555},"---\ntitle: \"What is crypto wallet integration? A developer's guide\"\nseoTitle: \"What is crypto wallet integration? A developer's guide\"\ndescription: \"Crypto wallet integration adds wallets, key custody, signing, and compliance to an app. The six components, three integration models, and cost drivers.\"\ndate: \"2026-08-17\"\nupdated: \"2026-08-17\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is crypto wallet integration?\"\n    a: \"Crypto wallet integration adds blockchain wallet functions to an existing app: creating or linking wallets, controlling the private keys, signing transactions, tracking balances, and screening transfers. Most teams plug in a wallet provider through a wallet API, an embedded SDK, or a white-label app instead of building key management themselves.\"\n  - q: \"What are the main components of a wallet integration?\"\n    a: \"Six components: key management, chain connectivity through RPC nodes, transaction signing under policies you define, balance and transaction monitoring, compliance hooks such as address screening, and the user interface. A wallet provider usually covers the first four. Compliance decisions and the interface stay with your team, even when vendors supply parts of them.\"\n  - q: \"Do I need a license to add crypto wallets to my app?\"\n    a: \"It depends on the custody model and the country. In the US, FinCEN's 2019 guidance treats hosted wallet providers that store and transmit value for users as money transmitters, while a person using an unhosted wallet for their own purchases is not one. Working with a registered provider can change your exposure. Confirm your setup with counsel.\"\n  - q: \"Which blockchains should a wallet integration support first?\"\n    a: \"Start with the networks your first customers and counterparties already use, and keep the first release to one or two chains. Each extra chain adds an address format, a fee model, confirmation logic, and test coverage. Ask your first ten customers which network and stablecoin they hold today, and build for that.\"\n  - q: \"Can I add stablecoin payments without building a wallet?\"\n    a: \"Yes. A payments API with virtual accounts and payouts can convert bank deposits into stablecoins, deliver them to a wallet, and pay out to bank accounts. The customer can use a wallet they already have, or a managed wallet the provider custodies. A wallet still exists somewhere in the flow. You just don't have to build it.\"\n  - q: \"Does BlindPay provide crypto wallets?\"\n    a: \"BlindPay is the payments layer, not a wallet provider. It links a customer's existing wallet to payins and payouts without holding its keys, and offers managed wallets in beta for teams that want BlindPay to custody the balance. For key management at scale, BlindPay works alongside wallet infrastructure providers such as Fireblocks, Circle, and Privy.\"\n---\n\nCrypto wallet integration is the work of adding blockchain wallet functions to a product you already run: creating or connecting wallets, deciding who holds the private keys, signing transactions, reading balances, and screening transfers before they move. Most teams don't build this layer themselves. They plug in a wallet provider through an API, an embedded SDK, or a white-label app.\n\nThis guide is for developers and product managers at the start of that project. It assumes you know REST APIs and webhooks, and not much about blockchains.\n\n## What is crypto wallet integration?\n\nCrypto wallet integration connects your application to wallets on one or more blockchains, so your users can hold, send, and receive digital assets inside your product. In practice it means wiring four things into your stack: a way to create or link wallets, a way to control their keys, a way to sign and broadcast transactions, and a way to watch what happens on-chain.\n\nA crypto wallet doesn't contain coins. A wallet is a private key plus the public address derived from it. The tokens live on the blockchain's ledger, and whoever controls the private key can move whatever that address holds. That one fact drives most design decisions in a wallet integration: who holds the key, who can sign, and what happens when a key is lost.\n\nFor fintech products the asset is usually a stablecoin, a token that tracks a currency like the US dollar. USDC and USDT are the two largest. Stablecoins are tokens issued on existing chains: on Ethereum, Polygon, Base, and Arbitrum they follow the [ERC-20 token standard](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-20), and on Solana, Stellar, and Tron they follow each network's own token model.\n\n## What can a wallet integration do inside a fintech product?\n\nA wallet integration gives a product four capabilities: store a balance, send it, receive it, and convert it to and from local currency. Most fintech use cases combine those four, applied to stablecoins rather than volatile crypto assets.\n\n| Capability | What it means | Example in a product |\n| --- | --- | --- |\n| Store | Hold a stablecoin balance at a wallet address | A dollar balance for a freelancer in Argentina |\n| Send | Sign and broadcast a transfer to another address | Paying a supplier's wallet in USDT |\n| Receive | Detect incoming transfers and credit them | A marketplace collecting USDC from buyers |\n| Convert | Turn bank money into stablecoins and back | Payroll funded by ACH, paid out over Pix |\n\nThe fourth capability is the one teams underestimate. Converting bank money into stablecoins is called an **on-ramp**. Converting stablecoins back into bank money is called an **off-ramp**. A wallet does neither on its own: it holds tokens and never touches a bank account. On-ramps and off-ramps need banking partners, liquidity, and licenses, which is why they usually come from a separate provider. [What is a stablecoin API](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api) explains that layer.\n\nMulti-chain support adds another dimension. The same stablecoin exists on several networks, and each network has its own address format, fees, and confirmation times. A user who sends USDC on Solana to an address your product only watches on Ethereum has sent it somewhere your system will never see. [What happens on-chain in a stablecoin payment](\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment) walks through what each network does during a transfer.\n\n## What are the main components of a wallet integration?\n\nA wallet integration has six components: key management, chain connectivity, transaction signing, balance and transaction monitoring, compliance hooks, and the user interface. A wallet provider usually covers the first four. Compliance and the interface stay with you, even when a vendor supplies parts of them.\n\n| Component | What it does | Usually provided by |\n| --- | --- | --- |\n| Key management | Generates, stores, and protects private keys, or splits them into shares | Wallet provider, or the user's own device |\n| Chain connectivity | Reads blockchain state and broadcasts transactions through RPC nodes | Wallet provider or a node provider |\n| Transaction signing | Produces the signature that authorizes a transfer, under rules you set | Wallet provider, with your policies |\n| Balance and transaction monitoring | Tracks balances, incoming transfers, and confirmations, then emits webhooks | Wallet provider or an indexer |\n| Compliance hooks | Verifies users, screens wallet addresses, monitors transactions | You, plus compliance vendors |\n| User interface | Shows balances, addresses, confirmations, and errors | You |\n\nThree terms from that table, defined once:\n\n- **RPC node**: a server that exposes a blockchain's data and accepts new transactions over an API. Every balance read and every broadcast goes through one.\n- **Signing policy**: rules that decide whether a transaction may be signed, such as amount limits, allowlisted destinations, or a second approver.\n- **Confirmation**: the point at which a transaction is included in a block. Finality, the point after which it can't be reversed, arrives later on some chains.\n\nKey management is where the risk concentrates. A leaked key means lost funds with no chargeback. A lost key means a balance nobody can move. That's why the custody decision comes before any code.\n\n## What are the three ways to integrate a wallet?\n\nThere are three integration models: a wallet API, an embedded wallet SDK, and a white-label wallet. They differ in how much of the product you build yourself, and how much control you keep over keys, user experience, and data.\n\nA **wallet API** is a set of backend endpoints for creating wallets, reading balances, and requesting signatures. Your server calls the provider, and you build every screen. A wallet API gives the most control and takes the most engineering.\n\nAn **embedded wallet SDK** is a client library that creates a wallet for each user inside your web or mobile app, often tied to an email, social, or passkey login. The user never installs a separate wallet app. You get prebuilt onboarding and signing flows, with less control over how they look and behave.\n\nA **white-label wallet** is a complete wallet application, branded as yours and run by the provider. A white-label wallet is the fastest route to launch and gives the least control over the product and the roadmap.\n\n| | Wallet API | Embedded SDK | White-label |\n| --- | --- | --- | --- |\n| Control | Full control of UX and data | Your app, prebuilt wallet flows | Branding and configuration only |\n| Speed to launch | Slowest | Middle | Fastest |\n| Security responsibility | Shared: you own policies and backend security | Shared: provider owns key flows, you own the app | Mostly the provider |\n| Best for | Fintechs with an engineering team and custom flows | Consumer apps that want wallets without wallet apps | Teams testing demand before investing |\n\nMany products mix models: an embedded SDK for end users, and a wallet API for the company's own treasury wallets.\n\n## Who holds the private keys?\n\nEvery wallet integration picks a custody model, and there are three. In a **custodial** model the provider or your company holds the keys. In a **non-custodial** model only the user holds them. In an **MPC** model the key is split into shares held by different parties, and no single party can sign alone.\n\nMPC stands for multi-party computation, a family of cryptographic techniques that let several parties produce one valid signature without ever assembling the full key. NIST runs a [Multi-Party Threshold Cryptography project](https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fthreshold-cryptography) to standardize these schemes. MPC is a key-management technique more than a custody model: who holds the shares decides whether an MPC wallet is custodial.\n\nThe custody choice has legal weight. FinCEN's [2019 guidance on convertible virtual currency](https:\u002F\u002Fwww.fincen.gov\u002Fresources\u002Fstatutes-regulations\u002Fguidance\u002Fapplication-fincens-regulations-certain-business-models) (FIN-2019-G001) treats hosted wallet providers, which receive, store, and transmit value on behalf of account holders, as money transmitters. A person using an unhosted wallet to buy goods or services for themselves is not one. Rules differ by country, so confirm your model with counsel. [Non-custodial payments explained](\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained) covers the same question for payment providers.\n\n## How long does a wallet integration take and what does it cost?\n\nThere's no reliable public benchmark for wallet integration timelines or costs, and vendor quotes depend on volume and contract terms. What drives both is predictable, though. Five factors set the scope:\n\n1. **Authentication model.** Tying wallets to your existing login (email, passkeys, social) takes more work than a standalone wallet, and it decides how account recovery works.\n2. **Number of chains.** Each chain adds an address format, a fee model, confirmation logic, and test coverage. One or two chains keep the first release small.\n3. **Custody choice.** Custodial and MPC setups need signing policies, approval flows, and operating procedures. Non-custodial setups need recovery and support flows for users who lose access.\n4. **Compliance scope.** User verification, address screening, transaction monitoring, and the Travel Rule each add an integration and a review queue. Moving money for others also raises the licensing question.\n5. **Fiat connectivity.** On-ramps and off-ramps add banking rails, quotes, and payout states on top of the wallet work.\n\nOn cost, expect a mix of platform fees, per-wallet or per-transaction fees from the wallet provider, network gas fees on every on-chain transaction, and conversion fees whenever money crosses between bank accounts and stablecoins. Ask each vendor for pricing in writing against your own projected volume. [Build vs buy](\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments) walks through what the in-house version costs in people and time.\n\n## Where does BlindPay fit?\n\nBlindPay is the payments layer around a wallet, not the wallet itself. It connects wallets to bank accounts: virtual accounts that turn bank deposits into USDC or USDT, on-ramps and off-ramps, live quotes, and payouts to local rails. It works alongside wallet infrastructure providers such as Fireblocks, Circle, Privy, Dfns, and Utila instead of replacing them.\n\nA customer's existing wallet is registered with BlindPay as a [blockchain wallet](\u002Fdocs\u002Fblockchain-wallets), either by signing a message or by submitting the address directly. From there:\n\n- A [virtual account](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained) gives the customer US bank details. Each deposit converts to USDC or USDT and settles to the linked wallet, and each deposit is tracked as a payin.\n- A payout pulls stablecoins from that wallet only after the customer authorizes the quoted amount, then sends local currency over Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO\u002FCOBO), and other rails. BlindPay never holds the keys to an external wallet, so that payout flow is non-custodial.\n- For teams that don't want to run signing, BlindPay also offers managed wallets, in beta, which it custodies on the customer's behalf.\n\nBlindPay is registered with FinCEN as a money services business. It is not a stablecoin issuer, a card acquirer, a consumer wallet app, or a key-management platform. If your main need is key custody for thousands of end users, a wallet infrastructure provider is the right first call, and BlindPay can sit behind it for the bank side.\n\n## Glossary: 8 terms you'll see in every wallet integration\n\n| Term | Plain-language definition |\n| --- | --- |\n| Private key | The secret number that authorizes transfers from a wallet address |\n| Wallet address | The public identifier that receives tokens, derived from the key |\n| Custodial wallet | A wallet whose keys a company holds on the user's behalf |\n| Non-custodial wallet | A wallet whose keys only the user holds |\n| MPC wallet | A wallet whose key is split into shares, so no single party can sign alone |\n| Account abstraction | A wallet that is a smart contract with programmable rules; [ERC-4337](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-4337) is the main Ethereum standard |\n| On-ramp and off-ramp | Converting bank money into stablecoins, and stablecoins back into bank money |\n| KYT | Know your transaction: monitoring transfers and wallet addresses for risk |\n\n## What to do next\n\nWrite down three answers before you talk to vendors: which chains and stablecoins you need at launch, who should hold the keys, and whether money has to reach bank accounts. Those three choices narrow the vendor list faster than any feature comparison.\n\nIf bank accounts are part of the answer, read [how a stablecoin payment works](\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works) end to end. Then open the [blockchain wallet docs](\u002Fdocs\u002Fblockchain-wallets) to see what linking an existing wallet to payins and payouts takes.\n",{"title":9113,"description":9662},"resources\u002Fmore\u002Fwhat-is-crypto-wallet-integration","u3uMmXk7s95fbZKAn7BWDoS8-kUn78ILM3hSAl0DNqU",{"id":9686,"title":9687,"authors":6,"body":9688,"categories":6,"category":533,"categoryType":6,"compare":6,"contributors":6,"date":10103,"description":10104,"extension":536,"faq":10105,"howto":6,"isBlog":553,"isChangelog":553,"meta":10118,"navigation":556,"path":1813,"pillar":553,"products":6,"rawbody":10119,"role":6,"seo":10120,"seoTitle":10107,"stem":10121,"thumbnail":6,"updated":2152,"__hash__":10122},"content\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing.md","What is stablecoin card issuing? How it works, who uses it, and how it differs from crypto debit cards",{"type":8,"value":9689,"toc":10091},[9690,9695,9700,9703,9706,9710,9713,9739,9743,9746,9760,9763,9767,9770,9773,9777,9780,9856,9867,9871,9874,9881,9885,9888,9980,9987,9994,9998,10001,10033,10038,10042,10045,10054,10060,10066,10068,10087],[11,9691,9692],{},[1210,9693,9694],{},"Reading time: about 7 minutes.",[11,9696,9697,9699],{},[150,9698,1803],{}," Stablecoin card issuing is issuing Visa or Mastercard debit, prepaid, or virtual cards whose spending balance is held in a dollar stablecoin such as USDC or USDT instead of a bank deposit. When the cardholder pays, the card program converts the stablecoin to fiat, and the merchant is paid in local currency over the normal card network.",[11,9701,9702],{},"The card itself is ordinary. Same chip, same Apple Pay button, same decline codes. What changes is the balance behind it and one conversion step that happens either at authorization or at settlement.",[11,9704,9705],{},"This explainer covers the mechanics, the companies in the stack, and the use cases. It is a reference, not a pitch.",[18,9707,9709],{"id":9708},"how-does-a-stablecoin-backed-debit-card-work","How does a stablecoin-backed debit card work?",[11,9711,9712],{},"Every card transaction runs in two phases: authorization at checkout, which takes seconds, and clearing and settlement, which usually happens the next business day. A stablecoin card program hooks into both.",[289,9714,9715,9721,9727,9733],{},[147,9716,9717,9720],{},[150,9718,9719],{},"Authorization."," The cardholder taps. The merchant's acquirer sends the request through Visa or Mastercard to the issuer processor, which asks the program one question: can this card pay? The program checks the cardholder's stablecoin balance, converts the amount at the current rate, places a hold, and approves or declines. The whole round trip has a few seconds, so the balance check reads from a ledger, not from a fresh blockchain confirmation.",[147,9722,9723,9726],{},[150,9724,9725],{},"Clearing."," The merchant submits the final amount. It can differ from the authorized one (a restaurant tip, a hotel's incidentals, a fuel pre-authorization), so the program adjusts the hold.",[147,9728,9729,9732],{},[150,9730,9731],{},"Settlement."," The network nets the day's transactions and moves money between issuers and acquirers. The issuer owes the network for its cardholders' purchases, and the program has to fund that. It either sells stablecoins for dollars through a liquidity partner or, where the network allows it, pays in USDC.",[147,9734,9735,9738],{},[150,9736,9737],{},"Merchant payout."," The acquirer pays the merchant in local currency on its normal schedule. The merchant has no idea a stablecoin was involved.",[1108,9740,9742],{"id":9741},"real-time-vs-batch-conversion","Real-time vs. batch conversion",[11,9744,9745],{},"Programs pick one of two funding models, and the choice decides who carries the rate risk.",[144,9747,9748,9754],{},[147,9749,9750,9753],{},[150,9751,9752],{},"Just-in-time conversion."," The stablecoin stays in the cardholder's wallet until a purchase happens, and the amount is reserved at authorization. The cardholder keeps the full balance in USDC or USDT until they spend it. The program carries a small exposure between authorization and settlement.",[147,9755,9756,9759],{},[150,9757,9758],{},"Pre-converted balance."," The cardholder or business loads a fiat card balance from stablecoins in advance. Simpler for the issuer, but the money sits in fiat until it is spent, which defeats part of the point.",[11,9761,9762],{},"For a USD card funded with USDC, the exposure is small because both sides are dollars. It grows when the card currency differs from the stablecoin, for example a euro card funded with USDC.",[1108,9764,9766],{"id":9765},"stablecoin-settlement-at-the-network-level","Stablecoin settlement at the network level",[11,9768,9769],{},"The networks now accept stablecoins on the settlement leg itself. Visa lets US issuer and acquirer partners settle in USDC, starting with Cross River Bank and Lead Bank over Solana. Mastercard announced in June 2026 that it would support settlement in USDC, PYUSD, RLUSD, and other regulated stablecoins across several blockchains, with intraday, weekend, and holiday cycles.",[11,9771,9772],{},"What this changes: an issuer can meet its settlement obligation on a Saturday without waiting for a bank wire window. What it does not change: anything the cardholder or merchant sees.",[18,9774,9776],{"id":9775},"stablecoin-card-vs-crypto-debit-card-whats-the-difference","Stablecoin card vs. crypto debit card: what's the difference?",[11,9778,9779],{},"The first crypto cards were a way to spend an exchange balance. You held bitcoin at an exchange, the exchange issued a card, and every swipe sold a little bitcoin. Stablecoin cards use the same plumbing with a different asset, and that one change affects budgeting, tax, and who uses them.",[23,9781,9782,9792],{},[26,9783,9784],{},[29,9785,9786,9788,9790],{},[32,9787,1855],{},[32,9789,1858],{},[32,9791,1861],{},[42,9793,9794,9804,9815,9824,9834,9845],{},[29,9795,9796,9798,9801],{},[47,9797,1868],{},[47,9799,9800],{},"Bitcoin, ether, or an exchange balance",[47,9802,9803],{},"A dollar stablecoin such as USDC or USDT",[29,9805,9806,9809,9812],{},[47,9807,9808],{},"Balance needed for a USD 100 purchase",[47,9810,9811],{},"Changes with the market",[47,9813,9814],{},"USD 100 plus fees",[29,9816,9817,9819,9821],{},[47,9818,1912],{},[47,9820,1915],{},[47,9822,9823],{},"A program wallet, or a self-custody wallet with a spending allowance, depending on the program",[29,9825,9826,9828,9831],{},[47,9827,1890],{},[47,9829,9830],{},"Sale of property, realizing a gain or loss",[47,9832,9833],{},"Also a disposal, but the gain is usually close to zero",[29,9835,9836,9839,9842],{},[47,9837,9838],{},"Typical user",[47,9840,9841],{},"Consumers spending crypto holdings",[47,9843,9844],{},"Businesses, contractors, platforms paying people abroad, consumers holding dollars",[29,9846,9847,9850,9853],{},[47,9848,9849],{},"Network settlement",[47,9851,9852],{},"Fiat, after the asset is sold",[47,9854,9855],{},"Fiat, or USDC where the network supports it",[11,9857,9858,9859,9862,9863,9866],{},"The ",[133,9860,9861],{"href":176},"USDC vs USDT comparison"," covers which stablecoin fits which program, and ",[133,9864,9865],{"href":1279},"what a stablecoin is"," covers the reserve model behind the peg.",[18,9868,9870],{"id":9869},"can-you-spend-usdc-or-usdt-directly-with-a-debit-card","Can you spend USDC or USDT directly with a debit card?",[11,9872,9873],{},"Not at the merchant. A coffee shop's terminal accepts Visa and Mastercard, not tokens. The card program does the conversion, so the cardholder experiences it as spending USDC and the merchant experiences it as a normal card payment in local currency.",[11,9875,9876,9877,9880],{},"A few merchants accept stablecoins directly through crypto payment processors. That is a different product: an on-chain transfer, with no card network, no chargeback rights, and ",[133,9878,9879],{"href":238},"no reversal"," once it confirms.",[18,9882,9884],{"id":9883},"who-are-the-main-players-in-stablecoin-card-issuing","Who are the main players in stablecoin card issuing?",[11,9886,9887],{},"A card program is a stack of companies, each with a regulated job. Stablecoin programs keep the same stack and add a funding layer.",[23,9889,9890,9901],{},[26,9891,9892],{},[29,9893,9894,9897,9899],{},[32,9895,9896],{},"Role",[32,9898,5255],{},[32,9900,4946],{},[42,9902,9903,9914,9925,9936,9947,9958,9969],{},[29,9904,9905,9908,9911],{},[47,9906,9907],{},"Card network",[47,9909,9910],{},"Sets the rules, routes authorizations, runs settlement",[47,9912,9913],{},"Visa, Mastercard",[29,9915,9916,9919,9922],{},[47,9917,9918],{},"Issuing bank or BIN sponsor",[47,9920,9921],{},"The legal issuer; owns the BIN range and the regulatory responsibility",[47,9923,9924],{},"Cross River Bank, Lead Bank, Pathward in the US; e-money institutions elsewhere",[29,9926,9927,9930,9933],{},[47,9928,9929],{},"Issuer processor",[47,9931,9932],{},"Runs authorizations, card lifecycle, and the card ledger",[47,9934,9935],{},"Marqeta, Lithic, Galileo",[29,9937,9938,9941,9944],{},[47,9939,9940],{},"Program manager",[47,9942,9943],{},"Owns the brand and the cardholder relationship, operates compliance under the sponsor's oversight",[47,9945,9946],{},"The fintech or platform whose name is on the card",[29,9948,9949,9952,9955],{},[47,9950,9951],{},"Stablecoin issuing platform",[47,9953,9954],{},"Bundles sponsor access, processing, and stablecoin wallet funding in one API",[47,9956,9957],{},"Rain, Bridge, Baanx, Reap",[29,9959,9960,9963,9966],{},[47,9961,9962],{},"Liquidity and ramps",[47,9964,9965],{},"Converts stablecoins to fiat for settlement and fiat to stablecoins for top-ups",[47,9967,9968],{},"BlindPay (stablecoin payouts over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), plus virtual USD accounts); other on-ramp and off-ramp providers",[29,9970,9971,9974,9977],{},[47,9972,9973],{},"Identity and monitoring",[47,9975,9976],{},"KYC, KYB, sanctions screening, transaction monitoring",[47,9978,9979],{},"Specialist vendors or in-house systems",[11,9981,9982,9983,9986],{},"The conversion providers in that stack are regulated too. Depending on the country they are a ",[133,9984,9985],{"href":9050},"VASP",", a money services business, or both.",[11,9988,9989,9990,9993],{},"A card is also one payout option among several. A company paying people abroad can issue a card, send money to a local bank account, or offer both. BlindPay handles the bank-account side: stablecoins out to local currency over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), and ",[133,9991,9992],{"href":1067},"virtual USD accounts"," that turn ACH or wire deposits into USDC or USDT.",[18,9995,9997],{"id":9996},"what-are-stablecoin-cards-used-for","What are stablecoin cards used for?",[11,9999,10000],{},"Five uses account for most programs.",[144,10002,10003,10009,10015,10021,10027],{},[147,10004,10005,10008],{},[150,10006,10007],{},"Contractor payouts."," A platform pays freelancers in USDC and gives them a card to spend it, so the contractor does not need a US bank account.",[147,10010,10011,10014],{},[150,10012,10013],{},"Marketplace and creator payouts."," Sellers and creators in dozens of countries get earnings on a card the day they are released, not after a weekly wire batch.",[147,10016,10017,10020],{},[150,10018,10019],{},"Treasury and team spend."," A company that holds its treasury in USDC issues corporate cards against it for software, ads, and travel.",[147,10022,10023,10026],{},[150,10024,10025],{},"Dollar access in high-inflation economies."," In Argentina, Turkey, or Nigeria, a USD stablecoin card is a way to hold dollars and spend them without a foreign bank account.",[147,10028,10029,10032],{},[150,10030,10031],{},"Travel and online spend."," A USD balance avoids some of the foreign exchange cost on USD-priced purchases.",[11,10034,9858,10035,10037],{},[133,10036,2102],{"href":2101}," guide goes country by country on the fourth use.",[18,10039,10041],{"id":10040},"what-a-stablecoin-card-does-not-change","What a stablecoin card does not change",[11,10043,10044],{},"Three things work the same as on any other card.",[11,10046,10047,10050,10051,10053],{},[150,10048,10049],{},"Identity checks."," Every cardholder passes KYC and every business program owner passes KYB, because the sponsor bank's anti-money-laundering program covers the program. The ",[133,10052,2112],{"href":2111}," covers who checks what.",[11,10055,10056,10059],{},[150,10057,10058],{},"Disputes."," Card network dispute rules apply to the card leg. A cardholder can still dispute a purchase. The on-chain transfer that funded the wallet cannot be reversed.",[11,10061,10062,10065],{},[150,10063,10064],{},"Fees."," Interchange, foreign transaction fees, and ATM fees still apply. Stablecoins remove cost on the funding side, not at the point of sale.",[18,10067,2091],{"id":2090},[11,10069,10070,10071,10074,10075,10077,10078,2103,10081,1567,10084,329],{},"This article is the first in a six-part series. Next, compare the two kinds of cards a company can hold in ",[133,10072,10073],{"href":2147},"crypto debit card vs. stablecoin card for business",". Then see ",[133,10076,2097],{"href":2064},", how programs work in ",[133,10079,10080],{"href":2101},"Latin America",[133,10082,10083],{"href":2106},"developer's guide to issuing cards through an API",[133,10085,10086],{"href":2111},"compliance for stablecoin card issuing",[11,10088,10089],{},[1210,10090,1212],{},{"title":519,"searchDepth":520,"depth":520,"links":10092},[10093,10097,10098,10099,10100,10101,10102],{"id":9708,"depth":520,"text":9709,"children":10094},[10095,10096],{"id":9741,"depth":1220,"text":9742},{"id":9765,"depth":1220,"text":9766},{"id":9775,"depth":520,"text":9776},{"id":9869,"depth":520,"text":9870},{"id":9883,"depth":520,"text":9884},{"id":9996,"depth":520,"text":9997},{"id":10040,"depth":520,"text":10041},{"id":2090,"depth":520,"text":2091},"2026-09-02","Stablecoin card issuing explained: how a USDC or USDT balance pays a card merchant in local currency, who runs each layer, and how it differs from a crypto debit card.",[10106,10109,10111,10114,10116],{"q":10107,"a":10108},"What is stablecoin card issuing?","Stablecoin card issuing is issuing Visa or Mastercard debit, prepaid, or virtual cards whose spending balance is held in a dollar stablecoin such as USDC or USDT instead of a bank deposit. When the cardholder pays, the card program converts the stablecoin to fiat, and the merchant is paid in local currency over the normal card network.",{"q":9709,"a":10110},"At checkout, the card network sends the authorization to the card program, which checks the cardholder's stablecoin balance, places a hold for the converted amount, and approves or declines within a few seconds. When the transaction clears, the program funds its settlement obligation by selling stablecoins for fiat or, where the network supports it, settling in USDC directly. The merchant is paid in its own currency and never touches a stablecoin.",{"q":10112,"a":10113},"What is the difference between a stablecoin card and a crypto debit card?","A crypto debit card sells a volatile asset such as bitcoin or ether at the moment of purchase, so the balance needed for the same purchase changes minute to minute. A stablecoin card spends a token pegged 1:1 to the US dollar, so the amount leaving the balance matches the price. In the US, selling a volatile asset at checkout also realizes a taxable gain or loss on every swipe, while spending a dollar stablecoin usually produces a gain close to zero.",{"q":9870,"a":10115},"Not directly at the merchant. Merchants accept Visa and Mastercard, not tokens, so a stablecoin card converts USDC or USDT into the transaction currency behind the scenes during authorization or settlement. From the cardholder's side it feels like spending USDC; from the merchant's side it is an ordinary card payment in local currency.",{"q":9884,"a":10117},"Card networks such as Visa and Mastercard route and settle transactions. A licensed bank or e-money institution acts as the issuer and BIN sponsor, an issuer processor such as Marqeta, Lithic, or Galileo runs authorizations, and a program manager owns the cardholder relationship. Stablecoin-native issuing platforms such as Rain, Bridge, Baanx, and Reap bundle several of those layers with stablecoin wallet funding.",{"author":555},"---\ntitle: \"What is stablecoin card issuing? How it works, who uses it, and how it differs from crypto debit cards\"\nseoTitle: \"What is stablecoin card issuing?\"\ndescription: \"Stablecoin card issuing explained: how a USDC or USDT balance pays a card merchant in local currency, who runs each layer, and how it differs from a crypto debit card.\"\ndate: \"2026-09-02\"\nupdated: \"2026-09-21\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is stablecoin card issuing?\"\n    a: \"Stablecoin card issuing is issuing Visa or Mastercard debit, prepaid, or virtual cards whose spending balance is held in a dollar stablecoin such as USDC or USDT instead of a bank deposit. When the cardholder pays, the card program converts the stablecoin to fiat, and the merchant is paid in local currency over the normal card network.\"\n  - q: \"How does a stablecoin-backed debit card work?\"\n    a: \"At checkout, the card network sends the authorization to the card program, which checks the cardholder's stablecoin balance, places a hold for the converted amount, and approves or declines within a few seconds. When the transaction clears, the program funds its settlement obligation by selling stablecoins for fiat or, where the network supports it, settling in USDC directly. The merchant is paid in its own currency and never touches a stablecoin.\"\n  - q: \"What is the difference between a stablecoin card and a crypto debit card?\"\n    a: \"A crypto debit card sells a volatile asset such as bitcoin or ether at the moment of purchase, so the balance needed for the same purchase changes minute to minute. A stablecoin card spends a token pegged 1:1 to the US dollar, so the amount leaving the balance matches the price. In the US, selling a volatile asset at checkout also realizes a taxable gain or loss on every swipe, while spending a dollar stablecoin usually produces a gain close to zero.\"\n  - q: \"Can you spend USDC or USDT directly with a debit card?\"\n    a: \"Not directly at the merchant. Merchants accept Visa and Mastercard, not tokens, so a stablecoin card converts USDC or USDT into the transaction currency behind the scenes during authorization or settlement. From the cardholder's side it feels like spending USDC; from the merchant's side it is an ordinary card payment in local currency.\"\n  - q: \"Who are the main players in stablecoin card issuing?\"\n    a: \"Card networks such as Visa and Mastercard route and settle transactions. A licensed bank or e-money institution acts as the issuer and BIN sponsor, an issuer processor such as Marqeta, Lithic, or Galileo runs authorizations, and a program manager owns the cardholder relationship. Stablecoin-native issuing platforms such as Rain, Bridge, Baanx, and Reap bundle several of those layers with stablecoin wallet funding.\"\n---\n\n*Reading time: about 7 minutes.*\n\n**Summary:** Stablecoin card issuing is issuing Visa or Mastercard debit, prepaid, or virtual cards whose spending balance is held in a dollar stablecoin such as USDC or USDT instead of a bank deposit. When the cardholder pays, the card program converts the stablecoin to fiat, and the merchant is paid in local currency over the normal card network.\n\nThe card itself is ordinary. Same chip, same Apple Pay button, same decline codes. What changes is the balance behind it and one conversion step that happens either at authorization or at settlement.\n\nThis explainer covers the mechanics, the companies in the stack, and the use cases. It is a reference, not a pitch.\n\n## How does a stablecoin-backed debit card work?\n\nEvery card transaction runs in two phases: authorization at checkout, which takes seconds, and clearing and settlement, which usually happens the next business day. A stablecoin card program hooks into both.\n\n1. **Authorization.** The cardholder taps. The merchant's acquirer sends the request through Visa or Mastercard to the issuer processor, which asks the program one question: can this card pay? The program checks the cardholder's stablecoin balance, converts the amount at the current rate, places a hold, and approves or declines. The whole round trip has a few seconds, so the balance check reads from a ledger, not from a fresh blockchain confirmation.\n2. **Clearing.** The merchant submits the final amount. It can differ from the authorized one (a restaurant tip, a hotel's incidentals, a fuel pre-authorization), so the program adjusts the hold.\n3. **Settlement.** The network nets the day's transactions and moves money between issuers and acquirers. The issuer owes the network for its cardholders' purchases, and the program has to fund that. It either sells stablecoins for dollars through a liquidity partner or, where the network allows it, pays in USDC.\n4. **Merchant payout.** The acquirer pays the merchant in local currency on its normal schedule. The merchant has no idea a stablecoin was involved.\n\n### Real-time vs. batch conversion\n\nPrograms pick one of two funding models, and the choice decides who carries the rate risk.\n\n- **Just-in-time conversion.** The stablecoin stays in the cardholder's wallet until a purchase happens, and the amount is reserved at authorization. The cardholder keeps the full balance in USDC or USDT until they spend it. The program carries a small exposure between authorization and settlement.\n- **Pre-converted balance.** The cardholder or business loads a fiat card balance from stablecoins in advance. Simpler for the issuer, but the money sits in fiat until it is spent, which defeats part of the point.\n\nFor a USD card funded with USDC, the exposure is small because both sides are dollars. It grows when the card currency differs from the stablecoin, for example a euro card funded with USDC.\n\n### Stablecoin settlement at the network level\n\nThe networks now accept stablecoins on the settlement leg itself. Visa lets US issuer and acquirer partners settle in USDC, starting with Cross River Bank and Lead Bank over Solana. Mastercard announced in June 2026 that it would support settlement in USDC, PYUSD, RLUSD, and other regulated stablecoins across several blockchains, with intraday, weekend, and holiday cycles.\n\nWhat this changes: an issuer can meet its settlement obligation on a Saturday without waiting for a bank wire window. What it does not change: anything the cardholder or merchant sees.\n\n## Stablecoin card vs. crypto debit card: what's the difference?\n\nThe first crypto cards were a way to spend an exchange balance. You held bitcoin at an exchange, the exchange issued a card, and every swipe sold a little bitcoin. Stablecoin cards use the same plumbing with a different asset, and that one change affects budgeting, tax, and who uses them.\n\n| Dimension | Crypto debit card | Stablecoin card |\n|---|---|---|\n| Asset spent | Bitcoin, ether, or an exchange balance | A dollar stablecoin such as USDC or USDT |\n| Balance needed for a USD 100 purchase | Changes with the market | USD 100 plus fees |\n| Custody | Usually the exchange that issues the card | A program wallet, or a self-custody wallet with a spending allowance, depending on the program |\n| Tax event per swipe (US) | Sale of property, realizing a gain or loss | Also a disposal, but the gain is usually close to zero |\n| Typical user | Consumers spending crypto holdings | Businesses, contractors, platforms paying people abroad, consumers holding dollars |\n| Network settlement | Fiat, after the asset is sold | Fiat, or USDC where the network supports it |\n\nThe [USDC vs USDT comparison](\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments) covers which stablecoin fits which program, and [what a stablecoin is](\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin) covers the reserve model behind the peg.\n\n## Can you spend USDC or USDT directly with a debit card?\n\nNot at the merchant. A coffee shop's terminal accepts Visa and Mastercard, not tokens. The card program does the conversion, so the cardholder experiences it as spending USDC and the merchant experiences it as a normal card payment in local currency.\n\nA few merchants accept stablecoins directly through crypto payment processors. That is a different product: an on-chain transfer, with no card network, no chargeback rights, and [no reversal](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) once it confirms.\n\n## Who are the main players in stablecoin card issuing?\n\nA card program is a stack of companies, each with a regulated job. Stablecoin programs keep the same stack and add a funding layer.\n\n| Role | What it does | Examples |\n|---|---|---|\n| Card network | Sets the rules, routes authorizations, runs settlement | Visa, Mastercard |\n| Issuing bank or BIN sponsor | The legal issuer; owns the BIN range and the regulatory responsibility | Cross River Bank, Lead Bank, Pathward in the US; e-money institutions elsewhere |\n| Issuer processor | Runs authorizations, card lifecycle, and the card ledger | Marqeta, Lithic, Galileo |\n| Program manager | Owns the brand and the cardholder relationship, operates compliance under the sponsor's oversight | The fintech or platform whose name is on the card |\n| Stablecoin issuing platform | Bundles sponsor access, processing, and stablecoin wallet funding in one API | Rain, Bridge, Baanx, Reap |\n| Liquidity and ramps | Converts stablecoins to fiat for settlement and fiat to stablecoins for top-ups | BlindPay (stablecoin payouts over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), plus virtual USD accounts); other on-ramp and off-ramp providers |\n| Identity and monitoring | KYC, KYB, sanctions screening, transaction monitoring | Specialist vendors or in-house systems |\n\nThe conversion providers in that stack are regulated too. Depending on the country they are a [VASP](\u002Fresources\u002Fmore\u002Fwhat-is-a-vasp), a money services business, or both.\n\nA card is also one payout option among several. A company paying people abroad can issue a card, send money to a local bank account, or offer both. BlindPay handles the bank-account side: stablecoins out to local currency over Pix, SPEI, ACH, SEPA, and SWIFT (POBO\u002FCOBO), and [virtual USD accounts](\u002Fvirtual-accounts) that turn ACH or wire deposits into USDC or USDT.\n\n## What are stablecoin cards used for?\n\nFive uses account for most programs.\n\n- **Contractor payouts.** A platform pays freelancers in USDC and gives them a card to spend it, so the contractor does not need a US bank account.\n- **Marketplace and creator payouts.** Sellers and creators in dozens of countries get earnings on a card the day they are released, not after a weekly wire batch.\n- **Treasury and team spend.** A company that holds its treasury in USDC issues corporate cards against it for software, ads, and travel.\n- **Dollar access in high-inflation economies.** In Argentina, Turkey, or Nigeria, a USD stablecoin card is a way to hold dollars and spend them without a foreign bank account.\n- **Travel and online spend.** A USD balance avoids some of the foreign exchange cost on USD-priced purchases.\n\nThe [stablecoin cards in Latin America](\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america) guide goes country by country on the fourth use.\n\n## What a stablecoin card does not change\n\nThree things work the same as on any other card.\n\n**Identity checks.** Every cardholder passes KYC and every business program owner passes KYB, because the sponsor bank's anti-money-laundering program covers the program. The [compliance guide](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance) covers who checks what.\n\n**Disputes.** Card network dispute rules apply to the card leg. A cardholder can still dispute a purchase. The on-chain transfer that funded the wallet cannot be reversed.\n\n**Fees.** Interchange, foreign transaction fees, and ATM fees still apply. Stablecoins remove cost on the funding side, not at the point of sale.\n\n## What to read next\n\nThis article is the first in a six-part series. Next, compare the two kinds of cards a company can hold in [crypto debit card vs. stablecoin card for business](\u002Fresources\u002Fmore\u002Fcrypto-debit-card-vs-stablecoin-card-for-business). Then see [stablecoin-funded virtual cards for cross-border payouts](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts), how programs work in [Latin America](\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america), the [developer's guide to issuing cards through an API](\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api), and [compliance for stablecoin card issuing](\u002Fresources\u002Fmore\u002Fstablecoin-card-issuing-compliance).\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":9687,"description":10104},"resources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing","Caytwg0GLgDGovPooKI8dM128t1F_sAj8CXHo4TvI6s",1790799442591]