The PhonePe app verifies the configured webhook credentials or account Salt Key before sending an empty-body wake for the attempt or refund named by the notification. It does not pass the notification’s payment outcome to Tringify. Tringify reads PhonePe live through status or refund_status and records the result before downstream platform events describe it.
A lost notification may delay an immediate check, but platform checks still obtain the outcome. Repeated or late notifications ask for the same live read and cannot create another captured payment or refund. Applications consuming Tringify payment events should read the corresponding platform state and deduplicate deliveries using the normal webhook delivery contract.
See PhonePe integration for supported provider events, account changes, cancellation limits and live result handling.