A partner of us operates multiple apps and processes Google Pay in those. There are some legacy apps which are hard to update and also some legacy websites using the Google Pay Javascript SDK.
In those websites the partner initializes the SDK with the information provided by the PSP. Following two options are used:
Adyen:
<code>"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "adyen",
"gatewayMerchantId": "YOUR_MERCHANT_ACCOUNT_NAME"
}
}
</code>
<code>"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "adyen",
"gatewayMerchantId": "YOUR_MERCHANT_ACCOUNT_NAME"
}
}
</code>
"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "adyen",
"gatewayMerchantId": "YOUR_MERCHANT_ACCOUNT_NAME"
}
}
Chase:
<code>"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "chase",
"gatewayMerchantId": "YOUR_GATEWAY_MERCHANT_ID"
}
}
</code>
<code>"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "chase",
"gatewayMerchantId": "YOUR_GATEWAY_MERCHANT_ID"
}
}
</code>
"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "chase",
"gatewayMerchantId": "YOUR_GATEWAY_MERCHANT_ID"
}
}
The partner then sends us the payload and we receive following:
<code>{
"encryptedPayload": "{"encryptedMessage":"dDkzUfxxxxxW/8K8"}",
"encryptedPaymentHeader": {
"ephemeralPublicKey": "BCxxxx="
},
"signature": "MEQCIQxxxxGQbxi7rJA==",
"protocolVersion": "ECv1"
}
</code>
<code>{
"encryptedPayload": "{"encryptedMessage":"dDkzUfxxxxxW/8K8"}",
"encryptedPaymentHeader": {
"ephemeralPublicKey": "BCxxxx="
},
"signature": "MEQCIQxxxxGQbxi7rJA==",
"protocolVersion": "ECv1"
}
</code>
{
"encryptedPayload": "{"encryptedMessage":"dDkzUfxxxxxW/8K8"}",
"encryptedPaymentHeader": {
"ephemeralPublicKey": "BCxxxx="
},
"signature": "MEQCIQxxxxGQbxi7rJA==",
"protocolVersion": "ECv1"
}
Is there a way to detect which config was used?
What we have tried:
- We tried to find any parameter which stays static
- We tried to decode the payload