It’s also about friction.
No one wants to troubleshoot a card decline by logging into their mobile browser bank account in checkout at the grocery store.
> “Just log into your bank account on the mobile web browser” is a pretty clunky way to see why your card declined.
But that's because the user experience as designed is more hostile or not otherwise accounting for mobile use--right? Or are you saying there is a limit to the web platform's ability to reduce friction?
You mean some kind of perceived personal convenience through the uneven-handed profit of others and at the expense of everyone else.
Trying to check why your card was declined at a checkout—while still standing at said checkout? Troubleshooting "PIN issues" (meaning your bad)? Is everyone still standing behind you at this point? LOL. Exactly.
No one wants to troubleshoot a card decline by having to download and install a 700MB bank app in checkout at the grocery store either. Personally I'll take the browser login every time in that situation!
My credit card doesn't need me to lock/unlock it, doesn't require I have a phone with me, and certainly doesn't require an app. The last thing I ever would want is for the people in charge of "apps" to have access to my finances. All you are doing is creating another layer where something is allowed to tell you "No". Why would you choose this?