About

Built on a single premise.

The product

eigin is being built to issue disposable virtual card numbers for UK consumers. When you pay with an eigin card, the merchant receives a payment confirmation and a virtual number. Your real card number is never transmitted. The virtual number is unlinkable. No card number thread connects your payments into a profile.

The card industry already uses tokenisation as a security measure. Apple Pay and Google Pay send tokens to merchants, not real card numbers. eigin extends that mechanism further: not just protecting the card number, but severing the persistent identity link that makes cross-merchant profiling possible.

The product runs on Visa and Mastercard rails via a regulated card issuing partner, operating under that partner's regulatory authorisation. Virtual card numbers are real card numbers that route identically to any other card. The novelty is not the technical mechanism. It is the privacy application of that mechanism, controlled by the user.

eigin is pre-launch. The company is incorporated in England and Wales. The product will be issued under the regulatory authorisation of a licensed BaaS partner. No financial service is currently being offered.

The founder

eigin is being built by Omer Yusuf, a UK-based founder building financial privacy infrastructure for UK consumers.

eigin started with a specific observation: payment privacy tools have existed in the US for years. Nothing equivalent exists for the UK or Europe. The regulatory framework, including UK GDPR, the Payment Services Regulations, and FCA consumer duty, already treats your financial data as yours. The infrastructure has not caught up.

eigin is being built to close that gap.

The infrastructure

eigin runs on EU-hosted infrastructure. The server is self-hosted on Hetzner in Nuremberg. No third-party analytics that track users across the web. Plausible Analytics for aggregated, cookieless traffic data, EU-hosted and GDPR-native. Postmark (transactional email) is operated by a US-headquartered company that runs EU/UK entities and is covered by standard contractual clauses under UK GDPR Article 46(2)(c). Card issuing will be provided by a regulated partner, to be disclosed at launch.

A privacy product should not be built on infrastructure that contradicts it. Every tool in the stack was chosen against that standard.

Questions, press, or partnership enquiries: contact@eigin.co