SONIC-696: Disable Wallets via code in the Legacy Payment Flow #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Anyone merging to this repository is expected to promptly release and monitor their changes; if you are not able to do this DO NOT MERGE, please coordinate with someone who can to ensure that the changes are released.
Description
We are planning to enable wallet payment options i.e Google Pay and Apple Pay, in our new CT checkout flow. However, since our Stripe account is shared across platforms, these options would also appear on payment.edx.org. Ideally, wallet options should only be displayed for trusted domains. Unfortunately, Stripe does not seem to enforce this setting correctly, as the wallet options are showing up on unregistered domains like payment.edx.org/payment.stage.edx.org. Given that our current Stripe payment logic does not support wallets and Stripe is not respecting domain restrictions, We are disabling wallets as a payment method in the Stripe payment options via code
Currently on stage when google pay is enabled:
Supporting information
Jira Ticket: https://2u-internal.atlassian.net/browse/SONIC-696
Checklist