A PhonePe browser return does not mark an order paid. Tringify obtains the result through the app’s signed status operation and records captured transactions once per provider transaction ID. Store API clients and MCP tools read that platform state; they do not submit PhonePe outcomes or treat navigation as proof of payment.
A verified PhonePe notification can request a check with an empty-body POST to /api/2025-01/payment-sessions/{session_id}/wake or /api/2025-01/payment-refunds/{refund_id}/wake, authenticated as the installed payment app. This is a request to check, not a paid, failed or refunded report. Tringify calls the provider app for the live result. Normal platform checks preserve correctness when notifications do not arrive.
PhonePe cancellation answers the same pending, paid or failed shape as status. Standard Checkout cannot remotely close an order, so cancellation does not prove that a later capture is impossible. Refund requests remain idempotent on refund_id; refund_status reads the provider’s result. Dates use RFC 3339 instants and amounts are exact decimal strings.
For the operation shapes and PhonePe limitations, see PhonePe payment integration. No additional Store API or MCP setting is needed.