[{"data":1,"prerenderedAt":887},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions":3,"resources-category-virtual-account-vs-one-time-deposit-instructions":558},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":525,"categoryType":6,"compare":6,"contributors":6,"date":526,"description":527,"extension":528,"faq":529,"howto":6,"isBlog":548,"isChangelog":548,"meta":549,"navigation":551,"path":552,"pillar":548,"products":6,"rawbody":553,"role":6,"seo":554,"seoTitle":555,"stem":556,"thumbnail":6,"updated":526,"__hash__":557},"content\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions.md","Virtual accounts vs one-time deposit instructions: how to collect bank transfers as stablecoins",null,{"type":8,"value":9,"toc":512},"minimark",[10,14,20,39,44,47,50,68,71,80,84,87,90,98,102,105,226,229,233,236,246,255,258,272,280,284,287,296,304,308,311,314,328,331,348,351,355,358,462,469,473,485,498,505,509],[11,12,13],"p",{},"Use one-time deposit instructions when a payer sends money occasionally, for a specific amount, or over a local rail like Pix or SPEI. Use a virtual account when the same payer sends US bank transfers again and again. Instructions need no setup but depend on a reference code. A virtual account's number identifies the customer by itself.",[11,15,16],{},[17,18,19],"strong",{},"Key takeaways",[21,22,23,27,30,33,36],"ul",{},[24,25,26],"li",{},"Both models turn a bank transfer into stablecoins in a wallet. They differ in how the deposit gets matched to a customer.",[24,28,29],{},"One-time instructions are created per payment: bank details plus a reference code, a Pix code, a CLABE, or a payment link.",[24,31,32],{},"A virtual account is a standing account number per customer. No reference to forget, but it needs KYC, review, and a monthly fee.",[24,34,35],{},"The most common failure in the one-time model is a missing or mangled reference. An ACH addenda field holds 80 characters, and payers lose codes far shorter than that.",[24,37,38],{},"Outside the US, per-payment instructions are often the only option, because Pix, SPEI, and similar rails already carry their own unique payment identifiers.",[40,41,43],"h2",{"id":42},"what-are-one-time-deposit-instructions","What are one-time deposit instructions?",[11,45,46],{},"One-time deposit instructions are payment details generated for a single pay-in, used once, for one amount.",[11,48,49],{},"The flow on a typical stablecoin on-ramp looks like this:",[51,52,53,56,59,62,65],"ol",{},[24,54,55],{},"You request a quote for the amount, the payment method, and the destination wallet.",[24,57,58],{},"You create the pay-in from that quote.",[24,60,61],{},"The provider returns instructions for that pay-in.",[24,63,64],{},"You show them to the payer, who sends the transfer.",[24,66,67],{},"The provider spots the deposit, matches it to the pay-in, converts it, and sends stablecoins to the wallet.",[11,69,70],{},"What \"instructions\" means depends on the rail. For a US transfer into a shared collection account, it's the account details plus a reference code the payer must include. For Pix, it's a payment code. For SPEI, it's a CLABE. For bank redirect rails such as PSE in Colombia, it's a payment link.",[11,72,73,74,79],{},"The ",[75,76,78],"a",{"href":77},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api","crypto on-ramp API integration guide"," walks through the quote and pay-in calls in detail.",[40,81,83],{"id":82},"what-is-a-virtual-account","What is a virtual account?",[11,85,86],{},"A virtual account is a bank account number assigned to one customer that receives every deposit for that customer, with no reference needed.",[11,88,89],{},"The payer sends money to it like any other bank account. Each deposit creates its own pay-in record, gets converted, and lands in the wallet linked to the account. The account number is the matching key, so the payer can leave the memo blank, pay from a parent company, or send an unexpected amount, and the money still reaches the right customer.",[11,91,92,93,97],{},"The trade-off is setup. A virtual account belongs to a verified customer, goes through compliance and bank review, and usually carries a monthly fee. The full lifecycle is in ",[75,94,96],{"href":95},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","stablecoin virtual accounts explained",".",[40,99,101],{"id":100},"how-do-the-two-models-compare","How do the two models compare?",[11,103,104],{},"One-time instructions win on setup and flexibility. Virtual accounts win on matching and repeat payments.",[106,107,108,123],"table",{},[109,110,111],"thead",{},[112,113,114,117,120],"tr",{},[115,116],"th",{},[115,118,119],{},"One-time deposit instructions",[115,121,122],{},"Virtual account",[124,125,126,138,149,160,171,182,193,204,215],"tbody",{},[112,127,128,132,135],{},[129,130,131],"td",{},"Reusable",[129,133,134],{},"No, one pay-in each",[129,136,137],{},"Yes, every deposit",[112,139,140,143,146],{},[129,141,142],{},"Matching key",[129,144,145],{},"Reference code or rail payment code",[129,147,148],{},"The receiving account number",[112,150,151,154,157],{},[129,152,153],{},"Setup before first payment",[129,155,156],{},"A quote and a pay-in, seconds",[129,158,159],{},"KYC or KYB, then compliance and bank review",[112,161,162,165,168],{},[129,163,164],{},"Ongoing cost",[129,166,167],{},"Per-transaction fees only",[129,169,170],{},"Per-transaction fees plus a monthly account fee",[112,172,173,176,179],{},[129,174,175],{},"Amount",[129,177,178],{},"Fixed by the quote",[129,180,181],{},"Any amount the payer sends",[112,183,184,187,190],{},[129,185,186],{},"Payer experience",[129,188,189],{},"New details each time",[129,191,192],{},"Same details forever, saved as a payee",[112,194,195,198,201],{},[129,196,197],{},"Main failure mode",[129,199,200],{},"Missing or wrong reference",[129,202,203],{},"Payer sends to an old or closed account",[112,205,206,209,212],{},[129,207,208],{},"Rails",[129,210,211],{},"US transfers and local rails (Pix, SPEI, and others)",[129,213,214],{},"Usually one country's rails",[112,216,217,220,223],{},[129,218,219],{},"Best for",[129,221,222],{},"Occasional payers, quoted amounts, local rails",[129,224,225],{},"Repeat payers, B2B invoices, foreign senders",[11,227,228],{},"Read the \"Main failure mode\" row twice. It's the reason most teams start with instructions and move their busiest payers to accounts.",[40,230,232],{"id":231},"why-do-references-go-missing","Why do references go missing?",[11,234,235],{},"Reference codes travel through fields that were never built to carry them reliably.",[11,237,238,239,245],{},"On ACH, free text rides in the addenda record's Payment Related Information field. Nacha's ",[75,240,244],{"href":241,"rel":242},"https:\u002F\u002Fachdevguide.nacha.org\u002Fach-file-details",[243],"nofollow","ACH file details"," describe it as an optional freeform field of 80 characters. Optional is the problem. Many bank apps hide it, shorten it, or put it on a second screen.",[11,247,248,249,254],{},"Wires got better structure when the Fedwire Funds Service ",[75,250,253],{"href":251,"rel":252},"https:\u002F\u002Fwww.frbservices.org\u002Fnews\u002Fcommunications\u002F061825-fedwire-iso-go",[243],"moved to ISO 20022 on July 14, 2025",". Better message formats don't help when a person types the code into the beneficiary name field.",[11,256,257],{},"The patterns repeat:",[21,259,260,263,266,269],{},[24,261,262],{},"An accounts payable team saves your bank details as a template and reuses last month's code.",[24,264,265],{},"The payer's bank truncates the memo.",[24,267,268],{},"Someone pays two invoices in one transfer with one code.",[24,270,271],{},"A parent company pays on behalf of a subsidiary and uses its own reference.",[11,273,274,275,279],{},"A deposit without its code lands in the right bank account with nothing tying it to a pay-in. Someone then has to work out who paid. ",[75,276,278],{"href":277},"\u002Fresources\u002Fmore\u002Fwhy-crypto-on-ramp-deposits-fail","Why crypto on-ramp deposits fail"," covers that failure and six others.",[40,281,283],{"id":282},"why-do-local-rails-work-well-with-one-time-instructions","Why do local rails work well with one-time instructions?",[11,285,286],{},"Instant rails like Pix and SPEI are built around unique payment identifiers, so the reference problem mostly disappears.",[11,288,289,290,295],{},"Pix is the clearest case. The Central Bank of Brazil's ",[75,291,294],{"href":292,"rel":293},"https:\u002F\u002Fwww.bcb.gov.br\u002Fcontent\u002Festabilidadefinanceira\u002Fpix\u002FRegulamento_Pix\u002FII_ManualdePadroesparaIniciacaodoPix.pdf",[243],"Pix initiation standards manual"," defines a transaction identifier, the txid, of 26 to 35 characters for dynamic QR codes. It exists so the receiver can reconcile each payment against the charge it belongs to. The payer scans or pastes the code. Nobody types a reference.",[11,297,298,299,303],{},"That's why per-payment instructions are the default for collections in Latin America. The payer's bank carries the identifier for you. ",[75,300,302],{"href":301},"\u002Fresources\u002Fmore\u002Fhow-to-on-ramp-local-currency-latin-america","How to on-ramp BRL, MXN, ARS, and COP"," covers the four local rails.",[40,305,307],{"id":306},"when-should-you-use-each-model","When should you use each model?",[11,309,310],{},"Pick by payer behavior first, then by rail.",[11,312,313],{},"Use one-time deposit instructions when:",[21,315,316,319,322,325],{},[24,317,318],{},"The payer pays once or rarely, like a consumer topping up a wallet.",[24,320,321],{},"The amount is tied to a specific quote or invoice and should not vary.",[24,323,324],{},"The rail is Pix, SPEI, or another local system with built-in payment codes.",[24,326,327],{},"You need to accept money today, before a customer finishes account review.",[11,329,330],{},"Use a virtual account when:",[21,332,333,336,339,342,345],{},[24,334,335],{},"The same payer sends transfers every week or month.",[24,337,338],{},"Payers pay from accounting systems that reuse saved bank details.",[24,340,341],{},"Amounts vary, like B2B invoices, marketplace seller funding, or payroll funding.",[24,343,344],{},"Foreign senders need to pay over SWIFT.",[24,346,347],{},"Finance wants the account number itself to be the customer ID in the ledger.",[11,349,350],{},"Many products run both. New customers start on instructions on day one, then get a virtual account once review clears.",[40,352,354],{"id":353},"what-should-you-check-before-choosing","What should you check before choosing?",[11,356,357],{},"Run this checklist against your payers and your provider before you commit to either model. It's what decides how much manual matching you'll do.",[106,359,360,372],{},[109,361,362],{},[112,363,364,367,370],{},[115,365,366],{},"Check",[115,368,369],{},"One-time instructions",[115,371,122],{},[124,373,374,385,396,407,418,429,440,451],{},[112,375,376,379,382],{},[129,377,378],{},"How does the payer see the matching key?",[129,380,381],{},"Shown with every payment. Is it hard to miss?",[129,383,384],{},"Saved once as a payee",[112,386,387,390,393],{},[129,388,389],{},"What happens to a deposit with no reference?",[129,391,392],{},"Ask the provider for the exact path: hold, manual match, or return",[129,394,395],{},"Not applicable, the account number matches it",[112,397,398,401,404],{},[129,399,400],{},"How long does a pay-in wait for money?",[129,402,403],{},"Minutes on instant rails, days on ACH and wire",[129,405,406],{},"No quote window, deposits create pay-ins as they arrive",[112,408,409,412,415],{},[129,410,411],{},"Is there a per-transaction cap?",[129,413,414],{},"Ask. Shared collection accounts can carry their own cap on top of customer limits",[129,416,417],{},"Customer limits from the verification tier apply",[112,419,420,423,426],{},[129,421,422],{},"Which rails are covered?",[129,424,425],{},"Check each local rail separately",[129,427,428],{},"Usually domestic rails plus wire and SWIFT",[112,430,431,434,437],{},[129,432,433],{},"What's the setup time?",[129,435,436],{},"None beyond the quote",[129,438,439],{},"Hours to business days for review",[112,441,442,445,448],{},[129,443,444],{},"What's the monthly cost?",[129,446,447],{},"None",[129,449,450],{},"A fixed fee per account",[112,452,453,456,459],{},[129,454,455],{},"Which webhook confirms the deposit?",[129,457,458],{},"The pay-in completion event",[129,460,461],{},"The same event, one per deposit",[11,463,464,465,97],{},"The ledger side, from webhooks to partial payments, is in ",[75,466,468],{"href":467},"\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation","how virtual accounts automate reconciliation",[40,470,472],{"id":471},"how-does-blindpay-handle-both-models","How does BlindPay handle both models?",[11,474,475,476,480,481,484],{},"BlindPay supports both, and picks automatically for US transfers. A pay-in quote locks the method, amount, fee split, and destination for 5 minutes, and the pay-in created from it returns the instructions for that rail: a ",[477,478,479],"code",{},"memo_code"," with bank details for ACH and wire, a ",[477,482,483],{},"pix_code"," for Pix, a CLABE for SPEI, an account number for Transfers 3.0, or a payment link for PSE.",[11,486,487,488,492,493,497],{},"When a customer has an approved virtual account, BlindPay shows that account's own details for ACH and wire and ignores the memo code. Two exceptions: RTP pay-ins always use the memo-code path, and SWIFT pay-ins require an approved virtual account. Pay-ins without a virtual account on ACH or wire are also capped at $500,000 per transaction. BlindPay's US virtual accounts cost $1.50 per month per account. The ",[75,489,491],{"href":490},"\u002Fdocs\u002Fpayins","payins docs"," and ",[75,494,496],{"href":495},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times"," have the details.",[11,499,500,501,97],{},"For how pay-in APIs sit next to issuer, wallet, and payout APIs, see the ",[75,502,504],{"href":503},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","types of stablecoin APIs",[40,506,508],{"id":507},"what-to-do-next","What to do next",[11,510,511],{},"Pull last quarter's deposits and count how many arrived without a usable reference, by payer. Move the top repeat payers to virtual accounts first, and keep one-time instructions for everyone else and for every local rail.",{"title":513,"searchDepth":514,"depth":514,"links":515},"",2,[516,517,518,519,520,521,522,523,524],{"id":42,"depth":514,"text":43},{"id":82,"depth":514,"text":83},{"id":100,"depth":514,"text":101},{"id":231,"depth":514,"text":232},{"id":282,"depth":514,"text":283},{"id":306,"depth":514,"text":307},{"id":353,"depth":514,"text":354},{"id":471,"depth":514,"text":472},{"id":507,"depth":514,"text":508},"payments","2026-10-04","One-time deposit instructions suit occasional payers and local rails. Virtual accounts suit repeat US payers. How each matches deposits and when to switch.","md",[530,533,536,539,542,545],{"q":531,"a":532},"What are one-time deposit instructions in a stablecoin on-ramp?","One-time deposit instructions are payment details generated for a single pay-in: a bank account plus a reference code, a Pix code, a CLABE, or a payment link. The payer uses them once, for one amount, and the provider matches the deposit to that pay-in. They need no account setup, which makes them the quickest way to accept a bank transfer and settle it in stablecoins.",{"q":534,"a":535},"What is the difference between a virtual account and deposit instructions?","A virtual account is a standing bank account number assigned to one customer, reusable for every deposit. Deposit instructions are created per payment and expire with it. The account number identifies the customer on its own, while instructions rely on a reference code or a unique payment code that the payer has to carry through their bank correctly.",{"q":537,"a":538},"When should I switch a customer from deposit instructions to a virtual account?","Switch when the same payer sends recurring transfers, when references keep going missing, when payers pay from accounting systems that reuse old details, or when you need foreign senders to pay over SWIFT. Keep one-time instructions for occasional payers, for amounts tied to a specific quote, and for local rails outside the US where virtual accounts are not offered.",{"q":540,"a":541},"Why do bank transfers lose their reference codes?","Reference fields are short and handled differently by every bank app. An ACH addenda record carries 80 characters of free text, and many consumer apps expose less. Payers type codes into the wrong field, reuse old templates, or drop the code entirely. A deposit without its code lands in the right account but can't be tied to the right pay-in automatically.",{"q":543,"a":544},"Can virtual accounts receive Pix or SPEI?","Virtual accounts are usually tied to one country's banking system. BlindPay's virtual accounts are US accounts that receive ACH, wire, and SWIFT. Brazilian, Mexican, Argentine, and Colombian collections use per-payment instructions instead: a Pix code, a CLABE, an account number for Transfers 3.0, or a PSE payment link.",{"q":546,"a":547},"Do one-time deposit instructions expire?","Usually yes, in two layers. The quote behind them expires quickly, often within minutes, so the pay-in must be created in that window. Then the pay-in waits for the money for a set period that depends on the rail: minutes for instant rails like Pix or SPEI, and days for ACH and wire. After that the pay-in is marked failed or cleaned up.",false,{"author":550},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","---\ntitle: \"Virtual accounts vs one-time deposit instructions: how to collect bank transfers as stablecoins\"\nseoTitle: \"Virtual account vs one-time deposit instructions\"\ndescription: \"One-time deposit instructions suit occasional payers and local rails. Virtual accounts suit repeat US payers. How each matches deposits and when to switch.\"\ndate: \"2026-10-04\"\nupdated: \"2026-10-04\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What are one-time deposit instructions in a stablecoin on-ramp?\"\n    a: \"One-time deposit instructions are payment details generated for a single pay-in: a bank account plus a reference code, a Pix code, a CLABE, or a payment link. The payer uses them once, for one amount, and the provider matches the deposit to that pay-in. They need no account setup, which makes them the quickest way to accept a bank transfer and settle it in stablecoins.\"\n  - q: \"What is the difference between a virtual account and deposit instructions?\"\n    a: \"A virtual account is a standing bank account number assigned to one customer, reusable for every deposit. Deposit instructions are created per payment and expire with it. The account number identifies the customer on its own, while instructions rely on a reference code or a unique payment code that the payer has to carry through their bank correctly.\"\n  - q: \"When should I switch a customer from deposit instructions to a virtual account?\"\n    a: \"Switch when the same payer sends recurring transfers, when references keep going missing, when payers pay from accounting systems that reuse old details, or when you need foreign senders to pay over SWIFT. Keep one-time instructions for occasional payers, for amounts tied to a specific quote, and for local rails outside the US where virtual accounts are not offered.\"\n  - q: \"Why do bank transfers lose their reference codes?\"\n    a: \"Reference fields are short and handled differently by every bank app. An ACH addenda record carries 80 characters of free text, and many consumer apps expose less. Payers type codes into the wrong field, reuse old templates, or drop the code entirely. A deposit without its code lands in the right account but can't be tied to the right pay-in automatically.\"\n  - q: \"Can virtual accounts receive Pix or SPEI?\"\n    a: \"Virtual accounts are usually tied to one country's banking system. BlindPay's virtual accounts are US accounts that receive ACH, wire, and SWIFT. Brazilian, Mexican, Argentine, and Colombian collections use per-payment instructions instead: a Pix code, a CLABE, an account number for Transfers 3.0, or a PSE payment link.\"\n  - q: \"Do one-time deposit instructions expire?\"\n    a: \"Usually yes, in two layers. The quote behind them expires quickly, often within minutes, so the pay-in must be created in that window. Then the pay-in waits for the money for a set period that depends on the rail: minutes for instant rails like Pix or SPEI, and days for ACH and wire. After that the pay-in is marked failed or cleaned up.\"\n---\n\nUse one-time deposit instructions when a payer sends money occasionally, for a specific amount, or over a local rail like Pix or SPEI. Use a virtual account when the same payer sends US bank transfers again and again. Instructions need no setup but depend on a reference code. A virtual account's number identifies the customer by itself.\n\n**Key takeaways**\n\n- Both models turn a bank transfer into stablecoins in a wallet. They differ in how the deposit gets matched to a customer.\n- One-time instructions are created per payment: bank details plus a reference code, a Pix code, a CLABE, or a payment link.\n- A virtual account is a standing account number per customer. No reference to forget, but it needs KYC, review, and a monthly fee.\n- The most common failure in the one-time model is a missing or mangled reference. An ACH addenda field holds 80 characters, and payers lose codes far shorter than that.\n- Outside the US, per-payment instructions are often the only option, because Pix, SPEI, and similar rails already carry their own unique payment identifiers.\n\n## What are one-time deposit instructions?\n\nOne-time deposit instructions are payment details generated for a single pay-in, used once, for one amount.\n\nThe flow on a typical stablecoin on-ramp looks like this:\n\n1. You request a quote for the amount, the payment method, and the destination wallet.\n2. You create the pay-in from that quote.\n3. The provider returns instructions for that pay-in.\n4. You show them to the payer, who sends the transfer.\n5. The provider spots the deposit, matches it to the pay-in, converts it, and sends stablecoins to the wallet.\n\nWhat \"instructions\" means depends on the rail. For a US transfer into a shared collection account, it's the account details plus a reference code the payer must include. For Pix, it's a payment code. For SPEI, it's a CLABE. For bank redirect rails such as PSE in Colombia, it's a payment link.\n\nThe [crypto on-ramp API integration guide](\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api) walks through the quote and pay-in calls in detail.\n\n## What is a virtual account?\n\nA virtual account is a bank account number assigned to one customer that receives every deposit for that customer, with no reference needed.\n\nThe payer sends money to it like any other bank account. Each deposit creates its own pay-in record, gets converted, and lands in the wallet linked to the account. The account number is the matching key, so the payer can leave the memo blank, pay from a parent company, or send an unexpected amount, and the money still reaches the right customer.\n\nThe trade-off is setup. A virtual account belongs to a verified customer, goes through compliance and bank review, and usually carries a monthly fee. The full lifecycle is in [stablecoin virtual accounts explained](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained).\n\n## How do the two models compare?\n\nOne-time instructions win on setup and flexibility. Virtual accounts win on matching and repeat payments.\n\n| | One-time deposit instructions | Virtual account |\n| --- | --- | --- |\n| Reusable | No, one pay-in each | Yes, every deposit |\n| Matching key | Reference code or rail payment code | The receiving account number |\n| Setup before first payment | A quote and a pay-in, seconds | KYC or KYB, then compliance and bank review |\n| Ongoing cost | Per-transaction fees only | Per-transaction fees plus a monthly account fee |\n| Amount | Fixed by the quote | Any amount the payer sends |\n| Payer experience | New details each time | Same details forever, saved as a payee |\n| Main failure mode | Missing or wrong reference | Payer sends to an old or closed account |\n| Rails | US transfers and local rails (Pix, SPEI, and others) | Usually one country's rails |\n| Best for | Occasional payers, quoted amounts, local rails | Repeat payers, B2B invoices, foreign senders |\n\nRead the \"Main failure mode\" row twice. It's the reason most teams start with instructions and move their busiest payers to accounts.\n\n## Why do references go missing?\n\nReference codes travel through fields that were never built to carry them reliably.\n\nOn ACH, free text rides in the addenda record's Payment Related Information field. Nacha's [ACH file details](https:\u002F\u002Fachdevguide.nacha.org\u002Fach-file-details) describe it as an optional freeform field of 80 characters. Optional is the problem. Many bank apps hide it, shorten it, or put it on a second screen.\n\nWires got better structure when the Fedwire Funds Service [moved to ISO 20022 on July 14, 2025](https:\u002F\u002Fwww.frbservices.org\u002Fnews\u002Fcommunications\u002F061825-fedwire-iso-go). Better message formats don't help when a person types the code into the beneficiary name field.\n\nThe patterns repeat:\n\n- An accounts payable team saves your bank details as a template and reuses last month's code.\n- The payer's bank truncates the memo.\n- Someone pays two invoices in one transfer with one code.\n- A parent company pays on behalf of a subsidiary and uses its own reference.\n\nA deposit without its code lands in the right bank account with nothing tying it to a pay-in. Someone then has to work out who paid. [Why crypto on-ramp deposits fail](\u002Fresources\u002Fmore\u002Fwhy-crypto-on-ramp-deposits-fail) covers that failure and six others.\n\n## Why do local rails work well with one-time instructions?\n\nInstant rails like Pix and SPEI are built around unique payment identifiers, so the reference problem mostly disappears.\n\nPix is the clearest case. The Central Bank of Brazil's [Pix initiation standards manual](https:\u002F\u002Fwww.bcb.gov.br\u002Fcontent\u002Festabilidadefinanceira\u002Fpix\u002FRegulamento_Pix\u002FII_ManualdePadroesparaIniciacaodoPix.pdf) defines a transaction identifier, the txid, of 26 to 35 characters for dynamic QR codes. It exists so the receiver can reconcile each payment against the charge it belongs to. The payer scans or pastes the code. Nobody types a reference.\n\nThat's why per-payment instructions are the default for collections in Latin America. The payer's bank carries the identifier for you. [How to on-ramp BRL, MXN, ARS, and COP](\u002Fresources\u002Fmore\u002Fhow-to-on-ramp-local-currency-latin-america) covers the four local rails.\n\n## When should you use each model?\n\nPick by payer behavior first, then by rail.\n\nUse one-time deposit instructions when:\n\n- The payer pays once or rarely, like a consumer topping up a wallet.\n- The amount is tied to a specific quote or invoice and should not vary.\n- The rail is Pix, SPEI, or another local system with built-in payment codes.\n- You need to accept money today, before a customer finishes account review.\n\nUse a virtual account when:\n\n- The same payer sends transfers every week or month.\n- Payers pay from accounting systems that reuse saved bank details.\n- Amounts vary, like B2B invoices, marketplace seller funding, or payroll funding.\n- Foreign senders need to pay over SWIFT.\n- Finance wants the account number itself to be the customer ID in the ledger.\n\nMany products run both. New customers start on instructions on day one, then get a virtual account once review clears.\n\n## What should you check before choosing?\n\nRun this checklist against your payers and your provider before you commit to either model. It's what decides how much manual matching you'll do.\n\n| Check | One-time instructions | Virtual account |\n| --- | --- | --- |\n| How does the payer see the matching key? | Shown with every payment. Is it hard to miss? | Saved once as a payee |\n| What happens to a deposit with no reference? | Ask the provider for the exact path: hold, manual match, or return | Not applicable, the account number matches it |\n| How long does a pay-in wait for money? | Minutes on instant rails, days on ACH and wire | No quote window, deposits create pay-ins as they arrive |\n| Is there a per-transaction cap? | Ask. Shared collection accounts can carry their own cap on top of customer limits | Customer limits from the verification tier apply |\n| Which rails are covered? | Check each local rail separately | Usually domestic rails plus wire and SWIFT |\n| What's the setup time? | None beyond the quote | Hours to business days for review |\n| What's the monthly cost? | None | A fixed fee per account |\n| Which webhook confirms the deposit? | The pay-in completion event | The same event, one per deposit |\n\nThe ledger side, from webhooks to partial payments, is in [how virtual accounts automate reconciliation](\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation).\n\n## How does BlindPay handle both models?\n\nBlindPay supports both, and picks automatically for US transfers. A pay-in quote locks the method, amount, fee split, and destination for 5 minutes, and the pay-in created from it returns the instructions for that rail: a `memo_code` with bank details for ACH and wire, a `pix_code` for Pix, a CLABE for SPEI, an account number for Transfers 3.0, or a payment link for PSE.\n\nWhen a customer has an approved virtual account, BlindPay shows that account's own details for ACH and wire and ignores the memo code. Two exceptions: RTP pay-ins always use the memo-code path, and SWIFT pay-ins require an approved virtual account. Pay-ins without a virtual account on ACH or wire are also capped at $500,000 per transaction. BlindPay's US virtual accounts cost $1.50 per month per account. The [payins docs](\u002Fdocs\u002Fpayins) and [cut-off times](\u002Fdocs\u002Fkb\u002Fcut-off-times) have the details.\n\nFor how pay-in APIs sit next to issuer, wallet, and payout APIs, see the [types of stablecoin APIs](\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis).\n\n## What to do next\n\nPull last quarter's deposits and count how many arrived without a usable reference, by payer. Move the top repeat payers to virtual accounts first, and keep one-time instructions for everyone else and for every local rail.\n",{"title":5,"description":527},"Virtual account vs one-time deposit instructions","resources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","-x03gUe5VoH2rOFZI6ertgk2hytXbTKLXKBuwuRhrAI",[559,563,567,571,575,579,583,587,591,595,599,603,607,611,615,619,623,627,631,635,639,643,647,651,655,659,663,666,670,674,678,682,685,689,693,697,701,704,708,712,716,720,724,728,732,736,740,744,748,752,756,760,764,768,772,776,780,784,788,792,796,799,803,807,811,815,819,823,827,831,835,839,840,844,848,852,856,860,864,868,872,876,880,884],{"path":560,"title":561,"description":562},"\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":564,"title":565,"description":566},"\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":568,"title":569,"description":570},"\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":572,"title":573,"description":574},"\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":576,"title":577,"description":578},"\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":580,"title":581,"description":582},"\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":584,"title":585,"description":586},"\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":588,"title":589,"description":590},"\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":592,"title":593,"description":594},"\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":596,"title":597,"description":598},"\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":600,"title":601,"description":602},"\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":604,"title":605,"description":606},"\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":608,"title":609,"description":610},"\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":612,"title":613,"description":614},"\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":616,"title":617,"description":618},"\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":620,"title":621,"description":622},"\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":624,"title":625,"description":626},"\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":628,"title":629,"description":630},"\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":632,"title":633,"description":634},"\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":636,"title":637,"description":638},"\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":640,"title":641,"description":642},"\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":644,"title":645,"description":646},"\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":648,"title":649,"description":650},"\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":652,"title":653,"description":654},"\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":656,"title":657,"description":658},"\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":660,"title":661,"description":662},"\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":77,"title":664,"description":665},"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":667,"title":668,"description":669},"\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":671,"title":672,"description":673},"\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":675,"title":676,"description":677},"\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":679,"title":680,"description":681},"\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":301,"title":683,"description":684},"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":686,"title":687,"description":688},"\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":690,"title":691,"description":692},"\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":694,"title":695,"description":696},"\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":698,"title":699,"description":700},"\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":467,"title":702,"description":703},"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":705,"title":706,"description":707},"\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":709,"title":710,"description":711},"\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":713,"title":714,"description":715},"\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":717,"title":718,"description":719},"\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":721,"title":722,"description":723},"\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":725,"title":726,"description":727},"\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":729,"title":730,"description":731},"\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":733,"title":734,"description":735},"\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained","POBO vs COBO: SWIFT payments and collections on behalf of, explained","POBO sends a SWIFT payment for a customer, COBO collects one for them. Whose name shows, how UETR tracking works, and where stablecoin settlement fits.",{"path":737,"title":738,"description":739},"\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":741,"title":742,"description":743},"\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":745,"title":746,"description":747},"\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":749,"title":750,"description":751},"\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":753,"title":754,"description":755},"\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":757,"title":758,"description":759},"\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":761,"title":762,"description":763},"\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":765,"title":766,"description":767},"\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":769,"title":770,"description":771},"\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":773,"title":774,"description":775},"\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":777,"title":778,"description":779},"\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":781,"title":782,"description":783},"\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":785,"title":786,"description":787},"\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":789,"title":790,"description":791},"\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":793,"title":794,"description":795},"\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":95,"title":797,"description":798},"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":800,"title":801,"description":802},"\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":804,"title":805,"description":806},"\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":808,"title":809,"description":810},"\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","Stablecoins vs SWIFT for B2B cross-border payments: a real comparison","Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes for business payments in 2026.",{"path":812,"title":813,"description":814},"\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":816,"title":817,"description":818},"\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":820,"title":821,"description":822},"\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":824,"title":825,"description":826},"\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":828,"title":829,"description":830},"\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":832,"title":833,"description":834},"\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":836,"title":837,"description":838},"\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":552,"title":5,"description":527},{"path":841,"title":842,"description":843},"\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":845,"title":846,"description":847},"\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":849,"title":850,"description":851},"\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":853,"title":854,"description":855},"\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":857,"title":858,"description":859},"\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":861,"title":862,"description":863},"\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":865,"title":866,"description":867},"\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":869,"title":870,"description":871},"\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":873,"title":874,"description":875},"\u002Fresources\u002Fmore\u002Fwhen-not-to-use-blockchain-payments","When not to use blockchain payments: 7 cases where a bank rail wins","Blockchain payments beat wires on many corridors, not all of them. Seven cases where a domestic rail, a card, or a plain wire is still the better choice.",{"path":877,"title":878,"description":879},"\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout","Where is my off-ramp payout? How to track it rail by rail, and what to tell the recipient","Track an off-ramp payout from transaction hash to bank: the reference each rail gives you (Pix E2E ID, SPEI key, ACH trace, UETR) and status copy.",{"path":881,"title":882,"description":883},"\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow","Why are cross-border payments slow? Where the days go in an international wire","Most SWIFT payments reach the destination bank within an hour. The days go to cut-offs, correspondent hops, compliance checks, and local crediting.",{"path":277,"title":885,"description":886},"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.",1791398896827]