Settings Synchronization: Apple Pay / Google Pay

[hsingyuc]

We aim to allow merchants to update gateway settings from both WC Stripe settings and Stripe dashboard settings.

In #3916 we are fetching the payment method configuration settings. For this issue, we want to hook up Apple Pay / Google Pay configuration settings to existing methods that check for Apple Pay / Google Pay enabled/disabled. After we are able to toggle settings from Stripe, and see those changes in the WooCommerce Stripe settings, we also want to be able to update the Stripe dashboard Apple Pay / Google Pay settings from the WC Stripe Apple Pay / Google Pay settings.

For example, this payment request response should be updated to use the Stripe configuration we added in #3916.

Acceptance criteria

• Merchants should be able to toggle settings from Stripe Apple Pay / Google Pay settings and we should see those changes in the WooCommerce Stripe Gateway Apple Pay / Google Pay settings.
• Merchants should be able to toggle settings from WC stripe Apple Pay / Google Pay settings, and we should see those changes in the Stripe dashboard Apple Pay / Google Pay settings.

Notes

• Blocked by Settings Synchronization : Fetch Stripe settings with Stripe configuration API #3916 and Settings Synchronization: Hook up payment methods configuration #4088
• Create a PR based on the feature branch

[annemirasol]

@hsingyuc In the Stripe dashboard, Apple Pay and Google Pay can be enabled/disabled separately, but in wp-admin, they are combined.

wp-admin	Stripe dashboard

I think we have 3 paths we can take:

1. Separate Apple Pay and Google Pay in wp-admin.
2. Keep them combined. At least one must be enabled in Stripe dashboard for the feature to be enabled in wp-admin.
3. Keep them combined. Both must be enabled in Stripe dashboard for the feature to be enabled in wp-admin.

Option 1 is more intuitive for our merchants, although I'm worried about the work being bigger. With a view of what we are aiming to deliver for 9.4, would Option 2 or 3 be acceptable as a thin slice?

Also, do we know yet how we will do the migration?

[hsingyuc]

Option 1 is more intuitive for our merchants, although I'm worried about the work being bigger. With a view of what we are aiming to deliver for 9.4

With the delievery for 9.4, I agree we shouldn't expand the work right now. Perhaps adjust later if we need to.

would Option 2 or 3 be acceptable as a thin slice?

I think option 2 make sense and we can change to option 1 later if we want to.

Also, do we know yet how we will do the migration?

The idea is to get current admin settings, update Stripe dashboard settings, make sure we are getting a 200 response and delete the local options.