Unsupported Assets

If you try to create a travel rule message with an asset that is not listed in the Notabene asset service, you will get the following error message:

{
    "err": {
        "code": 400,
        "message": "Notabene is currently not supporting this asset: UNSUPPORTED-COIN-NAME-HERE. Please contact Notabene customer service to request it. Additional information: assets-service-unsupported",
        "name": "NotabeneCryptoAssetNotAvailable"
    }
}

You can request Notabene to add the asset, but for that to happen, it has to have a price on Coingecko or CoinMarketCap. If an asset is not listed in Coingecko or CoinMarketCap or is listed but doesn't have any pricing information available, you can still use it in a travel rule message. However, you would also need to add the parameter customAssetPrice to tell us the value of one coin of the asset.

Notabene will then use that information when calculating the total FIAT value of the transfer, which is then compared against the travel rule threshold in your jurisdiction.

📘

Note!

1. Custom assets not in the Notabene asset service are NOT supported for screening against blockchain analytics through Notabene.
   1. This means any rules you set that include a result from your provider will not work and require transactions with these assets to be approved manually.
2. If an asset is listed on the asset service and you still provide a customAssetPrice, your price will have priority and be used.

The customAssetPrice object

// new notation (use this one)
"transactionAsset": "CHRISCOIN",
"transactionAmount": "12340000000000",
"customAssetPrice": {
    "decimals": 10,
    "price": 1.0,
    "currency": "USD" // can also be "EUR"
},

// old notation (still maintained for backwards compatibility)
"transactionAsset": "CHRISCOIN",
"transactionAmount": "12340000000000",
"customAssetPrice": {
    "priceUSD": 1.0,
    "decimals": 10
},

In the above example, you're saying that 1 CHRISCOIN is worth 1 USD and that the transactionAmount is written with 10 decimals:

1234(0000000000) x 1 USD = 1234 USD

Using customAssetPrice in txValidateFull and txCreate

You can validate a transfer for un-supported assets by passing the following to txValidateFull or txCreate

{
    "transactionRef": "{{$randomUUID}}",
    "transactionAsset": "CHRISCOIN",
    "transactionAmount": "12340000000000",
    "customAssetPrice": {
    "priceUSD": 1,
    "decimals": 10
    },
    "originatorVASPdid": "{{vaspDID}}",
    "beneficiaryVASPdid": "{{vaspDIDee}}",
    "beneficiaryRef": "[email protected]",
    "originatorRef": "[email protected]",
    "transactionBlockchainInfo": {
        "origin": "{{$randomBitcoin}}",
        "destination": "{{$randomBitcoin}}"
    },
  ....
}

Custom asset price and txNotify

You can call txNotify for an unlisted asset by passing the fields below.

{
    "txHash": "{{txHash}}",
    "transactionAmount": "1000000000000",
    "transactionAsset": "CHRISCOIN",
    "customAssetPrice": {
        "priceUSD": 1,
        "decimals": 10
    },
    "destination": "{{$randomBitcoin}}",
    "origin": "{{$randomBitcoin}}",
    "beneficiaryVASPdid": "{{vaspDID}}"
}

Requesting new coins to be added

Please use the following link to request new coins and we will do our best to add the asset within 5 business days.

You can look here to see what coins are pending or merged already.