-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(mandate): make payment_method_data optional for mandate scenario #1032
Conversation
}; | ||
if let storage_models::enums::PaymentMethod::Card = payment_method.payment_method { | ||
let _ = | ||
cards::get_lookup_key_from_locker(state, &token, &payment_method, &locker_id).await?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@manoj-juspay Why is this call being made and then the value is dropped? Is this to get the card data from permanent locker to basilisk?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than @Narayanbhat166 changes, looks good to me.
Type of Change
Description
For Recurring mandate payments we don't need payment_method_data, currently we are storing all card_details in locker so payment_method_data can be built from card_details in locker for card_payment but in other_payment_methods(google_pay, apple_pay) it won't be possible, so we can ignore the payment_method_data in all recurring mandate payments.
Additional Changes
Motivation and Context
Closes #1011
How did you test it?
Checklist
cargo +nightly fmt --all
cargo clippy