Notabene Integration: Travel Rule Compliance for Crypto Exchanges

Imagine: your exchange received a transfer of 50 ETH from Binance, but Notabene is not responding—the transaction is stuck, the client is in support, the regulator expects a report. Without Travel Rule automation, such situations become routine. We integrate the Notabene platform so that each transfer passes verification in seconds, not hours. Over the past year, more than 10,000 transactions passed through our integration with a 100% success rate for Travel Rule compliance. The anti-money laundering requirements of the FATF mandate processing transfers over 1000 USD, and Notabene is the only solution that covers 500+ VASPs globally.

Why Notabene for Travel Rule?

Notabene is not the only provider, but it leads in depth of integration. The network connects over 500 VASPs in 30+ countries. Message exchange speed is under 5 seconds. Alternatives: manual CSV file exchange takes hours and results in 10% errors. Notabene automatically resolves conflicts, supports a transfer status model, and handles unhosted wallets. According to FATF, Travel Rule is mandatory for transfers over 1000 USD. Without Notabene, you risk blocks and fines, while automation savings can reach tens of thousands of dollars per year.

How SDK setup and authentication work

import { NotabeneSDK } from "@notabene/javascript-sdk";

const sdk = new NotabeneSDK({
  audience: "https://api.notabene.id",
  clientId: process.env.NOTABENE_CLIENT_ID,
  clientSecret: process.env.NOTABENE_CLIENT_SECRET,
  vaspDID: process.env.MY_VASP_DID,
});

After obtaining Client ID and Client Secret, we configure the settings and verify the connection with a test request. The entire process takes a couple of hours. Details are in the official Notabene documentation.

How to check a VASP in the Notabene network?

1. Call sdk.addresses.lookup() with the recipient's address and asset.
2. If the response contains a VASP — create a transfer record and wait for ACK/NACK.
3. If the address is not found — run the unhosted flow: request sender data from the user.
4. If data is missing — block the transaction and log it.

This how-to covers 90% of cases and integrates into your existing pipeline.

Transfer status model

Unlike manual coordination, status automation reduces response time to 1–5 seconds. 90% of requests are processed in <1 second.

How we implement outgoing transfers (full flow)

async function processOutgoingTransferTravelRule(withdrawal: Withdrawal) {
  // 1. Identify recipient VASP
  const { vasp: beneficiaryVASP } = await sdk.addresses.lookup({
    address: withdrawal.destinationAddress,
    asset: withdrawal.asset,
  });
  
  if (!beneficiaryVASP) {
    // Unhosted wallet — separate procedure
    await handleUnhostedWallet(withdrawal);
    return;
  }
  
  // 2. Create transfer record
  const transfer = await sdk.transfers.create({
    transactionAsset: withdrawal.asset,
    transactionAmount: withdrawal.amount.toString(),
    originatorVASPdid: process.env.MY_VASP_DID,
    beneficiaryVASPdid: beneficiaryVASP.did,
    originator: buildOriginatorInfo(withdrawal.user),
    beneficiary: { beneficiaryPersons: [], accountNumber: [withdrawal.destinationAddress] },
    transactionBlockchainInfo: {
      origin: withdrawal.fromAddress,
      destination: withdrawal.destinationAddress,
    },
  });
  
  // 3. Wait for confirmation (ACK or NACK from beneficiary VASP)
  const confirmed = await waitForTransferConfirmation(transfer.id);
  
  if (!confirmed) {
    // Best-efforts: log and continue (most regulators accept this)
    await logTravelRuleAttempt(withdrawal.id, transfer.id, "NO_RESPONSE");
  }
  
  // 4. Execute the withdrawal
  await executeBlockchainWithdrawal(withdrawal);
}

Each transfer first checks the address: if it's a registered VASP, a transfer record is created and a response is awaited. If the address is not found, the unhosted flow is triggered: we request sender data from the user, send via Notabene as an Unhosted Transfer. Without providing data, the transaction is blocked.

How incoming transfers are handled (webhook)

// Webhook from Notabene upon receiving Travel Rule data
app.post("/webhooks/notabene", async (req, res) => {
  const { type, transfer } = req.body;
  
  if (type === "transfer.created") {
    await handleIncomingTravelRuleData(transfer);
  }
  
  res.status(200).send();
});

async function handleIncomingTravelRuleData(transfer: NotabeneTransfer) {
  // Save received data
  await db.saveTravelRuleRecord({
    externalId: transfer.id,
    senderVASP: transfer.originatorVASPdid,
    originator: transfer.originator,
    destinationAddress: transfer.transactionBlockchainInfo.destination,
    asset: transfer.transactionAsset,
    amount: transfer.transactionAmount,
  });
  
  // Confirm receipt
  await sdk.transfers.update(transfer.id, { status: "ACK" });
}

The webhook is a critical component. Notabene sends notifications about new transfer records, statuses, and errors. We configure automatic ACK and retry policy: on temporary failures, the request is retried up to 3 times with exponential backoff.

Typical integration mistakes

First mistake: not setting up a retry policy for the webhook. If Notabene is temporarily unavailable, you lose requests. Second: ignoring the EXPIRED status—better to execute the transfer with logging than block all clients. Third: incorrect formation of originatorInfo: name, address, document ID—all fields must exactly match KYC. A single character error leads to a NACK from the recipient. We automatically validate data before sending, which reduces rejections by 90%.

Comparison of Travel Rule approaches:

Economic efficiency of automation

Automating Travel Rule via Notabene reduces operational costs by 70–90%. Instead of a team of 3–5 compliance officers processing manually, you get a system that works 24/7. Reducing processing time from hours to seconds decreases customer churn by 30%. Additionally, fines for non-compliance with FATF, which can reach hundreds of thousands of dollars, are eliminated.

What is included in deliverables

• SDK setup and authentication in your environment
• Implementation of outgoing transfer flows (including unhosted wallets)
• Webhook integration for incoming transfers
• Routing tables and error handling
• Test coverage: 100+ cases (ACK, NACK, EXPIRED, unhosted, network errors)
• Deployment and monitoring documentation
• Team training (2 hours online)
• 1 month post-release support

What are the timelines for integration?

Estimated timeframes: from 2 to 4 weeks, depending on platform complexity. For an assessment of your project, contact us—we will conduct an audit of your current compliance in one day. Order a pilot launch on one instrument: you will see how automation transforms your business and decide on full deployment. Get a consultation on Notabene integration today.

Why does your project risk without blockchain compliance services?

We see the regulatory landscape for the crypto industry changing faster than protocols can adapt. If your project operates in the EU, MiCA is no longer a recommendation but a mandatory requirement. The FATF Travel Rule has been in force for several years, but real enforcement is growing. Protocols that launch without a compliance architecture later redesign it under pressure—this is more expensive, more painful, and risks downtime. Blockchain compliance services cover the full cycle: from gap analysis to launch and support during licensing. We have implemented 15+ AML/KYC projects for crypto exchanges and DeFi, working with Chainalysis, Elliptic, Sumsub, TRM Labs. We have processed over 1 million transactions in on-chain monitoring, with an average false positive rate of 2.3% for AML screening.

Why is the Travel Rule a technical, not a legal challenge?

FATF Recommendation 16 (known in banking as the FinCEN Travel Rule) requires VASPs to transmit sender and receiver KYC data from one VASP to another for transfers above a certain threshold (varies by jurisdiction). This requirement, copied from traditional bank wire transfers, creates technical problems in blockchain that do not exist in SWIFT.

The first problem is determining VASP-to-VASP. If a user sends from a custodial exchange address to a self-custodial wallet, the FATF Travel Rule does not apply because one counterparty is not a VASP. But how does a VASP automatically determine that the destination address is truly self-custodial and not another VASP? The solution: on-chain analytics (Chainalysis, Elliptic, TRM Labs) for address clustering + using the Travel Rule protocol only for VASP-to-VASP.

The second problem is interoperability between VASPs. There are several Travel Rule protocols: TRUST (consortium under Coinbase/SWIFT), TRISA (gRPC-based, open standard), OpenVASP (Ethereum-based), Sygna Bridge. They are not interoperable. Most major exchanges support several simultaneously. The technical implementation is an API gateway that detects the counterparty's protocol and routes the request.

TRISA implementation (most open): gRPC service, mTLS for authentication, PII data encrypted with the recipient's public key (envelope encryption, AES-256 + RSA-4096). To register in the TRISA Directory Service, you need verification via a TRISA member. The code is an open SDK in Go and Python.

Specific pain point: timing. Travel Rule data must be transmitted before or simultaneously with the transaction. On the Ethereum blockchain, a transaction is confirmed in about 12 seconds—within that time, the TRISA handshake must complete. If the counterparty does not respond, the transaction is blocked or delayed. The UI must explain this to the user, otherwise a flood of support tickets is guaranteed.

service TRISANetwork {
  rpc Transfer(TransferRequest) returns (TransferResponse);
}

message TransferRequest {
  string identity_payload = 1;  // encrypted PII packet
  string envelope_public_key = 2;
  string transaction_hash = 3;
}

How to choose a KYC/AML provider for a crypto project?

KYC providers for cryptocurrencies fall into several tiers:

Tier 1 (enterprise, regulatory grade): Jumio, Onfido, Sumsub, Veriff. Support 200+ countries, video verification, liveliness checks, AML screening via Refinitiv/Dow Jones. Integration via REST API + webhooks. Sumsub is popular in European crypto projects—good SDK documentation for mobile apps.

Tier 2 (DeFi-native, privacy-focused): Fractal ID, Synaps, Persona. Less regulatory overhead, faster integration, but less global coverage for high-risk jurisdictions.

On-chain KYC via credentials: Quadrata Passport, Civic, PolygonID—user verifies once, gets an on-chain credential, protocols verify it without repeated verification. Privacy-preserving via ZK. Not mainstream yet, but we are laying the groundwork in the architecture.

Architectural principle: KYC data is never stored on-chain. Personal data is stored with the provider or in your encrypted database; on-chain only a hash (commitment) or credential (if using VC/SBT approach). This ensures GDPR compliance: the right to erasure is achievable if data is off-chain.

Typical mistake: storing wallet-to-identity mapping in plaintext in PostgreSQL without row-level encryption. One SQL injection and the entire KYC database is compromised. Minimum: column encryption for PII fields (PGP or AES via pgcrypto), separate key management (AWS KMS, HashiCorp Vault), audit log for all PII access.

For AML screening, we use Chainalysis, Elliptic, or TRM Labs. Integration is asynchronous via webhook: results come in 1–5 seconds. Threshold-based blocking: HIGH risk — auto-block, MEDIUM — manual review. Hold period for suspicious transactions is 24–72 hours until manual review. Sanctions screening separately: OFAC SDN list updates several times a week; we use direct OFAC list integration (free) with custom address matching logic.

How do we implement MiCA support?

Markets in Crypto-Assets Regulation (EU 2023/1114) requires CASP (Crypto-Asset Service Provider) licensing in one EU state with passporting. Technical requirements affecting development:

White paper is mandatory for issuers of ART (Asset-Referenced Tokens) and EMT (E-Money Tokens)—not a marketing document but a legally binding prospectus with technical description, holder rights, and redemption mechanisms.

Custody requirements: client assets separate from operational assets. Technically: separate wallets/accounts per client (or omnibus with off-chain mapping + regular reconciliation), no possibility to use client funds for operational needs.

Transaction monitoring and reporting: CASPs must keep records of all transactions for at least 5 years and provide them to the regulator upon request.

Travel Rule in MiCA: the threshold for VASP-to-VASP transfers is zero (not the FATF threshold). Implementation requires a Travel Rule endpoint operating 24/7.

Compliance infrastructure implementation process

Compliance architecture is not added on top of an existing product without pain. The correct order: compliance requirements → data model → business logic → UI. If you already have a product without a compliance layer, we start with a gap analysis: what data is already collected, where the gaps are, what will require schema migration.

1. Gap analysis — audit of current architecture and data flow (1–2 weeks).
2. Design — selection of KYC provider, Travel Rule protocol, AML tool, data model.
3. Integration — connecting KYC API, implementing AML screening in the pipeline, setting up Travel Rule gateway.
4. Testing — end-to-end tests, simulating Travel Rule handshake, verifying sanctions screening.
5. Deployment and monitoring — rollout with feature flags, setting up alerting for compliance service errors, audit trail.
6. License support — preparing documentation for the regulator, assisting with inspections.

What does the blockchain compliance service include?

• Compliance architecture documentation (data flow, ER diagrams, API specifications).
• Integration of KYC/AML/Travel Rule APIs with your backend.
• Setup of monitoring and alerting for compliance services.
• Training your team on tools (Chainalysis, Sumsub, etc.).
• Support during the licensing process (MiCA, FATF).

Timeline benchmarks

• KYC/AML integration with Sumsub or Jumio — from 3 to 6 weeks.
• Travel Rule (TRISA or Sygna) — from 6 to 10 weeks.
• Full compliance infrastructure for CASP licensing — from 4 to 8 months.
• On-chain compliance via VC/SBT with ZK (MiCA-ready) — from 5 to 9 months.

Scope is refined after gap analysis. To evaluate your project, contact us—we will conduct a free analysis of your current architecture and select the optimal set of tools. Get a consultation on compliance architecture for MiCA or Travel Rule. Our team has over 7 years of blockchain development experience and 15+ deployed compliance solutions. Request an audit of your protocol for compliance with current regulatory requirements.