This experience with the payment gateway integrations also made me a go-to person in the company, and I became known as the “Gateway Guy” of the team. 😅 So, I’m also frequently the person responsible for fixing bugs or implementing new features in consolidated integrations like PayPal and Stripe that are the default payment gateways present in the Give core – check out my PayPal contributions and Stripe contributions directly on GitHub.

All this know-how with payment gateway integrations made me recognize some code duplication across multiple projects. We were duplicating similar logic to handle webhook notifications sent by the payment gateways across multiple add-ons. I solved this problem by improving the GiveWP gateway API with a new gateway webhook events API that I envisioned and implemented.

GiveWP Campaigns is another project that I’m particularly proud of co-leading, from the architectural design to development. This project involved creating a new, centralized system for managing fundraising efforts, moving beyond individual donation forms. 

My role on this project was multifaceted. I was a core co-author of the main epic branch, responsible for significant parts of the migration of forms to campaigns, backend architecture, and the foundational UI for admin screens – this included building the base components (title, breadcrumbs, header, tabs, update button, react-hook-form implementarion, etc.), which became the standard for other admin interfaces like donors, donations, and subscriptions later. I also developed key features like the Option-Based Form Editor feature flag, the campaign creation UI, and the campaigns merge functionality (methods, endpoint, and UI).

Beyond that, recently, I was directly involved with the architectural discussions, decisions, and implementation of the REST API V3 routes/endpoints to interact with donations, donors, subscriptions, and other resources. So I started to become the “REST API guy” of the team as well. 😅