
Dingpay
Product Designer
2025
Ding Wallet
The aim of the design for the wallet was to keep it simple and easy for users to select an asset and have their QR codes scanned. Users had to only select the desired asset, authenticate and use.

Each asset had it’s own record type for past events on the asset, for the transactions page I organized payments by date so users can easily look back at what they've spent and when. Each entry stays clean just the merchant name, time, and amount, nothing extra. The ticket archive works the same way but for past events.

Ding Wallet is your all-in-one digital wallet solution, designed to simplify everyday transactions and keep all your essentials in one place. Store your debit cards, bank accounts, event tickets, and more securely on your phone. Dingpay ensures fast, and easy contactless payment at point of sale and quick event check-ins, even when offline.
As part of the founding team I was charged with designing customer facing UI and internal & partner tools.
Ding Console (Web)
This was designed to allow partners track their merchants and their customers. The aim of the design was simple: our partners need to see what is happening through them. We had to cater for potential PSP and PTSP partners and make sure they saw what was needed for them.
I designer the dashboard to summarize what other important pages were showing using number metric and graphs, while still keeping it simple.

The transactions table was the usual record of the usual information from transactions but the details of each transaction varied and the transaction could be in progress depending on the type of partner, so we needed to show a timeline of the transaction process. This varied from Completed to in progress and also failure. All of this had to be showing along side the other transaction information.

Another important part of the dashboard in relation with our partners was the Webhooks page. I designed it to show all created endpoints by the partners and their states, the delivery status of each endpoint and a table to allow them retry failed once.


Dingpay
Product Designer
2025
Ding Wallet
The aim of the design for the wallet was to keep it simple and easy for users to select an asset and have their QR codes scanned. Users had to only select the desired asset, authenticate and use.

Each asset had it’s own record type for past events on the asset, for the transactions page I organized payments by date so users can easily look back at what they've spent and when. Each entry stays clean just the merchant name, time, and amount, nothing extra. The ticket archive works the same way but for past events.

Ding Wallet is your all-in-one digital wallet solution, designed to simplify everyday transactions and keep all your essentials in one place. Store your debit cards, bank accounts, event tickets, and more securely on your phone. Dingpay ensures fast, and easy contactless payment at point of sale and quick event check-ins, even when offline.
As part of the founding team I was charged with designing customer facing UI and internal & partner tools.
Ding Console (Web)
This was designed to allow partners track their merchants and their customers. The aim of the design was simple: our partners need to see what is happening through them. We had to cater for potential PSP and PTSP partners and make sure they saw what was needed for them.
I designer the dashboard to summarize what other important pages were showing using number metric and graphs, while still keeping it simple.

The transactions table was the usual record of the usual information from transactions but the details of each transaction varied and the transaction could be in progress depending on the type of partner, so we needed to show a timeline of the transaction process. This varied from Completed to in progress and also failure. All of this had to be showing along side the other transaction information.

Another important part of the dashboard in relation with our partners was the Webhooks page. I designed it to show all created endpoints by the partners and their states, the delivery status of each endpoint and a table to allow them retry failed once.







