fix: napmv2: on payment failure display error message provided by gateway instead of generic#251
Merged
szymon-mysiak-cko merged 3 commits intomasterfrom Mar 27, 2026
Merged
Conversation
szymon-mysiak-cko
changed the title
edwin-joseph-cko
approved these changes
Mar 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.
Display the actual error message returned by the flow instead of always showing the same generic
"Unable to connect"text.This in general happens when gateway does not respect returning proper error code, e.g.
gateway.invalid-customer-input/state:FAILEDinstead ofrequest.validation.invalid-input. New nAPM correctly treats its as Failure, but displays always generic message, ignoring gateway output.It’s needed so checkout can surface the real failure reason on HPP (e.g. invalid customer input) and avoid masking it as a fake connectivity/internal error.
reference: https://processout.slack.com/archives/C0548JC4NAG/p1774440299276609?thread_ts=1774368288.629709&cid=C0548JC4NAG