Skip to content
New issue

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

[BUG] [BANKOFAMERICA] Handle refund status 201 #4906

Open
2 tasks done
deepanshu-iiitu opened this issue Jun 7, 2024 · 0 comments · Fixed by #4908, #4911 or #4912
Open
2 tasks done

[BUG] [BANKOFAMERICA] Handle refund status 201 #4906

deepanshu-iiitu opened this issue Jun 7, 2024 · 0 comments · Fixed by #4908, #4911 or #4912
Assignees
Labels
A-connector-integration Area: Connector integration C-bug Category: Bug

Comments

@deepanshu-iiitu
Copy link
Contributor

Bug Description

Status in Bankofamerica refund response is returning a new value 201 along with errorInformation.reason as PROCESSOR_DECLINED which needs to be handled.

Expected Behavior

Status in Bankofamerica refund response is returning a new value 201 along with errorInformation.reason as PROCESSOR_DECLINED which should to be handled.

Actual Behavior

Status in Bankofamerica refund response is returning a new value 201 along with errorInformation.reason as PROCESSOR_DECLINED which is not being handled. The refunds in such cases should be marked as failed.

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'

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:

  1. Operating System or Linux distribution:
  2. Rust version (output of rustc --version): ``
  3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-connector-integration Area: Connector integration C-bug Category: Bug
Projects
None yet
1 participant