Payments — Hyperswitch + Gateways
Decision: self-hosted Hyperswitch as the payment orchestration layer in front of Indian gateways — Razorpay, CCAvenue, Cashfree (notes). Medusa talks to Hyperswitch via a custom payment provider.
Chargebacks — evidence agent and Razorpay filing
When a customer disputes a payment with their bank, the dispute appears in the staff console under
Courier — Shiprocket
Decision: Shiprocket as the first courier partner (notes #6), integrated as a Medusa fulfillment provider. Shiprocket itself aggregates many Indian carriers (Delhivery, Blue Dart, DTDC, …), so one integration yields multi-courier rate-shopping.
Marketplaces — Amazon & Flipkart
Decision: Amazon and Flipkart are sales channels (notes #1) synced via custom connectors — there is no off-the-shelf Medusa plugin for Amazon SP-API or the Flipkart Seller API. Each is a NestJS connector service mapped to a Medusa sales channel.
Notifications (SMS / WhatsApp / Email / Push)
A central, event-driven Notifications service: one place that turns domain events into messages across channels, with templates, localization, and tenant-configurable providers.
Newsletter — Listmonk (vs Ghost)
Decision (answers notes #7 "ghostjs or custom?"): use self-hosted Listmonk for bulk newsletters, with content authored in Payload (CMS). Ghost is not adopted.
AI — Semantic Search & RAG Assistant
Two AI surfaces, built on a shared embeddings + vector-store foundation in the
Automation — n8n, Zapier & Pabbly
Feature (notes #13): let the business wire automations by connecting platform events to automation engines. The platform exposes selected domain events as signed outbound webhooks; the engine does the rest (Slack, Sheets, CRMs, WhatsApp, thousands of apps).