After launching in the US last year, Android Pay™ is finally coming to the UK. It has enormous potential to make 2016 a very significant year for mobile payments. Android has a 51.9 %* market share in the UK which means millions of Android users will now be able to pay for things quickly and securely with just a single tap, whether in-store or in-app.
Security is at the heart of what we do here at judo, and to ensure that our platform and services are adhering to the latest security standards laid out by the PCI council (PCI DSS 3.1), we have made some updates to our API and SDKs.
These updates mean that we will be ending support for TLS 1.0 and below on 20th October 2016. After that date, any API requests or dashboard sessions will need to use either TLS 1.1 or TLS 1.2. (However, while not being immediately phased out, TLS 1.1’s days are numbered as well, so we would highly recommend an upgrade to TLS 1.2.)
This summer, I came across an opportunity to write my first SDK, so I leapt at it. As developers, there is something very appealing about writing software for use by other developers. It might be because of the sense of solidarity that you’ve made life easier for sisters/brothers in code, or the thrill of a backseat driver finally getting a chance at the wheel. That is until the realisation that the demographic you’re serving will also be the best equipped to critique your output, this is especially true when producing an open source repository.
So below are some lessons (some key, some trivial) that I learned while coding judo’s Xamarin SDK.
As an app developer or retailer – you have the sweetest opportunity to engage, and sell – to your loyal customer base in the coming months. Furthermore, this is the time of year to attract and retain new customers with great offers during a time of commercial frenzy.
Experts have predicted that the frenzy of Black Friday can ‘lead to the first £1bn online shopping day in the UK’. A recent survey also suggested that many shoppers have been put off by the frantic in-store shopping experience, and hence ‘only 38 per cent of Britons plan to hit the shops on Black Friday as opposed to 44 per cent last year’.
To help you get ready for the impending holiday season, we have pulled together some tips to make sure your mobile app is prepared when shoppers arrive looking for holiday deals.
Last week, James Quinn, the Group Business Editor of Telegraph Media Group, wrote that Domino’s Pizza is ‘far more valuable a digital company than any tech unicorn’ (read the full piece here). It is a good opinion piece, and we agree that Domino’s has seen major success in their investment in digital and mobile channels (we like what they did with their app, we even wrote about it here). However, it is rather concerning that one of our country’s leading business voices doesn’t seem to buy into the future of London: ‘so-called unicorn tech companies’.
Mobile now accounts for more than a quarter of all e-commerce transactions globally, and that number is increasing rapidly as our shopping behaviour continues to shift towards mobile first. The speed of commerce growth on mobile channels is now 3 times faster than on traditional e-commerce channels. UK commuters are already spending £9.3bn a year on the supercomputers in their pockets. We are increasingly trained to expect the purchasing experience on mobile to not only be easy but also fast. Which is why an overwhelming 69% of consumers would abandon a purchase if the checkout process within an app or website is not optimised for mobile devices.
Why is it then, that most of the top 100 retailers in the UK are still failing to offer customers a quick and seamless native mobile checkout experience?
1. Added support for loyalty cards, giving you another reason to keep using Apple Pay
(image from iphonehacks.com)
iOS 9 will give you the ability to add brand loyalty cards into Wallet (the new Passbook), so you can earn and redeem rewards while paying with Apple Pay. This is an important improvement because now consumers will have another reason to choose Apple Pay as their payment method of choice. Not only is Apple Pay easy, quick and secure, it is now also rewarding to use.
As consumers’ interest and excitement for Apple Pay escalate throughout this month, there are certain things that merchants should be prepped for before its arrival.
For example, if a customer purchase something from you via Apple Pay, how exactly do you process a return if needed? No idea? I’ve done a little digging and this is what I found on Apple’s support page: read more
What is Apple Pay?
Apple Pay is an easy, secure, private way for customers to pay while they’re dining in or ordering through an app. It is currently available on devices that has a secure element chip, which is a hardware chip dedicated to securely storing card information. These devices include iPhone 6, 6 Plus, iPad Air 2, iPad mini 3, and the Apple Watch (when paired with an iPhone 5 or 6)
Since the announcement of Apple Pay‘s inevitable expansion to the UK, many commentators has been speculating the impact it will have on in-store retail. Will consumers and merchants jump quickly on-board with the service? Will it really make paying for goods and services easier at a physical location?
What we haven’t talked enough about is the impact it will have on paying for goods and services within an app. Think about it, the next time you want to splurge on a nice sofa for your living room, you can simply use Apple Pay to complete checkout in just 1 step. No more account setup. No more lengthy forms for billing and shipping information. No more time to abandon a purchase before checkout is complete.
This article in UK’s Business Insider explores why being able to pay for goods and services in-app with one touch is truly where Apple Pay shines.