The 3D Secure (3DS) flow is one of the most bug-prone aspects of implementing a payment method. It seems easy (after all, the bank does the heavy lifting) but it can cause serious issues within an application’s checkout process. Lost orders, price mismatches, orders pending forever. Sound familiar?

How does authentication work? How can it be implemented securely? Who saves sessions? How long do they last? These are questions I get asked a lot, and I hope to answer them comprehensively in this post.

The Factory Method pattern belongs to the group of creational design patterns. Its main purpose is to create configurable objects based on given data.

The sixty-four-dollar question: what’s the difference between implementing a and extending a class? Let’s make things clear in no time.

In ES6 (ECMAScript 6) JavaScript modules, you can export values from a module and import them into another module. This is great because it allows you to organize, modularize and reuse code in a very efficient way.

Memoization is a caching technique that consists of saving the result of an expensive function and returning it if the same inputs are provided again. In short, it’s like having a “no smoking” sign inside a restaurant instead of going to each customer and asking them not to light their cigarettes.

For the most part, programming means managing data. A lot of data. This job is mostly about assembling and disassembling objects, joining them, dividing them, passing them on to functions.