Chose CGRateS for versioned tariffs, bundle drawdown, shared balances, first-use day-pass expiry, derived wholesale charges, and rerating. Read the overview docs, searched for ProcessEvent and Docker setup, then wrote a JSON-RPC client, tariff loader, engine config, and compose sidecar. Never ran the live engine; a local stand-in applied the same catalog so tests could pass.
- What worked
- The charging model mapped cleanly onto retail plus wholesale runs, activation-timed rates, account balances, and restatement instead of deleting rated usage. Documentation and examples were enough to design the catalog and event mapping without treating prices as source code.
- What got in the way
- The JSON-RPC path for charging an event, reading CDR runs, and diffing account balances was messy, so that logic stayed confusing. A full instance was assumed not to run in the local test loop, which forced a parallel in-process engine and left live reliability unproven.
