Connector · Self-hosted Travel Rule software

21 Analytics, running on your servers.

How our compliance reporting module uses 21 Analytics, Travel Rule software that runs in your own infrastructure: what it does with each transfer, where the data stays, and how we get you live.

Website
21analytics.co
Modules
Compliance reporting
Contract
We help you get it

Who 21 Analytics is

21 Analytics is a Swiss company based in Zug that builds 21 Travel Rule, compliance software that runs entirely on its clients' own servers. The company does not see its clients' data: transfers, customer details and proofs are stored in the clients' own databases.

It exchanges Travel Rule data over the open TRP protocol and the TRUST network, and it created AOPP, a protocol that lets customers prove they own a self-hosted wallet with a signature from that wallet. Crypto exchanges and other providers that want full control over their Travel Rule data use it, which is why it is one of the Travel Rule providers our compliance reporting module connects to.

What it does in your platform

  • Compliance reporting

    Carries the Travel Rule data for your customers' crypto transfers from software that runs in your own infrastructure, so customer details are stored in your databases, not with a software vendor. Incoming data is checked before funds are credited, and proofs that customers own their self-hosted wallets are kept with their transfers.

How the connection works

21 Travel Rule runs next to your platform, in your infrastructure, and the compliance reporting module talks to it through its GraphQL API. Counterparties reach it directly, over TRP or the TRUST network.

  1. Another exchange sends crypto

    The sending exchange delivers the Travel Rule data for the transfer to your 21 Travel Rule instance, over TRP or TRUST, and it is stored in your own database.

  2. The module checks it

    It reads the transfer through the GraphQL API and matches the recipient against your customer, under the rules your compliance team set.

  3. Your team reviews exceptions

    A mismatch or missing data goes to your team in the backoffice, where the transfer is accepted or rejected.

  4. The funds are credited

    Once the data checks out, the deposit is credited to your customer, and the decision is recorded next to it.

  5. Withdrawals go the other way

    Outgoing transfers carry your customer's data to the other exchange the same way. A withdrawal to a self-hosted wallet can carry the customer's proof of ownership: a signature through AOPP, a small test transfer or a visual proof.

Next to other providers

21 Analytics speaks TRP and the TRUST network itself, from your own servers. TRP is open: any provider that implements it, hosted or self-hosted, can exchange data with your instance.

The Travel Rule checks, the review in the backoffice and the records belong to the module, not to 21 Analytics. Moving to another provider later does not change your apps, and the data already exchanged stays in your own database.

When 21 Analytics fits best

A strong fit when

  • Travel Rule data must stay on your own servers, for your regulator, your auditors or your own policy.
  • Your customers often withdraw to self-hosted wallets and need to prove they own them.
  • Your counterparties exchange Travel Rule data over TRP or the TRUST network.

Also worth a look

  • A hosted provider such as Notabene, when you would rather not run Travel Rule software yourself.
  • A direct TRP connection from the platform, when TRP alone covers your counterparties.

How we get you live

  • The contract

    We help you get your 21 Analytics contract and software licence in place, set up for your markets.

  • The deployment

    We deploy 21 Travel Rule in your infrastructure next to your platform, with its database, its endpoints for counterparties and its compliance dashboard.

  • The keys

    API credentials, certificates and database credentials stay in your platform's secrets, and only the module talks to the GraphQL API.

  • A full test run

    Before go-live we run transfers end to end, from a test customer in 21 Travel Rule's address book to a decision in the backoffice.

Questions

Asked about this connector.

How do we get started with 21 Analytics?

Talk to us. We help you get the 21 Analytics contract in place, deploy the software in your infrastructure and connect it to your platform, then run test transfers end to end before your first real customer.

Does 21 Analytics see our customers' data?

No. The software runs on your servers and stores transfers, customer details and wallet proofs in your own databases, and 21 Analytics states that it never has access to them.

Which counterparties can we reach?

Those that exchange Travel Rule data over TRP or the TRUST network, which 21 Travel Rule supports directly. TRP is open, so hosted and self-hosted providers alike can implement it.

How do customers prove they own a self-hosted wallet?

With a signature from the wallet through AOPP, a protocol 21 Analytics created, or with a small test transfer or a visual proof when the wallet does not support it.

Start your project

Tell us the idea. We'll show you the platform.

One call is enough to map your product to the modules that already exist.

  • Response in under one business day
  • NDA on request
  • No obligation
What are you building?