Depends on your phone, but for some qualcomm devices there was a vulnerability some time ago, iirc the OnePlus 15 has a dedicated thread on XDA. I also found this on XDA while trying to find the other exploit:
Side note, it's quite ironic, google being so heavily anti-root is forcing people to opt for root access via more hidden ways, making it easier to avoid root being detected.
But it's meant to be returned in cases where the server is a teapot, more specifically when it's a teapot requested to brew coffee, not for cases where it's not a teapot.
It's been taken down by DMCA copyright strikes on every western platform that could distribute it. That's why you can't find it on the Firefox extension store anymore
Many EU online shops accept SEPA payment. It isn't convenient, because it's a push payment (giro) which means the site can't stick it in the middle of the order flow and expect it to take a few seconds. Some users might have to visit a bank branch to send payment.
Not all banks do SEPA Instant, yeah. I suppose the answer to that is connecting using PSD2 and sending the payment request then checking payment actually went out (using something like https://gocardless.com/). Many countries also have local bank link systems (e.g. in the Baltics it’s common to have dedicated buttons in the payment form for the big 3 or 4 banks everyone uses).
I’m talking about in-person payments though. It would be so easy to implement QR payments backed by the existing SEPA Instant rails. Many bank apps already understand EPC QR codes (usually found on invoices), so shops could just show these to accept payment. In case your bank doesn’t support SEPA Instant, you could show the cashier the receipt in your bank app, which, well, horribly insecure, but probably fine for low-stakes cases like grocery shopping (you don’t want to be banned from your grocery store chain for forging a 35 € payment).
reply