Google In-App Push Provisioning - Field Descriptions

The following page details each of the fields sent in the request and received in the response when using the Google Unified Push Provisioning endpoint.

Request Fields

The following table describes fields that can be included in the body of the request when using the Google Unified Push Provisioning endpoint.

FieldDescriptionLengthTypeMandatory?
clientWalletProviderThe Token Requestor’s ID (TRID). Only required for Visa.50StringConditional
clientWalletAccountIDClient-provided consumer ID that identifies the Wallet Account Holder entity.
Only required for Visa.
24StringConditional
clientDeviceIDThe stable device identifier set by the Wallet Provider. This can be a computer identifier or ID tied to hardware such as TEE_ID or SE_ID. Required by Visa push provisioning.24StringConditional
clientAppIDUnique identifier for the client application, used to provide some of the encrypted values. Example: Issuer’s AppID used to select the PAN and the wallet. Required for Visa push provisioning.36StringConditional
billingObject that contains information on the cardholder's billing address. If Thredd holds no address information of Cardholder then this is mandatory.


Conditional
line1First line of the cardholder's billing address.64StringConditional
line2Second line of the cardholder's billing address.64StringConditional
cityThe city for the cardholder's billing address.32StringConditional
countrySubdivisionThe country subdivision (for example, a county or state) of the cardholder's billing address.12StringConditional
postalCodeThe post code for the cardholder's billing address.26StringConditional
countryThe country for the cardholder's billing address, expressed as a 3-letter (alpha-3) country code as defined in ISO 3166-1.3StringConditional
billingEnd of the billing object.



serverSessionIDThis value should be generated via the Google SDK. It is a unique value created on Google's servers. When populated, this field triggers the inclusion of a Google Opaque Payment Card in the response.StringOptional

Response Fields

A successful response for the Google Unified Push Provisioning endpoint will return a 200 response.

FieldDescription
opaquePaymentCardBase64 encoded JSON object IssuerInitiatedDigitizationData containing both fundingAccountInfo and tokenizationAuthenticationValue. See Mastercard Developers.
last4digitsThe last 4 digits of the account number.
nameFirst name and surname of the cardholder.
networkThe name of network associated with card. For example, Visa or Mastercard.
addressObject that contains information on the cardholder's address.
line1First line of the cardholder's billing address.
line2Second line of the cardholder's billing address.
cityThe city for the cardholder's billing address.
countrySubdivisionThe country subdivision (for example, a county or state) of the cardholder's billing address.
postalCodeThe post code for the cardholder's billing address.
countryThe country for the cardholder's billing address, expressed as a 3-letter (alpha-3) country code as defined in ISO 3166-1.
addressEnd of the address object.
googleOpaquePaymentCardBase64‑encoded bytes containing a PGP‑encrypted Google Opaque Payment Card associated with a Google account card‑on‑file.