Shipping dispute management in two weeks
Merchant and operations flows for card disputes, from the first notice to the final decision: evidence upload, due dates, bulk actions and maker-checker approvals, plus the notification emails.
I'm Arjun. For the last two years I've built payment checkouts, merchant dashboards and design systems at PayGlocal, a cross-border payments company, using React, Next.js and TypeScript. Press I to see how this page is put together.
Merchant and operations flows for card disputes, from the first notice to the final decision: evidence upload, due dates, bulk actions and maker-checker approvals, plus the notification emails.
Auth, app shell, typed API layer and deployment for a merchant dashboard rewrite and a new operations console, then porting a legacy tool screen by screen while both ran side by side.
Data table, filter chips, date and time pickers, and elevation tokens across ~35 components in a public React library, with tests and most of its releases.
Bundle analysis, dependency removal and loading fixes on a hosted checkout, and one deleted build step that took CI from 12 minutes to just over 3.
A chat overlay for Next.js apps that drives a coding agent, with secret-file blocking, a tool allowlist, PR-only publishing and a build check that keeps it out of production.
Full case studies are on the way.