jamestc989

Thank you! That’s worked (I used a slight variation with GPT’s help), but it’s still requesting the Contact info in the Apple Pay Modal. Also is it possible to disable Contact? It’s still requiring the user to set their Contact (email address). I’ve tried modifying this filter, but I think the gateway is overriding it and still requesting. This is my code at the moment, but it’s still asking for Email.

add_filter('wc_stripe_output_display_items', function($data, $page, $gateway) {
    if ($page === 'checkout' && in_array($gateway->id, ['stripe_applepay', 'stripe_googlepay'], true)) {
        $data['needs_shipping'] = false;
        $data['requestPayerName']  = false;
        $data['requestPayerEmail'] = false;
        $data['requestPayerPhone'] = false;
    }
    return $data;
}, 1, 3); // 🔁 Priority lowered from 10 to 1

I’ve not tested yet, but if woo checkout fields are completed and then Apple Pay checkout selected (not express), will it store/save the values like a normal checkout?

Really appreciate your help, thank you! Just a thought – I think there may be lots of other customers not able to use Apple Pay because of the way it skips woo checkout (anyone with custom fields or if you run a service like we do where we need to get other information to complete checkout), it would be a great option to add in Options.

If we can get the Contact also disabled in Apple/Android, then we will create a custom JS rule to prevent clicking the button until all required fields on woo are complete 🎉

@alpha2 Thanks for the reply!

I’m also speaking with Stripe too via their support about it. Hopefully there is a resolution very soon.

We’ve only noticed a small amount of do not honor – perhaps no more than i’d ever notice.

With the Radar Rules at the moment we only have Request 3DS if 3D Secure is required for card – Enabled.

But are you suggesting to turn on Request 3DS if 3D Secure is recommended for card?

Thanks!