Tasdid Merchant

Not everyone who needs to pay a digital bill has SuperQi or a bank account. Tasdid Merchant gives them another option: they can take the bill to a nearby merchant, who looks it up and pays it through the mini-app inside SuperQi.

The merchant chooses a governorate, bill category and provider, then enters the account number from the bill. Tasdid Merchant shows the customer's name, bill number and amount due so the merchant can check the details before paying. The result is recorded in the merchant's payment history.

The Arabic, right-to-left interface accepts both Arabic and Western digits for account numbers, helping merchants use it naturally while serving customers at the counter.

I worked on Tasdid Merchant from December 2024 to February 2025 as a Software Engineer on the Billing Team. My changes covered provider lookup, the account number step and payment feedback.

The governorate needs to carry through to the provider list. I worked on that filtering so merchants saw the providers available in the location they chose. I also kept the provider's name visible on the account number screen, so the merchant could see which provider they were looking up a bill for.

A payment still processing shouldn't look like a failed payment. I worked on separate Arabic messages for paid, processing and failed results, and on showing an error when a payment couldn't start. The point was to give the merchant a useful answer at each of those stops.

Alongside those changes, I added Microsoft Clarity analytics and supported the builds used for testing. I worked in Svelte and TypeScript, with Vite and Tailwind CSS.

This was part of the Billing Team's work. My contribution was in the merchant interface and the feedback around bill lookup and payment, within the larger Tasdid service.

This mini-app runs inside SuperQi, so keeping its JavaScript payload small matters. Svelte was a good fit for that constraint.