Surface areaReliability firstMulti product
Core surface areas (quick map)
Think of Razorpay as three connected surfaces: checkout completion, money movement, and reporting. The most important thing is where failures show up and how teams recover.
Accept
ConversionCheckout orchestration across cards, UPI, netbanking, wallets.
Move
ReliabilityPayouts, refunds, settlements, dispute flows.
Reconcile
OpsLedger views, settlement reporting, ops workflows.
- More rails means more edge cases and integration variance
- Onboarding is product plus compliance, not just a form
- Trust is driven by success rate, latency, and clarity
Context lens
Before AI, map the surface area and the failure modes. Safe automation starts there.
