Real-Time Payment Confirmation

Background

EBS can provide real-time confirmation that a payment was accepted by our system. In the case of Credit Cards, the confirmation can include an "Approve / Decline" code. In the case of ACH, we can provide confirmation that the transaction was "Accepted" by our system (true approval / denial does not occur until 1 or more days after the transaction is submitted to the ACH system).

In its simplest form, our system will make an HTTPS form post to a CGI that the client provides. The information posted can range from simple confirmation to more complete transaction information. The rest of this document will explain the "simple" interface, which is the basis for all other implementations.

Simple Interface

			<form name="form01" method=POST action=https://www.yourdomain.com/cgi-bin/payment.cgi>
			  <input type="hidden" name="cid1" value="~cid1~">
			  <input type="hidden" name="seqno" value="~seqno~">
			  <input type="hidden" name="tdate" value="~date~">
			  <input type="hidden" name="ttime" value="~time~">
			</form>

The fields in the above example are defined here:

Variable Notes
CID1 The primary ID from the payment page (the first ID). All the identifiers can be passed, the example shows just CID1.
SEQNO The transaction sequence number. If you need to discuss a transaction, refer to this number.
tdate/ttime Transaction date and time, relative to our web server. This is Eastern time, syncronized to the NIST atomic clock servers.

 

Additional fields can be passed in any confirmation message. In fact, every field on the payment page can be included in the real-time interface to your system.

Set Up

  1. Client provides a CGI application on their web site which will accept a transaction from EBS and post it to your internal system.
  2. Decide which transaction types you want: Approved, denied, accepted (or a combination).
  3. EBS will create a series of test confirmations which you must process and report back to EBS. This will ensure the interface is working properly.
  4. We will arrange an implementation time convenient to both parties.

 

In the best case scenerio, a "simple" payment confirmation interface can be completed in as little as two business days.