Welcome for CMS integrations

Introduction

The following guide covers the first steps for integrating the payment gateway into your ecommerce platform. The steps to follow are:

1. Integrate Addon Payments into your website.
2. Set your gateway to the staging environment.
3. Make sure it works properly in the staging environment.
4. Ask to go live (switch to production).

During the integration phase, you can do all the testing you need with the gateway to make sure it works properly. To do so, see the following sections of this guide:

• Look things up on the BackOffice Portal.
• Orders not updated on my platform.

Integrate Addon Payments into your website

The first step is to properly install a compatible payment gateway and set it up with the information in the welcome email.

The merchant has to do the installation, or have it done by the service provider or integration company that is developing or integrating your online sales platform. Caixabank and Addon Payments are not responsible for this process.

For these platforms, you have a free module you can download from this page or the corresponding integration guides. These guides explain how to integrate, the most common mistakes with incidents and steps to follow, and how to manage transactions.

These are the platforms available. Click here for the installation guide:

• PrestaShop
• WooCommerce
• Magento
• Salesforce

To use modules, you have to authorize the domains you want to integrate the gateway into and activate compatibility with modules. To do so, follow the steps in Annex 1 of this guide – Add secure domain and activate compatibility with modules.

If your ecommerce platform isn’t on the list above (platform developed in house or customized or modular platform without Addon Payments compatible module), there are more details on integrations of this sort in this introductory guide.

Set up your gateway in staging environment

Once you’ve integrated Addon Payments into your ecommerce platform, you have to enter the configuration data for your merchant. The data you need to operate in the staging environment is:

• Environment or URL:

• • PrestaShop and WooCommerce:  “Production mode”: “disabled” in module set-up.
  • Magento: “Sandbox” on “Yes” in module set-up.
  • Custom developments: URLs of staging environments in the integration guides for each type of integration.

• Merchant ID: Provided in registration email.
• Product ID: Provided in registration email.
• Merchant password (encrypted): Provided in registration email.
• API key (modules and JS integration): Provided in registration email.

For modular platforms (PrestaShop, WooCommerce and Magento), you can set up the gateway following the specific integration guide for your platform:

• PrestaShop
• WooCommerce
• Magento

Make sure it works properly in the staging environment

With the payment gateway set up for the staging environment, it’s time for some test operations to make sure it works properly and your merchant data is set up correctly.

We recommend placing several orders through your ecommerce platform, choosing credit card as the payment method and continuing to the payment gateway, where you will be asked for the card number.

The following link has a list of cards that can be used to test various operations.

Once you have completed the operations correctly, check that they are all on the operations list on the Addon Payments BackOffice Portal. See the section on Searching BackOffice Portal of this guide.

Finally, check that the operations have updated the status of the orders on your ecommerce platform, marking them as authorized or declined, as applies. If this didn’t happen, see the section of this guide called Orders not updated on my platform.

Ask to Go Live (switch to production)

After testing and checking the payment gateway works correctly, you can request to switch to the production environment or go live.

To do so, send an email to support@addonpayments.com with the merchant ID you want to take live.

Once we’ve received your request, our team will make sure the payment gateway works properly on your ecommerce platform in the staging environment. To speed up the go live process, we recommend you verify these points before submitting your request:

1. Go to the URL provided for the virtual POS installed. If the URL isn’t accessible, or the virtual POS is temporarily installed on another URL for development or testing, you can give us the URL to visit for validation purposes in the email you send requesting the switch.
2. If a username and password or registered account are needed to complete the purchase process, please provide us with the necessary credentials. You can send them in the same email with your request to switch.
3. We will check that the products or services on offer comply with current legislation and are allowed by Caixabank for remote sales. See Annex 2 – Products or services not allowed for remote sales. So, most of the products or services must be loaded on your online shop, with a picture. If you offer unauthorized products or services, they will have to be removed before you can be validated.
4. We will choose a couple of items or make a booking, for rentals or hotels. The cart, booking engine or equivalent must be operational and allow us to complete the process. If specific steps are required to complete the order process, please include them in the same email with your request to switch.
5. We will choose credit card as the payment method. The online shop must generate and send the operation to the payment gateway in the staging environment, where we will check that all the merchant data is set up correctly. Note: The merchant platform is not allowed to capture, process or send customer card details if you don’t have PCI DSS certification.
6. If your ecommerce is a chemist that sells over-the-counter medicines, in addition to the requirements above, you must also meet those on the list of specific requirements for chemists selling medications.
7. Once your website has been validated successfully, you will receive an email to the authorized account with the steps for taking your virtual POS live.
8. If your shop isn’t successfully validated, you will receive a response to your request explaining why. You can ask to go live again when you’ve resolved the issue.

Below is a summary of the list of requirements for going live:

• Accessible URL, or provide an alternative URL.
• Credentials, if necessary to complete payment.
• Products or services loaded with pictures or photos.
• Working cart, booking engine or equivalent.
• No redirect to another page after choosing items.
• Active gateway for card payments that is correctly set up in the staging environment.
• Products or activities allowed for remote sales. See Annex 2 of this guide.
• Chemists that sell medications. Must comply with the instructions in Annex 3 of this guide.

Searching the BackOffice Portal

There is a BackOffice Portal where you can search for, capture and void operations that are pending and issue refunds of previous operations.

There is a guide to searching for operations on the Addon Payments BackOffice Portal with all the information you need.

Orders not updated on my platform

The most common issues that stop order statuses from being updated correctly are URL errors and errors involving server permissions.

On the BackOffice Portal, you can check that notifications from Addon Payments are reaching your ecommerce platform correctly with the order statuses.

To do so, find the “Transaction notifications” section at the bottom of the details for the transaction you want to check:

• The information is broken down in the following columns:
  • Date created: Date the notification was sent.
  • Notification URL: URL the notification was sent to.
  • Received: Boolean that shows your ecommerce platform received the notification.
    • true: The notification was received properly by your web server. A confirmation code (HTTP 200) was received.
    • false: The notification was not received properly by your ecommerce platform’s web server. May be due to non-existent URL, restricted-access URL (HTTP 403), URL not found (HTTP 404) or internal server error (HTTP 500) on your platform.

• • Message: Content of notification generated.

Note: If the notification can’t be delivered to the business site provided, AP will try again four (4) more times five (5) seconds apart.

If notification delivery fails, we recommend you follow the steps below to locate and correct the cause of the incident:

1. Go to the list of notifications for the transaction. Save the URL and content of the failed notifications.
2. Use a search engine to find a web tool that allows you to send HTTP POST requests.
3. Using the web tool of your choice, enter the notification URL on your platform in the outgoing URL. Use XLS format or type of content and notification message as the content.
4. Click “Send” in the web tool and review the response code you get back.
5. Check the code received and any solutions on the list of the most common HTTP response codes and rejections in this guide.

List of the most common HTTP response codes and rejections