-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(process_tracker): Invoke record back flow in PCR workflow [V2] #7660
base: main
Are you sure you want to change the base?
Conversation
Changed Files
|
let billing_mca = store | ||
.find_merchant_connector_account_by_id( | ||
key_manager_state, | ||
&billing_merchant_connector_account_id, | ||
&pcr_data.key_store, | ||
) | ||
.await?; |
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.
Note : We cannot avoid db call here since we need connector creds to make record back. Get MCA will not give api keys to call connector.
@@ -49,7 +50,8 @@ impl< | |||
+ api::FraudCheckV2 | |||
+ api::ConnectorMandateRevokeV2 | |||
+ api::authentication_v2::ExternalAuthenticationV2 | |||
+ api::UnifiedAuthenticationServiceV2, | |||
+ api::UnifiedAuthenticationServiceV2 | |||
+ api::revenue_recovery_v2::RevenueRecoveryV2, |
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.
+ api::revenue_recovery_v2::RevenueRecoveryV2, | |
+ api::revenue_recovery::RevenueRecovery, |
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.
Take this up in next pr
@@ -49,7 +50,8 @@ impl< | |||
+ api::FraudCheckV2 | |||
+ api::ConnectorMandateRevokeV2 | |||
+ api::authentication_v2::ExternalAuthenticationV2 | |||
+ api::UnifiedAuthenticationServiceV2, | |||
+ api::UnifiedAuthenticationServiceV2 | |||
+ api::revenue_recovery_v2::RevenueRecoveryV2, |
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.
Take this up in next pr
) -> Result<(), errors::ProcessTrackerError> { | ||
let db = &*state.store; | ||
let db: &dyn StorageInterface = &*state.store; |
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.
nit: Can you remove this
Type of Change
Description
What is record back flow ?
After payment is retried by revenue recovery by PCR workflow, We need to update the billing processor(update the invoce or record the attempt).This PR invokes record back functionality in process tracker flow for Terminal status.
Note: Adding support for retrying failed outgoing recordback webhooks is still pending attached in this issues.
Additional Changes
Motivation and Context
How did you test it?
Can be tested once this PR is merged #7614
Checklist
cargo +nightly fmt --all
cargo clippy