fix(connector): adyen - propagate connector mandate details in incoming webhooks #6720
Conversation
This file contains 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
…ils-are-not-persisted-for-adyen-connector
2 tasks
|
Review changes with Changed Files
|
deepanshu-iiitu
approved these changes
Dec 2, 2024
AkshayaFoiger
approved these changes
Dec 2, 2024
likhinbopanna
deleted the
6719-bug-mandate-details-are-not-persisted-for-adyen-connector
branch
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
Described in the linked #6719
Additional Changes
Motivation and Context
Ensures mandate details are stored for Adyen.
How did you test it?
Since this is an intermittent scenario, webhooks flow was tested locally by disabling propagation of mandate details during PSync flow for Adyen.
connector_mandate_detailsis populate post receiving the webhooksChecklist
cargo +nightly fmt --allcargo clippy