• What is the difference between the post-sale URLs and the redirection URLs?

    Both the redirection and post-sale URLs can be used to send feedback to once a transaction is completed. The main difference is that on the redirection URLs no feedback can be sent if the customer has left the payment page before being redirected to a redirection URL, whereas the post-sale URLs can also receive delayed feedback.

    Go to Transaction feedback (e-Commerce documentation) for more information.

  • What is the difference between Sale and Authorisation?

    In the "Global transaction parameters" tab of your account's Technical information page, you can choose between Sale and Authorisation as the "Default operation code".

    For some payment methods (mainly credit cards), transactions are performed in two steps: the authorisation and the data capture (payment request):

    • During the authorisation step, the transaction amount is either reserved on the customer’s card or account, or the request is matched against a blacklist (for fraud detection).
    • In the data capture (payment request) step, the acquirer is requested to take the reserved amount from the customer’s card or account and transfer it to your bank account.

    Based on these two steps, you can choose between two default operation codes:

    • Authorisation: our system will only ask for an authorisation, in order to have the authorisation and payment request performed separately at different times (the money remains on the customer’s account until a payment request has been performed).
    • Sale: our system automatically requests the payment (transfer of the amount), immediately after a successful authorisation. This procedure is often used for goods/services delivered online.
  • What is the difference between the SHA-IN and SHA-OUT passphrase?

    The SHA-IN passphrase is the key that is used to verify the input parameters of a transaction. The SHA-OUT passphrase is the key that is used to verify the returned parameters, once a transaction is completed.

    Go to SHA-IN and SHA-OUT for more information.

  • What are the different ECI values good for, and which one should I use?

    ECI (Electronic Commerce Indicator) values are used to indicate to the acquirer what the source of a transaction is, e.g. MOTO (mail/telephone order), e-Commerce (with and without 3-D Secure), etc.

    In the acquirer agreement is defined exactly what type of transactions you can process, and thus what ECI values can be used.

    With Ogone e-Commerce, the ECI is automatically determined. In case of Ogone e-Terminal, DirectLink and Batch, you can overwrite the default ECI by submitting another ECI value in the transaction details.

    A default ECI value is automatically configured in your Ogone account, based on your account type.

    The ECI values you can configure in your account (via Configuration > Technical information > Global transaction parameters > Default ECI value) are the following:

    ECI value Description
    1 Mail order/Telephone order (MOTO)
    2 Recurring payments coming from MOTO
    3 Installment payments
    4 Manually entered (card present)
    7 E-commerce with SSL encryption
    9 Recurring payments from e-commerce
  • What does the message “An error has occurred; please try again later. If you are the owner...” mean?

    The message "An error has occurred; please try again later. If you are the owner or the integrator of this website, please log into the Ingenico ePayments back office to see the details of the error." is a generic error message which is returned if a specific technical issue occurs at the moment the payment page is called. We don't display the actual error on the payment page, mainly because of security reasons, but also not to confuse your customers.

    In your Ingenico ePayments account, via "Configuration" > "Error logs", you can easily look up the errors that occurred when the generic error message was displayed. The actual meaning of these errors are described on the Possible errors page.

  • What credit card numbers can I use for testing?

    You can use the following card numbers to make test payments in the test environment:

    Payment method Test card number
    VISA 4111 1111 1111 1111
    VISA with 3-D Secure 4000 0000 0000 0002
    MasterCard 5399 9999 9999 9999
    MasterCard with 3-D Secure 5555 5555 5555 4444
    American Express 3741 1111 1111 111
    American Express with 3-D Secure 3714 4963 5311 004
    Maestro 6759 6498 2643 8453
    Bancontact/Mister Cash 6703 0000 0000 0000 3
    JCB 3530 1113 3330 0000

    In your test account you can find more and/or other test numbers via Configuration > Technical information > Test info.

    Note: You will only see the card numbers relevant to the cards you have activated in the Payment methods section of your account.

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