Change the receipt. See why the order takes a different path.
OrderDEMO-1042
ExpectedEGP 500.00
Receipt amountEGP 500.00
Receipt referenceDEMO-1042
Receive→Compare→Confirm
The details line up.
The amount and reference match. The gateway can send a confirmation callback to the store.
Simplified local example with fictional data. No payment is made and no live system is contacted.
Selected work
Three products, seen through their workflows. Explore the interface and the engineering decisions behind it. Source repositories remain private.
Inspect screen ↗Actual local app capture. Fictitious accounts used for UI testing.
Breakers Vault
An operations desk for account inventory and delivery.
Staff need to find the right game, choose an available variant, and keep a clear delivery history. I built the inventory and administration workflows around those tasks.
Arabic digits, game aliases, keyboard-layout corrections, and small spelling errors all feed the same search. The matching logic uses explicit rules and fuzzy comparison.
This is a local UI preview, with no saved credentials shown.
Inspect screen ↗Search in context, with empty email, password, and 2FA fields.
Inspect screen ↗Archived read-only dashboard demo. All amounts and counts are sample data.
Breakers Payment
Turn a transfer notification into an order decision.
A separate gateway connects bank-transfer notifications to store orders by checking the exact amount and reference, then reporting the result to the store.
Integration
Order creation, confirmation-status queries, Telegram receipt parsing, and authenticated callbacks.
Edge cases
Incorrect references, amount mismatches, delayed notifications, used receipts, and orders that need manual review.
Operator experience
Search, review workflows, manual confirmation, fee configuration, and checkout totals.
I built a mobile rewards experience with daily activities, referrals, achievements, balances, and withdrawal history. Iteration included profile navigation, progress displays, and a move to a Vite SPA to address deployment issues.
React · TypeScript · Vite · Tailwind CSS · Telegram Mini Apps
Opens in Telegram. No authenticated app screenshot was available for this portfolio.
The workflow matters
Customer support gives me the problem. Engineering gives me a way to fix the repeated work.
Start with the failure
Wrong references, blocked database migrations, and ambiguous account availability make real work harder. I use those cases to shape the product.
Carry it through
My work spans React interfaces, Python and Node.js services, SQL data models, Telegram integrations, deployment troubleshooting, and operational documentation.
Archived local sign-in screen. The current source also includes staff MFA and session-lifetime controls.
About Basel
Based in
Cairo, Egypt
Studying
Computer Science Cybersecurity, BUE Expected 2027
Languages
Arabic & English
I’m a Computer Science student building practical software alongside customer and technical support work at Breakers Store.
I’m interested in product engineering roles where I can own a workflow from the first customer problem through the interface, backend, deployment, and later improvements.
I also build Telegram-controlled browser automation with Python and Playwright, including session handling, regional inputs, user-provided verification codes, and recovery paths.
Inspect screen ↗
