Answers to Technical Questions:

Do I need my own SSL (Secure Socket Layer) certificate on my website?

SecurePayTech.com highly recommends you have access to an SSL certificate on your website, so that all information you are posting to the SecurePayTech.com application servers is encrypted. You can purchase your own SSL cert fromvarious certificate issuers, and we suggest Thawte and Instant SSL

For customers that simply want to process transactions manually, SecurePayTech.com offers this functionality when they are logged into their customer profile, which enables you to take advantage of SecurePayTech's own SSL certificate.

What currencies do you support?

Currently the only currencies supported is the New Zealand Dollar (NZ$). We will be adding additional, multi-currency support soon.

Can I get a working example template?

Templates in various programming languages can be accessed and downloaded from our Sample Code section.

What programming languages do you support?

Developers can use virtually any programming language to interface into the SecurePayTech.com payment gateway. Common examples that are being used are PHP, CF, ASP and .NET.

What encryption methods/levels do you use?

SecurePayTech.com uses 128bit Thawte Secure Socket Layer (SSL) certificates to encrypt all information transmitted between a customer's browser, and the SecurePayTech.com payment gateway. All sensitive information stored on SecurePayTech.com's servers is encrypted using the Blowfish encryption algorithm with a 448bit encryption key.

How do I integrate SecurePayTech into my website?

SecurePayTech.com has compiled a list of Integration Partners that you can contact for assistance in getting your website to transact through the SecurePayTech.com payment gateway. Furthermore, please read the information contained within Developers Documentation section.

How resilient is your architecture and what failover contingency plans do you have in place?

SecurePayTech.com is utilizing state of the art technology in the infrastructure, and incorporates PHP, mySQL clusters, J2EE, and JBOSS. As uptime is so crucial in a payment gateway, redundancy has been built into the entire process, with multiple application servers, the mySQL cluster, as well as utilizing Digiweb's state of the art data centre and Internet connectivity to ensure maximum uptime. IBM servers have been used for hardware throughout the SecurePayTech.com environment, and any node can be taken out of the cluster, and the service will continue to function normally.

Do you have an API document available for download?

Yes. All documentation relating to this will be stored in the Developers Documentation section.

What responses can I expect back from the SecurePayTech gateway in terms of errors, or successful transactions etc?

Full information pertaining to this can be located in the Developers Documentation section. A quick summation of the server responses are:

Code	Response	Description
1	Transaction OK	Self Explanatory
2	Insufficient Funds	Self Explanatory
3	Card Expired	Self Explanatory
4	Card Declined	Card is declined for a reason aside from insufficient funds or an expired card
5	Server Error Occurred	A software error occurred either at SecurePayTech or at one of our provider's systems
6	Communications Error	This usually indicates that a timeout has occurred while processing the transaction request
7	Unsupported Transaction Type	Self Explanatory
8	Bad or Malformed Request	Self Explanatory
9	Invalid Card Number	Self Explanatory