Responses
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:
| Key | Description |
|---|---|
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&customer_vault_id=payment_JxnwaadMn3h3H2237pHCz3hePh3EKrg39FXk3K24F2HHK7z4
| Attribute | Description |
|---|---|
response | 1 = Transaction Approved 2 = Transaction Declined 3 = Error in transaction data or system error 4 = Rejected |
responsetext* | Textual response. |
authcode | Transaction authorization code. |
transactionid | Payment gateway Transaction ID. |
avsresponse | AVS response code. |
cvvresponse | CVV response code. |
orderid | Original order id passed in the transaction request. |
response_code | Numeric mapping of processor responses. |
customer_vault_id | Consumer Credit Card Vault ID |
*responsetext - the response text will contain both the original processors response code and the processors response text separated by the pipe "|" symbol.
Updated over 1 year ago
Did this page help you?