Caution: This documentation is for eZ Publish legacy, from version 3.x to 6.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Testing

This section describes simple testing procedures which allow you to verify the proper functioning of the installed extension.

Test merchant

First, you could do some test transactions with the Paynet demo merchant. Set in "paynetterminal.ini" your "ShopID" to "00000001". Go to the Paynet test server and choose a "ShopSubID" that is not in use. (At the time of writing the URL to the paynet testserver is: "https://www.paynet.no/term193/".)

On the Paynet Web site, configure the URLs for receipt, abort and completion.

Creditcard validation

Once everything is configured, you can do some test transactions by mimiking a customer in the eZ Publish online shop. When it comes to the checkout, you can provide

  • a random number, which will fail.
  • choose a test creditcard number: 5555555555554444 or
    4444333322221111 with any expiry date, which should succeed.

Make sure that you will be directed to the correct URL before and after the checkout, especially when creditcard validation failed or continued successfully.

Failed transactions

Failed transactions can be faked by playing with the redirected Paynet URL. If you change the values "id", "subid", "currency", "amount", or "utref", the transaction will fail. This is visible in the "eZPaynetChecker.log" file.

If you change the "Receipt URL" on the Paynet server to an invalid URL, the customer will get a time-out after the payment. This time-out page should contain information how the customer can contact you.

Raymond Bosman (18/03/2005 12:06 pm)

Raymond Bosman (07/10/2005 2:26 pm)

Raymond Bosman, Sandro Groganz


Comments

There are no comments.