[{"data":1,"prerenderedAt":842},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained":3,"resources-category-swift-pobo-vs-cobo-explained":512},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":479,"categoryType":6,"compare":6,"contributors":6,"date":480,"description":481,"extension":482,"faq":483,"howto":6,"isBlog":502,"isChangelog":502,"meta":503,"navigation":505,"path":506,"pillar":502,"products":6,"rawbody":507,"role":6,"seo":508,"seoTitle":509,"stem":510,"thumbnail":6,"updated":480,"__hash__":511},"content\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained.md","POBO vs COBO: SWIFT payments and collections on behalf of, explained",null,{"type":8,"value":9,"toc":465},"minimark",[10,14,20,54,64,69,72,83,86,90,93,192,196,199,202,205,214,217,221,224,233,242,250,254,257,260,274,277,281,284,287,304,307,315,319,322,342,355,359,362,394,401,405,408,451,458,462],[11,12,13],"p",{},"POBO (payment on behalf of) is when one entity sends a SWIFT payment for an obligation that belongs to its customer. COBO (collection on behalf of) is when it receives a payment that belongs to its customer. Both let a platform pay and collect internationally for customers who don't hold their own overseas bank accounts.",[11,15,16],{},[17,18,19],"strong",{},"Key takeaways",[21,22,23,30,36,42,48],"ul",{},[24,25,26,29],"li",{},[17,27,28],{},"POBO is outbound, COBO is inbound."," Both come from corporate treasury, where a head office pays and collects for its subsidiaries.",[24,31,32,35],{},[17,33,34],{},"The name on the account decides what the counterparty sees."," ISO 20022 has ultimate debtor and creditor fields, but you can't count on every provider or bank to fill them.",[24,37,38,41],{},[17,39,40],{},"The UETR is the tracking number."," Every Swift payment instruction carries one, and every bank in the chain uses it.",[24,43,44,47],{},[17,45,46],{},"POBO is not nesting."," It only works when the provider has onboarded the party it pays or collects for.",[24,49,50,53],{},[17,51,52],{},"Stablecoins replace the middle, not the ends."," Hybrid setups settle in stablecoins and deliver a normal SWIFT payment to the supplier.",[11,55,56,59,60,63],{},[17,57,58],{},"Definition."," ",[17,61,62],{},"POBO and COBO"," are third-party payment arrangements in which one entity pays (POBO) or collects (COBO) through its own account on behalf of another party, the ultimate debtor or ultimate creditor.",[65,66,68],"h2",{"id":67},"what-are-pobo-and-cobo","What are POBO and COBO?",[11,70,71],{},"POBO and COBO are \"on behalf of\" arrangements in which the account holder and the party that owns the money are different entities.",[11,73,74,75,82],{},"The terms come from corporate treasury. A multinational runs a payment factory: one entity pays suppliers for every subsidiary and collects from customers into one set of accounts. The ",[76,77,81],"a",{"href":78,"rel":79},"https:\u002F\u002Fwww.gleif.org\u002Flei-solutions\u002Ffeaturing-the-lei\u002Fcross-border-payments\u002Fpmpg-ultimate-parties-in-cross-border-payments_v1_0.pdf",[80],"nofollow","Payments Market Practice Group's guidelines on ultimate parties"," (November 2023) define POBO as third-party payments executed from the entity's own bank account, and COBO, also called ROBO, as third-party collections received into it.",[11,84,85],{},"Platforms now do the same thing for their customers instead of their own group companies. A marketplace pays a seller's supplier. A payroll platform collects from a client abroad. The mechanics are the same; the compliance requirements are stricter, because the customers are separate businesses.",[65,87,89],{"id":88},"how-do-pobo-and-cobo-compare","How do POBO and COBO compare?",[11,91,92],{},"POBO moves money out for a customer and COBO brings money in for a customer; most other differences follow from that direction.",[94,95,96,111],"table",{},[97,98,99],"thead",{},[100,101,102,105,108],"tr",{},[103,104],"th",{},[103,106,107],{},"POBO",[103,109,110],{},"COBO",[112,113,114,126,137,148,159,170,181],"tbody",{},[100,115,116,120,123],{},[117,118,119],"td",{},"Direction",[117,121,122],{},"Outbound",[117,124,125],{},"Inbound",[100,127,128,131,134],{},[117,129,130],{},"Who owns the obligation",[117,132,133],{},"Your customer owes the payee",[117,135,136],{},"The payer owes your customer",[100,138,139,142,145],{},[117,140,141],{},"ISO 20022 party",[117,143,144],{},"Ultimate debtor",[117,146,147],{},"Ultimate creditor",[100,149,150,153,156],{},[117,151,152],{},"What the counterparty should see",[117,154,155],{},"Your customer as the sender",[117,157,158],{},"An account that looks like your customer's",[100,160,161,164,167],{},[117,162,163],{},"Typical setup",[117,165,166],{},"An account titled for the customer, plus a payment reference",[117,168,169],{},"A per-customer account with its own beneficiary name and SWIFT details",[100,171,172,175,178],{},[117,173,174],{},"Typical documents",[117,176,177],{},"Invoice or purchase order proving the obligation",[117,179,180],{},"Sender details captured on arrival for reconciliation",[100,182,183,186,189],{},[117,184,185],{},"Main failure",[117,187,188],{},"Payee can't match the payment to an invoice",[117,190,191],{},"Payer sends to the wrong details, or funds can't be attributed",[65,193,195],{"id":194},"whose-name-appears-on-a-pobo-payment","Whose name appears on a POBO payment?",[11,197,198],{},"The name that reaches the payee is usually the name on the account that was debited, so an account titled for your customer is the reliable way to show their name.",[11,200,201],{},"ISO 20022 does give each party its own field. The PMPG guidelines note that legacy MT messages had no dedicated fields for ultimate parties, which pushed that information into free-text fields like remittance information. ISO 20022 adds structured ultimate debtor and ultimate creditor elements.",[11,203,204],{},"The catch: a structured field only helps if every party in the chain populates it and the beneficiary bank shows it. Many don't. So ask any provider two questions before promising a customer that their name will appear:",[206,207,208,211],"ol",{},[24,209,210],{},"Is the debited account titled in my customer's name, or in yours?",[24,212,213],{},"Do you populate the ultimate debtor field, or only the debtor?",[11,215,216],{},"If the answer to the first is \"ours,\" the supplier will see the provider's name and will need the payment reference to match the invoice.",[65,218,220],{"id":219},"what-does-a-swift-payment-carry-back","What does a SWIFT payment carry back?",[11,222,223],{},"A SWIFT payment carries back a UETR, a 36-character reference the sending bank assigns, and every bank in the chain uses it to report status.",[11,225,226,227,232],{},"According to ",[76,228,231],{"href":229,"rel":230},"https:\u002F\u002Fwww.swift.com\u002Fpayments\u002Fwhat-unique-end-end-transaction-reference-uetr",[80],"Swift's UETR explainer",", a UETR works like a courier tracking number: any party in the chain can locate the payment, and the sender is notified when the funds are credited or rejected. Swift made it mandatory on MT103 payment instructions from November 2018.",[11,234,235,236,241],{},"The message format changed too. Swift ended the ",[76,237,240],{"href":238,"rel":239},"https:\u002F\u002Fwww.swift.com\u002Fstandards\u002Fiso-20022\u002Fiso-20022-faqs\u002Fimplementation",[80],"MT and ISO 20022 coexistence period"," for cross-border payment instructions on November 22, 2025. Instructions now travel as ISO 20022 pacs.008 messages. Banks and finance teams still ask for \"the MT103\" as payment confirmation, and the fields map across.",[11,243,244,245,249],{},"One field matters most for POBO: remittance information (field 70 on MT103, the remittance information element on pacs.008). It is the only payer-supplied text the beneficiary's bank reliably shows as the payment reference. Put the invoice number first and keep it short, because some routes truncate it. ",[76,246,248],{"href":247},"\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout","How to track an off-ramp payout"," covers what to send a recipient who can't find a payment.",[65,251,253],{"id":252},"where-is-the-line-between-pobo-and-nested-payments","Where is the line between POBO and nested payments?",[11,255,256],{},"POBO stays compliant only when the provider can see the party the payment is for; when it can't, the arrangement is nesting.",[11,258,259],{},"The PMPG guidelines cite the Wolfsberg Group's position that on-behalf-of arrangements must be understood by the sending bank, so it can confirm the relationship is allowed under local rules. For a platform, that translates to one test:",[21,261,262,268],{},[24,263,264,267],{},[17,265,266],{},"POBO or COBO:"," your customer is onboarded with the provider, has passed KYC or KYB, and the account is in their name. The provider sees who owns the money and what it is for.",[24,269,270,273],{},[17,271,272],{},"Nesting:"," your customer uses its account to pay or collect for its own clients, whom the provider has never onboarded or screened.",[11,275,276],{},"The payment reference doesn't change the answer. If one of your customers needs to pay for its own client base, those clients need to be onboarded too.",[65,278,280],{"id":279},"how-do-stablecoins-fit-into-pobo-and-cobo","How do stablecoins fit into POBO and COBO?",[11,282,283],{},"Stablecoins can carry the value across borders while SWIFT delivers the first or last leg, so the counterparty still sees an ordinary bank payment.",[11,285,286],{},"A hybrid POBO payment looks like this:",[206,288,289,292,295,298,301],{},[24,290,291],{},"Your customer funds the payment in USDC or USDT, or from local currency converted into stablecoins.",[24,293,294],{},"The provider quotes the payment and locks the rate.",[24,296,297],{},"The stablecoin moves on-chain to the provider in seconds or minutes.",[24,299,300],{},"The provider sends a SWIFT payment from an account titled for your customer, with the invoice number in the remittance field.",[24,302,303],{},"The UETR comes back once the payment is confirmed, and you pass it to the supplier.",[11,305,306],{},"COBO runs the other way: the payer sends a SWIFT payment to a per-customer account, the funds convert to stablecoins, and the stablecoins land in your customer's wallet.",[11,308,309,310,314],{},"The supplier never touches a stablecoin. What changes is the middle: no pre-funded nostro balance and no float sitting in a correspondent account. ",[76,311,313],{"href":312},"\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","Stablecoins vs SWIFT for B2B payments"," compares the two on cost and speed.",[65,316,318],{"id":317},"how-does-blindpay-run-pobo-and-cobo","How does BlindPay run POBO and COBO?",[11,320,321],{},"BlindPay runs SWIFT (POBO\u002FCOBO) on top of a virtual account issued to a specific onboarded customer, with UETR tracking and MT103 confirmations, and settles the value in USDC or USDT.",[21,323,324,330,336],{},[24,325,326,329],{},[17,327,328],{},"COBO."," Inbound international payments need a virtual account, which carries the customer's own beneficiary name, SWIFT BIC, and account number. Incoming funds convert to USDC or USDT and go to the customer's linked wallet, and the payin reports the sender's name, bank, account, and reference.",[24,331,332,335],{},[17,333,334],{},"POBO."," The Named Account setting puts the customer's name on the payment instead of BlindPay's. BlindPay doesn't populate the ISO 20022 ultimate debtor field, so the name travels through the account title and the reference.",[24,337,338,341],{},[17,339,340],{},"Rules worth planning around."," The minimum SWIFT payout is 100 USD, the cut-off is 10:30 AM ET, and settlement takes up to 5 business days. Every SWIFT payout starts on hold, and payments to a third party need a document such as an invoice before they release. Only the first 30 characters of the description reach the beneficiary.",[11,343,344,345,349,350,354],{},"The full setup is in the ",[76,346,348],{"href":347},"\u002Fdocs\u002Fkb\u002Fpobo-cobo","POBO and COBO guide",", and the product overview is on ",[76,351,353],{"href":352},"\u002Fpobo-cobo-swift","POBO and COBO over SWIFT",".",[65,356,358],{"id":357},"when-should-you-not-use-stablecoins-for-an-on-behalf-of-payment","When should you not use stablecoins for an on-behalf-of payment?",[11,360,361],{},"Skip the stablecoin leg when it adds a step without removing a cost.",[21,363,364,370,376,382,388],{},[24,365,366,369],{},[17,367,368],{},"Domestic payments."," A US company paying a US supplier is better served by ACH or a domestic wire.",[24,371,372,375],{},[17,373,374],{},"Countries that restrict third-party payments."," Some beneficiary banks decline a payment that isn't in the invoice party's name, whatever rail funds it.",[24,377,378,381],{},[17,379,380],{},"Suppliers who require a specific bank."," If the contract names the paying bank, a provider-issued account won't satisfy it.",[24,383,384,387],{},[17,385,386],{},"Very small payments."," Below a SWIFT minimum, use a local rail or batch the invoices.",[24,389,390,393],{},[17,391,392],{},"No one owns the documents."," If nobody on your side can produce invoices on request, third-party SWIFT payments will sit on hold.",[11,395,396,400],{},[76,397,399],{"href":398},"\u002Fresources\u002Fmore\u002Fwhen-not-to-use-blockchain-payments","When not to use blockchain payments"," covers the broader cases.",[65,402,404],{"id":403},"how-do-you-choose-a-rail-for-a-payment-on-behalf-of-a-customer","How do you choose a rail for a payment on behalf of a customer?",[11,406,407],{},"Pick by the corridor, the amount, and how the counterparty wants to be paid.",[206,409,410,416,422,428,434,440],{},[24,411,412,415],{},[17,413,414],{},"Does the recipient's country have an instant local rail the provider pays out to?"," If yes, a local payout usually beats SWIFT on speed and cost.",[24,417,418,421],{},[17,419,420],{},"Does the supplier insist on a wire?"," Then SWIFT delivers the last leg, with stablecoins or a bank balance funding it.",[24,423,424,427],{},[17,425,426],{},"Is the amount above the provider's SWIFT minimum?"," If not, batch or use a local rail.",[24,429,430,433],{},[17,431,432],{},"Can you produce the invoice?"," Third-party SWIFT payments need one.",[24,435,436,439],{},[17,437,438],{},"Does your customer's name need to show?"," Confirm the account is titled for them before you promise it.",[24,441,442,445,446,450],{},[17,443,444],{},"How urgent is it?"," SWIFT can take several business days; budget for cut-offs and weekends. ",[76,447,449],{"href":448},"\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow","Why cross-border payments are slow"," explains where the days go.",[11,452,453,454,354],{},"For how payout APIs, wallet APIs, and issuer APIs divide these jobs, see ",[76,455,457],{"href":456},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","types of stablecoin APIs",[65,459,461],{"id":460},"what-should-you-do-next","What should you do next?",[11,463,464],{},"List the customers you pay or collect for today and check each one against the nesting test. Then confirm with your provider whose name appears on the payment and where the invoice reference lands. Fix those two before the first supplier calls asking who sent the money.",{"title":466,"searchDepth":467,"depth":467,"links":468},"",2,[469,470,471,472,473,474,475,476,477,478],{"id":67,"depth":467,"text":68},{"id":88,"depth":467,"text":89},{"id":194,"depth":467,"text":195},{"id":219,"depth":467,"text":220},{"id":252,"depth":467,"text":253},{"id":279,"depth":467,"text":280},{"id":317,"depth":467,"text":318},{"id":357,"depth":467,"text":358},{"id":403,"depth":467,"text":404},{"id":460,"depth":467,"text":461},"payments","2026-09-30","POBO sends a SWIFT payment for a customer, COBO collects one for them. Whose name shows, how UETR tracking works, and where stablecoin settlement fits.","md",[484,487,490,493,496,499],{"q":485,"a":486},"What is the difference between POBO and COBO?","POBO, payment on behalf of, is outbound: one entity sends a payment from its own account for an obligation that belongs to someone else. COBO, collection on behalf of, is inbound: one entity receives a payment into its account that economically belongs to someone else. Both come from corporate treasury, where a parent pays and collects for its subsidiaries through one account.",{"q":488,"a":489},"Whose name does the supplier see on a POBO payment?","It depends on how the payment is built. Under ISO 20022 the message can name an ultimate debtor separately from the account holder, but many providers don't populate that field. In practice the payee sees the name on the account that was debited, so the reliable way to show your customer's name is an account titled in your customer's name, plus a clear payment reference.",{"q":491,"a":492},"What is a UETR and why does it matter for POBO?","A UETR, or Unique End-to-end Transaction Reference, is a 36-character identifier carried in every Swift payment instruction. Every bank in the chain refers to the payment by the same UETR, so the sender, the receiver, and each correspondent can trace the same payment. For POBO it is the number you give a supplier who says the money never arrived.",{"q":494,"a":495},"Is MT103 still used after Swift's ISO 20022 migration?","Swift ended the MT and ISO 20022 coexistence period for cross-border payment instructions on November 22, 2025, so banks now exchange those instructions as ISO 20022 messages such as pacs.008. Many banks and customers still call the payment confirmation an MT103, and the familiar fields map across: the MT103 field 70 remittance information becomes the remittance information element in pacs.008.",{"q":497,"a":498},"Is POBO the same as nested payments?","No. POBO is legitimate when the provider can see the party it is paying for: that party is onboarded, verified, and holds an account in its own name. Nesting is when a customer uses its account to move money for its own clients, whom the provider never onboarded or screened. The mechanics look alike. The visibility is what separates them.",{"q":500,"a":501},"Can stablecoins replace SWIFT for POBO and COBO?","Not fully. Stablecoin settlement can replace the expensive middle of the payment, but a supplier who invoices in dollars and banks with a correspondent-connected bank still expects a SWIFT payment. Hybrid setups settle the value in stablecoins and deliver the last leg as a SWIFT payment, so the supplier sees an ordinary wire with a UETR.",false,{"author":504},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained","---\ntitle: \"POBO vs COBO: SWIFT payments and collections on behalf of, explained\"\nseoTitle: \"POBO vs COBO: SWIFT payments on behalf of, explained\"\ndescription: \"POBO sends a SWIFT payment for a customer, COBO collects one for them. Whose name shows, how UETR tracking works, and where stablecoin settlement fits.\"\ndate: \"2026-09-30\"\nupdated: \"2026-09-30\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the difference between POBO and COBO?\"\n    a: \"POBO, payment on behalf of, is outbound: one entity sends a payment from its own account for an obligation that belongs to someone else. COBO, collection on behalf of, is inbound: one entity receives a payment into its account that economically belongs to someone else. Both come from corporate treasury, where a parent pays and collects for its subsidiaries through one account.\"\n  - q: \"Whose name does the supplier see on a POBO payment?\"\n    a: \"It depends on how the payment is built. Under ISO 20022 the message can name an ultimate debtor separately from the account holder, but many providers don't populate that field. In practice the payee sees the name on the account that was debited, so the reliable way to show your customer's name is an account titled in your customer's name, plus a clear payment reference.\"\n  - q: \"What is a UETR and why does it matter for POBO?\"\n    a: \"A UETR, or Unique End-to-end Transaction Reference, is a 36-character identifier carried in every Swift payment instruction. Every bank in the chain refers to the payment by the same UETR, so the sender, the receiver, and each correspondent can trace the same payment. For POBO it is the number you give a supplier who says the money never arrived.\"\n  - q: \"Is MT103 still used after Swift's ISO 20022 migration?\"\n    a: \"Swift ended the MT and ISO 20022 coexistence period for cross-border payment instructions on November 22, 2025, so banks now exchange those instructions as ISO 20022 messages such as pacs.008. Many banks and customers still call the payment confirmation an MT103, and the familiar fields map across: the MT103 field 70 remittance information becomes the remittance information element in pacs.008.\"\n  - q: \"Is POBO the same as nested payments?\"\n    a: \"No. POBO is legitimate when the provider can see the party it is paying for: that party is onboarded, verified, and holds an account in its own name. Nesting is when a customer uses its account to move money for its own clients, whom the provider never onboarded or screened. The mechanics look alike. The visibility is what separates them.\"\n  - q: \"Can stablecoins replace SWIFT for POBO and COBO?\"\n    a: \"Not fully. Stablecoin settlement can replace the expensive middle of the payment, but a supplier who invoices in dollars and banks with a correspondent-connected bank still expects a SWIFT payment. Hybrid setups settle the value in stablecoins and deliver the last leg as a SWIFT payment, so the supplier sees an ordinary wire with a UETR.\"\n---\n\nPOBO (payment on behalf of) is when one entity sends a SWIFT payment for an obligation that belongs to its customer. COBO (collection on behalf of) is when it receives a payment that belongs to its customer. Both let a platform pay and collect internationally for customers who don't hold their own overseas bank accounts.\n\n**Key takeaways**\n\n- **POBO is outbound, COBO is inbound.** Both come from corporate treasury, where a head office pays and collects for its subsidiaries.\n- **The name on the account decides what the counterparty sees.** ISO 20022 has ultimate debtor and creditor fields, but you can't count on every provider or bank to fill them.\n- **The UETR is the tracking number.** Every Swift payment instruction carries one, and every bank in the chain uses it.\n- **POBO is not nesting.** It only works when the provider has onboarded the party it pays or collects for.\n- **Stablecoins replace the middle, not the ends.** Hybrid setups settle in stablecoins and deliver a normal SWIFT payment to the supplier.\n\n**Definition.** **POBO and COBO** are third-party payment arrangements in which one entity pays (POBO) or collects (COBO) through its own account on behalf of another party, the ultimate debtor or ultimate creditor.\n\n## What are POBO and COBO?\n\nPOBO and COBO are \"on behalf of\" arrangements in which the account holder and the party that owns the money are different entities.\n\nThe terms come from corporate treasury. A multinational runs a payment factory: one entity pays suppliers for every subsidiary and collects from customers into one set of accounts. The [Payments Market Practice Group's guidelines on ultimate parties](https:\u002F\u002Fwww.gleif.org\u002Flei-solutions\u002Ffeaturing-the-lei\u002Fcross-border-payments\u002Fpmpg-ultimate-parties-in-cross-border-payments_v1_0.pdf) (November 2023) define POBO as third-party payments executed from the entity's own bank account, and COBO, also called ROBO, as third-party collections received into it.\n\nPlatforms now do the same thing for their customers instead of their own group companies. A marketplace pays a seller's supplier. A payroll platform collects from a client abroad. The mechanics are the same; the compliance requirements are stricter, because the customers are separate businesses.\n\n## How do POBO and COBO compare?\n\nPOBO moves money out for a customer and COBO brings money in for a customer; most other differences follow from that direction.\n\n| | POBO | COBO |\n| --- | --- | --- |\n| Direction | Outbound | Inbound |\n| Who owns the obligation | Your customer owes the payee | The payer owes your customer |\n| ISO 20022 party | Ultimate debtor | Ultimate creditor |\n| What the counterparty should see | Your customer as the sender | An account that looks like your customer's |\n| Typical setup | An account titled for the customer, plus a payment reference | A per-customer account with its own beneficiary name and SWIFT details |\n| Typical documents | Invoice or purchase order proving the obligation | Sender details captured on arrival for reconciliation |\n| Main failure | Payee can't match the payment to an invoice | Payer sends to the wrong details, or funds can't be attributed |\n\n## Whose name appears on a POBO payment?\n\nThe name that reaches the payee is usually the name on the account that was debited, so an account titled for your customer is the reliable way to show their name.\n\nISO 20022 does give each party its own field. The PMPG guidelines note that legacy MT messages had no dedicated fields for ultimate parties, which pushed that information into free-text fields like remittance information. ISO 20022 adds structured ultimate debtor and ultimate creditor elements.\n\nThe catch: a structured field only helps if every party in the chain populates it and the beneficiary bank shows it. Many don't. So ask any provider two questions before promising a customer that their name will appear:\n\n1. Is the debited account titled in my customer's name, or in yours?\n2. Do you populate the ultimate debtor field, or only the debtor?\n\nIf the answer to the first is \"ours,\" the supplier will see the provider's name and will need the payment reference to match the invoice.\n\n## What does a SWIFT payment carry back?\n\nA SWIFT payment carries back a UETR, a 36-character reference the sending bank assigns, and every bank in the chain uses it to report status.\n\nAccording to [Swift's UETR explainer](https:\u002F\u002Fwww.swift.com\u002Fpayments\u002Fwhat-unique-end-end-transaction-reference-uetr), a UETR works like a courier tracking number: any party in the chain can locate the payment, and the sender is notified when the funds are credited or rejected. Swift made it mandatory on MT103 payment instructions from November 2018.\n\nThe message format changed too. Swift ended the [MT and ISO 20022 coexistence period](https:\u002F\u002Fwww.swift.com\u002Fstandards\u002Fiso-20022\u002Fiso-20022-faqs\u002Fimplementation) for cross-border payment instructions on November 22, 2025. Instructions now travel as ISO 20022 pacs.008 messages. Banks and finance teams still ask for \"the MT103\" as payment confirmation, and the fields map across.\n\nOne field matters most for POBO: remittance information (field 70 on MT103, the remittance information element on pacs.008). It is the only payer-supplied text the beneficiary's bank reliably shows as the payment reference. Put the invoice number first and keep it short, because some routes truncate it. [How to track an off-ramp payout](\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout) covers what to send a recipient who can't find a payment.\n\n## Where is the line between POBO and nested payments?\n\nPOBO stays compliant only when the provider can see the party the payment is for; when it can't, the arrangement is nesting.\n\nThe PMPG guidelines cite the Wolfsberg Group's position that on-behalf-of arrangements must be understood by the sending bank, so it can confirm the relationship is allowed under local rules. For a platform, that translates to one test:\n\n- **POBO or COBO:** your customer is onboarded with the provider, has passed KYC or KYB, and the account is in their name. The provider sees who owns the money and what it is for.\n- **Nesting:** your customer uses its account to pay or collect for its own clients, whom the provider has never onboarded or screened.\n\nThe payment reference doesn't change the answer. If one of your customers needs to pay for its own client base, those clients need to be onboarded too.\n\n## How do stablecoins fit into POBO and COBO?\n\nStablecoins can carry the value across borders while SWIFT delivers the first or last leg, so the counterparty still sees an ordinary bank payment.\n\nA hybrid POBO payment looks like this:\n\n1. Your customer funds the payment in USDC or USDT, or from local currency converted into stablecoins.\n2. The provider quotes the payment and locks the rate.\n3. The stablecoin moves on-chain to the provider in seconds or minutes.\n4. The provider sends a SWIFT payment from an account titled for your customer, with the invoice number in the remittance field.\n5. The UETR comes back once the payment is confirmed, and you pass it to the supplier.\n\nCOBO runs the other way: the payer sends a SWIFT payment to a per-customer account, the funds convert to stablecoins, and the stablecoins land in your customer's wallet.\n\nThe supplier never touches a stablecoin. What changes is the middle: no pre-funded nostro balance and no float sitting in a correspondent account. [Stablecoins vs SWIFT for B2B payments](\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments) compares the two on cost and speed.\n\n## How does BlindPay run POBO and COBO?\n\nBlindPay runs SWIFT (POBO\u002FCOBO) on top of a virtual account issued to a specific onboarded customer, with UETR tracking and MT103 confirmations, and settles the value in USDC or USDT.\n\n- **COBO.** Inbound international payments need a virtual account, which carries the customer's own beneficiary name, SWIFT BIC, and account number. Incoming funds convert to USDC or USDT and go to the customer's linked wallet, and the payin reports the sender's name, bank, account, and reference.\n- **POBO.** The Named Account setting puts the customer's name on the payment instead of BlindPay's. BlindPay doesn't populate the ISO 20022 ultimate debtor field, so the name travels through the account title and the reference.\n- **Rules worth planning around.** The minimum SWIFT payout is 100 USD, the cut-off is 10:30 AM ET, and settlement takes up to 5 business days. Every SWIFT payout starts on hold, and payments to a third party need a document such as an invoice before they release. Only the first 30 characters of the description reach the beneficiary.\n\nThe full setup is in the [POBO and COBO guide](\u002Fdocs\u002Fkb\u002Fpobo-cobo), and the product overview is on [POBO and COBO over SWIFT](\u002Fpobo-cobo-swift).\n\n## When should you not use stablecoins for an on-behalf-of payment?\n\nSkip the stablecoin leg when it adds a step without removing a cost.\n\n- **Domestic payments.** A US company paying a US supplier is better served by ACH or a domestic wire.\n- **Countries that restrict third-party payments.** Some beneficiary banks decline a payment that isn't in the invoice party's name, whatever rail funds it.\n- **Suppliers who require a specific bank.** If the contract names the paying bank, a provider-issued account won't satisfy it.\n- **Very small payments.** Below a SWIFT minimum, use a local rail or batch the invoices.\n- **No one owns the documents.** If nobody on your side can produce invoices on request, third-party SWIFT payments will sit on hold.\n\n[When not to use blockchain payments](\u002Fresources\u002Fmore\u002Fwhen-not-to-use-blockchain-payments) covers the broader cases.\n\n## How do you choose a rail for a payment on behalf of a customer?\n\nPick by the corridor, the amount, and how the counterparty wants to be paid.\n\n1. **Does the recipient's country have an instant local rail the provider pays out to?** If yes, a local payout usually beats SWIFT on speed and cost.\n2. **Does the supplier insist on a wire?** Then SWIFT delivers the last leg, with stablecoins or a bank balance funding it.\n3. **Is the amount above the provider's SWIFT minimum?** If not, batch or use a local rail.\n4. **Can you produce the invoice?** Third-party SWIFT payments need one.\n5. **Does your customer's name need to show?** Confirm the account is titled for them before you promise it.\n6. **How urgent is it?** SWIFT can take several business days; budget for cut-offs and weekends. [Why cross-border payments are slow](\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow) explains where the days go.\n\nFor how payout APIs, wallet APIs, and issuer APIs divide these jobs, see [types of stablecoin APIs](\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis).\n\n## What should you do next?\n\nList the customers you pay or collect for today and check each one against the nesting test. Then confirm with your provider whose name appears on the payment and where the invoice reference lands. Fix those two before the first supplier calls asking who sent the money.\n",{"title":5,"description":481},"POBO vs COBO: SWIFT payments on behalf of, explained","resources\u002Fmore\u002Fswift-pobo-vs-cobo-explained","4kcKlSj1MvFfonQrB9KnaXZQ2dsSbo8tqgvdjYIL-4U",[513,517,521,525,529,533,537,541,545,549,553,557,561,565,569,573,577,581,585,589,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,690,694,698,702,706,710,714,718,722,726,730,734,738,742,746,750,754,758,762,765,769,773,777,781,785,789,793,797,801,805,809,813,817,821,825,829,832,835,838],{"path":514,"title":515,"description":516},"\u002Fresources\u002Fmore\u002Fblockchain-payment-use-cases","7 real-world blockchain payment use cases: payroll, remittances, B2B, and more","Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24\u002F7 treasury, bill pay, and PSP payouts.",{"path":518,"title":519,"description":520},"\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared","AP2 vs ACP vs x402: agent payment protocols compared","AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.",{"path":522,"title":523,"description":524},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026","Best stablecoin payment platforms for fintech in 2026: a US comparison","Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.",{"path":526,"title":527,"description":528},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","Best stablecoin payment providers in 2026: how to choose","How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.",{"path":530,"title":531,"description":532},"\u002Fresources\u002Fmore\u002Fwhat-are-blockchain-payments","Blockchain payments explained: how stablecoins move money without correspondent banks","Blockchain payments move a stablecoin on a public ledger instead of messages between banks. How they work, what they cost, and how they compare with SWIFT.",{"path":534,"title":535,"description":536},"\u002Fresources\u002Fmore\u002Fblockchain-payments-glossary","Blockchain payments glossary: 34 terms explained in plain English","Stablecoin, on-ramp, off-ramp, finality, gas, non-custodial, travel rule. The 34 terms of blockchain payments, each defined in one or two lines.",{"path":538,"title":539,"description":540},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","Build vs buy: should you build stablecoin payouts in-house or use an API?","Building stablecoin payouts in-house means wallets, liquidity, banking partners, licenses, and a compliance program. When building makes sense.",{"path":542,"title":543,"description":544},"\u002Fresources\u002Fmore\u002Fcan-a-virtual-account-replace-a-bank-account","Can a virtual account replace a business bank account? What each one does for cross-border companies","Usually not. A virtual account collects and settles payments; a bank account runs payroll, taxes, and credit. A job-by-job guide for cross-border teams.",{"path":546,"title":547,"description":548},"\u002Fresources\u002Fmore\u002Flatam-payout-liquidity-partner-pix-spei","Choosing a liquidity partner for LatAm payouts: Pix, SPEI, and beyond","How to choose a liquidity partner for payouts into Latin America: how Pix and SPEI work, how a stablecoin liquidity layer replaces local bank accounts, and a checklist for coverage, pricing, and compliance.",{"path":550,"title":551,"description":552},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes","Common stablecoin payout mistakes: wrong network, expired quotes, and bad bank details","The mistakes that make stablecoin payouts fail or stall: wrong network or token, expired quotes, deposits below minimums, bad bank details, and cut-offs.",{"path":554,"title":555,"description":556},"\u002Fresources\u002Fmore\u002Fcorrespondent-banking-vs-stablecoin-liquidity","Correspondent banking vs stablecoin liquidity: why pre-funding traps your capital","Correspondent banking keeps cross-border payouts liquid by parking cash in nostro accounts in every country. What that trapped capital costs a treasury team, and what stablecoin liquidity changes.",{"path":558,"title":559,"description":560},"\u002Fresources\u002Fmore\u002Fcrypto-payment-processor-for-businesses","Crypto payment processor for businesses: what to compare before you choose","Compare crypto payment processors on six criteria: settlement speed, stablecoins, compliance, dev effort, payout coverage, and pricing. Scorecard inside.",{"path":562,"title":563,"description":564},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps","Custodial vs non-custodial off-ramps: who holds the money, and what happens if the provider fails","A custodial off-ramp holds your stablecoins; a non-custodial one pulls them only at payout. What changes in insolvency, de-banking, and failed payouts.",{"path":566,"title":567,"description":568},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets","Custodial vs non-custodial vs MPC wallets: how to choose","Custodial, non-custodial, and MPC wallets differ in who holds the keys. Compare control, recovery, risk, and regulation, with product examples for each.",{"path":570,"title":571,"description":572},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-cut-off-times-weekends-holidays","Do stablecoin payouts work on weekends and holidays? Cut-offs and bank calendars by rail","The stablecoin leg runs 24\u002F7, and so do Pix, SPEI, and RTP. ACH, wire, SEPA, TED, and SWIFT wait for a business day. Cut-offs and calendars by rail.",{"path":574,"title":575,"description":576},"\u002Fresources\u002Fmore\u002Fstablecoin-cross-border-payments-savings","How businesses use stablecoins for cross-border payments (and where the savings come from)","Correspondent hops, FX markup, and pre-funding: what stablecoin settlement does to each cost of a cross-border payment, with a $50,000 example to Brazil.",{"path":578,"title":579,"description":580},"\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works","How does a stablecoin payment move? From bank deposit to local payout, step by step","A stablecoin payment moves in legs: fiat collected, stablecoin settled, fiat paid out. What happens at each step, where delays hide, what recipients see.",{"path":582,"title":583,"description":584},"\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding","How global merchants get paid across borders with stablecoins, no pre-funding required","Pre-funding means parking local currency in every market before money moves. Stablecoin virtual accounts remove it. A worked example across 4 countries.",{"path":586,"title":587,"description":588},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times","How long does a stablecoin payout take? Settlement times by country and rail","Stablecoin payouts settle in minutes on Pix, SPEI, RTP, and Transfers 3.0, and in 1 to 5 business days on ACH, SEPA, and SWIFT. Full table by rail.",{"path":590,"title":591,"description":592},"\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-fees-explained","How much does a crypto on-ramp cost? Fees, spreads, and how to read a quote","A crypto on-ramp charges through the rate spread, a service fee, the payment rail, and sometimes the network. How each works, and how to read the quote.",{"path":594,"title":595,"description":596},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-fees-explained","How much does a stablecoin off-ramp cost? Fees per transaction vs a bank wire","What a stablecoin off-ramp costs per transaction: network fee, FX spread, percentage and flat fees, worked at $200, $2,000, and $20,000 vs a bank wire.",{"path":598,"title":599,"description":600},"\u002Fresources\u002Fmore\u002Fhow-to-add-stablecoin-payments-to-your-wallet-integration","How to add stablecoin payments to your wallet integration","Connect the wallets you already run to bank deposits and local payouts: register addresses, open virtual accounts, quote, authorize, and track webhooks.",{"path":602,"title":603,"description":604},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-virtual-account-provider","How to choose a virtual account provider: a 12-point checklist for developers and finance teams","Twelve criteria for evaluating a virtual account API, from rails and naming to custody, webhooks, and pricing, plus red flags and a scorecard to copy.",{"path":606,"title":607,"description":608},"\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","How to choose the best on\u002Foff ramp provider for your fintech app","Six criteria for evaluating a crypto on\u002Foff ramp provider: corridor coverage, live quotes, fiat settlement speed, licensing, API quality, and liquidity depth. Each with concrete tests to run, a comparison table, and a scoring framework.",{"path":610,"title":611,"description":612},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","How to evaluate a payment orchestration platform for cross-border payments","Six criteria that decide whether an orchestration platform works for cross-border money: rail coverage, compliance per corridor, developer experience, settlement speed, FX transparency, and pricing.",{"path":614,"title":615,"description":616},"\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan","How to evaluate a stablecoin API in 30 days: a week-by-week plan","A 30-day plan to evaluate a stablecoin API: shortlist, sandbox tests, compliance review, and a live pilot, plus where costs hide and a worked cost model.",{"path":618,"title":619,"description":620},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api","How to integrate a crypto on-ramp API: payin quotes, deposit instructions, and webhooks","The on-ramp API flow step by step: verify the customer, pick the wallet, quote, create the payin, show deposit instructions, and handle webhooks.",{"path":622,"title":623,"description":624},"\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","How to issue stablecoin-funded cards through an API: a developer's guide","Build vs. buy for stablecoin card issuing, the objects a card issuing API must expose, a step-by-step integration flow, and where KYC and KYB sit in it.",{"path":626,"title":627,"description":628},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-us-bank-account","How to off-ramp USDC to a US bank account: ACH, RTP, or wire","Cashing out USDC or USDT to a US bank account: when ACH, Same Day ACH, RTP, and wire pay out, the cut-offs in ET, the fields you need, and what delays it.",{"path":630,"title":631,"description":632},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-euros-sepa","How to off-ramp USDC to euros over SEPA: networks, IBAN details, and timing","Converting USDC to EUR in a SEPA bank account: which networks work, the IBAN details you need, SEPA vs SEPA Instant timing, limits, and what MiCA changes.",{"path":634,"title":635,"description":636},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdt-latin-america","How to off-ramp USDT to local currency in Latin America","Converting USDT to BRL, MXN, ARS, or COP: which networks work, the payout rail in each country, weekend timing, fees, and the documents a business needs.",{"path":638,"title":639,"description":640},"\u002Fresources\u002Fmore\u002Fhow-to-on-ramp-local-currency-latin-america","How to on-ramp BRL, MXN, ARS, and COP into stablecoins: Pix, SPEI, Transfers 3.0, and PSE","How Latin American bank payments become USDC or USDT: what each rail shows the payer, the payer data it needs, how fast it lands, and the traps by country.",{"path":642,"title":643,"description":644},"\u002Fresources\u002Fmore\u002Fhow-to-pay-invoices-with-stablecoins-api","How to pay invoices, boletos, and Pix codes with stablecoins through an API","Register the bill, quote it, pay it from USDC or USDT, and track two webhook streams. A developer guide to stablecoin bill pay, boleto gotchas included.",{"path":646,"title":647,"description":648},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","How to send USDC to a bank account in Brazil","Step-by-step: convert USDC to Brazilian reais and deliver them to a bank account over Pix using a stablecoin payout API. Quote, verify, send, settle in minutes.",{"path":650,"title":651,"description":652},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI","Send USDC to a Mexican bank account: verify the recipient, quote in pesos, fund from a wallet, and confirm on SPEI. Recipient data, statuses, and failures.",{"path":654,"title":655,"description":656},"\u002Fresources\u002Fmore\u002Fhow-to-test-virtual-accounts-sandbox","How to test a virtual accounts API integration before going live","The integration sequence for a virtual accounts API, what a sandbox simulates and what it can't, and a test plan with the statuses and webhooks to expect.",{"path":658,"title":659,"description":660},"\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation","How virtual accounts automate payment reconciliation (with a worked example)","Virtual accounts match each deposit to a customer by account number, not a free-text reference. A worked example with partial payments and micro-deposits.",{"path":662,"title":663,"description":664},"\u002Fresources\u002Fmore\u002Fstablecoin-api-idempotency-keys","Idempotency keys in a stablecoin API: how to never send the same payout twice","A timeout on a payout call is the most common way to pay someone twice. How idempotency keys prevent it, what replays, what conflicts, and how to retry.",{"path":666,"title":667,"description":668},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api","Integrating a stablecoin API: a developer's guide to cross-border payments with BlindPay","Step-by-step integration of a stablecoin API: authenticate, onboard a customer, create a virtual USD account, quote and send a cross-border payout, and handle signed webhooks. Endpoints, statuses, and SDKs for BlindPay.",{"path":670,"title":671,"description":672},"\u002Fresources\u002Fmore\u002Fliquidity-risk-global-payouts","Managing liquidity risk in global payouts: a practical guide for fintechs and PSPs","Liquidity risk in payouts is the chance funds aren't available at the right rate, in the right currency, when a payout settles. Its four sources and a six-step framework to manage them.",{"path":674,"title":675,"description":676},"\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","Marketplace payouts in Latin America: stablecoin rails for sellers in Brazil, Mexico, Colombia, and Argentina","How marketplaces pay sellers, creators, and vendors across Latin America with stablecoin settlement: supported rails (Pix, SPEI, PSE, Argentine transfers), the end-to-end payout workflow, API integration, and what changes for speed, minimums, and FX cost.",{"path":678,"title":679,"description":680},"\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained","Non-custodial payments: what they are and why they reduce risk for businesses","A non-custodial payment provider moves your money without holding it between payments. Who controls the funds, who carries the risk, and what to ask.",{"path":682,"title":683,"description":684},"\u002Fresources\u002Fmore\u002Fon-ramp-or-off-ramp-which-does-your-product-need","On-ramp, off-ramp, or both? How to tell which stablecoin API your product needs","Match your use case to the direction money moves: on-ramp, off-ramp, or both. Covers payroll, remittance, marketplaces, treasury, and 10 questions to ask.",{"path":686,"title":687,"description":688},"\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","On\u002Foff ramp liquidity with live quotes: how it works and why it matters","What on\u002Foff ramp liquidity with live quotes means for developers: live quote vs batch rate, the quote ID flow in an API, what happens on expiry, how liquidity depth changes spread by transaction size, rate windows and UX, and a checklist for evaluating a live quote API.",{"path":506,"title":5,"description":481},{"path":691,"title":692,"description":693},"\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","Payment orchestration vs payment gateway: what's the difference?","A gateway connects you to one processor. An orchestration platform connects to many rails and picks the best path per transaction. The table, the triggers, and a worked USD to BRL example.",{"path":695,"title":696,"description":697},"\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks","Stablecoin API SDKs: how one OpenAPI spec keeps five languages in sync","BlindPay's stablecoin API is described by one OpenAPI 3.1 spec that drives validation, docs, SDKs for Node, Python, Go, PHP, and Swift, and the MCP server.",{"path":699,"title":700,"description":701},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","Stablecoin API SLAs and settlement finality explained","Stablecoin API uptime numbers cluster near 99.9% for a reason: most providers measure API acceptance instead of the point where money becomes final and spendable.",{"path":703,"title":704,"description":705},"\u002Fresources\u002Fmore\u002Fstablecoin-api-objects-explained","Stablecoin API objects explained: customers, bank accounts, wallets, quotes, payouts, and webhooks","The core objects behind a stablecoin API, how they relate, which IDs to store in your ledger, and 8 data-model mistakes that break payout integrations.",{"path":707,"title":708,"description":709},"\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained","Stablecoin API quotes explained: expiry, fee direction, and minor units","A stablecoin API quote locks the rate, fees, and amounts for a few minutes. How expiry works, which side pays the fee, and the field that flips meaning.",{"path":711,"title":712,"description":713},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Stablecoin API sandbox vs production: what testing misses","Most stablecoin API sandboxes pass every integration test and still leave a team unprepared for production, because webhook delivery and idempotent retries are exactly what sandboxes fake or skip.",{"path":715,"title":716,"description":717},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","Stablecoin API webhooks: signature checks, duplicate events, and reconciliation","How to handle stablecoin API webhooks in production: verify signatures on raw bytes, dedupe retries, never regress a final status, reconcile daily.",{"path":719,"title":720,"description":721},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","Stablecoin FX slippage: how live quotes turn the quoted rate into the rate you get","FX slippage is the gap between the rate a stablecoin on-ramp or off-ramp shows and the rate that settles. Why quote freshness is a liquidity signal, and how to check a quote-then-execute flow.",{"path":723,"title":724,"description":725},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america","Stablecoin cards in Latin America: how they work in Brazil, Mexico, Argentina, and Colombia","How USD stablecoin cards work in Brazil, Mexico, Argentina, and Colombia: local card and crypto rules, costs at the point of sale, and when a Pix or SPEI payout fits better.",{"path":727,"title":728,"description":729},"\u002Fresources\u002Fmore\u002Fstablecoin-liquidity-provider-vs-fx-desk","Stablecoin liquidity providers vs traditional FX desks: what finance teams should know","A bank FX desk prices cross-border payouts by relationship. A stablecoin liquidity provider prices them by API. How the two compare on cost, speed, minimums, coverage, and compliance.",{"path":731,"title":732,"description":733},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees","Stablecoin payment fees vs credit card processing fees: what merchants actually pay","Cards cost merchants 1.5% to 3.5% plus cross-border, FX, and chargeback fees. Stablecoin payments cost cents on-chain plus a sub-percent conversion spread.",{"path":735,"title":736,"description":737},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide","Stablecoin payments explained: a guide for businesses","Stablecoin payments move dollar-pegged tokens between parties and settle in minutes, 24\u002F7. How they work, what they cost, and how businesses accept and send them.",{"path":739,"title":740,"description":741},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained","Stablecoin payout statuses explained: processing, on hold, completed, failed, and refunded","What each stablecoin payout status means, which are final, why an on-chain confirmation isn't a completed payout, and how to test every failure.",{"path":743,"title":744,"description":745},"\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","Stablecoin payroll for LATAM contractors: how it actually works in 2026","How US companies pay contractors in Argentina, Brazil, Mexico, and Colombia with stablecoins in 2026: USDC vs USDT, the step-by-step payout flow, US tax reporting, a platform comparison, and how to start.",{"path":747,"title":748,"description":749},"\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants","Stablecoin settlement explained: how merchants get paid faster than card networks","Stablecoin payments settle in seconds to minutes, final and 24\u002F7. Cards take 1 to 3 business days and wires up to 5. How it works and how to cash out.",{"path":751,"title":752,"description":753},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","Stablecoin virtual accounts explained: from bank transfer to wallet balance","A stablecoin virtual account is a bank account in your customer's name whose deposits convert to USDC or USDT. How approval, deposits, and fees work.",{"path":755,"title":756,"description":757},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","Stablecoin-funded virtual cards vs. traditional virtual cards for cross-border payouts","Stablecoin-funded vs. bank-funded virtual cards for paying contractors and vendors abroad: funding speed, pre-funding, FX cost, settlement finality, and a Brazil walkthrough.",{"path":759,"title":760,"description":761},"\u002Fresources\u002Fmore\u002Fstablecoins-local-rails-latin-america","Stablecoins plus local rails: how cross-border payments actually land in Latin America","A stablecoin crosses the border in seconds, but the payment lands over Pix, SPEI, or another local rail. How that last mile works in Brazil and Mexico.",{"path":312,"title":763,"description":764},"Stablecoins vs SWIFT for B2B cross-border payments: a real comparison","Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes for business payments in 2026.",{"path":766,"title":767,"description":768},"\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026","USDC to ARS in 2026: routes, fees, and rules compared","Four ways to convert USDC to Argentine pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Transfers 3.0. Fees, speed, KYC, and Argentina's PSAV rules compared.",{"path":770,"title":771,"description":772},"\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026","USDC to BRL in 2026: routes, fees, and rules compared","Four ways to convert USDC to Brazilian reais in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Pix. Fees, speed, KYC, and Brazil's VASP rules compared.",{"path":774,"title":775,"description":776},"\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026","USDC to COP in 2026: routes, fees, and rules compared","Four ways to convert USDC to Colombian pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with PSE. Fees, speed, KYC, and Colombia's VASP rules compared.",{"path":778,"title":779,"description":780},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN in 2026: routes, fees, and rules compared","Four ways to convert USDC to Mexican pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with SPEI. Fees, speed, KYC, and Mexico's rules compared.",{"path":782,"title":783,"description":784},"\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received","Virtual account deposit not received? Why deposits get delayed, held, or returned","Why a virtual account deposit is late, on hold, or returned: arrival windows, payin statuses, RFIs, wrong rails, and how to trace a wire or SWIFT payment.",{"path":786,"title":787,"description":788},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-virtual-iban","Virtual account vs virtual IBAN vs real bank account: what's the difference?","A real account holds funds for one holder. A virtual account routes deposits into a master account. A virtual IBAN is the IBAN version. When to use each.",{"path":790,"title":791,"description":792},"\u002Fresources\u002Fmore\u002Fvirtual-accounts-cross-border-payments","Virtual accounts for cross-border payments: use cases, payment rails, and costs","How virtual accounts let payers abroad pay a local-style account, which rails collect and pay out, what drives the cost, and five questions to ask.",{"path":794,"title":795,"description":796},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","Virtual accounts vs one-time deposit instructions: how to collect bank transfers as stablecoins","One-time deposit instructions suit occasional payers and local rails. Virtual accounts suit repeat US payers. How each matches deposits and when to switch.",{"path":798,"title":799,"description":800},"\u002Fresources\u002Fmore\u002Fpix-key-cpf-clabe-payout-details","What details do you need to pay someone in Brazil or Mexico? Pix keys, CPF, and CLABE","What a payout to Brazil or Mexico needs from the recipient: Pix key types, CPF and CNPJ formats, the 18-digit CLABE, and the checks that stop a bad payout.",{"path":802,"title":803,"description":804},"\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","What does \"no pre-funding\" mean in a stablecoin API?","No pre-funding means each payout is funded when you send it, not from a balance parked in advance. The three funding models, the math, and what to ask.",{"path":806,"title":807,"description":808},"\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","What is a crypto on-ramp and off-ramp? A guide for fintech builders","A crypto on-ramp converts fiat into stablecoins or crypto; an off-ramp converts them back into fiat in a bank account. How each works step by step, how they differ, which payment methods on-ramps support, and who they are built for.",{"path":810,"title":811,"description":812},"\u002Fresources\u002Fmore\u002Fwhat-is-a-liquidity-market-cross-border-payments","What is a liquidity market in cross-border payments? And why stablecoin liquidity is changing it","A liquidity market in cross-border payments is where the currency to settle a transfer gets sourced. How correspondent banks pre-fund it, and how stablecoin liquidity changes the model.",{"path":814,"title":815,"description":816},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","What is a stablecoin off-ramp? How crypto becomes cash","A stablecoin off-ramp converts stablecoins like USDC or USDT back into fiat currency in a bank account. How the conversion works and who regulates it.",{"path":818,"title":819,"description":820},"\u002Fresources\u002Fmore\u002Fwhat-is-a-virtual-account","What is a virtual account? A plain-English guide for fintech teams","A virtual account is a unique set of bank details that routes incoming payments to one customer or purpose. How it works, who uses it, and where it fits.",{"path":822,"title":823,"description":824},"\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration","What is payment orchestration? The routing layer, explained","Payment orchestration is the routing layer between your app and every processor, bank, and rail you use. The five layers, how stablecoin settlement fits, and how it differs from a gateway.",{"path":826,"title":827,"description":828},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","What to ask a stablecoin payments provider: 30 due diligence questions","The questions to ask a stablecoin payments vendor before you sign: licensing, custody, pricing, rails, compliance, failure handling, security, and exit.",{"path":398,"title":830,"description":831},"When not to use blockchain payments: 7 cases where a bank rail wins","Blockchain payments beat wires on many corridors, not all of them. Seven cases where a domestic rail, a card, or a plain wire is still the better choice.",{"path":247,"title":833,"description":834},"Where is my off-ramp payout? How to track it rail by rail, and what to tell the recipient","Track an off-ramp payout from transaction hash to bank: the reference each rail gives you (Pix E2E ID, SPEI key, ACH trace, UETR) and status copy.",{"path":448,"title":836,"description":837},"Why are cross-border payments slow? Where the days go in an international wire","Most SWIFT payments reach the destination bank within an hour. The days go to cut-offs, correspondent hops, compliance checks, and local crediting.",{"path":839,"title":840,"description":841},"\u002Fresources\u002Fmore\u002Fwhy-crypto-on-ramp-deposits-fail","Why crypto on-ramp deposits fail: missing references, late transfers, holds, and refunds","Most failed on-ramps fail on the fiat side: a missing reference, the wrong payer, a late transfer, a hold. What happens to the money in each case.",1791398893135]