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

Direct Payment Integrations and API and Guides

You can use this area to download any of the relevent documents, guides, manuals and instructions that you may need for informational purposes.

Due to the nature of our business integrations methods can change. Therefore the information within these documents is subject to change without notice. Up-to-date manuals and integration guides are available once your application is approved and ready for integration work.

API Reference Guide for Web Services
The API allows you to securely submit several transaction types by way of your own e-commerce 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.

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.

Pre-Check Form
With the info you provide, we can determine whether we can assist you with obtaining your credit card merchant account(s). If your precheck is approved, we ask you to proceed and complete our (more elaborate) application form.

Submitting Transactions to our Hosted Payment Page (HTML Redirect)
This guide describes how to connect your Internet shop to the Gateway Only payment processing system, using our HTML integration method. It provides practical guidance as well as in-depth reference material.

Test and Go Live
This guide describes how to test your website shop with our payment processing system, and how to take your website live. It provides practical guidance as well as reference material.

Customising Guide (Standard)
This guide explains how you can customise our HTML-based payment service. You can customise the appearance of the Payment Service to a considerable extent. For instance, if you would prefer to have Payment Service Pages that match the other pages in your website, rather than use our standard ones, then you can do this. We provide a Payment Page Editor which enables you to carry out a range of customising tasks.

• This guide covers the customisations you can carry out using the Payment Page Editor.
• Some basic but frequently used customisations are described in the chapter Some Basic Customisations.

Customising Guide (Advanced)
This guide explains how you can customise our HTML-based payment service. You can customise the behaviour of the Payment Service as well as the look and feel of the Payment Service Pages. Generally,

1. You can customise the Payment Service behaviour via installation settings in the Integration Setup Pages,
2. And you can customise the look and feel of the Payment Service via changes
   made to the Payment Service Page files.

Payment Notifications
Once a payment has been processed, either through to success or to cancellation, information about that payment is sent to you by using the Payment Response feature. The Payment Response feature posts the payment information from our server to a URL on your server via HTTP(s). This enables you to validate the information, update the order and if required display your own shopper result pages.

Remote Administration of FuturePay Agreements

Select Invisible Batch Processing

3D Secure introduction manual

White Papers

Payment Page and VT Demos

Credit Card and Corporate Logos

Solution 1 Merchant Account + Gateway Datasheet

Solution 2 Merchant Account + Gateway Datasheet

High-Risk Merchant Account + Gateway Datasheet