Android Pay support for Visa Checkout, Masterpass inbound

Mobile payment systems don’t make headlines nowadays. While that might imply that they’re not the hot items many thought they would be, it could also be because they’ve become so normal, so ingrained in modern lives. Aiming for the latter, more optimistic scenario, Google has announced that Android Pay will be embracing more purchases done on the mobile web. In particular, it will be supporting online shops that use Visa’s Checkout and MasterCard’s Masterpass platforms, offering convenience not just for buyers but for merchants as well.

READ:   GIONEE S6s With 3 Gig Ram, 32gig Rom

Paying using your smartphone isn’t exactly new but its first incarnations were of course limited to paying for apps and digital content. Mobile payment opened the doors for that to cross over to the physical realm, paying for physical goods, whether online or in person.

While in-store purchases are the most sensationalized aspect of mobile payment systems, buying online is still perhaps the most common use case. It also happens to often be the most laborious, involving multiple steps, different payment methods, and everything in between or a combination of those.

READ:   Subscribe For 1.5Gb For 1k And Double It To 3gb On Mtn

Platforms like Android Pay aim to reduce all of that to just step, either placing your finger on a sensor or entering a PIN code. With this new partnership with Visa and MasterCard, Google is aiming to embrace all web purchases made through smartphones, at least those using Visa Checkout and Masterpass. Considering these are two of the biggest payment solutions, that’s going to be quite a lot.

Google plans to roll out this support early next year, which should give merchants ample time to prepare for a flood of successful purchases. Or so Google wants them to believe. Lowering the barrier for purchases, in its opinion, will naturally translate to improved sales, something we’ll have to wait for next year to prove.

Add a Comment

Your email address will not be published. Required fields are marked *