Advanced Implementation

Back

View Advanced Impl. Guide

How to implement a coupling between your website and the ICEPAY payment methods in Advanced Mode

(Not applicable for other payment method initialization methods.) 

Who should read this? This information is intended for the technical staff (webmaster, software engineer, etc.) at your company.

Requirements

The following things are required to get started:
• A server-side scripting environment that is capable of generating SHA1 hashes. PHP4, PHP5, Perl 5.x and ASP.NET 2.0 are capable of doing this. Although other languages and environments might also be capable of generating SHA1 hashes, they have not been tested by us.

• An ICEPAY account – once your account is activated you can create a Merchant by logging in to the ICEPAY portal. Go to ‘My Websites’ and fill in the data, your secret code (encryption code) will be provided automatically if the URLs are correct.

Warning: Never reveal these two codes to third parties! The Merchant ID and Secret Code (encryption code) are used to verify your identity.

Note: Each Merchant ID (+ Secret Code) is meant to be used for only 1 (one) website. Additional merchant ID’s are available via the ICEPAY portal, under ‘My Website’.

Implementation

You must implement the following items:
• One scripted page for server-to-server communication. You can set this value in web interface when you login into the client area. This URL is named IC_Postback in the Guide (see 5.5).

• A “Shopping Cart Checkout” page. This is where your system must initiate the ICEPAY payment.

• A “Success” page. This is where the user will go to when the ICEPAY payment has been completed successfully. In the more technical part of this document, it is referred to as IC_URLCompleted (see 5.4).

• An “Error” page. This is where the user will go to when the ICEPAY payment cannot be completed, aborted, failed, or canceled. In the more technical part of the Guide, it is referred to as IC_URLError (see 5.4).