You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-> When a payment is created with save card we store the card in the locker and also a payment method entry is created in the payment method table. And the corresponding payment_method_id will be stored in the payment_attempt table.
-> And later when that payment method is deleted, psycn is failing as we are trying to fetch the payment method data from the payment_method table in the psync flow.
-> The error occurred because of the recent change that was trying to fetch the payment method in the psync flow using the payment_method_id in the payment attempt.
So to fix this we need to make the payment methods delete api as soft delete. In this case when the payment method is deleted the payment method for the corresponding payment_method_id will be set to inactive. So that there won't be data inconsistency.
The text was updated successfully, but these errors were encountered:
ShankarSinghC
changed the title
Make the Payment methods delete api as soft delete
Make the Payment methods delete api to perform soft delete
Apr 8, 2024
-> When a payment is created with save card we store the card in the locker and also a payment method entry is created in the payment method table. And the corresponding payment_method_id will be stored in the payment_attempt table.
-> And later when that payment method is deleted, psycn is failing as we are trying to fetch the payment method data from the payment_method table in the psync flow.
-> The error occurred because of the recent change that was trying to fetch the payment method in the psync flow using the payment_method_id in the payment attempt.
So to fix this we need to make the payment methods delete api as soft delete. In this case when the payment method is deleted the payment method for the corresponding
payment_method_id
will be set to inactive. So that there won't be data inconsistency.The text was updated successfully, but these errors were encountered: