Integrating the payment gateway with your site
This page covers integration for merchants using our payment gateway Lite, Professional and Enterprise solutions. It does not cover the complete solutions Fast Track or Bank Enterprise. You can find information on integrating the complete solutions here.
The information below is only a brief summary of the integration process, for complete Integration Guides, visit our Resources & Documentation section.
Details of the remote procedure calls accepted by our API are available online for both SOAP and XML-RPC.
ValCard
ValCard is the name of PayPoint.net’s hosted payment page. If you have a Lite account, this page will look like this, but Professional account holders can template the page to tie in with the look of their own ’site.
This page is typically called by an HTML POST created by a form on your website which includes at least an PayPoint.net account ID, a transaction ID, an amount, a callback url and an MD5 digest. Other parameters can be accepted also, but these four are the minimum required to create a transaction. We will give you an account ID when you sign up, you choose the transaction ID and the amount, and the callback url is that of a page on your ’site which will display a thank you message, and perhaps update a database with the results of the transaction. The digest field is an MD5 hash of the transaction ID, amount, and a remote password known only to you and PayPoint.net. It’s purpose is to ensure that the transaction really does come from you.
ValCard functionality is described in both the Lite Account Integration Guide and the Professional and Enterprise Account Integration Guide, which are available from the Resources and Documentation page.
There is a method called XMLValCard with which you can access the functionality of ValCard, but it should not be confused with the full API methods. This approach to integration is deprecated now.
The API
Professional (and Enterprise) account holders have the option of interfacing with our powerful API (Application Programming Interface). This offers the potential of performing more complex operations than initiating transactions; eg, refunds, reporting and the release of deferred transactions. A guide to the SOAP API interface and a guide to the XML-RPC API interface are available.
Integrating with the API is rather more complex than with ValCard, and there are security requirements as you will be gathering (though probably not storing*) credit card details on your ’site. However, the API is well documented with consistent behaviour, and with the help of our experienced Technical Support department, any reasonably competent developer will be able to access the full functionality.
*Full support for ‘tokenisation’ (a unique code given in exchange for an authorised card) – eliminates the need to store sensitive card data and reduces your PCI DSS requirements.
Download our complete Integration Guides in the Resources & Documentation section >>
