Payment-method icon

FPX Online banking Malaysia for API only

Add FPX Online banking Malaysia to an existing API-only integration.

Accept FPX Online banking payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Requirements

Requirement Description
Integration type Make sure that you have built an API-only integration.
Setup steps Before you begin, add in your test Customer Area.

Build your payment form for Online banking Malaysia

To show FPX Online banking in your payment form, you need to:

  1. Show a list of available banks to your shopper.
  2. After the shopper selects a bank, pass the corresponding Issuer value to your server. You'll need this to make a payment. All issuers in this list must be included on your checkout to be compliant with PayNet local regulations.
Bank name Issuer ID
Affin Bank fpx_abb
Agro Bank fpx_agrobank
Alliance Bank fpx_abmb
Am Bank fpx_amb
Bank Islam fpx_bimb
Bank Muamalat fpx_bmmb
Bank Rakyat fpx_bkrm
Bank Simpanan Nasional fpx_bsn
CIMB Bank fpx_cimbclicks
Hong Leong Bank fpx_hlb
HSBC Bank fpx_hsbc
Kuwait Finance House fpx_kfh
Maybank fpx_mb2u
OCBC Bank fpx_ocbc
Public Bank fpx_pbb
RHB Bank fpx_rhb
Standard Chartered Bank fpx_scb
UOB Bank fpx_uob

We provide logos for Razer Merchant Services and the issuing banks, which you can use on your payment form. For more information, refer to Downloading logos.

You can also get the issuer list from the /paymentMethods response, as explained in the API-only integration guide.

In your /paymentMethods request, specify:

The list of issuing banks are included in the object with type: molpay_ebanking_fpx_MY.

Make a payment

In your /payments request, specify:

  • paymentMethod.type: molpay_ebanking_fpx_MY.
  • paymentMethod.issuer: The shopper's bank. In this example, the issuer is set to Bank Rakyat. Specify this with the Issuer value that corresponds to this bank.
  • returnUrl: The URL where the shopper will be redirected back to after they complete the payment.

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

Handle the redirect

  1. To complete the payment, redirect the shopper to the action.url returned in the /payments response, taking into account the following recommendations:

    • When using the HTTP GET method:
      For security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.

    • Redirection for mobile integrations:
      For mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.

  2. After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:

    • details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.

  3. In the response note the following:

    • resultCode: use this to present the result to your shopper.
    • pspReference: our unique identifier for the transaction.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for MOLPay online banking are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
You will receive the funds in 2-3 days.
Cancelled The shopper cancelled the payment while on their bank's website. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment. You'll receive a refusalReason in the same response, indicating the cause of the error.
Pending or
Received		 The shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the MOLPay online banking payments network to confirm this. Inform the shopper that you have received their order, and are waiting for the payment to be completed.
You will receive the final result of the payment in an AUTHORISATION webhook.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.

If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment:

eventCode success field Description Action to take
AUTHORISATION false The transaction failed. Cancel the order and inform the shopper that the payment failed.
AUTHORISATION true The shopper successfully completed the payment. Inform the shopper that the payment has been successful and proceed with the order.

Test and go live

Using any issuer ID that is available for the Online banking Malaysia Component for the respective country/region, make Online banking Malaysia online banking test payments to test the different payment results.

Check the status of the Online banking Malaysia test payments in your Customer Area > Transactions > Payments.

Before you can accept live Online banking Malaysia payments, you need to submit a request for Online banking Malaysia in your live Customer Area.

See also