A request ID helps identify a particular API request. Stripe exposes a request identifier in response headers and recommends providing it when contacting support about that request. It should not be confused with the business reference for the booking being investigated. Source: Stripe API: request IDs

Include it in a useful support record

For an illustrative supplier issue, record the request ID alongside the operation, timestamp, environment and booking reference if one exists. Keeping those fields separate helps the technical team find the relevant exchange without assuming that every reference means the same thing.

Protect the rest of the evidence

Use the approved support route for any logs or response extracts. Redact credentials and unnecessary personal details before sharing them, so an investigation does not create an avoidable disclosure.

Retain the investigation outcome with the case. If the issue returns, that gives the next person both the original trace reference and the decision made at the time.

Where no request ID was returned, record that fact and supply the other available context. Do not invent a reference or substitute an unrelated booking number.

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.