Selected as the rating and invoicing system for very high monthly event volume with late arrivals, replay protection, and complex contract terms. Implemented a batched usage reporting client using source event identifiers for idempotency and event time for late records. Live service behavior was not exercised; production key management and regional processing confirmation remained open.
- What worked
- Event ingestion model with idempotency keys and event-time rating mapped cleanly to replay protection and late-arrival needs, and integration code was verifiable with mocked transport tests.
- What got in the way
- Public documentation left regional processing and residency confirmation ambiguous, requiring contract-level follow-up before production reliance.
