#TheDoubleBear - Android
lilac flicker
Any updates?
agile sparrow
Still searching, give me more couple of minutes please
hazy egret
I think I've looked into this in the past and there's no direct callback for it
lilac flicker
In that case, I can achieve this only by calling CustomerSession.getInstance().getPaymentMethods again?
hazy egret
that would be an option I suppose yes, listing the PaymentMethods again and comparing to some initial state
lilac flicker
Given scenario is simple, In payment screen, user has a card which is the app's default payment at the moment. User goes to this screen and remove the card and goes back to payment screen and he still see the removed card because I don't have any callback to receive that card was removed!
Not sure why it's not supported out of the box! We have this onPaymentSessionDataChanged callback and I expect it to provide it for me!
hazy egret
makes sense and is feedback I think I've raised before, we don't really actively develop that component any more since we focus on the PaymentSheet as the default integration
lilac flicker
Can you please share more about this PaymentSheet? A link to refer maybe?
lilac flicker
Thank you 🙂
I don't see a specific mention about this issue in the document! The issue I mentioned won't happen in PaymentSheets?
hazy egret
well it works completely differently and is a different integration so it's not directly comparable. I'm not sure about how it works with notification of removing payment methods and I'm a bit too swamped to test it unfortunately
lilac flicker
No problem, thank you again..