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 | customerId provided | Payment scenario | |||
Cashier Payment | Auto Debit | User-presented Mode | Merchant-presented Mode | ||||
Alipay |
| 1022088000000000001 | Yes |
|
|
|
|
TrueMoney Wallet |
| 1022167000000000001 | Yes |
|
|
|
|
AlipayHK |
| 1022160000000000000 | Yes |
|
|
|
|
TNG eWallet |
| 1022171000000000001 | Yes |
|
|
|
|
GCash |
| 1022170000000000000 | Yes |
|
|
|
|
DANA |
| 1022166000000000001 | Yes |
|
|
|
|
Kakao Pay |
| 1022172000000000001 | Yes |
|
|
|
|
Rabbit LINE Pay |
| 2021226300000000 | Yes |
|
|
|
|
BPI |
| 2010BOPI00000000 | No |
|
|
|
|
Boost |
| 2021227800000000 | Yes |
|
|
|
|
Akulaku PayLater |
| 2021241800000000 | Yes |
|
|
|
|
HelloMoney by AUB |
| A010AUBK00000000 | Yes |
|
|
|
|
BillEase |
| A111253000000000 | Yes |
|
|
|
|
Tinaba |
| 2021224000000000 | Yes |
|
|
|
|
NAVER Pay |
| 2021234400000000 | Yes |
|
|
|
|
Toss |
| A111254300000000 | Yes |
|
|
|
|
OCBC |
| A111263900000000 | Yes |
|
|
|
|
CHANGIPAY |
| A111265200000000 | Yes |
|
|
|
|
Hipay |
| A111265400000000 | Yes |
|
|
|
|
MyPB |
| A111265500000000 | Yes |
|
|
|
|
MPay |
| A111253100000000 | Yes |
|
|
|
|
Maya |
| A111254900000000 | Yes |
|
|
|
|
GrabPay SG |
| A111247200000000 | Yes |
|
|
|
|
KREDIVO ID |
| A111256400000000 | Yes |
|
|
|
|
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 | |||
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 |
|
|
|
|
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 | |||
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 |
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 (UPM) | pay (MPM Entry Code) | pay (MPM Order Code) |
When the terminal type is mini program, valid values are:
When the terminal type is not mini program, valid value is:
|
|
|
|
|
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 |
|
|
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 |
|
|
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.