[{"data":1,"prerenderedAt":803},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fstellar-anchors-vs-payout-api":3,"resources-category-stellar-anchors-vs-payout-api":592},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":563,"categoryType":6,"compare":6,"contributors":6,"date":564,"description":565,"extension":566,"faq":567,"howto":6,"isBlog":582,"isChangelog":582,"meta":583,"navigation":585,"path":586,"pillar":582,"products":6,"rawbody":587,"role":6,"seo":588,"seoTitle":589,"stem":590,"thumbnail":6,"updated":564,"__hash__":591},"content\u002Fresources\u002Fmore\u002Fstellar-anchors-vs-payout-api.md","Stellar anchors vs a payout API: how SEP-24, SEP-31, and SEP-38 off-ramp USDC",null,{"type":8,"value":9,"toc":550},"minimark",[10,14,17,23,50,55,66,73,81,85,88,116,119,123,132,135,161,190,193,197,206,234,237,244,248,255,284,296,304,308,420,424,427,499,502,506,509,529,536,540],[11,12,13],"p",{},"Stellar anchors and payout APIs both turn USDC on Stellar into money in a bank account. Anchors do it through open standards: SEP-24 for a user's own withdrawals, SEP-31 for business cross-border payments, and SEP-38 for quotes. A payout API does it behind one REST integration. The choice comes down to who owns the user, the KYC, and the corridors.",[11,15,16],{},"Stellar is unusual here. Most networks have no shared standard for off-ramps, so every provider invents its own. Stellar has a whole family of them. That's worth understanding even if you end up using an API, because the SEPs spell out the same steps every off-ramp has to solve.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,44,47],"ul",{},[27,28,29],"li",{},"An anchor bridges Stellar assets and bank money, and talks to wallets through SEPs.",[27,31,32],{},"SEP-24 is interactive: the anchor hosts the KYC page, the wallet sends the payment with a memo.",[27,34,35],{},"SEP-31 is for businesses: a sending anchor pays a receiving anchor outside Stellar.",[27,37,38,39,43],{},"SEP-38 separates indicative prices from firm quotes with an ",[40,41,42],"code",{},"expires_at",". It's still a Draft.",[27,45,46],{},"Each anchor brings its own auth, KYC rules, and quote server, so corridors multiply integrations.",[27,48,49],{},"A payout API like BlindPay takes signed USDC on Stellar and pays out over local rails from one integration.",[51,52,54],"h2",{"id":53},"what-is-a-stellar-anchor","What is a Stellar anchor?",[11,56,57,58,65],{},"An anchor is a business that connects Stellar to the outside financial system. It accepts bank currency and delivers a Stellar asset, or accepts a Stellar asset and pays bank currency out. The SEP-24 spec describes its goal as \"the standard way for anchors and wallets to interact on behalf of users\" (",[59,60,64],"a",{"href":61,"rel":62},"https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0024.md",[63],"nofollow","SEP-24",").",[11,67,68,69,72],{},"Anchors publish what they support in a ",[40,70,71],{},"stellar.toml"," file and authenticate clients with SEP-10 web authentication. On top of that sit the flows. Three matter for off-ramps: SEP-24, SEP-31, and SEP-38.",[11,74,75,76,80],{},"In payment terms, an anchor is an off-ramp with a public protocol. ",[59,77,79],{"href":78},"\u002Fresources\u002Fmore\u002Ftypes-of-crypto-off-ramps","Types of crypto off-ramps"," places it next to exchanges, widgets, and payout APIs.",[51,82,84],{"id":83},"how-does-a-sep-24-withdrawal-work","How does a SEP-24 withdrawal work?",[11,86,87],{},"SEP-24 is the hosted flow. The wallet asks, the anchor collects what it needs on its own page, and the wallet sends the funds.",[89,90,91,94,97,104,110],"ol",{},[27,92,93],{},"The wallet authenticates with SEP-10. The spec says anchors \"must support SEP-10 and\u002For SEP-45 web authentication.\"",[27,95,96],{},"The wallet starts a withdrawal. If the anchor needs KYC or bank details, it returns a URL, and the wallet \"should open a popup browser window or embedded webview\" to it.",[27,98,99,100,103],{},"The user fills in the anchor's form. The transaction moves to ",[40,101,102],{},"pending_user_transfer_start",".",[27,105,106,107,103],{},"The wallet pays. \"In order to fulfill a withdrawal, a wallet must make a payment to the Stellar address that the anchor provides,\" using the anchor's ",[40,108,109],{},"withdraw_memo",[27,111,112,113,103],{},"The anchor sees the payment and sends the bank transfer. Status ends at ",[40,114,115],{},"completed",[11,117,118],{},"Good for a consumer wallet: the user picks a local anchor, and the anchor owns its compliance screen. The tradeoff is that you don't control that screen, and each anchor's form looks different.",[51,120,122],{"id":121},"how-does-sep-31-move-a-cross-border-payment","How does SEP-31 move a cross-border payment?",[11,124,125,126,131],{},"SEP-31 is the business version. It \"defines a protocol for enabling payments between two financial accounts that exist outside the Stellar network\" (",[59,127,130],{"href":128,"rel":129},"https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0031.md",[63],"SEP-31","). A sending anchor collects from its client and pays a receiving anchor, which delivers to the recipient's bank.",[11,133,134],{},"What the receiving anchor requires:",[24,136,137,143,152],{},[27,138,139,142],{},[20,140,141],{},"SEP-10 auth."," \"Sending Anchors must authenticate with Receiving Anchors via SEP-10 Web Authentication.\"",[27,144,145,148,149,103],{},[20,146,147],{},"SEP-12 KYC",", when the receiving anchor needs customer data, through its own ",[40,150,151],{},"KYC_SERVER",[27,153,154,157,158,103],{},[20,155,156],{},"SEP-38 quotes",", for flows with asset conversion, through its ",[40,159,160],{},"ANCHOR_QUOTE_SERVER",[11,162,163,164,167,168,167,171,167,174,167,177,167,179,167,182,185,186,189],{},"Transactions report statuses like ",[40,165,166],{},"pending_sender",", ",[40,169,170],{},"pending_stellar",[40,172,173],{},"pending_receiver",[40,175,176],{},"pending_external",[40,178,115],{},[40,180,181],{},"refunded",[40,183,184],{},"expired",", and ",[40,187,188],{},"error",". SEP-31 is marked Active at version 3.1.0.",[11,191,192],{},"The catch is in the plural. Every receiving anchor is a separate counterparty with its own KYC fields and its own quote server. Three corridors can mean three integrations.",[51,194,196],{"id":195},"what-do-sep-38-quotes-lock","What do SEP-38 quotes lock?",[11,198,199,200,205],{},"SEP-38, the Anchor RFQ API, has two kinds of price (",[59,201,204],{"href":202,"rel":203},"https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0038.md",[63],"SEP-38","):",[24,207,208,222],{},[27,209,210,213,214,217,218,221],{},[20,211,212],{},"Indicative",", from ",[40,215,216],{},"GET \u002Fprices"," and ",[40,219,220],{},"GET \u002Fprice",". \"These prices are indicative.\" The actual price is set at conversion time.",[27,223,224,213,227,230,231,233],{},[20,225,226],{},"Firm",[40,228,229],{},"POST \u002Fquote",". The quoted amount \"must be held in reserve\" until expiry, and ",[40,232,42],{}," is \"the date and time by which the anchor must receive funds from the client.\"",[11,235,236],{},"SEP-31 ties the two together: with a firm quote, \"the Stellar transaction must be submitted to the Stellar network prior to the quote's expiration.\" Same idea as any binding payout quote. One more detail: SEP-38 is still a Draft, at version 2.5.0, so anchors may implement it differently.",[11,238,239,240,103],{},"That split mirrors the RFQ model in wholesale FX, covered in ",[59,241,243],{"href":242},"\u002Fresources\u002Fmore\u002Frfq-pricing-stablecoin-fx-explained","RFQ pricing for stablecoin FX",[51,245,247],{"id":246},"how-does-a-payout-api-do-the-same-off-ramp","How does a payout API do the same off-ramp?",[11,249,250,251,205],{},"One integration, one quote format, one KYC relationship. On BlindPay, a Stellar payout funded from your own wallet takes three calls (",[59,252,254],{"href":253},"\u002Fdocs\u002Fpayout-stellar","payout with Stellar",[89,256,257,272,278],{},[27,258,259,262,263,267,268,271],{},[20,260,261],{},"Quote."," Create a ",[59,264,266],{"href":265},"\u002Fdocs\u002Fpayout-quotes","payout quote"," against the recipient's bank account with a Stellar ",[40,269,270],{},"network",". It locks the rate and fees for 5 minutes.",[27,273,274,277],{},[20,275,276],{},"Authorize and sign."," Stellar has no allowance mechanism, so the authorize endpoint returns an unsigned transaction to BlindPay's treasury address. You sign it with your Stellar key and submit it.",[27,279,280,283],{},[20,281,282],{},"Create the payout."," Send the quote ID and the signed transaction. BlindPay \"independently re-validates the signed transaction against the quote (destination and amount)\" before paying out.",[11,285,286,287,290,291,295],{},"On Stellar, BlindPay payouts are funded in USDC on mainnet, and development instances use USDB on ",[40,288,289],{},"stellar_testnet"," (",[59,292,294],{"href":293},"\u002Fdocs\u002Fkb\u002Fsupported-chains","supported chains","). The fiat side runs on local rails: ACH, wire, RTP, and SWIFT (POBO\u002FCOBO) in the US and globally, Pix and TED in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, and SEPA in Europe. The recipient never sees Stellar. They see a bank deposit.",[11,297,298,299,303],{},"Which network to fund from in the first place is its own question; ",[59,300,302],{"href":301},"\u002Fresources\u002Fmore\u002Fbest-network-to-off-ramp-stablecoins","the best network to off-ramp stablecoins"," compares finality and fees.",[51,305,307],{"id":306},"how-do-anchors-and-a-payout-api-compare","How do anchors and a payout API compare?",[309,310,311,329],"table",{},[312,313,314],"thead",{},[315,316,317,320,322,324,326],"tr",{},[318,319],"th",{},[318,321,64],{},[318,323,130],{},[318,325,204],{},[318,327,328],{},"Payout API (BlindPay)",[330,331,332,350,367,386,403],"tbody",{},[315,333,334,338,341,344,347],{},[335,336,337],"td",{},"Job",[335,339,340],{},"User's own deposit or withdrawal",[335,342,343],{},"Business cross-border payment",[335,345,346],{},"Prices and firm quotes",[335,348,349],{},"Business payout to a bank account",[315,351,352,355,358,361,364],{},[335,353,354],{},"Who runs KYC",[335,356,357],{},"Anchor, on its hosted page",[335,359,360],{},"Receiving anchor, via SEP-12",[335,362,363],{},"n\u002Fa",[335,365,366],{},"BlindPay, through the API",[315,368,369,372,375,378,383],{},[335,370,371],{},"Price",[335,373,374],{},"Anchor's terms",[335,376,377],{},"SEP-38 quote, optional",[335,379,380,381],{},"Indicative or firm with ",[40,382,42],{},[335,384,385],{},"Locked quote, 5 minutes",[315,387,388,391,394,397,400],{},[335,389,390],{},"Integration per corridor",[335,392,393],{},"One per anchor",[335,395,396],{},"One per receiving anchor",[335,398,399],{},"Per anchor quote server",[335,401,402],{},"One API for every rail",[315,404,405,408,411,414,417],{},[335,406,407],{},"Spec status",[335,409,410],{},"Active, v3.8.0",[335,412,413],{},"Active, v3.1.0",[335,415,416],{},"Draft, v2.5.0",[335,418,419],{},"Versioned REST API",[51,421,423],{"id":422},"illustrative-example-what-do-three-corridors-cost-to-integrate","Illustrative example: what do three corridors cost to integrate?",[11,425,426],{},"Illustrative example. A company holding USDC on Stellar pays contractors in Brazil, Mexico, and the US every month. These counts describe integration work, not prices.",[309,428,429,442],{},[312,430,431],{},[315,432,433,436,439],{},[318,434,435],{},"Step",[318,437,438],{},"Through anchors (SEP-31)",[318,440,441],{},"Through a payout API",[330,443,444,455,466,477,488],{},[315,445,446,449,452],{},[335,447,448],{},"Find a counterparty per country",[335,450,451],{},"3 receiving anchors",[335,453,454],{},"1 provider",[315,456,457,460,463],{},[335,458,459],{},"Auth setups (SEP-10 or API key)",[335,461,462],{},"3",[335,464,465],{},"1",[315,467,468,471,474],{},[335,469,470],{},"KYC field sets to map",[335,472,473],{},"3 SEP-12 schemas",[335,475,476],{},"1 customer schema",[315,478,479,482,485],{},[335,480,481],{},"Quote formats to parse",[335,483,484],{},"Up to 3 SEP-38 servers",[335,486,487],{},"1 quote object",[315,489,490,493,496],{},[335,491,492],{},"Status models to reconcile",[335,494,495],{},"3 implementations of the SEP-31 statuses",[335,497,498],{},"1 payout status model",[11,500,501],{},"The anchor column isn't wrong. It's open, and nobody sits in the middle. It's just more surface. Add a fourth country and the left column grows by one of everything.",[51,503,505],{"id":504},"which-one-fits-your-product","Which one fits your product?",[11,507,508],{},"Pick by who owns the user.",[24,510,511,517,523],{},[27,512,513,516],{},[20,514,515],{},"Consumer Stellar wallet."," SEP-24 fits. Users pick a local anchor, the anchor's page handles their KYC, and your wallet only sends the payment.",[27,518,519,522],{},[20,520,521],{},"Remittance business with existing anchor partners."," SEP-31 fits, if you already have the bilateral relationships in your corridors.",[27,524,525,528],{},[20,526,527],{},"A business paying many recipients across countries."," A payout API fits. One quote format, one KYC flow, and the same code path for Stellar and every other network you hold.",[11,530,531,532,103],{},"You can mix them. A wallet that offers SEP-24 to its users can still send its own treasury payouts through an API. And the hub question behind both, who earns what on a conversion, is in ",[59,533,535],{"href":534},"\u002Fresources\u002Fmore\u002Fhow-onramp-offramp-providers-make-money","how on\u002Foff-ramp providers make money",[51,537,539],{"id":538},"what-to-do-next","What to do next",[11,541,542,543,545,546,549],{},"If you hold USDC on Stellar, run one test payout on a development instance: create a quote with ",[40,544,289],{}," and USDB, call authorize, sign, and create the payout. Time it end to end and compare it with the anchor flow you have today. The ",[59,547,548],{"href":253},"Stellar payout guide"," has the code.",{"title":551,"searchDepth":552,"depth":552,"links":553},"",2,[554,555,556,557,558,559,560,561,562],{"id":53,"depth":552,"text":54},{"id":83,"depth":552,"text":84},{"id":121,"depth":552,"text":122},{"id":195,"depth":552,"text":196},{"id":246,"depth":552,"text":247},{"id":306,"depth":552,"text":307},{"id":422,"depth":552,"text":423},{"id":504,"depth":552,"text":505},{"id":538,"depth":552,"text":539},"stablecoins","2026-10-05","How Stellar anchors off-ramp USDC through SEP-24, SEP-31, and SEP-38 quotes, how a payout API does the same job, and which one fits your product.","md",[568,570,573,576,579],{"q":54,"a":569},"An anchor is a business that connects the Stellar network to off-chain money: it takes deposits of bank currency and issues or delivers Stellar assets, and it takes Stellar assets back and pays out bank currency. Anchors interoperate through Stellar Ecosystem Proposals, or SEPs, such as SEP-24 for hosted deposits and withdrawals and SEP-31 for cross-border payments.",{"q":571,"a":572},"What is the difference between SEP-24 and SEP-31?","SEP-24 is a wallet-to-anchor flow for a user's own deposits and withdrawals: the anchor hosts a web page for KYC and details, and the wallet sends the payment. SEP-31 is a business-to-business flow: a sending anchor pays a receiving anchor, which delivers to an account outside Stellar, with KYC through SEP-12 and optional quotes through SEP-38.",{"q":574,"a":575},"Are SEP-38 quotes firm?","They can be. SEP-38 separates indicative prices, from GET \u002Fprices and GET \u002Fprice, from firm quotes, from POST \u002Fquote. A firm quote carries an expires_at, the time by which the anchor must receive the funds, and SEP-31 says the Stellar transaction must be submitted before the quote expires. SEP-38 itself is still marked Draft.",{"q":577,"a":578},"Can I off-ramp USDC on Stellar without an anchor?","Yes, through a payout API that accepts Stellar. With BlindPay, you create a payout quote with a Stellar network, call authorize to get an unsigned transaction, sign it with your Stellar key, submit it, and create the payout with the signed transaction. BlindPay re-validates the destination and amount, then pays the bank account over a local rail.",{"q":580,"a":581},"When should a business use an anchor instead of a payout API?","Use anchors when you build a consumer Stellar wallet and want users to pick a local anchor and complete KYC on that anchor's own page, or when you already have bilateral SEP-31 relationships in your corridors. Use a payout API when you pay many recipients across several countries and want one integration, one KYC relationship, and one quote format.",false,{"author":584},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fstellar-anchors-vs-payout-api","---\ntitle: \"Stellar anchors vs a payout API: how SEP-24, SEP-31, and SEP-38 off-ramp USDC\"\nseoTitle: \"Stellar anchors vs a payout API: SEP-24, SEP-31, SEP-38\"\ndescription: \"How Stellar anchors off-ramp USDC through SEP-24, SEP-31, and SEP-38 quotes, how a payout API does the same job, and which one fits your product.\"\ndate: \"2026-10-05\"\nupdated: \"2026-10-05\"\ncategory: \"stablecoins\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is a Stellar anchor?\"\n    a: \"An anchor is a business that connects the Stellar network to off-chain money: it takes deposits of bank currency and issues or delivers Stellar assets, and it takes Stellar assets back and pays out bank currency. Anchors interoperate through Stellar Ecosystem Proposals, or SEPs, such as SEP-24 for hosted deposits and withdrawals and SEP-31 for cross-border payments.\"\n  - q: \"What is the difference between SEP-24 and SEP-31?\"\n    a: \"SEP-24 is a wallet-to-anchor flow for a user's own deposits and withdrawals: the anchor hosts a web page for KYC and details, and the wallet sends the payment. SEP-31 is a business-to-business flow: a sending anchor pays a receiving anchor, which delivers to an account outside Stellar, with KYC through SEP-12 and optional quotes through SEP-38.\"\n  - q: \"Are SEP-38 quotes firm?\"\n    a: \"They can be. SEP-38 separates indicative prices, from GET \u002Fprices and GET \u002Fprice, from firm quotes, from POST \u002Fquote. A firm quote carries an expires_at, the time by which the anchor must receive the funds, and SEP-31 says the Stellar transaction must be submitted before the quote expires. SEP-38 itself is still marked Draft.\"\n  - q: \"Can I off-ramp USDC on Stellar without an anchor?\"\n    a: \"Yes, through a payout API that accepts Stellar. With BlindPay, you create a payout quote with a Stellar network, call authorize to get an unsigned transaction, sign it with your Stellar key, submit it, and create the payout with the signed transaction. BlindPay re-validates the destination and amount, then pays the bank account over a local rail.\"\n  - q: \"When should a business use an anchor instead of a payout API?\"\n    a: \"Use anchors when you build a consumer Stellar wallet and want users to pick a local anchor and complete KYC on that anchor's own page, or when you already have bilateral SEP-31 relationships in your corridors. Use a payout API when you pay many recipients across several countries and want one integration, one KYC relationship, and one quote format.\"\n---\n\nStellar anchors and payout APIs both turn USDC on Stellar into money in a bank account. Anchors do it through open standards: SEP-24 for a user's own withdrawals, SEP-31 for business cross-border payments, and SEP-38 for quotes. A payout API does it behind one REST integration. The choice comes down to who owns the user, the KYC, and the corridors.\n\nStellar is unusual here. Most networks have no shared standard for off-ramps, so every provider invents its own. Stellar has a whole family of them. That's worth understanding even if you end up using an API, because the SEPs spell out the same steps every off-ramp has to solve.\n\n**Key takeaways**\n\n- An anchor bridges Stellar assets and bank money, and talks to wallets through SEPs.\n- SEP-24 is interactive: the anchor hosts the KYC page, the wallet sends the payment with a memo.\n- SEP-31 is for businesses: a sending anchor pays a receiving anchor outside Stellar.\n- SEP-38 separates indicative prices from firm quotes with an `expires_at`. It's still a Draft.\n- Each anchor brings its own auth, KYC rules, and quote server, so corridors multiply integrations.\n- A payout API like BlindPay takes signed USDC on Stellar and pays out over local rails from one integration.\n\n## What is a Stellar anchor?\n\nAn anchor is a business that connects Stellar to the outside financial system. It accepts bank currency and delivers a Stellar asset, or accepts a Stellar asset and pays bank currency out. The SEP-24 spec describes its goal as \"the standard way for anchors and wallets to interact on behalf of users\" ([SEP-24](https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0024.md)).\n\nAnchors publish what they support in a `stellar.toml` file and authenticate clients with SEP-10 web authentication. On top of that sit the flows. Three matter for off-ramps: SEP-24, SEP-31, and SEP-38.\n\nIn payment terms, an anchor is an off-ramp with a public protocol. [Types of crypto off-ramps](\u002Fresources\u002Fmore\u002Ftypes-of-crypto-off-ramps) places it next to exchanges, widgets, and payout APIs.\n\n## How does a SEP-24 withdrawal work?\n\nSEP-24 is the hosted flow. The wallet asks, the anchor collects what it needs on its own page, and the wallet sends the funds.\n\n1. The wallet authenticates with SEP-10. The spec says anchors \"must support SEP-10 and\u002For SEP-45 web authentication.\"\n2. The wallet starts a withdrawal. If the anchor needs KYC or bank details, it returns a URL, and the wallet \"should open a popup browser window or embedded webview\" to it.\n3. The user fills in the anchor's form. The transaction moves to `pending_user_transfer_start`.\n4. The wallet pays. \"In order to fulfill a withdrawal, a wallet must make a payment to the Stellar address that the anchor provides,\" using the anchor's `withdraw_memo`.\n5. The anchor sees the payment and sends the bank transfer. Status ends at `completed`.\n\nGood for a consumer wallet: the user picks a local anchor, and the anchor owns its compliance screen. The tradeoff is that you don't control that screen, and each anchor's form looks different.\n\n## How does SEP-31 move a cross-border payment?\n\nSEP-31 is the business version. It \"defines a protocol for enabling payments between two financial accounts that exist outside the Stellar network\" ([SEP-31](https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0031.md)). A sending anchor collects from its client and pays a receiving anchor, which delivers to the recipient's bank.\n\nWhat the receiving anchor requires:\n\n- **SEP-10 auth.** \"Sending Anchors must authenticate with Receiving Anchors via SEP-10 Web Authentication.\"\n- **SEP-12 KYC**, when the receiving anchor needs customer data, through its own `KYC_SERVER`.\n- **SEP-38 quotes**, for flows with asset conversion, through its `ANCHOR_QUOTE_SERVER`.\n\nTransactions report statuses like `pending_sender`, `pending_stellar`, `pending_receiver`, `pending_external`, `completed`, `refunded`, `expired`, and `error`. SEP-31 is marked Active at version 3.1.0.\n\nThe catch is in the plural. Every receiving anchor is a separate counterparty with its own KYC fields and its own quote server. Three corridors can mean three integrations.\n\n## What do SEP-38 quotes lock?\n\nSEP-38, the Anchor RFQ API, has two kinds of price ([SEP-38](https:\u002F\u002Fgithub.com\u002Fstellar\u002Fstellar-protocol\u002Fblob\u002Fmaster\u002Fecosystem\u002Fsep-0038.md)):\n\n- **Indicative**, from `GET \u002Fprices` and `GET \u002Fprice`. \"These prices are indicative.\" The actual price is set at conversion time.\n- **Firm**, from `POST \u002Fquote`. The quoted amount \"must be held in reserve\" until expiry, and `expires_at` is \"the date and time by which the anchor must receive funds from the client.\"\n\nSEP-31 ties the two together: with a firm quote, \"the Stellar transaction must be submitted to the Stellar network prior to the quote's expiration.\" Same idea as any binding payout quote. One more detail: SEP-38 is still a Draft, at version 2.5.0, so anchors may implement it differently.\n\nThat split mirrors the RFQ model in wholesale FX, covered in [RFQ pricing for stablecoin FX](\u002Fresources\u002Fmore\u002Frfq-pricing-stablecoin-fx-explained).\n\n## How does a payout API do the same off-ramp?\n\nOne integration, one quote format, one KYC relationship. On BlindPay, a Stellar payout funded from your own wallet takes three calls ([payout with Stellar](\u002Fdocs\u002Fpayout-stellar)):\n\n1. **Quote.** Create a [payout quote](\u002Fdocs\u002Fpayout-quotes) against the recipient's bank account with a Stellar `network`. It locks the rate and fees for 5 minutes.\n2. **Authorize and sign.** Stellar has no allowance mechanism, so the authorize endpoint returns an unsigned transaction to BlindPay's treasury address. You sign it with your Stellar key and submit it.\n3. **Create the payout.** Send the quote ID and the signed transaction. BlindPay \"independently re-validates the signed transaction against the quote (destination and amount)\" before paying out.\n\nOn Stellar, BlindPay payouts are funded in USDC on mainnet, and development instances use USDB on `stellar_testnet` ([supported chains](\u002Fdocs\u002Fkb\u002Fsupported-chains)). The fiat side runs on local rails: ACH, wire, RTP, and SWIFT (POBO\u002FCOBO) in the US and globally, Pix and TED in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, and SEPA in Europe. The recipient never sees Stellar. They see a bank deposit.\n\nWhich network to fund from in the first place is its own question; [the best network to off-ramp stablecoins](\u002Fresources\u002Fmore\u002Fbest-network-to-off-ramp-stablecoins) compares finality and fees.\n\n## How do anchors and a payout API compare?\n\n| | SEP-24 | SEP-31 | SEP-38 | Payout API (BlindPay) |\n| --- | --- | --- | --- | --- |\n| Job | User's own deposit or withdrawal | Business cross-border payment | Prices and firm quotes | Business payout to a bank account |\n| Who runs KYC | Anchor, on its hosted page | Receiving anchor, via SEP-12 | n\u002Fa | BlindPay, through the API |\n| Price | Anchor's terms | SEP-38 quote, optional | Indicative or firm with `expires_at` | Locked quote, 5 minutes |\n| Integration per corridor | One per anchor | One per receiving anchor | Per anchor quote server | One API for every rail |\n| Spec status | Active, v3.8.0 | Active, v3.1.0 | Draft, v2.5.0 | Versioned REST API |\n\n## Illustrative example: what do three corridors cost to integrate?\n\nIllustrative example. A company holding USDC on Stellar pays contractors in Brazil, Mexico, and the US every month. These counts describe integration work, not prices.\n\n| Step | Through anchors (SEP-31) | Through a payout API |\n| --- | --- | --- |\n| Find a counterparty per country | 3 receiving anchors | 1 provider |\n| Auth setups (SEP-10 or API key) | 3 | 1 |\n| KYC field sets to map | 3 SEP-12 schemas | 1 customer schema |\n| Quote formats to parse | Up to 3 SEP-38 servers | 1 quote object |\n| Status models to reconcile | 3 implementations of the SEP-31 statuses | 1 payout status model |\n\nThe anchor column isn't wrong. It's open, and nobody sits in the middle. It's just more surface. Add a fourth country and the left column grows by one of everything.\n\n## Which one fits your product?\n\nPick by who owns the user.\n\n- **Consumer Stellar wallet.** SEP-24 fits. Users pick a local anchor, the anchor's page handles their KYC, and your wallet only sends the payment.\n- **Remittance business with existing anchor partners.** SEP-31 fits, if you already have the bilateral relationships in your corridors.\n- **A business paying many recipients across countries.** A payout API fits. One quote format, one KYC flow, and the same code path for Stellar and every other network you hold.\n\nYou can mix them. A wallet that offers SEP-24 to its users can still send its own treasury payouts through an API. And the hub question behind both, who earns what on a conversion, is in [how on\u002Foff-ramp providers make money](\u002Fresources\u002Fmore\u002Fhow-onramp-offramp-providers-make-money).\n\n## What to do next\n\nIf you hold USDC on Stellar, run one test payout on a development instance: create a quote with `stellar_testnet` and USDB, call authorize, sign, and create the payout. Time it end to end and compare it with the anchor flow you have today. The [Stellar payout guide](\u002Fdocs\u002Fpayout-stellar) has the code.\n",{"title":5,"description":565},"Stellar anchors vs a payout API: SEP-24, SEP-31, SEP-38","resources\u002Fmore\u002Fstellar-anchors-vs-payout-api","niZtdOXClOHZo1dprn1ikL81WEFZiIti3oZISp-3CWM",[593,597,601,605,609,613,617,621,625,629,633,637,641,645,649,653,657,661,665,669,673,677,681,685,689,693,697,701,705,709,713,717,721,722,726,730,734,738,742,746,749,753,756,760,764,768,772,776,780,784,788,792,795,799],{"path":594,"title":595,"description":596},"\u002Fresources\u002Fmore\u002Fare-stablecoin-cards-safe","Are stablecoin cards safe? Peg, issuer, custody, and smart contract risks","The five risks of a stablecoin card: peg, program failure, custody, smart contracts, and fraud, with the August 2026 incident and a safety checklist.",{"path":598,"title":599,"description":600},"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-safe","Are stablecoin payments safe? The risks businesses should check, and how to reduce them","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.",{"path":602,"title":603,"description":604},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-cross-border-payments-2026","Best stablecoin APIs for cross-border payments in 2026: BlindPay, Circle, Stripe, Bridge, and Fireblocks compared","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.",{"path":606,"title":607,"description":608},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-apis-2026","Best stablecoin APIs in 2026: 10 providers compared","Ten stablecoin APIs compared for 2026: BlindPay, Circle, Bridge, BVNK, Fireblocks, Crossmint, Zero Hash, Conduit, Sphere, and Borderless, across rails, custody, pricing, and compliance.",{"path":610,"title":611,"description":612},"\u002Fresources\u002Fmore\u002Fbest-virtual-account-providers-stablecoins","Best virtual account providers for stablecoins in 2026: BlindPay, Bridge, HIFI, Noah, and Conduit compared","Five virtual account providers for fiat and stablecoins compared on deposit rails, settlement chains, account naming, and custody, plus a 30-day test plan.",{"path":614,"title":615,"description":616},"\u002Fresources\u002Fmore\u002Fbusiness-vs-consumer-crypto-on-ramps","Business vs consumer crypto on-ramps: what changes when a company buys stablecoins","A consumer on-ramp sells crypto to one person, usually by card. A business on-ramp turns company bank deposits into stablecoins via an API. What differs.",{"path":618,"title":619,"description":620},"\u002Fresources\u002Fmore\u002Fcrypto-debit-card-vs-stablecoin-card-for-business","Crypto debit card vs. stablecoin card for business: custody, accounting, tax, and controls compared","Why a company should treat crypto debit cards and stablecoin cards differently: budget predictability, custody risk, per-swipe tax events, accounting, and spend controls.",{"path":622,"title":623,"description":624},"\u002Fresources\u002Fmore\u002Fcustodial-vs-self-custodial-stablecoin-cards","Custodial vs. self-custodial stablecoin cards: who actually holds your money?","Who holds the stablecoins behind your card: custodial vs. self-custodial models, smart-account allowances, failure modes, and what August 2026 showed.",{"path":626,"title":627,"description":628},"\u002Fresources\u002Fmore\u002Fdo-you-need-a-crypto-wallet-for-stablecoin-payments","Do you need a crypto wallet to make stablecoin payments?","Who needs a wallet in a stablecoin payment, who doesn't, and how payment providers hide keys, networks, gas, and confirmations from payers and recipients.",{"path":630,"title":631,"description":632},"\u002Fresources\u002Fmore\u002Fdoes-network-change-offramp-quote","Does the blockchain network change your off-ramp quote? What moves and what doesn't","Network and token are inputs to every payout quote. Which quote lines can change by chain, where gas sits, and how to compare two networks fairly.",{"path":634,"title":635,"description":636},"\u002Fresources\u002Fmore\u002Fstablecoin-platform-vs-payout-api","Full-stack stablecoin platform vs payout API: which layer does your product need?","Issuance, wallets, cards, orchestration, or local payouts? Map your job to the right layer of the stablecoin stack, with BlindPay and Bridge as examples.",{"path":638,"title":639,"description":640},"\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments","How merchants accept stablecoin payments: the complete 2026 guide","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.",{"path":642,"title":643,"description":644},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-orchestration-cross-border-payouts","How stablecoins fit into payment orchestration for cross-border payouts","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.",{"path":646,"title":647,"description":648},"\u002Fresources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins","How to accept bank transfers and settle in stablecoins using virtual accounts","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.",{"path":650,"title":651,"description":652},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-blockchain-payment-api","How to choose a blockchain payment API: a technical buyer's checklist","Seven checks for a blockchain payment API: SDKs, OpenAPI quality, abstraction level, networks, built-in compliance, local payout rails, and pricing.",{"path":654,"title":655,"description":656},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-stablecoin-api","How to choose a stablecoin API: the 6 questions that actually matter","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.",{"path":658,"title":659,"description":660},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-a-wallet-integration-provider","How to evaluate a wallet integration provider: 12-point checklist","A 12-point checklist for choosing a wallet or stablecoin payments provider: custody, chains, rails, pricing, compliance, SOC 2, SLAs, and AI tooling.",{"path":662,"title":663,"description":664},"\u002Fresources\u002Fmore\u002Fhow-to-fund-a-stablecoin-card","How to fund a stablecoin card: exchanges, wallet transfers, virtual accounts, and bank deposits","Four ways to fund a stablecoin card, compared by speed, cost, and control: exchange withdrawal, wallet transfer, virtual account deposit, and card top-up.",{"path":666,"title":667,"description":668},"\u002Fresources\u002Fmore\u002Fis-stripe-a-stablecoin-api","Is Stripe a stablecoin API? What a payout API, Stripe, and Bridge each do","Partly. Stripe offers stablecoin checkout and balances, and owns Bridge, a stablecoin infrastructure API. What each covers for cross-border payouts.",{"path":670,"title":671,"description":672},"\u002Fresources\u002Fmore\u002Fis-xrp-a-stablecoin","Is XRP a stablecoin? No, and here is the difference","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.",{"path":674,"title":675,"description":676},"\u002Fresources\u002Fmore\u002Fotc-quote-vs-standard-quote","OTC quotes vs standard quotes for large BRL on-ramps: how a 10-second quote works","An OTC quote prices a large BRL to USDT on-ramp through an OTC desk, locks for 10 seconds, and lists fees as lines. When to pick it over a standard quote.",{"path":678,"title":679,"description":680},"\u002Fresources\u002Fmore\u002Fonramp-offramp-liquidity-glossary","On-ramp and off-ramp liquidity glossary: 40 terms for live quotes, spread, and settlement","Live quote, expiry, spread, slippage, basis points, depth, market maker, RFQ, pre-funding: the 40 terms behind on\u002Foff-ramp liquidity, in plain English.",{"path":682,"title":683,"description":684},"\u002Fresources\u002Fmore\u002Fonchain-liquidity-vs-offramp-liquidity","Onchain liquidity vs off-ramp liquidity: why a deep DEX pool doesn't mean a deep BRL payout","Onchain liquidity is tokens in pools. Off-ramp liquidity is local currency a provider can pay into bank accounts. Why one doesn't predict the other.",{"path":686,"title":687,"description":688},"\u002Fresources\u002Fmore\u002Fstablecoin-api-pricing-explained","Stablecoin API pricing: mint fees, spread, and what you actually pay","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.",{"path":690,"title":691,"description":692},"\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-crypto-payment-gateway","Stablecoin API vs crypto payment gateway: what's the difference?","A crypto payment gateway accepts crypto at checkout. A stablecoin API moves money across borders through code, and neither side needs a wallet.",{"path":694,"title":695,"description":696},"\u002Fresources\u002Fmore\u002Fstablecoin-api-vs-traditional-cross-border-rails","Stablecoin API vs traditional cross-border rails: a plain-English guide for payments teams","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.",{"path":698,"title":699,"description":700},"\u002Fresources\u002Fmore\u002Fstablecoin-b2b-payments-by-region","Stablecoin B2B payments in 2025: volume, regions, and what the data misses","B2B stablecoin payments hit $226 billion in 2025, per McKinsey and Artemis. Where payments start, why Latin America looks tiny, and what blocks scale.",{"path":702,"title":703,"description":704},"\u002Fresources\u002Fmore\u002Fstablecoin-card-vs-crypto-debit-prepaid-credit","Stablecoin card vs. crypto debit card vs. prepaid vs. credit: which type of crypto card is which?","Four kinds of crypto card compared: funding source, when conversion happens, tax timing, volatility, fees to check, and who each one suits.",{"path":706,"title":707,"description":708},"\u002Fresources\u002Fmore\u002Fstablecoin-depeg-risk-payments","Stablecoin depeg risk for payment companies: what past depegs teach and how to set limits","A depeg hurts a payment flow only while you hold the stablecoin. What USDC's 2023 depeg and UST's collapse teach, and the limits and triggers to set.",{"path":710,"title":711,"description":712},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-statistics-2026","Stablecoin payment statistics 2026: volume, B2B share, and cross-border data","Sourced stablecoin payment statistics for 2026: real payment volume vs transfer volume, B2B share, domestic vs cross-border, top markets, and chains.",{"path":714,"title":715,"description":716},"\u002Fresources\u002Fmore\u002Fstablecoins-vs-bitcoin-for-business-payments","Stablecoins vs Bitcoin for business payments: price risk, settlement, accounting, and rules","Stablecoins or Bitcoin for business payments? Compare price stability, settlement, US tax, the GENIUS Act, and issuer risk, with a clear decision rule.",{"path":718,"title":719,"description":720},"\u002Fresources\u002Fmore\u002Fstablecoin-card-statistics-2026","State of stablecoin cards 2026: volume, programs, networks, and risks (data report)","Sourced stablecoin card statistics for 2026: Visa volume and programs, monthly onchain spend, average ticket, chain and token mix, and incidents.",{"path":586,"title":5,"description":565},{"path":723,"title":724,"description":725},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","Types of stablecoin APIs: issuer, wallet, orchestration, payout, and non-custodial APIs compared","The five types of stablecoin APIs, what each one does, and who holds the funds and the compliance work in each. Plus how they differ from exchange APIs.",{"path":727,"title":728,"description":729},"\u002Fresources\u002Fmore\u002Fusdc-vs-usdt-for-payments","USDC vs USDT for payments: which should businesses use?","USDC offers stronger reserve transparency and US regulatory posture; USDT offers deeper liquidity in emerging markets. Most payment flows should support both.",{"path":731,"title":732,"description":733},"\u002Fresources\u002Fmore\u002Fvirtual-account-fees","Virtual account fees: every cost between the payer's bank and the stablecoin wallet","Monthly, deposit, wire, SWIFT, conversion, and partner fees on a virtual account: who pays each one, and a worked 10,000 USD wire to USDC example.",{"path":735,"title":736,"description":737},"\u002Fresources\u002Fmore\u002Fvisa-mastercard-stablecoin-settlement","Visa and Mastercard stablecoin settlement explained: what changed in 2025 and 2026","How Visa's USDC settlement and $7B run rate, Mastercard's BVNK deal, and INFINIOS in Bahrain change card settlement, and what stays the same for payouts.",{"path":739,"title":740,"description":741},"\u002Fresources\u002Fmore\u002Fwallet-api-vs-embedded-wallet-sdk-vs-white-label","Wallet API vs embedded SDK vs white-label: which fits?","Compare the three wallet integration models on control, launch time, engineering effort, security, lock-in, and cost, with a five-question decision tree.",{"path":743,"title":744,"description":745},"\u002Fresources\u002Fmore\u002Fpayment-blockchains-tempo-arc-explained","What are payment blockchains? Tempo, Arc, and stablecoin-native chains explained","Tempo and Arc charge fees in stablecoins and finalize in under a second. How payment blockchains differ from Ethereum and Solana, and when to use them.",{"path":78,"title":747,"description":748},"What are the types of crypto off-ramps? Payment APIs, off-ramp wallets, exchanges, OTC desks, and wallet ramps compared","The five kinds of crypto off-ramp compared: who each serves, who holds funds, limits, trade-offs, consumer vs business, and why stablecoins win.",{"path":750,"title":751,"description":752},"\u002Fresources\u002Fmore\u002Fwhat-happens-on-chain-in-a-stablecoin-payment","What happens on-chain in a stablecoin payment? A step-by-step walkthrough","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.",{"path":242,"title":754,"description":755},"What is RFQ (request for quote) in stablecoin FX, and how does it relate to payouts?","RFQ is a pricing model where a taker asks approved liquidity providers for executable quotes and takes the best. How it works in stablecoin FX and payouts.",{"path":757,"title":758,"description":759},"\u002Fresources\u002Fmore\u002Fwhat-is-usdc","What is USDC? The dollar-pegged stablecoin explained","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.",{"path":761,"title":762,"description":763},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-api","What is a stablecoin API? Infrastructure explained","A stablecoin API lets businesses move money with stablecoins through code: wallets, conversion, local payout rails, and compliance behind one integration.",{"path":765,"title":766,"description":767},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-backed-card","What is a stablecoin-backed card? How spending USDC with a card works, in plain English","A stablecoin-backed card spends USDC or USDT wherever Visa or Mastercard works. The four parts behind it, who does what, and where the money comes from.",{"path":769,"title":770,"description":771},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin","What is a stablecoin? Definition, types, and how they work","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.",{"path":773,"title":774,"description":775},"\u002Fresources\u002Fmore\u002Fwhat-is-an-off-ramp-wallet","What is an off-ramp wallet? A deposit address that pays out to a bank account","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.",{"path":777,"title":778,"description":779},"\u002Fresources\u002Fmore\u002Fwhat-is-crypto-wallet-integration","What is crypto wallet integration? A developer's guide","Crypto wallet integration adds wallets, key custody, signing, and compliance to an app. The six components, three integration models, and cost drivers.",{"path":781,"title":782,"description":783},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-card-issuing","What is stablecoin card issuing? How it works, who uses it, and how it differs from crypto debit cards","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.",{"path":785,"title":786,"description":787},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure","What is stablecoin infrastructure? The 8 layers of a stablecoin payments stack","Stablecoin infrastructure is the stack that issues, moves, converts, secures, and checks stablecoins. Here are its 8 layers and who provides each.",{"path":789,"title":790,"description":791},"\u002Fresources\u002Fmore\u002Fstablecoin-card-demand-by-country","Where stablecoin card demand is growing: the US, India, UAE, Vietnam, Pakistan, and beyond","Which countries ask AI about stablecoin cards most, why interest is rising in India, the UAE, Vietnam, and Pakistan, and where local payouts matter.",{"path":301,"title":793,"description":794},"Which network should you use to off-ramp stablecoins? Finality, fees, and confirmations by chain","How Ethereum, Polygon, Base, Arbitrum, Solana, Tron, Stellar, Tempo, and Arc compare for off-ramps: time to finality, fee model, and which tokens work.",{"path":796,"title":797,"description":798},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-for-card-spending","Which stablecoin is best for card spending? USDC vs USDT vs euro stablecoins","Which stablecoins power crypto cards in 2026: USDC vs USDT vs euro stablecoins and synthetic dollars, compared on reserves, rules, chains, and support.",{"path":800,"title":801,"description":802},"\u002Fresources\u002Fmore\u002Fwhy-onramp-and-offramp-rates-differ","Why are on-ramp and off-ramp rates different? Bid, ask, and the round-trip cost","Buying stablecoins and selling them back happen at two prices. How bid, ask, and mid-market rates work, and how to calculate a round-trip cost.",1792779564948]