Development Integration Overview

Integrate eProcessing Network solutions directly into most Web pages, shopping carts, and third-party software. ePN provides specs, sample code and support at no additional charge. Listed below are the tools to payment-enable your solution with eProcessing Network.

TDBE Transparent Database Engine Integration

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.

DBE DataBase Engine

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 ReturnApprovedURL and ReturnDeclinedURL. You can bypass the Auth/Approval page and automatically redirect and post to your URL by passing Redirect = 1.

WOFG Web Order Form Generator

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 ePN Order Form Generator produces one HTML page each time it is executed, which may be saved to your computer. Use your favorite HTML editor to customize each of those pages as you see fit.

SDK for Mobile Processing

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

Authorize.Net Emulation

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.

We support the following Authorize.Net protocols:

  • AIM (Advanced Integration Method)
  • SIM (Simple Integration Method)
  • DPM (Direct Post Method)
  • CP (Card Present)

Hash and SIM

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.

Typically all a developer has to do is change the posting URL from Authorize.Net to eProcessing Network:

Change this link:

To one of these links, depending on the integration method being used:

AIM Users:
SIM Users:

Then just pass in the merchant's eProcessing Network information in place of Authorize.Net account information.

  • You must replace the x_login value with the ePNAccount number.
  • Also, replace the x_trankey value with the Restrict Key generated through the ePN account.
  • If you would like to utilize ePN's Processing Control as the default fraud prevention tool with the Authorize.Net™ Emulator, do NOT submit the x_type variable 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.

Supported transaction types by integration:

Sale Auth AuthConvert Void Returns Recur Store Gift Sale from Token (TransID)
TDBE (eProcessing Network API) X X X X X X X X X
Authorize.Net Emulator Credit Cards (AIM) X X X X X
Authorize.Net Emulator Credit Cards (SIM) X X X
Authorize.Net Emulator Check Processor (AIM & SIM)
ECHO Checks (WEB) X X
ECHO Checks (CCD) X X
GETI/SAGE Web Checks (WEB) X
GETI/SAGE Web Checks (CCD) X

Note: An "X" denotes that the transaction type is supported.

Integration Diagnostics

Follow the steps below to diagnose problems you may encounter with your integration:

  1. Temporarily change the URL to which you are posting your transactions to:
  2. Include a variable called email (case insensitive) to send a reflection of your variables and their value to that email address.

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, such as:

Include a variable called email (case insensitive) and this will send a reflection of your variables and their value to that email address.

For questions, suggestions or special requests, email us at