The Wallet Address Book allows Virtual Asset Service Providers (VASPs) to upload wallet addresses belonging to their users via the API, ensuring complete, secure, and timely data exchanges under Travel Rule requirements.

Benefits of wallet addresses upload to Sumsub

This service ensures 100% delivery of inbound Travel Rule data exchanges through the Wallet Address Book from VASPs in Sumsub's network, as not all wallet addresses can be discovered by blockchain analytics providers due to a number of reasons.

Adding wallet addresses to the wallet address book is the first step in automating your Travel Rule responses from other VASPs. This, coupled with linking wallet addresses to applicants sets your VASP up for a fully automated workflow.

This reduces operational costs by eliminating the need for third-party blockchain analytics providers (such as Crystal Intelligence, Merkle Science, Chainalysis, and so on) to attribute wallet addresses to counterparty VASPs.

For security reasons, you may choose to hash your addresses.

Ensure wallet address ownership

Each time you create a Travel Rule data exchange transaction, Sumsub extracts the wallet address/hash and tries to match it against the Wallet Address Book. In this case, Sumsub is checking for wallet addresses submitted from other VASPs.

If the match is found, it returns all the available data, which includes the information about the VASP the wallet belongs to, its local entity, and more.

For example, our blockchain analytics partners may provide only a general answer about the wallet owner, such as BitPanda. The Sumsub Wallet Address Book allows wallets to be attributed specifically to Bitpanda entities, such as Bitpanda Germany, Bitpanda Custody, and so on.

• In case of the CODE and GTR protocols, this procedure is a necessary part of the inbound data exchange transaction delivery and ensures the subsequent performance of the blockchain transaction.
• In case of the Sumsub protocol, the Wallet Address Book helps to streamline the data exchange transaction processing. With this feature enabled, you do not have to confirm that the wallet address belongs to you with each new data exchange transaction.

📘

Note

You can speed up the confirmation process for the Sumsub protocol and ensure the correct data exchange for the CODE and GTR protocols by following the Automation instructions given in this article.

Import wallet addresses

The Wallet Address Book is free and enabled on your VASP account upon creation. You can submit up to 10.000 wallet addresses via one API call. All the data that you share is encrypted/hashed in transit and/or at rest. We recommend that you implement the logic that submits wallet addresses every couple of hours.

When submitting the wallet data, you can send:

• Only walletAddress, if you are ready to share the wallet addresses with Sumsub.
• Only walletAddressHash, if you do not want to share direct wallet addresses for security reasons. Generate a SHA-256 hash of a wallet address (new Sha256Hash(walletAddress).toBase64()).
• Both walletAddressHash and walletAddress, so you can check if your hashing function is the same as in Sumsub (in case the functions differ, the response returns an error).

Use this API method as the following example demonstrates to import the wallet addresses of your users for further transaction processing:

curl -X POST \
     `https://api.sumsub.com/resources/kyt/walletAddress/import` \
     -H 'content-type: application/json' \
     -d '
        [
          {
              "walletAddress": "1njrRcKQtfjjLuQ",
              "asset": "USDT",
              "chain": "ETH"
            },
            {
              "walletAddressHash": "04c4926a21184665ef890493cd3c67a919f868724fc44adb933b911234567890",
              "asset": "USDT",
              "chain": "ETH"
            }
        ]
      '