Fix: correct handling on LIVE prefix #1617
Merged
Merged
Conversation
jeandersonbc
approved these changes
Jan 26, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request corrects the validation for the
liveEndpointUrlPrefixto ensure it's only required for specific service URLs in the LIVE environment. It significantly expands the test coverage for theServiceclass, particularly around URL construction logic for different Adyen services and environments.This is a cherry-pick from #1616:
liveEndpointUrlPrefixvalidation logic. The prefix is now strictly required only for Live environment calls topal-andcheckout-services, preventing unnecessary errors for other service types.service.spec.ts.