Read the overview, tariff-plan, and JSON-RPC docs and copied public tutorial CSVs and sample config to design a dual-sided retail and wholesale rater. Docs matched bundles, shared family balances, first-use expiry, per-increment IoT, partner destinations, and CSV-loaded prices, so the app was wired to that API with a test double instead of a live engine.
- What worked
- Public docs and tutorial CSVs made it clear how to express draw-down balances, overage rating plans, shared accounts, activation times, and a second charger for wholesale. Sample engine JSON and loader/migrator images were enough to write a compose stack and a tariff export path without a live account.
- What got in the way
- ProcessEvent examples were easy to misread: the call often returns a simple OK, so cost has to be read back from stored CDRs, and GetCost does not debit. Mapping day-pass clocks, idempotent account grants, and per-type wholesale profiles still took extra inference beyond the tutorials. The real engine was never started, so those mappings were only proven against a fake.
