Open albin-engstrom opened 1 week ago
I have not had an issue with this (Neither with German nor Luxembourgian banks) so it seems to be a more particular problem with your bank / some banks.
I have not had an issue with this (Neither with German nor Luxembourgian banks) so it seems to be a more particular problem with your bank / some banks.
All discussions I've seen about it seem to talk about the EU in general, and the PSD2 directive specifically, but perhaps there are some flexibility in how countries implement it. Although I've seen no mentions before now of some EU countries or banks that works.
I've personally tried with two separate Swedish banks.
This is not an issue on your end, but rather Google's.
As far as I've gathered after trying and failing is that to create the Billing Account that is necessary to make he API key functional Google wants to give you a 0 cost charge to the card you've provided.
This, for several years now, is illegal in the EU. So if you have an EU bank you can't do that and the charge silently fails.
The only workaround is to get a bank and card from outside the EU, which I suppose for companies is easy enough for Google to not change this. But for individuals that's a big hurdle.
I'm bringing this up because I'd assume it's likely that others have and will encounter this issue when trying to create an API key and it would be useful information to include in your tutorial for creating a key.
To ease further research into the topic; The error that Google throws is
OR-CAVT-01
and the issue supposedly stems from the PSD2 EU directive.