You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the payment status is processing, the backend was returning an incorrect error message. The message incorrectly stated that the issue was with the capture method, whereas it should indicate that the payment status
is processing and the expected states are requires_capture or partially_captured_and_capturable. It is due to the incorrect mapping of one of the attempt status in NMI connector.
This fix ensures the correct error message is displayed.
Payments - Create:
Payments - Capture:
Expected Behavior
it should return an error indicating that the payment status is processing and the expected states are requires_capture or partially_captured_and_capturable.
Payments - Create:
Payments - Capture:
Actual Behavior
It actually returned an incorrect error message stating that the issue was with the capture method.
Anurag-05-prog
changed the title
[BUG] Incorrect error message during status validation check in capture call
[BUG] Incorrect mapping of attempt status in NMI connector
Feb 6, 2025
Bug Description
When the payment status is
processing
, the backend was returning an incorrect error message. The message incorrectly stated that the issue was with the capture method, whereas it should indicate that the payment statusis
processing
and the expected states arerequires_capture
orpartially_captured_and_capturable
. It is due to the incorrect mapping of one of the attempt status in NMI connector.This fix ensures the correct error message is displayed.
Payments - Create:
Payments - Capture:
Expected Behavior
it should return an error indicating that the payment status is
processing
and the expected states arerequires_capture
orpartially_captured_and_capturable
.Payments - Create:
Payments - Capture:
Actual Behavior
It actually returned an incorrect error message stating that the issue was with the capture method.
Payments - Create:
Payments - Capture:
Steps To Reproduce
Request -
Request -
Request -
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the
x-request-id
response header to help us debug your issue.If not (or if building/running locally), please provide the following details:
rustc --version
):1.83.0
cargo r --features vergen -- --version
):router 2025.01.27.0-30-ge0ec27d-dirty-e0ec27d-2025-02-05T09:54:57.000000000Z
Have you spent some time checking if this bug has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: