Google Pay - Issue with Maestro - regression from #3539

[dimitri-dev]

Hello, long time no see :)

Describe the bug

Since the merge of PR #3539 (release v6.23.0+), Google Pay integration crashes at runtime whenever the maestro brand is included in the mapped brands list. The issue seems related to the way Google Pay interprets "MAESTRO" in the allowedCardNetworks array.

This is how allowedCardNetworks are defined in GooglePay docs (link):

To Reproduce

Example of payment method configuration that works

"paymentMethods": {
        "paymentMethods": [
            {
                "brands": [
                    "maestro",
                    "amex",
                    "visa"
                ],
                "name": "Cards",
                "type": "scheme"
            },
            {
                "brands": [
                    "mc",
                    "visa"
                ],
                "configuration": {
                    "merchantId": "REDACTED",
                    "gatewayMerchantId": "REDACTED"
                },
                "name": "Google Pay",
                "type": "googlepay"
            }
        ]
    }

Example of payment method configuration that doesn't work

"paymentMethods": {
        "paymentMethods": [
            {
                "brands": [
                    "maestro",
                    "amex",
                    "visa"
                ],
                "name": "Cards",
                "type": "scheme"
            },
            {
                "brands": [
                    "maestro",
                    "visa"
                ],
                "configuration": {
                    "merchantId": "REDACTED",
                    "gatewayMerchantId": "REDACTED"
                },
                "name": "Google Pay",
                "type": "googlepay"
            }
        ]
    }

Screenshots

Additional context

Tested on v6.23.0 and v6.25.0, on both desktop (Windows, MacOS) and mobile (Android, iOS) devices. If maestro is supplied as a brand in the google pay configuration, the initialization will crash.

I have also found this to be a similar issue in Stripe's gh. Crosslink: stripe/stripe-android#8435 (comment) Something to do with Brazil specific methods regarding Google Pay? However, this is an inconsistency with Adyen then, where Google Pay - Maestro is treated just like any other payment method.

Hope for a quick resolution.

[dimitri-dev]

@m1aw Just to let you know - we have temporarily fixed this on our side by sending the maestro_googlepay method in blockedPaymentMethods on the /paymentMetods request. However, this still feels like something that should have been filtered out on your end using the CountryCode supplied within the request - if it is in fact intended for just BR transactions.

[m1aw]

Hey @m1aw, we have raised this internally, we are checking why you are getting maestro in the brands array for countries outside of Brazil. We will have a response for you soon.

[obber]

Just wanted to +1, we were seeing the same OR_BIBED_06 error. I was digging around and saw that we recently bumped from v6.21 to v6.24, and right around that time we stopped processing Google Pay transactions.

I reverted to 6.21 and it seems to work now. This is the payment methods response object being relayed into the Adyen Web SDK:

{
    "paymentMethods": [
        {
            "brands": [
                "maestro",
                "amex",
                "discover",
                "jcb",
                "mc",
                "visa"
            ],
            "configuration": {
                "merchantId": "REDACTED",
                "merchantName": "REDACTED"
            },
            "name": "Apple Pay",
            "type": "applepay"
        },
        {
            "brands": [
                "maestro",
                "amex",
                "cup",
                "diners",
                "discover",
                "jcb",
                "mc",
                "visa"
            ],
            "name": "Cards",
            "type": "scheme"
        },
        {
            "brands": [
                "maestro",
                "amex",
                "discover",
                "mc",
                "visa"
            ],
            "configuration": {
                "gatewayMerchantId": "REDACTED",
                "merchantId": "REDACTED"
            },
            "name": "Google Pay",
            "type": "googlepay"
        },
        {
            "configuration": {
                "intent": "authorize",
                "merchantId": "REDACTED"
            },
            "name": "PayPal",
            "type": "paypal"
        }
    ]
},

It does seem that we also have maestro in that list. Hopefully this helps with your investigation!

[ribeiroguilherme]

Hi @obber - thanks for sharing.

Apparently the issue is that 'maestro' works only for Brazil. So if the backend is returning that and the countryCode is not BR, then you will see the error that @dimitri-dev shared above.

As @m1aw mentioned, we are checking it internally and we will get back here as soon as we find out how to move forward.

[ribeiroguilherme]

Hi @dimitri-dev ,

An update from our side: the team responsible for this setup will work to not return maestro in case the country code does not support that. We won't do any fix on the library side. As it is peak season, unfortunately we do not have timelines for the fix. We will update this ticket as soon as the problem is solved.

[apryamostanov]

@ribeiroguilherme " unfortunately we do not have timelines for the fix" - sorry but this is not acceptable given the criticality of this issue.