Skip to content
Back to Prompts

Production readiness checklist

Verify a BlindPay integration is ready to move from a development instance to production: config, tokens, networks, webhooks, compliance, and monitoring.

Payouts
Payins
Virtual accounts
Compliance
Webhooks

Paste this prompt into your coding agent before flipping a development-instance integration to production.

Prompt

text
My BlindPay integration works on a development instance. Verify it is ready for production and produce a go/no-go checklist with evidence from my code and configuration.

Ground truth:
- https://blindpay.com/docs/llms.txt (read the sandbox vs production and instances pages, plus the pages for the flows in my code)
- The OpenAPI spec: curl https://api.blindpay.com/doc

Verify each item and mark it pass or fail with the evidence:
1. 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).
2. 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/USDT on mainnets.
3. Test scaffolding removed: no sentinel-amount logic ($666.00/$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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.

Output: the checklist with pass/fail and evidence per item, the blocking failures, and the exact changes needed to reach go.

How to use

  1. Run this after the integration quality audit passes; this one focuses on the dev-to-prod transition.
  2. Request your production instance early; approval can take days.
  3. Keep the output as your launch sign-off document.

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.