Last update 21/05/2014

1. Disclaimer

Copyright © 2016 Ingenico ePayments.

All trademarks, service marks and trade names referenced in this material are the property of their respective owners. The information contained herein is provided as a courtesy and is for general informational purposes only. This information is not intended to be a complete description of all applicable rules, policies and procedures. The matters referenced are subject to change from time to time, and individual circumstances may vary.

Ingenico ePayments shall not be responsible for any inaccurate or incomplete information. The information contained herein includes, among other things, a compilation of information received from third parties, and any such information is and shall remain the property of its respective owner. Nothing contained in this presentation is intended to supplement, amend or modify any applicable contract, rule or regulation.

Ingenico ePayments has given extensive attention to the content of this information but makes no warranties or representations about the accuracy or completeness of it. Neither Ingenico ePayments nor any of its affiliates shall be liable for any costs, losses and/or damages arising out of access to or use of any content of this document. Because of the complexity of the process and the right of Banks to alter conditions, this document can only serve as a description and is subject to further modifications.

The Extension referred to in this document was developed as a generic solution. Ingenico ePayments shall not be responsible for any damages that are caused by the extension. In the event that the Extension is modified by a user in any way Ingenico ePayments shall not be responsible for any damages that are caused by the modified Extension. The description of the Extension in this document is provided for convenience purposes only, and Ingenico ePayments makes no warranties or representations about the use or operation of the Extension. Neither Ingenico ePayments nor any of its affiliates shall be liable for any costs, losses and/or damages arising out of access to or use of the extension.

2. What is a PSPID?

The PSPID is the unique identifier of your Ingenico ePayments account. It is the ID you chose (or were given) at the registration of your Ingenico ePayments account, and which you usually login with.

When configured in your shopping cart, our system will use the PSPID to identify you as a registered merchant.

3. What is an API user and its differences?

Depending on your shopping cart, you may be asked for an API-user and password for the API-user.

The API-user is a separate user you create in your Ingenico ePayments Account. Its only purpose is to allow an application (your shopping cart) to create and/or maintain transactions on our platform.

Unlike other users, you can't login with the API-user.

Where in my Ingenico ePayments account can I find this setting?

In the main menu, go to "Advanced" > "Users", click "New user" and check "Special user for API".

More information on User Management

4. What is an operation code?

In your shopping cart you may be requested to configure an operation code. This way you can choose how you want your credit card transactions to be processed; in two stages (Authorisation) or in one stage (Sale). If you use a different operation code in your shopping cart, this will override the default operation code in your account.

Authorisation

The money is reserved on the customer's card. You need to confirm the transaction (within a certain period, depending on your acquirer contract), so the amount is taken from the customer's card.

> We recommend this option if you don't have an automated stock system, if you work with reservations/bookings (such as for hotels), etc

Sale

The money is taken instantly from the customer's card

> We recommend this option if you provide an online service such as ticket sales, etc.


Where in my Ingenico ePayments account can I find this setting?

In the main menu, go to "Configuration" > "Technical information" > "Global transaction parameters" > "Default operation code".

5. What is a SHA signature/passphrase?

The SHA signature is a data integrity check, that guarantees no one can tamper with the details of a transaction, e.g. to lower the amount. You need to enter a passphrase, a character string of your own choice, both in your shopping cart and in your Ingenico ePayments account. 

SHA-IN passphrase

The SHA-IN verifies the data when they are submitted to the payment page. This is a mandatory check.

SHA-OUT passphrase

The SHA-OUT works the same as the SHA-IN, only it is used to verify the data after the transaction is processed.

Although the SHA-OUT check is not required, you are still obliged to enter a value for the SHA-OUT
passphrase.

Note: the SHA-IN/OUT passphrases must be different in your production and test account

Where in my Ingenico ePayments account can I find these settings?

SHA-IN passphrase: go to "Configuration" > "Technical information" > "Data and origin verification" > "Checks for e-Commerce"

> More information about SHA-IN 

SHA-OUT passphrase: go to "Configuration" > "Technical information" > "Transaction feedback" > "Security for request parameters"

> More information about SHA-OUT

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