Here is the comprehensive side-by-side comparison of Notabene vs. RemiDe followed by strategic actions to maximize defensibility and competitive edge.
Updated: July 2025
For use in investor/partner discussions or standalone Notion page
| Category | Notabene | RemiDe |
|---|---|---|
| Core Function | FATF Travel Rule relay (SaaS for VASPs) | Wallet-to-wallet remittance routing layer with built-in compliance |
| Positioning | Compliance middleware | Embedded payment + compliance infrastructure |
| Business Model | B2B SaaS (license + API calls) | Transaction-fee-based network (0.9% → 0.4%) |
| Target Users | Compliance teams at exchanges, custodians | Web3 wallets (30k–1m MAU) in EM corridors |
| Form Factor | Dashboard + API + network of VASPs | API + SDK; no UI layer for wallets’ end users |
| Feature | Notabene | RemiDe |
|---|---|---|
| Travel Rule Protocol | Sends full IVMS-101 packet to counterparty VASP via mTLS & JWE | Sends full IVMS-101 via /travelRule/notify; ACK required within 1s or tx fails |
| KYC / IVMS-101 Data | Sees full unencrypted PII | Stores full PII (DoB, ID#, name, etc.); attestation hash stored 5y |
| PII Storage Location | Centralized (hosted by Notabene, unclear data regions) | Frankfurt (AWS eu-central-1); structured for GDPR/BR/RU compliance |
| Legal Role | Technical service provider (no liability) | Joint controller with wallet under GDPR/MiCA |
| Sanctions Checks | Optional; integrates Chainalysis | Self-attestation model + optional sanctions API (TRM / Elliptic) |
| Element | Notabene | RemiDe |
|---|---|---|
| Money Movement | Does not handle funds; messaging only | Executes transfer (same- or cross-chain), reconciles fees |
| Custody | Not applicable | Non-custodial by design: funds held by sending/receiving wallets |
| Settlement Path | Outside scope | Native stablecoin (USDT→USDC); cross-chain via Circle CCTP |
| Cross-Chain Flow | Not supported | Fully abstracted: Tron → Polygon → Base via native burn/mint |
| Aspect | Notabene | RemiDe |
|---|---|---|
| End-User Touchpoint | None (pure backend) | RemiTag alias + 4-digit code UX; sub-20s delivery for user |
| Partner Integration Time | Weeks–months (due diligence, API setup) | ≤5 business days onboarding (MSA + KYC vendor + $100 prefund) |
| Prefund Requirement | None | $100 refundable fee wallet balance; overdraft allowed (+50 bp) |
| Blocking Transfers | N/A | Never blocks user tx – applies fee markup on low balance |
| Layer | Notabene | RemiDe |
|---|---|---|
| Protocol Stack | TRP (Travel Rule Protocol) + OpenVASP/IVMS schemas | Go microservices + routing + fee ledger + IVMS-101 transport |
| On-Chain Anchoring | None | Daily Merkle root of KYC attestations on-chain (Polygon/IPFS) |
| Ledger Design | Not applicable | Redis + Postgres off-chain fee ledger; webhook-settled |
| API Footprint | mTLS REST; VASP lookups + payload transmission | /route, /travelRule/notify, /settle; chain-agnostic routing |
| Audit Trail | Message logs | Full JSON + partner ledger snapshot + CCTP attestation hash |