Introduction   Specifications   Membership Application   Example   Demos   Admin   FAQ   Merchants   e-mail


SPECIFICATIONS


Egnatia Bank suggests all Merchants wishing to utilise WebShop comply with the specifications mentioned here.

Each Merchant can ask his customers for whatever data he needs to complete the order (through an HTML form, or a script with automatic entry check). Some of this data will feed Egnatia's server side script, if proven necessary. However there are some form variables which are anyway needed, for Egnatia to complete the transaction cycle, and should be included in the form.
After reading this page carefully, you will be ready to proceed to the Membership Application


WebShop service, at completion, will return certain parameters to the Merchant depending on whether charging the credit card was successful or not. For this reason, EXITURL and CANCELURL should be cgi scripts (and not static pages) and will record these parameters in log files/databases. Similarly, the Application which will send final data to Egnatia bank, could be a cgi script, because it has to assign TRANSACTION_ID to its users.

MERCHANT'S HTML FORM NECESSARY VARIABLES
FORM/CGI VARIABLE NAME FORM/CGI VARIABLE DESCRIPTION/VALUE
EXITURL The URL to load if charging Customer's credit card was successful. This URL should be in Merchant's domain. The script should record in a file all important order data (date, total amount, customer's personal info, ...) so the Merchant would be able to deal with the order. The Merchant will also be given the initial TRANSACTION_ID (set by Merchant's script), the AUTHORIZATION_ID (sent by VISA) and the total amount the card was charged.
CANCELURL The URL to load if charging Customer's credit card was not successful (card number not valid, expired card, revoked card). This URL should be in Merchant's domain. TRANSACTION_ID will be sent by Egnatia Bank as the main parameter, so the Merchant would have an estimate of number of customers being unsuccessful to charge their cards.
TRANSACTION_ID A uniquely defined number set by the Merchant which defines a certain attempt to charge a credit card.
This number will be used later for authentication purposes (sent back by Egnatia Bank).
CHARGE The amount VISA credit card will be charged.
RETURN_URL The URL (in Merchant's domain) to load if a customer exits the transaction cycle prematurely. Used by Egnatia Bank if a customer presses Return during applet download to cancel it. This page can contain a hyperlink to the first page of transaction cycle at Merchant's site. On this occasion Egnatia Bank will send TRANSACTION_ID to the Merchant.
LANGUAGE The language for the images (logo, background, colour, ...) to load. At the moment, could be one out of the following:
  1. Greek
  2. English
  3. German
  4. French
Don't forget that you have to set your images and info, for each language. If you set a language for which images are not defined, Egnatia's Bank script will detect it and provide appropriate help.


CAUTION

It is recommended EXITURL, CANCELURL, RETURN_URL to have the following form (cgi script call using GET method): http://..URL../exit?TRANSACTION_ID=3444445&USERNAME=Dimitrios &AUTHORIZATION_ID=344455&AMOUNT=23000

Merchant must himself assign as exit (script) parameters, the form variables he needs when cc charging is complete, which were collected by Application (TRANSACTION_ID, USERNAME). Egnatia Bank adds AUTHORIZATION_ID (not yet known to Customer) to the parameters end. In this way each Merchant can himself define all data he needs to complete his Customer's order, and record it appropriately after the transaction cycle.

1) EXITURL could be the same as CANCELURL if Merchant can handle both cases using the same script.

2) CANCELURL is designed to handle cc charging attempts, using cards which are not valid for some reason (mentioned above).
RETURN_URL is designed to handle cases in which a Customer cancelled Egnatia Bank's applet download (pressing return during download).

3) CANCELURL could be the same as RETURN_URL if Merchant can handle both cases using the same script.

4) CANCELURL, EXITURL, RETURN_URL could all be the same, if Merchant can handle all cases using the same script.


Introduction   Specifications   Membership Application   Example   Demos   Admin   FAQ   Merchants   e-mail