Terminal. SECURENET Gateway API

SecureNet Gateway API is a secure platform that facilitates electronic commerce by enabling merchants to accept credit cards and electronic checks as methods of payment for goods and services sold.

PDF

Document

SecureNet Gateway Implementation Guide 4.1.5

XML Tag

</SECONDARY_MERCHANT_K

EY>

Data Type /

Max Length Required

Integer / 8 True

String / 250 Required if

METHOD=E

Description

7-digit unique SecureNet ID provided by

SecureNet to identify the merchant and is required for each submitted transaction

If a SecureNet ID is needed contact

SecureNet

For EBT transactions only. String format:

11 (EBT indicator) followed by a 7-digit

FNS number (left-justified, space-filled, if

FNS is less than 7 digits).

Reference

6.17 Terminal

This object includes merchant-related information on locations and terminal. If not provided, this information will be taken from the merchants records. If provided, this object will overwrite any existing data in the merchants records.

XML Tag

Data Type /

Max Length

String / 10

String / 27

String / 20

<TERMINALLOCATION> String / 27

Required

Required for Ceridian

Required if SECCODE POS

AND several locations are being processed via one single SecureNet ID

Required if SECCODE POS

AND several locations are being processed via one single SecureNet ID

Required if SECCODE POS

AND several locations are being processed via one single SecureNet ID

Notes

Terminal City—This field identifies the city, town, village, or township in which an Electronic terminal is located

Terminal Identification Code—This filed identifies an Electronic terminal with a unique code that allows a terminal owner and/or switching network to identify the terminal at which an Entry originated

Terminal Location—This field identifies the specific location of a terminal (i.e. street names of an intersection, address, etc.) in accordance with the requirements on

Regulation E. Section 205.9(a)(5) requires that an ATM or POS terminal receipt contain the location of the terminal where the transfer is initiated, or an identification such as a code or terminal number.

Comment 9(a)(5)–1 is revised, as proposed, to clarify that either a code or location may be disclosed.

Comments 9(a) (5) (iv)–1 and –2 are re-designated as comments 9(a) (5)–

3 and –4.

Reference

Refer to Section 4.1 and 4.2 for Methods and Section 7.1 for

Transaction Object

Specification.

Key features

Supports real-time and offline requests for credit card authorization
Supports electronic check transactions
Secure socket connection
Server and client-side encryption
Supports Simple Object Access Protocol (SOAP)
Supports REpresentational State Transfer (REST)

Frequently asked questions

A typical transaction is performed in the following way:

The customers program has a reference to the Gateway Service and connects securely to the merchants server to transmit payment information.
The merchants server initiates a secure connection to the Gateway and creates the objects as described. It then initiates a “ProcessTransaction” function by passing the TRANSACTION object along with required data to the Gateway server.
The payment Gateway receives and processes the TRANSACTION object.
The payment Gateway generates the GATEWAYRESPONSE object and submits it to the merchants server.
The merchants server receives and processes the GATEWAYRESPONSE object.
Finally, the merchants server communicates the success (or failure) of the authorization to the customer’s web browser or program.

Merchants must be able to perform the following functions in order to submit transactions to the Gateway:

Complete the Gateway Certification Request Form
Create an account in our test environment
Establish a secure socket connection
Provide both server and client-side encryption
Develop code on a web server for the integration to the Gateway utilizing the Gateway service (e.g. for submitting transaction data object and receiving and translating system response object)
Securely store the following information in a way that it is configurable: Service URL, SecureNet ID, its corresponding SecureKey, and, optionally, transaction mode (TEST or LIVE). This information will be accessed by the script that submits transactions to the Gateway
Complete the certification process by running test scripts for the transaction scenarios.

The SecureNet Gateway supports the following types of transactions: Standard Payment Transactions Vault Transactions AutoBill Transactions Reporting Methods for Batch and Transaction Services Reporting Methods for SecureNet Vault and AutoBill Services Reporting Methods for P2P Encryption Services Batch Close