Flipkart Marketplace Platform · View 09 of 25 · 3 · Structure
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