<aside>

Senior Software Engineer, Alfabolt, embedded at Nomod (YC S21) · Apr 2024 to Present

</aside>

About Nomod

en-ae(Screenshot HD).webp

Nomod is a YC S21 payments platform for merchants across the GCC. Its products cover payment links, invoices, checkout, in-person payments and QR-based payments across web and mobile.

It serves 40,000+ merchants and processes $350M+ in annualized payment volume.

At a glance

<aside>

170k+ transactions per quarter · 5 payment providers · Apple Pay + Google Pay · PCI DSS / VAPT work

</aside>


Rebuilding the payments architecture

The Problem

Nomod's Link, Invoice and Checkout products had grown from a small number of payment providers to several providers, wallets and payment methods. The frontend architecture had not grown with them.

Provider selection was tied to hardcoded frontend rules. Card forms were implemented separately for different providers, and Apple Pay and Google Pay logic was duplicated across integrations. Adding or changing a provider often required a frontend release even when the routing decision belonged on the backend.

That made payment retries, rerouting and new integrations harder to introduce safely.

What I Did