Just dropping here some wisdom that might pop up to people looking up “Intesa Sanpaolo” (or San Paolo) on the search bar. The bank has begun using dynamic logos. The way this works (or is supposed to) is that after making a payment on a different platform (e.g. PC) you have to tap on a notification on your phone and then scan a sort of moving QR code on your screen using the bank app.
On my FP3 (/e/OS 3.7.2), I would get the notification but when I clicked on it, instead of opening up the scanner, it behaved just as though I had normally opened the app. At the fourth or fifth time I have tried, it did open the scanner and it worked perfectly. I should note that the time it worked, the phone was locked so that might make a difference. At any rate, I suppose that the gist of the story is - the dynamic logo on Intesa Sanpaolo does work, you just have to persevere.
I do not see any way on how to edit original wiki post with a table. So someone else will have to do that for me.
My previous contribution is still not represented in a table:
I also have news about FlikPay app (instant payment app for most of Slovenian banks) just started working. I do not know with what version. It also support NFC payment, but I did not test it if NFC payment works. However, I have tested in-app payments and they work.
You haven’t specified which model you have, mine is a Redmi Note 9s (miatoll), e-3.7.3-A15, unrooted.
I downloaded the two older versions, 10.52.1 and 10.56.1, from apkmirror.com onto my PC and transferred them to the phone. Each time, it always displays the warning message:
You’re lucky that your phone model works; others aren’t.
I just wanted to use Revolut as a digital wallet for small domestic payments or when travelling, to avoid the exorbitant exchange rates charged by our “beloved” traditional banks.
It’s a shame that Go$$le claims to be boosting “security” when, in reality, they’re losing control of our activity and the revenue generated by all the adverts they display, not to mention all the nonsense installed on our phones.
Zugriff verweigert. Aus Sicherheitsgründen kannst du diese App nur auf Geräten mit offizieller Software und bei Installation aus dem offiziellen App-store verwenden.
I don’t know who said that the BoursoBank (Boursorama) app is working, but it’s not the case. I’ve updated the table.
Also, about the Shelter workaround, it doesn’t have the “microG Services” app in the shelter tab, only the microG companion, so this workaround doesn’t actually work (FP6 with /e/OS 3.7.3)
It seems that many people use the BoursoBank app with the same configuration as yours.
I am one of them. It works for me in Shelter except for application notifications since version 3.6. I can log in, view all the information, and validate a payment initiated from a browser.
I use a browser for other operations. Therefore, I can’t say whether they work in the application.
Which is perfectly logic. You can use an Android device running Android 9 which hasn’t had security updates for 6 years… this device they classify as “trusted”. But your safe-as-hell running Android 16 device is not. Those banks and their app-programmers are planets away from realistic thinking. Somebody should tell em.
I re-read the last weeks threads about BoursoBank in this forum, and it’s totally random, a lot of people like me can’t manage to make it work. And when it works it’s either partial (like you) or by using complex workarounds like Shelter (which doesn’t work on my FP6).
So, we cannot say “OK” in this table. “OK” means “you install and it just works” like on a regular Android.
Considering your comments in the table and those regarding microG services, you may not have strictly followed the workaround to install the application in Shelter.
Today, the only way to use BoursoBank is to apply the workaround for the installation. Yes, it is not plug and play like Android, and there are some limits. However, it exists.
It’s a shame that your comment doesn’t mention the workaround even with its limits. I would have written “OK with limits” rather than “NOT_OK”.
So, /e/OS/ forum newcomers could decide to use or not the application with all relevant information.
You have already installed /e/OS/ 4.0 on your FP6 . I am waiting some weeks before switching from 3.7.3 to 4.0.
I saw yesterday in the Gitlab relese notes that BoursoBank should work better with /e/OS/ 4.0. It is a great piece of news that you confirm this.
Third Party Apps support
Apps that support GMS-free devices can now run on /e/OS thanks to a new option to hide microG from selected third-party apps. This should help apps like Swisscard and BoursoBank.
It depends on several factors:
. The country where you live
. The bank and/or app you use
. The brand and/or model of the phone you choose.
You can check out post [LIST] Banking Apps on /e/OS and [LIST] Banking Apps on /e/OS - #899 by Tien to get an idea of what to consider before choosing /e/ for your phone.
As for the phone model, in my opinion, it comes down to personal preference and luck, because:
. The brand and manufacturer may make unlocking the bootloader more difficult, or even impossible.
. App developers must comply with g$$gle’s requirements in order to publish/distribute it on the G$$gle Play Store.
. It may happen that the app works on one phone but not on another
. After an update, the app may stop working, and so on…
How ever 2fa still works with the app. So you can login to your banking via browser and confirm the login with the app. So this is a workaround for what its worth.
I am using a fair phone 6, with the latest official eos release.
Yeah, I mainly access via the browser, but it asks me to confirm transfers on my Android app. I’ve seen that Revolut works on /e/, so I guess I can use it for these operations.
Thanks a lot for your reply !
After some recent app update, a new message is showing off : “device not sure enough .. blahblahblah”
Is there a way to validate security without this damn play store ?
You are continuing re Crédit Agricole, any posibilty of a fix would depend on your results from your earlier request for help to “dig into the issue”. Did you find firstly to what extent the app is Google dependant?