notabene-primary-sources-2026-04-22

Notabene primary-source snapshot

Fetched: 2026-04-22 UTC

1) Official homepage

Source: https://notabene.id/

Selected excerpts from the official site:

Notabene connects financial institutions worldwide with instant, compliant, and secure stablecoin payments and crypto transactions.

The open trust layer for global payments.

Notabene isn’t just a product. It’s a modular architecture for pre-transaction coordination—spanning protocol, network, and interface.

Additional signals from the homepage:

• Product layers are presented as Notabene Flow, Notabene Transact, and Transaction Authorization Protocol (TAP)
• Flow is positioned around pull payments, push payments, and recurring payments for businesses
• Homepage claims 2,000+ verified entities in the network, 100+ jurisdictions, 85% straight-through processing, $600Binstablecointransactions,and$1T+ annual TPV processed on the network

2) Official Transact product page

Source: https://notabene.id/transact

Selected excerpts from the official site:

Notabene Transact automates pre-transaction decision-making, turning Travel Rule compliance requirements into faster settlements, more throughput, and fewer blockers to revenue.

Transaction Authorization Protocol (TAP) defines how counterparties coordinate authorization before a blockchain transaction settles—across any platform or network.

It uses signed Transfer Requests and encrypted messaging to authorize payments securely across wallets, exchanges, and smart contracts.

Additional signals from the Transact page:

• Product copy emphasizes multi-party coordination, multi-dimensional policy control, cross-border and multi-leg transaction handling, and real-time policy enforcement
• The page explicitly describes the product as API-first and links out to documentation at https://doc.notabene.id/
• Notabene frames the network as a counterparty-discovery and authorization layer rather than a token or L1/L2 thesis

3) Official API documentation

Source: https://doc.notabene.id/

Selected excerpts from the API docs:

The Notabene API is organized around REST.

Our API accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP status codes and verbs.

All requests to the Notabene API should be made to one of the following root URLs: Test: https://api.notabene.dev; Live: https://api.notabene.id

Additional signals from the docs:

• Docs describe DIDs as a foundational identity primitive in the API model
• Public endpoint groupings include Transactions, VASP Administration, Trust Framework, Customer, Documents, Address Book, Rules, Settings, and Integrations
• Integration sections reference external compliance / risk vendors including Chainalysis, Elliptic, TRM, LexisNexis, Refinitiv, ComplyAdvantage, Coinfirm, BitGo, and Merkle Science
• The docs surface suggests Notabene is an operating platform for institutional transaction workflows, not just a point compliance product

4) Official security page

Source: https://notabene.id/security

Selected excerpts from the official site:

Notabene was built from the ground up by veterans of the digital identification and crypto industries.

We created a next-generation cloud platform that passes bank-grade security compliance assessments and uses advanced cryptographic techniques.

All data elements are individually cryptographically signed and immutable as W3C Verifiable Credentials.

Additional signals from the security page:

• Notabene says PII records are individually encrypted and can use customer-managed keys for signing and encryption
• Security page claims annual SOC 2 Type II audits, recurring Cobalt penetration testing, and real-time control monitoring via Vanta
• The page stresses secure data exchange and due-diligence posture for Travel Rule counterparties

5) Official GitHub organization and OpenVASP materials

Sources:

• https://github.com/Notabene-id
• https://github.com/Notabene-id/openvasp-node-client
• https://notabene-id.github.io/openvasp-node-client/

Selected excerpts from the public GitHub materials:

OpenVASP Typescript Library

A VASPCode with the corresponding VASP contract (to store the handshake and signing keys) needs to be created to use OpenVASP.

Documentation: https://notabene-id.github.io/openvasp-node-client/

Additional signals from the GitHub materials:

• Public org repos include openvasp-node-client, did-auth-express, go-didcomm, notabene-crypto, and other identity / protocol-adjacent tools
• The OpenVASP client examples show VASP contract creation, handshake keys, signing keys, and VASP-code utilities
• These repos look more legacy / protocol-tooling oriented than the current marketing site, but they help explain Notabene’s roots in identity and pre-transaction coordination

Notes

• This pass did not locate a classic whitepaper or litepaper from official Notabene sources.
• The strongest primary materials in this pass were the homepage, Transact page, API docs, security page, and public GitHub / OpenVASP materials.
• An older docs hostname (https://docs.notabene.id/) returned a Cloudflare configuration error during this pass, while https://doc.notabene.id/ served the live API documentation.