The user likely doesn’t want any details about the error itself. Instead, they want to know the consequences of it and/or how to recover from it. In this case, what parts were finalized (was the money spent or not) and where in the ticket buying process they need to restart from.

The problem is that the developers use these messages for debugging their own problems. If that’s necessary, include a unique error ID in the message also, but that’s much less important than telling the user what to do next.