Pratyusha’s approach
First, identify the actual deficit. If the API was expected at T-10 before launch and is now 2 weeks late, what is the new T-X? Compare this with Y — the days our team needs for integration, testing, and release including buffer.
If T-X > Y (low/no impact): Set up a daily tracker with the vendor to ensure no further delays. Unblock internal teams using API contracts, share expected output formats and keys so our teams can continue work assuming the expected responses. Reprioritise requirements so primary usecases get delivered first, edge cases later. Loop in leadership, finance, and legal/ops teams as they may be able to exert more pressure on the vendor than product can, since they own the contract relationship.
If T-X ≤ Y (high impact):
Leverage contract T&Cs. if the vendor committed to delivery dates, highlight this to speed things up. Even without formal terms, a commitment is a commitment. Loop in legal/procurement to apply pressure formally.
Push for partial, phased delivery: primary usecase + top 3 payment failure scenarios first, edge cases later. Keep stakeholders updated on action plan and risk factor.
If even partial delivery impacts launch, evaluate existing payment gateways. Are issues technical? Work with existing vendors to resolve. Are issues around user adoption? Explore options like COD with a small cancellation charge for returns, or discount incentives for using existing gateways. Identify the root issue first, then decide path forward. Keep stakeholders looped in on plan of action, expected sales impact, and timelines throughout.