❗️ These API keys should never be stored on your client-side application, always store them securely on your applications backend, following security best practices.
UserId
body param. The UserId
is a unique ID representing the end user. This identifier is a map to reference which customers you are logging in through Mesh Link.
IntegrationId
param.
The IntegrationId
of the integration you wish to connect can be obtained by calling the Retrieve the list of all available integrations. endpoint and referencing the id
field.
IntegrationId
param.
The IntegrationId
of the integration you wish to connect can be obtained by calling the Retrieve the list of all available integrations. endpoint and referencing the id
field.
toAddresses
object items, but the most streamlined way for users to transfer assets is to include a single token/network/address combo. Please remember that for each item in the ‘toAddresses’ array, you must provide the Mesh UID for the network to which you are sending the supported token. The comprehensive list of tokens, networks and integrations that can Mesh supports can be found here: Tokens | Networks | Integrations
👍 If only one destination address is provided, the Link UI skips the ‘Select asset’ and ‘Select network’ screens to streamline the user experience.
toAddresses
object items as needed to enable your users to perform transfers. Each item, represents the symbol they can transfer and the network it could be sent over. Please remember that for each item in the ‘toAddresses’ array, you must provide the Mesh UID for the network to which you are sending the supported token. The comprehensive list of tokens, networks and integrations that can Mesh supports can be found here: Tokens | Networks | Integrations
auth_token
when initializing the SDK.
accessTokens
Code ExampletransferDestinationTokens
The transferDestinationTokens
are used for crypto transfers flow. It is an alternative way of providing target addresses for crypto transfers by using previously obtained integration auth_tokens
.
The type of the transferDestinationTokens
parameter is an array of IntegrationAccessToken
.
See the type definition on our GitHub.
toAddresses
array to the LinkToken endpoint, to indicate that you wish to use the transfers workflow.
AmountInFiat
parameter when calling the LinkToken endpoint
By providing a unique TransactionID
, you’ll be to map a payments to a specific identifier, similar to an order number.
👍 If AmountInFiat
is included and only a single network/token/address combo is included, Link will skip directly to the preview page, making even more streamlined for a user to complete their transfer.
ClientFee
field to the above JSON object examples. This fee should only be used for Payments (when the transfer destination is an address owned by your company), and not for Deposits (when the transfer destination is an address owned by the end-user).
A percentage fee (input as a ratio, eg. 0.02500 = 2.500%) added onto your users’ gross transfer to your company.
This will override any default fee entered in your Mesh dashboard for an individual transaction.