We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently we are not populating error message and error code when refund fails in BOA and Cybersource. We have to handle this.
Hyperswitch should know and store the reason on why the refund failed
Hyperswitch don't know or store the reason on why the refund failed
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
No response
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.
x-request-id
If not (or if building/running locally), please provide the following details:
rustc --version
cargo r --features vergen -- --version
None
The text was updated successfully, but these errors were encountered:
AkshayaFoiger
Successfully merging a pull request may close this issue.
Bug Description
Currently we are not populating error message and error code when refund fails in BOA and Cybersource. We have to handle this.
Expected Behavior
Hyperswitch should know and store the reason on why the refund failed
Actual Behavior
Hyperswitch don't know or store the reason on why the refund failed
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
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
): ``cargo r --features vergen -- --version
): ``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?
None
The text was updated successfully, but these errors were encountered: