THE PAYMENTS TRACE SEARCH/

Over 20 years in technology. 12+ years leading in payments architecture and strategy.

Some of the key aspects of my work

Abstract view of a latticed dome ceiling, structural ribs radiating to a central point.

Full payment lifecycle orchestration

Payment initiation journeys can start across a range of channels, from point of sale to e-commerce and m-commerce. From there they move through consent and enrolment and on through the whole payment lifecycle, including authorisation, settlement, refunds, disputes, and fraud.

That pattern repeats more or less across every scheme, but what happens inside each stage does not, because each scheme's own rulebook defines it, not necessarily a convention inherited across a shared payment-method family.

Open banking and iDEAL are a case in point. They entered the market with no concept of chargeback at all, whereas Wero has built a chargeback-style dispute process into its scheme design. That is the kind of variation that only surfaces once a rulebook and API specifications are examined in detail, rather than assumed from the scheme's family or shape.

A big part of my work is building that discipline, orchestrating the entire payment lifecycle and delivering it to merchants and partners through consistent API interfaces and event notifications. The goal is to harmonise their experience at the point of initiation, providing a single, dependable way to interact with every scheme and payment method. This helps us adopt each new lifecycle as it arrives, while the complexity and detail that live within each payment method and scheme are absorbed by the architecture I define rather than passed on to them.

Whilst I am passionate about payments, our customers and partners want predictable, low-friction, consistent outcomes and experiences, and this orchestration is designed to deliver them. It only holds together under a clear end-to-end architectural vision the whole organisation buys into, so defining and championing that vision and its roadmap, and holding cross-domain stakeholders accountable for delivery, are among my key responsibilities.

Interior of a grand atrium with tiered balconies rising toward a glass roof.

Target architecture through M&A and ownership change

What a business asks of its architecture changes with who owns it. Private equity provides capital that accelerates investment, pays down technical debt, and backs innovation wherever strategic value can be demonstrated. A publicly listed company operates under a different discipline, where capital investment is more constrained. Every initiative competes on the strength of its business case, with levers including cost, margin growth, and operating leverage.

I have lived that cycle from the inside more than once. I joined Worldpay as private equity was extricating it from RBS. I helped form the architecture and the practices a newly independent processor needed. I stayed through the London Stock Exchange IPO, the Vantiv merger, the FIS years and subsequent divestment. I experienced a second spell under private equity with GTCR, and now the $24bn acquisition by Global Payments. Each change of ownership reset what my work had to optimise for, whilst the roadmap it governed kept moving.

Mergers and Acquisitions (M&A) also puts architecture on the other side of the table. Technical due diligence for an acquisition means reviewing its codebase, security, resilience, and engineering practices in detail before and after the deal, and quantifying what it would take to bring the asset up to the standards a global processor must meet. I have seen that work change how an acquisition was integrated, with capital already earmarked for its expansion redirected towards the strategic platform once the true cost was visible. Whether an acquired platform is integrated or kept separate is decided, among other things, by that analysis, not just by the deal announcement.

Today, within the combined organisation, my responsibility is the Target Architecture Model (TAM) for alternative payments (digital payments). I hold the pen, which means leading discovery across the combined estate, building balanced scorecards that give contending platforms a clean, unbiased evaluation, and carrying the decision on the go-forward, growth-focused platform. Holding the pen does not mean deciding alone. The TAM only stands if engineering can build it and be held to account for delivering it, and if product can see their roadmap live on it, unlocking commercial value in support of the business's objectives. The three of us have to agree, and we reach the target state through continuously negotiated and refined transitional states.

Patterns are what make this repeatable. A market entry with data sovereignty requirements does not start from a blank page, because the data flows and the operating model that answered that constraint elsewhere already exist as reusable assets, and everybody understands a pattern, which is what lets conversations with regulators, partners and our own legal and compliance teams move at pace. A seat at the strategy table is earned rather than given. Mine is held through artefacts the organisation has learned to trust, and against a movable target state, with the architecture adjusted continuously whilst the business constantly transforms around it.

Aerial view of a multi-lane highway interchange curving through open landscape.

Zero-to-one launches and new market entry

Taking a product from zero to one (0→1) is different from maturing a roadmap. Incremental delivery adds features to an existing capability, and the machinery for it is well-oiled. A zero-to-one launch starts earlier, at the ideation stage, with product, filtering, and sizing to determine whether a business case for investment exists at all, and to identify where the idea depends on an enterprise capability that has not yet been built. Spotting that dependency at the ideation stage, rather than midway through delivery, is where my work starts.

My part runs from that first conversation to a clean handoff with engineering. Clean means the proposed architecture is well understood by the teams who will build it, and that the operational teams have worked through the runbooks and solution design to keep it running day to day. Architecture that cannot be operationalised is not finished, and the two disciplines depend on each other throughout.

Wero is a recent example. Worldpay, now Global Payments, joined the European Payments Initiative (EPI) as a Principal Member to enable Wero for merchants, and work of this kind starts long before an announcement. That meant sitting with product to understand what the EPI was building and what its rulebook would mean for merchants in practice, since Wero is not a like-for-like replacement for the schemes it succeeds. Its settlement model changes how refunds must be funded and managed. Reading that early, in the scheme's own documentation, turned a payment-method launch into the design of a new enterprise capability, with its own engineering effort and its own operating model, rather than another integration.

New market entry runs on the same discipline at a larger scale. The architecture is one thread in a cascade of regulatory approvals, legal entities, banking relationships, payment routes, contracts and operational readiness, and my work has ranged from the merchant-acquirer response to the Central Bank of the UAE's Aani requirement to licence applications in new markets, navigated with specialist consulting partners. I often build the technical material that goes to a regulator in sufficient depth that the regulator's questions can be answered and the review can move forward.

Not every part of my role is collaborative, though. Once the organisation has committed to a target architecture, my job is to act as its conscience, because each risk-adjusted, time-critical and commercially important deviation from it creates debt that the organisation has to pay down tomorrow, and that tomorrow sometimes never comes. Holding and negotiating that line, launch after launch, is what keeps each launch building on the last rather than borrowing against it.

Where the work has taken me

delivery depth market expertise
click a tinted region to zoom

At this level

The world view. Oxblood markets are delivery stories and slate markets are architecture and advisory expertise. The pale tint marks the regional scheme layers, Alipay+, WeChat Pay and GrabPay territory in APAC.