Last update 11/09/2018

5. Notes

5.1 General

The following statuses can appear in Magento ®:

  • No credits in Ingenico ePayments back office: This means that you can only send your credit requests via Magento ®.
  • 3D-Secure (MasterCard, SecureCode and Verified by Visa) must be activated: This means that your Ingenico ePayments account must accept 3D-Secure. 

5.2 Multistore

You can use the extension in Magento ® Multistores with:

  • multiple websites
  • multiple stores
  • multiple domains
  • multiple Ingenico ePayments accounts

In order to use multiple Ingenico ePayments accounts, you have to follow the steps mentioned in Ingenico ePayments back office and Magento for each Ingenico ePayments account and website or store.

Most important is that you setup correctly the response urls in the Ingenico ePayments back office:

  1. Go to "Configuration > Technical information > Transaction feedback".
  2. Configure the following fields:
    • Direct HTTP server-to-server request
    • HTTP request for status changes.

The correct configuration of these urls is clarified with the following examples. 

5.2.1 Example: store code in url using the same Ingenico ePayments account

The Multistore consists of two stores which are assigned to the same website. The example is also valid in case both stores were assigned to different websites:

  • Store A operates under http://www.my-shop.com/shopa/
  • Store B operates under http://www.my-shop.com/shopb/

The correct configuration in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop.com/shopa/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop.com/shopa/ops/api/directLinkPostBack

The feedback will be processed correctly for store B, also if the response is send only to the url of store A. 

5.2.2 Example: different domains and different Ingenico ePayments accounts

The multistore consists of two stores which are assigned to different websites and uses two different Ingenico ePayments accounts:

  • Store A operates under http://www.my-shop-a.com/
  • Store B operates under http://www.my-shop-b.com/

The correct configuration for Store A in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop-a.com/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop-a.com/ops/api/directLinkPostBack

The correct configuration for Store B in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop-b.com/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop-b.com/ops/api/directLinkPostBack

5.2.3 Example: different domains using the same Ingenico ePayments account

The multistore consists of two stores which are assigned to different websites and the same Ingenico ePayments account:

  • Store A operates under http://www.my-shop-a.com/
  • Store B operates under http://www.my-shop-b.com/

The correct configuration for both stores in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop-a.com/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop-a.com/ops/api/directLinkPostBack

You also have to configure Magento ®'s base url for Store B:

  1. Go to "System > Configuration > General > Web".
  2. Insert "http://www.my-shop-b.com/" in the "Base URL" and "Base Link URL" fields in the "Unsecure" section. Use/keep the default value for the other fields of the "Unsecure" section.
  3. Insert "https://www.my-shop-b.com/" in the "Base URL" and "Base Link URL" fields in the "Secure" section. Use/keep the default value for the other fields of the "Secure" section.

5.2.4 Example: store code in url using different Ingenico ePayments accounts

The multistore consists of two stores which are assigned to the same website and uses two different Ingenico ePayments accounts. The example is also valid in case both stores were assigned to different websites:

  • Store A operates under http://www.my-shop-a.com/
  • Store B operates under http://www.my-shop-b.com/

The correct configuration for Store A in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop-a.com/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop-a.com/ops/api/directLinkPostBack

The correct configuration for Store B in the Ingenico ePayments back office is the following:

  • Direct HTTP server-to-server request: http://www.my-shop-b.com/ops/api/postBack
  • HTTP request for status changes: http://www.my-shop-b.com/ops/api/directLinkPostBack
As a leading global digital payment service provider, Ingenico Payment Services provides a seamless response to the complexity of payments, whatever the channel: online, mobile and point-of-sale. Offering innovative e-commerce, multi-channel, financial, and marketing solutions, it helps merchants to manage, collect and secure their payments, prevent fraud and increase their revenues through higher conversions. Ingenico Payment Services is part of the Ingenico Group, the global leader in seamless payment.

This website uses cookies to be able to give you the best user experience. If you don't want to accept these cookies, we allow you to change the cookie settings. Click 'Accept' to allow all cookies from this website.

Cookie settings

Introduction

Functional

Functional cookies are required for the website to operate correctly. These cookies cannot be disabled.

Optimized

Optimization cookies allow us to analyze site usage so we can measure and improve our website.
This is the default level.

Personalized

Personalization cookies are used for social media and advanced personalization. They allow us to show you information related to your company.


Example functionality allowed

  • Store country preference
  • Store language preference

Example functionality not allowed

  • Saving personal data
  • Anonymous tracking via Google Analytics
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics

Example functionality not allowed

  • Saving personal data
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics
  • Serve content relevant to your interests
  • Serve ads relevant to your interests
  • Tracking for remarketing purposes

Example functionality not allowed

  • Saving personal data