The integration bug hiding behind a valid algorithm
One of the easiest ways to break a signed integration is to let two services mean different things by “the signature.”
In a B2B fraud-detection platform I worked on, HMAC request signing connected a Laravel application, its SDKs and an ML service. A signature-format mismatch nearly shipped. That is the engineering lesson I want to share, without exposing the employer, its code or its internal API contract.
The question I now ask during review is simple: can two independent implementations produce exactly the same authenticated message and the same transmitted signature representation?
Saying “we both use HMAC” does not answer that question. The algorithm is one part of the agreement. The message bytes, key handling and representation also need an explicit contract.
The examples and review process below are general guidance.…