Difference between revisions of "Payflow Pro"
| Line 1: | Line 1: | ||
| + | ===Configuration=== | ||
| + | To activate the module, begin by going to '''Setup > Payments > Payment Gateways''' and choosing "Payflow Pro (PayPal)" from the available list of gateways to activate. | ||
| + | |||
| + | ====API Details==== | ||
| + | |||
| + | [[File:Pp_api1.png|thumb|PayPal API Step 1]] | ||
| + | Once activated, you then need to enter your details for the PayPal Pro API. These can be found as described below. | ||
| + | |||
| + | #Login to PayPal | ||
| + | #Go to Profile > My selling preferences > API Access | ||
| + | [[File:Pp_api2.png|thumb|PayPal API Step 2]] | ||
| + | #Choose '''Option 2''' - Request API credentials to create your own API username and password. | ||
| + | #Choose '''Option 1''' - Request API Signature and click Agree and Submit | ||
| + | #Copy the username, password and signature that get provided and then click Done | ||
| + | #Enter the details from the previous step into the WHMCS Payment Gateways config screen where requested | ||
| + | |||
| + | ===3D Secure=== | ||
| + | |||
| + | The next 3 fields in the configuration after API details are: '''Processor ID, Merchant ID & Transaction PW'''. These are used by the 3D Secure process. PayPal Pro Accounts are usually enrolled for this by default these days and if you have been enrolled, PayPal will have provided you with the details for it. | ||
| + | |||
| + | If they haven't or you don't want to use the 3D Secure feature, then simply leaving these fields blank in WHMCS will disable the 3D Secure process, and mean it is not used during the checkout process on your site. | ||
| + | |||
===Use Reference Transactions=== | ===Use Reference Transactions=== | ||
This feature helps reduce your PCI compliance liability. Instead of storing card details in the WHMCS database the ID of the last transaction is used to make repeat charges. The limitation with remote card number storage is that changing payment gateway would require clients to re-enter their card details. | This feature helps reduce your PCI compliance liability. Instead of storing card details in the WHMCS database the ID of the last transaction is used to make repeat charges. The limitation with remote card number storage is that changing payment gateway would require clients to re-enter their card details. | ||
Contrary to what you might think, you should not tick the setting to "Disable Credit Card Storage" in '''Setup > General Settings > Security''' as that will disable entry by a client. | Contrary to what you might think, you should not tick the setting to "Disable Credit Card Storage" in '''Setup > General Settings > Security''' as that will disable entry by a client. | ||
Revision as of 11:21, 24 July 2012
Configuration
To activate the module, begin by going to Setup > Payments > Payment Gateways and choosing "Payflow Pro (PayPal)" from the available list of gateways to activate.
API Details
Once activated, you then need to enter your details for the PayPal Pro API. These can be found as described below.
- Login to PayPal
- Go to Profile > My selling preferences > API Access
- Choose Option 2 - Request API credentials to create your own API username and password.
- Choose Option 1 - Request API Signature and click Agree and Submit
- Copy the username, password and signature that get provided and then click Done
- Enter the details from the previous step into the WHMCS Payment Gateways config screen where requested
3D Secure
The next 3 fields in the configuration after API details are: Processor ID, Merchant ID & Transaction PW. These are used by the 3D Secure process. PayPal Pro Accounts are usually enrolled for this by default these days and if you have been enrolled, PayPal will have provided you with the details for it.
If they haven't or you don't want to use the 3D Secure feature, then simply leaving these fields blank in WHMCS will disable the 3D Secure process, and mean it is not used during the checkout process on your site.
Use Reference Transactions
This feature helps reduce your PCI compliance liability. Instead of storing card details in the WHMCS database the ID of the last transaction is used to make repeat charges. The limitation with remote card number storage is that changing payment gateway would require clients to re-enter their card details.
Contrary to what you might think, you should not tick the setting to "Disable Credit Card Storage" in Setup > General Settings > Security as that will disable entry by a client.