BlindPay

• Name: BlindPay
• URL: https://www.blindpay.com/
• Category: stablecoin-fiat payments infrastructure / payout corridor control plane
• Summary: BlindPay is a corridor operator with an API, not a protocol. The useful thing here is the operational surface: receivers, quotes, bank accounts, virtual accounts, webhooks, and wallet-linked settlement across local fiat rails. The AI-agent packaging is real, but it is still packaging around a payments operations stack.
• What it does:
  • Provides APIs and dashboard workflows for stablecoin payins and fiat payouts built around receivers, quotes, transfers, wallets, and virtual accounts
  • Connects supported stablecoin networks to local banking rails and compliance checks
  • Exposes partner-fee, webhook, and API-key surfaces so integrators can run payout workflows from software rather than manual ops
  • Publishes MCP, CLI, and agent-facing surfaces, which makes the platform unusually explicit about machine-operated payments workflows
• Key claims:
  • Official docs position BlindPay as non-custodial global payments infrastructure rather than a wallet
  • The product surface is broad for a smaller vendor: payout and payin quotes, receivers, bank accounts, virtual accounts, blockchain wallets, partner fees, webhooks, and file upload
  • Failed settlements are described as refunding back to the originating wallet, which reinforces the model: BlindPay coordinates corridors and state, while final asset movement starts from user-controlled wallets
  • The first-party MCP server, skills index, and CLI show the company is intentionally packaging this stack for agentic and developer operation
• Whitepaper: No canonical standalone BlindPay whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, docs corpus, well-known agent endpoints, and first-party GitHub repos; see ../whitepapers/blindpay-primary-sources-2026-04-30.md.
• Sources:
  • https://www.blindpay.com/
  • https://www.blindpay.com/docs/getting-started/overview
  • https://www.blindpay.com/docs/getting-started/quick-start
  • https://www.blindpay.com/.well-known/mcp/server-card.json
  • https://www.blindpay.com/.well-known/agent-skills/index.json
  • https://www.blindpay.com/blog/mcp
  • https://www.blindpay.com/blog/cli
  • https://github.com/blindpaylabs/blindpay-cli
  • https://github.com/blindpaylabs/blindpay-skills

Internal linkages

• Best upward reads for this corridor-operator branch: bridge-xyz, coinflow, and dakota.

Governance / control risk

• The practical power sits in corridor coverage, quote construction, receiver approval, webhook state, compliance review, and payout failure handling.

• So non-custodial does not remove operator leverage. It just moves it away from wallet custody and into routing and approval policy.

• Read BlindPay as a smaller corridor stack pointing upward to stronger payment-control anchors, not as a general payments baseline.

• Last reviewed: 2026-05-28 UTC