MPP capabilities

This topic introduces the varying capabilities of Mobile Payment Providers (MPPs) in different payment scenarios and lists the API parameters that use MPP enum values as valid values.

Overview

The following table shows the enum value and pspId of each MPP, whether the MPP provides customerId, and the payment scenarios that are supported by different MPPs.

MPP brand name (walletBrandName)	Enum value	pspId/counterParticipantId	Payment scenario
MPP brand name (walletBrandName)	Enum value	pspId/counterParticipantId	Cashier Payment	Auto Debit	User-presented Mode	Merchant-presented Mode
Alipay	`ALIPAY_CN`	1022088000000000001	✅	✅	✅	✅
TrueMoney Wallet	`TRUEMONEY`	1022167000000000001	✅	✅	✅	✅
AlipayHK	`ALIPAY_HK`	1022160000000000000	✅	✅	✅	✅
TNG eWallet	`TNG`	1022171000000000001	✅	✅	✅	✅
GCash	`GCASH`	1022170000000000000	✅	✅	✅	✅
DANA	`DANA`	1022166000000000001	✅	✅	🔲	🔲
Kakao Pay	`KAKAOPAY`	1022172000000000001	✅	✅	✅	✅
Rabbit LINE Pay	`RABBIT_LINE_PAY`	2021226300000000	✅	✅	🔲	🔲
BPI	`BPI`	2010BOPI00000000	✅	🔲	🔲	🔲
Boost	`BOOST`	2021227800000000	✅	✅	🔲	🔲
Akulaku PayLater	`AKULAKU_PAYLATER`	2021241800000000	✅	🔲	🔲	🔲
HelloMoney by AUB	`HELLOMONEY_BY_AUB`	A010AUBK00000000	🔲	🔲	✅	✅
BillEase	`BILLEASE`	A111253000000000	✅	🔲	🔲	🔲
Tinaba	`TINABA`	2021224000000000	✅	🔲	✅	✅
NAVER Pay	`NAVERPAY`	2021234400000000	✅	✅	✅	✅
Toss	`TOSSPAY`	A111254300000000	✅	🔲	✅	✅
OCBC	`OCBC`	A111263900000000	🔲	🔲	✅	✅
CHANGIPAY	`CHANGIPAY`	A111265200000000	🔲	🔲	✅	✅
HiPay	`HIPAY`	A111265400000000	✅	✅	✅	✅
MyPB	`PBENGAGEMY`	A111265500000000	🔲	🔲	✅	✅
MPay	`MPAY`	A111253100000000	✅	✅	✅	✅
Maya	`MAYA`	A111254900000000	🔲	✅	🔲	🔲
GrabPay SG	`GRABPAY_SG`	A111247200000000	🔲	✅	🔲	🔲
KREDIVO ID	`KREDIVO_ID`	A111256400000000	✅	🔲	🔲	🔲
Kaspi.kz	`KASPI_KZ`	A111266400000000	🔲	🔲	✅	✅
BigPay	`BIGPAY_MY`	A111274400000000	🔲	🔲	✅	✅
BigPay	`BIGPAY_TH`	A111274500000000	🔲	🔲	✅	✅
BigPay	`BIGPAY_SG`	A111274300000000	🔲	🔲	✅	✅
K PLUS	`KPLUS`	A111266800000000	✅	✅	✅	✅
Zalopay	`ZALOPAY`	A111275800000000	🔲	🔲	✅	✅
Bluecode	`BLUECODE`	A111271200000000	🔲	🔲	✅	✅
NayaPay	`NAYAPAY`	A111265600000000	🔲	🔲	✅	✅
SCB Planet Plus	`SCB_PLANET_PLUS`	A111265800000000	🔲	🔲	✅	✅

Note: For each MPP:
the MPP brand name is specified by the value of the walletBrandName parameter.
the value of the pspId parameter is the same as that of the counterParticipantId parameter used in the Transaction Detail Report.

Cashier Payment

The following table lists the terminal types supported by different MPPs in Cashier Payment.

MPP brand name	Terminal type
MPP brand name	APP	WAP	Web	Mini Program
Alipay	✅	🔲	✅	✅
TrueMoney Wallet	✅	🔲	✅	✅
AlipayHK	✅	✅	✅	✅
TNG eWallet	✅	✅	✅	✅
GCash	✅	✅	✅	✅
DANA	✅	✅	✅	✅
Kakao Pay	✅	🔲	✅	🔲
Rabbit LINE Pay	✅	🔲	✅	🔲
BPI	🔲	✅	✅	🔲
Boost	✅	✅	✅	🔲
Akulaku PayLater	✅	✅	✅	🔲
BillEase	✅	✅	✅	🔲
Tinaba	✅	✅	✅	🔲
NAVER Pay	🔲	✅	✅	🔲
Toss	✅	🔲	✅	✅
MPay	✅	✅	✅	🔲
KREDIVO ID	✅	🔲	✅	🔲
K PLUS	✅	✅	✅	🔲
HiPay	✅	✅	✅	✅

Note: The MPPs that support Web as terminal type also support scan-to-pay, except:
DANA
BPI
Boost
Akulaku PayLater
BillEase

Auto Debit

The following table lists the terminal types supported by different MPPs in Auto Debit and the effective periods of the access tokens provided by the MPPs.

MPP brand name	Terminal type			Authorization
MPP brand name	APP	WAP	Web	accessToken	refreshToken
Alipay	✅	🔲	✅	Long-term effective: 100 years	N/A
TrueMoney Wallet	✅	✅	✅	Short-term effective: 2 years	Short-term effective: 2.5 years
AlipayHK	✅	✅	✅	Long-term effective: 15 years	Long-term effective: 15 years
TNG eWallet	✅	✅	✅	Short-term effective: 2 years	Short-term effective: 2.5 years
GCash	✅	✅	✅	Short-term effective: 2 years	Short-term effective: 2 years
DANA	✅	✅	✅	Long-term effective: 10 years	Long-term effective: 10 years
Kakao Pay	✅	🔲	✅	Long-term effective: 100 years	N/A
Rabbit LINE Pay	✅	🔲	✅	Long-term effective: 27 years	Long-term effective: 27 years
Boost	✅	✅	✅	Short-term effective: 1 year	Short-term effective: 1.5 years
NAVER Pay	🔲	✅	✅	Short-term effective: 1 year (automatically refreshed as long as there is a transaction)	N/A
MPay	✅	✅	✅	Long-term effective: 100 years	Long-term effective: 100 years
Maya	✅	✅	✅	Short-term effective: 1 year	Short-term effective: 1.5 year
GrabPay SG	🔲	✅	✅	Long-term effective: 10 years	Long-term effective: 10 years
K PLUS	✅	🔲	✅	Long-term effective: 100 years	N/A
HiPay	✅	✅	✅	Long-term effective: 10 years	N/A

Differences between AlipayCN and other Alipay+ MPPs

The following table lists the differences between AlipayCN and other Alipay+ MPPs in terms of registration, reconciliation, and customs declaration.

Item	AlipayCN	Other Alipay+ MPPs
Registration	Required in all payment scenarios	Required only in Cashier Payment and Auto Debit
Reconciliation	A dedicated set of reports is provided for AlipayCN. The file structure/directory/filename rules are the same as those provided for other Alipay+ MPPs, only the partner agreement ID is different in the filename.	One set of financial reports is provided for all other Alipay+ MPPs.
Reconciliation	Alipay+ sends the settlement funds to the ACQP separately for AlipayCN transactions. The settlement cycle, settlement calendar, and minimum settlement amount are different, following AlipayCN settlement generation rules. By default, AlipayCN settles on every T+1 day.	By default, the other Alipay+ MPPs settle on every T+2 day.
Customs declaration	Required in e-commerce scenarios.	Not required

MPP enum values as valid values

The following tables list the API parameters that use MPP enum names as valid values.

paymentMethod.paymentMethodType

The following table lists the APIs that involve the paymentMethod.paymentMethodType parameter and its valid values in the APIs.

API name

pay (Cashier Payment)

pay (Auto Debit)

pay (UPM)

pay (MPM Entry Code)

pay (MPM Order Code)

When the terminal type is mini program, valid values are:

TRUEMONEY
ALIPAY_HK
TNG
ALIPAY_CN
GCASH
DANA
TOSS
HIPAY

When the terminal type is not mini program, valid value is:

CONNECT_WALLET

CONNECT_WALLET

CONNECT_WALLET

CONNECT_WALLET

CONNECT_WALLET

Note: CONNECT_WALLET indicates Alipay+ MPPs and is used when the specific MPP is unknown or more than one MPP is used. For more information about the MPPs and their enum values, see the Overview table above.

pspRegistrationResultList.pspName

The following table lists the APIs that involve the pspRegistrationResultList.pspName parameter and its valid values in the APIs.

API name
inquiryRegistrationStatus	notifyRegistrationStatus
`TRUEMONEY` `ALIPAY_HK` `TNG` `ALIPAY_CN` `GCASH` `DANA` `KAKAOPAY` `RABBIT_LINE_PAY` `BPI` `BOOST` `AKULAKU_PAYLATER` `HELLOMONEY_BY_AUB` `BILLEASE` `TINABA` `NAVERPAY` `TOSSPAY` `OCBC` `CHANGIPAY` `HIPAY` `PBENGAGEMY` `MPAY` `MAYA` `GRABPAY_SG` `KREDIVO_ID` `KASPI_KZ` `BIGPAY_MY` `BIGPAY_TH` `BIGPAY_SG` `KPLUS` `ZALOPAY` `BLUECODE` `NAYAPAY` `SCB_PLANET_PLUS`	`TRUEMONEY` `ALIPAY_HK` `TNG` `ALIPAY_CN` `GCASH` `DANA` `KAKAOPAY` `RABBIT_LINE_PAY` `BPI` `BOOST` `AKULAKU_PAYLATER` `HELLOMONEY_BY_AUB` `BILLEASE` `TINABA` `NAVERPAY` `TOSSPAY` `OCBC` `CHANGIPAY` `HIPAY` `PBENGAGEMY` `MPAY` `MAYA` `GRABPAY_SG` `KREDIVO_ID` `KASPI_KZ` `BIGPAY_MY` `BIGPAY_TH` `BIGPAY_SG` `KPLUS` `ZALOPAY` `BLUECODE` `NAYAPAY` `SCB_PLANET_PLUS`

Note: For more information about the MPPs and their enum values, see the Overview table above.

walletForAccountBinding.walletName

The following table lists the APIs that involve the walletForAccountBinding.walletName parameter and its valid values in the APIs.

API name
authNotify	applyToken
`CONNECT_WALLET` `TRUEMONEY` `ALIPAY_HK` `TNG` `ALIPAY_CN` `GCASH` `DANA` `KAKAOPAY` `RABBIT_LINE_PAY` `BOOST` `NAVERPAY` `MPAY` `MAYA` `GRABPAY_SG` `KPLUS` `HIPAY`	`CONNECT_WALLET` `TRUEMONEY` `ALIPAY_HK` `TNG` `ALIPAY_CN` `GCASH` `DANA` `KAKAOPAY` `RABBIT_LINE_PAY` `BOOST` `NAVERPAY` `MPAY` `MAYA` `GRABPAY_SG` `KPLUS` `HIPAY`

Note: CONNECT_WALLET indicates Alipay+ MPPs and is used when the specific MPP is unknown or more than one MPP is used. For more information about the MPPs and their enum values, see the Overview table above.