List of CRMs already integrated with our Crypto Gateway

• Utip
• FX Back Office
• Skale
• Trade Smarter
• Kenmore design
• TradeSoft
• Nullpoint
• Plugit
• Axis (Broctagon)
• Reltrix
• Datalyst
• FTT (Fair Trading Technology)
• Leverate
• Pheasantech
• UpTrader
• Syntellicore (Dynamic Works)

List of payment cashiers already integrated with our Crypto Gateway

• Paytiko
• Praxis
• BridgerPay
• Akurateco
• Corefy

1. The client requests a deposit in the broker’s Client Office.
2. Client Office sends the request to the M2P.
3. Processing request, generating individual crypto deposit wallet address.
   • It is possible to assign generated wallet address to a particular trading account/client. Detailed guide can be found at the bottom.
4. Returning generated crypto deposit wallet address on the payment page.
   • If the client has a cryptocurrency, they can send this cryptocurrency to this individual deposit wallet address.
5. The transaction is being processed by the blockchain.
6. After receiving the information from the blockchain about a successfully processed transaction, the cryptocurrency is being booked on the deposit wallet address.
7. Converting the cryptocurrency to FIAT. The final amount is being added to the broker’s M2P balance.
8. The amount from a callback is being booked on the client’s trading account.

In order to be able to accept multiple deposits to the same wallet address, the integration should be changed so that the payment_id of the generated request is assigned to a particular account on your end. The same payment_id should always be used/displayed for a specific account within the same crypto gateways.

Within one payment_id there may be other deposits, which will have different hashes from the others but will still belong to the same payment_id.

To sum up, the integration on your side should assume that the payment_id of the request may be repeated for deposits, but the transaction hash will be different, so if you receive a callback in which there is a hash with a new transaction it should be booked.

This integration will have to be changed for each crypto payment gateway you use.

Optionally, you can also add the ability to unlink the wallet address (payment_id) from the selected account so that it will be possible to generate a new wallet address in exceptional situations.

The first callback will be sent to you after the client makes a deposit

{
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ", 
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":0,
    "amount":0.10000000,
    "status":"PENDING",
    "processingFee":0.00500000,
    "conversionRate":0
    }
  ],
"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
} {
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ", 
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":0,
    "amount":0.10000000,
    "status":"PENDING",
    "processingFee":0.00500000,
    "conversionRate":0
    }
  ],
"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
} 

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

{
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ",
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":2,
    "amount":0.10000000,
    "confirmedTime":"Mar 20, 2019 7:06:38PM",
    "status":"DONE",
    "processingFee":0.00500000,
    "conversionRate":3198.64800
    }
  ],
"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
} {
"depositAddress":"C9wic7ex7etARjPGQPKBHGLr2cRcCD17aZ",
"cryptoTransactionInfo":
  [
    {
    "txid":"b20feab400c3cd61a9d0daec8526d739a2335fe1900415f24835001e58a837a7",
    "confirmations":2,
    "amount":0.10000000,
    "confirmedTime":"Mar 20, 2019 7:06:38PM",
    "status":"DONE",
    "processingFee":0.00500000,
    "conversionRate":3198.64800
    }
  ],
"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
} 

Fields

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.

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

• Legacy – starting with “1”
• Script – starting with “3”
• Segwit – starting with “bc1q”

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

TON Blockchain

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 walletAddress;memo (separated by a ;)

Important: 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.

If a memo is required, use the format walletAddress;memo, for example:

"address": "UQANXiRA9BhsOAcuaQ30L7W2StlboH2p9_eOxf4VB1ohz0v6;1708317974"

All signatures are valid for one minute after creation.

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

Algorithm

1. Take all the keys from your deposit or withdrawal request and sort them in A-Z order
2. Concatenate the values according to the order of keys from the first step
3. Append the API secret key to the concatenated string from the second step
4. Build the sha384 hash of the string from the third step

Example

Select...
{
"apiToken" : "b3RJ4qBRai129psUfrbGisnE5wpaMaFvovQS",
"callbackUrl" : "http://test.com",
"currency" : "USD",
"paymentCurrency" : "BTC",
"timestamp" : "1566214818"
}

Select...
{
"apiToken" : "b3RJ4qBRai129psUfrbGisnE5wpaMaFvovQS",
"callbackUrl" : "http://test.com",
"currency" : "USD",
"paymentCurrency" : "BTC",
"signature":"1e0e1de03c8f00177f689cef9e48a9cefab5deb2f572eb578e719ccf2b7f526758ae5aca12b0433d2812908e233a2325",
"timestamp" : "1566214818"
}