Payment Core handover

Needs review

Webhook retries have conflicting delivery records

PR #204 says SQS FIFO. Slack records RabbitMQ as the active retry fallback.

Claims94 verified

Open conflicts11 routing conflict needs review

Unfinished22 successor actions

Ownership22 assets to transfer

Claim evidence

Successor sign-off

Architecture decisionsPending

Unfinished workPending

OwnershipPending

Routing conflictPending

0 of 4 sections accepted

Routing conflict

AWS SQS FIFO Queue (fintrack-settlement-fifo.fifo)GitHub PR #204: AWS SQS MigrationAlex Chen (Staff Engineer) · Oct 14, 2026

All batch settlement events now stream through `fintrack-settlement-fifo.fifo` with exactly-once delivery guarantees. Deprecates the legacy RabbitMQ cluster on ECS.

RabbitMQ Cluster (Active Fallback for Retries)Slack #payment-eng Throttling RollbackAlex Chen · Nov 2, 2026

Temporarily routed webhook retries back to our RabbitMQ cluster while AWS support investigates the burst quota. RabbitMQ is currently handling live delivery fallback.

claim_09

Decisions

ADR-004: Migrate Payment Event Queue Worker to Postgres SKIP LOCKEDRationale documented · Aug 14, 2026 · claim_01

Ownership

Stripe Webhook Gateway & Secret CustodyAlex Chen → Priya SharmaTransfer by Nov 10, 2026 · escalate to Vikram Malhotra

Unfinished work

PR #214: Exponential backoff with jitter for webhook retriesCI test failure: AssertionError in test_retry_jitter_bounds on line 84 (random seed collision).Immediate · claim_05

Leaver interview

In commit 8f4a1 on Oct 4, you extended JWT auth token TTL from 15m to 72h with the comment '// quick fix'. No Jira ticket was linked. Why was this extended, and is it safe to revert?Claim claim_03 · Pending answer

0 of 4 handover sections accepted