sta
August 2, 2022, 11:51am
1
Hi all,
How can I pay contactless “by card” in a store with my phone?
Until 31st of July 2022, I was able to use the Rabo Wallet app for contactless payments by the Rabobank (Dutch bank), this worked perfectly. But for some reason the Rabobank has decided to stop supporting it from 1 august forward and referred everyone to Google pay.
I installed Google pay, but it does not boot on my phone. I can install it, but after opening it just shows me a “loading picture” and nothing happens.
So how can I pay with my phone?
1 Like
tcecyk
August 3, 2022, 3:12pm
2
Google Pay very likely needs more original Google APIs present. In that thread the microG author explains what would be necessary for a banking Apps to add Cards to Google Pay.
But even with this implemented, if Google Pay itself then can work in all circumstances, without Google Play and more? I don’t know
opened 04:05PM - 23 Oct 20 UTC
## Vivid Money
### Description
_Vivid Money_ is a German fintech offering … bank services managed via an Android app. A customer can have multiple bank accounts. Most of the app functionality works fine with MicroG, however an account ("pocket") screen never completes loading **if a card is linked to the account**. There is no error message shown to the user. Other account screens load immediately and can be used without problems.
* Package name: **[vivid.money](https://play.google.com/store/apps/details?id=vivid.money)**
* Package version: **1.20.0.480** (Nov 24, 2020)
* MicroG version: **0.2.14.204215** (latest GitHub release build as of Nov 25, 2020)
* To reproduce, one has to log in to the app and tap on an account with a card linked to it; by default this is the _Main pocket_ label.
### Cause
ADB logcat inspection reveals the likely cause to be the _Google Pay_ (formerly _Google Wallet_) integration, **specifically the TapAndPay API calls**:
D GmsTapAndPaySvc: onBind: Intent { act=com.google.android.gms.tapandpay.service.BIND pkg=com.google.android.gms }
D GmsTapAndPaySvc: bound by: GetServiceRequest{serviceId=TAP_AND_PAY, gmsVersion=12451000, packageName='vivid.money', extras=Bundle[{}]}
D GmsTapAndPayImpl: onTransact [unknown]: 21, android.os.Parcel@2bd3dc, 16
D GmsTapAndPayImpl: onTransact [unknown]: 21, android.os.Parcel@55e6ce5, 16
When other account screens load succesfully there are no such calls logged.
### Workaround
The app allows the opening of several sub-accounts and reassigning the card to any of them, with immediate effect. Thus, you can link the card to an account other than the one you want to view or make changes to, open the account screen, which will now work, and relink the card back to the original account once you're finished.
## Related Issues
It seems similar issues affected a number of other apps relating to banking and payments in the past. Some of them have already been resolved. This is to keep track of all of them:
### Confirmed
* #1162 ([comment](https://github.com/microg/android_packages_apps_GmsCore/issues/1162#issuecomment-713026582)): _mBank_ (**pl.mbank**) @Natalcia's [comment](https://github.com/microg/GmsCore/issues/1245#issuecomment-734445893) from 2020-11-26
### Resolved
* #626: ~~_Revolut_ (**com.revolut.revolut**)~~ _Resolved as of 2020-11-03 per [comment](https://github.com/microg/GmsCore/issues/626#issuecomment-721033458)_
* #987: ~~_Yandex Taxi_ (**ru.yandex.taxi**)~~; #994: ~~_Uber_ (**com.ubercab**)~~; #1006: ~~_Uber Eats_ (**com.ubercab.eats**)~~ _Resolved as of 2020-11-27 per @selurvedu's [comment](https://github.com/microg/GmsCore/issues/994#issuecomment-734960495) (note: some of the earlier discussion for these issues related to Mapbox problems, which are unrelated)_
* #1162 ([comment](https://github.com/microg/android_packages_apps_GmsCore/issues/1162#issuecomment-713026582)): ~~_Vinted.pl_ (**pl.vinted**) Last confirmed 2020-10-20 (recently), however an update to MicroG as of 2020-11-25 might have fixed this issue.~~ _Resolved as of 2020-11-26 per @Natalcia's [comment](https://github.com/microg/GmsCore/issues/1245#issuecomment-734445893)_
* #1207: ~~_N26 Bank_ (**de.number26.android**), another German fintech, however the issue there is related to `GmsWalletPaySvc` and `GmsWalletOwSvc` instead, also there exists [a workaround](https://old.reddit.com/r/number26bank/comments/huacw1/using_the_n26_app_with_microg/) (downgrade to an older app version before _Google Pay_ integration)~~ _No longer an issue as of 2020-11-26, apparently was addressed earlier on the application side, per @ArchangeGabriel's [comment](https://github.com/microg/GmsCore/issues/1245#issuecomment-734252860)_
### Unconfirmed
* #372: _Google Assistant_ (**com.google.android.googlequicksearchbox**) Last confirmed 2017-12-07 (3 years ago). Might also be outside of the scope of the MicroG project since the issue pertains to a Google app.
* #971: _First Bus_ (**com.firstgroup.first.bus**) Last confirmed 2019-11-11 (a year ago).
## Current Status
According to @mar-v-in's [comment](https://github.com/microg/GmsCore/issues/1245#issuecomment-734969823), the current situation is (emphasis mine):
> * The Wallet Payment API **isReadyToPay()** dummy always returns that payment via Google Wallet Payment API is not available, so this should fix all apps that use that API for checkout / payment
> * The **SafeParcel** unknown fields are not an issue (though I could probably get rid of some of them easily so that logs are not spammed that much).
> * Banking apps sometimes use the **TapAndPay** API which allows them to add your bank account to Google Pay / Android Pay. This API is not yet implemented and probably causing issues here. As I guess one needs a bank account with that bank to try out, I can try to provide test builds, but debugging that way obviously is much harder.
What follows:
* Before reporting any issues that might be related to Google Pay/Wallet, make sure to update to version **0.2.14.204215** of **2020-11-25** or newer, and check if the issue is still present, as many of them should be resolved with this version
* When posting logcat dumps, ignore anything related to `SafeParcel`
* The **TapAndPay** API is not expected to work as of now
Banking apps sometimes use the TapAndPay API which allows them to add your bank account to Google Pay / Android Pay. This API is not yet implemented and probably causing issues here. As I guess one needs a bank account with that bank to try out, I can try to provide test builds, but debugging that way obviously is much harder.
so an adb logcat would clarify what Class the radobank App calls to add its Card etc, that microG could delegate if Google Pay is present
tcecyk
August 17, 2023, 11:03am
3
because lots of ppl click that microG link with a 2020 statement - microG still widens the Pay surface with classes and definitions, mostly to keep Apps from crashing that call into these
Q: Now do Google pay can work?
A: No. This is just the beginning of laying a foundation to get things to work.
1 Like