In a latest collaboration with banks, Google expands Android Pay’s capabilities as an open platform, and moves toward to empowering mobile payments everywhere.
To this end, Android Pay now joining several banks around the world—including “Bank of America, Bank of New Zealand, Discover, mBank and USAA,” making it even easier to use cards with Android Pay.
Here is it works:
All existing customer of these banks, now with just a click of a button inside their mobile banking app can easily add cards to Android Pay.
Once a setup completes, using tap and pay on your phone, you can pay at stores wherever you see the Android Pay button in apps and on the mobile web. After successful transaction, Android Pay will send you a notification.
Android Things Developer Preview 3 (DP3), brings new features and bug fixes to the Internet of Things (IoT) products platform including added support for Android Bluetooth APIs and USB Host support.
Developers can now quickly build smart devices using Android APIs and Google services, while staying secure with updates directly from Google.
The System-on-Module (SoM) architecture supports prototyping with development boards, and then scaling them to large production runs while using the same Board Support Package (BSP) from Google.
Android O also introduces some improvements to help provide user control over the use of identifiers including:
- limiting the use of device-scoped identifiers that are not resettable
- updating the Android O Wi-Fi stack in conjunction with changes to the Wi-Fi chipset firmware used by Pixel, Pixel XL and Nexus 5x phones to randomize MAC addresses in probe requests
- updating the way that applications request account information and providing more user-facing control
In addition, Android O will also drop insecure TLS version fallback in HttpsURLConnection, to improve security. “The workaround is no longer needed, because fewer than 0.01% of web servers relied on it as of late 2015,” the team said.
“TLS version fallback is a compatibility workaround in the HTTPS stack to connect to servers that do not implement TLS protocol version negotiation correctly.”
In Android O, “it will no longer attempt those retries. Connections to servers that correctly implement TLS protocol version negotiation are not affected.”
Update 04/14: FORTIFY, an important security feature available in Android since mid of 2012, is a set of extensions to C standard library that tries to catch the incorrect use of standard functions, such as memset, sprintf, open, and others.
The new redesigned FORTIFY has three new primary features:
- If FORTIFY detects a bad call to a standard library function at compile-time, it won’t allow your code to compile until the bug is fixed.
- If FORTIFY doesn’t have enough information, or if the code is definitely safe, FORTIFY compiles away into nothing. This means that FORTIFY has 0 runtime overhead when used in a context where it can’t find a bug.
- Otherwise, FORTIFY adds checks to dynamically determine if the questionable code is buggy. If it detects bugs, FORTIFY will print out some debugging information and abort the program.