POSTING information to PROTX Limited via HTTPS

(N.B: ALL code examples and references to integration kit files within this document are related
to the ASP kit ONLY. To download kits in other languages please visit the Downloads page.)

In the previous step, we covered which values needed to be collected in order to successfully register a transaction. Now these values have been collected and formatted they must now be POSTed securely to Protx - to begin the transaction registration process.

As a Vendor, you have now, through the use of your shopping cart or the kit provided collected a number of values that are mandatory requirements to successfully register a transaction against the VSP System. Those values are set out clearly and distinctly in the Protocol guide and must be adhered to strictly if you wish to experience trouble free transactions.

Whether you collect those values on one page or over a number of pages is down to your discretion. You can pass those values around the script pages in the kit using the session and also hardcode such consistent variables such as your VSP Vendor name, if you wish to do so.

In the previous section you will have gathered and formatted the fields, you now need to prepare them to POST to Protx. Please see below an example of the 'vps_order_purchase.asp' page (please note, all example code is in ASP ONLY)

In this kit you will use the standard WinHTTP component to POST securely to Protx. This component should be built into the server you have your website and cart hosted on. Please remember that the POST must come from an Static IP address that you have registered with your Protx account, by adding it into the appropriate administration area. This is additional security, and Protx will ONLY accept POSTs from IP's that are explicitly declared by being added into your admin area or supplied during your online application.

Please see below an example of the 'vps_order_purchase.asp' page which makes the POST via the WinHTTP component.

In the above you are declaring the POST destination as 'PurchaseURL' (see line 79). These URL's are declared and listed in your Includes.ini file. You will have a number of URL's to choose from. Where you POST to will depend primarily on two things:

•   What the POST is trying to achieve
•   What 'mode' your Protx account is set to

By this, we mean that there are individual and specific URL's for the following:

•   A transaction REGISTRATION
•   A transaction REFUND
•   A transaction ABORT
•   A transaction REPEAT

Furthermore, these URL's reside on either our TEST or LIVE servers and are broken down into:

•   The SIMULATOR server URL
•   The TEST server URL
•   The LIVE server URL

For example, to register a transaction on the LIVE server, you would use the Live purchase URL and NOT a refund URL on the test server.

The URL's are simply called upon and pulled out of the includes.ini file. You will notice the following in that file:

The three examples above specify the full URLs used for SIMULATOR, TEST and LIVE. It is important that in your protx.ini file you have the below code set to whatever is appropriate for your current situation:

SimulatorSite=1
TestSite=0
LiveSite=0

Be aware that by default you will NOT be Live, until the testing criteria has been met. This will include at least ONE transaction being processed via your website to your Protx test account and followed by at least ONE refund.