[{"data":1,"prerenderedAt":1056},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received":3,"resources-category-virtual-account-deposit-not-received":769},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":739,"categoryType":6,"compare":6,"contributors":6,"date":740,"description":741,"extension":742,"faq":743,"howto":6,"isBlog":759,"isChangelog":759,"meta":760,"navigation":762,"path":763,"pillar":759,"products":6,"rawbody":764,"role":6,"seo":765,"seoTitle":766,"stem":767,"thumbnail":6,"updated":6,"__hash__":768},"content\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received.md","Virtual account deposit not received? Why deposits get delayed, held, or returned",null,{"type":8,"value":9,"toc":725},"minimark",[10,14,17,22,46,50,53,168,177,181,184,192,251,259,262,265,269,272,367,410,437,441,447,455,463,475,483,487,490,529,535,539,542,587,594,598,601,607,638,654,663,666,673,677,680,687,699,703,719],[11,12,13],"p",{},"A virtual account deposit that hasn't shown up is usually one of four things: it's still inside the rail's settlement window, it's held for compliance review, a bank returned it because the details didn't match, or the payer used a rail the account doesn't accept. The deposit's status and the payer's bank reference tell you which one.",[11,15,16],{},"Start with the status, not the support ticket.",[18,19,21],"h2",{"id":20},"key-takeaways","Key takeaways",[23,24,25,29,37,40,43],"ul",{},[26,27,28],"li",{},"ACH and wire deposits can take up to 5 business days, and anything sent after the cut-off starts counting from the next business day.",[26,30,31,32,36],{},"A deposit ",[33,34,35],"code",{},"on_hold"," is waiting on compliance review. Answer the request for information the same day: an unanswered hold can end in a refund to the sender.",[26,38,39],{},"Returns usually trace back to details that don't match: a wrong account number, a beneficiary name that isn't the account holder, or a closed account.",[26,41,42],{},"A US virtual account takes USD over ACH, wire, and SWIFT. Not SEPA, not Pix, and at BlindPay, not RTP.",[26,44,45],{},"To find a missing wire, ask the payer for the bank reference: the IMAD for a domestic wire, the UETR for SWIFT.",[18,47,49],{"id":48},"what-usually-goes-wrong-with-a-virtual-account-deposit","What usually goes wrong with a virtual account deposit?",[11,51,52],{},"Most missing deposits fit one of eight patterns, and each has a different fix. Match the symptom first, then act.",[54,55,56,72],"table",{},[57,58,59],"thead",{},[60,61,62,66,69],"tr",{},[63,64,65],"th",{},"Symptom",[63,67,68],{},"Likely cause",[63,70,71],{},"What to do",[73,74,75,87,98,111,124,135,146,157],"tbody",{},[60,76,77,81,84],{},[78,79,80],"td",{},"Payer sent it today, nothing shows",[78,82,83],{},"Still in the settlement window, or sent after the cut-off",[78,85,86],{},"Wait out the rail's window before escalating",[60,88,89,92,95],{},[78,90,91],{},"Nothing after 5 business days",[78,93,94],{},"Wrong account or routing number, or the transfer never left the payer's bank",[78,96,97],{},"Ask the payer for the bank reference and trace it",[60,99,100,105,108],{},[78,101,102,103],{},"Deposit shows as ",[33,104,35],{},[78,106,107],{},"Flagged for compliance review",[78,109,110],{},"Watch for a request for information and answer it within 24 hours",[60,112,113,118,121],{},[78,114,102,115],{},[33,116,117],{},"refunded",[78,119,120],{},"Returned to the sender after a mismatch or an unanswered hold",[78,122,123],{},"Find the reason, fix it, ask the payer to resend",[60,125,126,129,132],{},[78,127,128],{},"Less money arrived than was sent",[78,130,131],{},"Intermediary or receiving bank fees on a wire or SWIFT payment",[78,133,134],{},"Reconcile it as a bank fee, not an underpayment",[60,136,137,140,143],{},[78,138,139],{},"Foreign payer asks for an IBAN",[78,141,142],{},"US virtual accounts have no IBAN",[78,144,145],{},"Send the SWIFT details and ask for USD",[60,147,148,151,154],{},[78,149,150],{},"Payer sent an instant RTP payment",[78,152,153],{},"RTP isn't a rail into a BlindPay virtual account",[78,155,156],{},"Ask for ACH or wire, or use an RTP payin's own instructions",[60,158,159,162,165],{},[78,160,161],{},"A $0.01 deposit appears",[78,163,164],{},"A platform verifying the account with a micro-deposit",[78,166,167],{},"Reconcile it, it's expected",[11,169,170,171,176],{},"New to the account itself? Start with ",[172,173,175],"a",{"href":174},"\u002Fresources\u002Fmore\u002Fwhat-is-a-virtual-account","what is a virtual account",".",[18,178,180],{"id":179},"why-hasnt-the-deposit-arrived-yet","Why hasn't the deposit arrived yet?",[11,182,183],{},"Most of the time, it's still on the rail. Bank transfers settle on business days, every rail has a daily cut-off, and a transfer sent after the cut-off is processed the next business day. Weekends, US federal holidays, and international banking holidays don't count.",[11,185,186,187,191],{},"These are the network windows from BlindPay's ",[172,188,190],{"href":189},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times"," reference:",[54,193,194,207],{},[57,195,196],{},[60,197,198,201,204],{},[63,199,200],{},"Rail",[63,202,203],{},"Cut-off (ET)",[63,205,206],{},"Typical network settlement",[73,208,209,220,231,240],{},[60,210,211,214,217],{},[78,212,213],{},"ACH",[78,215,216],{},"9:00 PM",[78,218,219],{},"1 to 3 business days",[60,221,222,225,228],{},[78,223,224],{},"Same-Day ACH",[78,226,227],{},"3:00 PM",[78,229,230],{},"Same business day",[60,232,233,236,238],{},[78,234,235],{},"Domestic wire",[78,237,227],{},[78,239,230],{},[60,241,242,245,248],{},[78,243,244],{},"International SWIFT",[78,246,247],{},"10:30 AM",[78,249,250],{},"Up to 5 business days",[11,252,253,254,258],{},"Those are network times, not end-to-end ETAs. For ACH and wire deposits, BlindPay's own arrival window is up to 5 business days (",[172,255,257],{"href":256},"\u002Fdocs\u002Fpayins","payins","). A SWIFT payment sent at 4:00 PM ET on the Friday before a US holiday can lose several calendar days before anyone has a reason to worry.",[11,260,261],{},"Check the payer's side too. Banks cap daily ACH and wire amounts, and a transfer over the cap can sit at the sending bank waiting for approval. From your side, that looks like a slow rail.",[11,263,264],{},"Rule of thumb: don't open a trace until the rail's full window has passed. Until then, the most useful thing your product can show is an expected arrival date.",[18,266,268],{"id":267},"which-statuses-will-a-virtual-account-deposit-go-through","Which statuses will a virtual account deposit go through?",[11,270,271],{},"Every deposit into a BlindPay virtual account creates a payin, and the payin's status tells you where the money is. There are five statuses, and three of them are final. Because the deposit itself creates the payin, no payin at all usually means the money hasn't reached the account.",[54,273,274,290],{},[57,275,276],{},[60,277,278,281,284,287],{},[63,279,280],{},"Status",[63,282,283],{},"What it means",[63,285,286],{},"Final?",[63,288,289],{},"What to show your customer",[73,291,292,308,322,338,353],{},[60,293,294,299,302,305],{},[78,295,296],{},[33,297,298],{},"processing",[78,300,301],{},"The deposit is arriving, or stablecoins are being converted and sent",[78,303,304],{},"No",[78,306,307],{},"\"Payment received, processing\"",[60,309,310,314,317,319],{},[78,311,312],{},[33,313,35],{},[78,315,316],{},"Held for manual risk or compliance review",[78,318,304],{},[78,320,321],{},"\"Under review, we may ask for details\"",[60,323,324,329,332,335],{},[78,325,326],{},[33,327,328],{},"completed",[78,330,331],{},"Stablecoins delivered to the linked wallet",[78,333,334],{},"Yes",[78,336,337],{},"\"Funds available\"",[60,339,340,345,348,350],{},[78,341,342],{},[33,343,344],{},"failed",[78,346,347],{},"The payin didn't go through",[78,349,334],{},[78,351,352],{},"\"Payment failed\" plus the next step",[60,354,355,359,362,364],{},[78,356,357],{},[33,358,117],{},[78,360,361],{},"The deposit went back to the sender",[78,363,334],{},[78,365,366],{},"\"Returned to sender\" plus the reason",[11,368,369,370,373,374,377,378,380,381,380,383,380,386,389,390,392,393,396,397,400,401,404,405,407,408,176],{},"For a finer view, each ",[33,371,372],{},"tracking_*"," object on the payin has its own ",[33,375,376],{},"step",": ",[33,379,298],{},", ",[33,382,35],{},[33,384,385],{},"pending_review",[33,387,388],{},"pending_refund_review",", or ",[33,391,328],{},". ",[33,394,395],{},"tracking_transaction"," covers the fiat leg and carries a separate ",[33,398,399],{},"status"," that stays ",[33,402,403],{},"null"," until the bank side resolves to ",[33,406,328],{}," or ",[33,409,344],{},[11,411,412,413,416,417,420,421,424,425,427,428,432,433,176],{},"The webhooks follow the same shape. ",[33,414,415],{},"payin.new"," fires when the deposit creates the payin, ",[33,418,419],{},"payin.update"," fires on intermediate steps like an arrival check or a manual review, and ",[33,422,423],{},"payin.complete"," fires when the payin is sent, refunded, or failed. So ",[33,426,423],{}," doesn't mean success. Read the status (",[172,429,431],{"href":430},"\u002Fdocs\u002Flearn\u002Fwebhooks-events","webhook events","). Signature checks and duplicate handling are in ",[172,434,436],{"href":435},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","stablecoin API webhooks",[18,438,440],{"id":439},"why-is-a-deposit-on-hold","Why is a deposit on hold?",[11,442,443,444,446],{},"A deposit lands ",[33,445,35],{}," when transaction monitoring flags it for manual review. It's a pause, not a rejection: if compliance clears it, the payin continues and the stablecoins go out.",[11,448,449,450,454],{},"The triggers BlindPay lists include unusual activity patterns, amounts that are large compared with the customer's history, sanctions or watchlist screening matches, and an open request for information on the customer (",[172,451,453],{"href":452},"\u002Fdocs\u002Fkb\u002Fcut-off-times#compliance-holds","compliance holds",").",[11,456,457,458,462],{},"If the flag can't be cleared internally, BlindPay emails your team (or sends a Slack message) with a request for information, or RFI. It asks for the relationship between the sender and your customer, the purpose of the payment, and the expected outcome. Per ",[172,459,461],{"href":460},"\u002Fdocs\u002Fkb\u002Fon-hold-transactions","on-hold transactions",", if the RFI isn't answered within 24 hours, the transaction may be refunded to the sender. A hold can last up to 30 days, and a timeout without a decision fails the transaction.",[11,464,465,466,469,470,474],{},"Don't mix this up with a customer-level RFI. When KYC or KYB review needs more documents, the customer moves to ",[33,467,468],{},"compliance_request",", can't send or receive funds until it's resolved, and gets 27 days to respond (",[172,471,473],{"href":472},"\u002Fdocs\u002Fkb\u002Finformation-requests","information requests","). Different trigger, different clock.",[11,476,477,478,482],{},"The best prevention is boring: keep an invoice or contract on file for each large payer, and make sure the business description from onboarding matches what flows through the account. ",[172,479,481],{"href":480},"\u002Fresources\u002Fmore\u002Fvirtual-account-requirements-kyc-kyb","Virtual account requirements"," covers what the review looks at.",[18,484,486],{"id":485},"why-do-deposits-get-returned-to-the-sender","Why do deposits get returned to the sender?",[11,488,489],{},"A deposit comes back when a bank in the chain or the compliance review can't accept it. The usual reasons are wrong details, a name mismatch, a closed or restricted account, unmet compliance requirements, or a rail the account doesn't take.",[23,491,492,499,505,511,517],{},[26,493,494,498],{},[495,496,497],"strong",{},"Wrong account or routing number."," ACH returns carry a reason code: R03 means the receiving bank couldn't locate the account, R04 means the account number is invalid, R02 means it's closed. A wire with a bad account number comes back the same way, just slower.",[26,500,501,504],{},[495,502,503],{},"Beneficiary name doesn't match."," A named virtual account is in your customer's name. The payer should use that exact name as the beneficiary, not your platform's brand or a trading nickname. Receiving banks can reject wires where the name and the account don't line up.",[26,506,507,510],{},[495,508,509],{},"The account isn't live, or isn't anymore."," A BlindPay virtual account has no rail numbers until it's approved, so any details a payer has from before approval are wrong. Payments to an account that's closed or restricted fail or get refunded.",[26,512,513,516],{},[495,514,515],{},"Compliance requirements aren't met."," This includes the hold from the section above where nobody answered the RFI.",[26,518,519,522,523,526,527,454],{},[495,520,521],{},"The payer used a rail the account doesn't take."," RTP isn't one: at BlindPay, no virtual account carries an RTP rail, and an ",[33,524,525],{},"rtp"," payin always uses the shared memo-code account. SEPA needs an IBAN, which a US account doesn't have. SWIFT works, but only once the account is approved, since there's no memo-code fallback for SWIFT (",[172,528,257],{"href":256},[11,530,531,532,534],{},"When a deposit is ",[33,533,117],{},", the money goes back to the sender, not to the wallet. Fiat refunds reach the payer once the banking network returns the funds, which depends on each bank's processing time, and fees may apply. Your customer's client can get back less than they sent.",[18,536,538],{"id":537},"how-do-you-trace-a-missing-wire-or-swift-payment","How do you trace a missing wire or SWIFT payment?",[11,540,541],{},"Trace with the payer's bank reference, not the amount. Every rail has one, and it's the only thing a bank's operations team can search by.",[543,544,545,551,557,563,569,575,581],"ol",{},[26,546,547,550],{},[495,548,549],{},"Confirm the window has passed."," Up to 5 business days for ACH, wire, and SWIFT, counted from the first business day after the cut-off.",[26,552,553,556],{},[495,554,555],{},"Check the details against the right rail."," The account object carries separate ACH and wire details. A payer who copied the ACH numbers into a wire form, or the reverse, may have sent the money somewhere else.",[26,558,559,562],{},[495,560,561],{},"Get the reference."," For ACH, the 15-digit trace number. For a domestic wire, the Fedwire IMAD (Input Message Accountability Data). For SWIFT, the UETR, a 36-character reference that follows a payment end to end.",[26,564,565,568],{},[495,566,567],{},"Ask for the MT103 on SWIFT payments."," It shows the beneficiary name (field 59), the amount and currency, the charge code (field 71A: OUR, SHA, or BEN), and the intermediary banks.",[26,570,571,574],{},[495,572,573],{},"Have the payer's bank trace it."," With the UETR, the sending bank can see which bank in the chain is holding the payment and why.",[26,576,577,580],{},[495,578,579],{},"Send everything to your provider."," Include the virtual account id, the expected amount, the date sent, and the reference.",[26,582,583,586],{},[495,584,585],{},"If it was returned, resend with corrected details"," once the return has credited the payer.",[11,588,589,590,176],{},"Where the days go on a SWIFT payment, hop by hop, is in ",[172,591,593],{"href":592},"\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow","why are cross-border payments slow",[18,595,597],{"id":596},"what-does-a-held-swift-deposit-look-like-start-to-finish","What does a held SWIFT deposit look like, start to finish?",[11,599,600],{},"Here's one deposit through two endings. Amounts and timings are illustrative, not quotes.",[11,602,603,606],{},[495,604,605],{},"Setup."," A client in Germany pays a 4,800 USD invoice to your customer's US virtual account by SWIFT, with the SHA charge option.",[543,608,609,615,626],{},[26,610,611,614],{},[495,612,613],{},"Day 0."," The client's bank sends the payment late in the afternoon, so it starts moving the next business day.",[26,616,617,620,621,623,624,176],{},[495,618,619],{},"Day 3."," An intermediary bank deducts 30 USD. 4,770 USD lands on the virtual account. The payin is created (",[33,622,415],{},") and moves to ",[33,625,298],{},[26,627,628,631,632,634,635,637],{},[495,629,630],{},"Day 3, an hour later."," Monitoring flags it: first payment from this sender, and about four times the customer's usual deposit. The payin goes ",[33,633,35],{}," (",[33,636,419],{},"), and your team gets an RFI email.",[11,639,640,643,644,647,648,650,651,653],{},[495,641,642],{},"Ending A: you answer the same day."," You send the invoice and the service contract. Compliance releases the hold, the 4,770 USD converts to USDC, and because the deposit is over $100, BlindPay's fee is deducted from the delivered amount at transaction time (",[33,645,646],{},"transaction_fee_amount","). ",[33,649,423],{}," arrives with status ",[33,652,328],{},". Your ledger books 4,800 invoiced, 30 bank fee, the BlindPay fee, and the net USDC received. Done.",[11,655,656,659,660,662],{},[495,657,658],{},"Ending B: nobody answers for 24 hours."," The transaction may be refunded. The payin ends ",[33,661,117],{},", and the 4,770 USD travels back through the banking network, possibly minus more fees. The client gets a partial refund days later and has to pay again. Same money, two weeks lost.",[11,664,665],{},"The difference between the two endings is one email. Put RFIs on someone's on-call rota.",[11,667,668,669,176],{},"How each fee in that chain works, including where the BlindPay fee lands below and above $100, is in ",[172,670,672],{"href":671},"\u002Fresources\u002Fmore\u002Fvirtual-account-fees","virtual account fees",[18,674,676],{"id":675},"where-does-blindpay-fit","Where does BlindPay fit?",[11,678,679],{},"BlindPay issues US virtual accounts in your customer's own name. They receive ACH, wire, and SWIFT, depending on the account type, and every deposit converts to USDC or USDT and settles to the wallet linked to the account. The account doesn't hold a balance. The money ends up in the wallet.",[11,681,682,683,686],{},"Each deposit is a payin with a status, tracking steps, and ",[33,684,685],{},"payin.*"," webhooks, so \"where is my money\" has an API answer. Holds come with an RFI to your team.",[11,688,689,690,694,695,176],{},"What it doesn't do: IBANs, SEPA, or RTP into the dedicated account. If your payers are in Europe, they pay by SWIFT in USD. The full account behavior is in ",[172,691,693],{"href":692},"\u002Fdocs\u002Fvirtual-accounts","virtual accounts",", and the flow from bank deposit to wallet is in ",[172,696,698],{"href":697},"\u002Fresources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins","accept bank transfers and settle in stablecoins",[18,700,702],{"id":701},"what-to-do-next","What to do next",[11,704,705,706,708,709,712,713,715,716,718],{},"Map all five payin statuses to customer-facing messages, and name an owner for ",[33,707,35],{}," RFIs, before your next account goes live. Then build the failure screens on a development instance: a payin with a ",[33,710,711],{},"request_amount"," of $666.00 forces ",[33,714,344],{},", and $777.00 forces ",[33,717,117],{},". You'll see both in production eventually. Better to see them first in a sandbox.",[11,720,721],{},[722,723,724],"em",{},"This article is for general information only and is not legal, tax, or financial advice.",{"title":726,"searchDepth":727,"depth":727,"links":728},"",2,[729,730,731,732,733,734,735,736,737,738],{"id":20,"depth":727,"text":21},{"id":48,"depth":727,"text":49},{"id":179,"depth":727,"text":180},{"id":267,"depth":727,"text":268},{"id":439,"depth":727,"text":440},{"id":485,"depth":727,"text":486},{"id":537,"depth":727,"text":538},{"id":596,"depth":727,"text":597},{"id":675,"depth":727,"text":676},{"id":701,"depth":727,"text":702},"payments","2026-09-13","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.","md",[744,747,750,753,756],{"q":745,"a":746},"How long does a virtual account deposit take to arrive?","It depends on the rail. On the networks, ACH settles in 1 to 3 business days, Same-Day ACH and domestic wires on the same business day, and SWIFT in up to 5 business days. Transfers sent after the daily cut-off start counting from the next business day. At BlindPay, the arrival window for ACH and wire deposits is up to 5 business days.",{"q":748,"a":749},"Why is my virtual account deposit on hold?","A deposit goes on hold when transaction monitoring flags it for manual compliance review, for example an unusual activity pattern or an amount that's large for that customer. It's a pause, not a rejection. At BlindPay, your team may get a request for information about the sender and the purpose. If it isn't answered within 24 hours, the deposit may be refunded to the sender.",{"q":751,"a":752},"Why was my virtual account deposit returned?","Deposits usually come back because the details didn't match: a wrong account or routing number, a beneficiary name that isn't the account holder's, or an account that's closed or restricted. Unmet compliance requirements, including a hold nobody answered, can also end in a refund. Fiat refunds reach the payer once the banking network returns the funds, and fees may apply.",{"q":754,"a":755},"Can a US virtual account receive SEPA, Pix, or RTP payments?","Not at BlindPay. A US virtual account receives USD over ACH, wire, and SWIFT, depending on the account type. It has no IBAN, so SEPA payers need the SWIFT details instead, and Pix is a Brazilian rail with its own instructions. RTP payins go through BlindPay's shared memo-code account, not the dedicated account, even when the customer has an approved virtual account.",{"q":757,"a":758},"Why did less money arrive than the payer sent?","On wires, and SWIFT payments in particular, banks in the chain can deduct their own fees before the money lands. With the SHA charge option, the payer covers their own bank and the beneficiary absorbs intermediary and receiving fees. With BEN, every fee comes out of the amount. Ask the payer for the MT103, which shows the charge code, and book the gap as a bank fee.",false,{"author":761},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received","---\ntitle: \"Virtual account deposit not received? Why deposits get delayed, held, or returned\"\nseoTitle: \"Virtual account deposit not received? Holds and returns\"\ndescription: \"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.\"\ndate: \"2026-09-13\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"How long does a virtual account deposit take to arrive?\"\n    a: \"It depends on the rail. On the networks, ACH settles in 1 to 3 business days, Same-Day ACH and domestic wires on the same business day, and SWIFT in up to 5 business days. Transfers sent after the daily cut-off start counting from the next business day. At BlindPay, the arrival window for ACH and wire deposits is up to 5 business days.\"\n  - q: \"Why is my virtual account deposit on hold?\"\n    a: \"A deposit goes on hold when transaction monitoring flags it for manual compliance review, for example an unusual activity pattern or an amount that's large for that customer. It's a pause, not a rejection. At BlindPay, your team may get a request for information about the sender and the purpose. If it isn't answered within 24 hours, the deposit may be refunded to the sender.\"\n  - q: \"Why was my virtual account deposit returned?\"\n    a: \"Deposits usually come back because the details didn't match: a wrong account or routing number, a beneficiary name that isn't the account holder's, or an account that's closed or restricted. Unmet compliance requirements, including a hold nobody answered, can also end in a refund. Fiat refunds reach the payer once the banking network returns the funds, and fees may apply.\"\n  - q: \"Can a US virtual account receive SEPA, Pix, or RTP payments?\"\n    a: \"Not at BlindPay. A US virtual account receives USD over ACH, wire, and SWIFT, depending on the account type. It has no IBAN, so SEPA payers need the SWIFT details instead, and Pix is a Brazilian rail with its own instructions. RTP payins go through BlindPay's shared memo-code account, not the dedicated account, even when the customer has an approved virtual account.\"\n  - q: \"Why did less money arrive than the payer sent?\"\n    a: \"On wires, and SWIFT payments in particular, banks in the chain can deduct their own fees before the money lands. With the SHA charge option, the payer covers their own bank and the beneficiary absorbs intermediary and receiving fees. With BEN, every fee comes out of the amount. Ask the payer for the MT103, which shows the charge code, and book the gap as a bank fee.\"\n---\n\nA virtual account deposit that hasn't shown up is usually one of four things: it's still inside the rail's settlement window, it's held for compliance review, a bank returned it because the details didn't match, or the payer used a rail the account doesn't accept. The deposit's status and the payer's bank reference tell you which one.\n\nStart with the status, not the support ticket.\n\n## Key takeaways\n\n- ACH and wire deposits can take up to 5 business days, and anything sent after the cut-off starts counting from the next business day.\n- A deposit `on_hold` is waiting on compliance review. Answer the request for information the same day: an unanswered hold can end in a refund to the sender.\n- Returns usually trace back to details that don't match: a wrong account number, a beneficiary name that isn't the account holder, or a closed account.\n- A US virtual account takes USD over ACH, wire, and SWIFT. Not SEPA, not Pix, and at BlindPay, not RTP.\n- To find a missing wire, ask the payer for the bank reference: the IMAD for a domestic wire, the UETR for SWIFT.\n\n## What usually goes wrong with a virtual account deposit?\n\nMost missing deposits fit one of eight patterns, and each has a different fix. Match the symptom first, then act.\n\n| Symptom | Likely cause | What to do |\n| --- | --- | --- |\n| Payer sent it today, nothing shows | Still in the settlement window, or sent after the cut-off | Wait out the rail's window before escalating |\n| Nothing after 5 business days | Wrong account or routing number, or the transfer never left the payer's bank | Ask the payer for the bank reference and trace it |\n| Deposit shows as `on_hold` | Flagged for compliance review | Watch for a request for information and answer it within 24 hours |\n| Deposit shows as `refunded` | Returned to the sender after a mismatch or an unanswered hold | Find the reason, fix it, ask the payer to resend |\n| Less money arrived than was sent | Intermediary or receiving bank fees on a wire or SWIFT payment | Reconcile it as a bank fee, not an underpayment |\n| Foreign payer asks for an IBAN | US virtual accounts have no IBAN | Send the SWIFT details and ask for USD |\n| Payer sent an instant RTP payment | RTP isn't a rail into a BlindPay virtual account | Ask for ACH or wire, or use an RTP payin's own instructions |\n| A $0.01 deposit appears | A platform verifying the account with a micro-deposit | Reconcile it, it's expected |\n\nNew to the account itself? Start with [what is a virtual account](\u002Fresources\u002Fmore\u002Fwhat-is-a-virtual-account).\n\n## Why hasn't the deposit arrived yet?\n\nMost of the time, it's still on the rail. Bank transfers settle on business days, every rail has a daily cut-off, and a transfer sent after the cut-off is processed the next business day. Weekends, US federal holidays, and international banking holidays don't count.\n\nThese are the network windows from BlindPay's [cut-off times](\u002Fdocs\u002Fkb\u002Fcut-off-times) reference:\n\n| Rail | Cut-off (ET) | Typical network settlement |\n| --- | --- | --- |\n| ACH | 9:00 PM | 1 to 3 business days |\n| Same-Day ACH | 3:00 PM | Same business day |\n| Domestic wire | 3:00 PM | Same business day |\n| International SWIFT | 10:30 AM | Up to 5 business days |\n\nThose are network times, not end-to-end ETAs. For ACH and wire deposits, BlindPay's own arrival window is up to 5 business days ([payins](\u002Fdocs\u002Fpayins)). A SWIFT payment sent at 4:00 PM ET on the Friday before a US holiday can lose several calendar days before anyone has a reason to worry.\n\nCheck the payer's side too. Banks cap daily ACH and wire amounts, and a transfer over the cap can sit at the sending bank waiting for approval. From your side, that looks like a slow rail.\n\nRule of thumb: don't open a trace until the rail's full window has passed. Until then, the most useful thing your product can show is an expected arrival date.\n\n## Which statuses will a virtual account deposit go through?\n\nEvery deposit into a BlindPay virtual account creates a payin, and the payin's status tells you where the money is. There are five statuses, and three of them are final. Because the deposit itself creates the payin, no payin at all usually means the money hasn't reached the account.\n\n| Status | What it means | Final? | What to show your customer |\n| --- | --- | --- | --- |\n| `processing` | The deposit is arriving, or stablecoins are being converted and sent | No | \"Payment received, processing\" |\n| `on_hold` | Held for manual risk or compliance review | No | \"Under review, we may ask for details\" |\n| `completed` | Stablecoins delivered to the linked wallet | Yes | \"Funds available\" |\n| `failed` | The payin didn't go through | Yes | \"Payment failed\" plus the next step |\n| `refunded` | The deposit went back to the sender | Yes | \"Returned to sender\" plus the reason |\n\nFor a finer view, each `tracking_*` object on the payin has its own `step`: `processing`, `on_hold`, `pending_review`, `pending_refund_review`, or `completed`. `tracking_transaction` covers the fiat leg and carries a separate `status` that stays `null` until the bank side resolves to `completed` or `failed`.\n\nThe webhooks follow the same shape. `payin.new` fires when the deposit creates the payin, `payin.update` fires on intermediate steps like an arrival check or a manual review, and `payin.complete` fires when the payin is sent, refunded, or failed. So `payin.complete` doesn't mean success. Read the status ([webhook events](\u002Fdocs\u002Flearn\u002Fwebhooks-events)). Signature checks and duplicate handling are in [stablecoin API webhooks](\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation).\n\n## Why is a deposit on hold?\n\nA deposit lands `on_hold` when transaction monitoring flags it for manual review. It's a pause, not a rejection: if compliance clears it, the payin continues and the stablecoins go out.\n\nThe triggers BlindPay lists include unusual activity patterns, amounts that are large compared with the customer's history, sanctions or watchlist screening matches, and an open request for information on the customer ([compliance holds](\u002Fdocs\u002Fkb\u002Fcut-off-times#compliance-holds)).\n\nIf the flag can't be cleared internally, BlindPay emails your team (or sends a Slack message) with a request for information, or RFI. It asks for the relationship between the sender and your customer, the purpose of the payment, and the expected outcome. Per [on-hold transactions](\u002Fdocs\u002Fkb\u002Fon-hold-transactions), if the RFI isn't answered within 24 hours, the transaction may be refunded to the sender. A hold can last up to 30 days, and a timeout without a decision fails the transaction.\n\nDon't mix this up with a customer-level RFI. When KYC or KYB review needs more documents, the customer moves to `compliance_request`, can't send or receive funds until it's resolved, and gets 27 days to respond ([information requests](\u002Fdocs\u002Fkb\u002Finformation-requests)). Different trigger, different clock.\n\nThe best prevention is boring: keep an invoice or contract on file for each large payer, and make sure the business description from onboarding matches what flows through the account. [Virtual account requirements](\u002Fresources\u002Fmore\u002Fvirtual-account-requirements-kyc-kyb) covers what the review looks at.\n\n## Why do deposits get returned to the sender?\n\nA deposit comes back when a bank in the chain or the compliance review can't accept it. The usual reasons are wrong details, a name mismatch, a closed or restricted account, unmet compliance requirements, or a rail the account doesn't take.\n\n- **Wrong account or routing number.** ACH returns carry a reason code: R03 means the receiving bank couldn't locate the account, R04 means the account number is invalid, R02 means it's closed. A wire with a bad account number comes back the same way, just slower.\n- **Beneficiary name doesn't match.** A named virtual account is in your customer's name. The payer should use that exact name as the beneficiary, not your platform's brand or a trading nickname. Receiving banks can reject wires where the name and the account don't line up.\n- **The account isn't live, or isn't anymore.** A BlindPay virtual account has no rail numbers until it's approved, so any details a payer has from before approval are wrong. Payments to an account that's closed or restricted fail or get refunded.\n- **Compliance requirements aren't met.** This includes the hold from the section above where nobody answered the RFI.\n- **The payer used a rail the account doesn't take.** RTP isn't one: at BlindPay, no virtual account carries an RTP rail, and an `rtp` payin always uses the shared memo-code account. SEPA needs an IBAN, which a US account doesn't have. SWIFT works, but only once the account is approved, since there's no memo-code fallback for SWIFT ([payins](\u002Fdocs\u002Fpayins)).\n\nWhen a deposit is `refunded`, the money goes back to the sender, not to the wallet. Fiat refunds reach the payer once the banking network returns the funds, which depends on each bank's processing time, and fees may apply. Your customer's client can get back less than they sent.\n\n## How do you trace a missing wire or SWIFT payment?\n\nTrace with the payer's bank reference, not the amount. Every rail has one, and it's the only thing a bank's operations team can search by.\n\n1. **Confirm the window has passed.** Up to 5 business days for ACH, wire, and SWIFT, counted from the first business day after the cut-off.\n2. **Check the details against the right rail.** The account object carries separate ACH and wire details. A payer who copied the ACH numbers into a wire form, or the reverse, may have sent the money somewhere else.\n3. **Get the reference.** For ACH, the 15-digit trace number. For a domestic wire, the Fedwire IMAD (Input Message Accountability Data). For SWIFT, the UETR, a 36-character reference that follows a payment end to end.\n4. **Ask for the MT103 on SWIFT payments.** It shows the beneficiary name (field 59), the amount and currency, the charge code (field 71A: OUR, SHA, or BEN), and the intermediary banks.\n5. **Have the payer's bank trace it.** With the UETR, the sending bank can see which bank in the chain is holding the payment and why.\n6. **Send everything to your provider.** Include the virtual account id, the expected amount, the date sent, and the reference.\n7. **If it was returned, resend with corrected details** once the return has credited the payer.\n\nWhere the days go on a SWIFT payment, hop by hop, is in [why are cross-border payments slow](\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow).\n\n## What does a held SWIFT deposit look like, start to finish?\n\nHere's one deposit through two endings. Amounts and timings are illustrative, not quotes.\n\n**Setup.** A client in Germany pays a 4,800 USD invoice to your customer's US virtual account by SWIFT, with the SHA charge option.\n\n1. **Day 0.** The client's bank sends the payment late in the afternoon, so it starts moving the next business day.\n2. **Day 3.** An intermediary bank deducts 30 USD. 4,770 USD lands on the virtual account. The payin is created (`payin.new`) and moves to `processing`.\n3. **Day 3, an hour later.** Monitoring flags it: first payment from this sender, and about four times the customer's usual deposit. The payin goes `on_hold` (`payin.update`), and your team gets an RFI email.\n\n**Ending A: you answer the same day.** You send the invoice and the service contract. Compliance releases the hold, the 4,770 USD converts to USDC, and because the deposit is over $100, BlindPay's fee is deducted from the delivered amount at transaction time (`transaction_fee_amount`). `payin.complete` arrives with status `completed`. Your ledger books 4,800 invoiced, 30 bank fee, the BlindPay fee, and the net USDC received. Done.\n\n**Ending B: nobody answers for 24 hours.** The transaction may be refunded. The payin ends `refunded`, and the 4,770 USD travels back through the banking network, possibly minus more fees. The client gets a partial refund days later and has to pay again. Same money, two weeks lost.\n\nThe difference between the two endings is one email. Put RFIs on someone's on-call rota.\n\nHow each fee in that chain works, including where the BlindPay fee lands below and above $100, is in [virtual account fees](\u002Fresources\u002Fmore\u002Fvirtual-account-fees).\n\n## Where does BlindPay fit?\n\nBlindPay issues US virtual accounts in your customer's own name. They receive ACH, wire, and SWIFT, depending on the account type, and every deposit converts to USDC or USDT and settles to the wallet linked to the account. The account doesn't hold a balance. The money ends up in the wallet.\n\nEach deposit is a payin with a status, tracking steps, and `payin.*` webhooks, so \"where is my money\" has an API answer. Holds come with an RFI to your team.\n\nWhat it doesn't do: IBANs, SEPA, or RTP into the dedicated account. If your payers are in Europe, they pay by SWIFT in USD. The full account behavior is in [virtual accounts](\u002Fdocs\u002Fvirtual-accounts), and the flow from bank deposit to wallet is in [accept bank transfers and settle in stablecoins](\u002Fresources\u002Fmore\u002Faccept-bank-transfers-settle-in-stablecoins).\n\n## What to do next\n\nMap all five payin statuses to customer-facing messages, and name an owner for `on_hold` RFIs, before your next account goes live. Then build the failure screens on a development instance: a payin with a `request_amount` of $666.00 forces `failed`, and $777.00 forces `refunded`. You'll see both in production eventually. Better to see them first in a sandbox.\n\n*This article is for general information only and is not legal, tax, or financial advice.*\n",{"title":5,"description":741},"Virtual account deposit not received? Holds and returns","resources\u002Fmore\u002Fvirtual-account-deposit-not-received","y8Z_oulGHEmmTj3Z6Xacam7gRJhaITxycN5nGD88kmg",[770,774,778,782,786,790,794,798,802,806,810,814,818,822,826,830,834,838,842,846,850,854,858,862,866,870,874,878,882,886,890,894,898,902,906,910,914,918,922,926,930,934,938,941,945,949,953,957,961,965,969,973,977,981,985,989,993,997,1001,1005,1006,1010,1014,1018,1022,1026,1030,1034,1037,1041,1045,1049,1052],{"path":771,"title":772,"description":773},"\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":775,"title":776,"description":777},"\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":779,"title":780,"description":781},"\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":783,"title":784,"description":785},"\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":787,"title":788,"description":789},"\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":791,"title":792,"description":793},"\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":795,"title":796,"description":797},"\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":799,"title":800,"description":801},"\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":803,"title":804,"description":805},"\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":807,"title":808,"description":809},"\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":811,"title":812,"description":813},"\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":815,"title":816,"description":817},"\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":819,"title":820,"description":821},"\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":823,"title":824,"description":825},"\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":827,"title":828,"description":829},"\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":831,"title":832,"description":833},"\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":835,"title":836,"description":837},"\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":839,"title":840,"description":841},"\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":843,"title":844,"description":845},"\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":847,"title":848,"description":849},"\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":851,"title":852,"description":853},"\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":855,"title":856,"description":857},"\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":859,"title":860,"description":861},"\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":863,"title":864,"description":865},"\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":867,"title":868,"description":869},"\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":871,"title":872,"description":873},"\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":875,"title":876,"description":877},"\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":879,"title":880,"description":881},"\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":883,"title":884,"description":885},"\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":887,"title":888,"description":889},"\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":891,"title":892,"description":893},"\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":895,"title":896,"description":897},"\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":899,"title":900,"description":901},"\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":903,"title":904,"description":905},"\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":907,"title":908,"description":909},"\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":911,"title":912,"description":913},"\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":915,"title":916,"description":917},"\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":919,"title":920,"description":921},"\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":923,"title":924,"description":925},"\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":927,"title":928,"description":929},"\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":931,"title":932,"description":933},"\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":935,"title":936,"description":937},"\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":435,"title":939,"description":940},"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":942,"title":943,"description":944},"\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":946,"title":947,"description":948},"\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":950,"title":951,"description":952},"\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":954,"title":955,"description":956},"\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":958,"title":959,"description":960},"\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":962,"title":963,"description":964},"\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":966,"title":967,"description":968},"\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":970,"title":971,"description":972},"\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":974,"title":975,"description":976},"\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":978,"title":979,"description":980},"\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":982,"title":983,"description":984},"\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":986,"title":987,"description":988},"\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":990,"title":991,"description":992},"\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":994,"title":995,"description":996},"\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":998,"title":999,"description":1000},"\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":1002,"title":1003,"description":1004},"\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":763,"title":5,"description":741},{"path":1007,"title":1008,"description":1009},"\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":1011,"title":1012,"description":1013},"\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":1015,"title":1016,"description":1017},"\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":1019,"title":1020,"description":1021},"\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":1023,"title":1024,"description":1025},"\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":1027,"title":1028,"description":1029},"\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":1031,"title":1032,"description":1033},"\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":174,"title":1035,"description":1036},"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":1038,"title":1039,"description":1040},"\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":1042,"title":1043,"description":1044},"\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":1046,"title":1047,"description":1048},"\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":592,"title":1050,"description":1051},"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":1053,"title":1054,"description":1055},"\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.",1790867713211]