[{"data":1,"prerenderedAt":165},["ShallowReactive",2],{"content-\u002Fprompts\u002Fmigrate-from-swift-wires":3,"prompts-category-migrations":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\u002Fmigrate-from-swift-wires.md","Migrate from SWIFT wires to stablecoin payouts",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 move an international wire flow onto stablecoin rails corridor by corridor.",[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 migrating my application's international payments from SWIFT wire transfers to BlindPay stablecoin payouts, which convert USDC\u002FUSDT to local fiat and settle over local rails (Pix for BRL, SPEI for MXN, SEPA for EUR, ACH\u002FRTP\u002Fwire for USD, Transfers 3.0 for ARS).\n\nBefore writing code, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the payout quickstart, bank accounts, quotes, and payment methods pages)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nDo the migration in this order:\n1. Inventory my current wire flow: where beneficiary bank details are stored, which currencies and countries we pay, how status is tracked, and what reconciliation looks like today. Produce a corridor-by-corridor mapping to BlindPay rails, flagging any corridor BlindPay does not cover so it stays on SWIFT (BlindPay also supports international_swift as a payment rail where needed).\n2. Map beneficiary records to BlindPay: each payee becomes a customer (with KYC\u002FKYB) plus one or more bank accounts with the local rail type. SWIFT fields like IBAN\u002FBIC map to the rail-specific fields documented per bank account type.\n3. Replace the wire initiation code path with quote (POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fquotes) then payout (POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fpayouts\u002Fevm), executing before the quote's expires_at.\n4. Replace status tracking: instead of waiting days for MT103 confirmations, drive state from payout.new, payout.update, and payout.complete webhooks with Svix signature verification.\n5. Plan a phased rollout: dual-run one corridor first (shadow mode comparing costs and settlement times), then cut over corridor by corridor behind a feature flag, keeping the SWIFT path as fallback until each corridor is proven.\n\nConstraints:\n- Amounts in integer minor units; API keys server-side only.\n- Build and test everything against a development instance (USDB on testnets) before touching production.\n- Do not delete the legacy wire code until the rollback window closes.\n\nDeliverables: the corridor mapping document, beneficiary migration script, the new payout code path behind a feature flag, webhook handlers, and a cutover checklist.\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",{},"Paste the prompt and point the agent at the code that currently initiates wires.",[38,42,43],{},"Review the corridor mapping it produces before letting it write the migration.",[38,45,46],{},"Dual-run one corridor before cutting over the rest.",[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\u002Fquickstart-payout",[61],"nofollow","Payout quickstart",[38,64,65],{},[57,66,69],{"href":67,"rel":68},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fkb\u002Fpayment-methods",[61],"Payment methods",[38,71,72],{},[57,73,76],{"href":74,"rel":75},"https:\u002F\u002Fblindpay.com\u002Fpobo-cobo-swift",[61],"POBO and COBO over SWIFT",{"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},"migrations","2026-08-26","Replace multi-day international wires with same-day stablecoin settlement over local rails, keeping SWIFT as a fallback where you still need it.","md",false,{},true,"\u002Fprompts\u002Fmigrate-from-swift-wires",[92,93,94],"payouts","quotes","compliance","---\ntitle: \"Migrate from SWIFT wires to stablecoin payouts\"\ndescription: \"Replace multi-day international wires with same-day stablecoin settlement over local rails, keeping SWIFT as a fallback where you still need it.\"\ndate: \"2026-08-26\"\ncategory: \"migrations\"\nproducts: [\"payouts\", \"quotes\", \"compliance\"]\n---\n\nPaste this prompt into your coding agent to move an international wire flow onto stablecoin rails corridor by corridor.\n\n## Prompt\n\n```text\nYou are migrating my application's international payments from SWIFT wire transfers to BlindPay stablecoin payouts, which convert USDC\u002FUSDT to local fiat and settle over local rails (Pix for BRL, SPEI for MXN, SEPA for EUR, ACH\u002FRTP\u002Fwire for USD, Transfers 3.0 for ARS).\n\nBefore writing code, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the payout quickstart, bank accounts, quotes, and payment methods pages)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nDo the migration in this order:\n1. Inventory my current wire flow: where beneficiary bank details are stored, which currencies and countries we pay, how status is tracked, and what reconciliation looks like today. Produce a corridor-by-corridor mapping to BlindPay rails, flagging any corridor BlindPay does not cover so it stays on SWIFT (BlindPay also supports international_swift as a payment rail where needed).\n2. Map beneficiary records to BlindPay: each payee becomes a customer (with KYC\u002FKYB) plus one or more bank accounts with the local rail type. SWIFT fields like IBAN\u002FBIC map to the rail-specific fields documented per bank account type.\n3. Replace the wire initiation code path with quote (POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fquotes) then payout (POST \u002Fv1\u002Finstances\u002F{instance_id}\u002Fpayouts\u002Fevm), executing before the quote's expires_at.\n4. Replace status tracking: instead of waiting days for MT103 confirmations, drive state from payout.new, payout.update, and payout.complete webhooks with Svix signature verification.\n5. Plan a phased rollout: dual-run one corridor first (shadow mode comparing costs and settlement times), then cut over corridor by corridor behind a feature flag, keeping the SWIFT path as fallback until each corridor is proven.\n\nConstraints:\n- Amounts in integer minor units; API keys server-side only.\n- Build and test everything against a development instance (USDB on testnets) before touching production.\n- Do not delete the legacy wire code until the rollback window closes.\n\nDeliverables: the corridor mapping document, beneficiary migration script, the new payout code path behind a feature flag, webhook handlers, and a cutover checklist.\n```\n\n## How to use\n\n1. Paste the prompt and point the agent at the code that currently initiates wires.\n2. Review the corridor mapping it produces before letting it write the migration.\n3. Dual-run one corridor before cutting over the rest.\n\n## Related docs\n\n- [Payout quickstart](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fquickstart-payout)\n- [Payment methods](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fkb\u002Fpayment-methods)\n- [POBO and COBO over SWIFT](https:\u002F\u002Fblindpay.com\u002Fpobo-cobo-swift)\n",{"title":5,"description":85},"prompts\u002Fmigrate-from-swift-wires","C8a_3-inBHQZALtfOQUj98AzVBpIxG5XFaVXSgzlUHQ",[100,104,108,112,116,120,124,128,132,136,140,144,148,152,153,157,161],{"path":101,"title":102,"description":103},"\u002Fprompts\u002Fmigrate-from-anchorage","Migrate from Anchorage Digital to BlindPay","Keep Anchorage Digital for custody and move the stablecoin-to-fiat leg to BlindPay: map transfers, withdrawals, and settlement events to BlindPay quotes, payouts, and webhooks.",{"path":105,"title":106,"description":107},"\u002Fprompts\u002Fmigrate-from-bitgo","Migrate from BitGo to BlindPay","Move the stablecoin-to-fiat leg of a BitGo integration to BlindPay: map wallets, transfers, and settlement webhooks to BlindPay customers, quotes, payouts, and Svix events.",{"path":109,"title":110,"description":111},"\u002Fprompts\u002Fmigrate-from-bridge","Migrate from Bridge to BlindPay","Move an existing Bridge integration to the BlindPay API: map customers, external accounts, liquidation addresses, and transfers to their BlindPay equivalents.",{"path":113,"title":114,"description":115},"\u002Fprompts\u002Fmigrate-from-circle","Migrate from Circle to BlindPay","Move payouts and fiat on\u002Foff ramps from Circle Mint or the Circle Payments Network to BlindPay's quote-and-execute API with local rails.",{"path":117,"title":118,"description":119},"\u002Fprompts\u002Fmigrate-from-cobo","Migrate from Cobo to BlindPay","Move an existing Cobo Payments integration to the BlindPay API: keep Cobo for custody if you want, and replace the stablecoin-to-fiat leg with BlindPay's customers, quotes, and payouts.",{"path":121,"title":122,"description":123},"\u002Fprompts\u002Fmigrate-from-coinbase-cdp","Migrate from Coinbase CDP to BlindPay","Move the stablecoin-to-fiat offramp leg of a Coinbase Developer Platform integration to BlindPay: add Pix, SPEI, SEPA, ACH, and wire payouts while CDP wallets keep custody.",{"path":125,"title":126,"description":127},"\u002Fprompts\u002Fmigrate-from-conduit","Migrate from Conduit to BlindPay","Move a Conduit cross-border payments integration to BlindPay: counterparties, corridors, and settlement tracking on the quote-and-execute model.",{"path":129,"title":130,"description":131},"\u002Fprompts\u002Fmigrate-from-crossmint","Migrate from Crossmint to BlindPay","Move the stablecoin-to-fiat leg of a Crossmint integration to BlindPay while Crossmint keeps handling wallets, checkout, or orchestration.",{"path":133,"title":134,"description":135},"\u002Fprompts\u002Fmigrate-from-dfns","Migrate from Dfns to BlindPay","Keep Dfns for MPC wallet custody and move the stablecoin-to-fiat leg to BlindPay: map transfers and exchange withdrawals to quotes, payouts, and registered external wallets.",{"path":137,"title":138,"description":139},"\u002Fprompts\u002Fmigrate-from-dynamic","Migrate from Dynamic to BlindPay","Keep Dynamic for embedded and server wallets, move the stablecoin-to-fiat offramp leg to BlindPay: register the Dynamic wallet, quote and execute payouts, and verify webhooks.",{"path":141,"title":142,"description":143},"\u002Fprompts\u002Fmigrate-from-fern","Migrate from Fern to BlindPay","Move a Fern stablecoin integration to BlindPay: customers, wallets, on\u002Foff ramps, and webhook-driven settlement on the quote-and-execute model.",{"path":145,"title":146,"description":147},"\u002Fprompts\u002Fmigrate-from-fireblocks","Migrate from Fireblocks to BlindPay","Move the stablecoin-to-fiat payout leg of a Fireblocks integration to BlindPay: map payout instruction sets, fiat accounts, and webhooks while Fireblocks stays as custodian.",{"path":149,"title":150,"description":151},"\u002Fprompts\u002Fmigrate-from-privy","Migrate from Privy to BlindPay","Keep Privy for embedded and server wallets, move the stablecoin-to-fiat offramp leg to BlindPay: register the Privy wallet, quote and execute payouts, and verify webhooks.",{"path":90,"title":5,"description":85},{"path":154,"title":155,"description":156},"\u002Fprompts\u002Fmigrate-from-turnkey","Migrate from Turnkey to BlindPay","Keep Turnkey for wallets and signing, and move the stablecoin-to-fiat offramp leg of a Turnkey-based product to BlindPay: map payout accounts, quotes, and webhooks.",{"path":158,"title":159,"description":160},"\u002Fprompts\u002Fmigrate-from-utila","Migrate from Utila to BlindPay","Keep Utila as custodian and signer, and route the stablecoin-to-fiat leg through BlindPay: map vaults, wallets, transactions, and webhooks to their BlindPay equivalents.",{"path":162,"title":163,"description":164},"\u002Fprompts\u002Fmigrate-from-manual-payouts","Migrate from manual bank payouts to the API","Turn a spreadsheet-and-bank-portal payout operation into an automated, webhook-driven API flow with an auditable state machine.",1787868850548]