Alipay+ DocsAlipay+ Docs

tokenDigitizeDecisionAlipay+ → MPP

Alipay+ calls the tokenDigitizeDecision API to provide the Mobile Payment Provider (MPP) with provisioning and risk data to support its decision-making and to retrieve applicable activation method details when additional authentication is required.

Structure

A message consists of a header and body. The following sections are focused on the body structure. For the header structure, see:

Note:

  • Set the data type of each parameter (except array) as String. This means that you must use double quotation marks (" ") to enclose the parameter value. Examples:
    • If the data type of a parameter is Integer and its value is 20, set it as "20".
    • If the data type of a parameter is Boolean and its value is true , set it as "true".  
  • For optional parameters that are not required in your case, you can take one of the following actions:
    • Exclude the parameters from the request body.
    • Set the parameter values as null  (without the double quotation marks). 

Do NOT leave the optional parameters empty by setting their values as ""; otherwise, an error might occur. 

Request parameters

tokenReferenceId String  REQUIRED

The unique ID assigned by Alipay+ to identify a token when it is created.

More information:

  • Maximum length: 64 characters

customerId String  

The unique ID that is assigned by the MPP to identify a user.

More information:

  • Maximum length: 64 characters

tokenType String  REQUIRED

The token type.

Valid values are:

  • EMBEDDED_SE: embedded secure element
  • CLOUD: Mastercard cloud-based payments
  • STATIC: static token

walletId String  

The unique ID used to identify the wallet provider requesting the token digitization.

More information:

  • Maximum length: 16 characters

tokenRequestorId String  

The unique ID used to identify the token requestor requesting the token digitization.

More information:

  • Maximum length: 16 characters

consumerFacingEntityName String  

The name of the entity where the user stores their tokens (e.g., a specific wallet, merchant, or platform).

More information:

  • Maximum length: 128 characters

paymentAppInstanceId String  

The unique ID of the payment app instance on the device. This parameter is provided when supplied by a wallet provider.

More information:

  • Maximum length: 64 characters

accountSource String  

The source of this account information.

Valid values are:

  • ACCOUNT_ON_FILE: Pre-stored account.
  • ACCOUNT_ADDED_MANUALLY: Manually entered by the user.
  • ACCOUNT_ADDED_VIA_APPLICATION: Added via another app (e.g., banking app).
  • EXISTING_TOKEN_CREDENTIAL: Derived from an existing token.
  • ACCOUNT_ADDED_VIA_BROWSER: Added via a web browser.
  • ACCOUNT_ADDED_VIA_CHIP_DATA: Added via chip data, including contactless Mastercard chip data.

accountHolder AccountHolder  

Additional information used to identify the account holder.

Show child parameters

accountIdHash String  

The SHA-256 hash of the account holder's ID. The ID is provided by the MPP and typically is an email address.

More information:

  • Maximum length: 64 characters

mobileNumberSuffix String  

The last digits of the device's mobile phone number, typically the last 4 digits.

More information:

  • Maximum length: 32 characters

walletProviderDecisioningInfo WalletProviderDecisioningInfo  

Risk recommendations from the wallet provider to support the MPP's decision.

Show child parameters

deviceInfo DeviceInfo  

Information about the device where the account has been digitized.

Show child parameters

associatedToken AssociatedToken  

Information about an existing token associated with the current digitization request.

Show child parameters

aplusDecisioningInfo AplusDecisioningInfo  

Risk recommendations from Alipay+ to support the MPP's decision.

Show child parameters

Response parameters

result Result  REQUIRED

The result of the business processing, including the result code, result status, and result message. For more information about how to return the result in different payment scenarios, see How to return the result in the More information section of this topic.

Show child parameters

activationMethods Array<ActivationMethod>  

The set of activation methods to be used for this digitization.

Show child parameters

decision String  

The authorization decision for the service request.

This parameter is returned if the value of result.resultCode is SUCCESS.

Valid values are:

  • APPROVED: The service request is approved.
  • REQUIRE_ADDITIONAL_AUTHENTICATION: The service request requires additional authentication to be approved. One or more activation methods should be provided.
  • DECLINED: The service request is declined.
API Explorer

Request

Request Body

Response

Response Body

More information

How to return the result

According to the request processing result, the MPP needs to return the corresponding result (specified by the result parameter):

  • If the business processing succeeds, set the value of result.resultStatus to S and the value of result.resultCode to SUCCESS.
  • If the business processing fails, set the value of result.resultStatus to F and the value of result.resultCode accordingly.
  • If the business processing result is unknown, set the value of result.resultStatus to U and the value of result.resultCode accordingly.

For more information about how to define your result codes, see the Result codes section below.

Result/Error codes

CodeValueMessageFurther action
SUCCESSSSuccess

ACCESS_DENIEDFAccess is denied.
INVALID_SIGNATUREFThe signature is invalid.
INVALID_CLIENTFThe client is invalid.


KEY_NOT_FOUNDFThe key is not found.
MEDIA_TYPE_NOT_ACCEPTABLEFThe server does not implement the media type that is acceptable to the client.
METHOD_NOT_SUPPORTEDFThe server does not implement the requested HTTP method.
NO_INTERFACE_DEFFAPI is not defined.
PARAM_ILLEGALFIllegal parameters exist. For example, a non-numeric input, or an invalid date.
USER_NO_ACTIVATE_METHODFUser has no available activation method.
PROCESS_FAILFA general business failure occurred. Don't retry.
USER_NOT_EXISTFThe user does not exist.
USER_STATUS_ABNORMALFThe user status is abnormal.
REQUEST_TRAFFIC_EXCEED_LIMITUThe request traffic exceeds the limit.
UNKNOWN_EXCEPTION UAn API calling is failed, which is caused by unknown reasons.