Software for financial services. Built to hold up under regulation.
For payment companies, banks, lenders and B2B fintechs. Gateways, checkout, card-management portals, and the reconciliation and audit work regulated teams need — the same work we have shipped for Pay2m, Kuickpay and 1Link.
We build payment gateways, checkout, card-management portals and invoicing for fintechs and banks in Qatar, Saudi Arabia, the UAE and Oman, then Europe and Pakistan. Our work includes Pay2m, a Qatar gateway built from the client's idea, Kuickpay's checkout, in production for over four years, and a portal for 1Link, Pakistan's largest payment switch.
Updated November 2026
A practice, not a sales territory.
Fintech doesn’t forgive cutting corners. The systems we build run inside PCI DSS, KYC/AML and each market's central-bank rules — Qatar Central Bank, SAMA, the CBUAE, the State Bank of Pakistan — as a design constraint from the first commit, not a checkbox at launch.
This is the sector where we have the most to show. We built Pay2m, a Qatar payment gateway and invoicing platform, from the client's idea to a live product. We have worked on Kuickpay's checkout in Pakistan for more than four years, and we built the card-management portal 1Link — Pakistan's largest shared payment switch — runs on its own infrastructure. We design for the audit, the incident and the migration, because those are the moments fintech teams pay for.
We are not a QSA, an auditor or a licensed payment institution. We build systems designed to pass those reviews; the certification itself is a separate audit, done by a specialist.
Sub-verticals.
Common engagements.
Payment gateway builds
Merchant onboarding, payment links, hosted checkout, settlement and reconciliation, and the merchant dashboard that shows where the money is. Pay2m in Qatar was built this way, from the client's idea.
Checkout that doesn't drop payments
Idempotent payment requests, retries that don't double-charge, clear failure states, and the bank and wallet integrations behind them. Kuickpay's checkout has been in production with us for more than four years.
Portals for regulated operations
Role-based access, maker-checker approvals, reporting and audit trails for the teams who handle cards, disputes and limits. We built this for 1Link, deployed on its own infrastructure.
PCI DSS scope reduction
Tokenisation, hosted payment fields and vaulting so raw card data stays out of your systems, plus secrets management and the evidence your auditor will ask for. We build to these patterns; certification is a separate audit.
Legacy core migrations
Moving off older core systems onto modern services without breaking ledger continuity — run in parallel, reconciled daily, cut over in stages.
Fraud and credit decisioning
Rules first, models where the data supports them, with every decision logged and explainable. We build the pipeline and the audit trail; the risk policy stays yours.
Fintech, market by market.
Gulf — Qatar, UAE, Saudi Arabia, Oman
Each central bank runs its own licensing and sandbox — QCB in Qatar, SAMA in Saudi Arabia, the CBUAE in the UAE, the Central Bank of Oman. Local debit networks such as NAPS and mada, and Apple Pay, matter as much as international cards, and Arabic and English interfaces are expected. Saudi B2B products also need ZATCA FATOORA e-invoicing.
Spain, Italy, France
PSD2 strong customer authentication, GDPR and open-banking APIs set the build. Italy's SDI and Spain's VeriFactu rules change how invoices must be issued, so invoicing products need those flows from the start.
Pakistan
Home market. Raast instant payments, 1Link's switch and mobile wallets sit underneath most digital payments, and the State Bank sets the rules for EMIs and payment providers. Our Kuickpay and 1Link work is here.
Fintech we have shipped.
When a licensed platform is the better buy.
If you need a licensed payment processor, card issuer or core banking system, buy one — an established gateway or a white-label core gets you to market faster than a custom build, and the licence is theirs. Hire us for what sits on top: your product, checkout, portals and integrations. And if you need someone to certify you, that is an auditor, not us.
Where to start.
Built for regulated work.
Tools we reach for first.
Frequently asked.
6 questions answered. Still have one? Reach out.
Yes, but we hold no PCI certification ourselves and we are not a QSA. We design for minimum scope — tokenisation, hosted payment fields, vaulting — so raw card data stays out of your systems. Certification is a separate audit, done by a QSA or a specialist consultant.
Other sectors.
Tell us where it hurts.
We will say honestly whether we have shipped in your sector, what transfers from the ones we have, and where the expensive mistakes usually are.