[{"data":1,"prerenderedAt":165},["ShallowReactive",2],{"content-\u002Fprompts\u002Fintegrate-virtual-accounts":3,"prompts-category-integrations":99},{"id":4,"title":5,"author":6,"body":7,"categories":6,"category":83,"categoryType":6,"date":84,"description":85,"extension":86,"faq":6,"howto":6,"isBlog":87,"isChangelog":87,"meta":88,"navigation":89,"path":90,"pillar":87,"products":91,"rawbody":95,"seo":96,"stem":97,"thumbnail":6,"updated":6,"__hash__":98},"content\u002Fprompts\u002Fintegrate-virtual-accounts.md","Integrate US virtual accounts",null,{"type":8,"value":9,"toc":77},"minimark",[10,14,19,30,34,47,51],[11,12,13],"p",{},"Paste this prompt into your coding agent to issue dedicated US account numbers for your customers and settle incoming transfers to stablecoins.",[15,16,18],"h2",{"id":17},"prompt","Prompt",[20,21,27],"pre",{"className":22,"code":24,"language":25,"meta":26},[23],"language-text","You are integrating BlindPay virtual accounts into my application: each customer gets a dedicated US bank account (routing and account number) whose deposits settle automatically as USDC\u002FUSDT to a linked blockchain wallet.\n\nBefore writing code, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the virtual accounts pages, customers, blockchain wallets, and webhooks)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nBuild the flow:\n1. Create the customer and wait for KYC\u002FKYB approval (customer.update webhook). Business customers need owners and the KYB document set.\n2. Register the settlement blockchain wallet for the customer.\n3. Make sure the compliance fields virtual accounts require are set on the customer (account_purpose, source_of_wealth, and the business fields for KYB), updating via PUT \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id} if needed.\n4. Create the virtual account: POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fvirtual-accounts with banking_partner, token, and blockchain_wallet_id.\n5. Handle the two-stage review lifecycle (pending_review, verifying, approved or rejected) through virtualAccount.new and virtualAccount.complete webhooks; only show account details to the customer once approved.\n6. Record deposit settlements via wallet.inbound webhooks and reconcile fees: deposits under $100 accrue to the monthly invoice (billing_fee_amount), larger ones are charged at transaction time (transaction_fee_amount).\n\nConstraints:\n- API keys stay server-side; verify Svix webhook signatures on every event.\n- On a development instance virtual accounts skip review and go straight to approved, so also code the rejected path deliberately.\n- Persist va_, re_, and bw_ IDs on my own records.\n\nDeliverables: virtual account service, webhook handlers for the account lifecycle and inbound deposits, and a summary of which compliance fields my onboarding form must collect for individuals versus businesses.\n","text","",[28,29,24],"code",{"__ignoreMap":26},[15,31,33],{"id":32},"how-to-use","How to use",[35,36,37,41,44],"ol",{},[38,39,40],"li",{},"Ensure your onboarding collects the compliance fields (account purpose, source of wealth, business documentation for KYB) before creating accounts.",[38,42,43],{},"Paste the prompt with your stack details and instance ID.",[38,45,46],{},"Test on a development instance first; review auto-approves there.",[15,48,50],{"id":49},"related-docs","Related docs",[52,53,54,63,70],"ul",{},[38,55,56],{},[57,58,62],"a",{"href":59,"rel":60},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fvirtual-accounts",[61],"nofollow","Virtual accounts overview",[38,64,65],{},[57,66,69],{"href":67,"rel":68},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fvirtual-accounts-create",[61],"Creating virtual accounts",[38,71,72],{},[57,73,76],{"href":74,"rel":75},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fblockchain-wallets",[61],"Blockchain wallets",{"title":26,"searchDepth":78,"depth":78,"links":79},2,[80,81,82],{"id":17,"depth":78,"text":18},{"id":32,"depth":78,"text":33},{"id":49,"depth":78,"text":50},"integrations","2026-08-26","Give each customer a named US bank account with ACH, RTP, wire, and SWIFT details that settles automatically to USDC or USDT in their wallet.","md",false,{},true,"\u002Fprompts\u002Fintegrate-virtual-accounts",[92,93,94],"virtual-accounts","compliance","webhooks","---\ntitle: \"Integrate US virtual accounts\"\ndescription: \"Give each customer a named US bank account with ACH, RTP, wire, and SWIFT details that settles automatically to USDC or USDT in their wallet.\"\ndate: \"2026-08-26\"\ncategory: \"integrations\"\nproducts: [\"virtual-accounts\", \"compliance\", \"webhooks\"]\n---\n\nPaste this prompt into your coding agent to issue dedicated US account numbers for your customers and settle incoming transfers to stablecoins.\n\n## Prompt\n\n```text\nYou are integrating BlindPay virtual accounts into my application: each customer gets a dedicated US bank account (routing and account number) whose deposits settle automatically as USDC\u002FUSDT to a linked blockchain wallet.\n\nBefore writing code, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the virtual accounts pages, customers, blockchain wallets, and webhooks)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nBuild the flow:\n1. Create the customer and wait for KYC\u002FKYB approval (customer.update webhook). Business customers need owners and the KYB document set.\n2. Register the settlement blockchain wallet for the customer.\n3. Make sure the compliance fields virtual accounts require are set on the customer (account_purpose, source_of_wealth, and the business fields for KYB), updating via PUT \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id} if needed.\n4. Create the virtual account: POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fcustomers\u002F{customer_id}\u002Fvirtual-accounts with banking_partner, token, and blockchain_wallet_id.\n5. Handle the two-stage review lifecycle (pending_review, verifying, approved or rejected) through virtualAccount.new and virtualAccount.complete webhooks; only show account details to the customer once approved.\n6. Record deposit settlements via wallet.inbound webhooks and reconcile fees: deposits under $100 accrue to the monthly invoice (billing_fee_amount), larger ones are charged at transaction time (transaction_fee_amount).\n\nConstraints:\n- API keys stay server-side; verify Svix webhook signatures on every event.\n- On a development instance virtual accounts skip review and go straight to approved, so also code the rejected path deliberately.\n- Persist va_, re_, and bw_ IDs on my own records.\n\nDeliverables: virtual account service, webhook handlers for the account lifecycle and inbound deposits, and a summary of which compliance fields my onboarding form must collect for individuals versus businesses.\n```\n\n## How to use\n\n1. Ensure your onboarding collects the compliance fields (account purpose, source of wealth, business documentation for KYB) before creating accounts.\n2. Paste the prompt with your stack details and instance ID.\n3. Test on a development instance first; review auto-approves there.\n\n## Related docs\n\n- [Virtual accounts overview](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fvirtual-accounts)\n- [Creating virtual accounts](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fvirtual-accounts-create)\n- [Blockchain wallets](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fblockchain-wallets)\n",{"title":5,"description":85},"prompts\u002Fintegrate-virtual-accounts","zmBYhM1Nx5xUIsakwEZ5eqaIrr5cRtfV_lw5ffLsv0s",[100,104,108,112,116,120,124,128,129,133,137,141,145,149,153,157,161],{"path":101,"title":102,"description":103},"\u002Fprompts\u002Fbuild-contractor-payouts","Build a global contractor payout product","Compose onboarding, bank accounts, quotes, payouts, and reconciliation into a complete pay-your-contractors feature across Pix, SPEI, SEPA, and ACH.",{"path":105,"title":106,"description":107},"\u002Fprompts\u002Fconnect-ai-agent-mcp","Connect an AI agent with the MCP server","Wire Claude, Cursor, or any MCP-compatible host to the BlindPay API with the official MCP server and agent skills, with guardrails for money movement.",{"path":109,"title":110,"description":111},"\u002Fprompts\u002Fintegrate-external-wallet-payouts","Fund payouts from external wallets","Let customers pay out from their own EVM, Solana, or Stellar wallets: signed-message registration plus the on-chain authorization step per chain.",{"path":113,"title":114,"description":115},"\u002Fprompts\u002Fintegrate-circle-wallets","Integrate Circle wallets with BlindPay","Fund BlindPay payouts from Circle developer-controlled wallets: sign the registration challenge and the ERC-20 approve through Circle's API instead of a browser wallet.",{"path":117,"title":118,"description":119},"\u002Fprompts\u002Fintegrate-dfns","Integrate Dfns with BlindPay","Fund BlindPay stablecoin payouts from Dfns MPC wallets: sign the registration challenge and the ERC-20 approve through Dfns's User Action Signature flow.",{"path":121,"title":122,"description":123},"\u002Fprompts\u002Fintegrate-fireblocks","Integrate Fireblocks with BlindPay","Fund BlindPay stablecoin payouts from Fireblocks vault accounts: MPC-signed wallet registration and the ERC-20 approve through Fireblocks' transactions API.",{"path":125,"title":126,"description":127},"\u002Fprompts\u002Fintegrate-privy","Integrate Privy with BlindPay","Fund BlindPay stablecoin payouts from Privy Server Wallets: sign the registration challenge and the ERC-20 approve through Privy's wallet RPC endpoint.",{"path":90,"title":5,"description":85},{"path":130,"title":131,"description":132},"\u002Fprompts\u002Fintegrate-utila","Integrate Utila with BlindPay","Fund BlindPay payouts from Utila MPC vaults: sign the wallet-registration challenge and the ERC-20 approve through Utila's service-account API, with async transaction confirmation handled.",{"path":134,"title":135,"description":136},"\u002Fprompts\u002Fintegrate-customer-onboarding","Integrate customer onboarding with KYC and KYB","Build the full onboarding pipeline: terms of service, individual and business customers, document uploads, RFI handling, and status webhooks.",{"path":138,"title":139,"description":140},"\u002Fprompts\u002Fintegrate-offramp-wallets","Integrate offramp wallets for auto-conversion","Give each bank account a dedicated crypto deposit address: stablecoins sent to it convert and pay out to the linked bank account automatically.",{"path":142,"title":143,"description":144},"\u002Fprompts\u002Fintegrate-payins","Integrate payins from bank transfers to stablecoins","Accept Pix, ACH, wire, SPEI, and other local bank transfers and settle them as USDC or USDT in a wallet, with quotes, payment instructions, and webhooks.",{"path":146,"title":147,"description":148},"\u002Fprompts\u002Fintegrate-quotes-fx","Integrate quotes and FX handling","Handle payin, payout, and transfer quotes correctly: expiry windows, currency_type conventions, fees, and displaying rates to users.",{"path":150,"title":151,"description":152},"\u002Fprompts\u002Fintegrate-stablecoin-payouts","Integrate stablecoin payouts end to end","Build a complete stablecoin to fiat payout flow: customer onboarding, bank accounts, quotes, and payout execution over Pix, ACH, SPEI, SEPA, and more.",{"path":154,"title":155,"description":156},"\u002Fprompts\u002Fintegrate-wallet-transfers","Integrate wallet transfers and cross-chain USDC","Move stablecoins from managed wallets to any address with transfer quotes, including cross-chain USDC over Circle CCTP v2.",{"path":158,"title":159,"description":160},"\u002Fprompts\u002Fintegrate-webhooks","Integrate webhooks end to end","Register endpoints, verify Svix signatures correctly, deduplicate retries, and drive payment state from the full BlindPay event catalog.",{"path":162,"title":163,"description":164},"\u002Fprompts\u002Fintegrate-payables","Pay boletos and Brazilian bills with payables","Register boletos, arrecadacao slips, and PIX codes as payables and settle them from stablecoins through the quote-and-execute flow.",1787868849045]