Transaction Delivery Methods

InterPay™ supports request/response delivery using SSL. You can connect to our server using SSL and send just the request (without HTTP headers), or HTTPS “GET” can be used in order to send the request and receive the response in a “Web page” type format. The “POST” method is also supported.

The HTTPS GET method is useful if your platform is capable of performing HTTPS page retrievals. Our servers use port 1443 for all SSL-encrypted traffic. The information returned from this method is not formatted to be displayed directly to the cardholder.

In its simplest form, the GET may be accomplished with a web browser by entering the request in the “location” text box. The response is then delivered back to the browser as a document of MIME type “text/plain”. This will allow the response to be shown in the browser.

Using a browser is a good method of testing connectivity before you start building your interface.

Gateway Requests

All requests are delivered using field names and values commonly referred to as tag/value format or, optionally, JSON.

Requests are built by concatenating a series of fields and their values, separated by ampersands (&). The field value is separated from the field name by an equal sign (=).

If an ampersand is required in a field value then two ampersands (&&) must be sent in order to distinguish between the field and field separators.

Field values may be URL-encoded to allow for special characters.

A field may also consist of a list of field groups. This is represented by the following format:

&field=[subfield=value&subfield2=value][subfield=value&subfield2=value]

Gateway Responses

Responses will also be in tag/value format.

HTTP headers will be added to the response message if HTTP headers were included in the request.

Gateway Addresses

Requests are processed by connecting to the InterPay™ gateway servers at:

https://svra.InterPayPOS.com:1443/

https://svrb.InterPayPOS.com:1443/

These servers are geographically disbursed and equally capable of processing requests. If one server does not respond or returns a 99xx error code then retry the request on the other server.

Sample Message Format

Sample request and response for a host-based credit card Sale transaction.

Request:

TERMID=TESTMERC&PASS=mypass&CARD=5123456789012345&EXP=0407&AMT=4350&REF=43&TYPE=S

or (this can be placed right in your browser)

TERMID=TESTMERC&PASS=mypass&CARD=5123456789012345&EXP=0407&AMT=4350&REF=43&TYPE=S

Response:

HTTP/1.0 200 OK
Content-type: text/plain
Content-length: 145

TEXT=T7580843.50&CODE=0000&AUTH=T75808&TOKEN=4003IFNTCCP16781&HASH=AFD6B61A6955A3B11B2ACEB4193EA981&DATE=2016-03-28&TIME=17:58:08&DUR=0.146