Boost

Overview

Boost, a popular payment method in Malaysia, offers your customers a convenient way of paying for your services and receiving payouts. In the Boost payment method, customers make purchases by using e-wallets.

With Boost, you can accept payments from your customers by using Payment Page and Gate and perform payouts by using Gate and Dashboard.

Download the logo in vector format here.
Payment method type E-wallets
Countries and regions Malaysia
Payment currencies MYR
Currency conversion On the Monetix side
Purchases
Payouts
COF payments
Full refunds
Partial refunds
Chargebacks
Special considerations
Note: The following considerations might be not relevant in your case. Refer to your Key Account Manager at Monetix to check if they are.
  • In some cases, the payment platform may increase the payment amount by 0.01 to 0.99 MYR. For more details about why the payment platform adjusts the payment amount, see Special payment processing considerations.
  • If the customer does not make all required steps to complete the payment within 15 minutes after the payment was initiated, the payment is declined on the provider side.
  • If the customer enters an incorrect payment amount, the payment is assigned an intermediate status until the conflict is resolved manually by Monetix technical support specialists. For more information about this scenario, see in Handling payments with amount changed by customer.
Onboarding and access fee Refer to your key account manager at Monetix.

Operations support

Interfaces Payment amount, MYR Payment processing time
Payment Page Gate Dashboard minimum maximum basic threshold
Purchase * * 1 minute 48 hours
Payout 1.00 10,000.00 1 minute 24 hours

* Contact your key account manager at Monetix for details.

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 then click the Payment methods tab.

The following sections provide more information about the payment processing flow and the analysis of completed payments.

Special payment processing considerations

Note: These considerations might be not relevant in your case. Refer to your Key Account Manager at Monetix to check if they are.

If the payment amount is exactly the same as the amount of one of the currently processed payments, then due to some special aspects of the provider operation, the payment platform may increase the payment amount by 0.01 to 0.99 MYR (but does not necessarily do so). This is sometimes required to distinguish between the current payment and the other ongoing payments with the same amount. The platform makes its best to avoid increasing the payment amount, if this is possible.

If number of the currently processed payments is so large that there are no more free slots in the 0,01 to 0,99 MYR range, then the payment platform declines the current request and all subsequent ones until processing of at least one of the current payments with the same amount is complete.

If the payment platform is forced to increase the payment amount, it responds to the web service with a callback with the new amount.

Here is an example of how the payment platform may behave when receiving two requests for payment with the same amount:

  1. The payment platform accepts the first request for payment of 15.00 MYR. This is the first request with this amount, therefore the payment platform does not change its amount and starts processing a 15,00 MYR payment.
  2. The payment platform accepts the second request for payment of 15.00 MYR.
  3. Since the payment with the amount of 15.00 MYR is already being processed, the payment platform changes the amount of the second payment to 15.01 MYR and proceeds with this amount.

Purchase by using Payment Page

General information

To perform a purchase by using Payment Page with the Boost payment method:

  1. Send a request with all the required parameters and signature to the Monetix URL.
  2. Accept the callback with the purchase result from the payment platform.

The following figure shows the complete purchase processing flow in the Boost payment method.

Figure 1. Purchase processing steps for a purchase by using Payment Page
  1. The customer initiates a purchase in your system.
  2. Your system sends the request for the purchase through Payment Page to the Monetix URL.
  3. The Monetix payment platform receives the request.
  4. The payment platform processes the request and checks whether it contains all the required parameters and the signature is correct.
  5. The payment platform creates the checkout page based on the project settings and request parameters.
  6. The checkout page is displayed to the customer.
  7. The customer chooses to make a purchase with the Boost payment method.
  8. Payment Page forwards the purchase request to the payment platform.
  9. Depending on the provider that processes this payment, the purchase processing flow in the Boost payment method may be one of the following:
    • Option 1
      1. The payment platform processes the request and generates the data for redirecting the customer to the provider service.
    • Option 2
      1. The payment platform processes the request and forwards it to the provider service.
      2. The provider service processes the purchase request.
      3. The provider service sends the customer redirection data to the payment platform.
  10. The payment platform forwards the data to Payment Page.
  11. Payment Page redirects the customer to the provider service.
  12. The customer completes the purchase.
  13. The provider service processes the purchase.
  14. The provider service sends the purchase result information to the payment platform.
  15. The payment platform sends a callback with the payment result to your system.
  16. The payment platform sends the payment result to Payment Page.
  17. Payment Page displays the payment result to the customer on the checkout page.

Request

The following table lists the parameters that you need to include in the request for purchase through Payment Page with the Boost payment method.

Table 1. Basic parameters of requests to Payment Page

strictly required—the parameter must be in the initial request.

optional—the parameter is optional but adding it to the request either makes the payment process more customer-friendly or helps to increase the percentage of successful payments.
Parameter Description

project_id
integer
strictly required

 Project ID you obtained from Monetix when integrating.

Example: 123

payment_id
string
strictly required

 Payment ID unique within your project.

Example: payment_47

customer_id
string
strictly required

 Unique ID of the customer within your project.

Example: customer_123

customer_first_name
string
strictly required

 Customer's first name.

Example: John

customer_last_name
string
strictly required

 Customer's last name.

Example: Doe

customer_email
string
strictly required

 Customer's email.

Example: johndoe@example.com

payment_currency
string
strictly required

 Code of the purchase currency in the ISO-4217 alpha-3 format.

Example: MYR

payment_amount
integer
strictly required

 Purchase amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units. If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 500 MYR must be sent as 50000

signature
string
strictly required

 Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

force_payment_method
string
optional

 Parameter that allows you to enforce the Boost payment method for your customer and skip the page with payment method selections.

To enforce the Boost payment method and skip the page with payment method selection, add the force_payment_method parameter to the request and set its value to boost. For more information about enforcing payment methods, see Preselecting payment methods.

Example: force_payment_method: 'boost'
You can also add any other optional parameters to the request, if necessary. For the list of all the parameters possible in requests to Payment Page, see Payment Page invocation parameters.

Here is an example of the data from a request to open the checkout page by using EPayWidget:

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

Callback

In the Boost payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Payment Page.

The following is an example of a callback body with information about a successfully completed purchase.

Figure 2. Example of the data from a successful purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

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

Figure 3. Example of the data from a declined purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 15923,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlfqz8155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

Purchase by using Gate

General information

To perform a purchase by using Gate with the Boost payment method:

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

The following figure provides the details of the purchase processing flow in the Boost payment method.

Figure 4. Purchase processing flow when performing a purchase by using Gate
  1. The customer initiates a purchase in your system.
  2. Your system sends the purchase request to Gate.
  3. The Monetix payment platform receives the request.
  4. The payment platform checks whether the request contains all the required parameters and correct signature.
  5. The payment platform sends you a response in which it acknowledges your request and provides the request validation result. (For more information about the response format, see Response structure.)
  6. Depending on the provider processing this payment, the purchase processing flow in the Boost payment method may be one of the following:
    • Option 1
      1. The payment platform processes the request and generates the data for redirecting the customer to the provider service.
    • Option 2
      1. The payment platform processes the request and forwards it to the provider service.
      2. The provider service processes the purchase request.
      3. The provider service sends the customer redirection data to the payment platform.
  7. The payment platform forwards the data to your system in the redirect_data object.
  8. Your system redirects the customer to the provider service.
  9. The customer completes the purchase.
  10. The provider service processes the purchase.
  11. The result is displayed to the customer.
  12. The provider service informs the payment platform about the purchase result.
  13. The payment platform sends the callback with the payment result to your system.
  14. Your system sends the payment result to the customer.

Request

This section provides the instructions on how to build the request for purchase with the Boost payment method.

HTTP request method POST
Request body format JSON
API endpoint /v2/payment/wallet/boost/sale
Full API endpoint specification /v2/payment/wallet/{payment_method}/sale
Table 2. Basic parameters of a purchase request

strictly required—the parameter must be in the initial request.

optional—the parameter is optional but adding it to the request either makes the payment process more customer-friendly or helps to increase the percentage of successful payments.
Object Parameter Description

general
object
strictly required

project_id
integer
strictly required

 Project ID you obtained from Monetix when integrating.

Example: 123

payment_id
string
strictly required

 Payment ID unique within your project.

Example: payment_47

signature
string
strictly required

 Signature created after you've specified all the request parameters. For more information about signature generation, see Signature generation and verification.

customer
object
strictly required

id
string
strictly required

 Unique ID of the customer within your project.

Example: customer_123

ip_address
string
strictly required

 IP address of the customer's device.

Example: 198.51.100.47

email
string
strictly required

 Customer's email.

Example: johndoe@example.com

first_name
string
strictly required

 Customer's first name.

Example: John

last_name
string
strictly required

 Customer's last name.

Example: Doe

payment
object
strictly required

amount
integer
strictly required

 Purchase amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units. If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 500 MYR must be sent as 50000

currency
string
strictly required

 Code of the purchase currency in the ISO-4217 alpha-3 format.

Example: MYR

return_url
object
optional

return
string
optional

 The URL to redirect the customer to when they prematurely terminate the payment. This URL is also used if the success and decline parameters are not specified in the request. 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.

Example: https://example.com/return/

success
string
optional

 The URL to redirect the customer to after the payment is successfully completed.

Example: https://example.com/success/

decline
string
optional

 The URL to redirect the customer to after the payment is declined.

Example: https://example.com/decline/
You can also add any other optional parameters to the purchase request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from a request to initiate a purchase with the Boost payment method.

Figure 5. Example of the data from a purchase request
{
    "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": 50000,
        "currency": "MYR"
    },
    "return_url": {
        "success": "https://example.com/success/",
        "decline": "https://example.com/decline/",
        "return": "https://example.com/return/"
    } 
}

Customer redirection

After receiving and processing your purchase request, the payment platform sends you the callback with the data for redirecting the customer to the provider 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 send in the request body
  • method—the HTTP method for retrieving the website page (for example, POST or GET)
  • encrypted—this is the service parameter. Ignore it.

Here is an example of the callback snippet with 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

In the Boost payment method, the payment platform returns the purchase result in a callback. For the information about the callback structure, see Callbacks in Gate.

The following is an example of a callback body with the information about a successfully completed purchase.

Figure 6. Example of the data from a successful purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

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

Figure 7. Example of the data from a declined purchase callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 15923,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlfqz8155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

Payout by using Gate

General information

To perform a payout by using Gate with the Boost payment method:

  1. Send a request with all the required parameters and signature to the Monetix URL.
  2. Accept a callback with the payout result from the payment platform.

The following picture provides the details of the payout processing flow in the Boost payment method.

Figure 8. Payout processing flow when performing a payout by using Gate
  1. The customer initiates a payout in your system.
  2. Your system sends the payout request to Gate.
  3. The Monetix payment platform receives the request.
  4. The payment platform checks whether the request contains all the required parameters and correct signature.
  5. The payment platform sends you a response in which it acknowledges your request and provides the request validation result. (For more information about the response format, see Response structure.)
  6. The payment platform processes the request and forwards it to the provider service.
  7. The provider service processes this request.
  8. The provider service informs the payment platform about the payout result.
  9. The payment platform sends a callback with the payout result to your system.
  10. Your system sends the payout result to the customer.

Request

This section provides the instructions on how to build the payout request through Gate by using the Boost payment method.

HTTP request method POST
Request body format JSON
API endpoint /v2/payment/wallet/boost/payout
Full API endpoint specification /v2/payment/wallet/{payment_method}/payout
Table 3. Basic parameters of a payout request

strictly required—the parameter must be in the initial request.
Object Parameter Description

general
object
strictly required

project_id
integer
strictly required

 Project ID you obtained from Monetix when integrating.

Example: 123

payment_id
string
strictly required

 Payment ID unique within your project.

Example: payment_47

signature
string
strictly required

 Signature created after you've specified all the request parameters. To learn about signature generation, see Signature generation and verification.

customer
object
strictly required

id
string
strictly required

 Unique ID of the customer within your project.

Example: customer_123

ip_address
string
strictly required

 IP address of the customer's device.

Example: 198.51.100.47

email
string
strictly required

 Customer's email.

Example: johndoe@example.com

first_name
string
strictly required

 Customer's first name.

Example: John

last_name
string
strictly required

 Customer's last name.

Example: Doe

payment
object
strictly required

amount
integer
strictly required

 Payout amount in minor currency units without any decimal point or comma except for the cases when the currency doesn't have any minor currency units. If the currency doesn't have any minor units (i.e. the number of digits for minor currency units is zero), set this parameter to the amount in the major currency units. To check whether the currency has any minor units, see Currency codes.

Example: 500 MYR must be sent as 50000

currency
string
strictly required

 Code of the payout currency in the ISO-4217 alpha-3 format.

Example: MYR

account
object
strictly required

number
string
strictly required

 Customer's account number.

Example: 1234567890
You can also add any other optional parameters to the payout request, if necessary. For the list of all the parameters available in Gate, see API Reference.

Here is an example of the data from a request to initiate a payout with the Boost payment method.

Figure 9. Example of payout request body
{
    "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"
    },
    "account": {
        "number": "1234567890"
    },
    "payment": {
        "amount": 50000,
        "currency": "MYR"
    }
}

Callback

In the Boost payment method, the payment platform returns the payout result in a callback. For the information about the callback structure, see Callbacks in Gate.

The following is an example of a callback body with the information about a successfully completed payout.

Figure 10. Example of the data from a successful payout callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2UuHp99rHrtaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

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

Figure 11. Example of the data from a declined payout callback
{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Boost",
        "sum": {
            "amount": 50000,
            "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": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 12345,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnlVlf155QSlXJKR4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Related topics

Payout by using Dashboard

To make a payout through Dashboard, the merchant sends a request and receives a notification with the request processing result. There are two ways to initiate payouts through Dashboard:
  • 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.

Analysis of payments results

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.