...
| Name | Description | ||
|---|---|---|---|
| Network Type | Select the network to perform transactions on:
"Mainnet" uses assets with actual monetary value. Please use "Testnet" for testing purposes. | ||
| Backend Service | Select the backend service you wish to use to execute your blockchain queries/transactions with:
| ||
| Blockfrost Project Key | This property will only appear when Backend Service is Blockfrost. Paste in your generated mainnet/testnet project API key. See blockfrost.io. | GraphQL Endpoint URL | This property will only appear when Backend Service is Custom GraphQL API. Paste in the GraphQL endpoint URL of your choice. |
Transaction Details
| Name | Description | |||||
|---|---|---|---|---|---|---|
| Form | Select a form to retrieve transaction data from. All fields from the selected form will be made available for field mapping in the sections below. | |||||
| Asset Configuration | ||||||
| Payment Type | Select the asset type to transfer:
| |||||
| Policy ID | This property will only appear when Payment Type is Native Token or NFT. The policy ID that minted the token. Can use a Hash Variable or simply hardcoded. | |||||
| Asset Name | This property will only appear when Payment Type is Native Token or NFT. The asset name of the token, e.g.: MyTestToken, My-First-NFT. Typically a Hash Variable is used here. | |||||
| Payment Configuration | ||||||
| Sender Address | Address to send assets from. | |||||
| Sender Account Mnemonic Phrase | This is the sender's account secret key required in order to perform actions with the sender's account. Only accepts Hash Variable that points to the sender's encrypted stored mnemonic phrase.
| |||||
| Enable Multiple Receivers | This property will only appear when Payment Type is ADA or Native Token. When this option is checked, you can pull multiple rows of data from a datalist to send assets to multiple receivers with their respective amounts. With this feature, all the receivers are compiled into a single transaction and executed atomically. Binder To Retrieve Receivers property will appear for you to select a datalist binder and then configure the datalist binder accordingly. After then, the Binder Column Mapping (Multiple Receivers Mode) configuration tab will be available for you to map columns accordingly. | |||||
| Binder To Retrieve Receivers | This property will only appear when Enable Multiple Receivers is checked. Select a datalist binder and configure the selected binder accordingly in subsequent configuration tab(s). | |||||
| Receiver Address | This property will only appear when Enable Multiple Receivers is not checked. Address to send assets to. | |||||
| Amount To Send | This property will only appear when Enable Multiple Receivers is not checked. Amount of tokens to send. Amount can only contain max 6 decimal places. This rule applies for both ADA and native tokens. | |||||
| Additional Metadata | ||||||
| Metadata | Fields available here depends on the Form selected. Select the field(s) you wish to embed into the transaction metadata. Written transaction metadata follows the CIP-20 standard. To learn more about transaction metadata, see https://developers.cardano.org/docs/transaction-metadata/.
| |||||
...