James Lewes

I am a dedicated vastly experienced technologist with a love of computing working at all levels from VP engineering to Developer. Over the last few years, I have enjoyed building on my technical experience in payments to architecture and management I am writing this blog to share some of that

Table of contents: * Leadership * Languages * Platforms * DevOps * Utilities * Security * Payment schemes * Support * Fraud Prevention Leadership * Management - At Bankable manage four teams comprising a total of 30 engineers in five countries * Offshoring - At Bankable established three teams in India * Nearshoring - Managed a team in France while at Bankable

(These are to demonstrate the range of my technical expertise where I had a more hands-on role. Projects where I was leading a team have some overlap but are separate from the ones below.) HSM cloud processing Role: Architect / VP Engineering Organisation: Bankable When: 2023 Designed the iteration to the

When Orginisation Role Location 2022 - Bankable VP Engineering London UK 2012 - 2022 WorldPay / FIS Principle Developer Technical Lead Architect Senior Developer Consultant London UK 2009 - 2012 Nationwide Building Society Consultant Swindon UK 2009 VocaLink Consultant Harrogate UK 2008 ANZ National Bank Consultant Wellington NZ 2006 - 2008

In my previous post, I detailed how to accept traffic into a Kubernetes cluster through ingress. This post will expand on how to secure these connections through a Secure Socket Layer (SSL) certificate. To do this we will use a certificate manager and the services of the lovely people at

Note This post outlines generic card processing. Card schemes and regions within card schemes vary widely. For example, I will assume dual messages, i.e. separate phases for authorisation and clearing. In a number of regions, this is done as a single phase. Also, in reality there are institutions who