Header Response
Besides the response body which is a standard NMI response, OpenPath will also include our internal payment packet ID, the server which executed the transaction, the OpenPath Payment Provider/Gateway "Connector" ID and the name of that connector in the following format:
X-OpenPath-PacketId | The internal OpenPath Transaction Packet ID, which will also match up with the OpenPath webhook Packet ID. |
X-OpenPath-Server | The OpenPath server which processed the request. |
X-OpenPath-GatewayId | The Connector ID in the OpenPath system that processed the transaction. |
X-OpenPath-GatewayName | The merchant assigned name of the Connector that processed the transaction. |
Body Response
Example
response=1&responsetext=100 | Transaction approved&authcode=8H32Z&transactionid=30201092293&avsresponse=X&cvvresponse=M&orderid=1000&response_code=100
Standard Response
| Variable Name | Description |
|---|---|
| response | 1 = Transaction Approved |
| responsetext* | Textual response |
| authcode | Transaction authorization code. |
| transactionid | Payment gateway transaction id. |
| avsresponse | AVS response code. See: AVS Response Codes |
| cvvresponse | CVV response code. See: CVV Response Codes |
| orderid | Original order id passed in the transaction request. |
| response_code | Numeric mapping of processor responses. See: Transaction Result Codes |
*responsetext - the response text will contain both the original processors response code and the processors response text seperated by the pipe "|" symbol.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article