Digital wallet: from discovery to an in-house payments ecosystem
I contributed as a Technical Product Manager to the end-to-end development of a government digital wallet, from discovery and competitive analysis through production as a multi-tenant platform for different public-sector organizations.
My role: Technical Product Manager, Casa de Moneda Argentina
The problem
Discovery
Decisions and trade-offs
Design a multi-tenant architecture
We defined a model with central administration at Casa de Moneda and independent tenants for each organization. Each tenant could have its own environments, database, frontend and mobile application while sharing a common product foundation. This allowed capabilities to be reused and the solution to scale without building a separate wallet from scratch for every organization.
Ruled out: Building an independent solution for every organization. Although it allowed greater initial customization, it increased maintenance costs, duplicated capabilities and made product evolution more difficult.
Integrate the wallet with the financial ecosystem through APIs
I coordinated API integrations with organizations such as RENAPER, COELSA and Banco Hipotecario, aligning functional requirements, technical teams, business stakeholders and external providers. These integrations supported processes such as identity validation and the financial operations required by the wallet.
Build in-house capabilities within the payments ecosystem
During development, Casa de Moneda progressed toward certification as a Payment Service Provider (PSP). This was part of a strategy to reduce reliance on external providers and keep a greater share of the operation within its own ecosystem.
Validate the product through a production pilot
Before expanding the solution to other organizations, Casa de Moneda's internal cafeteria was used as the first production use case. Users could use funds available in the wallet to pay for lunch, allowing the complete flow to be validated in a real environment.
Ruled out: Expanding externally before validating the complete flow. The internal pilot reduced risk and allowed adjustments to be identified before offering the platform to other organizations.