DEVELOPER NOTICE: ePN will be discontinuing all communications using TLS v1.0 and TLS v1.1 effective August 15, 2016.
The Transparent Database Engine Integration (TDBE) is an Application Programming Interface (API) that allows you to integrate your website or application to perform credit card, debit card, gift card, and check transactions.
TDBE allows you to collect customer, order and shipping information to process transactions from your own secure servers. POST the transaction information to TDBE and we will reply with a comma delimited response. Integrating with the TDBE requires advanced programming skills.
Websites and applications that collect and maintain customer order information can use the TDBE to seamlessly process transactions without the customer ever leaving the website. All applications that communicate with the TDBE are required to securely transmit transactions. Developers generally must install the required security libraries for the language being used on their own server. Installing these libraries is beyond the scope of the support offered by eProcessingNetwork.
The Database Engine Integration (DBE) was developed for merchants that securely collect and save customer, order and shipping information to their own database, but wish to leave the secure collection of credit card data to us.
You can pass your customers information and a few order details to our secure hosted page, where we collect all the credit card data and processes the transaction on a real-time basis. After the transaction has been processed, we can automatically post back to you or we can present an authorization page on our site that indicates the status of the transaction with a redirect button.
The button is directed at the URL provided in your post. Just specify your database
ID and the URLs for your form handlers with
You can bypass the Auth/Approval page and automatically redirect and post to your URL by passing
Redirect = 1.
The ePN Web Order Form Generator assists you in creating order forms for your Web site that tie into ePNs Web Order Template. Advanced options available for the ePN Web Order Template are in the documentation below. The Order Form Generator, will walk you through defining options that once defined, will generate a Web Page that is tailored to your products.
The SDK provides a framework for processing both swiped and keyed transactions via eProcessing Networks' secure gateway. We support the ePNMobile iMagPro encrypted card reader for card present, swiped transactions.
Supporting the iOS and Android platforms, our SDK provides key methods for card reader interaction.Get The SDK
For developers who have already integrated Authorize.Net™, we offer an Emulator.
ePN allows the basic set of AuthNet™ transaction types to facilitate a quick and simple migration to our gateway. However, we do not recommend using this product in custom solutions being built from the "ground up". We recommend the Authorize.Net™ Emulator in situations where pre-existing software is being used or if using a shopping cart that will allow the posting URL to be redirected to ePN (instructions below).
To use the full potential of eProcessing Network processing capabilities, we recommend using our Transparent Database Engine Integration (TDBE). This API allows credit card, debit card, gift card, and check transactions with the maximum available functionality from our company.
To support the response hash used by all protocols as well as the fingerprint hashing used by the SIM protocol, eProcessing Network uses the RestrictKey in the "Processing Controls" section of the Merchant Support Center (ePN/MSC). Use this RestrictKey as your secret key for hashing.
Change this link:
To one of these links, depending on the integration method being used:
Then just pass in the merchant's eProcessing Network information in place of Authorize.Net™ account information.
x_loginvalue with the ePNAccount number.
x_trankeyvalue with the Restrict Key generated through the ePN account.
x_typevariable at all. (SIDE NOTE: the Processing Controls section can be accessed by logging into the Gateway Account and selecting Processing Controls from the navigation menu.)
For documentation on these protocols, please reference Authorize.Net™ directly.
|DBE||TDBE||AN-AIM3||MERCHANT SUPPORT CENTER|
|AUTH 2 SALE||X||X||X|
|TRANS ID /TOKENS||X||X|
Follow the steps below to diagnose problems you may encounter with your integration:
This URL will generate a Web page that displays exactly what was sent to it, helping confirm that you are correctly sending required information.
Include a variable called
PostURL (case insensitive), with a value of
where you are posting to eProcessingNetwork.com, such as:
Include a variable called
For questions, suggestions or special requests, email us at firstname.lastname@example.org
API changes for .NET, Java, and cURL to enable TLS v1.2
SecurityProtocol property to enable TLS v1.2.
For details on how to use the SecurityProtocol property, visit:
For example, to force TLS v1.2 in a C# .NET implementation, you would use:
NOTE: JDK 8 will use TLS v1.2 as default:
For JDK 7, use the
SSLContext.getInstance method to enable TLS v1.2.
For details on how to use the
SSLContext.getInstance method, visit:
For example, to use the default security layer provider to enable TLS v1.2, you would use:
object = SSLContext.getInstance("TLSv1.2");
To force TLS v1.2 while using Oracle’s Sun Java Secure Socket Extension (JSSE), you would use:
object = SSLConnect.getInstance("TLSv1.2", "SunJSEE");
CURLOPT_SSLVERSION option to enable TLS v1.2.
For details on how to use the
CURLOPT_SSLVERSION option, visit:
In cURL version 7.34.0 or later, use the following examples to force TLS v1.2:
curl_easy_setopt(curl, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1_2);
curl_setopt($curl_request, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1_2);