On this page
Installation and configuration
Configure Ingenico
-
Log in with your Ingenico merchant account to the test or prod environment (depending which one you want to configure)
-
Make sure your test account is properly configured and activated
-
In Configuration > Account > Your options you should have at least the following options activated:
- Fraud detection module (FDM)
- D3D (Direct Link 3D)
- DirectLink (new payments)
- Partial maintenance
- Alias Manager
- Refunds
- User Manager up to 5 users
You might need to contact Ingenico's Customer Care team to activate some of them.
-
In Configuration > Users: create a special API user that will be used for the API calls by Drupal - click on the New user button, enter required details, select Admin profile and check the Special user for API (no access to admin) checkbox.
-
In Configuration > Technical information:
-
Tab Global transaction parameters:
- Default operation code setting doesn't matter, as it will depend on the Commerce's Transaction mode value
- set Processing for individual transactions to Online but switch to offline when the online acquiring system is unavailable.
- set Default ECI value to 7 - E-commerce with SSL encryption
-
Tab Global security parameters:
- set Hash algorithm to SHA-512 (most secure)
- set Character encoding to UTF-8
-
Tab Data and origin verification:
- set URL of the merchant page containing the payment form that will call the page: orderstandard.asp to your site's base URL
- set SHA-IN pass phrase twice - both for e-Commerce & Alias Gateway as well as for Ogone DirectLink and Ogone Batch (Automatic) - both keys have to be alphanumeric only and both must have the same value
- optionally set IP address to that of your server
-
Tab Transaction feedback:
- In HTTP redirection in the browser section:
- no need to set Accepturl, Declineurl, Exceptionurl or Cancelurl, as they will be added automatically to each API request
- enable I would like to receive transaction feedback parameters on the redirection URLs checkbox
- disable I would like Ingenico e-Commerce Solutions to display a short text to the customer on the secure payment page if a redirection to my website is detected immediately after the payment process checkbox
- In Direct HTTP server-to-server request section:
- set Timing of the request to Online but switch to a deferred request when the online requests fail
- set both URLs of the merchant's post-payment page to
https://yoursite.com/payment/notify/<PARAMVAR>
- set Request method to GET
- In Security for request parameters section:
- set SHA-OUT pass phrase
- In HTTP redirection in the browser section:
-
Tab Transaction e-mails (optionally):
- fill in your email address
- set Receive transaction confirmation e-mails to Yes, for all transaction submission modes
- set Receive e-mails in the event of offline transaction status changes to Yes, for each offline status change (payment, cancellation, etc.)
-
Install and configure the module
-
Use Composer to get the module with all its dependencies:
composer require drupal/commerce_ingenico
Alternatively download the module manually together with marlon-ogone and mobiledetectlib libraries.
-
Add payment gateways at Administration > Commerce > Configuration > Payment gateways. The settings for both gateways are pretty much the same and should reflect your Ingenico account settings.
-
You might also want to change / verify the Transaction mode setting to be either Authorize and capture or Authorize only - at Administration > Commerce > Configuration > Checkout flows.
-
Make sure that your site is visible from the Internet, as otherwise you will not be able to receive asynchronous server-to-server notifications, which are required to update to payment transaction status.
For testing the integration on local installations you might use a service like Pagekite to make your local site visible from the Internet.
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion