Incident Learning Hub
Enablement Command Center
Back to course: Commerce

Commerce | Reading Module

Runbook: Payment Decline Rate

Status: Not Started | Pass threshold: 100% | Points: 75

L3 25 min triage

Best score

0%

Attempts

0

Pass rate

0%

Passed

0

Completion happens in the checkpoint panel below.

Module Navigator

Previous

Runbook: Otp Failure Spike

Reading Module

Review Prior Module ←

Recommended Next

Commerce Service Topology

Reading Module

Resume Recommended Path →

Next

Commerce Core Signal Pattern Check

Skill Check Quiz

Continue To Next Module →

Learning Guidance

Objectives

  • confirm decline spike across last 30 minutes
  • group by processor and organization
  • classify decline reasons into vendor vs normal card declines
  • vendor outage vs normal decline mix
  • single store gift card activation issue vs broad outage

Evidence To Capture

  • processor distribution
  • decline reason distribution
  • vendor status evidence

Source Artifacts

Internal source references are available for maintainers but are not exposed in deployed environments.

Field Evidence

Real incidents related to what you're learning.

01KJ1EGNR2JP3C9SJNYFA32X3Q

2/22/2026 | n/a

medium

PH US Pick Up Order Flow 2 synthetic test failed on Pizza Hut website

This browser synthetic test is basic. It tests for basic user functionality on Pizza Hut's website and refreshes orders on Customer Support with default filt...

commerce Same product lane: commerceKeywords: monitor, status, orderRoot cause (deployment) aligns with L3 focus

Study Incident →

01KHY4SW3BRJ4FYA0V71XMWDJ6

2/20/2026 | n/a

medium

Browser synthetic test failure on PH US Pick Up Order Flow 4 - Wings Menu

This browser synthetic test is basic. It tests for basic user functionality on Pizza Hut's website and refreshes orders on Customer Support with default filt...

commerce Same product lane: commerceKeywords: monitor, status, orderRoot cause (deployment) aligns with L3 focus

Study Incident →

01KJ16GB3W1G8HNZWM57BY87QX

2/21/2026 | n/a

medium

Customer login flow failure on PH US Pick Up Order for Ultimate Hut Bundle

This browser synthetic test is basic. It tests for basic user functionality on Pizza Hut's website and refreshes orders on Customer Support with default filt...

commerce Same product lane: commerceKeywords: monitor, status, orderRoot cause (deployment) aligns with L3 focus

Study Incident →

Module Content

Not Started

Key Takeaways

  • Monitor 251308017 or 163999810 fires.
  • Confirm spike in alert window:
  • Group by processor and organization:
  • Group by decline reason and classify:
  • Vendor indicators: "Unable to process your request", "System Error", timeout patterns.

Trigger

  • Monitor 251308017 or 163999810 fires.

Triage Steps

  1. Confirm spike in alert window:
service:payment-dgs @event.action:payments_post_auth @metadata.status:DECLINED env:prod*
  1. Group by processor and organization:
SELECT "@metadata.processor_source", "@organization", count(*) FROM logs
WHERE service = 'payment-dgs' AND "@metadata.status" = 'DECLINED'
GROUP BY "@metadata.processor_source", "@organization"
ORDER BY count(*) DESC
  1. Group by decline reason and classify:
  • Vendor indicators: "Unable to process your request", "System Error", timeout patterns.
  • Normal declines: insufficient funds, invalid card, do not honor.
  1. Check vendor status:
  • Fiserv: https://fiserv3.statuspage.io/
  • Cybersource: https://status.cybersource.com/

Decision Points

  • Vendor-specific decline surge across brands: escalate as vendor outage pattern.
  • Gift card declines concentrated on one store: likely store activation issue.
  • Broad payment errors + infra signals: involve SRE for dependency checks.

Escalation

  • Payments on-call (incident.io) for sustained checkout impact.
  • KFC gift card activation path: KFC_DCI@yum.com.
  • TB gift card activation path: TB L3 ecommerce channel.

Recovery Validation

  • Decline rate back to baseline.
  • Confirmed order rate no longer suppressed.
  • Incident summary includes vendor status and timeline.

Reading Checkpoint

Current score: 0%

Sections complete

0/0

Checkpoint confirmed

Not yet

Reflection

0 chars

Completion requires 80% section coverage, checkpoint confirmation, and a short reflection. On completion, you will move to the next module automatically.

Add 40 more characters.

Mark at least 80% of sections complete.