Commerce integrations
The integration layer between eCommerce platforms and every payment gateway, carrier, delivery app and marketing platform a regional merchant actually uses — plus the SDKs that made them consumable.
- Role
- Full-stack, then tech lead — Conexa
- Period
- 2021 — 2023
- Type
- Client work
- Status
- production
Overview
Integration work is where software meets other people’s decisions. Every provider has its own idea of what a webhook is, when to retry, and what a failure looks like — and none of it matches the documentation once real orders are flowing.
The surface was regional and wide: payment methods and shipping providers across Argentina, Mexico and the rest of Latin America, delivery platforms like PedidosYa and Rappi, carriers like Andreani, and marketing platforms on both sides of the hemisphere — Sendinblue and Klaviyo among them.
I built and maintained that layer, then wrapped it in internal SDKs so the rest of the company stopped rewriting the same auth, retry and webhook handling on every project. As tech lead, those SDKs and boilerplates became the team’s shared foundation.
Modules
Payments
Payment gateways across Argentina, Mexico and the wider region, each with its own capture, refund and webhook semantics.
Shipping & delivery
Carriers such as Andreani and delivery platforms such as PedidosYa and Rappi, wired into order fulfilment.
Marketing platforms
Regional and US marketing tools — Sendinblue, Klaviyo and others — fed with customer and order events.
Internal SDKs
The wrappers that turned all of the above into something the rest of the company could call without relearning each provider’s quirks.
Stack
- 01TypeScript
- 02NestJS
- 03Express
- 04MongoDB
- 05REST
- 06Webhooks