4 ms·
They do it for CC numbers too, as outlined in their page for developpers [1]: > To ensure that the Not Secure warning is not displayed for your pages, you must
by hk__2 10y ago
They do it for CC numbers too, as outlined in their page for developpers [1]:
> To ensure that the Not Secure warning is not displayed for your pages, you must ensure that all forms containing <input type=password> elements and any inputs detected as credit card fields are present only on secure origins.
[1]: https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn https://developers.google.com/web/updates/2016/10/avoid-not-...
- kuschku 10y agoDo they also do it for IBAN?
- icebraining 10y agoThe people who decided that the new SEPA payments should include a way for creditors to take people's money using just public information and their signature should be fired. It's like they learned nothing from the billions of dollars wasted from fraud in the credit card system. Payments should always start after an explicit order by the payer to their bank, not just having the payee say "trust me, they totally want me to have this money".
- kuschku 10y agoWell, luckily, there is! SEPA is a bi-directional protocol – if you try to take money from a bank account, the bank can say "nope", and the transaction can fail (with the person trying to pull the money taking the loss). As banks allow you to configure this – mine allows me to disallow all direct debit, or disallow foreign direct debit, or only allow it from specific companies – this is not an issue.