fix(core): add validation to check if routable connector supports network tokenization in CIT repeat flow #6749
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
Currently we always fetch network token for the connector that does not support network tokenization.
Fix: we ll only fetch network token if the connector supports network tokenization else fetch card details to make CIT repeat.
Additional Changes
Motivation and Context
How did you test it?
test cases -
Create two MCA ex - Cybersource(network tokenization supported conn), Adyen
enable network tokenization for business profile
Make saved card flow transaction.
when routable connector list - [Cybersource, Adyen] -> payment should happen with Network token + cryptogram
when routable connector list - [ Adyen, Cybersource] -> payment should happen with card+cvc
CIT -
Checklist
cargo +nightly fmt --all
cargo clippy