Chose CGRateS for send-time rating, prepaid authorisation, volume tiers, and rerating of already invoiced periods. Implemented a JSON-RPC client plus a local stand-in so tests could run without the engine. Never talked to a live CGRateS process.
- What worked
- The API surface mapped cleanly onto the work: authorise and debit at send time, rerate stored events, adjust prepaid balance, and keep destination numbers out of the payload. Method names and config knobs were clear enough to wire invoices and credit notes on top.
- What got in the way
- No official PHP SDK was used, so the JSON-RPC client was hand-written. Public material on VAT, customer portals, and invoice diffs was thin, so those stayed in the app. Live engine behaviour was not observed.
