refactor(constraint_graph): add setup_future_usage for mandate check in payments #6744
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
Previously the
mandate_details
were enough to identify the payment as mandate payment but now it is optional so a payment can be mandate even if there is nomandate_details
but the payment'ssetup_future_usage
isoff-session
.Additional Changes
Motivation and Context
How did you test it?
This can be tested in the following way:
It shouldn't have any payment_method
Checklist
cargo +nightly fmt --all
cargo clippy