refactor(payment_method_data): add a trait to retrieve billing from payment method data #4095
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
sai-harsha-vardhan
approved these changes
Mar 20, 2024
Gnanasundari24
deleted the
4505-refactor-add-backwards-compatible-payment_method_data-billing
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
This PR adds a trait to extract billing detials from payment method data. No logical changes that affect payment flows are present in this PR.
Motivation and Context
This change will be used in further PRs to consume payment method data billing and unify it and send it to the connector module.
Impact
Only code changes, no flows are affected
How did you test it?
Checklist
cargo +nightly fmt --allcargo clippy