The DevOps mindset is at the core of how we maintain a robust infrastructure here at Judopay, and we’re always on the lookout for anything that can improve our existing toolset.
With that in mind, we have recently looked at the Concourse CI system as a possible continuous integration/build server. The product looks very strong, but documentation for installing is sparse as it’s still in its infancy, so we thought we’d go through some detail and gotchas here for anyone else thinking of giving it a try. read more
What hardware should you give a developer? The answer is, it depends. Below is an overview of what we’ve invested in and why it’s important to us.
For the best part of the past ten years, I’ve been a software developer, with the majority of that time building .NET applications. Microsoft has a platform that enables languages such as C# to be incredibly powerful, constantly evolving, and expressive, yet easy to read and follow. Technologies such as ASP.NET MVC, WebAPI and EntityFramework remove much of the complexity from the developer, allowing them to concentrate on their primary tasks — building and releasing software.
Recently, I was given the opportunity to cross-train, learn and contribute to judo’s iOS native SDKs. Given the above, I surprised myself with how quickly I jumped at the chance. I’ve been working with the SDK team for just over a month now, below are some initial thoughts from my jump to the ‘other’ side.
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.
We have come a long way from the 4.1 iOS Objective-C SDK. Since the release, we have introduced our new collection of Swift SDKs, judoSwift, which simplified the communications with judo’s REST API, and paved the way for the feature rich judoKit. Our kit contains out-of-the-box functionalities like Address Verification System (AVS), 3D Secure, and other input verifications necessary for submitting card information for payments and other transactions. Together with our mobile-specific fraud prevention judoShield module, we provide the perfect basis that makes accepting transactions easier, simpler, and more secure.
In our pursuit to make payments in apps even more secure, and due to changes in PCI’s security standards, we are phasing out some older versions of our tech. This means you might need to upgrade to our latest SDKs by the 20th October 2016.
This guide will walk you through the steps needed to upgrade your app to the latest SDK.
In version 5.1 of our Android SDK, we wanted to introduce lots of new features, focus on improving the quality of the codebase, and make customizing the SDK to match your app’s brand easier. With this in mind, it made sense to completely rewrite the SDK from the ground up.
If you’re using an older version of the Android SDK (pre 5.1), you will need to complete an upgrade to this version by 20th October 2016 due to PCI Compliance changes that were introduced (PCI DSS 3.1).
To make the process of upgrading to version 5.1 as smooth as possible, let’s walk through the main steps required to get your app updated.
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.