refactor(connector): [Stripebilling] change Billing Connector Payment Sync url from charges to payment intents api #7893
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
…ync flow of stripebilling
|
Review changes with Changed Files
|
NISHANTH1221
added
A-connector-integration
NISHANTH1221
changed the title
crates/hyperswitch_connectors/src/connectors/stripebilling/transformers.rs
Show resolved
Hide resolved
srujanchikke
approved these changes
Apr 28, 2025
swangi-kumari
approved these changes
Apr 28, 2025
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
This PR changes the url of billing connector payment sync flow from using stripe charge api to stripe payment intents api. Because in Recovery Flow there is a chance to call stripe's psync flow to update the error codes and other details for an attempt. And psync flow accepts payment intent id rather than the charge id. To reuse the existing flow we need payment_intent id to propogate.
Additional Changes
Motivation and Context
How did you test it?
To test this You can follow the steps of this PR: #7461
Tested it locally. And the logs are as following.
Checklist
cargo +nightly fmt --allcargo clippy