Prestashop Boarding Guide

Modified on Mon, 27 Feb 2023 at 09:10 PM

Before You Start

Before you attempt to set up the integration, please ensure you have/are using the following:

  • From Live Payments:

    • Registration for an ‘eCommerce / ISV’ account

      • If you are unsure whether your account is properly configured to support Cybersource integrations, please contact help@livepayments.com or call 1300 780 788. Be sure to mention that you are seeking to install the Cybersource Prestashop plugin.

    • Your ‘ISV Configuration Kit’ to configure the Prestashop plugin.

      • Note: This Configuration kit should contain 'REST API + Shared Secret' keys in here.

        • If you see a different type of API key in here, please flag this with the apps team member who previously contacted you.

      • You should have received this from the Live Payments CS/applications team shortly after you applied for the integration. This kit will contain key information required for a successful configuration.

      • If you have not received this, please contact customer support to obtain one. You can kick start this process by emailing help@livepayments.com with the email title ‘Request for CBS Woo ISV Configuration Kit’

 

Installation Guide

Step 1. Install the Cybersource Payment Add-on into your Prestashop Store

1.1 Download the module from here: https://addons.prestashop.com/en/other-payment-methods/49944-cybersource-official.html


1.2 In the “Modules” tab, click on “Module Manager”


1.3 In Module Manager, click on “Upload a module” button. 


1.4 Click on “select file” to browse the Add-on and upload it.


Once the Add-on is installed, head back to the PrestaShop Back Office to configure it.



Step 2. Open your 'ISV Configuration Kit'

This was shared with you by the Live Payments applications team. It should contain the relevant Merchant ID and API keys you'll need to configure your store. Please get ready to copy and paste the CBS Merchant ID, API Key and Shared Secret key into your Store.





Step 3.  Configure General Settings



Sandbox Mode
UNTICKED
Merchant IDCBS Merchant ID (from ISV Configuration Kit)
Merchant Key IDAPI Key (from API Configuration Kit)
Merchant Secret Key
Shared Secret (from API Configuration Kit)
Payer Authentication / 3D SecureUNTICKED
Note: we are exploring how to enable this in the near future. If you would like to apply to test this feature once we have enabled it, please submit a request here.

Enhanced LogsUNTICKED
Payment ActionSALE
Developer ID
Leave BLANK


HIT SAVE!


Step 4. Configure Payment Settings




Credit Card
TICKED
Click to PayVisa Click to Pay is Available on request. Please lodge a ticket with help@livepayments.com with the title: 'Prestashop ISV Visa Click to Pay Request'
Google PayThis can be configured with our Google Pay account. 
Apple Pay
UNTICKED
Note: we are exploring how to enable this in the near future. If you would like to apply to test this feature once we have enabled it, please submit a request here.
eCheckUNTICKED


HIT SAVE!





Step 5. Configure Fraud Management Settings




Fraud ManagementTICKED
TokenizationUNTICKED
Note: we are exploring how to enable this in the near future. If you would like to apply to test this feature once we have enabled it, please submit a request here.
Google reCAPTCHAreCAPTCHA v3 can be configured as an added layer of payment security. Please refer to Google's guides, available here: https://www.google.com/recaptcha/about/
Device FingerprintTICKED


HIT SAVE



Step 6. Ignore 'Report Settings'




Step 7. Happy Selling!

Please note, you can navigate back into here at any time to review the configurations






Support

If you require any assistance configuring the integration, or if you tun into any unexpected hurdles, please lodge a ticket by sending an email to help@livepayments.com

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article