Downloads & Guides
.............................................................................................................................................................................................................

Due to the nature of our business integration methods are often subject to change without notice. Therefore we now only provide Direct Payment Integrations, API's and Guides once an application is approved and ready for integration work. Please note that we can supply integration guides on request (subject to terms)

We provide test environments and test accounts to enable you to test your website and ecommerce integration. This can be advantageous when developing your website, as it enables you to try out your payment pages with credit cards without transferring real funds - more >>>

API Reference Guide for Web Services

The API allows you to securely submit several transaction types by way of your own site.

• Your customer can create a profile that includes personal information and billing details. The profile is securely stored, which is used for future e-commerce transactions and can be modified by the customer when required.
• Your customer can transparently process purchases on your e-commerce site – the customer experiences your branded site only.
• You can use existing customer profiles to process purchase transaction requests, e.g., for billing requests that occur regularly.

Direct Payment Component Guide (for Java)

The merchant sends transaction requests (e.g., Purchase) to the transaction processor via Java Direct Payment, which acts as a secure transport medium. The merchant uses sockets through SSL (Secure Sockets Layer) to communicate securely with the payment server over the Internet. Transactions are validated at both the Java Direct Payment and the payment service levels. For example, the transaction processor sends a response for both successful and failed transactions (e.g., if an invalid card type is supplied).

Direct Payment Component Guide (for Windows 2000/NT)

The merchant application (ASP, VB, or VC++) uses a dictionary object to exchange relevant data with the Direct Payment component. The dictionary object is a data structure that stores information in pairs of keys, with a one-to-one key value (e.g., the credit card type might be Visa). This transaction request information is coded in an ASP script or in a VB or VC++ application.

Direct Payment Component Guide (for Unix/Linux)

Transactions are validated at both the Direct Payment library and the payment service levels. For example, the transaction processor sends a response for both successful and failed transactions (e.g., if an invalid card type is supplied). The Direct Payment library sends an error message if information it requires is missing or incorrect (e.g., if your merchantId value is missing).

Static Payment Link Guide

The Static Payment Link service allows merchants to receive payments by credit card quickly and securely via the Internet, without having to integrate their online stores to the payments transaction processing service. With Static Payment Link, you only have to embed one or more HTML links – which we provide– into your store’s Web page. This link takes your customer to a secure payment page transparently hosted by said bank. The customer provides all the required payment information and clicks the Make Payment button.

Dynamic Payment Link Guide

The Dynamic Payment Link service allows merchants to receive payments by credit card quickly and securely via the Internet, without having to integrate their online stores to the payments transaction processing service. With Dynamic Payment Link, you only have to embed some HTML – of which wes provides example of – into your online store. This takes your customers to a secure payment page transparently hosted by said bank. The customer provides all the required payment information and clicks the payment button.

Checkout API for one-time payments (Tradegard account)

The Checkout API allows a customer to transparently process secure purchases on your e-commerce site. Please note that the account for this integration is for eCommerce transactions only and does not support the virtual terminal or the repeat billing facility.

The Unified Payment Page Method (UPP)

This integration method is simpler than that of the Checkout API in terms of implementation. You would need to simply send certain variables through a standard HTML form and a payment page is generated for the customer to process a payment. Like all our integrations, the customer will be redirected back to your website.

Stand Alone Recurring Billing Guide

The Stand Alone Recurring Billing tool allows you to create, update, and search for recurring billing records. Once you set up your recurring billing records, we do the rest, processing the recurring transactions for the amount, at the frequency, and over the time period that you specify. Billing records are easy to set up and edit. All you have to do is enter some basic information in the Recurring Billing tool in the back office.

Recurring Billing API

The recurring billing operations allow you to create and update recurring billing records. You can integrate easily with the Web Service API, using their favourite platform and language. You can automate operation and avoid manually keying in information via the banks Secure Payments Web page. Merchants can operate independently of changes and updates to the Payments Web site.

Chargebacks and how to minimise them

Manual review of transactions

AVS / Security code

Refunding a suspected fraudulent transaction

Solution 1 Merchant Account + Gateway Datasheet

Solution 2 Merchant Account + Gateway Datasheet

High-Risk Merchant Account + Gateway Datasheet