MOLPay

REST API

Please note that you can use the REST API documentation also for Wirecard Payment Page v1 LEGACY integration.

MOLPay is a type of Online Bank Transfer.

Countries and Currencies

Countries

China, Indonesia (coming soon), Malaysia, Philippines, Singapore, Thailand, Vietnam

Currencies

Processing: IDR, MYR, PHP, RMB/CNY, SGD, THB, VND
Settlement: local currency/USD
Available Payment Methods (Channels)

This table shows all available channels through which a consumer can make a payment:

Payment Method (Channel) Name Country Currency

alipay

Alipay

China

RMB/CNY/USD/MYR/SGD

cimbclicks

CIMB Clicks

Malaysia

MYR

maybank2u

Maybank2u

Malaysia

MYR

fpx_amonline

FPX B2C AmOnline

Malaysia

MYR

fpx_muamalat

FPX B2C Bank Muamalat

Malaysia

MYR

fpx_bankrakyat

FPX B2C Bank Rakyat

Malaysia

MYR

fpx_bimb

FPX B2C Bank Islam

Malaysia

MYR

dragonpay

Dragonpay

Philippines

PHP

fpx_abb

FPX B2C Affin Bank

Malaysia

MYR

fpx_abmb

FPX B2C Alliance Bank

Malaysia

MYR

fpx_bsn

FPX B2C Bank Simpanan Nasional

Malaysia

MYR

fpx_ocbc

FPX B2C OCBC

Malaysia

MYR

fpx_scb

FPX B2C Standard Chartered

Malaysia

MYR

fpx_uob

FPX B2C United Overseas Bank

Malaysia

MYR

fpx_hlbconnect

FPX B2C Hong Leong

Malaysia

MYR

nganluong

NganLuong

Vietnam

VND

omise

Omise

Thailand

THB

omise_bay

Krungsri e-Payment via Omise

Thailand

THB

omise_bbl

Bangkok Bank via Omise

Thailand

THB

omise_ktb

Krung Thai Bank via Omise

Thailand

THB

omise_scb

Siam Commercial Bank via Omise

Thailand

THB

omise_tl

Tesco Lotus via Omise

Thailand

THB

fpx_pbb

FPX B2C Public Bank

Malaysia

MYR

fpx_rhbnow

FPX B2C RHB Bank

Malaysia

MYR

singpost

SAM by SingPost

Singapore

SGD

UPOP

UnionPay

China

CNY/USD/MYR

vtcpay

VTC Pay

Vietnam

VND
Communication Formats

This table illustrates how MOLPay notifications are encoded and which formats and methods can be used for requests and responses.

Requests/Responses

Format

XML, JSON

Methods

POST

IPN Encodement

Please follow the instructions given at Instant Payment Notification to set up IPN.
Transaction Types

This table lists all transaction types available for MOLPay.

For transaction type details which are not given here, look at Transaction Types.

Transaction Type Description Request Response/IPN WEP Link to sample

debit

Creates a request to charge the specified amount from the consumer’s bank account.

YES

YES

YES

debit sample

get-url

Retrieves the URL of the MOLPay landing page for the consumer to be redirected to.

NO

YES

YES

YES indicates that the transaction type is sent in the request, in the response/notification or in the Wirecard Enterprise Portal.

Test Credentials

URL (Endpoint)

For transaction type debit (REST API)

https://api-test.wirecard.com/engine/rest/paymentmethods/

Merchant Account ID (MAID)

0518ac4e-a622-48d8-87f5-a04835ded715

Username

Molpay-EETest

Password

he04YtvH

Secret Key

39c6793b-888b-4dd6-a5ac-f6b844418451
Workflow
debit
Payment Process Using REST API
Debit Workflow with REST API

  1. Consumer initiates a debit transaction.

  2. Merchant sends a request to the WPG endpoint. This request must contain

    • the transaction type debit

    • the selected payment method (channel)

    • the consumer’s data

    • payment data.

  3. WPG sends a response to merchant. This response contains a generated URL for MOLPay's landing page (field “payment-methods/payment-method/@url”).

  4. With this URL, the merchant redirects the consumer to MOLPay's landing page.

  5. The consumer submits the transaction on MOLPay's landing page and is redirected to their online banking system.

  6. The consumer finishes the payment in their online banking system. Optionally, the consumer can be redirected back to the shop.

  7. WPG sends a success/failure notification to the merchant.

Payment Process Using HPP
Debit Workflow with HPP

  1. Consumer selects one of the MOLPay payment methods (channel).

  2. WPG redirects the consumer to MOLPay's landing page.

  3. The consumer submits the transaction on MOLPay's landing page and is redirected to their online banking system.

  4. The consumer finishes the payment in their online banking system. Optionally, the consumer can be redirected back to the shop.

  5. WPG sends a success/failure notification to the merchant.

Fields

The fields used for MOLPay requests, responses and notifications are the same as the REST API Fields. Please refer to the REST API field list or the request example for the fields required in a debit transaction.

Samples
debit
XML debit Request (Successful)
<payment xmlns="http://www.elastic-payments.com/schema/payment">
  <merchant-account-id>0518ac4e-a622-48d8-87f5-a04835ded715</merchant-account-id>
  <request-id>{{$guid}}</request-id>
  <transaction-type>debit</transaction-type>
  <requested-amount currency="MYR">10</requested-amount>
  <account-holder>
    <first-name>John</first-name>
    <last-name>Doe</last-name>
    <email>john@doe.com</email>
    <phone>+123456789</phone>
  </account-holder>
  <descriptor>description</descriptor>
  <payment-methods>
    <payment-method name="fpx_abb"/>
  </payment-methods>
  <country>MY</country>
  <cancel-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/cancel</cancel-redirect-url>
  <fail-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/error</fail-redirect-url>
  <success-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/success</success-redirect-url>
</payment>
XML debit Response (Successful)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<payment xmlns="http://www.elastic-payments.com/schema/payment">
    <merchant-account-id>0518ac4e-a622-48d8-87f5-a04835ded715</merchant-account-id>
    <transaction-id>f3efe8e4-c1eb-4600-878b-b1df4f9beef3</transaction-id>
    <request-id>e8537162-91d7-4ffe-8623-1f2f7ea69d88</request-id>
    <transaction-type>debit</transaction-type>
    <transaction-state>success</transaction-state>
    <completion-time-stamp>2019-07-09T09:15:28.000Z</completion-time-stamp>
    <statuses>
        <status code="201.0000" description="The resource was successfully created." severity="information"/>
    </statuses>
    <requested-amount currency="MYR">10</requested-amount>
    <account-holder>
        <first-name>John</first-name>
        <last-name>Doe</last-name>
        <email>john@doe.com</email>
        <phone>+123456789</phone>
    </account-holder>
    <descriptor>description</descriptor>
    <payment-methods>
        <payment-method url="https://sandbox.molpay.com/MOLPay/pay/SB_wirecard/FPX_ABB.php?amount=10&amp;orderid=f3efe8e4c1eb4600878bb1df4f9beef3&amp;cur=MYR&amp;vcode=a480484d84ea0ec762b95af7cad2cef4&amp;bill_desc=description&amp;bill_mobile=%2B123456789&amp;bill_email=john%40doe.com&amp;bill_name=John+Doe&amp;cancelurl=https%3A%2F%2Fapi-test.wirecard.com%3A443%2Fengine%2Fnotification%2Fmolpay%2Fredirect" name="fpx_abb"/>
    </payment-methods>
    <cancel-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/cancel</cancel-redirect-url>
    <fail-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/error</fail-redirect-url>
    <success-redirect-url>https://demoshop-test.wirecard.com/demoshop/#/success</success-redirect-url>
    <country>MY</country>
</payment>
XML debit Request (Failure)
<payment xmlns="http://www.elastic-payments.com/schema/payment">
  <merchant-account-id>0518ac4e-a622-48d8-87f5-a04835ded715</merchant-account-id>
  <request-id>17b0f1b1-00b1-4e14-a4c4-8f3f80a4085b</request-id>
  <transaction-type>debit</transaction-type>
  <requested-amount currency="MYR">10</requested-amount>
  <account-holder>
    <first-name>John</first-name>
    <last-name>Doe</last-name>
    <email>john.doe</email>
    <phone>+123456789</phone>
  </account-holder>
  <descriptor>description</descriptor>
  <payment-methods>
    <payment-method name="fpx_abb"/>
  </payment-methods>
  <country>MY</country>
</payment>
XML debit Response (Failure)
<payment xmlns="http://www.elastic-payments.com/schema/payment" xmlns:ns2="http://www.elastic-payments.com/schema/epa/transaction">
  <merchant-account-id>0518ac4e-a622-48d8-87f5-a04835ded715</merchant-account-id>
  <transaction-id>dfb68a27-65de-4682-98d2-17e83c532116</transaction-id>
  <request-id>17b0f1b1-00b1-4e14-a4c4-8f3f80a4085b</request-id>
  <transaction-type>debit</transaction-type>
  <transaction-state>failed</transaction-state>
  <completion-time-stamp>2018-10-16T09:47:30.000Z</completion-time-stamp>
  <statuses>
    <status code="400.1016" description="The Email Address is syntactically incorrect.  Please check your input and try again." severity="error"/>
  </statuses>
  <requested-amount currency="MYR">10</requested-amount>
  <account-holder>
    <first-name>John</first-name>
    <last-name>Doe</last-name>
    <email>john.doe</email>
    <phone>+123456789</phone>
  </account-holder>
  <descriptor>description</descriptor>
  <payment-methods>
    <payment-method name="fpx_abb"/>
  </payment-methods>
  <country>MY</country>
</payment>

← moip Pagamentos | moneta.ru →