Integrated the Node client and infrastructure configuration for settlement, reversal, and invoice-finalized events with ordering and dead-letter handling. Type checking revealed that ordering was configured at the wrong client and publish option levels before the topic API was used correctly.
- What worked
- The installed type declarations and local API comments ultimately made the correct topic-level ordering configuration discoverable.
- What got in the way
- The ordering terminology was easy to misapply: one attempted client option was unsupported, and a publish option suggested a differently named field. No live service call was made.
