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
Iatapay sends CLEARED refund status, during some exceptional cases. Therefor we need to add this to Iatapay's refund status.
Cleared status marks to refund success
Refund must be marked success on receiving Cleared status
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
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
AkshayaFoiger
Successfully merging a pull request may close this issue.
Bug Description
Iatapay sends CLEARED refund status, during some exceptional cases. Therefor we need to add this to Iatapay's refund status.
Expected Behavior
Cleared status marks to refund success
Actual Behavior
Refund must be marked success on receiving Cleared status
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?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: