-
Notifications
You must be signed in to change notification settings - Fork 4.2k
refactor(core): accept manual retry from profile #9302
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
Conversation
is_manual_retry_enabled: Option<bool>, | ||
action: &str, | ||
) -> RouterResult<AttemptType> { | ||
match payment_intent.status { | ||
enums::IntentStatus::Failed => { | ||
if matches!( | ||
request.retry_action, | ||
Some(api_models::enums::RetryAction::ManualRetry) | ||
) { | ||
if matches!(is_manual_retry_enabled, Some(true)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are we removing the request support?
like we wont rely at all on request?
what happens to the current merchant who is sending manual retry config in request? will we inform them to update profile.
ig we need to check both for now imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we are deprecating the request parameter for manual retry. No merchant is actively using this flow. This is to simplify the solution since we don't want SDK to have separate approach for non-redirection and redirection case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we are removing the request parameter.
seems like those changes are not in this pr. i mean we need to update the api ref that we are deprecating this field.
Will there be a seperate pr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated the reference to deprecated
…ee-ds * 'main' of github.com:juspay/hyperswitch: feat(webhooks): Provide outgoing webhook support for revenue recovery (#9294) feat(connector): Add Peachpayments Template Code (#9363) feat(connector): [Paysafe] Implement card 3ds flow (#9305) feat(router): Add Connector changes for 3ds (v2) (#9117) feat(connector): [ADYEN] Add support to ideal Mandate Webhook (#9347) refactor(core): accept manual retry from profile (#9302) fix(nuvei): nuvei 3ds fix + psync fix (#9279) fix(connector): [checkout] Add US Support for Apple Pay and Google Pay + Enhanced Checkout Response Data (#9356) fix(router): adding connector_customer_id for external vault proxy (#9263) feat(core): Add first_name and last_name as Secret<String> Types. (#9326) feat(injector): injector request formation changes (#9306) fix(revenue-recovery): Update Redis TTL for customer locks after token selection (#9282) chore(version): 2025.09.11.0 refactor(connector): [Paysafe] fix wasm (#9349) refactor(connector): rename RevenueRecoveryRecordBack as InvoiceRecordBack (#9321) feat(connector): [checkout] add support for MOTO payments (#9327) feat(connector): enhance ACI connector with comprehensive 3DS support - DRAFT (#8986) feat(core): [Retry] MIT Retries (#8628)
Type of Change
Description
Currently manual retry is enabled through request.
We need to make it profile configurable such that the merchant/SDK doesn't need to send it for each request
is_manual_retry
is enabled through profile with this prAdditional Changes
Motivation and Context
How did you test it?
Tested through Postman:
Create an MCA(Cybersource):
Case 1: (without manual retry enabled)
Case 2: (with manual retry enabeld)
Checklist
cargo +nightly fmt --all
cargo clippy