[1]Google Pay Suica Goes Live:

    As anticipated by Android Police [2]earlier this month Suica has
    officially launched on [3]Google Pay in Japan. Mobile Suica has been
    available on the Android platform since 2011 via the
    [4]Osaifu-Keitai e-wallet service offered by the major Japanese
    carriers NTT Docomo, KDDI au and Softbank.

    With this rollout all the major stored value "prepaid" e-money cards
    are now on Google Pay: [5]Suica, [6]WAON, [7]nananco and [8]Rakuten
    EDY. JCB and JACCS credit card support and the Japanese P2P startup
    [9]Kyash service is promised for later this summer. It's not clear
    however what Android devices are supported beyond Osaifu-Keitai
    models from the major JP carriers. As I wrote earlier, FeliCa
    support on Android devices outside of the Japan market is a
    [10]complicated story, Google support of FeliCa up to now has been
    uneven at best.

    Hopefully we'll get a clearer picture in the next few days.

  (Via [11]Ata Distance)

  This might be too little, too late. Apple Pay has a huge lead here. The
  fragmented nature of Android devices doesn't help.

  UPDATE: [12]More Google Pay Suica MIA:

    Japanese Twitter users are posting lots of interesting details and
    the list of [13]Google Pay Suica limitations continues to grow: one
    Suica per phone, limited (no?) Suica Commuter support, no Shinkansen
    e-tickets, Google Pay Suica transaction records only cover
    purchases, not transit, and so on.

    Osaifu-Keitai Android users will continue to rely on the Mobile
    Suica app to cover the functions that Google Pay Suica does not
    support.

  (Via [14]Ata Distance)

  UPDATE 2: [15]Google Pay + HCE-F ≠ FeliCa Suica:

    Google Pay users outside of Japan who do not have a Osaifu-Keitai
    compatible model are waking up to the rude fact that Google Pay does
    not give them all that FeliCa Apple Pay Suica-like goodness out of
    the box.

    Google Pay Japan is exactly what Android Pay Japan was: a thin
    veneer over Osaifu-Keitai that confuses the hell out of Android
    users around the world. A lot of angry users will vent that this is
    a 'Japanese tech' failure but the reality is that this is simply a
    Google choice. Google could have licensed the entire FeliCa stack
    like Apple did but they didn't.

    My money says it is a market related political choice to keep the JP
    carriers happy selling carrier locked Android devices. The Android
    equivalent of the [16]Global FeliCa iPhone has yet to appear.

  (Via [17]Ata Distance)
  Also on:

  [18]Twitter
    __________________________________________________________________

  My original entry is here: [19]Google Pay Suica Goes Live. It posted
  Fri, 25 May 2018 01:49:23 +0000.
  Filed under: Japan, tech,

References

  1. https://atadistance.net/2018/05/24/google-pay-suica-goes-live/
  2. https://www.androidpolice.com/2018/04/22/google-pay-v1-57-prepares-support-airline-boarding-passes-event-tickets-suica-waon-payment-cards-apk-teardown/
  3. https://pay.google.com/intl/ja_jp/about/
  4. https://en.wikipedia.org/wiki/Osaifu-Keitai
  5. http://www.jreast.co.jp/mobilesuica/android/
  6. https://www.waon.net/
  7. https://www.nanaco-net.jp/
  8. https://edy.rakuten.co.jp/howto/
  9. https://kyash.co/en/company/#vision
 10. https://atadistance.net/2018/05/03/google-pay-suica/
 11. https://atadistance.net/
 12. https://atadistance.net/2018/05/24/more-google-pay-suica-mia/
 13. https://atadistance.net/2018/05/24/google-pay-suica-goes-live/
 14. https://atadistance.net/
 15. https://atadistance.net/2018/05/24/google-pay-hce-f-≠-felica-suica/
 16. https://atadistance.net/2017/09/12/iphone-x-keynote-global-felica/
 17. https://atadistance.net/
 18. https://twitter.com/TokyoGringo/status/999830823485534210
 19. https://www.prjorgensen.com/?p=1121

You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.