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

[FEATURE] Add auto_retries configs in Payment Settings #1499

Closed
2 tasks done
sai-harsha-vardhan opened this issue Sep 30, 2024 · 0 comments · Fixed by #1551
Closed
2 tasks done

[FEATURE] Add auto_retries configs in Payment Settings #1499

sai-harsha-vardhan opened this issue Sep 30, 2024 · 0 comments · Fixed by #1551
Assignees
Labels
C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet

Comments

@sai-harsha-vardhan
Copy link

Feature Description

Add auto_retries configs in Payment Settings

  1. is_auto_retries_enabled - Boolean (denotes whether auto retries should be performed for a profile)
  2. max_auto_retries_enabled - Int (maximum auto retries to be performed)

Reference PR - juspay/hyperswitch#6134

Possible Implementation

Accept is_auto_retries_enabled and max_auto_retries_enabled in Payment settings and send those fields in Profile update api request

Have you spent some time checking if this feature request 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?

None

@sai-harsha-vardhan sai-harsha-vardhan added C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet labels Sep 30, 2024
@gitanjli525 gitanjli525 linked a pull request Oct 4, 2024 that will close this issue
13 tasks
@gitanjli525 gitanjli525 self-assigned this Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants