[{"data":1,"prerenderedAt":906},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link":3,"resources-category-virtual-account-vs-wallet-address-vs-payment-link":551},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":519,"categoryType":6,"compare":6,"contributors":6,"date":520,"description":521,"extension":522,"faq":523,"howto":6,"isBlog":541,"isChangelog":541,"meta":542,"navigation":544,"path":545,"pillar":541,"products":6,"rawbody":546,"role":6,"seo":547,"seoTitle":548,"stem":549,"thumbnail":6,"updated":520,"__hash__":550},"content\u002Fresources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link.md","Virtual account vs wallet address vs payment link: how to collect in stablecoins",null,{"type":8,"value":9,"toc":505},"minimark",[10,14,17,23,42,51,56,59,75,87,91,94,97,118,125,129,132,152,155,159,162,323,326,330,333,377,381,384,387,394,398,401,421,424,428,431,455,463,467,470,481,487,493,497],[11,12,13],"p",{},"There are three common ways to collect money that ends up as stablecoins. A virtual account gives the payer bank details and converts their transfer. A wallet address takes stablecoins directly from a payer who already holds them. A payment link prefills a stablecoin transfer for a wallet. The right one depends on what your payer already has.",[11,15,16],{},"Teams usually pick one and force every payer through it. That works until the first customer who only has a bank account meets a checkout that only takes USDC. The three methods solve different problems, and plenty of products need two of them.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"Start from the payer. Bank account only: virtual account. Already holds stablecoins: wallet address or payment link.",[27,31,32],{},"Virtual accounts are the only one of the three where the payer never touches crypto.",[27,34,35],{},"Reconciliation gets harder as accounts get more shared. One virtual account per payer is the cleanest.",[27,37,38],{},"Onchain transfers can't be reversed. Plan refunds as new outbound payments.",[27,40,41],{},"Payment links are a wallet UX layer on top of an address, not a separate rail.",[11,43,44,45,50],{},"All three sit in the collection layer of ",[46,47,49],"a",{"href":48},"\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure","stablecoin infrastructure",". Below is how they differ and how to pick.",[52,53,55],"h2",{"id":54},"what-is-a-virtual-account-in-stablecoin-collection","What is a virtual account in stablecoin collection?",[11,57,58],{},"A stablecoin virtual account is a set of bank details issued for one customer that receives fiat transfers and automatically converts each deposit into USDC or USDT, sent to a linked wallet. The payer sees a normal bank account. The business ends up with stablecoins.",[11,60,61,62,68,69,74],{},"In the US, the payer uses the routing and account number to send ACH or a wire. ACH is the batch network the US uses for payroll and bill pay (",[46,63,67],{"href":64,"rel":65},"https:\u002F\u002Fwww.nacha.org\u002Fcontent\u002Fwhat-is-ach",[66],"nofollow","Nacha","). Wires usually run over Fedwire, where payments credited to Federal Reserve master accounts are final (",[46,70,73],{"href":71,"rel":72},"https:\u002F\u002Fwww.frbservices.org\u002Ffinancial-services\u002Fwires",[66],"Federal Reserve Financial Services","). Some accounts also accept SWIFT from foreign banks.",[11,76,77,81,82,86],{},[46,78,80],{"href":79},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","Stablecoin virtual accounts explained"," covers the mechanics in depth. If you're choosing between a reusable account and per-payment instructions, see ",[46,83,85],{"href":84},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","virtual account vs one-time deposit instructions",".",[52,88,90],{"id":89},"what-is-a-deposit-wallet-address","What is a deposit wallet address?",[11,92,93],{},"A deposit wallet address is a blockchain address where a payer sends stablecoins directly. No conversion happens on the way in, because the payer already holds USDC or USDT.",[11,95,96],{},"Three details trip people up:",[98,99,100,106,112],"ol",{},[27,101,102,105],{},[20,103,104],{},"The network has to match."," USDC on Solana sent to an Ethereum address doesn't arrive. Tell payers the token and network, not just the address.",[27,107,108,111],{},[20,109,110],{},"The address can be shared or unique."," A shared address is simple to publish and hard to reconcile. A unique address per payer or per invoice fixes that, at the cost of managing more addresses.",[27,113,114,117],{},[20,115,116],{},"Someone controls the keys."," If the address belongs to a custodial provider, it holds the funds. If it's your own wallet, you do.",[11,119,120,124],{},[46,121,123],{"href":122},"\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments","How merchants accept stablecoin payments"," walks through the merchant side of address-based collection.",[52,126,128],{"id":127},"what-is-a-stablecoin-payment-link","What is a stablecoin payment link?",[11,130,131],{},"A stablecoin payment link is a URL or QR code that encodes a payment request: recipient, token, amount, and often a reference ID. A wallet opens it and prefills the transfer, so the payer only confirms.",[11,133,134,135,140,141,146,147,151],{},"Two open standards define the format on major chains. Ethereum's ",[46,136,139],{"href":137,"rel":138},"https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-681",[66],"EIP-681"," specifies a URL format for payment requests that opens the user's wallet with the transaction parameters filled in. The ",[46,142,145],{"href":143,"rel":144},"https:\u002F\u002Fdocs.solanapay.com\u002Fspec",[66],"Solana Pay specification"," does the same for Solana and adds optional ",[148,149,150],"code",{},"reference"," fields that can serve as IDs before the transaction exists, which helps match a payment to an order.",[11,153,154],{},"Hosted checkout pages build on the same idea: a web page shows the amount, a QR code, a countdown, and a status that flips to paid when the transfer confirms. Underneath, it's still a transfer to an address.",[52,156,158],{"id":157},"how-do-the-three-methods-compare","How do the three methods compare?",[11,160,161],{},"The table compares the three on what matters after launch: who can pay, how you match the money, and what happens when something goes wrong.",[163,164,165,184],"table",{},[166,167,168],"thead",{},[169,170,171,175,178,181],"tr",{},[172,173,174],"th",{},"Question",[172,176,177],{},"Virtual account",[172,179,180],{},"Deposit wallet address",[172,182,183],{},"Payment link or hosted checkout",[185,186,187,201,215,228,242,256,269,282,296,309],"tbody",{},[169,188,189,193,196,199],{},[190,191,192],"td",{},"Payer needs crypto?",[190,194,195],{},"No",[190,197,198],{},"Yes",[190,200,198],{},[169,202,203,206,209,212],{},[190,204,205],{},"What the payer uses",[190,207,208],{},"Bank transfer (ACH, wire, SWIFT)",[190,210,211],{},"Any wallet on the right network",[190,213,214],{},"A wallet that reads the link or QR code",[169,216,217,220,223,226],{},[190,218,219],{},"Speed to funds",[190,221,222],{},"Rail-dependent: minutes to days",[190,224,225],{},"Seconds to minutes after confirmation",[190,227,225],{},[169,229,230,233,236,239],{},[190,231,232],{},"Reconciliation",[190,234,235],{},"Strong if one account per payer",[190,237,238],{},"Weak if shared, strong if unique per payer",[190,240,241],{},"Strong with a unique reference per request",[169,243,244,247,250,253],{},[190,245,246],{},"Wrong-network risk",[190,248,249],{},"None for the payer",[190,251,252],{},"Real",[190,254,255],{},"Lower, since the link sets the network",[169,257,258,261,264,267],{},[190,259,260],{},"Refunds",[190,262,263],{},"Return rules of the bank rail",[190,265,266],{},"New outbound transfer",[190,268,266],{},[169,270,271,274,277,280],{},[190,272,273],{},"KYC on the account holder",[190,275,276],{},"Yes, before issuance",[190,278,279],{},"Depends on provider",[190,281,279],{},[169,283,284,287,290,293],{},[190,285,286],{},"Setup per payer",[190,288,289],{},"Account issuance and review",[190,291,292],{},"Address generation",[190,294,295],{},"One link per payment",[169,297,298,301,304,306],{},[190,299,300],{},"Recurring payments",[190,302,303],{},"Yes, same details every time",[190,305,198],{},[190,307,308],{},"Usually one link per payment",[169,310,311,314,317,320],{},[190,312,313],{},"Best for",[190,315,316],{},"B2B invoices, payroll funding, payers with bank accounts",[190,318,319],{},"Partners and treasuries that hold stablecoins",[190,321,322],{},"Checkout for buyers who hold stablecoins",[11,324,325],{},"Look at the \"payer needs crypto?\" row first. It removes one or two options for most products before anything else matters.",[52,327,329],{"id":328},"which-method-should-you-choose-in-order","Which method should you choose, in order?",[11,331,332],{},"Answer these questions in order and stop at the first clear answer.",[98,334,335,341,347,353,359,365,371],{},[27,336,337,340],{},[20,338,339],{},"Do your payers hold stablecoins?"," If most don't, you need a virtual account. Nothing else works for them.",[27,342,343,346],{},[20,344,345],{},"Do payers pay you more than once?"," Recurring payers suit a virtual account or a dedicated address: the same details every time.",[27,348,349,352],{},[20,350,351],{},"Does each payment need to match an order?"," Use a payment link with a unique reference, or one account or address per payer.",[27,354,355,358],{},[20,356,357],{},"Who is paying, a person at checkout or a finance team?"," People at checkout want a QR code and a timer. Finance teams want bank details or an address they can save.",[27,360,361,364],{},[20,362,363],{},"What happens when someone sends the wrong amount or network?"," Write the refund rule before launch, not after the first mistake.",[27,366,367,370],{},[20,368,369],{},"Who must pass KYC?"," Virtual accounts verify the holder before issuance. Check what your address or link provider requires.",[27,372,373,376],{},[20,374,375],{},"Can your ledger handle more than one?"," If yes, offer two methods and route payers by type.",[52,378,380],{"id":379},"how-does-reconciliation-differ-between-the-three","How does reconciliation differ between the three?",[11,382,383],{},"Reconciliation is easiest when the destination identifies the payer, and hardest when many payers share one destination.",[11,385,386],{},"A virtual account per customer is the cleanest case: every deposit belongs to its owner, and the provider's deposit event carries the account ID. A shared address forces matching by amount, timestamp, or sender address, and sender addresses change when payers use exchanges. Payment links sit in between, as long as each request carries a unique reference you store before the payer pays.",[11,388,389,390,86],{},"For the virtual account case in detail, see ",[46,391,393],{"href":392},"\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation","virtual account reconciliation",[52,395,397],{"id":396},"where-do-costs-show-up-in-each-method","Where do costs show up in each method?",[11,399,400],{},"Costs land in different places, so compare them per method rather than per provider headline.",[24,402,403,409,415],{},[27,404,405,408],{},[20,406,407],{},"Virtual accounts"," often carry a monthly fee per account plus a conversion fee on each deposit. The payer may also pay their own bank's wire fee, which can shrink the amount that arrives.",[27,410,411,414],{},[20,412,413],{},"Wallet addresses"," cost the payer a network fee to send. You pay nothing on the way in unless the address belongs to a provider that charges per deposit.",[27,416,417,420],{},[20,418,419],{},"Payment links and hosted checkout"," usually charge a percentage per payment, like a card processor, plus the payer's network fee.",[11,422,423],{},"Run the numbers at your real payment size. A flat monthly fee is noise on large B2B deposits and a real cost on hundreds of small ones.",[52,425,427],{"id":426},"what-are-the-limits-of-each-method","What are the limits of each method?",[11,429,430],{},"Each method has a failure mode worth knowing before launch.",[24,432,433,438,443,449],{},[27,434,435,437],{},[20,436,407],{}," need KYC or KYB and a review before the account exists, so they aren't instant. Coverage is limited to the countries and rails the provider supports, and bank rails have cut-off times.",[27,439,440,442],{},[20,441,413],{}," put network choice on the payer. A wrong-network transfer may be recoverable or lost, depending on who controls the receiving keys.",[27,444,445,448],{},[20,446,447],{},"Payment links"," depend on the payer's wallet supporting the standard. A link that opens nothing on a payer's phone is a dead end.",[27,450,451,454],{},[20,452,453],{},"All three"," end in stablecoins. If you need local currency in a bank account, you still need an off-ramp after collection.",[11,456,457,458,462],{},"Onchain transfers are final, so none of the crypto-in methods has a chargeback. That protects the merchant and removes a buyer protection, which matters for consumer checkout. ",[46,459,461],{"href":460},"\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible","Are stablecoin payments reversible?"," explains what that means in practice.",[52,464,466],{"id":465},"how-does-blindpay-handle-collection","How does BlindPay handle collection?",[11,468,469],{},"BlindPay covers the first two methods through its API. It doesn't offer payment links or a hosted checkout.",[11,471,472,475,476,480],{},[20,473,474],{},"Virtual accounts."," BlindPay issues ",[46,477,479],{"href":478},"\u002Fdocs\u002Fvirtual-accounts","US virtual accounts"," in the customer's name with their own routing and account number. They accept ACH, wire, and SWIFT, depending on the account type, and each deposit creates a payin that settles USDC or USDT to the linked wallet. USDT settlement needs the linked wallet on Polygon, Ethereum, or Solana. The customer must have approved KYC first, then each account goes through compliance and bank review. Accounts cost $1.50 per month each. RTP deposits don't land in a virtual account; an RTP payin uses shared bank details with a memo code instead.",[11,482,483,486],{},[20,484,485],{},"Wallet addresses."," For customers who already hold stablecoins, there are two options. An external blockchain wallet is an address your customer controls, which keeps that flow non-custodial. A managed wallet (beta) is an address BlindPay creates and holds the keys for, so it's custodial.",[11,488,489,492],{},[20,490,491],{},"The other direction."," An offramp wallet is the mirror of a virtual account: a deposit address where every USDC or USDT that lands pays out automatically to a linked bank account. Payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO).",[52,494,496],{"id":495},"what-to-do-next","What to do next",[11,498,499,500,504],{},"List your payers by type: bank account only, or already holding stablecoins. If the first group is bigger, create a customer and a test virtual account on a free development instance with the ",[46,501,503],{"href":502},"\u002Fdocs\u002Fvirtual-accounts-create","create a virtual account"," guide, and send your first test deposit today.",{"title":506,"searchDepth":507,"depth":507,"links":508},"",2,[509,510,511,512,513,514,515,516,517,518],{"id":54,"depth":507,"text":55},{"id":89,"depth":507,"text":90},{"id":127,"depth":507,"text":128},{"id":157,"depth":507,"text":158},{"id":328,"depth":507,"text":329},{"id":379,"depth":507,"text":380},{"id":396,"depth":507,"text":397},{"id":426,"depth":507,"text":427},{"id":465,"depth":507,"text":466},{"id":495,"depth":507,"text":496},"payments","2026-10-06","Three ways to collect money that ends in stablecoins: a virtual account, a deposit wallet address, or a payment link. Compare rails, refunds, KYC, and fit.","md",[524,527,529,532,535,538],{"q":525,"a":526},"What is the difference between a virtual account and a wallet address?","A virtual account is a set of bank details, such as a routing and account number, that receives fiat transfers like ACH or wire and converts them to stablecoins. A wallet address receives stablecoins directly on a blockchain, so the payer must already hold USDC or USDT on the right network. One is for payers with bank accounts. The other is for payers with crypto.",{"q":128,"a":528},"A stablecoin payment link is a URL or QR code that encodes a payment request: the recipient address, the token, the amount, and often a reference. Standards like Ethereum's EIP-681 and the Solana Pay specification define the format, so a wallet can open it and prefill the transfer. Hosted checkout pages wrap the same idea in a web page with a timer and status.",{"q":530,"a":531},"Does the payer need crypto to pay into a virtual account?","No. The payer sends a normal bank transfer from any bank account, using the routing and account number the virtual account provides. The provider converts the deposit into USDC or USDT and sends it to the wallet linked to the account. The payer may not know stablecoins are involved at all, which is the main reason businesses use virtual accounts.",{"q":533,"a":534},"Which collection method is easiest to reconcile?","A virtual account per customer is usually easiest, because every deposit into that account belongs to one payer, with no memo to match. Payment links with a unique reference come next. A shared wallet address is the hardest: many payers send to one address, and you have to match transfers by amount, time, or sender address, which breaks when two payers send the same amount.",{"q":536,"a":537},"Can a stablecoin payment to a wallet address be refunded?","Not by reversing it. Onchain transfers are final once confirmed, so a refund is a new transfer from the recipient back to the payer, and the recipient has to know a safe address to send it to. Bank transfers into a virtual account follow the rules of the rail, and providers may return a deposit they can't accept to the sender.",{"q":539,"a":540},"When should a business use more than one collection method?","When its payers differ. A marketplace may give each seller a virtual account for bank payers, show a payment link at checkout for buyers who hold USDC, and keep a deposit address for partners who settle in stablecoins. Each method ends in the same place, a stablecoin balance, so the ledger can treat them as three inputs to one account.",false,{"author":543},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link","---\ntitle: \"Virtual account vs wallet address vs payment link: how to collect in stablecoins\"\nseoTitle: \"Virtual account vs wallet address vs payment link\"\ndescription: \"Three ways to collect money that ends in stablecoins: a virtual account, a deposit wallet address, or a payment link. Compare rails, refunds, KYC, and fit.\"\ndate: \"2026-10-06\"\nupdated: \"2026-10-06\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nfaq:\n  - q: \"What is the difference between a virtual account and a wallet address?\"\n    a: \"A virtual account is a set of bank details, such as a routing and account number, that receives fiat transfers like ACH or wire and converts them to stablecoins. A wallet address receives stablecoins directly on a blockchain, so the payer must already hold USDC or USDT on the right network. One is for payers with bank accounts. The other is for payers with crypto.\"\n  - q: \"What is a stablecoin payment link?\"\n    a: \"A stablecoin payment link is a URL or QR code that encodes a payment request: the recipient address, the token, the amount, and often a reference. Standards like Ethereum's EIP-681 and the Solana Pay specification define the format, so a wallet can open it and prefill the transfer. Hosted checkout pages wrap the same idea in a web page with a timer and status.\"\n  - q: \"Does the payer need crypto to pay into a virtual account?\"\n    a: \"No. The payer sends a normal bank transfer from any bank account, using the routing and account number the virtual account provides. The provider converts the deposit into USDC or USDT and sends it to the wallet linked to the account. The payer may not know stablecoins are involved at all, which is the main reason businesses use virtual accounts.\"\n  - q: \"Which collection method is easiest to reconcile?\"\n    a: \"A virtual account per customer is usually easiest, because every deposit into that account belongs to one payer, with no memo to match. Payment links with a unique reference come next. A shared wallet address is the hardest: many payers send to one address, and you have to match transfers by amount, time, or sender address, which breaks when two payers send the same amount.\"\n  - q: \"Can a stablecoin payment to a wallet address be refunded?\"\n    a: \"Not by reversing it. Onchain transfers are final once confirmed, so a refund is a new transfer from the recipient back to the payer, and the recipient has to know a safe address to send it to. Bank transfers into a virtual account follow the rules of the rail, and providers may return a deposit they can't accept to the sender.\"\n  - q: \"When should a business use more than one collection method?\"\n    a: \"When its payers differ. A marketplace may give each seller a virtual account for bank payers, show a payment link at checkout for buyers who hold USDC, and keep a deposit address for partners who settle in stablecoins. Each method ends in the same place, a stablecoin balance, so the ledger can treat them as three inputs to one account.\"\n---\n\nThere are three common ways to collect money that ends up as stablecoins. A virtual account gives the payer bank details and converts their transfer. A wallet address takes stablecoins directly from a payer who already holds them. A payment link prefills a stablecoin transfer for a wallet. The right one depends on what your payer already has.\n\nTeams usually pick one and force every payer through it. That works until the first customer who only has a bank account meets a checkout that only takes USDC. The three methods solve different problems, and plenty of products need two of them.\n\n**Key takeaways**\n\n- Start from the payer. Bank account only: virtual account. Already holds stablecoins: wallet address or payment link.\n- Virtual accounts are the only one of the three where the payer never touches crypto.\n- Reconciliation gets harder as accounts get more shared. One virtual account per payer is the cleanest.\n- Onchain transfers can't be reversed. Plan refunds as new outbound payments.\n- Payment links are a wallet UX layer on top of an address, not a separate rail.\n\nAll three sit in the collection layer of [stablecoin infrastructure](\u002Fresources\u002Fmore\u002Fwhat-is-stablecoin-infrastructure). Below is how they differ and how to pick.\n\n## What is a virtual account in stablecoin collection?\n\nA stablecoin virtual account is a set of bank details issued for one customer that receives fiat transfers and automatically converts each deposit into USDC or USDT, sent to a linked wallet. The payer sees a normal bank account. The business ends up with stablecoins.\n\nIn the US, the payer uses the routing and account number to send ACH or a wire. ACH is the batch network the US uses for payroll and bill pay ([Nacha](https:\u002F\u002Fwww.nacha.org\u002Fcontent\u002Fwhat-is-ach)). Wires usually run over Fedwire, where payments credited to Federal Reserve master accounts are final ([Federal Reserve Financial Services](https:\u002F\u002Fwww.frbservices.org\u002Ffinancial-services\u002Fwires)). Some accounts also accept SWIFT from foreign banks.\n\n[Stablecoin virtual accounts explained](\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained) covers the mechanics in depth. If you're choosing between a reusable account and per-payment instructions, see [virtual account vs one-time deposit instructions](\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions).\n\n## What is a deposit wallet address?\n\nA deposit wallet address is a blockchain address where a payer sends stablecoins directly. No conversion happens on the way in, because the payer already holds USDC or USDT.\n\nThree details trip people up:\n\n1. **The network has to match.** USDC on Solana sent to an Ethereum address doesn't arrive. Tell payers the token and network, not just the address.\n2. **The address can be shared or unique.** A shared address is simple to publish and hard to reconcile. A unique address per payer or per invoice fixes that, at the cost of managing more addresses.\n3. **Someone controls the keys.** If the address belongs to a custodial provider, it holds the funds. If it's your own wallet, you do.\n\n[How merchants accept stablecoin payments](\u002Fresources\u002Fmore\u002Fhow-merchants-accept-stablecoin-payments) walks through the merchant side of address-based collection.\n\n## What is a stablecoin payment link?\n\nA stablecoin payment link is a URL or QR code that encodes a payment request: recipient, token, amount, and often a reference ID. A wallet opens it and prefills the transfer, so the payer only confirms.\n\nTwo open standards define the format on major chains. Ethereum's [EIP-681](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-681) specifies a URL format for payment requests that opens the user's wallet with the transaction parameters filled in. The [Solana Pay specification](https:\u002F\u002Fdocs.solanapay.com\u002Fspec) does the same for Solana and adds optional `reference` fields that can serve as IDs before the transaction exists, which helps match a payment to an order.\n\nHosted checkout pages build on the same idea: a web page shows the amount, a QR code, a countdown, and a status that flips to paid when the transfer confirms. Underneath, it's still a transfer to an address.\n\n## How do the three methods compare?\n\nThe table compares the three on what matters after launch: who can pay, how you match the money, and what happens when something goes wrong.\n\n| Question | Virtual account | Deposit wallet address | Payment link or hosted checkout |\n| --- | --- | --- | --- |\n| Payer needs crypto? | No | Yes | Yes |\n| What the payer uses | Bank transfer (ACH, wire, SWIFT) | Any wallet on the right network | A wallet that reads the link or QR code |\n| Speed to funds | Rail-dependent: minutes to days | Seconds to minutes after confirmation | Seconds to minutes after confirmation |\n| Reconciliation | Strong if one account per payer | Weak if shared, strong if unique per payer | Strong with a unique reference per request |\n| Wrong-network risk | None for the payer | Real | Lower, since the link sets the network |\n| Refunds | Return rules of the bank rail | New outbound transfer | New outbound transfer |\n| KYC on the account holder | Yes, before issuance | Depends on provider | Depends on provider |\n| Setup per payer | Account issuance and review | Address generation | One link per payment |\n| Recurring payments | Yes, same details every time | Yes | Usually one link per payment |\n| Best for | B2B invoices, payroll funding, payers with bank accounts | Partners and treasuries that hold stablecoins | Checkout for buyers who hold stablecoins |\n\nLook at the \"payer needs crypto?\" row first. It removes one or two options for most products before anything else matters.\n\n## Which method should you choose, in order?\n\nAnswer these questions in order and stop at the first clear answer.\n\n1. **Do your payers hold stablecoins?** If most don't, you need a virtual account. Nothing else works for them.\n2. **Do payers pay you more than once?** Recurring payers suit a virtual account or a dedicated address: the same details every time.\n3. **Does each payment need to match an order?** Use a payment link with a unique reference, or one account or address per payer.\n4. **Who is paying, a person at checkout or a finance team?** People at checkout want a QR code and a timer. Finance teams want bank details or an address they can save.\n5. **What happens when someone sends the wrong amount or network?** Write the refund rule before launch, not after the first mistake.\n6. **Who must pass KYC?** Virtual accounts verify the holder before issuance. Check what your address or link provider requires.\n7. **Can your ledger handle more than one?** If yes, offer two methods and route payers by type.\n\n## How does reconciliation differ between the three?\n\nReconciliation is easiest when the destination identifies the payer, and hardest when many payers share one destination.\n\nA virtual account per customer is the cleanest case: every deposit belongs to its owner, and the provider's deposit event carries the account ID. A shared address forces matching by amount, timestamp, or sender address, and sender addresses change when payers use exchanges. Payment links sit in between, as long as each request carries a unique reference you store before the payer pays.\n\nFor the virtual account case in detail, see [virtual account reconciliation](\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation).\n\n## Where do costs show up in each method?\n\nCosts land in different places, so compare them per method rather than per provider headline.\n\n- **Virtual accounts** often carry a monthly fee per account plus a conversion fee on each deposit. The payer may also pay their own bank's wire fee, which can shrink the amount that arrives.\n- **Wallet addresses** cost the payer a network fee to send. You pay nothing on the way in unless the address belongs to a provider that charges per deposit.\n- **Payment links and hosted checkout** usually charge a percentage per payment, like a card processor, plus the payer's network fee.\n\nRun the numbers at your real payment size. A flat monthly fee is noise on large B2B deposits and a real cost on hundreds of small ones.\n\n## What are the limits of each method?\n\nEach method has a failure mode worth knowing before launch.\n\n- **Virtual accounts** need KYC or KYB and a review before the account exists, so they aren't instant. Coverage is limited to the countries and rails the provider supports, and bank rails have cut-off times.\n- **Wallet addresses** put network choice on the payer. A wrong-network transfer may be recoverable or lost, depending on who controls the receiving keys.\n- **Payment links** depend on the payer's wallet supporting the standard. A link that opens nothing on a payer's phone is a dead end.\n- **All three** end in stablecoins. If you need local currency in a bank account, you still need an off-ramp after collection.\n\nOnchain transfers are final, so none of the crypto-in methods has a chargeback. That protects the merchant and removes a buyer protection, which matters for consumer checkout. [Are stablecoin payments reversible?](\u002Fresources\u002Fmore\u002Fare-stablecoin-payments-reversible) explains what that means in practice.\n\n## How does BlindPay handle collection?\n\nBlindPay covers the first two methods through its API. It doesn't offer payment links or a hosted checkout.\n\n**Virtual accounts.** BlindPay issues [US virtual accounts](\u002Fdocs\u002Fvirtual-accounts) in the customer's name with their own routing and account number. They accept ACH, wire, and SWIFT, depending on the account type, and each deposit creates a payin that settles USDC or USDT to the linked wallet. USDT settlement needs the linked wallet on Polygon, Ethereum, or Solana. The customer must have approved KYC first, then each account goes through compliance and bank review. Accounts cost $1.50 per month each. RTP deposits don't land in a virtual account; an RTP payin uses shared bank details with a memo code instead.\n\n**Wallet addresses.** For customers who already hold stablecoins, there are two options. An external blockchain wallet is an address your customer controls, which keeps that flow non-custodial. A managed wallet (beta) is an address BlindPay creates and holds the keys for, so it's custodial.\n\n**The other direction.** An offramp wallet is the mirror of a virtual account: a deposit address where every USDC or USDT that lands pays out automatically to a linked bank account. Payouts run over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO\u002FCOBO).\n\n## What to do next\n\nList your payers by type: bank account only, or already holding stablecoins. If the first group is bigger, create a customer and a test virtual account on a free development instance with the [create a virtual account](\u002Fdocs\u002Fvirtual-accounts-create) guide, and send your first test deposit today.\n",{"title":5,"description":521},"Virtual account vs wallet address vs payment link","resources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link","d1IMJlNiQi8l0Bw6shJIwSYPusPc-8i0fhffi74pOjk",[552,556,560,564,568,572,576,580,584,588,592,596,600,604,608,612,616,620,624,628,632,636,640,644,648,652,656,660,664,668,672,676,680,684,688,692,696,699,703,707,711,715,719,723,727,731,735,739,743,747,751,755,759,763,767,771,775,779,783,787,791,795,799,803,807,810,814,818,822,826,830,834,838,842,846,847,851,854,858,862,866,870,874,878,882,886,890,894,898,902],{"path":553,"title":554,"description":555},"\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":557,"title":558,"description":559},"\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":561,"title":562,"description":563},"\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":565,"title":566,"description":567},"\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":569,"title":570,"description":571},"\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":573,"title":574,"description":575},"\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":577,"title":578,"description":579},"\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":581,"title":582,"description":583},"\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":585,"title":586,"description":587},"\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":589,"title":590,"description":591},"\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":593,"title":594,"description":595},"\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":597,"title":598,"description":599},"\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":601,"title":602,"description":603},"\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":605,"title":606,"description":607},"\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":609,"title":610,"description":611},"\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":613,"title":614,"description":615},"\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":617,"title":618,"description":619},"\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":621,"title":622,"description":623},"\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":625,"title":626,"description":627},"\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":629,"title":630,"description":631},"\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":633,"title":634,"description":635},"\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":637,"title":638,"description":639},"\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":641,"title":642,"description":643},"\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":645,"title":646,"description":647},"\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":649,"title":650,"description":651},"\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":653,"title":654,"description":655},"\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":657,"title":658,"description":659},"\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":661,"title":662,"description":663},"\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":665,"title":666,"description":667},"\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":669,"title":670,"description":671},"\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":673,"title":674,"description":675},"\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":677,"title":678,"description":679},"\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":681,"title":682,"description":683},"\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":685,"title":686,"description":687},"\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":689,"title":690,"description":691},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI","Send USDC to a Mexican bank account: verify the recipient, quote in pesos, fund from a wallet, and confirm on SPEI. Recipient data, statuses, and failures.",{"path":693,"title":694,"description":695},"\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":392,"title":697,"description":698},"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":700,"title":701,"description":702},"\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":704,"title":705,"description":706},"\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":708,"title":709,"description":710},"\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":712,"title":713,"description":714},"\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":716,"title":717,"description":718},"\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":720,"title":721,"description":722},"\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api","On-ramp widget vs API: which integration fits your product?","Hosted on-ramp widget or API-first ramp? Compare who owns the UX, KYC, quotes, webhooks, branding, and compliance, plus a decision table and checklist.",{"path":724,"title":725,"description":726},"\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":728,"title":729,"description":730},"\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":732,"title":733,"description":734},"\u002Fresources\u002Fmore\u002Fonchain-settlement-vs-bank-settlement","Onchain settlement vs bank settlement: RTGS, ACH, cards, and blockchain finality compared","How onchain settlement compares with Fedwire, Pix, ACH, and card settlement: settlement asset, hours, finality, reversibility, and where payout risk sits.",{"path":736,"title":737,"description":738},"\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":740,"title":741,"description":742},"\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":744,"title":745,"description":746},"\u002Fresources\u002Fmore\u002Fpix-vs-spei","Pix vs SPEI: how Brazil's and Mexico's instant payment rails compare","Pix vs SPEI side by side: who runs each rail, how recipients are identified, hours, settlement, returns, and proof of payment for stablecoin payouts.",{"path":748,"title":749,"description":750},"\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template","Stablecoin API RFP template: sections, scoring, and a vendor scorecard","How to write an RFP for a stablecoin API: the eight sections to include, pass or fail gates, 1 to 3 weighted scoring, a copyable scorecard, and a timeline.",{"path":752,"title":753,"description":754},"\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":756,"title":757,"description":758},"\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":760,"title":761,"description":762},"\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":764,"title":765,"description":766},"\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":768,"title":769,"description":770},"\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":772,"title":773,"description":774},"\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":776,"title":777,"description":778},"\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":780,"title":781,"description":782},"\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":784,"title":785,"description":786},"\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":788,"title":789,"description":790},"\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":792,"title":793,"description":794},"\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":796,"title":797,"description":798},"\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":800,"title":801,"description":802},"\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":804,"title":805,"description":806},"\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":79,"title":808,"description":809},"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":811,"title":812,"description":813},"\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":815,"title":816,"description":817},"\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":819,"title":820,"description":821},"\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":823,"title":824,"description":825},"\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":827,"title":828,"description":829},"\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":831,"title":832,"description":833},"\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":835,"title":836,"description":837},"\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":839,"title":840,"description":841},"\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":843,"title":844,"description":845},"\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":545,"title":5,"description":521},{"path":848,"title":849,"description":850},"\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":84,"title":852,"description":853},"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":855,"title":856,"description":857},"\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":859,"title":860,"description":861},"\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":863,"title":864,"description":865},"\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":867,"title":868,"description":869},"\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":871,"title":872,"description":873},"\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":875,"title":876,"description":877},"\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":879,"title":880,"description":881},"\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":883,"title":884,"description":885},"\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":887,"title":888,"description":889},"\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":891,"title":892,"description":893},"\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":895,"title":896,"description":897},"\u002Fresources\u002Fmore\u002Fwho-pays-gas-fees-stablecoin-payments","Who pays gas fees in stablecoin payments?","Who pays network fees in each stablecoin payment flow, how gas works on Ethereum, Solana, Tron, Stellar, and Arc, and how to compare it across providers.",{"path":899,"title":900,"description":901},"\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":903,"title":904,"description":905},"\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.",1791469672737]