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] Remaining authorized amount may not be voided after partial capture #2036

Open
2 tasks done
hrithikesh026 opened this issue Aug 28, 2023 · 0 comments
Open
2 tasks done
Assignees
Labels
C-bug Category: Bug

Comments

@hrithikesh026
Copy link
Contributor

Bug Description

There is no implementation currently to void remaining authorized amount after single partial capture.
Some connectors may automatically void the remaining authorized amount. But this behaviour cannot be generalized for all connectors.

After partial capture, payment status goes to succeeded without ensureing that remaining amount is voided at connector.

Expected Behavior

After single partial capture is done, if connector doesn't automatically void the remaining amount, we need to void it.

Actual Behavior

After partial capture, the remaining authorized amount must be voided.

Steps To Reproduce

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

  1. Create a payment with "capture_method":"manual"
  2. Partially capture the payment.
  3. status changes to succeeded without voiding remaining authorized amount.

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!

@hrithikesh026 hrithikesh026 added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Aug 28, 2023
@hrithikesh026 hrithikesh026 self-assigned this Aug 28, 2023
@SanchithHegde SanchithHegde removed the S-awaiting-triage Status: New issues that have not been assessed yet label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug
Projects
None yet
Development

No branches or pull requests

2 participants