Gateway Emulation
To help our clients get integrated quickly, OpenPath has implemented proprietary Gateway Emulation. This means that our system’s frontend accepts API requests as if OpenPath were one of the several most popular Payment Gateway System on the market. Currently OpenPath supports:
If your Point of Sales system is currently integrated into one of these Payment Gateways, integrating to OpenPath is as easy as changing your Payment Gateway URL to point to OpenPath instead of your Payment Gateway and OpenPath will manage your transactions from there.
- NMI
If your Point of Sales system is currently integrated into one of these Payment Gateways, integrating to OpenPath is as easy as changing your Payment Gateway URL to point to OpenPath instead of your Payment Gateway and OpenPath will manage your transactions from there.
How it Works
- Your Point of Sale sends a transaction to the OpenPath API URL as if it were one of the supported Gateways.
- OpenPath takes that transaction call and converts it to an OpenPath Global Transaction Object (GTO) which normalizes the data.
- OpenPath business logic chooses which Gateway the transaction should be sent to and converts the GTO to a supported API call to that particular Gateway.
- OpenPath receives the response from the Gateway and updates the GTO.
- OpenPath converts the GTO back to a response that is the equivalent of the originating Gateway Emulation call back to your Point of Sale.
Required Field Considerations
When integrating a single Gateway on the front-end and several different Gateways on the back-end, OpenPath will reliably convert the data from one format to another. However, there are occasions when the front end gateway emulation you chose may have less required fields then back-end gateways, so you should take into consideration when determining what data you want to send from your Point of Sale to OpenPath.
In scenarios where this occurs, if you have return OpenPath responses enabled, then you will receive a message about the missing required fields. Otherwise, it will be returned in the Client Application Reports.
The OpenPath responses are enabled at the Site level and allow additional fields to be sent (and returned) above those allowed by the original gateway protocol.
In scenarios where this occurs, if you have return OpenPath responses enabled, then you will receive a message about the missing required fields. Otherwise, it will be returned in the Client Application Reports.
The OpenPath responses are enabled at the Site level and allow additional fields to be sent (and returned) above those allowed by the original gateway protocol.
