• Resolved anjoid

    (@anjoid)


    Hi, for some reason the apple and google pay buttons display correctly on desktop but not on mobile. Do you know how I can fix this?

    Thanks!

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    @anjoid

    I see you left us a one star review almost 2 years ago. I’d appreciate if you updated your review since you’re still using this plugin and asking for support.

    Do you know how I can fix this?

    Your product page was tested on an iPhone and Apple Pay rendered correctly. It was only GPay that didn’t render and that’s because you’re using the Payment Request Gateway. The GPay integration through the Payment Request Gateway is more limited since it’s using the browser’s wallet, which Safari doesn’t support. The Payment Request Gateway’s GPay integration will only show on Chrome.

    If you were to use the Google Pay Gateway, it would show on mobile devices and is not limited to just Chrome (it would show with Safari, Firefox etc). To use the Google Pay Gateway, you would need to request a Google Merchant ID. Our documentation has a step by step guide.

    Kind Regards

    Thread Starter anjoid

    (@anjoid)

    Got it I will try that. Thanks for the quick reply, review has been updated!

    Thread Starter anjoid

    (@anjoid)

    would you mind taking a look at this client site where the google pay button keeps flashing in and out? https://recoverfasttherapy.com/product/inflatable-ice-bath-tub/

    Plugin Author Payment Plugins

    (@mrclayton)

    @anjoid what’s happening is the button keeps reloading every 3 seconds or so. That’s because for some strange reason the needsShipping attribute coming from the cart calculation request has a value of false.

    But the product does needs shipping. The Stripe plugin has logic to re-initalize the payment request object if the local state doesn’t match the server’s state. That’s to ensure the proper info like shipping address and shipping options are being shown in the wallet when it open.

    Do you know why this product would load with needsShipping: true but then return false for subsequent requests?

    Here is an example of the response from the cart calculation request:

    {
        "data": {
            "needsShipping": false,
            "stripe_applepay": {
                "total": "495.00",
                "subtotal": "495.00",
                "totalCents": 49500,
                "displayItems": [
                    {
                        "label": "Inflatable Ice Bath Tub with Drop Stitch Portable Technology",
                        "pending": false,
                        "amount": 49500
                    }
                ],
                "shippingOptions": []
            },
            "stripe_googlepay": {
                "total": "495.00",
                "subtotal": "495.00",
                "totalCents": 49500,
                "displayItems": [
                    {
                        "label": "Inflatable Ice Bath Tub with Drop Stitch Portable Technology",
                        "type": "LINE_ITEM",
                        "price": "495.00"
                    }
                ],
                "shippingOptions": [
                    {
                        "id": "default",
                        "label": "Waiting...",
                        "description": "loading shipping methods..."
                    }
                ]
            },
            "stripe_payment_request": {
                "total": "495.00",
                "subtotal": "495.00",
                "totalCents": 49500,
                "displayItems": [
                    {
                        "label": "Inflatable Ice Bath Tub with Drop Stitch Portable Technology",
                        "pending": false,
                        "amount": 49500
                    }
                ],
                "shippingOptions": []
            }
        }
    }
    Thread Starter anjoid

    (@anjoid)

    Ahh makes sense! Thank you, I really appreciate your plugin and all your help.

    Thread Starter anjoid

    (@anjoid)

    Hey I’m facing this same issue again and can’t figure out what’s causing it. I’ve tried disabling all pluging and using storefront theme with no luck.

    Appl/google pay load on desktop completely fine but on mobile neither appear on the item or checkout page.

    Can you take a look and let me know if I’m missing something? https://aquilegy.com/product/buy-aquilegy/

    Plugin Author Payment Plugins

    (@mrclayton)

    @anjoid I see you also have the WooCommerce Stripe Gateway plugin enabled and that’s resulting in the js.stripe.com script being loaded twice. Have you tried testing with just one Stripe plugin enabled?

    Kind Regards

    Thread Starter anjoid

    (@anjoid)

    Yes, I just shut it off if you would like to see now? I was testing their plugin but same issue. It’s very odd it only shows on desktop

    Plugin Author Payment Plugins

    (@mrclayton)

    Here are some screenshots of the browser debugger. The first is on a laptop, which shows the payment request returns a valid object, which means the GPay button can be rendered.

    On mobile, Stripe is returning a null value which means GPay isn’t supported. So for some reason Stripe is determining that the button can’t be rendered on mobile. This wouldn’t be caused by a Stripe plugin issue; I am not sure why Stripe is returning null for mobile.

    Thread Starter anjoid

    (@anjoid)

    Ok thanks I guess I will contact stripe and see if they have an insight. Tried matching all settings to another site it’s working on so maybe it is a setting within stripe

    Plugin Author Payment Plugins

    (@mrclayton)

    Ok thanks I guess I will contact stripe and see if they have an insight.

    Show them this thread and the two screenshots showing that the payment request returns null on mobile.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Apple/Google Pay Not Showing on Mobile’ is closed to new replies.