PAYMENT STATUS RECOVERYUPI UNCERTAINTY ENGINE

Financial Clearinghouse Prototype • Multi-Party Telemetry

← Back to Transactions
SYNTH-TX-108P2P (Personal)Debited • Timeout HoldDO NOT RETRY

Priya Verma (P2P) [SYNTHETIC]

VPA: priya.v@icici • Bank UTR: 908234120918

Initiated: 01 Oct 2026, 01:10 pm•Elapsed: 49 mins ago•Routing: HDFC Bank → ICICI Bank
Transaction Amount₹4,000
Debited from HDFC Bank

Deterministic Recovery Guidance

Strict Directive: DO NOT RETRYRule: RULE_06_UNRESOLVED_DEBIT_TIMEOUT

Settlement Window Exceeded - Formal Action Required

Money was debited but unacknowledged. DO NOT RETRY. Eligible for auto-reversal.

What We Know

  • ₹4,000 debited from HDFC Bank.
  • Transaction UTR: 908234120918
  • More than 49 minutes have elapsed since payment initiation.

What Remains Uncertain

  • Beneficiary confirmation was not received within the app cooling-off window.

Recommended Next Step

File Bank Dispute / Auto-Reversal Claim

The in-flight window has closed without positive credit confirmation. Under RBI guidelines, your bank must reverse the funds or provide confirmation.

Alternative Escalation: Query the switch one more time for delayed settlement flags.
App Cooling-Off Window (Product Design Threshold) (15 minutes): Client-side synchronization window allowing banking networks to reconcile before prompting dispute escalation. This is a product UX decision and NOT an RBI regulatory requirement.

Applicable Statutory Regulatory Mandate

RBI Circular
RBI Harmonisation of Turn Around Time (TAT) and Customer Compensation (RBI/2019-20/67 DPSS.CO.PD No.629/02.01.014/2019-20)
Applicable Clause:Table 5(a) - UPI Person to Person (P2P): Debited but beneficiary not credited
Mandated Auto-Reversal TAT:T + 1 Business Day (Auto-reversal by remitter bank)
Delay Compensation Policy:₹100 per calendar day of delay beyond T + 1 day
Important Distinction: Statutory TAT is an official regulatory banking deadline and does not promise immediate instantaneous refund. It is separate from the app’s 15-minute UX cooldown.

Multi-Party Telemetry Breakdown

4-Party Clearing Rails
1
Debited

Remitter Bank (Payer)

HDFC Bank

Issuing bank holding user account

Confirmed funds deduction of ₹4,000 from customer account.

remitterDebit = DEBITED
2
Network Timeout

NPCI UPI Switch

NPCI Central Network

National payment switch & router

Switch session timed out during transit. Packet state is non-terminal / unresolved.

npciSwitch = TIMEOUT
3
Credit Pending / Unknown

Beneficiary Bank

ICICI Bank

Receiving bank holding payee account

Payee bank has not yet posted credit confirmation to the central switch.

beneficiaryCredit = UNKNOWN
4
N/A (P2P Transfer)

Merchant POS / Soundbox

Not Applicable

Individual recipient

Person-to-person transfer; no merchant point-of-sale integration involved.

merchantOrder = NOT_APPLICABLE
* Multi-party signals modeled after UPI ISO 8583 / XML clearing protocol. 100% simulated synthetic telemetry.

Chronological Event Log

Multi-Party Event Timeline

Chronological sequence of synthetic network events and deterministic evaluation steps.

Recorded EventInferred State
Payment Request InitiatedSynthetic Event
01 Oct 2026, 01:10 pm
Source: UPI Client App (Synthetic)

Initiated transfer of ₹4,000 to Priya Verma (P2P) [SYNTHETIC]. Assigned UPI UTR 908234120918.

Type: P2P
Remitter Debit ConfirmedSynthetic Event
Source: HDFC Bank

Account debited ₹4,000 by HDFC Bank. Debit authorization logged.

remitterDebit: DEBITED
Switch Network Timeout ObservedSynthetic Event
Source: NPCI UPI Central Switch

Network switch session timed out without a definitive terminal packet. In-flight reconciliation active (49 mins elapsed).

npciSwitch: TIMEOUT
Beneficiary Credit Pending / UnconfirmedInferred Observation
Source: ICICI Bank

Final credit settlement has not yet been acknowledged by ICICI Bank.

beneficiaryCredit: UNKNOWN
Recovery Engine: UNRESOLVED_DEBIT_TIMEOUTSynthetic Event
Source: Payment Status Recovery Engine

Settlement Window Exceeded - Formal Action Required

Rule: RULE_06_UNRESOLVED_DEBIT_TIMEOUT | safeToRetry: false