For a redirect before checkout payment, the customer is redirected to the PSP using the redirect URL that the ICM generates.
When the customer is back in the PWA and the redirect was successful, he can add further products to the basket, which then triggers a new basket validation in the checkout.
This basket validation returns that a new redirect is necessary (depending on the payment connector implementation) but does not return a new redirect URL.
What Is the New Behavior?
This bug has been fixed in ICM version 12.3.0 and the ICM now returns a new redirect URL on basket validation if adjustments are allowed and if a new redirect is needed.
This PR takes the newly generated URL and stores it in the Store to then perform the redirect with the newly generated URL.
PR Type
[x] Bugfix [ ] Feature [ ] Code style update (formatting, local variables) [ ] Refactoring (no functional changes, no API changes) [ ] Build-related changes [ ] CI-related changes [ ] Documentation content changes [ ] Application / infrastructure changes [ ] Other:
What Is the Current Behavior?
For a redirect before checkout payment, the customer is redirected to the PSP using the redirect URL that the ICM generates. When the customer is back in the PWA and the redirect was successful, he can add further products to the basket, which then triggers a new basket validation in the checkout. This basket validation returns that a new redirect is necessary (depending on the payment connector implementation) but does not return a new redirect URL.
What Is the New Behavior?
This bug has been fixed in ICM version 12.3.0 and the ICM now returns a new redirect URL on basket validation if adjustments are allowed and if a new redirect is needed.
This PR takes the newly generated URL and stores it in the Store to then perform the redirect with the newly generated URL.
Does this PR Introduce a Breaking Change?
[ ] Yes [x] No
Other Information
Requires ICM 12.3.0 Azure DevOps Issue: 97415
AB#100804