Signing a payment request
We recommend using our helper to construct the required signatures as described in Generate signed data. However, if that is not possible, you can follow this guide to do it manually.
The data you will need to construct your signature is as follows:
Property | Type | Description | Example |
---|---|---|---|
address | String | The user’s address that receives the token/NFT. It will also act as a fallback address if a smart contract can’t be executed. In case of fallback, we will transfer | 0x00000000000000000000000000000 |
commodity | String | Cryptocurrency which should be sent to the smart contract, see Supported coins and blockchains |
|
network | String | Network for the cryptocurrency, see Supported coins and blockchains |
|
commodity_amount | Number | Amount of cryptocurrency necessary for executing the given smart contract. | 0.03 (maximum 8 decimal places) |
sc_address | String | The address of the smart contract. | 0x00000000000000000000000000000 |
sc_input_data | String | Input data used for the smart contract execution in hex format. For Tezos, this must be Michelson code passed as JSON transformed into hex format. See Forming input data. | 0x40c10f1900000000000000000000000 |
Alternate implementation
Use the following implementation if you are importing scripts via CDNs and Buffer is not available for use.
Updated about 1 month ago