Sage Pay Server requires you to have your own server to communicate with our payment systems and to store additional transaction information. You won't need to handle card details but it is recommended that you get an SSL certificate. Shoppers will be redirected to Sage Pay's payment pages during the checkout process.
Sage Pay Server is bundled with osCommerce Online Merchant and is also available as a separate Add-On package existing store owners can use to upgrade to.
The Sage Pay Server payment module supports the following features:
This document can be found online at:
PayPal payments can be accepted as a payment method through Sage Pay. This requires PayPal to be added as a supported payment method to your Sage Pay account and your PayPal seller account to be linked to your Sage Pay account.
Please refer to Linking PayPal to Your Account for instructions on how to link PayPal to your account.
All secured API transaction calls sent to Sage Pay are performed by verifying Sage Pay's SSL certificates to guarantee the identity of Sage Pay. This is performed by using the following public keys in order if they are available:
A test connection link is available on the payment module configuration page which can be used to test if API transaction calls to Sage Pay can be verified from your web server. If the test connection fails, please contact your hosting provider as they may need to update your web server configuration. The SSL certificate verification can also be disabled on the payment module configuration page however it is highly discouraged to disable.
|Enable Sage Pay Server Module||Setting this parameter to True makes the payment method available to customers during the checkout procedure.||True|
|Vendor Login Name||The vendor login name used to connect to the transaction gateway with.|
|Profile Payment Page||
Profile page to use for the payment page.
The following transaction methods are available to process transactions with:
|Set Order Status||The orders status will be updated to this value when a successful transaction has been made.||Default Order Status|
|Transaction Order Status||Transactions are logged in this private order status level.||Sage Pay [Transactions]|
|Payment Zone||If set, this payment method will only be available to orders made within the defined zone.|
The following transaction servers are available to process transactions through:
|Verify SSL Certificate||Verify Sage Pay's identity when API communication calls are sent.||True|
|Proxy Server||Send API communication calls through this proxy server.|
|Debug E-Mail Address||Send invalid transaction parameters to this e-mail address.|
|Sort Order||The position to show the payment method on the checkout payment page against other available payment methods.|
The separate Sage Pay Server Add-On package is available at:
An online demonstration is available at:
For the online demonstration, Sage Pay Server has been configured with Sage Pay's test server environment and requires a test payment card to purchase an order.
After extracting the Add-On package, copy the files located in the catalog directory to your osCommerce installation directory on the server. The files must be copied in the correct directory structure as extracted from the Add-On package.
The file listing is as follows:
The standard language definitions in English are provided in the Add-On package. For additional languages, copy the English language definition file to the appropriate language directory and open the file with a text editor to edit the language definitions. The location of the language definition file must be in:
When the files have been copied to their appropriate locations, the payment module will be available on the Administration Tool -> Modules -> Payment -> Install Module page where it can be installed, or on the Administration Tool -> Modules -> Payment page if the module was already previously installed.
If the module was already previously installed, it is important to visit the module configuration page to make sure new parameters are automatically installed in the database.