feat(connector): Add recovery support for stripebilling #7461
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jarnura
requested changes
Mar 25, 2025
| router_request_types::revenue_recovery::RevenueRecoveryRecordBackRequest, | ||
| router_response_types::revenue_recovery::RevenueRecoveryRecordBackResponse, | ||
| types::RevenueRecoveryRecordBackRouterData, | ||
| router_flow_types::revenue_recovery::{ |
There was a problem hiding this comment.
Suggested change
| router_flow_types::revenue_recovery::{ | |
| router_flow_types::revenue_recovery |
jarnura
requested changes
Mar 27, 2025
| @@ -71,10 +71,10 @@ pub use self::fraud_check_v2::*; | |||
| pub use self::payouts::*; | |||
| #[cfg(feature = "payouts")] | |||
| pub use self::payouts_v2::*; | |||
| pub use self::{payments::*, refunds::*}; | |||
| pub use self::{payments::*, refunds::*, revenue_recovery::*}; | |||
There was a problem hiding this comment.
Suggested change
| pub use self::{payments::*, refunds::*, revenue_recovery::*}; | |
| pub use self::{payments::*, refunds::*, revenue_recovery}; |
| errors::api_error_response, revenue_recovery, router_data_v2::flow_common_types, | ||
| router_flow_types, router_request_types::revenue_recovery as revenue_recovery_request, | ||
| router_response_types::revenue_recovery as revenue_recovery_response, | ||
| types::AdditionalRevenueRecoveryDetailsRouterData, |
There was a problem hiding this comment.
Suggested change
| types::AdditionalRevenueRecoveryDetailsRouterData, | |
| types, |
| router_response_types::revenue_recovery as revenue_recovery_response, | ||
| types::AdditionalRevenueRecoveryDetailsRouterData, | ||
| }; | ||
| use hyperswitch_interfaces::{api::RevenueRecovery, webhooks as interface_webhooks}; |
There was a problem hiding this comment.
Suggested change
| use hyperswitch_interfaces::{api::RevenueRecovery, webhooks as interface_webhooks}; | |
| use hyperswitch_interfaces::{api, webhooks as interface_webhooks}; |
jarnura
previously approved these changes
Mar 27, 2025
| router_flow_types::revenue_recovery::{ | ||
| GetAdditionalRevenueRecoveryDetails, RecoveryRecordBack, | ||
| }, | ||
| router_flow_types::revenue_recovery::{BillingConnectorPaymentsSync, RecoveryRecordBack}, |
There was a problem hiding this comment.
Suggested change
| router_flow_types::revenue_recovery::{BillingConnectorPaymentsSync, RecoveryRecordBack}, | |
| router_flow_types::revenue_recovery, |
srujanchikke
previously approved these changes
Mar 27, 2025
jarnura
approved these changes
Mar 27, 2025
srujanchikke
approved these changes
Mar 28, 2025
NISHANTH1221
removed
the
S-waiting-on-review
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
Context: In case of some billing connectors we dont get the enough data in the webhook itself to support creation of payment intent and payment attempt in our system. So previously we derived a flow named "AdditionalRevenuerecoveryDetails" in this PR:#7402 which name is now changed to "BillingConnectorPaymentSync". This flow is used to fetch payment details of the invoices from the billing connectors using an API call to that billing connector. In this pr we are calling the flow and getting the details which are needed to create payment intent and attempt in our system.
Additional Changes
Motivation and Context
Testing
change the profile id and other feilds while creating you own one
3. copy the mca id of stripe and paste it in the billing mca curl in feature metadata
Images of the logs:
Checklist
cargo +nightly fmt --allcargo clippy