Bank transfers in Malaysia

Interaction diagram

Payment processing by using the Bank transfers in Malaysia payment method requires merchant's web service, one of Monetix interfaces, and the Monetix payment platform, as well as provider's technical facilities.

Operations support

	Interfaces			Amounts, MYR		Times
	Payment Page	Gate	Dashboard	minimum	maximum	basic	threshold
Purchases				100.00			48 hours

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 Bank transfers in Malaysia method, purchase workflow includes displaying payment instructions to the customer.

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

General information

In the Bank transfers in Malaysia methods, 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 then accepts a callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with one of the Bank transfers in Malaysia methods selected. For more information about pre-selecting payment methods, see in Preselecting payment methods. The full sequence of the purchase process is provided below.

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

Request format

There are several things you need to consider when using the Bank transfers in 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
   • customer_email—customer email
   • customer_first_name—customer first name. If the parameter is missing from the request, Payment Page will contain an additional field for the customer to enter missing information. For more information about additional information submission, see in Submission of additional payment information.
   • customer_last_name—customer last name. If the parameter is missing from the request, Payment Page will contain an additional field for the customer to enter missing information. For more information about additional information submission, see in Submission of additional payment information.
   • 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. If you need to have payment form displayed with the Bank transfers in Malaysia method pre-selected, set the force_payment_method parameter to bank-transfer-malaysia.
3. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the Bank transfers in Malaysia payment method, see Payment Page invocation parameters.
4. After you specify all the parameters you need, you need to create the signature for the request. For instructions on how to generate signatures, see Signature generation and verification.

Here is an example of data from a request for Payment Page opening:

EPayWidget.run(
    {
        project_id: 1234, 
        payment_id: 'payment_47',
        customer_id: 'customer_123',
        payment_currency: 'MYR',
        payment_amount: 200000,
        customer_first_name: 'John',
        customer_last_name: 'Doe',
        customer_email: 'johndoe@email.com',
        signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y19vySO\/RLUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

Callback format

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

The following is the example of a callback with an information about successful 2000.00 MYR purchase in project 1234.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Malaysia bank transfer",
        "sum": {
            "amount": 200000,
            "currency": "MYR"
        },
        "description": ""
    },
    "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": 200000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 200000,
            "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": "Malaysia bank transfer",
        "sum": {
            "amount": 200000,
            "currency": "MYR"
        },
        "description": ""
    },
    "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": 200000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 200000,
            "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 Bank transfers in Malaysia method, when processing a purchase through Gate, the merchant web service is required to do the following:

1. Send a request with all the required parameters and signature to the Monetix URL.
2. Display payment instruction to the customer.
3. Get 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 Bank transfers in Malaysia payment method and provide the information on the format of callbacks with purchase results. For general information about using Gate API, see API Description.

Request format

1. You send purchase requests by sending the request to /v2/payment/bank-transfer/malaysia/sale by using the POST (HTTP) method. This request belongs to the following request group /v2/payment/bank-transfer/{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—customer email
     • first_name—customer first name. This parameter may be passed either in initial request or in the process of additional payment information submission.
     • last_name—customer last name. This parameter may be passed either in initial request or in the process of additional payment information submission
   • 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
   • return_url—object with URLs for redirecting the customer back to the web service:
     • success—the URL to redirect in case the purchase successfully completed
     • decline—the URL to redirect in case the purchase failed
3. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a purchase request in the Bank transfers in 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",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@example.com"
    },
    "payment": {
        "amount": 200000,
        "currency": "MYR"
    },
    "return_url": {
        "success": "http://example.com/success",
        "decline": "http://example.com/decline"
    }
}

Format of the payment instruction data

To display the payment instructions to the customer, you need to receive and process a callback from the payment platform containing the payment data in the in the display_data array and display the payment instructions to the customer.

Each element of the display_data array contains the following parameters:

• type—data type, the value is always add_info
• title—name of the payment instruction components. Possible values:
  • transaction_id—payment number on the provider side
  • beneficiary—full name of transfer recipient
  • account_number—account number of the transfer recipient
  • bank_name—bank name of the transfer recipient
  • bank_address—bank address of the transfer recipient
• data—payment instruction data

The following is the callback fragment containing the data to display to the customer:

 "display_data": [
    {
      "type": "add_info",
      "title": "transaction_id",
      "data": "12a34b5c-6789"
    },
    {
      "type": "add_info",
      "title": "beneficiary",
      "data": "John Doe"
    },
    {
      "type": "add_info",
      "title": "account_number",
      "data": "999999999999999"
    },
    {
      "type": "add_info",
      "title": "bank_name",
      "data": "Reserve Bank of India"
    },
    {
      "type": "add_info",
      "title": "bank_address",
      "data": "Mumbai"
    }
  ]

Here is an example of a payment instruction text which can be used in payment instruction in the web service:

Callback format

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

The following is the example of a callback with an information about a successful 2000.00 MYR purchase in the 1234 project.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Malaysia bank transfer",
        "sum": {
            "amount": 200000,
            "currency": "MYR"
        },
        "description": ""
    },
    "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": 200000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 200000,
            "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": "Malaysia bank transfer",
        "sum": {
            "amount": 200000,
            "currency": "MYR"
        },
        "description": ""
    },
    "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": 200000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 200000,
            "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:

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

General information

You can perform test purchases with the Bank transfers in Malaysia payment method by using Payment Page and Gate.

To perform test purchases, you'll need the test project ID and the secret key to it. To get them, please contact the technical support team at support@monetix.pro and then contact your Monetix key account manager to set up a test environment to work with the Bank transfers in Malaysia payment method.

When performing test payments, keep in mind that:

• your requests must contain the test project ID
• the payment currency that you send in requests can be only MYR
• random values may be used as the payment ID and in the parameters with customer information
• the interface of the test checkout page may be different from the production one.

Test payments statuses

To receive one of the following statuses in the callback with the test purchase result, use a particular value for the purchase amount in the request:

• 40000 and 40400—to receive a callback with the decline status
• 90000—to receive a callback with the success status and a purchase amount different from the amount in the request
• any other value—to receive a callback with the success status

Testing purchase by using Payment Page

To perform a test purchase by using Payment Page:

1. Send a request for purchase through Payment Page to the payment platform.
2. Choose a payment method on the test checkout page. If you've passed the force_payment_method parameter with the bank-transfer-malaysia value in the request, you won't have to choose the payment method.
3. Specify a random first name and last name in the data entry fields. The payment instructions will be displayed to you after.
4. Accept a callback with information about the test purchase result.
5. Wait a few seconds until the result of the test purchase is displayed to you on the test checkout page.

See the detailed information about purchase processing through Payment Page in the Bank transfers in Malaysia payment method in the Purchase by using Payment Page section.

Testing purchase by using Gate

To perform a test purchase by using Gate:

1. Send a request for performing a test purchase to the payment platform.
2. Accept a callback with the data for displaying payment instructions. Your system will display the payment instructions to you after.
3. Accept a callback with information about the test payment result.
4. Wait a few seconds until your system shows you the result of the test purchase.

See the detailed information about purchase processing through Gate in the Bank transfers in Malaysia payment method in the Purchase by using Gate section.

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.