Void
The Openpath NMI Emulation API supports POST requests in various formats, including query strings and form data. It allows for void transactions, with specific parameters and required fields for processing.
POST
POST URL:
[https://api.openpath.io/v1/nmi](https://api.openpath.io/api/transact.php)
The OpenPath NMI Emulation API can receive transactions posted in the following formats:
| Format | Description |
|---|---|
| Query String (Not Recommended) | A query string is part of a URL that assigns values to specified parameters. It is commonly used for HTML or multimedia content navigation. |
| Form Data | The FormData interface allows constructing key/value pairs representing form fields and values, sent using the XMLHttpRequest.send() method, in the multipart/form-data encoding. |
| X-WWW Form URL Encoded (Recommended) | application/x-www-form-urlencoded is the default encoding used by web forms. It must be specified explicitly for multipart/form-data submissions. |
Void (void)
void)Transaction voids cancel an existing sale or captured authorization. Non-captured authorizations can also be voided to prevent future capture. Voids are only allowed for unsettled transactions.
Request Parameters
| Variable Name | Description |
|---|---|
type* | Type of transaction. Value: void |
username* | Site Username (API Login ID) assigned to the merchant account. |
password* | Site Password (Transaction Key) assigned to the merchant account. |
transactionid* | Original payment gateway transaction ID. |
void_reason** | Reason for voiding the EMV transaction. Values: fraud, user_cancel, icc_rejected, icc_card_removed, icc_no_confirmation, pos_timeout |
payment*** | Type of payment. Default: creditcard Values: creditcard, check |
*Required fields
**Conditionally required for EMV transactions
***Required for ACH transactions
Updated 10 days ago
What’s Next