TransferRequestDto

Data structure for performing a native token transfer.

Signature:

{
  walletId! : string;
  to! : string;
  secretType! : SecretType;
  data! : string;
  value! : BigDecimal;
  chainSpecificFields? : object;
}

Parameters:

Parameter	Required	Type	Description
Parameter	Required	Type	Description
`walletId`	`True`	`String`	ID of the wallet one wants to sign with.
`to`	`True`	`String`	Destination address of the transaction. Can be an address or an email address.
`secretType`	`True`	`SecretType`	Chain the transaction will be executed on.
`data`	`False`	`String`	Data you want to send. This field will be ignored when building a token transaction request
`value`	`True`	`Number`	Token value that should be transferred.
`ChainSpecificFields`	`False`	`Object`	This field can be used to pass properties specific to a chain. More info: Chain specific fields

📘
🧙 You don’t have to take into account the number of decimals for different tokens, Venly handles that for you.
Example: If a token has 18 decimals and you want to transfer 1 token, provide the value 1. Venly will translate this to the correct non-decimal value (1 * 10e18).

Example:

Plain

{
  "walletsId" : "cdc4c08a-b8fa-4e4c-z5a2-92c87b80f174",
  "to" : "0xdc71b72db51e227e65a45004ab2798d31e8934c9",
  "secretType" : "VECHAIN",
  "data" : "0x",
  "value" : 1.15
}

With Hedera Memo

{
    "secretType": "HEDERA",
    "walletId": "d1e091d7-0fab-4f46-8afd-ad31f1e735d7",
    "to": "0.0.2278508",
    "value": "0.0314",
    "chainSpecificFields": {
        "transactionMemo": "0.0.2810009"
    }
}

Function Types

📘

executeTransfer

chainSpecificFields

Updated 12 months ago