Flipkart Marketplace Platform  ·  View 09 of 25  ·  3 · Structure

Integration Catalogue

Every way this platform touches another system, in both directions, with who owns the contract.

Editable source SVG draw.io All views
Inbound consumers Customer apps Seller portal and app Brand bulk feeds ONDC buyer apps Affiliate and ads Care and ops consoles Platform interfaces API Management OAuth2 · quotas Customer BFF Envoy Gateway Event backbone 38 topics · webhooks Outbound dependencies Payment rails UPI, cards, wallets Nodal bank payouts KYC and GST 3PL carriers REST REST bulk Beckn REST REST REST NACH REST scans Integration Architecture — Every Interface, Both Directions Application we own External / third party Interface / broker Queue / topic synchronous batch event / async SMS, WhatsApp and push providers are omitted here and drawn on the notification path. We own every contract except NPCI, the acquirer webhooks and the NACH file format. Each third-party call sits behind a circuit breaker with a stated fallback. v 1.0 · owner Integration Architecture · date 2026-09

Decisions

  • Two front doors on purpose: an Envoy BFF for first-party apps, API Management for anyone we bill, throttle or version
  • Partner-facing events leave as signed, replayable webhooks off the same topics the platform consumes internally
  • Every outbound dependency sits behind a circuit breaker with a written fallback — routing to another acquirer, queueing, or degrading a feature

Contracts we do not own

  • NPCI UPI specifications and their change windows
  • Acquirer webhook payloads, which are unordered and can be delivered twice
  • The NACH settlement file format and the bank cut-off time

Deliberately omitted

  • SMS, WhatsApp and push providers — drawn on the notification path instead
  • Internal service-to-service calls, which are the container view's job
  • Two accepted clutter warnings on this page: two outbound labels sit close together and were kept because dropping an interface would misrepresent the estate