triPOS®

Request ID

Request ID

Every request to triPOS should contain a request ID that uniquely identifies that particular request. This request ID should be:

  1. Sent to triPOS in a header named tp-request-id on the HTTP request
  2. A valid UUID or GUID
  3. Unique for each and every request. triPOS will reject requests with a duplicate request ID.

The tp-request-id header is also returned in all triPOS responses. The triPOS request ID is useful in several scenarios:

  1. The request ID allows an integrator to precisely match each request and response.
  2. When utilizing triPOS’ store and forward capability, the request ID is used to identify the stored transaction that should be forwarded.
  3. In the event of a timeout or communication error, the request ID can be used to verify if triPOS received a request by resending it. triPOS rejects requests with the same request ID.

Legacy Support

To support legacy triPOS integrations, requests without a triPOS request ID (tp-request-id header) will not be rejected. Instead, triPOS will use the Nonce supplied in the tp-authorization header as the tp-request-id if the Nonce is a valid UUID/GUID. If a tp-request-id header is not supplied and the Nonce is also not a UUID/GUID, triPOS will generate a tp-request-id on behalf of the client.