Banks of Malaysia

Interaction diagram

Payment processing by using the Banks of Malaysia payment method requires merchant's web service, one of the interfaces and the payment platform of Monetix, as well as one of the bank services which supports this payment method.

Operations support

	Interfaces			Amounts, MYR		Times
	Payment Page	Gate	Dashboard	Minimum	Maximum	basic	threshold
Purchases				*	*	up to 20 minutes	48 hours
Payouts				*	*	up to 30 minutes	48 hours

* For the most recent amount limits, contact your Monetix Key Account Manager.

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.

Processing scenarios

In the Banks of Malaysia method, purchases and payouts follow different processing procedures. To perform a purchase, you need to redirect customer to the bank service, while to initiate a payout, you need to notify customer via merchant web service.

The sections that follow provide more information about what you need to perform payments and how you can analyze payments and operations information.

Supported banks

In the Banks of Malaysia payment method, in the payments that use Gate, the customer selects a bank on the web service side. Thus, the web service needs to submit the bank ID in the request for the payment processing.

The table below provides the information about supported banks. The list is provided for the informational purposes only.

Table 1. Supported banks

Bank	ID	Purchase	Payout
Affin Bank	109
Affin Islamic Bank Berhad	67941
Al-Rajhi	75112
Alliance Bank	110
Alliance Islamic Bank	67951
AM Bank	108
Bangkok Bank Berhad	68941
Bank Islam Malaysia	471
Bank of America	62421
Bank of China	157
Bank Muamalat Malaysia	472
Bank Pertanian Malaysia Berhad (Agrobank)	3921
Bank Rakyat	112
Bank Simpanan National	481
BNP Paribas Malaysia	68931
China Construction Bank	68951
CIMB Bank	105
Citi bank	114
Deutsche Bank (M) Berhad	67931
GXBank	75132
Hong Leong Bank	106
HSBC Bank	116
Industrial and Commercial Bank of China	68961
J.P. Morgan Chase Bank Berhad	68971
Kuwait Finance House	473
Malayan Banking Berhad (M2E)	117
Maybank Berhad	103
MBSB BANK	68991
MUFG Bank (Malaysia) Berhad	75092
Oversea-Chinese Banking Corporation Limited (OCBC)	118
Public Bank	104
RHB Bank	107
Standard Chartered Bank	122
Sumitomo Mitsui Banking Corporation (M)	75122
United Overseas Bank	478

Note that the list of supported banks may change without notice; to get the most recent list of supported banks, use the Gate API to send a POST request to one of the /v2/info/banks/{payment_method}/{operationType}/list endpoints.

In the Banks of Malaysia method, you can use the following endpoints:

• /v2/info/banks/malaysia/sale/list—to retrieve the list of banks that support purchase
• /v2/info/banks/malaysia/payout/list—to retrieve the list of banks that support payout

The following objects and parameters must be specified in request for the list of supported banks:

• general—object with general request information
  • project_id—project ID obtained from Monetix
  • payment_id—payment ID unique within the project
  • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
• payment—object with payment information:
  • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
  • currency—payout currency in the ISO-4217 alpha-3 format

Here is an example of the data from a request for the supported banks list. It is important to specify real payment data, but if the payment has not yet been generated, you can specify a random value for the payment ID in the request.

{
  "general": {
    "project_id": 200,
    "payment_id": "ORDER_155860015",
    "signature": "K6jllym+PtObocZtr345st...=="
  },
  "payment": {
    "amount": 150000,
    "currency": "MYR"
  }
}

General information

In the Banks of Malaysia method, when processing a purchase by using Payment Page, the merchant web service sends a request with all the required parameters and signature to the Monetix URL and accepts the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with the Banks of Malaysia method pre-selected. (For more information about pre-selecting payment methods, see in Preselecting payment methods.)

The full sequence of the purchase workflow is provided below.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the Banks of Malaysia payment method and provide the information about format of callbacks with payment results. For the general information about how to use the Payment Page API, see Payment Page API Description.

Request format

There are several things you need to consider when dealing with purchase requests in the Banks of Malaysia method:

1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are required for any payment method:
   • project_id—project ID you obtained from Monetix
   • payment_id—payment ID unique within the project
   • customer_id—unique ID of the customer within your project
   • payment_currency—payment currency in ISO-4217 alpha-3 format
   • payment_amount—payment amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
2. Also, you may need to add the following customer information parameters:
   • account_customer_name—customer full name
   • customer_email—customer email

   If any of these parameters is missing, Payment Page will contain an additional fields for the customer to enter missing information. For more information about additional information submission, see in Submission of additional payment information.

3. There are several options to customize the payment method selection page on Payment Page.
   • Bank selection in two steps This is the default option. The banks that support Banks of Malaysia payment method are grouped in one button on Payment Page, therefore bank selection is carried out in two steps. On the first step, the Banks of Malaysia method is chosen among others, and then, on the second step, particular bank is selected on the next page with the list of the group banks.
   • Display each bank as a separate button along with other payment methods—show each bank of the Banks of Malaysia group as a separate button, set the split_banks parameter in the payment_methods_options object to true.

     payment_methods_options={"online_malaysian_banks": {"split_banks": true}}

   • Show the banks of a single payment method—show only the banks available in the Banks of Malaysia payment method on Payment Page for customers, pass the code online-malaysian-banks in the force_payment_method parameter. The customer will see only the banks available in the Banks of Malaysia method.
   • Show only selected banks—show a button of specific banks (one or several) from Banks of Malaysia group on Payment Page in the list of payment methods, set force_payment_method to online-malaysian-banks and add an array with IDs of the banks to show on Payment Page in the banks_id parameter. Here an example:

     payment_methods_options={"online_malaysian_banks": {"split_banks": true, "banks_id": [105, 106]}}

     Here is an example of a request to open Payment Page with a pre-selected bank:

     EPayWidget.run(
         { 
             project_id: 1234,
             payment_id: "X03936",
             customer_id: "customer_123",
             payment_currency: "MYR",
             payment_amount: 2500000,
             force_payment_method: "online-malaysian-banks",
             payment_methods_options: {"online_malaysian_banks": {"banks_id": [106]}},
             signature: "kUi2x9dKHAVNU0FY...vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
         }
     )

4. You can also add any other additional parameters Payment Page supports. For more information about parameters supported by Payment Page, see Payment Page invocation parameters.
5. After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign payment requests, see Signature generation and verification.

Here is an example of data from a purchase request.

EPayWidget.run(
    {
        project_id: 1234, 
        payment_id: 'payment_47',
        customer_id: 'customer_123',
        account_customer_name: 'John Doe',
        payment_currency: 'MYR',
        payment_amount: 2500000,      
        signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO\/RLUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

Callback format

The Banks of Malaysia method uses the standard format for callbacks to deliver purchase results. For more information about callbacks, see Callbacks in Payment Page.

The following is an example of a callback with an information about successful 25,000.00 MYR purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0b08569d7d150e387a16a80e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback for a declined purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 15923,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlfqz8155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

The following topics might be useful when implementing payments through Payment Page:

• Integration procedure
• Payment types, operations and payments
• Signature generation and verification
• Operation statuses and response codes

General information

In the Banks of Malaysia method, the merchant web service is required to do the following when processing a purchase by using Gate:

1. Send request with all the required parameters and signature to the Monetix URL.
2. Redirect the customer to the bank service.
3. Accept the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Banks of Malaysia payment method and provide the information about the format of callbacks with purchase results. For the general information on how to use the Gate API, see API Description.

Request format

There are several things you need to consider when dealing with purchase requests in the Banks of Malaysia method:

1. You initiate purchase by submitting a purchase request to the /v2/payment/banks/malaysia/sale endpoint by using HTTP method POST. This endpoint belongs to the following group of endpoints for payments by using online banking: /v2/payment/banks/{payment_method}/sale.
2. The following objects and parameters must be specified in any request:
   • general—object with general request identification information:
     • project_id—the project ID you obtained from Monetix
     • payment_id—payment ID unique within the project
     • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—customer device IP
     • email—email address. This parameter may be passed either in initial request or in the process of additional payment information submission. For more information about additional information submission, see Submission of additional payment information.
   • payment—object with purchase information:
     • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of purchase currency in the ISO-4217 alpha-3 format
   • account—object with customer account information:
     • bank_id—bank ID
     • customer_name—customer full name. This parameter may not be mandatory. Refer to you Key Account Manager at Monetix for details.
   • return_url—object with the information where to redirect the customer to when the payment is completed:
     • success—the URL to redirect the customer to after the payment is successfully completed.
3. The following parameters with the return URLs are optional, but we strongly advise you to specify them in the request to provide your customer a better user experience. If you don't specify any parameters of the return_url object in the request, by default Gate will redirect the customer to the URL specified in your project in Monetix.
   • return_url—object with the information where to redirect the customer to when the payment is completed or prematurely terminated by the customer:
     • decline—the URL to redirect the customer to after the payment is declined.
     • return—the URL to redirect the customer to when they prematurely terminate the payment.
4. If required, you can add any other additional (optional) parameters Gate supports.

Here is an example of data from a purchase request in the Banks of Malaysia method.

{
    "general": {
        "project_id": 1234,
        "payment_id": "payment_47",
        "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "customer": {
        "id": "customer_123",
        "ip_address": "198.51.100.47",
        "email": "example@email.com"
    },
    "account":{
        "bank_id": 105,
        "customer_name": "John Doe"
    },
    "payment": {
        "amount": 2500000,
        "currency": "MYR"
    },
    "return_url": {
        "success": "https://example.com/success/",
        "decline": "https://example.com/decline/",
        "return": "https://example.com/return/"
    }
}

Format of customer redirection data

After receiving and processing your purchase request, the payment platform sends a callback to your web service containing the data to redirect the customer to the bank service.

To redirect the customer, use the values of the following parameters in the redirect_data object:

• url—the URL to redirect the customer to
• body—the data to be sent in the request body
• method—the HTTP method to get an HTML page of the website (for example, POST or GET)
• encrypted—this is the service parameter. Ignore the data it contains.

Here is an example of a piece of callback containing the data to redirect the customer.

"redirect_data": {
    "method": "POST",
    "body": {
        "example_parameter_1": "value_1",
        "example_parameter_2": "value_2"
    },
    "encrypted": [],
    "url": "https://example.com/redirect"
}

Callback format

The Banks of Malaysia method uses the standard format for callbacks to deliver purchase results. For more information about callbacks, see Callbacks in Gate.

The following is an example of a callback with an information about successful 25,000.00 MYR purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0b08569d7d150e387a16a80e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback for a declined purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 15923,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlfqz8155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

The following topics might be useful when implementing payments through Gate:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

General information

To perform payout with the Banks of Malaysia method, merchant's web service sends a request with all the required parameters and signature to Monetix URL, and receives callback with the payment result.

The complete sequence of the payout process is provided below.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Banks of Malaysia payment method and provide the information on the format of callbacks with payout results. For the general information on how to use the Gate API, see API Description.

Request format

There are several things you must consider when using payout requests in the Banks of Malaysia method:

1. You initiate a payout by sending a payout request to the /v2/payment/banks/malaysia/payout endpoint by using the HTTP method POST. This endpoint belongs to the following group of endpoints for the online banking payments: /v2/payment/banks/{payment_method}/payout.
2. The following objects and parameters must be specified in any request:
   • general—object with general request identification information:
     • project_id—the project ID obtained from Monetix
     • payment_id—payment ID unique within the project
     • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—customer device IP
   • account—object with customer account information:
     • number—customer account number
     • customer_name—customer full name
     • bank_id—bank identificator
   • payment—object with payout information:
     • amount—payout amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of payout currency in the ISO-4217 alpha-3 format
3. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a payout request in the Banks of Malaysia method.

{
    "general": {
        "project_id": 1234,
        "payment_id": "payment_47",
        "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "customer": {
        "id": "customer_123",
        "ip_address": "198.51.100.47"
    },
    "account": {
        "number": "1234567890123456",
        "customer_name": "John Doe",
        "bank_id": 105
    },
    "payment": {
        "amount": 2500000,
        "currency": "MYR"
    }
}

Callback format

The Banks of Malaysia method uses the standard format for callbacks to deliver payout results. For more information about callbacks, see Callbacks in Gate.

The following is the example of a callback with an information about successful 25,000.00 MYR payout.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "operation": {
        "id": 29,
        "type": "payout",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0b08569d7d150e387a16a80e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback for a declined payout.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Malaysian banks",
        "sum": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "description": ""
    },
    "operation": {
        "id": 29,
        "type": "payout",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 2500000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlf155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

The following topics might be useful when implementing payments through Gate:

• Synchronous and asynchronous message processing
• Payment types, operations and payments
• Signature generation and verification
• Operation statuses and response codes

• single payout—you specify the currency and amount for a payout available for this method and fill in all the fields required for the selected payment method on the Dashboard pages.
• as a part of a mass payment—all the parameters are specified in a CSV file. Refer to the Payouts by using Gate section for the parameters required by your payment method.

Information about completed payouts is available for viewing in the Payments and Manual Payments sections of Dashboard.

For more information about payout processing by using Dashboard, see Performing payouts.

General information

For the Banks of Malaysia method the testing of purchases by using Payment Page and Gate as well as payouts by using Gate.

Testing can be performed within a test project, to enable and disable the testing availability, contact Monetix technical support via support@monetix.pro.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests, the interfaces of the payment forms emulator of Payment Page and Banks of Malaysia differ from the production environment.

Test payments statuses

When testing purchases, the final payment status is determined by the amount specified in the request:

• decline status with 40000 or 40400 amount
• success status with any other amount

When testing payouts, the final payment status is determined by the amount specified in the request:

• decline status with 40000 or 40400 amount
• success status with any other amount

Testing purchase by using Payment Page

To perform a test purchase by using Payment Page, do the following:

1. Send a correct test request for Payment Page opening to the payment platform.
2. If the online-malaysian-banks method was not specified in the request—select the method on the emulator page.
3. If multiple banks are available for selection, select a bank; if only one bank is available, click the Pay button.
4. Click the Success or Decline button (depending on the amount specified in the request).
5. Accept a callback with information about the payment result.

The full information about purchase process by using Banks of Malaysia through Payment Page is provided in the section Purchase by using Payment Page.

Testing purchase by using Gate

To perform a test purchase by using Gate, do the following:

1. Send a correct test request for purchase to the payment platform (the bank_id parameter must be used in the request, refer to Monetix technical support for the parameter value).
2. Accept a callback with redirection data.
3. Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
4. Accept a callback with information about the payment result.

The full information about purchase process by using Banks of Malaysia through Gate is provided in the section Purchase by using Gate.

Testing payout by using Gate

To perform a test payout by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. The full information about payout process by using Banks of Malaysia through Gate is provided in the section Payout by using Gate.

As with other payment methods Monetix offers, when using this method, you have several options to analyze the information about payments and operations.

You can load and analyze all the necessary information in Dashboard (dash-light.trxhost.com), for instance you can use the analytic panels in the Analytics section for this purpose.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

• Dashboard allows you to download reports in CSV format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
• Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by means of sending requests to the /operations/get endpoint.

If you have any further questions regarding payment data analysis, contact Monetix technical support.