CHECKOUT-9450: Fix resolve IDs of components for hosted payment methods to match with SDK #2756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… payment methods to match with SDK
richapatel1510
approved these changes
Dec 24, 2025
animesh1987
approved these changes
Dec 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What/Why?
We're still seeing "A different strategy is registered for" warnings in Sentry. Upon investigation, we found two issues.
afterpayandclearpay, these payment methods could either be initialised withid: 'afterpay'andid: 'clearpay'orgateway: 'afterpay'andgateway: 'clearpay'param. To fix this, we need to make them the same as Checkout SDK (see configuration for Afterpay and Clearpay on SDK side).paypalexpresscredit, we also need to match the configuration with SDK (see PayPal Express configuration on SDK side).Rollout/Rollback
Revert
Testing
Before
After