Google Pay push provisioning
This endpoint is only used for Google Pay push provisioning.
Response is a JSON that must be passed to Google and onwards to MDES/VTS.
Google is introducing Unified Android Push Provisioning (UPP) for Google Wallet.
Existing Enfuce Google Pay Push Provisioning integrations remain backwards compatible.
Customers migrating to UPP only need to extend their existing integration with two additional
request fields (googleOpaquePaymentCardRequested and serverSessionId) and one additional
response field (googleOpaquePaymentCard).
These fields are only required when integrating with Google’s Unified Android Push Provisioning flow. Existing integrations using the legacy Google Pay Push Provisioning flow continue to work unchanged.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Path Parameters
CardId for the card that should be provisioned (returned from card operation)
Query Parameters
The audit user to log the request
Body
Only applicable for VTS customers
36When true, a Google OPC is generated and returned in googleOpaquePaymentCard. Requires serverSessionId.
UUID generated by the Google Wallet SDK for Unified Push Provisioning. Required when googleOpaquePaymentCardRequested is true; ignored otherwise.
Response
OK
Base64 encoded json structure containing needed data for MDES/VTS
Base64-encoded (RFC 4648 §4, non-URL-safe) PGP signed and encrypted Google Opaque Payment Card. Present only on Google Pay provisioning responses when the request included a serverSessionId.

