Optional
address?: stringAsset symbol indicating which asset this account is managing. BTC or ETH are obvious examples, but there are thousands of possible symbols. In case of coins (ERC20 and alike) use COIN.BLOCKCHAIN
syntax, such as USDC.ETH or USDC.SOL to indicate that USDC on Ethereum or USDC on Solana is required. To get a list of all allowed values, send a CreateAssetAccount
request with the assetSymbol
field empty.
Optional
authorizations?: AssetAccountAuthorization[]Optional
externalField can be used if entity is created in external (customer’s) system first. This way the external id can be attached to identify entity from Dfns’s data store.
Custom name that can be added for an account.
Indicates id of the Organisation, such as usually a customer, or sub-devision, sub-tenant, and others.
Optional
publicPublicKey
which is used by AssetAccount
. Usually this is used to derive addresses on a given blockchain network.
Alternatively can be used to verify signatures produced by the platform.
Optional
publicIndicates whether account is ready to be used.
Optional
tags?: Tag[]Multiple tags can be attached to an entity to categorise or otherwise mark it. For example tags could indicate risk (High, Medium, Low), departments (Trading, Sales, IT), purpose (Treasury, Hot, Deposits), and jurisdictions (US, EU, DE).
Multiple tags can be attached to same entity.
Generated using TypeDoc
Blockchain address for a chosen Blockchain network.