01 / About
A payments person who can read the code, and an engineer who sits in the acceptance review.
I have spent ten years building software and the last five inside iGaming card payments: first as the architect of a gateway, now as the technical lead running payment channels across multiple PSPs.
Profile
The work I find most meaningful sits at the edge of what most teams avoid. Switching a live payment database with no downtime. Loading a million BIN records into a running system without touching the transaction hot path. Normalising error codes from several PSPs at once.
These are not glamorous problems, but getting them right is what separates a payment system that scales from one that breaks under pressure.
Because I have built a gateway myself, I can follow a failed transaction from the merchant request through the PSP response code to the issuer decline. Because I now run channels every day, I know which of those findings is worth acting on.

Career journey
How I got from web applications to payment infrastructure.
2013 – 2016
Systems and incidents
After an engineering degree at the University of the Punjab I joined Qarshi Industries in systems coordination. Part of the job was information security incident investigation: failure analysis, reporting, corrective action, closure. I did not know it yet, but that is most of what payment operations is.
2016 – 2020
Building for clients abroad
Four years at Elementary Logics writing full-stack applications in Laravel and CodeIgniter for international clients: e-commerce, automotive, booking. This is where I learned to ship, and to keep live systems running after shipping.
2020 – 2021
Scale, then money
At Bookme I worked on national-scale booking: hotel integrations, an Events module, Easypaisa wallet checkout. At Tech Scale I led the team behind Faktura, an invoicing platform synced live with e-conomic for Nordic SMEs. Software that handles other people's money has a different standard of correct.
2021 – 2026
A gateway of my own
At Developers Studio I designed and built CardEye, an international card payment gateway for iGaming merchants, and stayed to run it: architecture, PCI DSS, merchant integrations, a team of 7 to 8 engineers. It reached 7,000+ transactions a day across 10 active merchants.
2026 – now
The other side of the transaction
Today I am payment gateway technical lead, as a consultant, for a European payments company serving regulated iGaming merchants. Multiple PSPs, acquirers and alternative payment providers, a white-label platform, and a daily question: why did this decline, and what do we change?
How I work
Five habits clients end up relying on.
- 01
Follow the transaction, not the dashboard
Aggregates hide problems. I go down to the BIN, the MID and the response code until the cause has a name and an owner.
- 02
Say whose problem it is
An issuer decline, a fraud-rule decline and a provider failure look the same in a headline rate. Separating them is how the right person gets the ticket.
- 03
Change live systems without stopping them
Migrations, data loads and error-code rollouts under transaction load. Plan the path so the hot path never notices.
- 04
Write the procedure down
Data rules, metric definitions, onboarding steps. If it only works when I am in the room, it does not work.
- 05
No promises before the data
I will not quote an acceptance-rate uplift before I have seen the numbers. I will tell you what I find and what I would change.
Open to consulting engagements
Have a payment problem that needs tracing?
Tell me which providers are involved and what is going wrong, or what needs to go live. I will tell you plainly whether I can help.
- Tell me
- Which providers and markets are involved
- Show me
- What is failing, or what needs to go live
- You get
- A plain answer on whether I can help