[{"data":1,"prerenderedAt":1186},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico":3,"resources-category-how-to-send-usdc-to-bank-account-mexico":857},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":803,"categoryType":6,"compare":6,"contributors":6,"date":804,"description":805,"extension":806,"faq":807,"howto":826,"isBlog":847,"isChangelog":847,"meta":848,"navigation":850,"path":851,"pillar":847,"products":6,"rawbody":852,"role":6,"seo":853,"seoTitle":854,"stem":855,"thumbnail":6,"updated":804,"__hash__":856},"content\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico.md","How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI",null,{"type":8,"value":9,"toc":787},"minimark",[10,14,17,23,42,51,56,59,62,65,70,163,166,174,178,195,299,307,311,314,330,333,438,441,445,448,457,465,469,472,536,539,543,546,622,630,634,637,645,649,652,757,761,764,781],[11,12,13],"p",{},"To send USDC to a bank account in Mexico, onboard with a stablecoin payout API, add the recipient's CLABE and legal name, request a USDC to MXN quote, fund it from a wallet, and execute. The provider converts to pesos and delivers them over SPEI, which runs 24\u002F7, so most payouts land in minutes.",[11,15,16],{},"That's the short version. The rest of this guide is the detail that decides whether the first payout works: what to collect from each type of recipient, what each SPEI status means, and where Mexican payouts fail.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"SPEI is Banco de México's real-time settlement system. It has run since August 13, 2004 and operates 24\u002F7, so weekends and holidays don't delay a peso payout.",[27,31,32],{},"Collect the legal name and an 18-digit CLABE. A debit card or phone number also works, but needs the bank's institution code.",[27,34,35],{},"Quote in pesos when the recipient must get an exact amount, and decide up front who pays the fee.",[27,37,38],{},"SPEI routes on the account number. A valid CLABE that belongs to the wrong person is the most expensive mistake in the corridor.",[27,40,41],{},"Store the SPEI tracking key with every payout. Banxico's CEP lookup turns it into a receipt anyone can check.",[11,43,44,45,50],{},"If you're new to the categories of APIs that do this, start with ",[46,47,49],"a",{"href":48},"\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis","the types of stablecoin APIs",". This guide assumes a payout API: one that takes stablecoins in and sends local currency out.",[52,53,55],"h2",{"id":54},"what-do-you-need-before-the-first-payout-to-mexico","What do you need before the first payout to Mexico?",[11,57,58],{},"You need three things before any money moves: a verified sender, a verified recipient bank account, and USDC or USDT on a network the provider accepts.",[11,60,61],{},"The sender side is onboarding. A business completes KYB once, an individual completes KYC. Nothing in the Mexico corridor skips this.",[11,63,64],{},"The recipient side is where most teams under-collect. What you need depends on who you're paying, so build the form per recipient type instead of one generic \"bank details\" box.",[66,67,69],"h3",{"id":68},"recipient-data-checklist-by-recipient-type","Recipient data checklist by recipient type",[71,72,73,92],"table",{},[74,75,76],"thead",{},[77,78,79,83,86,89],"tr",{},[80,81,82],"th",{},"Recipient",[80,84,85],{},"Account identifier",[80,87,88],{},"Name to collect",[80,90,91],{},"Keep on file",[93,94,95,110,122,136,150],"tbody",{},[77,96,97,101,104,107],{},[98,99,100],"td",{},"Employee",[98,102,103],{},"CLABE",[98,105,106],{},"Full legal name on the account",[98,108,109],{},"Payroll record, RFC if finance needs it",[77,111,112,115,117,119],{},[98,113,114],{},"Independent contractor",[98,116,103],{},[98,118,106],{},[98,120,121],{},"Contract and the invoice being paid",[77,123,124,127,130,133],{},[98,125,126],{},"Supplier (company)",[98,128,129],{},"CLABE of the company's account",[98,131,132],{},"Legal company name, not the trade name",[98,134,135],{},"The supplier's invoice and its RFC",[77,137,138,141,144,147],{},[98,139,140],{},"Family member (remittance)",[98,142,143],{},"CLABE, debit card, or phone number",[98,145,146],{},"Full legal name",[98,148,149],{},"Relationship and, if asked, source of funds",[77,151,152,155,157,160],{},[98,153,154],{},"Your own Mexican entity",[98,156,103],{},[98,158,159],{},"The entity's legal name",[98,161,162],{},"Intercompany agreement",[11,164,165],{},"Two details from that table trip teams up. First, a debit card or phone number only works with the receiving bank's institution code, so the form has to ask for the bank too. Second, the relationship matters to compliance. Payout APIs usually ask whether the account belongs to the sender, an employee, a contractor, or a supplier, and some run a name-match check only when you pay your own account.",[11,167,168,169,173],{},"The field-by-field anatomy of a CLABE, including the check digit math, is in ",[46,170,172],{"href":171},"\u002Fresources\u002Fmore\u002Fpix-key-cpf-clabe-payout-details","what details you need to pay someone in Brazil or Mexico",". Validate it client-side. It catches typos before they become returns.",[52,175,177],{"id":176},"how-do-you-send-usdc-to-a-mexican-bank-account-step-by-step","How do you send USDC to a Mexican bank account step by step?",[11,179,180,181,185,186,185,190,194],{},"You add the bank account once, then quote, fund, and execute each payout against it. The field names below come from BlindPay's API (",[46,182,184],{"href":183},"\u002Fdocs\u002Fbank-accounts","bank accounts",", ",[46,187,189],{"href":188},"\u002Fdocs\u002Fpayout-quotes","payout quotes",[46,191,193],{"href":192},"\u002Fdocs\u002Fpayouts","payouts","); other providers use similar objects with different names.",[196,197,198,216,226,256,262,268,274],"ol",{},[27,199,200,203,204,185,208,211,212,215],{},[20,201,202],{},"Add the bank account."," Create a SPEI bank account on the customer with ",[205,206,207],"code",{},"beneficiary_name",[205,209,210],{},"spei_protocol"," (CLABE, debit card, or phone), the identifier, and ",[205,213,214],{},"spei_institution_code"," when the protocol is card or phone. Validation runs the same way on development and production, so a malformed CLABE fails in testing.",[27,217,218,221,222,225],{},[20,219,220],{},"Filter the bank list."," If you build a bank picker from the provider's bank-details endpoint, drop inactive banks. Some providers, BlindPay included, return them flagged ",[205,223,224],{},"is_active: false"," instead of removing them.",[27,227,228,231,232,235,236,239,240,243,244,247,248,251,252,255],{},[20,229,230],{},"Request a quote."," Quote against the bank account with a ",[205,233,234],{},"network"," and ",[205,237,238],{},"token",". Set ",[205,241,242],{},"currency_type"," to ",[205,245,246],{},"receiver"," to fix the peso amount, or ",[205,249,250],{},"sender"," to fix the USDC amount. Set ",[205,253,254],{},"cover_fees: true"," if the recipient must get the full amount. Amounts are integers in minor units.",[27,257,258,261],{},[20,259,260],{},"Execute before the quote expires."," Here that's 5 minutes after creation. Past that, request a new one.",[27,263,264,267],{},[20,265,266],{},"Fund it."," From a managed wallet, pass its address and you're done. From a wallet you control, authorize first: an ERC-20 approve on EVM chains, a signed transaction on Stellar, or a token delegation on Solana.",[27,269,270,273],{},[20,271,272],{},"Create the payout."," One call against the quote ID. The stablecoins leave the funding wallet, convert to pesos, and go out over SPEI.",[27,275,276,279,280,283,284,287,288,185,291,294,295,298],{},[20,277,278],{},"Track it."," ",[205,281,282],{},"payout.update"," fires on status changes and ",[205,285,286],{},"payout.complete"," fires when the payout reaches ",[205,289,290],{},"completed",[205,292,293],{},"failed",", or ",[205,296,297],{},"refunded",".",[11,300,301,302,306],{},"Network choice is part of step 3. In this API's matrix, USDC payouts can be funded on networks including Ethereum, Polygon, Base, Arbitrum, Stellar, and Solana, and USDT on Ethereum, Polygon, Solana, and Tron. USDT isn't available on Base, Arbitrum, or Stellar, and USDC isn't on Tron. The full matrix is in ",[46,303,305],{"href":304},"\u002Fdocs\u002Fkb\u002Fsupported-chains","supported chains",". The recipient never sees any of this. They get pesos.",[52,308,310],{"id":309},"what-happens-to-the-pesos-inside-spei","What happens to the pesos inside SPEI?",[11,312,313],{},"Once the provider releases the transfer, SPEI settles it between the two banks in real time, and the receiving bank credits the account.",[11,315,316,317,323,324,329],{},"Banco de México runs SPEI as a ",[46,318,322],{"href":319,"rel":320},"https:\u002F\u002Fwww.banxico.org.mx\u002Fservicios\u002Fspei_-informacion-banco-mex.html",[321],"nofollow","real-time settlement system on a 24\u002F7 schedule",". Its ",[46,325,328],{"href":326,"rel":327},"https:\u002F\u002Fwww.banxico.org.mx\u002Fservices\u002Finterbanking-electronic-payme.html",[321],"user guide"," cites Notice 17\u002F2010: a SPEI payment should not take more than 30 seconds after approval. That's why \"minutes\" is a fair ETA for the whole payout, and why a Friday night payout lands like a Tuesday morning one.",[11,331,332],{},"Your provider's status is the first thing to check. When you need the bank-level view, Banxico's MI-SPEI service reports these states:",[71,334,335,348],{},[74,336,337],{},[77,338,339,342,345],{},[80,340,341],{},"SPEI status",[80,343,344],{},"What it means",[80,346,347],{},"What to do",[93,349,350,361,372,383,394,405,416,427],{},[77,351,352,355,358],{},[98,353,354],{},"Being processed",[98,356,357],{},"SPEI received the order, money not yet deposited",[98,359,360],{},"Wait. This normally clears in seconds",[77,362,363,366,369],{},[98,364,365],{},"Liquidated",[98,367,368],{},"SPEI settled it; the receiving bank can credit the account",[98,370,371],{},"Send the recipient the tracking key",[77,373,374,377,380],{},[98,375,376],{},"Cancelled",[98,378,379],{},"The sending bank cancelled before the money moved",[98,381,382],{},"Check the payout status with your provider",[77,384,385,388,391],{},[98,386,387],{},"Rejected",[98,389,390],{},"SPEI rejected it for errors or inconsistent data",[98,392,393],{},"Fix the account data, then send a new payout",[77,395,396,399,402],{},[98,397,398],{},"Undergoing return",[98,400,401],{},"The receiving bank is sending the money back",[98,403,404],{},"Don't resend yet; wait for the return to finish",[77,406,407,410,413],{},[98,408,409],{},"Returned",[98,411,412],{},"The money is back with the sender",[98,414,415],{},"Confirm the account details, then resend",[77,417,418,421,424],{},[98,419,420],{},"Cancelled at the close",[98,422,423],{},"Not authorized before SPEI's close of operations",[98,425,426],{},"Check with your provider before resending",[77,428,429,432,435],{},[98,430,431],{},"Not found",[98,433,434],{},"No SPEI record matches the search",[98,436,437],{},"Recheck the date, key, and amount you searched",[11,439,440],{},"\"Liquidated\" is the state that matters for disputes. From there, the recipient's bank has the money, and a CEP can prove it.",[52,442,444],{"id":443},"how-do-you-prove-a-spei-payment-arrived","How do you prove a SPEI payment arrived?",[11,446,447],{},"You prove it with the CEP, the electronic payment receipt Banco de México issues from the receiving bank's confirmation.",[11,449,450,451,456],{},"According to Banxico, the CEP can take up to 30 minutes after the deposit to become available, and it can be looked up for SPEI payments from the last 45 working days. The lookup needs the date, the tracking key or reference, the sending and receiving banks, the receiving account, and the amount. Download it at ",[46,452,455],{"href":453,"rel":454},"https:\u002F\u002Fwww.banxico.org.mx\u002Fcep\u002F",[321],"Banxico's CEP page",". The CEP comes as a PDF and an XML file with a digital seal, so an auditor can validate it.",[11,458,459,460,464],{},"Practical rule: store the tracking key on your payout record the moment you have it. A recipient who says \"I didn't get it\" gets a CEP link, not a support ticket. ",[46,461,463],{"href":462},"\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout","How to track an off-ramp payout"," covers the same idea across every rail.",[52,466,468],{"id":467},"where-do-usdc-payouts-to-mexico-fail","Where do USDC payouts to Mexico fail?",[11,470,471],{},"Most failures come from recipient data, not from SPEI. Here are the eight that show up most, with the fix.",[196,473,474,480,486,492,498,504,510,521],{},[27,475,476,479],{},[20,477,478],{},"CLABE with a bad check digit."," Fix: validate the 18th digit in the form.",[27,481,482,485],{},[20,483,484],{},"A 16-digit card number in the CLABE field."," Fix: a length check per protocol.",[27,487,488,491],{},[20,489,490],{},"Card or phone payout without the institution code."," Fix: make the bank field required for those protocols.",[27,493,494,497],{},[20,495,496],{},"Trade name instead of legal name."," Fix: ask for the name exactly as the bank registered it.",[27,499,500,503],{},[20,501,502],{},"A valid CLABE that belongs to someone else."," SPEI won't catch this. Fix: confirm new accounts with the recipient before the first large payout, for example with a small first payment.",[27,505,506,509],{},[20,507,508],{},"Expired quote."," Fix: quote right before execution, never from a cache.",[27,511,512,515,516,520],{},[20,513,514],{},"Recipient doesn't recognize the sender."," On BlindPay, SPEI payouts show BlindPay's name as the sender (",[46,517,519],{"href":518},"\u002Fdocs\u002Fkb\u002Fpayout-descriptor","payout descriptor","). Fix: tell recipients in advance and put your invoice or payroll ID in the reference.",[27,522,523,529,530,532,533,535],{},[20,524,525,526,528],{},"Assuming ",[205,527,293],{}," means refunded."," It doesn't. Here, ",[205,531,297],{}," means the stablecoins went back to the funding source; ",[205,534,293],{}," does not refund automatically, so contact support.",[11,537,538],{},"On references: Banxico's guide says the payment description that reaches the payee runs up to 40 characters. Whatever your provider passes through, put the invoice or payroll ID at the front.",[52,540,542],{"id":541},"how-should-different-businesses-run-the-mexico-corridor","How should different businesses run the Mexico corridor?",[11,544,545],{},"The steps are the same for everyone; the quote settings and records change by use case. These are illustrative scenarios, not customer stories.",[71,547,548,564],{},[74,549,550],{},[77,551,552,555,558,561],{},[80,553,554],{},"Use case",[80,556,557],{},"Illustrative scenario",[80,559,560],{},"Quote setting",[80,562,563],{},"Record to keep",[93,565,566,580,594,608],{},[77,567,568,571,574,577],{},[98,569,570],{},"Contractor payroll",[98,572,573],{},"A US startup pays 40 engineers in Guadalajara every two weeks",[98,575,576],{},"Fix the peso amount, sender covers fees",[98,578,579],{},"Contract and invoice per contractor",[77,581,582,585,588,591],{},[98,583,584],{},"Supplier payments",[98,586,587],{},"An importer pays a Monterrey manufacturer a MXN invoice",[98,589,590],{},"Fix the peso amount to match the invoice",[98,592,593],{},"Supplier invoice and RFC",[77,595,596,599,602,605],{},[98,597,598],{},"Marketplace payouts",[98,600,601],{},"A platform pays out weekly seller balances",[98,603,604],{},"Fix the USDC amount, fees from the payout",[98,606,607],{},"Seller ledger entry per payout",[77,609,610,613,616,619],{},[98,611,612],{},"Remittance",[98,614,615],{},"An app lets US users send pesos to family",[98,617,618],{},"Show the peso amount before confirming",[98,620,621],{},"Sender KYC and relationship",[11,623,624,625,629],{},"Payroll is the clearest case for fixed-receiver quotes: contractors expect a round peso number, not whatever is left after fees. ",[46,626,628],{"href":627},"\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","Stablecoin payroll for LATAM contractors"," goes deeper on that flow.",[52,631,633],{"id":632},"what-mexican-rules-should-you-know-about","What Mexican rules should you know about?",[11,635,636],{},"Mexico regulates financial technology and virtual asset activity under its 2018 Fintech Law, with Banco de México and the CNBV as the main authorities, and the SAT handles tax. Paying from a stablecoin balance doesn't change the recipient's tax treatment or your payroll and supplier obligations; it changes how the pesos get there.",[11,638,639,640,644],{},"The rules for converting USDC to pesos, and the stablecoin bill introduced in the Senate in May 2026, are covered in ",[46,641,643],{"href":642},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN routes compared",". Confirm your specific obligations in Mexico with qualified counsel before launching a corridor.",[52,646,648],{"id":647},"how-do-you-choose-a-provider-for-mexico-payouts","How do you choose a provider for Mexico payouts?",[11,650,651],{},"Score each provider on eight criteria, and test the ones you can in a sandbox instead of asking.",[71,653,654,667],{},[74,655,656],{},[77,657,658,661,664],{},[80,659,660],{},"Criterion",[80,662,663],{},"What to test",[80,665,666],{},"Red flag",[93,668,669,680,691,702,713,724,735,746],{},[77,670,671,674,677],{},[98,672,673],{},"SPEI protocols",[98,675,676],{},"Can you pay to CLABE, debit card, and phone?",[98,678,679],{},"CLABE only, with no plan for the rest",[77,681,682,685,688],{},[98,683,684],{},"Validation",[98,686,687],{},"Does a bad CLABE fail at bank account creation?",[98,689,690],{},"It fails days later as a return",[77,692,693,696,699],{},[98,694,695],{},"Quote control",[98,697,698],{},"Can you fix the peso amount and choose who pays fees?",[98,700,701],{},"Only sender-side amounts",[77,703,704,707,710],{},[98,705,706],{},"Funding networks",[98,708,709],{},"Is your token supported on the network you hold it on?",[98,711,712],{},"One chain, or USDC only",[77,714,715,718,721],{},[98,716,717],{},"Pre-funding",[98,719,720],{},"Do you need a peso balance parked in Mexico?",[98,722,723],{},"A float that grows with volume",[77,725,726,729,732],{},[98,727,728],{},"Status detail",[98,730,731],{},"Do webhooks separate conversion from bank delivery?",[98,733,734],{},"One \"pending\" until \"done\"",[77,736,737,740,743],{},[98,738,739],{},"Tracking reference",[98,741,742],{},"Do you get a reference you can take to Banxico's CEP lookup?",[98,744,745],{},"No rail reference exposed",[77,747,748,751,754],{},[98,749,750],{},"Refund rules",[98,752,753],{},"What happens to the stablecoins when a payout can't complete?",[98,755,756],{},"No written answer",[52,758,760],{"id":759},"how-does-blindpay-handle-mexico-payouts","How does BlindPay handle Mexico payouts?",[11,762,763],{},"BlindPay pays out pesos over SPEI to a CLABE, debit card, or phone number, funded with USDC or USDT from a managed wallet or a wallet you control, with no pre-funded peso balance. KYC, KYB, and sanctions screening run inside the payout flow. The same API also pays out over Pix, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), and SDKs for Node.js, Python, Go, PHP, and Swift wrap it.",[11,765,766,767,771,772,776,777,298],{},"For the Brazil version of this walkthrough, see ",[46,768,770],{"href":769},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","how to send USDC to a bank account in Brazil",". Then send a test payout to a CLABE on a free development instance with the ",[46,773,775],{"href":774},"\u002Fdocs\u002Fquickstart-payout","payout quickstart",", and check today's rate on the ",[46,778,780],{"href":779},"\u002Fusdc-to-mxn","USDC to MXN page",[11,782,783],{},[784,785,786],"em",{},"This article is general information, not legal or tax advice.",{"title":788,"searchDepth":789,"depth":789,"links":790},"",2,[791,795,796,797,798,799,800,801,802],{"id":54,"depth":789,"text":55,"children":792},[793],{"id":68,"depth":794,"text":69},3,{"id":176,"depth":789,"text":177},{"id":309,"depth":789,"text":310},{"id":443,"depth":789,"text":444},{"id":467,"depth":789,"text":468},{"id":541,"depth":789,"text":542},{"id":632,"depth":789,"text":633},{"id":647,"depth":789,"text":648},{"id":759,"depth":789,"text":760},"payments","2026-10-05","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.","md",[808,811,814,817,820,823],{"q":809,"a":810},"How long does it take to send USDC to a bank account in Mexico?","Usually minutes. SPEI is Banco de México's real-time settlement system and runs 24\u002F7, and Banxico's rules say a SPEI payment should not take more than 30 seconds after approval. The longer part is the step before it: receiver checks, the quote, and converting USDC to pesos. A payout held for a compliance review takes longer, whatever the rail.",{"q":812,"a":813},"What details do I need to pay someone in Mexico?","The beneficiary's full legal name and an account identifier. The default is the 18-digit CLABE. SPEI also accepts a 16-digit debit card number or a 10-digit mobile number linked to the account, and those two need the receiving bank's institution code. For companies, use the legal name the bank registered, not the brand name on their website.",{"q":815,"a":816},"Can I send USDT instead of USDC to Mexico?","Yes, if the provider accepts USDT on the network you hold it on. The recipient still gets pesos over SPEI, so the stablecoin only changes the funding leg. Check network support first: on many payout APIs, USDT runs on Ethereum, Polygon, Solana, and Tron, but not on Base or Arbitrum, while USDC is the reverse on Tron.",{"q":818,"a":819},"What happens if the CLABE is wrong?","If the CLABE fails its check digit, a good provider rejects it when you save the bank account. If it is valid but closed or belongs to someone else, the receiving bank can return the SPEI transfer, and Banxico's MI-SPEI service would show it as undergoing return or returned. A valid CLABE for the wrong person is the expensive case, because SPEI routes on the account number.",{"q":821,"a":822},"Do I need the recipient's RFC to pay them over SPEI?","Not to route the money. SPEI moves pesos on the CLABE, card, or phone number. Collect the RFC anyway when your finance team needs it for supplier invoices, contractor records, or tax filings, and keep it next to the payout record. Paying from a stablecoin balance does not change what you owe on the Mexican tax side.",{"q":824,"a":825},"How does the recipient prove the payment arrived?","With a CEP, the electronic payment receipt Banco de México issues from the receiving bank's confirmation. Banxico says the CEP can take up to 30 minutes to become available and can be looked up for payments from the last 45 working days. It needs the date, the tracking key or reference, both banks, the receiving account, and the amount.",{"name":827,"steps":828},"How to send USDC to a bank account in Mexico",[829,832,835,838,841,844],{"name":830,"text":831},"Onboard your business","Complete KYB with the payout provider so your company can send. Individuals sending for themselves complete KYC instead.",{"name":833,"text":834},"Add the recipient's bank account","Collect the beneficiary's legal name and an 18-digit CLABE, or a debit card or phone number linked to the account plus the bank's institution code. Validate the CLABE check digit before you save it.",{"name":836,"text":837},"Request a quote in pesos","Ask for a USDC to MXN payout quote against that bank account, choosing whether the amount is the USDC you send or the pesos the recipient gets, and who pays the fee. Execute before the quote expires.",{"name":839,"text":840},"Fund the payout from a wallet","Pick the network and token the quote prices, then fund from a provider-managed balance or authorize the transfer from a wallet you control.",{"name":842,"text":843},"Execute and let SPEI settle","Create the payout against the quote. The provider converts USDC to pesos and sends them over SPEI, which runs 24\u002F7 and settles in seconds once the transfer is released.",{"name":845,"text":846},"Confirm delivery","Listen for the payout's completion webhook, store the SPEI tracking key, and use Banxico's CEP lookup if the recipient says the money never arrived.",false,{"author":849},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","---\ntitle: \"How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI\"\nseoTitle: \"How to send USDC to a bank account in Mexico over SPEI\"\ndescription: \"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.\"\ndate: \"2026-10-05\"\nupdated: \"2026-10-05\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to send USDC to a bank account in Mexico\"\n  steps:\n    - name: \"Onboard your business\"\n      text: \"Complete KYB with the payout provider so your company can send. Individuals sending for themselves complete KYC instead.\"\n    - name: \"Add the recipient's bank account\"\n      text: \"Collect the beneficiary's legal name and an 18-digit CLABE, or a debit card or phone number linked to the account plus the bank's institution code. Validate the CLABE check digit before you save it.\"\n    - name: \"Request a quote in pesos\"\n      text: \"Ask for a USDC to MXN payout quote against that bank account, choosing whether the amount is the USDC you send or the pesos the recipient gets, and who pays the fee. Execute before the quote expires.\"\n    - name: \"Fund the payout from a wallet\"\n      text: \"Pick the network and token the quote prices, then fund from a provider-managed balance or authorize the transfer from a wallet you control.\"\n    - name: \"Execute and let SPEI settle\"\n      text: \"Create the payout against the quote. The provider converts USDC to pesos and sends them over SPEI, which runs 24\u002F7 and settles in seconds once the transfer is released.\"\n    - name: \"Confirm delivery\"\n      text: \"Listen for the payout's completion webhook, store the SPEI tracking key, and use Banxico's CEP lookup if the recipient says the money never arrived.\"\nfaq:\n  - q: \"How long does it take to send USDC to a bank account in Mexico?\"\n    a: \"Usually minutes. SPEI is Banco de México's real-time settlement system and runs 24\u002F7, and Banxico's rules say a SPEI payment should not take more than 30 seconds after approval. The longer part is the step before it: receiver checks, the quote, and converting USDC to pesos. A payout held for a compliance review takes longer, whatever the rail.\"\n  - q: \"What details do I need to pay someone in Mexico?\"\n    a: \"The beneficiary's full legal name and an account identifier. The default is the 18-digit CLABE. SPEI also accepts a 16-digit debit card number or a 10-digit mobile number linked to the account, and those two need the receiving bank's institution code. For companies, use the legal name the bank registered, not the brand name on their website.\"\n  - q: \"Can I send USDT instead of USDC to Mexico?\"\n    a: \"Yes, if the provider accepts USDT on the network you hold it on. The recipient still gets pesos over SPEI, so the stablecoin only changes the funding leg. Check network support first: on many payout APIs, USDT runs on Ethereum, Polygon, Solana, and Tron, but not on Base or Arbitrum, while USDC is the reverse on Tron.\"\n  - q: \"What happens if the CLABE is wrong?\"\n    a: \"If the CLABE fails its check digit, a good provider rejects it when you save the bank account. If it is valid but closed or belongs to someone else, the receiving bank can return the SPEI transfer, and Banxico's MI-SPEI service would show it as undergoing return or returned. A valid CLABE for the wrong person is the expensive case, because SPEI routes on the account number.\"\n  - q: \"Do I need the recipient's RFC to pay them over SPEI?\"\n    a: \"Not to route the money. SPEI moves pesos on the CLABE, card, or phone number. Collect the RFC anyway when your finance team needs it for supplier invoices, contractor records, or tax filings, and keep it next to the payout record. Paying from a stablecoin balance does not change what you owe on the Mexican tax side.\"\n  - q: \"How does the recipient prove the payment arrived?\"\n    a: \"With a CEP, the electronic payment receipt Banco de México issues from the receiving bank's confirmation. Banxico says the CEP can take up to 30 minutes to become available and can be looked up for payments from the last 45 working days. It needs the date, the tracking key or reference, both banks, the receiving account, and the amount.\"\n---\n\nTo send USDC to a bank account in Mexico, onboard with a stablecoin payout API, add the recipient's CLABE and legal name, request a USDC to MXN quote, fund it from a wallet, and execute. The provider converts to pesos and delivers them over SPEI, which runs 24\u002F7, so most payouts land in minutes.\n\nThat's the short version. The rest of this guide is the detail that decides whether the first payout works: what to collect from each type of recipient, what each SPEI status means, and where Mexican payouts fail.\n\n**Key takeaways**\n\n- SPEI is Banco de México's real-time settlement system. It has run since August 13, 2004 and operates 24\u002F7, so weekends and holidays don't delay a peso payout.\n- Collect the legal name and an 18-digit CLABE. A debit card or phone number also works, but needs the bank's institution code.\n- Quote in pesos when the recipient must get an exact amount, and decide up front who pays the fee.\n- SPEI routes on the account number. A valid CLABE that belongs to the wrong person is the most expensive mistake in the corridor.\n- Store the SPEI tracking key with every payout. Banxico's CEP lookup turns it into a receipt anyone can check.\n\nIf you're new to the categories of APIs that do this, start with [the types of stablecoin APIs](\u002Fresources\u002Fmore\u002Ftypes-of-stablecoin-apis). This guide assumes a payout API: one that takes stablecoins in and sends local currency out.\n\n## What do you need before the first payout to Mexico?\n\nYou need three things before any money moves: a verified sender, a verified recipient bank account, and USDC or USDT on a network the provider accepts.\n\nThe sender side is onboarding. A business completes KYB once, an individual completes KYC. Nothing in the Mexico corridor skips this.\n\nThe recipient side is where most teams under-collect. What you need depends on who you're paying, so build the form per recipient type instead of one generic \"bank details\" box.\n\n### Recipient data checklist by recipient type\n\n| Recipient | Account identifier | Name to collect | Keep on file |\n| --- | --- | --- | --- |\n| Employee | CLABE | Full legal name on the account | Payroll record, RFC if finance needs it |\n| Independent contractor | CLABE | Full legal name on the account | Contract and the invoice being paid |\n| Supplier (company) | CLABE of the company's account | Legal company name, not the trade name | The supplier's invoice and its RFC |\n| Family member (remittance) | CLABE, debit card, or phone number | Full legal name | Relationship and, if asked, source of funds |\n| Your own Mexican entity | CLABE | The entity's legal name | Intercompany agreement |\n\nTwo details from that table trip teams up. First, a debit card or phone number only works with the receiving bank's institution code, so the form has to ask for the bank too. Second, the relationship matters to compliance. Payout APIs usually ask whether the account belongs to the sender, an employee, a contractor, or a supplier, and some run a name-match check only when you pay your own account.\n\nThe field-by-field anatomy of a CLABE, including the check digit math, is in [what details you need to pay someone in Brazil or Mexico](\u002Fresources\u002Fmore\u002Fpix-key-cpf-clabe-payout-details). Validate it client-side. It catches typos before they become returns.\n\n## How do you send USDC to a Mexican bank account step by step?\n\nYou add the bank account once, then quote, fund, and execute each payout against it. The field names below come from BlindPay's API ([bank accounts](\u002Fdocs\u002Fbank-accounts), [payout quotes](\u002Fdocs\u002Fpayout-quotes), [payouts](\u002Fdocs\u002Fpayouts)); other providers use similar objects with different names.\n\n1. **Add the bank account.** Create a SPEI bank account on the customer with `beneficiary_name`, `spei_protocol` (CLABE, debit card, or phone), the identifier, and `spei_institution_code` when the protocol is card or phone. Validation runs the same way on development and production, so a malformed CLABE fails in testing.\n2. **Filter the bank list.** If you build a bank picker from the provider's bank-details endpoint, drop inactive banks. Some providers, BlindPay included, return them flagged `is_active: false` instead of removing them.\n3. **Request a quote.** Quote against the bank account with a `network` and `token`. Set `currency_type` to `receiver` to fix the peso amount, or `sender` to fix the USDC amount. Set `cover_fees: true` if the recipient must get the full amount. Amounts are integers in minor units.\n4. **Execute before the quote expires.** Here that's 5 minutes after creation. Past that, request a new one.\n5. **Fund it.** From a managed wallet, pass its address and you're done. From a wallet you control, authorize first: an ERC-20 approve on EVM chains, a signed transaction on Stellar, or a token delegation on Solana.\n6. **Create the payout.** One call against the quote ID. The stablecoins leave the funding wallet, convert to pesos, and go out over SPEI.\n7. **Track it.** `payout.update` fires on status changes and `payout.complete` fires when the payout reaches `completed`, `failed`, or `refunded`.\n\nNetwork choice is part of step 3. In this API's matrix, USDC payouts can be funded on networks including Ethereum, Polygon, Base, Arbitrum, Stellar, and Solana, and USDT on Ethereum, Polygon, Solana, and Tron. USDT isn't available on Base, Arbitrum, or Stellar, and USDC isn't on Tron. The full matrix is in [supported chains](\u002Fdocs\u002Fkb\u002Fsupported-chains). The recipient never sees any of this. They get pesos.\n\n## What happens to the pesos inside SPEI?\n\nOnce the provider releases the transfer, SPEI settles it between the two banks in real time, and the receiving bank credits the account.\n\nBanco de México runs SPEI as a [real-time settlement system on a 24\u002F7 schedule](https:\u002F\u002Fwww.banxico.org.mx\u002Fservicios\u002Fspei_-informacion-banco-mex.html). Its [user guide](https:\u002F\u002Fwww.banxico.org.mx\u002Fservices\u002Finterbanking-electronic-payme.html) cites Notice 17\u002F2010: a SPEI payment should not take more than 30 seconds after approval. That's why \"minutes\" is a fair ETA for the whole payout, and why a Friday night payout lands like a Tuesday morning one.\n\nYour provider's status is the first thing to check. When you need the bank-level view, Banxico's MI-SPEI service reports these states:\n\n| SPEI status | What it means | What to do |\n| --- | --- | --- |\n| Being processed | SPEI received the order, money not yet deposited | Wait. This normally clears in seconds |\n| Liquidated | SPEI settled it; the receiving bank can credit the account | Send the recipient the tracking key |\n| Cancelled | The sending bank cancelled before the money moved | Check the payout status with your provider |\n| Rejected | SPEI rejected it for errors or inconsistent data | Fix the account data, then send a new payout |\n| Undergoing return | The receiving bank is sending the money back | Don't resend yet; wait for the return to finish |\n| Returned | The money is back with the sender | Confirm the account details, then resend |\n| Cancelled at the close | Not authorized before SPEI's close of operations | Check with your provider before resending |\n| Not found | No SPEI record matches the search | Recheck the date, key, and amount you searched |\n\n\"Liquidated\" is the state that matters for disputes. From there, the recipient's bank has the money, and a CEP can prove it.\n\n## How do you prove a SPEI payment arrived?\n\nYou prove it with the CEP, the electronic payment receipt Banco de México issues from the receiving bank's confirmation.\n\nAccording to Banxico, the CEP can take up to 30 minutes after the deposit to become available, and it can be looked up for SPEI payments from the last 45 working days. The lookup needs the date, the tracking key or reference, the sending and receiving banks, the receiving account, and the amount. Download it at [Banxico's CEP page](https:\u002F\u002Fwww.banxico.org.mx\u002Fcep\u002F). The CEP comes as a PDF and an XML file with a digital seal, so an auditor can validate it.\n\nPractical rule: store the tracking key on your payout record the moment you have it. A recipient who says \"I didn't get it\" gets a CEP link, not a support ticket. [How to track an off-ramp payout](\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout) covers the same idea across every rail.\n\n## Where do USDC payouts to Mexico fail?\n\nMost failures come from recipient data, not from SPEI. Here are the eight that show up most, with the fix.\n\n1. **CLABE with a bad check digit.** Fix: validate the 18th digit in the form.\n2. **A 16-digit card number in the CLABE field.** Fix: a length check per protocol.\n3. **Card or phone payout without the institution code.** Fix: make the bank field required for those protocols.\n4. **Trade name instead of legal name.** Fix: ask for the name exactly as the bank registered it.\n5. **A valid CLABE that belongs to someone else.** SPEI won't catch this. Fix: confirm new accounts with the recipient before the first large payout, for example with a small first payment.\n6. **Expired quote.** Fix: quote right before execution, never from a cache.\n7. **Recipient doesn't recognize the sender.** On BlindPay, SPEI payouts show BlindPay's name as the sender ([payout descriptor](\u002Fdocs\u002Fkb\u002Fpayout-descriptor)). Fix: tell recipients in advance and put your invoice or payroll ID in the reference.\n8. **Assuming `failed` means refunded.** It doesn't. Here, `refunded` means the stablecoins went back to the funding source; `failed` does not refund automatically, so contact support.\n\nOn references: Banxico's guide says the payment description that reaches the payee runs up to 40 characters. Whatever your provider passes through, put the invoice or payroll ID at the front.\n\n## How should different businesses run the Mexico corridor?\n\nThe steps are the same for everyone; the quote settings and records change by use case. These are illustrative scenarios, not customer stories.\n\n| Use case | Illustrative scenario | Quote setting | Record to keep |\n| --- | --- | --- | --- |\n| Contractor payroll | A US startup pays 40 engineers in Guadalajara every two weeks | Fix the peso amount, sender covers fees | Contract and invoice per contractor |\n| Supplier payments | An importer pays a Monterrey manufacturer a MXN invoice | Fix the peso amount to match the invoice | Supplier invoice and RFC |\n| Marketplace payouts | A platform pays out weekly seller balances | Fix the USDC amount, fees from the payout | Seller ledger entry per payout |\n| Remittance | An app lets US users send pesos to family | Show the peso amount before confirming | Sender KYC and relationship |\n\nPayroll is the clearest case for fixed-receiver quotes: contractors expect a round peso number, not whatever is left after fees. [Stablecoin payroll for LATAM contractors](\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors) goes deeper on that flow.\n\n## What Mexican rules should you know about?\n\nMexico regulates financial technology and virtual asset activity under its 2018 Fintech Law, with Banco de México and the CNBV as the main authorities, and the SAT handles tax. Paying from a stablecoin balance doesn't change the recipient's tax treatment or your payroll and supplier obligations; it changes how the pesos get there.\n\nThe rules for converting USDC to pesos, and the stablecoin bill introduced in the Senate in May 2026, are covered in [USDC to MXN routes compared](\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026). Confirm your specific obligations in Mexico with qualified counsel before launching a corridor.\n\n## How do you choose a provider for Mexico payouts?\n\nScore each provider on eight criteria, and test the ones you can in a sandbox instead of asking.\n\n| Criterion | What to test | Red flag |\n| --- | --- | --- |\n| SPEI protocols | Can you pay to CLABE, debit card, and phone? | CLABE only, with no plan for the rest |\n| Validation | Does a bad CLABE fail at bank account creation? | It fails days later as a return |\n| Quote control | Can you fix the peso amount and choose who pays fees? | Only sender-side amounts |\n| Funding networks | Is your token supported on the network you hold it on? | One chain, or USDC only |\n| Pre-funding | Do you need a peso balance parked in Mexico? | A float that grows with volume |\n| Status detail | Do webhooks separate conversion from bank delivery? | One \"pending\" until \"done\" |\n| Tracking reference | Do you get a reference you can take to Banxico's CEP lookup? | No rail reference exposed |\n| Refund rules | What happens to the stablecoins when a payout can't complete? | No written answer |\n\n## How does BlindPay handle Mexico payouts?\n\nBlindPay pays out pesos over SPEI to a CLABE, debit card, or phone number, funded with USDC or USDT from a managed wallet or a wallet you control, with no pre-funded peso balance. KYC, KYB, and sanctions screening run inside the payout flow. The same API also pays out over Pix, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO), and SDKs for Node.js, Python, Go, PHP, and Swift wrap it.\n\nFor the Brazil version of this walkthrough, see [how to send USDC to a bank account in Brazil](\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil). Then send a test payout to a CLABE on a free development instance with the [payout quickstart](\u002Fdocs\u002Fquickstart-payout), and check today's rate on the [USDC to MXN page](\u002Fusdc-to-mxn).\n\n*This article is general information, not legal or tax advice.*\n",{"title":5,"description":805},"How to send USDC to a bank account in Mexico over SPEI","resources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","qCIL3FlPe6oWyLr4gC358HLyzqUXZ0RZvddHh23dK6Y",[858,862,866,870,874,878,882,886,890,894,898,902,906,910,914,918,922,926,930,934,938,942,946,950,954,958,962,966,970,974,978,982,986,990,993,994,998,1002,1006,1010,1014,1018,1022,1026,1030,1034,1038,1042,1046,1050,1054,1058,1062,1066,1070,1074,1078,1082,1086,1089,1093,1097,1101,1105,1109,1113,1117,1121,1124,1128,1132,1136,1140,1143,1147,1151,1155,1159,1163,1167,1171,1175,1178,1182],{"path":859,"title":860,"description":861},"\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":863,"title":864,"description":865},"\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":867,"title":868,"description":869},"\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":871,"title":872,"description":873},"\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":875,"title":876,"description":877},"\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":879,"title":880,"description":881},"\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":883,"title":884,"description":885},"\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":887,"title":888,"description":889},"\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":891,"title":892,"description":893},"\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":895,"title":896,"description":897},"\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":899,"title":900,"description":901},"\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":903,"title":904,"description":905},"\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":907,"title":908,"description":909},"\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":911,"title":912,"description":913},"\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":915,"title":916,"description":917},"\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":919,"title":920,"description":921},"\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":923,"title":924,"description":925},"\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":927,"title":928,"description":929},"\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":931,"title":932,"description":933},"\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":935,"title":936,"description":937},"\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":939,"title":940,"description":941},"\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":943,"title":944,"description":945},"\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":947,"title":948,"description":949},"\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":951,"title":952,"description":953},"\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":955,"title":956,"description":957},"\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":959,"title":960,"description":961},"\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":963,"title":964,"description":965},"\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":967,"title":968,"description":969},"\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":971,"title":972,"description":973},"\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":975,"title":976,"description":977},"\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":979,"title":980,"description":981},"\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":983,"title":984,"description":985},"\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":987,"title":988,"description":989},"\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":769,"title":991,"description":992},"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":851,"title":5,"description":805},{"path":995,"title":996,"description":997},"\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":999,"title":1000,"description":1001},"\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":1003,"title":1004,"description":1005},"\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":1007,"title":1008,"description":1009},"\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":1011,"title":1012,"description":1013},"\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":1015,"title":1016,"description":1017},"\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":1019,"title":1020,"description":1021},"\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":1023,"title":1024,"description":1025},"\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":1027,"title":1028,"description":1029},"\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":1031,"title":1032,"description":1033},"\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":1035,"title":1036,"description":1037},"\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":1039,"title":1040,"description":1041},"\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":1043,"title":1044,"description":1045},"\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":1047,"title":1048,"description":1049},"\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":1051,"title":1052,"description":1053},"\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":1055,"title":1056,"description":1057},"\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":1059,"title":1060,"description":1061},"\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":1063,"title":1064,"description":1065},"\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":1067,"title":1068,"description":1069},"\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":1071,"title":1072,"description":1073},"\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":1075,"title":1076,"description":1077},"\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":1079,"title":1080,"description":1081},"\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":1083,"title":1084,"description":1085},"\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":627,"title":1087,"description":1088},"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":1090,"title":1091,"description":1092},"\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":1094,"title":1095,"description":1096},"\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":1098,"title":1099,"description":1100},"\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":1102,"title":1103,"description":1104},"\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":1106,"title":1107,"description":1108},"\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":1110,"title":1111,"description":1112},"\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":1114,"title":1115,"description":1116},"\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":1118,"title":1119,"description":1120},"\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":642,"title":1122,"description":1123},"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":1125,"title":1126,"description":1127},"\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":1129,"title":1130,"description":1131},"\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":1133,"title":1134,"description":1135},"\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":1137,"title":1138,"description":1139},"\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":171,"title":1141,"description":1142},"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":1144,"title":1145,"description":1146},"\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":1148,"title":1149,"description":1150},"\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":1152,"title":1153,"description":1154},"\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":1156,"title":1157,"description":1158},"\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":1160,"title":1161,"description":1162},"\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":1164,"title":1165,"description":1166},"\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":1168,"title":1169,"description":1170},"\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":1172,"title":1173,"description":1174},"\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":462,"title":1176,"description":1177},"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":1179,"title":1180,"description":1181},"\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":1183,"title":1184,"description":1185},"\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.",1791398892520]