No merchant order exists for this payment.
Chronological facts from Razorpay and merchant sources.
Razorpay webhook received with payment state captured.
EV-TWO-ORDERS-WEBHOOK
{
"event_id": "evt_two_orders_001",
"event_type": "payment.captured",
"payment_id": "pay_two_orders_001",
"payment_state": "captured",
"amount_minor": 3000,
"currency": "INR",
"idempotency_key": "two-orders-001",
"signature_verified": true,
"operation": "capture"
}Merchant order state observed as missing.
EV-TWO-ORDERS-A
{
"payment_id": "pay_two_orders_001",
"order_id": "order_two_orders_a",
"order_state": "missing",
"amount_minor": 3000,
"currency": "INR",
"operation": "capture",
"idempotency_key": "two-orders-001"
}Merchant order state observed as missing.
EV-TWO-ORDERS-B
{
"payment_id": "pay_two_orders_001",
"order_id": "order_two_orders_b",
"order_state": "missing",
"amount_minor": 3000,
"currency": "INR",
"operation": "capture",
"idempotency_key": "two-orders-001"
}What the evidence shows happened, and the mismatch diagnosed from it.
No merchant order exists for this payment.
One Razorpay payment is linked to two merchant orders.
Missing or conflicting evidence
What the model concluded from the evidence. It advises; the policy decides.
The evidence shows two distinct order IDs (order two orders a and order two orders b) both claiming the same payment with a 'missing' state. To resolve the 'one payment two orders' exception, we must determine the true merchant-side linkage. fetch merchant order is the tool designated to establish durable merchant order state and identity.
Uncertainty
It is unclear if one of the order IDs is a stale artifact or if the merchant system has a data integrity bug creating duplicate links.
The durable merchant order state and identity for the captured payment.
What to check nextfetch merchant order
The authoritative merchant order record associated with payment pay two orders 001, confirming which order (if any) is validly linked.
Decision needed
No discretionary financial decision is requested.
Stops when
Verified closure when the merchant order state confirms a single valid order linkage or explicit escalation if the merchant data is corrupted beyond read-only resolution.
The provider captured a single payment, but the merchant system failed to link it to a specific order, resulting in two conflicting 'missing' order states.
The evidence shows two distinct order IDs (order two orders a and order two orders b) both claiming the same payment with a 'missing' state. To resolve the 'one payment two orders' exception, we must determine the true merchant-side linkage. fetch merchant order is the tool designated to establish durable merchant order state and identity.
Whether policy authorizes a merchant-side repair.
Payment/order mapping is not unique
Verification runs after an approved repair. This exception was escalated without one.
| Check | Razorpay observation | Merchant observation | Result |
|---|---|---|---|
| State | Captured (verified) | multiple | Does not hold |
| Amount | ₹30.00 | ₹30.00 | Holds |
| Identity | Razorpay payment linked | 2 orders | Holds |
Razorpay: Captured (verified)
Merchant: multiple
Razorpay: ₹30.00
Merchant: ₹30.00
Razorpay: Razorpay payment linked
Merchant: 2 orders
No repair was applied, so no verification checks were recorded.