Difference between revisions of "Quantum Gateway"
(Created page with 'In V4 we have implemented the MD5 hash verification in the Quantum Gateway callback file to prevent forged callback requests. Therefore, if you are a user of Quantum, you need to…') |
|||
| Line 1: | Line 1: | ||
| − | + | Quantum Gateway is a merchant gateway solution that supports 3D Secure for Visa & MasterCard Transactions in WHMCS. | |
| + | |||
| + | If you don't yet have an account, visit www.whmcs.com/quantumgateway.php for more information. | ||
| + | |||
| + | ==MD5 Hash Verification== | ||
| + | |||
| + | The MD5 Hash in the Quantum Gateway module is used to prevent forged callback requests. To set this up, you simply need to define a secret key value inside your Quantum Gateway account and then enter the same value into your WHMCS installation Quantum Gateway config in Setup > Payment Gateways. | ||
| + | |||
| + | Quantum also now have an "Include Response In Hash" setting which you should set to "No" within the account settings area. | ||
| + | |||
| + | ==Quantum Vault Service== | ||
| + | |||
| + | The Vault Solution from Quantum Gateway enables you to accept credit cards through your site while completely avoiding the hassles of PCI compliance and here at WHMCS we were one of the first to offer this new service to Quantum users. | ||
| + | |||
| + | ===How does it work?=== | ||
| + | |||
| + | #The customer leaves your site to perform 3D Secure authentication (exactly the same as they already do now) but the difference is they enter their card details once they've left your site aswell so that the card details never pass through your site | ||
| + | #The customer can still edit their card held on file at any time from the client area | ||
| + | #WHMCS can still request the card is rebilled whenever needed meaning fully automated recurring billing can continue as before and manual captures at any time are also still possible - it's just like you have the card details stored locally | ||
| + | |||
| + | ===Why does it avoid PCI compliance?=== | ||
| + | |||
| + | #No cardholder data ever touches or passes through your Network, Server or WHMCS System | ||
| + | #No cardholder data is ever retained or stored on your Network, Server or WHMCS system | ||
| + | |||
| + | ===Configuration/Setup=== | ||
| + | |||
| + | You will find the module in the '''Setup > Payment Gateways''' area listed as Quantum Vault which you can activate and configure in the same way as the regular module. | ||
| + | |||
| + | For existing Quantum Gateway users, there is also a '''vault migration script''' available on request to transfer all your existing clients card details over to the vault automatically and remove them from your local database. | ||
| + | |||
| + | Inside your Quantum Gateway account, you will need to configure and API Username, Key and Vault Key to use the Vault API, and in the Inline Frame API settings where it asks for various urls, you should leave all of those fields blank. | ||
Revision as of 14:33, 30 July 2010
Quantum Gateway is a merchant gateway solution that supports 3D Secure for Visa & MasterCard Transactions in WHMCS.
If you don't yet have an account, visit www.whmcs.com/quantumgateway.php for more information.
Contents
MD5 Hash Verification
The MD5 Hash in the Quantum Gateway module is used to prevent forged callback requests. To set this up, you simply need to define a secret key value inside your Quantum Gateway account and then enter the same value into your WHMCS installation Quantum Gateway config in Setup > Payment Gateways.
Quantum also now have an "Include Response In Hash" setting which you should set to "No" within the account settings area.
Quantum Vault Service
The Vault Solution from Quantum Gateway enables you to accept credit cards through your site while completely avoiding the hassles of PCI compliance and here at WHMCS we were one of the first to offer this new service to Quantum users.
How does it work?
- The customer leaves your site to perform 3D Secure authentication (exactly the same as they already do now) but the difference is they enter their card details once they've left your site aswell so that the card details never pass through your site
- The customer can still edit their card held on file at any time from the client area
- WHMCS can still request the card is rebilled whenever needed meaning fully automated recurring billing can continue as before and manual captures at any time are also still possible - it's just like you have the card details stored locally
Why does it avoid PCI compliance?
- No cardholder data ever touches or passes through your Network, Server or WHMCS System
- No cardholder data is ever retained or stored on your Network, Server or WHMCS system
Configuration/Setup
You will find the module in the Setup > Payment Gateways area listed as Quantum Vault which you can activate and configure in the same way as the regular module.
For existing Quantum Gateway users, there is also a vault migration script available on request to transfer all your existing clients card details over to the vault automatically and remove them from your local database.
Inside your Quantum Gateway account, you will need to configure and API Username, Key and Vault Key to use the Vault API, and in the Inline Frame API settings where it asks for various urls, you should leave all of those fields blank.