A quick overview of the issue:
We have a webserver that talks to a payment processor. This server goes directly outbound (no proxy) and starts a transaction. We send them the data, they receive the data successfully, they send the response to let us know they received it, and our webserver does not receive the reply. After staying connected waiting for the reply, their end terminates the connection after 120 seconds.
This causes our system to think that the transaction was unsuccessful and re-try the payment, causing unfortunate things like double transactions because our end has no record of it being successful.
I have run packet caps with wireshark and at the end of the frame I can see the connection reset from the remote side, but nothing else indicating the where the issue lies. Of course everything is encrypted so the captured traffic isn't super helpful either. This connection issue is sporadic, as most transactions are successful.
This is one of my few times having to troubleshoot something like this, is there something specific I should be looking for in the captures that would indicate some sort of mismatch or compatibility issue with TLS?
No comments:
Post a Comment