Match-Trade

Integrated systems

Crypto deposit flow

Deposit Request

Callbacks

Withdrawal Request

Cryptocurrency details

Callback signature generation

Signature

Onchain Fee

Match2pay

match2pay-v2

Staging

Sandbox

<p class="slate-p " ><strong class="slate-bold">List of CRMs already integrated with our Crypto Gateway</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Utip</div></li><li class="slate-li " ><div style="position:relative">FX Back Office</div></li><li class="slate-li " ><div style="position:relative">Skale</div></li><li class="slate-li " ><div style="position:relative">Trade Smarter</div></li><li class="slate-li " ><div style="position:relative">Kenmore design</div></li><li class="slate-li " ><div style="position:relative">TradeSoft</div></li><li class="slate-li " ><div style="position:relative">Nullpoint</div></li><li class="slate-li " ><div style="position:relative">Plugit</div></li><li class="slate-li " ><div style="position:relative">Axis (Broctagon)</div></li><li class="slate-li " ><div style="position:relative">Reltrix</div></li><li class="slate-li " ><div style="position:relative">Datalyst</div></li><li class="slate-li " ><div style="position:relative">FTT (Fair Trading Technology)</div></li><li class="slate-li " ><div style="position:relative">Leverate</div></li><li class="slate-li " ><div style="position:relative">Pheasantech</div></li><li class="slate-li " ><div style="position:relative">UpTrader</div></li><li class="slate-li " ><div style="position:relative">Syntellicore (Dynamic Works)</div></li><li class="slate-li " ><div style="position:relative">Delasport</div></li></ul><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">List of payment cashiers already integrated with our Crypto Gateway</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="https://www.paytiko.com/" target="_blank">Paytiko</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://praxis.tech/" target="_blank">Praxis</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://bridgerpay.com/" target="_blank">BridgerPay</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://akurateco.com/" target="_blank">Akurateco</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://corefy.com/" target="_blank">Corefy</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://payprocc.com/" target="">PayProcc</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://paymaxis.com/" target="">Paymaxis</a></div></li><li class="slate-li " ><div style="position:relative"><a href="https://pay.binance.com/en" target="">Binance Pay</a></div></li></ul><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">List of supported wallets (coming soon)</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Trust Wallet</div></li><li class="slate-li " ><div style="position:relative">MetaMask</div></li><li class="slate-li " ><div style="position:relative">Binance Wallet</div></li><li class="slate-li " ><div style="position:relative">OKX Wallet</div></li><li class="slate-li " ><div style="position:relative">Bitget Wallet</div></li><li class="slate-li " ><div style="position:relative">TokenPocket</div></li><li class="slate-li " ><div style="position:relative">1inch Wallet</div></li><li class="slate-li " ><div style="position:relative">Best Wallet</div></li></ul><p class="slate-p " >  And many more...</p><p class="slate-p " ></p><p class="slate-p " ></p>

List of CRMs already integrated with our Crypto Gateway

List of payment cashiers already integrated with our Crypto Gateway

<div class="slate-div"><p class="slate-p " ></p><div style="text-align:left"><figure ><div style="display:inline-block"><img src="https://theneo-prod-public.s3.amazonaws.com/images-1698752387676.png" alt="" style="
              width:2643px;
	            height:1099px;
	            aspect-ratio:2643 / 1099"
         /></div></figure></div><h2 class="slate-h2 " >
Dynamic single-use deposit flow:</h2><div class="slate-div"><h4 class="slate-h4 " ><strong class="slate-bold">a unique wallet address is generated per deposit request and expires after a time window. </strong>
</h4></div><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">The client requests a deposit in the broker’s Client Office.</div></li><li class="slate-li " ><div style="position:relative">Client Office sends the request to the Match2Pay.</div></li><li class="slate-li " ><div style="position:relative">Processing request, generating individual crypto deposit wallet address.</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">The Match2Pay system processes the request and generates a unique cryptocurrency deposit wallet address for this individual deposit transaction.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">IMPORTANT</strong>: Wallet addresses must be newly generated each time a client initiates a new deposit. Wallet addresses are <strong class="slate-bold">single-use only</strong>; if a client deposits to a previously used address at a later time, they risk losing their funds. </div></li></ul></li><li class="slate-li " ><div style="position:relative">Displaying the Match2Pay Payment Page to the Client.</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">We strongly recommend that the broker&apos;s Client Office redirects the client to the Match2Pay payment page or displays it in an Iframe.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">IMPORTANT</strong>: Generated wallet address has an expiration time. Currently, this is set to 2 hours for Bitcoin (BTC) deposits and 30 minutes for all other cryptocurrencies. <strong class="slate-bold">Clients must ensure their deposit is made to the provided address within this specific time window for the transaction to be processed successfully</strong>. <strong class="slate-bold">A 12-hour post-expiration grace period applies, deposits confirmed on-chain within this window will still be accepted and processed.</strong></div></li><li class="slate-li " ><div style="position:relative">If the client has a cryptocurrency, they can send this cryptocurrency to this individual deposit wallet address.</div></li></ul></li><li class="slate-li " ><div style="position:relative">The transaction is being processed by the blockchain.</div></li><li class="slate-li " ><div style="position:relative">After receiving the information from the blockchain about a successfully processed transaction, the cryptocurrency is being booked on the deposit wallet address.</div></li><li class="slate-li " ><div style="position:relative">Converting the cryptocurrency to FIAT. The final amount is being added to the broker’s Match2Pay balance.</div></li><li class="slate-li " ><div style="position:relative">The amount from a callback is being booked on the client’s trading account.
<strong class="slate-bold">An important benefit of this solution is that, unlike the Static Wallet flow, there is no minimum fee applied to deposits.</strong>
If you are unable to ensure that a unique wallet address is generated for each client deposit, or if you cannot integrate our payment page, please contact Match2Pay support.</div></li></ol><h2 class="slate-h2 " >
Static wallet flow (set by default):</h2><h4 class="slate-h4 " >a reusable wallet address is assigned to a specific trading account; multiple deposits can be sent to the same address.
</h4><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">The client requests a deposit in the broker’s Client Office.</div></li><li class="slate-li " ><div style="position:relative">Client Office sends the request to the M2P.</div></li><li class="slate-li " ><div style="position:relative">Processing request, generating<strong class="slate-bold"> individual crypto deposit wallet address</strong>.</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">It is possible to assign generated wallet address to a particular trading account/client. Detailed guide can be found at the bottom.</div></li></ul></li><li class="slate-li " ><div style="position:relative">Returning generated crypto deposit wallet address on the payment page.</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">If the client has a cryptocurrency, they can send this cryptocurrency to this individual deposit wallet address.</div></li></ul></li><li class="slate-li " ><div style="position:relative">The transaction is being processed by the blockchain.</div></li><li class="slate-li " ><div style="position:relative">After receiving the information from the blockchain about a successfully processed transaction, the cryptocurrency is being booked on the deposit wallet address.</div></li><li class="slate-li " ><div style="position:relative">Converting the cryptocurrency to FIAT. The final amount is being added to the broker’s M2P balance.</div></li><li class="slate-li " ><div style="position:relative">The amount from a callback is being booked on the client’s trading account.</div></li></ol><p class="slate-p " ></p></div><div class="slate-div"><p class="slate-p " ><strong class="slate-bold">To correctly handle multiple deposits to the same static wallet address, your integration must be adapted as follows:</strong></p></div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Assign </strong><code class="slate-code"><strong class="slate-bold">payment_id</strong></code><strong class="slate-bold">: </strong>The <code class="slate-code">payment_id</code> generated with the first deposit request must be assigned and stored for a particular client account on your end.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Reuse </strong><code class="slate-code"><strong class="slate-bold">payment_id</strong></code><strong class="slate-bold">: </strong>For all future deposit requests from that same client (within the same crypto gateway), you must use/display the same, originally assigned <code class="slate-code">payment_id</code>.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Handle Callbacks Correctly: </strong>A single <code class="slate-code">payment_id</code> will be associated with multiple deposits. Each deposit will have a unique transaction hash. Your system must process incoming callbacks by checking for a new, unbooked transaction hash. If you receive a callback with a known <code class="slate-code">payment_id</code> but a new hash, the transaction should be booked.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Gateway-Specific Implementation: </strong>This integration logic must be applied separately for each crypto payment gateway you use.</div></li><li class="slate-li " ><div style="position:relative">Optional - Unlink Wallet: You can optionally add a feature to unlink the wallet address (<code class="slate-code">payment_id</code>) from a selected account. This would allow a new wallet address to be generated for that client in exceptional situations.</div></li></ul><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:293px;">Title</div><div style="width:611px;"></div><div style="width:544px;"></div></div><colgroup ><col style="width:293px"><col style="width:611px"><col style="width:544px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><div class="slate-div"><h3 class="slate-h3 " >Feature Key Differences</h3></div></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><div class="slate-div"><h3 class="slate-h3 " >Dynamic single-use deposit flow</h3></div></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><div class="slate-div"><h3 class="slate-h3 " >Static wallet flow</h3></div></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Wallet address generation</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Merchant’s Client Office requests a brand-new deposit address from Match2Pay</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Merchant’s Client Office generates a wallet address which they can save </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Wallet Address Usage </p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Single-use per transaction.</strong> Address is released back to the pool after successful completion or expiration</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Multi-use.</strong> Client can deposit to the same saved address multiple times </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Consequence of Reusing Old Address by Client</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Risk of fund loss.</strong> Client should NEVER reuse a previously generated wallet address. Once an address is returned to the pool it can be reassigned to a different client </p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >No risk, if client deposit to previously generated wallet address </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Address Expiration </p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Yes.</strong> 30 minutes (2 hours for Bitcoin) + an additional 12-hour window for deposit</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">No expiration time</strong> for the client&apos;s generated wallet address </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Minimum Deposit Fees</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">No minimal fees for deposits </strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Minimal deposit fees for: 
USDT ERC20 - 5$ ;
USDC ERC20 - 5$ ;
USDT TRC20 - 1$ ;
ETH - 0.001 ETH</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Payment Page Integration </p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Strongly recommended. </strong>Merchants&apos;s Client Office redirects to Match2Pay payment page or displays it in an Iframe on every deposit </p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Client can send funds directly to the wallet address saved to his trading account</p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p>

Title

<p class="slate-p " >This request is responsible for generating a new deposit wallet address for cryptocurrency transactions and providing a link to the payment page. It is a valuable tool for users who wish to make a deposit or payment using cryptocurrencies. </p><p class="slate-p " ><strong class="slate-bold">Important Informations:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">On live environment, there is a need to provide IP addresses to whitelist to be able to send requests</div></li><li class="slate-li " ><div style="position:relative">Under one paymentID there can be more than one transaction. </div></li></ul><p class="slate-p " ><strong class="slate-bold">Crypto selection flow (2-step payment page)</strong></p><p class="slate-p " >When a deposit request is created without a preselected cryptocurrency (<code class="slate-code">&quot;paymentCurrency&quot;</code><span style="color:rgb(0, 211, 189)"> </span>and <code class="slate-code">&quot;paymentGatewayName&quot;</code>), the user is redirected to a two-step payment page:</p><p class="slate-p " >Step I – Cryptocurrency selection – the user chooses which currency to use.</p><p class="slate-p " >Step II – Payment details – the user sees the address, amount and completes the deposit.</p><p class="slate-p " >The user may navigate back from Step II to Step I to select a different cryptocurrency.
In this case, a single deposit request can have multiple deposit addresses associated with it, one per selected cryptocurrency.</p><p class="slate-p " ><strong class="slate-bold">If paymentCurrency and payment is not provided, a 2-step payment page with cryptocurrency selection</strong> <strong class="slate-bold">will be generated:</strong></p><p class="slate-p " >If <code class="slate-code">&quot;paymentCurrency&quot;</code><span style="color:rgb(0, 211, 189)"> </span>and <code class="slate-code">&quot;paymentGatewayName&quot;</code> are not provided, a 2-step payment page will be generated:</p><p class="slate-p " >If <code class="slate-code">&quot;paymentCurrency&quot;</code><span style="color:rgb(0, 211, 189)"> </span>and <code class="slate-code">&quot;paymentGatewayName&quot;</code> are provided, the user is redirected directly to the payment details. </p><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Fixed wallet</strong></p><p class="slate-p " >By default, Match2Pay generates a new deposit address for each deposit request.
For gateways using the <code class="slate-code">&quot;CRYPTO_AGENT&quot;</code> method, it is possible to enable the fixed wallets feature on the gateway configuration level
<u class="slate-underline">When fixed wallets are enabled</u>:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Match2Pay checks if there is an existing deposit address for the given client email - <code class="slate-code">&quot;email&quot;</code>parameter.</div></li><li class="slate-li " ><div style="position:relative">If an address exists, the same deposit address is returned.</div></li><li class="slate-li " ><div style="position:relative">If not, a new deposit address is generated and linked to this email for future requests.</div></li></ul><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Deposit endpoint:</strong> /api/v2/payment/deposit</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">HTTP method:</strong> POST</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Request content:</strong> JSON object</p><p class="slate-p slate-indent-0" style="0px">
<strong class="slate-bold">Binance Pay intefration: </strong>To use the Binance Pay gateway, you must set <code class="slate-code">&quot;paymentGatewayName&quot;</code> parameter to <code class="slate-code">“BNB_BINANCE”</code> and set the <code class="slate-code">“paymentCurrency”</code> parameter to <code class="slate-code">“BNB”</code>.
Note: This configuration unlocks multiple cryptocurrency options for the user on the payment page.</p><div class="slate-div"></div><p class="slate-p " ></p><h2 class="slate-h2 " >Statuses of deposit requests</h2><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:initial;">Title</div><div style="width:429px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:429px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">NEW</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction has been initiated
(for example, the user displayed the wallet address to deposit)</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">PENDING</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction is processing.
This status is temporary. It should change to DONE after receiving confirmation/response from the blockchain</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">DECLINED</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction has failed in the blockchain</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">DONE</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction is done. The funds are booked</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">SUSPECTED</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">A suspicious transaction that must go through verification process by our legal team</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">PARTIALLY PAID</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">The received amount is less than the requested amount. An additional payment covering the missing balance is required for the transaction status to change to DONE</strong></p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

This request is responsible for generating a new deposit wallet address for cryptocurrency transactions and providing a link to the payment page. It is a valuable tool for users who wish to make a deposit or payment using cryptocurrencies. 

Crypto selection flow (2-step payment page)

When a deposit request is created without a preselected cryptocurrency (

), the user is redirected to a two-step payment page:

Step I – Cryptocurrency selection – the user chooses which currency to use.

Step II – Payment details – the user sees the address, amount and completes the deposit.

The user may navigate back from Step II to Step I to select a different cryptocurrency.
In this case, a single deposit request can have multiple deposit addresses associated with it, one per selected cryptocurrency.

If paymentCurrency and payment is not provided, a 2-step payment page with cryptocurrency selection

 are not provided, a 2-step payment page will be generated:

 are provided, the user is redirected directly to the payment details. 

By default, Match2Pay generates a new deposit address for each deposit request.
For gateways using the 

 method, it is possible to enable the fixed wallets feature on the gateway configuration level


To use the Binance Pay gateway, you must set 

.
Note: This configuration unlocks multiple cryptocurrency options for the user on the payment page.

Description

The requested deposit amount in the currency provided in "currency" param

amount

Your API token - it will be provided by support

apiToken

Notification URL to send updates of payment status

callbackUrl

Symbol of currency to which currency deposit shhould be converted
Use the paymentCurrency from Cryptocurrency details section

currency

The order of parameters in the "customer" object must be exactly as specified in the documentation; otherwise, the request will not be processed successfully

customer

The URL to redirect the user in case of a failed transaction

failureUrl

Optional (direct specific payment details flow). The currency of the payment gateway
All currency symbols are described in the Cryptocurrency Details section

paymentCurrency

Optional (direct specific payment details flow). Name of payment gateway that will be used for deposit (e.g., USDT TRC20)
All available payment gateways are described in the Cryptocurrency Details section.

paymentGatewayName

The method of payment used for the transaction. 
For cryptocurrency gateways it is always CRYPTO_AGENT 
For PSP gateways, please ask support what paymentMethod you should use

paymentMethod

The URL to redirect the user upon a successful transaction

successUrl

timestamp

The signature generated from the request body and API secret

All necessary information to generate a valid signature can be found in the Signature section

signature

address

Unique id of the payment transaction in the Match2Pay

paymentId

status

transactionAmount

transactionCurrency

netAmount

finalAmount

Symbol of currency to which deposited currency was converted

finalCurrency

processingFee

Match2Pay page URL. The client should be redirected to this URL

checkoutUrl

errorList

totalInCryptoCurrency

totalInAccountCurrency

feeInAccountCurrency

Expiration time of the wallet address in UTC

expiration

URLs to the exchangers where you can redirect the user to make the crypto purchase through exchanger

exchangerLinks

<h3 class="slate-h3 " >The first callback will be sent to you after transaction appears in blockchain - PENDING status</h3><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ", 
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":0,
    "amount":0.10000000,
    "transactionCurrency": "BTC",
    "status":"PENDING",
    "processingFee":0.00500000,
    "conversionRate":0
    "blockchainType": "BITCOIN"
    }
  ],
"paymentId":"99ca8c34-5191-41d9-a1a2-666b9badf1ce", 
"status":"PENDING",
"transactionAmount":0.10000000,
"netAmount":0.09500000,
"transactionCurrency":"BTC",
"processingFee":0.00500000,
"finalAmount":0,
"finalCurrency":"USD",
"conversionRate":0
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h3 class="slate-h3 " >The second callback will be sent to you after the funds are correctly booked - DONE status</h3><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ",
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":2,
    "amount":0.10000000,
    "transactionCurrency": "BTC",
    "confirmedTime":"Mar 20, 2019 7:06:38PM",
    "status":"DONE",
    "processingFee":0.00500000,
    "conversionRate":3198.64800
    "blockchainType": "BITCOIN"
    }
  ],
"paymentId":"99ca8c34-5191-41d9-a1a2-666b9badf1ce",
"status":"DONE",
"transactionAmount":0.10000000,
"netAmount":0.09500000,
"transactionCurrency":"BTC",
"processingFee":0.00500000,
"finalAmount":303.87,
"finalCurrency":"USD",
"conversionRate":3198.65
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h3 class="slate-h3 " >Fields</h3><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">depositAddress</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Cryptocurrency wallet address</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">txid</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Blockchain id of the transaction
(can be used to check the transaction status in the blockchain)</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">confirmations</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Number of transaction confirmations</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">amount</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Deposited amount</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">status</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Transaction status</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">processingFee</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Charged fee amount</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">conversionRate</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Conversion rate from transactionCurrency to finalCurrency</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">paymentId</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Unique id of the payment transaction in the Match2Pay</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">transactionAmount</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Value of transactions in the transactions currency</strong></p><p class="slate-p " ><strong class="slate-bold">That value should NOT be used to book deposits</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">netAmount</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">transactionAmount after processsing fee deduction</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">finalAmount</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Amount sum of confirmed transactions</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">finalCurrency</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Currency in which we will return the finalAmount</strong></p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

The first callback will be sent to you after transaction appears in blockchain - PENDING status

The second callback will be sent to you after the funds are correctly booked - DONE status

<p class="slate-p " >A withdrawal request is a fundamental process that facilitates the transfer of cryptocurrency funds from one&apos;s wallet to an external recipient&apos;s address.</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Endpoint:</strong> /api/v2/payment/withdrawal</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">HTTP method:</strong> POST</p><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">Request Content:</strong> JSON Object</p><div class="slate-div"></div><p class="slate-p " ></p><div class="slate-div"></div><h2 class="slate-h2 " >Statuses of withdrawal requests</h2><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">NEW</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction has been initiated</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">ADMIN CONFIRMATION</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transactions need to be confirmed by Support</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">PENDING</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction is processing.
This status is temporary. It should change to DONE or DECLINED after receiving confirmation/response from the blockchain</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">DECLINED</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction has failed.
This status is not final – it can be reprocessed within the same paymentID</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">DONE</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><strong class="slate-bold">The transaction is done. The funds are booked</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">FAIL</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">The transaction has failed</strong></p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

A withdrawal request is a fundamental process that facilitates the transfer of cryptocurrency funds from one's wallet to an external recipient's address.

The amount the client wants to withdraw in the currency specified in the currency parameter

Notification about changes in payment status will be sent to this URL

The wallet address of the end user to which they want to withdraw funds

The wallet address must match the network of the paymentCurrency

cryptoAddress

Symbol of currency of client's account.

In that currency funds will be taken from your Match2Pay balance

Optional. The symbol of the currency that will be withdrawn (e.g. USX)


All currency symbols are described in the Cryptocurrency details section

Optional. Name of payment gateway that will be used for withdrawal (e.g., USDT TRC20)

All available payment gateways are described in the Cryptocurrency details section.

The method of payment used for the transaction. 
For crypto gateways it is always CRYPTO_AGENT 

For PSP methods please ask support what method to use

Content-Type

Payment Id which helps you find this transaction in the m2p dashboard

Status of the transaction on the moment of sending request

convertRatio

tempTransactionId

Please make sure you send cryptocurrency from the list below and use a network supported by Match2pay.
Sending funds via an unsupported token or network may result in loss of funds.

, there are 3 types of BTC addresses supported by our system:

For the test environment, we provide Bitcoin and USDT TRC20 gateways.

To deposit using the TON blockchain via Match2Pay, you must include a memo.

The deposit request will generate a wallet address and memo in the format 

 Failing to include the memo may result in a loss of funds!

For withdrawals, Match2Pay supports both options: with or without a memo. 

To withdraw without a memo, simply enter the wallet address as usual. 

"address": "UQANXiRA9BhsOAcuaQ30L7W2StlboH2p9_eOxf4VB1ohz0v6;1708317974"

depositAddress

cryptoTransactionInfo

conversionRate

Example

<p class="slate-p " ><strong class="slate-bold">Important note</strong>: Callback signature should only be validated for status <strong class="slate-bold">DONE</strong></p><p class="slate-p " >To ensure that callback comes from match2pay system you can optionally check the callback signature. To do this you have to build the sha384 hash by adding the content of callback in following order:
“transactionAmount” + “transactionCurrency” + “status” + “apitoken” + “apisecret”
It’s important to mention that signature will be recieved in <strong class="slate-bold">Headers</strong>

<strong class="slate-bold">Example:</strong></p><div class="slate-div"></div><div class="slate-code_line">In this case &quot;transactionAmount&quot; + &quot;transactionCurrency&quot; + &quot;status&quot;</div><div class="slate-code_line">string will look like this:</div><div class="slate-code_line"></div><div class="slate-code_line">0.00011873BTCDONE +&quot;apitoken&quot;+&quot;apisecret&quot;</div><div class="slate-code_line"></div><div class="slate-code_line">amount = <strong class="slate-bold">0.00011873</strong></div><div class="slate-code_line">transactionCurrency = <strong class="slate-bold">BTC</strong></div><div class="slate-code_line">status = <strong class="slate-bold">DONE</strong></div><div class="slate-code_line">apitoken = provided by Support</div><div class="slate-code_line">apisecret = provided by Support</div><div class="slate-code_line"></div><div class="slate-code_line">In case when(USX for Example):</div><div class="slate-code_line">      &quot;amount&quot;: 1,</div><div class="slate-code_line">you have to add .00000000 to the amount. Beginning of string should looks like this:</div><div class="slate-code_line">1.00000000USXDONE</div><div class="slate-code_line"></div><p class="slate-p " >&quot;amount&quot; should allways have 8 decimal places in string to generate signature.

</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

: Callback signature should only be validated for status 

To ensure that callback comes from match2pay system you can optionally check the callback signature. To do this you have to build the sha384 hash by adding the content of callback in following order:
“transactionAmount” + “transactionCurrency” + “status” + “apitoken” + “apisecret”
It’s important to mention that signature will be recieved in 

In this case "transactionAmount" + "transactionCurrency" + "status"

0.00011873BTCDONE +"apitoken"+"apisecret"

you have to add .00000000 to the amount. Beginning of string should looks like this:

"amount" should allways have 8 decimal places in string to generate signature.



Python

<p class="slate-p " >All signatures are valid for one minute after creation.</p><p class="slate-p " >API token and API secret key are provided by Match-Trade.</p><p class="slate-p " ><strong class="slate-bold">Algorithm</strong></p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Take all the keys from your deposit or withdrawal request and sort them in A-Z order</div></li><li class="slate-li " ><div style="position:relative">Concatenate the values according to the order of keys from the first step</div></li><li class="slate-li " ><div style="position:relative">Append the API secret key to the concatenated string from the second step</div></li><li class="slate-li " ><div style="position:relative">Build the sha384 hash of the string from the third step</div></li></ol><p class="slate-p " ><strong class="slate-bold">Example</strong></p><p class="slate-p " >API secret key: <span style="background-color:rgb(31, 31, 31);color:rgb(206, 145, 120)">ApiSecretProvidedBySupport</span></p><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "amount": 10,
  "apiToken": "ApiTokenProvidedBySupport",
  "callbackUrl": "http://test/deposit/callback",
  "currency": "USD",
  "customer": {
    "firstName": "firstName_4da0af01617c",
    "lastName": "lastName_801eb285edd1",
    "address": {
      "address": "address_52c10ed842fb",
      "city": "city_62da6faaeb17",
      "country": "country_a6be7ed127cc",
      "zipCode": "zipCode_3e168862ef49",
      "state": "state_b8d531055c90"
    },
    "contactInformation": {
      "email": "email_e4ac63093536",
      "phoneNumber": "phoneNumber_8fcb0237f7ee"
    },
    "locale": "en_US",
    "dateOfBirth": "dateOfBirth_338c08d95dd6",
    "tradingAccountLogin": "clientId_d6811bff2963",
    "tradingAccountUuid": "clientUid_56b798ba2ae2"
  },
  "failureUrl": "http://test/failed-payment",
  "paymentCurrency": "USX",
  "paymentGatewayName": "USDT TRC20",
  "paymentMethod": "CRYPTO_AGENT",
  "successUrl": "http://test/thanku",
  "timestamp": "1764149779000" 
}
 </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">The string from this request body is: <code class="slate-code">10ApiTokenProvidedBySupporthttp://test/deposit/callbackUSD{firstName=firstName_4da0af01617c, lastName=lastName_801eb285edd1, address={address=address_52c10ed842fb, city=city_62da6faaeb17, country=country_a6be7ed127cc, zipCode=zipCode_3e168862ef49, state=state_b8d531055c90}, contactInformation={email=email_e4ac63093536, phoneNumber=phoneNumber_8fcb0237f7ee}, locale=en_US, dateOfBirth=dateOfBirth_338c08d95dd6, tradingAccountLogin=clientId_d6811bff2963, tradingAccountUuid=clientUid_56b798ba2ae2}http://test/failed-paymentUSXUSDT TRC20CRYPTO_AGENThttp://test/thanku1764149779000</code></div></li><li class="slate-li " ><div style="position:relative">Then we append the secret key at the end and we receive: <code class="slate-code">10.00ApiTokenProvidedBySupporthttp://test/deposit/callbackUSD{firstName=firstName_4da0af01617c, lastName=lastName_801eb285edd1, address={address=address_52c10ed842fb, city=city_62da6faaeb17, country=country_a6be7ed127cc, zipCode=zipCode_3e168862ef49, state=state_b8d531055c90}, contactInformation={email=email_e4ac63093536, phoneNumber=phoneNumber_8fcb0237f7ee}, locale=en_US, dateOfBirth=dateOfBirth_338c08d95dd6, tradingAccountLogin=clientId_d6811bff2963, tradingAccountUuid=clientUid_56b798ba2ae2}http://test/failed-paymentUSXUSDT TRC20CRYPTO_AGENThttp://test/thanku1764149779000ApiSecretProvidedBySupport</code></div></li><li class="slate-li " ><div style="position:relative">Then we use sha-384 to generate a hash from this string and we receive our final signature value: <code class="slate-code">e058a6fb0d310335985f69d686ae47bdf1c34ad33bcafd83852b6034d8eb3254e7d300a63590f815baf2fe3d8eff11ec</code>
Please remember that signature must have <strong class="slate-bold">lowercase letters</strong>.</div></li><li class="slate-li " ><div style="position:relative">We add it to the request body in the signature field. The final request body is:</div></li></ol><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "amount": 10,
  "apiToken": "ApiTokenProvidedBySupport",
  "callbackUrl": "http://test/deposit/callback",
  "currency": "USD",
  "customer": {
    "firstName": "firstName_4da0af01617c",
    "lastName": "lastName_801eb285edd1",
    "address": {
      "address": "address_52c10ed842fb",
      "city": "city_62da6faaeb17",
      "country": "country_a6be7ed127cc",
      "zipCode": "zipCode_3e168862ef49",
      "state": "state_b8d531055c90"
    },
    "contactInformation": {
      "email": "email_e4ac63093536",
      "phoneNumber": "phoneNumber_8fcb0237f7ee"
    },
    "locale": "en_US",
    "dateOfBirth": "dateOfBirth_338c08d95dd6",
    "tradingAccountLogin": "clientId_d6811bff2963",
    "tradingAccountUuid": "clientUid_56b798ba2ae2"
  },
  "failureUrl": "http://test/failed-payment",
  "paymentCurrency": "USX",
  "paymentGatewayName": "USDT TRC20",
  "paymentMethod": "CRYPTO_AGENT",
  "successUrl": "http://test/thanku",
  "timestamp": "1764149779000",
  "signature": "e058a6fb0d310335985f69d686ae47bdf1c34ad33bcafd83852b6034d8eb3254e7d300a63590f815baf2fe3d8eff11ec"
}
 </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><p class="slate-p " ><strong class="slate-bold">Algorithm for creating the siganture</strong></p><p class="slate-p " >This Python script generates a SHA-384 signature from a structured request body and an API secret. It is designed to ensure data integrity by concatenating specific request parameters in a defined order and hashing them.</p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

All signatures are valid for one minute after creation.

API token and API secret key are provided by Match-Trade.

This Python script generates a SHA-384 signature from a structured request body and an API secret. It is designed to ensure data integrity by concatenating specific request parameters in a defined order and hashing them.

<p class="slate-p " >Onchain fees are charges associated with processing cryptocurrency transactions on their respective blockchain networks. </p><p class="slate-p " >Match2Pay applies fixed onchain fees to:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Direct settlement withdrawals</strong> </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Client withdrawals</strong>, if specified in the agreement</div></li></ul><p class="slate-p " ></p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:195px;">Cryptocurrency</div><div style="width:225px;"> Network</div><div style="width:224px;">Onchain Fee</div></div><colgroup ><col style="width:195px"><col style="width:225px"><col style="width:224px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >BTC</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Bitcoin</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >0.00004 BTC</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >ETH</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Ethereum</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >0.001 ETH</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >BNB</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Binance Chain</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >0.0005 BNB</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >MATIC</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Polygon</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >0.5 MATIC</p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:195px;">Stablecoin</div><div style="width:226px;">Network</div><div style="width:224px;">Onchain Fee</div></div><colgroup ><col style="width:195px"><col style="width:226px"><col style="width:224px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDT</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >TRC20</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2.5 USDT</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDT</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >BEP20</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1 USDT</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDT</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >ERC20</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2.5 USDT</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDT</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >POLYGON</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1 USDT</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDC</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >BEP20</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1 USDC</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDC</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >ERC20</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2.5 USDC</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >USDC</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >POLYGON</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1 USDC</p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><p class="slate-p " ></p>

Onchain fees are charges associated with processing cryptocurrency transactions on their respective blockchain networks. 

Sections

Ask an AI

Code with AI