This payment gateway works with the following setup's
- Joomla 1.5.X (Legacy on) and Virtuemart 1.1.X
- Joomla 1.0.X with Virtuemart 1.0.X
- Joomla 1.0.X and Virtuemart 1.1.X
It wont work with Joomla 1.5.X unless the Legacy plugin is turned on, as it just keeps saying "direct Access to this location is not allowed." within the payment gateway configuration panel, which I'm trying to find a solution now.
A fully working Payment Gateway that I will install for you included in the price.
For £50 (which is 2hrs labour) I will add the gateway, set it up, and contact the HSBC E-Payment team, have them check it and activate the account for you.
All I need is -
- Customer ID Number
- Hash Key
- FTP or Joomla Xplorer access
- Customers address (as HSBC will ask me for this when I call them to verify they are in the correct account)
- The site MUST have a valid SSL cert, shared or dedicated to the site, (otherwise the gateway will fail every time, this is a HSBC requirement)
I don't need any other details regarding the account/client such as sort code or account number. When I am speaking to HSBC, they cant/wont give me any info for security reasons regarding your client or finances. All they can do to by law is tell me if the gateway has been accepted or declined, no other info will be passed over. Once they have accepted it, they will turn the gateway to live within 24 hrs allowing you or your client to accept payments.
Once the order has been paid successfully, the order status is updated to "completed", allowing digital downloads to be downloaded, and the webmaster to see it has been accepted. The buyer is transferred back to the site after with a Message explaining what has happened in plain English. There are about 16 messages that could be displayed, depending on what result HSBC gives.
- Transaction has been successfully processed.
- You have cancelled the transaction.
- The transaction was rejected by Fraud Shield (which is a fraud detection system by HSBC).
- The transaction was placed in Review state by Fraud Shield (which is a fraud detection system by HSBC).
- The transaction failed because of invalid input data.
- The transaction failed because the CPI was configured incorrectly.
- The transaction failed because the Storefront was configured incorrectly.
- The connection timed out.
- The transaction failed because your browser refused a cookie.
- Your browser does not support 128-bit encryption.
- The CPI cannot communicate with the secure ePayment engine.
- The processor declined the transaction for an unknown reason.
- The transaction was declined because of a problem with the card. For example, an invalid card number or expiration date was specified.
- The processor did not return a response.
- The amount specified in the transaction was either too high or too low for the processor.
- The specified currency is not supported by either the processor or the card.
- The order is invalid because the order ID is a duplicate.
I have been told by the E Payment team, that this will work for any HSBC account anywhere in the world, I have set it up for one Hong Kong account, and it worked perfect.
Any queries, please ask away, but please look at my feedback on other extensions, so you can see how I work with my clients :)
All Products
