Imported the client library and added topics, subscriptions, retries, and a dead-letter queue so settlement and reversal events can leave the ledger without card data. Configuration followed an existing sibling closely; dead-letter publish rights were left as a known gap and the topics were never exercised live.
- What worked
- Retry plus dead-letter settings and a non-card payload were easy to express in both the consumer and the infrastructure config, which fit an event-driven rating path.
- What got in the way
- Publisher access on the dead-letter topic still looked incomplete, matching a gap already present for the sibling consumer, and nothing was published against a real project.
