Global Configuration PayPal: Configure

Global configuration parameters affect all App modules and can be configured on the Configure page using the General button.

Configuring the global App configuration parameters

This should be left as PayPal unless you have set up your PayPal account to process payments through Payflow. Setting this to Payflow affects the following modules:
  • PayPal Express Checkout
  • PayPal Payments Pro (Direct Payments)
Transactions Order Status
This is the Order Status level where the result of API transactions are stored. This Order Status level should be private and should not be visible to customers when they view their order information.
Verify SSL
Keeping this enabled ensures the connections to PayPal's servers are secure and are not being tampered with. This uses the following public keys in order if they are available:
  • ext/modules/payment/paypal/
  • includes/cacert.pem (public key bundle)
  • the php / web server configured public key bundle
If connections to PayPal's servers cannot be made, disabling this setting may help however it is recommended to find a solution that allows this settings to remain enabled.
SSL Version
Use the default cURL configured SSL version connection setting when making API calls to PayPal or force TLS v1.2 connections.
A connection test can be performed using the Test Connection button to open a dialog window showing the results of the default configured SSL version and forced TLS v1.2 connections.
Some hosting providers require a proxy to be used for cURL connections to be made.
Log Transactions
The request and response values of each API transaction call can be logged to identify and help find a solution to any problem. It is recommended to log all API calls when beginning to use the App and to change it to log only errors when all App features have been tested.

Module Configuration

App modules that have already been enabled can be configured using their respective configuration buttons. Additional App modules can be enabled using the + button and selecting from a list of available modules to install.

Installing additional App modules

After a new module has been installed, it performs requirement checks to make sure the module can be enabled on the store. If any requirements are not met, the module remains in a disabled state until the requirement has been fixed.

Notification of a requirement for a new module

In the image above, a notification is displayed due to missing API Credentials. The module will remain in a disabled state until the Live credentials have been entered or the module has been configured to use the Sandbox credentials.