Notabene

• Name: Notabene
• URL: https://notabene.id/
• Category: transaction-authorization network operator / Travel Rule compliance company / pre-settlement stablecoin-payments workflow company
• Summary: Notabene belongs as an entity note, not a protocol note. The useful question is who operates the verified-counterparty network, authors the pre-transaction policy and authorization workflow, handles identity discovery and sensitive-data exchange, and turns Travel Rule or stablecoin-payment requirements into day-to-day operational truth for counterparties before funds move. That authority sits with the Notabene company boundary more clearly than with TAP alone.
• What it does:
  • Operates a network of verified counterparties for compliant crypto and stablecoin transactions across jurisdictions
  • Runs Notabene Transact for pre-transaction decision-making, policy enforcement, and Travel Rule authorization before settlement
  • Runs Notabene Flow for business payment flows such as pull payments, push payments, and recurring billing
  • Exposes API surfaces for transfers, VASP administration, rules, documents, webhooks, and related trust-framework operations
  • Packages DIDs, signed transfer requests, encrypted messaging, and role-based access patterns into one operator-managed workflow stack
  • Markets managed security and privacy controls around PII exchange, auditable custody, and customer-managed keys rather than leaving those concerns to a neutral protocol layer
• Key claims:
  • The homepage calls Notabene the open trust layer for global payments and frames the stack as one system, three layers spanning Notabene Flow, Notabene Transact, and the Transaction Authorization Protocol
  • The homepage says 2,000+ verified entities use the Notabene network across 100+ jurisdictions, claims 85% straight-through processing, and markets both $1T+annualTPVandmorethan$2T of compliant volume moved through the network; those are useful scale signals, but still vendor claims
  • The Transact page says Notabene automates pre-transaction decision-making, supports multi-party flows and jurisdiction-specific rules, and lets customers approve or reject transactions instantly using flexible risk-based authorization logic
  • The same materials say counterparties coordinate through TAP using signed Transfer Requests and encrypted messaging before a blockchain transaction settles, which is exactly why the operator boundary matters: the company packages the workflow that makes those messages actionable in practice
  • The security page says all data elements are individually signed as W3C Verifiable Credentials, PII records are individually encrypted, sensitive Travel Rule data can be held in escrow pending due-diligence checks, and customers can use their own signing and encryption keys
  • The security page also says Notabene undergoes annual SOC 2 Type II auditing, regular penetration testing, and supports IAM integration plus granular role setup, reinforcing that the company is selling a security-sensitive institutional workflow environment rather than a simple messaging standard
• Whitepaper: No classic standalone company whitepaper is the important artifact here. The strongest current primary materials are Notabene’s homepage, Transact page, security materials, developer documentation, and public GitHub organization; the earlier source capture remains ../whitepapers/notabene-primary-sources-2026-04-22.md.
• Sources:
  • https://notabene.id/
  • https://notabene.id/transact
  • https://notabene.id/security
  • https://doc.notabene.id/
  • https://github.com/Notabene-id
  • https://github.com/Notabene-id/openvasp-node-client
  • https://notabene-id.github.io/openvasp-node-client/

Internal linkages

• Project-layer alias: notabene.
• Keep the protocol / company split explicit: transaction-authorization-protocol is the open pre-settlement messaging layer, while this note is the operator and workflow boundary.
• Useful adjacent entity reads: 21-analytics, chainalysis, and trm-labs.
• Transport-interoperability contrast: trisa.

Protocol / company boundary

• TAP is the protocol layer: signed pre-transaction messages, authorization semantics, and the idea of coordinating before settlement.
• Notabene is the company layer: verified-counterparty network admission, identity discovery, workflow defaults, rules engines, managed security posture, and the API / dashboard surface that institutions actually wire into payment and compliance operations.
• That distinction matters because the sticky dependency is rarely a protocol exists. It is which network operator and workflow stack do institutions treat as the real authorization surface before they release funds?

Control surface

• Practical leverage sits in verified-counterparty admission, network reachability, policy templates and rule evaluation, identity discovery, how multi-party flows are represented, which pre-transaction checks block or clear settlement, how sensitive Travel Rule data is encrypted and escrowed, and which API or webhook events downstream teams treat as authoritative.

• Notabene does not matter because it owns a blockchain. It matters because it can become the company-run trust and authorization layer that counterparties rely on before money moves.

• Read Notabene as a compliance-and-payments workflow operator, not as a neutral protocol primitive.

• Last reviewed: 2026-08-06 UTC