Alipay+Alipay+

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 name

Enum value

pspId / counterParticipantId

customerId provided

Payment scenario

Cashier Payment

Auto Debit

User-presented Mode Payment

Merchant-presented Mode Payment

Alipay

ALIPAY_CN

1022088000000000001

Yes





TrueMoney Wallet

TRUEMONEY

1022167000000000001

Yes





AlipayHK

ALIPAY_HK

1022160000000000000

Yes





TNG eWallet

TNG

1022171000000000001

Yes





GCash

GCASH

1022170000000000000

Yes





DANA

DANA

1022166000000000001

Yes





Kakao Pay

KAKAOPAY

1022172000000000001

Yes





Rabbit LINE Pay

RABBIT_LINE_PAY

2021226300000000

Yes



  • 🔲
  • 🔲

BPI

BPI

2010BOPI00000000

No


  • 🔲
  • 🔲
  • 🔲

Boost

BOOST

2021227800000000

Yes



  • 🔲
  • 🔲

Akulaku PayLater

AKULAKU_PAYLATER

2021241800000000

Yes


  • 🔲
  • 🔲
  • 🔲

HelloMoney by AUB

AUB

A010AUBK00000000

Yes

  • 🔲
  • 🔲


Note: For each MPP, the value of the pspId parameter is the same as that of the counterParticipantId parameter used in Transaction Detail Report.

Cashier Payment

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

MPP name

Terminal type

APP

WAP

Web

Mini Program

Alipay


  • 🔲


TrueMoney Wallet


  • 🔲


AlipayHK





TNG eWallet





GCash





DANA





Kakao Pay


  • 🔲

  • 🔲

Rabbit LINE Pay


  • 🔲

  • 🔲

BPI

  • 🔲


  • 🔲

Boost




  • 🔲
Akulaku PayLater



  • 🔲

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 name

Terminal type

Authorization

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.5 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

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.

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 (User-presented Mode Payment)

pay (Merchant-presented Mode Payment Entry Code)

pay (Merchant-presented Mode Payment Order Code)

Valid value

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

  • TRUEMONEY
  • ALIPAY_HK
  • TNG
  • ALIPAY_CN
  • GCASH
  • DANA

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

Valid value

  • TRUEMONEY
  • ALIPAY_HK
  • TNG
  • ALIPAY_CN
  • GCASH
  • DANA
  • KAKAOPAY
  • RABBIT_LINE_PAY
  • BPI
  • BOOST
  • AKULAKU_PAYLATER
  • AUB
  • TRUEMONEY
  • ALIPAY_HK
  • TNG
  • ALIPAY_CN
  • GCASH
  • DANA
  • KAKAOPAY
  • RABBIT_LINE_PAY
  • BPI
  • BOOST
  • AKULAKU_PAYLATER
  • AUB

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

Valid value

  • CONNECT_WALLET
  • TRUEMONEY
  • ALIPAY_HK
  • TNG
  • ALIPAY_CN
  • GCASH
  • DANA
  • KAKAOPAY
  • RABBIT_LINE_PAY
  • BOOST
  • CONNECT_WALLET
  • TRUEMONEY
  • ALIPAY_HK
  • TNG
  • ALIPAY_CN
  • GCASH
  • DANA
  • KAKAOPAY
  • RABBIT_LINE_PAY
  • BOOST

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.