Correlation ID and Client IP
`In the ever-evolving landscape of digital services, ensuring transparency and accuracy in billing and metering processes is paramount. At Signzy, our existing metering stack has been diligently recording usage data with essential meta fields such as Timestamp, GatewayUserId, ProductID, StatusCode, and ResponseTime. This meticulous collection of data underscores our commitment to providing clear and accurate usage metrics to our customers.
However, we recognize that in the complex domain of digital transactions and services, discrepancies can arise. Customers might question the metering numbers due to various reasons, leading to disputes that can affect trust and business relationships. To address this challenge and enhance our billing and metering integrity, we are introducing an additional layer of data reconciliation through the implementation of a new requirement Client Correlation ID (Generated by Client) shared in headers to be stored in our logs, along with the Client IP thats tracked.
Client Correlation ID will be echoed back to the Client as part of the response headers as well for them to also have a track of the requests generated by them.
This allows use to achieve the following:
- TraceabilityIt allows both Signzy and the client to trace every transaction or request back to its origin, providing a clear audit trail.
- Dispute ResolutionIn the event of a discrepancy, the correlation ID can be used to quickly identify and review the specific transaction in question, simplifying and speeding up the resolution process.
- Enhanced TransparencyBy involving clients more directly in the metering process, we foster a greater sense of transparency and partnership. Clients can have a better understanding and trust in the billing process, knowing that they have the tools to verify and reconcile their usage data.
- Improved AccuracyThe additional data point helps in refining our analytics and metering algorithms, leading to more accurate billing and usage metrics.
The client is required to send a unique identifier in x-client-unique-id in the request headers , the same will be sent back in response headers and also stored in our logs along with Client IP
In the event of the absense of x-client-unique-id , x-trace-id which has been part of response headers for both gateways will be stored in logs , always giving us a UUID to reconcile at both our ends.
