Aquanow

• Name: Aquanow
• URL: https://www.aquanow.com/
• Category: institutional digital-asset infrastructure / brokerage-and-payments control-plane company / custody-and-compliance workflow operator
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Aquanow belongs in companies/, not just projects/, because the durable dependency is a named company operating the account, custody, compliance, trading, settlement, and payment workflow shell that institutions inherit. The useful question is not only what products does Aquanow expose? but which company controls customer admission, sub-account structure, wallet handling, approval workflow, Travel Rule posture, payment routing, and operational truth across the stack?
• What it does:
  • Sells institutional digital-asset infrastructure to banks, neobanks, brokerages, payment companies, and enterprises rather than only offering a narrow end-user app or venue surface
  • Runs CAMS, a client-account management and virtual-asset operations system with multi-sub-account customer structures, dedicated-wallet support, fiat and crypto funding flows, RFQ spot trading, and custody operations
  • Packages brokerage, payments, send, and hold workflows inside one commercial operating shell with APIs spanning customers, funding requests, trades, executions, settlements, withdrawals, payouts, transfers, custody, files, and VASP-related resources
  • Exposes access-rights, approval workflows, pricing and fee configuration, and compliance controls including KYC, AML, Travel Rule, and FATF checks as part of the same company-run stack
  • Markets stablecoin settlement and money-movement infrastructure in partnership with larger financial rails, including Visa’s CEMEA stablecoin-settlement expansion
  • Operates through licensed or registered entities across multiple jurisdictions, which reinforces that the relevant control surface is organizational and regulatory, not just product-shaped
• Key claims:
  • Aquanow’s homepage now frames the company as Digital Asset Infrastructure for Institutions and markets a unified infrastructure layer combining institutional liquidity, compliant operations, and scalable technology
  • The CAMS docs describe Aquanow as providing a robust financial software solution for comprehensive virtual-asset management, including customer setup, sub-accounts, wallet organization, funding flows, RFQ trading, custody, approval workflows, and compliance checks
  • The same docs explicitly call out configurable user permissions, approval workflows, pricing and fee settings, and security monitoring, which is strong evidence that the practical authority sits in company-run operating defaults
  • The public site emphasizes regulated infrastructure, Security & Compliance, and institutional deployment for banks, brokerages, payment providers, fintechs, and enterprises rather than a neutral protocol surface
  • The Visa stablecoin-settlement announcement says Aquanow’s infrastructure is being integrated with Visa’s network so issuers and acquirers can settle using approved stablecoins, and says Aquanow underwrites billions of dollars in monthly crypto brokerage and payment transactions
  • Aquanow’s own regulatory language says it operates through licensed and registered entities in multiple jurisdictions, which matters because partner access, product scope, and legal operating posture all flow through the company boundary
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are Aquanow’s homepage, CAMS documentation, API reference, and the Visa stablecoin-settlement announcement; the source bundle remains ../whitepapers/aquanow-primary-sources-2026-04-30.md.
• Sources:
  • https://www.aquanow.com/
  • https://www.aquanow.com/products/trade
  • https://www.aquanow.com/products/pay
  • https://www.aquanow.com/infrastructure/compliance
  • https://docs.aquanow.io/cams/welcome.md
  • https://docs.aquanow.io/cams/api-reference
  • https://www.aquanow.com/insights-blog/aquanow-partners-with-visa-to-enable-faster-settlement-using-stablecoins

Internal linkages

• Project-layer alias note: aquanow.
• Useful adjacent company reads: talos, bitgo, and fireblocks.
• Cleaner contrast where the question becomes market-structure middleware rather than one company’s managed institutional stack: bridgeport.

Protocol / company boundary

• Aquanow does not read like a neutral protocol or standalone network whose deployed mechanics explain the main risk.
• The analytically important surface is the company-run operating shell that packages client onboarding, customer-account structure, wallet and custody handling, trading workflow, payment routing, settlement state, compliance checks, and partner support inside one institutional dependency.
• That is why Aquanow belongs in companies/: the real leverage sits with the entity that controls the workflow graph, not with an abstract protocol boundary.

Control surface

• Practical authority sits in partner admission, account and sub-account modeling, wallet and custody configuration, approval workflow, pricing and fee controls, RFQ trading access, fiat and crypto funding rails, compliance policy, Travel Rule handling, payout and withdrawal lifecycle, and the API or dashboard surfaces institutions treat as operational truth.

• The sticky dependency is workflow memory: once a bank, brokerage, or payments firm builds around Aquanow-managed customer objects, wallet mappings, approvals, compliance decisions, and settlement lifecycle state, the real lock-in is to the company-run operating shell rather than to a generic liquidity or payments API.

• Read Aquanow as an institutional operator boundary first. Trade, Pay, Send, and Hold are product branches on top of the same company-controlled infrastructure.

• Last reviewed: 2026-08-06 UTC