Defined a gRPC API for contracts, running totals, and invoices, and added refund and chargeback RPCs on the payments service. The Node gRPC and proto-loader stack matched the rest of the workspace. Field naming, integer width defaults, and error codes had to be reasoned through from existing services rather than a live call.
- What worked
- Existing proto-plus-Nest microservice wiring was enough to add a new service definition and extra RPCs without introducing a second RPC stack.
- What got in the way
- int64 fields defaulting to zero made optional fee amounts easy to mishandle, and transport mapping for not-found versus invalid-argument was assumed from framework behavior, not observed.