NAB OPI Pay Web Service and RES 3700 Driver
North American Bancard's OPI Pay Web Service and Micros RES 3700 Credit Authorization driver were built to enhance the credit card authorization process and serve merchants using numerous POS software and terminal combinations.
The OPI Pay web service API can be utilized independently, but is also included as a standard component of the RES driver package. When these two products are combined, you'll get many benefits of the API without using any of Oracle’s services — meaning your business gains robust performance and processing capabilities at no additional cost. What's more, because our custom-built driver makes use of the API, OPI Pay's performance is constantly being validated internally.
For additional specifications, please refer to our Partner Payment Validation Report.
How your business benefits:
Inclusive Software Support
The OPI Pay API can be leveraged in two distinct ways. It supports the use of Oracle Payment Interface (OPI) specifications, which allow the API to communicate with OPI XML requests.
It can also support the use of a standard Swagger Consumable Interface, which allows the API to communicate with modern REST requests generated by third-party POS systems via XML or JSON. Simply going to the Swagger endpoint started by the web service allows developers to begin processing CAEDC within hours.
For merchants with third-party POS software who wish to use the API but need help getting started, our development team offers the necessary support to get setup so you can begin processing quickly.
Inclusive Hardware Support
The OPI Pay web service allows our development team to quickly and easily add support for most terminal lines. With a terminal market that’s constantly evolving, you will never need to worry that your devices will become obsolete. Merchants who choose the driver will retain the value of their hardware investment, while optimizing its performance potential.
With OPI Pay or the RES 3700 driver, cardholder data typically only needs to be accessed one time. When the terminal initially reads the credit card information, a transaction token is created and used throughout the rest of the payment process. Any subsequent parts of the transaction are handled directly with EPX using the token. This means terminals will not access cardholder data again unless a new token is required, for example, if a different card will be used for payment or if a new check is started. Because sensitive data is never passed back to the POS system, merchants can receive a PCI scope reduction.
Subsequent transaction data can be passed directly to EPX at any time prior to batch settlement. We've created a direct line of communication between the API and the EPX processor, which allows as many data transfers to take place as needed. This means tips can be added and authorizations can be captured without the card being swiped a second time. To start a tab, simply swipe the card to authorize and return it to the customer. When it’s time to finish the transaction, the customer can add a tip and the tab can be closed without swiping the card again.
The driver is completely integrated with the native Micros RES 3700 system. It was designed using Micros RES 3700 specifications, meaning the driver and POS system work in unison. The payment processing advantages that the driver offers are typically only available through the use of external, add-on products which increase the potential for slow-downs and technical issues. Using a driver built for the Micros RES system grants businesses crucial speed and workflow efficiencies with no need to manage third-party products.
Popular, Classic Design
The driver’s integration with Micros RES 3700 will please those who liked classic RES Crystal Reports, the standard RES CAEDC back-end, and OPS workflow, as it was built based on those methodologies.
Cutting-edge Technology without RES 3700 Upgrade
Merchants using RES 3700 version 5.2 MR1 and above will benefit from all of these enhancements, as well as an extended POS lifetime, thanks to the driver’s ability to work with existing RES systems. You won’t need to buy a newer version of RES 3700 software to gain the advantages of this cutting-edge technology. Whether concepts like drivers and web services are familiar or not, don’t worry — the only changes merchants will see are a few updated buttons on the POS touch screen that allow them to utilize the driver’s special features, all of which are explained in the end-user documentation.