EPX Level II & III API
EPX Level II and Level III transactions pass along qualifying transactional information during payment processing. Level II and Level III data allows merchants to supply corporate customers information about the transaction. EPX supports Level II and Level III transactions via batching and real-time transactions (Server POST and Browser POST).
How your business benefits:
Merchants who submit enhanced data fields typically experience lower interchange rates on those transactions, thus lowering the processing costs if the requirements for enhanced data are met. The extra data also allows merchants to pass valuable information to their customers like item information, purchase order number, and other transaction specific details.
How it works:
The enhanced fields must be included with sale or capture only transaction type. Most fields and values can be submitted using any of the EPX transactional products (Server POST, Browser POST, XML Batch, our Semi-integrated solution, etc). One line item Level III fields can be submitted via Server POST and multiple line item Level III can be submitted via XML Batch.
Level II transaction data includes tax-exempt status and the taxable amount of the transaction. Level III data includes other transactional data such as shipping and item information from the sale.
Level II data can be attached to any type of sale transaction, but Level III data can be sent via real-time products only if one item is being referenced during the transaction. If more than one item needs to be sent, the data will need to be appended to the sale using a separate XML batch transaction and the given enhanced data XML structure.
Level II/III transaction processing in 6 simple steps:
- You provide an interface to take account information from the merchant’s agent or customer.
- The account information and customer-supplied enhanced data is collected via the interface.
- You send the transaction data to EPX using your desired method.
- EPX processes the transaction and returns a response.
- Your server can then parse the results to determine if the response is an approval or decline and then provide this information back to the originating interface if required.
- If Level III data needs to be supplied that does not meet the real time submittal rules, the developer can then batch the Level III data from multiple transactions and send it to the EPX system using an XML batch for processing.
How to get started:
EPX provides developers access to a test environment for application building and separate credentials for production after completing certification.
The typical steps to completion:
- A developer must register to access the dashboard, initiate a project, and receive test credentials.
- With these credentials, the developer can build their application against the test environment.
- Prior to transmitting test level 3 batch files to EPX, an integration specialist must review the format of your file, as required.
- Upon review and approval of the test file’s format, they will release the SFTP credentials for the developer to begin transmitting request files.
- Once development is complete, you can submit the application for certification.
- After certification has been passed, the Integration Team will issue a certification letter, which you can use to get production credentials.