feat(connector): [stripebilling] consume necessary fields in stripe billing from webhooks for transaction monitoring support#7722
Merged
Gnanasundari24 merged 56 commits intomainfrom May 6, 2025
Conversation
Changed Files
|
srujanchikke
reviewed
Apr 7, 2025
Contributor
srujanchikke
left a comment
There was a problem hiding this comment.
We are not storing this data in payment attempt/payment intent, Can you make that changes as well ?
…tion_monitoring_feilds
…g' into stripebilling_transaction_monitoring_feilds
…g' into stripebilling_transaction_monitoring_feilds
Base automatically changed from
recurly_invoice_sync_support_with_transaction_monitoring
to
main
May 2, 2025 12:12
srujanchikke
approved these changes
May 2, 2025
swangi-kumari
approved these changes
May 2, 2025
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
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
Consuming the following fields in the webhook which will support the transaction monitoring feature further.
In stripebilling the subscribed webhook contains an object of that particular invoice. The details needed in the issue are available in the invoice object. Consume Billing address, Retry Count and Next Billing At for the invoice thorugh the webhook and populating in payment intent is the primary goal of this PR.
Additional Changes
Motivation and Context
How did you test it?
To test this follow the steps, follow the steps in this PR #7461. After doing all the steps you can find the billing address in payment intent table for this corresponding record. Retry count and Next Billing time in feature metadata of the same payment intent
Checklist
cargo +nightly fmt --allcargo clippy