-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat(connector): [Recurly] add invoice sync support along with transaction monitoring #7867
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(connector): [Recurly] add invoice sync support along with transaction monitoring #7867
Conversation
…ice_sync_support_with_transaction_monitoring
#[derive(Serialize, Deserialize, Debug, Clone)] | ||
#[serde(rename_all = "snake_case")] | ||
pub struct RecurlyInvoiceTransactionsStatus { | ||
pub status: String, |
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.
Isn't this supposed to an enum ?
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.
Yes, If you remember for chargebee we are doing the same we just wnat this for no. of transactions.
use masking::Secret; | ||
use router::types::{self, api, storage::enums}; | ||
use test_utils::connector_auth; | ||
// use hyperswitch_domain_models::payment_method_data::{Card, PaymentMethodData}; |
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.
instead of commenting it out can we delete this file ?
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.
yeah forgot about it.
The base branch was changed.
connector_enums::Connector::Recurly => Ok(self.recurly.clone()), | ||
connector_enums::Connector::Stripebilling => Ok(self.stripebilling.clone()), | ||
connector_enums::Connector::Chargebee => Ok(self.chargebee.clone()), | ||
_ => Err(api_error_response::ApiErrorResponse::IncorrectConnectorNameGiven.into()), |
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.
Can you define all other connectors instead of using default ?
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.
One of the required check is failing when we mention all the connectors. Because connectors are from common_enums and this config is in domain models . This cargo check was failing when I mention all the connnectors
cargo check --all-targets --package hyperswitch_domain_models --no-default-features --features dummy_connector,v1
Co-authored-by: chikke srujan <[email protected]>
Type of Change
Description
Transaction Monitoring means to record all the transaction that are happening in the billing connectors and storing them in our database. So that we can use those to train our model and get insights from that data in revenue recovery flow.
To support monitor the transaction happening in the billing connectors and to get maximum efficiency we need the fields in the issue which are billing address, retry count, subscription next billing date. To make this support for recurly we need invoice api call to recurly. BillingConnectorInvoiceSync will do that work. This PR contains the Connector Integration V2 Implementations of BillingConnectorInvoiceSync , BillingConnectorPaymentsSync and RecoveryRecordBack only for recurly. This PR also contains transaction monitoring support for recurly.
Additional Changes
Motivation and Context
How did you test it?
Cannot test it
Here is a picture depicting that we are able to get all the details:

Checklist
cargo +nightly fmt --all
cargo clippy