The EPX Server POST API is a service designed to allow the secure communication of financial transactions from a developer’s server directly to the EPX Payment Gateway servers. The transactions are passed to the EPX servers via standard HTTPS. The system allows a developer to send any EPX transaction type (ecommerce, retail, EBT, ACH, MOTO, debit, banking, CyberSource, signature capture, money transfer) from a merchant's agent or customer driven interface, through the developer’s servers, directly to EPX for real-time financial processing. Server POST transactions can be initiated on physical developer servers or cloud servers as per your specific needs.

Delivering definitive business benefits:

The EPX Server POST API simplifies the method of processing transactions by allowing one device to communicate with a payment processor. Implementations based on the Server POST API can be used for Gateways, Web Based transactions, POS devices/terminal, and other solutions. The Server POST API can be used with the majority of the EPX transaction types making it the most versatile tool in the EPX toolbox.

Data can be passed containing typical customer account information (credit card, ACH, EBT, debit, and more), as well as using tokenization (EPX BRIC). As an alternative to processing transactions via Server POST HTTPS, Server POST XML offers the same API, but across an active SSL connection that decreases the latency in communication.

How it works:

The EPX Server POST API receives transactions in HTTPS format from developer servers and submits the supplied data to the EPX Payment Gateway. EPX then processes the request document of the transaction and responds back to Server POST API with network response information. The Server POST API sends the transaction response information (formatted in XML) back to the developer’s server as a response to the original POST request.

EPX Server POST HTTPS API transactions in 7 simple steps:

  1. The developer provides an interface to take account information from the merchant’s agent or customer.
  2. The account information is taken from the interface and delivered back to the developer’s servers.
  3. The developer sends the HTTPS POST transaction over the standard SSL port, 443, to send the request data to the Server POST API.
  4. The Server POST API formats the financial transaction and submits it to the EPX Payment Gateway.
  5. The EPX Payment Gateway responds back to the Server POST API with the network response information.
  6. The transaction response information is formatted in XML and sent on the same connection back to the merchant’s server, typically within a second of the request being received.
  7. The developer’s server can then parse the XML results to determine if the response is an approval or decline, and then provide this information back to the originating interface.

How to get started:

EPX provides you with access to a test environment for application building, as well as separate credentials for production (after completing certification).

The typical steps to completion:

  1. A developer must register to access the dashboard, initiate a project, and receive test credentials.
  2. With these credentials, you can then build your application against the test environment.
  3. Once development is complete, you submit your application for certification.
  4. After certification has been completed, the Integration Team will issue a certification letter, which can be used to secure production credentials.