[{"data":1,"prerenderedAt":115},["ShallowReactive",2],{"content-\u002Fprompts\u002Fproduction-readiness-checklist":3,"prompts-category-diagnostics":106},{"id":4,"title":5,"author":6,"body":7,"categories":6,"category":88,"categoryType":6,"date":89,"description":90,"extension":91,"faq":6,"howto":6,"isBlog":92,"isChangelog":92,"meta":93,"navigation":94,"path":95,"pillar":92,"products":96,"rawbody":102,"seo":103,"stem":104,"thumbnail":6,"updated":6,"__hash__":105},"content\u002Fprompts\u002Fproduction-readiness-checklist.md","Production readiness checklist",null,{"type":8,"value":9,"toc":82},"minimark",[10,14,19,30,34,53,57],[11,12,13],"p",{},"Paste this prompt into your coding agent before flipping a development-instance integration to production.",[15,16,18],"h2",{"id":17},"prompt","Prompt",[20,21,27],"pre",{"className":22,"code":24,"language":25,"meta":26},[23],"language-text","My BlindPay integration works on a development instance. Verify it is ready for production and produce a go\u002Fno-go checklist with evidence from my code and configuration.\n\nGround truth:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the sandbox vs production and instances pages, plus the pages for the flows in my code)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nVerify each item and mark it pass or fail with the evidence:\n1. Instance separation: production uses its own instance ID and its own API key (dev keys do not work in prod); both come from environment config, never hardcoded; the production instance has been requested (approval can take up to 3 business days).\n2. Token and network swap: no USDB and no testnet networks (base_sepolia, solana_devnet, sepolia, polygon_amoy, arbitrum_sepolia, stellar_testnet) reachable from production config; production uses USDC\u002FUSDT on mainnets.\n3. Test scaffolding removed: no sentinel-amount logic ($666.00\u002F$777.00), no auto-approve assumptions. Production KYC takes real time (standard about 60 seconds, enhanced and KYB up to a business day), so onboarding must be genuinely webhook-driven with a pending state in the UX, not a synchronous wait.\n4. Webhooks re-registered: endpoint configuration does not carry over between instances; the production endpoint is registered on the production instance, its own whsec_ secret is in production config, and a real signed event has been received and verified there.\n5. Real-world failure handling: rejected KYC and RFIs surface to users with a path forward; failed and refunded payouts alert someone; quote expiry triggers re-quote, not a stuck payment.\n6. Limits and coverage: expected transaction sizes fit the per-transaction, daily, and monthly limits for my customers' KYC tiers, and every corridor I serve is supported in production; flag anything needing a limit increase in advance.\n7. Monitoring: alerting exists for webhook delivery failures, payouts stuck in non-terminal states beyond the rail's expected settlement time, and reconciliation mismatches between my ledger and BlindPay statuses.\n8. Runbook: a written procedure exists for a stuck or failed payment, including where to find the payout in the dashboard and how to contact BlindPay support.\n\nOutput: the checklist with pass\u002Ffail and evidence per item, the blocking failures, and the exact changes needed to reach go.\n","text","",[28,29,24],"code",{"__ignoreMap":26},[15,31,33],{"id":32},"how-to-use","How to use",[35,36,37,47,50],"ol",{},[38,39,40,41,46],"li",{},"Run this after the ",[42,43,45],"a",{"href":44},"\u002Fprompts\u002Fintegration-quality-audit","integration quality audit"," passes; this one focuses on the dev-to-prod transition.",[38,48,49],{},"Request your production instance early; approval can take days.",[38,51,52],{},"Keep the output as your launch sign-off document.",[15,54,56],{"id":55},"related-docs","Related docs",[58,59,60,68,75],"ul",{},[38,61,62],{},[42,63,67],{"href":64,"rel":65},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Fsandbox-vs-production",[66],"nofollow","Sandbox vs production",[38,69,70],{},[42,71,74],{"href":72,"rel":73},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Finstances",[66],"Instances",[38,76,77],{},[42,78,81],{"href":79,"rel":80},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fkb\u002Fcut-off-times",[66],"Cut-off times and limits",{"title":26,"searchDepth":83,"depth":83,"links":84},2,[85,86,87],{"id":17,"depth":83,"text":18},{"id":32,"depth":83,"text":33},{"id":55,"depth":83,"text":56},"diagnostics","2026-08-26","Verify a BlindPay integration is ready to move from a development instance to production: config, tokens, networks, webhooks, compliance, and monitoring.","md",false,{},true,"\u002Fprompts\u002Fproduction-readiness-checklist",[97,98,99,100,101],"payouts","payins","virtual-accounts","compliance","webhooks","---\ntitle: \"Production readiness checklist\"\ndescription: \"Verify a BlindPay integration is ready to move from a development instance to production: config, tokens, networks, webhooks, compliance, and monitoring.\"\ndate: \"2026-08-26\"\ncategory: \"diagnostics\"\nproducts: [\"payouts\", \"payins\", \"virtual-accounts\", \"compliance\", \"webhooks\"]\n---\n\nPaste this prompt into your coding agent before flipping a development-instance integration to production.\n\n## Prompt\n\n```text\nMy BlindPay integration works on a development instance. Verify it is ready for production and produce a go\u002Fno-go checklist with evidence from my code and configuration.\n\nGround truth:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the sandbox vs production and instances pages, plus the pages for the flows in my code)\n- The OpenAPI spec: curl https:\u002F\u002Fapi.blindpay.com\u002Fdoc\n\nVerify each item and mark it pass or fail with the evidence:\n1. Instance separation: production uses its own instance ID and its own API key (dev keys do not work in prod); both come from environment config, never hardcoded; the production instance has been requested (approval can take up to 3 business days).\n2. Token and network swap: no USDB and no testnet networks (base_sepolia, solana_devnet, sepolia, polygon_amoy, arbitrum_sepolia, stellar_testnet) reachable from production config; production uses USDC\u002FUSDT on mainnets.\n3. Test scaffolding removed: no sentinel-amount logic ($666.00\u002F$777.00), no auto-approve assumptions. Production KYC takes real time (standard about 60 seconds, enhanced and KYB up to a business day), so onboarding must be genuinely webhook-driven with a pending state in the UX, not a synchronous wait.\n4. Webhooks re-registered: endpoint configuration does not carry over between instances; the production endpoint is registered on the production instance, its own whsec_ secret is in production config, and a real signed event has been received and verified there.\n5. Real-world failure handling: rejected KYC and RFIs surface to users with a path forward; failed and refunded payouts alert someone; quote expiry triggers re-quote, not a stuck payment.\n6. Limits and coverage: expected transaction sizes fit the per-transaction, daily, and monthly limits for my customers' KYC tiers, and every corridor I serve is supported in production; flag anything needing a limit increase in advance.\n7. Monitoring: alerting exists for webhook delivery failures, payouts stuck in non-terminal states beyond the rail's expected settlement time, and reconciliation mismatches between my ledger and BlindPay statuses.\n8. Runbook: a written procedure exists for a stuck or failed payment, including where to find the payout in the dashboard and how to contact BlindPay support.\n\nOutput: the checklist with pass\u002Ffail and evidence per item, the blocking failures, and the exact changes needed to reach go.\n```\n\n## How to use\n\n1. Run this after the [integration quality audit](\u002Fprompts\u002Fintegration-quality-audit) passes; this one focuses on the dev-to-prod transition.\n2. Request your production instance early; approval can take days.\n3. Keep the output as your launch sign-off document.\n\n## Related docs\n\n- [Sandbox vs production](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Fsandbox-vs-production)\n- [Instances](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Finstances)\n- [Cut-off times and limits](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fkb\u002Fcut-off-times)\n",{"title":5,"description":90},"prompts\u002Fproduction-readiness-checklist","2JsIhDEKp3x8KkVOFvJrqtUw9TqsSnvzuCEc8G8ugOU",[107,111,114],{"path":108,"title":109,"description":110},"\u002Fprompts\u002Fbuild-reconciliation-ledger","Build a reconciliation ledger","A daily job that compares your database against BlindPay's payout, payin, and transfer statuses, catches drift, and alerts on stuck or mismatched money.",{"path":44,"title":112,"description":113},"Integration quality audit","Audit an existing BlindPay integration for correctness and resilience: quote expiry handling, webhook security, idempotency, error paths, and reconciliation.",{"path":95,"title":5,"description":90},1787868851424]