Cowrie Research

blockradar

4 min read

Blockradar

  • Name: Blockradar
  • URL: https://www.blockradar.co/
  • Category: stablecoin wallet-and-settlement infrastructure company / fintech wallet-control-plane operator / virtual-account and payout workflow vendor
  • Summary: Blockradar clears the bar for a company note because the analytically useful question is not only what wallet API exists? but which named operator packages address issuance, virtual-account mapping, AML and blocklist policy, auto-settlement routing, gateway usage, and the compliance-and-webhook shell fintech customers may start treating as operational truth? The product surface matters, but the sharper dependency is the company-run operating layer around funding, screening, routing, and payout workflow.
  • What it does:
    • Runs Wallet-as-a-Service infrastructure for fintechs that want stablecoin wallets, addresses, balances, and transaction monitoring through one operator-managed API surface
    • Packages pay-in, pay-out, virtual-account, and cross-chain settlement flows around the same platform rather than selling only a narrow wallet primitive
    • Exposes AML screening, whitelist and blacklist checks, monitoring, and compliance workflow as part of the default operating shell
    • Lets operators define auto-sweep and auto-settlement rules with routing-style preferences like FASTEST, CHEAPEST, RECOMMENDED, and NO_SLIPPAGE
    • Markets corridor-based treasury, remittance, neobank, and borderless-banking use cases rather than a neutral protocol primitive
  • Key claims:
    • The homepage calls Blockradar secure stablecoin wallet infrastructure for fintechs and highlights plug-and-play APIs, non-custodial wallets, auto-sweeping, gasless transactions, and built-in compliance
    • The docs introduction says Blockradar is a wallet and settlement infrastructure platform for fintechs and explicitly packages Wallet-as-a-Service, settlement rails, and compliance tooling for remittance, neobank, cross-border payments, and savings-platform use cases
    • The docs say Blockradar provides dedicated wallet addresses, real-time webhook notifications, virtual accounts linked to on-chain addresses, cross-chain settlement through the Blockradar Gateway, stablecoin checkout flows, and corridor-oriented FX/liquidity management
    • The docs frame Blockradar as non-custodial by design, but they also say users’ wallets are generated and controlled through the client’s API keys, which keeps the practical control-surface question centered on operator-managed key issuance, API access, and workflow defaults rather than on custody marketing alone
    • The docs say every wallet comes with real-time AML screening against OFAC, FBI, Tether, and Circle blocklists, which is a direct example of company-run admission and filtering logic becoming part of the live transaction path
    • The auto-settlement API reference exposes rule configuration for wallet-level settlement, including typed flows like withdraw, swap, gateway, or earn, plus routing preferences and destination controls, which is stronger evidence of an operator-managed treasury and settlement shell than a simple wallet SDK would provide
  • Whitepaper: No standalone company whitepaper is the point here. The clearest primary materials are the homepage, the docs introduction, the auto-settlement API reference, and the earlier source capture in ../whitepapers/blockradar-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

  • Legacy project alias: blockradar.
  • Strong adjacent operator reads: bvnk, bridge-xyz, and coinflow.
  • Reusable lens: stablecoin-wallet vendors often need a separate company cut when webhook truth, AML policy, virtual-account issuance, and settlement routing sit behind one named operator boundary.

Protocol / company boundary

  • Keep this note on the company boundary: address issuance, wallet and API-key provisioning, webhook and monitoring truth, AML policy, virtual-account mapping, gateway and payout routing, and auto-settlement rule semantics.
  • Do not force a separate protocol note right now. Blockradar is already the company-facing product brand, and the useful split is between the named operator shell and the underlying rails or settlement mechanisms it composes.
  • That matters because how does a fintech receive stablecoin deposits or route payouts? and which company controls the compliance, rule-engine, and webhook shell around that workflow? are related but not identical questions.

Control surface

  • Practical leverage sits in customer onboarding, API-key issuance, address and virtual-account provisioning, AML and blacklist policy, auto-sweep defaults, auto-settlement routing, gateway usage, payout rules, webhook truth, and incident handling around the live wallet stack.

  • The important point is not merely that Blockradar exposes wallet endpoints. It is that one named operator can become the policy, routing, and compliance shell around a fintech’s stablecoin treasury and payout workflow.

  • Read Blockradar as company-run payment and settlement middleware, not as a neutral payments rail.

  • Last reviewed: 2026-08-09 UTC

Graph View

Backlinks