FPX Online banking Malaysia Android Component

Add FPX Online banking Malaysia to an existing Components integration.

If you are using Android Components v5.0.0 or later:

This payment method requires no additional configuration.

Follow the Components integration guide and use the following module and Component names:

To import the module: molpay
To launch and show the Component: MolpayComponent

Our Online banking Malaysia Component renders Online banking Malaysia in your payment form and collects your shopper's selected bank.

When making an Online banking Malaysia payment, you additionally need to:

Handle the redirect.

Requirements

Requirement	Description
Integration type	Make sure that you have an existing Advanced flow Android Components integration.
Setup steps	Before you begin, add in your Customer Area.

Show Online banking Malaysia in your payment form

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

Specify in your /paymentMethods request:
- countryCode: MY
- amount.currency: MYR
Deserialize the response from the /paymentMethods call and get the object with type: molpay_ebanking_fpx_MY or molpay_ebanking_TH.

Add the Online banking Malaysia Component:

a. Import the Online banking Malaysia Component to your build.gradle file.

implementation "com.adyen.checkout:molpay:<latest-version>"

Check the latest version on GitHub.

b. Create an molpayConfiguration object:

val molpayConfiguration =
 MolpayConfiguration.Builder(context, "YOUR_CLIENT_KEY")
     // When you are ready to accept live payments, change the value to one of our live environments.
     .setEnvironment(Environment.TEST)
     .build()

c. Initialize the Online banking Malaysia Component. Pass the payment method object and the molpayConfiguration object.

val molpayComponent = MolpayComponent.PROVIDER.get(this@YourActivity, paymentMethod, molpayConfiguration)

d. Add the Online banking Malaysia Component view to your layout.

<com.adyen.checkout.molpay.MolpaySpinnerView
   android:layout_width="wrap_content"
   android:layout_height="wrap_content"/>

e. Attach the Component to the view to start getting your shopper's payment details.

molpaySpinnerView.attach(molpayComponent, this@YourActivity)

f. When shoppers enter their payment details, you start receiving updates. If isValid is true and the shopper proceeds to pay, pass the paymentComponentState.data.paymentMethod to your server and make a payment request.

molpayComponent.observe(this) { paymentComponentState ->
  if (paymentComponentState?.isValid == true) {
     // When the shopper proceeds to pay, pass the `paymentComponentState.data` to your server to send a /payments request
     sendPayment(paymentComponentState.data)
  }
}

Make a payment

When the shopper proceeds to pay, the Component returns the paymentComponentState.data.paymentMethod.

Pass the paymentComponentState.data.paymentMethod to your server.
From your server, make a /payments request, specifying:
- paymentMethod.type: The paymentComponentState.data.paymentMethod from your client app. In this example, the issuer is set to Bank Rakyat.
- returnURL: URL to where the shopper should be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).

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

Pass the action object to your client app. You need this to initialize the Redirect Component.

Handle the redirect

Use the Redirect Component to redirect the shopper to the issuing bank's app or website.
After the shopper returns to your app, make a POST /payments/details request from your server, providing:
- details: The actionComponentData.details object from the Redirect Component.

You receive a response containing:

resultCode: Use this to present the payment 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 MOLPay eBanking Component for the respective country/region, make MOLPay online banking test payments to test the different payment results.

Check the status of the MOLPay test payments in your Customer Area > Transactions > Payments.

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