Integration with Securetrading internet payment system is easy with BazaarBuilder ecommerce shopping cart software

Online Payment By SECPay

Securetrading is a secure, online, real-time payment service provider, supporting all major credit and debit cards with the (major) UK acquiring banks for Visa, Mastercard, Switch, Solo, Delta, JCB, American Express and Diners Club.

Their business is real time online Payment Processing over the Internet.

Bazaarbuilder provides integration with Securetrading:

You need to have a SecureTrading account before you can set up your system; for instructions on how to obtain one see the web page at:

Your site Reference:

You should have received a "Welcome " email when your secure trading account was set up. This contains your site reference. Your site reference is important you will need to quote it in all correspondence with secure trading.

Images in customized web pages:

You may want to display an image, for example logo.jpg or .gif file of your company logo, on one of your web pages held on the secure trading secure server. If so then the images that you are using should also be located on the secure trading secure server.

Lets say that you want to insert a logo into form.html, which is called companylog.gif.

You can insert the logo into the web page using HTML code like this.

<IMG SRC="$path/companylogo.gif">

The $path variable holds the full path to your files on the secure trading secure server. Its value is generated automatically by the secure trading system. You need to upload the images to the secure trading secure server before they can be used on your pages.

Use the upload manager of my-st to do this.

Uploading files

The form.html must be uploaded to the securetrading secure server.

You must not change the name of the file(form.html). You can upload these files to the securetrading secure server by using the upload manager of my-st using this link


The st payment pages callback feature allows you to run a script on your merchant web server at the final stage of a transaction.

Different script can be run in different circumstances for example whether or not the transection is authorized by the bank.

Callback is an advance feature of securetrading's st payment pages service.

Callback.txt and callback-f txt

Callback.txt contains information about which script to run on your merchant server if an authorization is successful callback-f .txt contains similar information for unsuccessful authorization. After these files have been created they should be uploaded (using my-st) to the secure trading secure server.

The two files have the same format

The basis callback.txt file looks like this .

Method1 POST url1

Fields1 orderref,name,address,postcode

Pipe1 yes


This variable defines the method by which data is passed to the script on the merchant server. The method available are same as used in HTML forms, POST and GET


This variable contains the URL of the script to be run on the merchant web server.


This variable contains a list of fields that should be sent to the script on the merchant web server. Individual field name are separated by a comma following by a single space.

Callback url

Callbackurl is the variable that determines which of the script listed in callback.txt is run following a successful authorization. If the form.html value of callbackurl is 1 then callback is enable and script from callback.txt is called

Failureurl is the variable that determines which of the scripts listed in the callback-f .txt is run following an unsuccessful authorization. It is used in exactly the same way as callbackurl, so enable it


You have to add extra variable to callback.txt and callback-f to fine tune the way that callback behaves.

PipeX (where X is an number from 1 to 8) is an optional variable that governs whether success.html or failure.html is displayed to customer after transection .it can take the values yes or no and is inserted in callback.txt or callback-f.txt

Valid XHTML 1.0 Transitional