Requirements and preparation

The "Paynet Direct" extension will only work if the following requirements are met:

• The web server must be configured in a special way.
• The eZ Publish version must be 3.5.0 or higher.
• For production use, a Paynet merchant account is needed.

Web server preparation

The web server needs to be configured in a special way. The following list reveals the most important issues that have to be taken care of.

• The web server must be able to access the Paynet server.
• The web server should use PHP 4.3.2 or higher.
• CURL support must be installed for PHP.
• The web server should be SSL-enabled.

Access to Paynet server

The web server on which eZ Publish is running must be able to access the Paynet server using HTTPS on port 8210. In particular, eZ Publish will attempt to access the following address: https://www.paynet.no:8210/if2. This means that the outer firewall must be opened, the local firewall (which is running on the web server itself, if any) must be configured, and so on.

Testing access

The "telnet" command line application (available on both Linux/UNIX and Windows systems) can be used to test whether the web server (the machine running the eZ Publish solution) has access to the paynet service or not. Instructions:

1. Bring up a shell / command line interface.
2. Attempt to access the paynet server using port 8210:
   

   telnet paynet.no 8210
   

   A connection should be established. On Linux/UNIX systems, this is indicated with a line saying "connected to paynet.no.". On Windows, an empty command window will be displayed.
3. Use the established connection to send a bogus GET request to Paynet:
   

   GET / HTTP/1.0
   

   There is a space between the first slash and HTTP. Hereafter press enter a couple of times.
4. The Paynet server should reply with something like "Your browser sent a request that this server could not understand". You should be able to see the HTTP response.

If everything works as described in the list above, it means that the web server running eZ Publish has proper access to the Paynet server. If something goes wrong or if no response is produced, a firewall somewhere between the web server running eZ Publish and the Paynet server is most likely blocking the traffic. This or these firewalls will need to be reconfigured. If you do not know how to do this or do not have access, you will have to consult either the local system administrator or the internet service provider.

CURL support for PHP

The "Paynet Direct" extension uses the "Client URL Library" (CURL) functions, which provide solutions for communication over a range of protocols (in particular HTTPS). This means that the CURL extension for PHP must be installed and enabled. Furthermore, the PHP version should be at least 4.3.2 if not higher. The installation instructions are available within the documentation page of CURL. The following text shows two methods that can be used to check if CURL is installed or not.

Checking CURL support using eZ Publish

1. Log into the administration interface of eZ Publish.
2. Click on the "Setup" tab.
3. Select "System information" from the menu on the left
4. Check if "CURL" is displayed under the "Extensions" section for PHP.

Checking CURL support using a PHP file

1. Create a PHP file (for example "test.php") and make sure it contains the following:
   

   <?php phpinfo(); ?>
   

2. Access the script (for example "http://www.example.com/test.php") from within a browser.
3. The output should reveal whether CURL is installed or not (just search for "curl" on the page).

SSL support

The CURL extension for PHP (mentioned above) will only encrypt communication between the web server running eZ Publish and the Paynet server. However, communication between the customers and the web server running eZ Publish should also be encrypted. Otherwise, the solution will be open and thus extremely insecure. Having SSL support on the web server running eZ Publish is highly recommend because it will encrypt the communication between the customers and eZ Publish. This means that it should be possible to access an eZ Publish page using a secure HTTP (HTTPS) connection. Please refer to the documentation of Apache SSL for information about installation, configuration, etc. The following illustration shows an overview of the visitor, the web server running eZ Publish and the Paynet server.

Payment traffic and encryption

Testing the SSL mechanism

To test whether SSL is working or not, attempt to access an eZ Publish page using the HTTPS protocol. This can be done by instructing a browser to access an URL that is similar to the following:

https://www.example.com/content/view/full/2

If everything works, the expected eZ Publish generated page should be visible in the browser.

Registering a Paynet merchant account

The Paynet service can only be used by authorized/registered Paynet merchants. In other words, you will have to sign up and become Paynet merchant. More information about becoming a Paynet merchant can be found at the following address: http://www.paynet.no/index.php/paynet/sign_up/merchant_application.html. When setting up the eZ Publish Paynet extension, make sure that you have the following information available:

• Your Paynet merchant number (also known as the agreement number)
• Your Paynet key-certificate

Please note that the Paynet extension can be tested using a special demo key-certificate. In other words, you do not need an actual Paynet account to test the solution. Please refer to the "Testing" section for more information about testing and the demo key-certificate.