> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# Ingenico / Worldline / Ogone

## Configuration Ingenico

In order for the Ingenico Direct Adapter to work you need to configure the following settings in the Ingenico Portal.

1. Navigate to **Configuration > Technical Information > Ingenico Direct Settings** (see Ingenico Portal)
2. Insert as **Endpoint Urls** the **Notification URL** of the configured Ingenico Connector (to be found in the Connector Base data, see e.g. Connector Detail Overview - Ingenico Creditcard - Vault Configuration)
3. Save the **API Key, API Secret** , **Webhook Key** and the **Webhook Secret** to be used in the Connector configuration

![Ingenico Portal](https://documentation.ixopay.com/manual/assets/ideal-img/ingenico-portal.558697f.1280.png)Ingenico Portal

> **Tip**
>
> You can create the IXOPAY platform connector using dummy input parameters in order to generate the Notification URL to be inserted for the Webhook Key creation in the Ingenico Portal.

## Connector Configuration

Configure the following parameters for the Connector, depending on the selected Payment Method and Ingenico Endpoint (see Connector Config - Ingenico Direct):

1. Fill in the mandatory **Merchant ID**
2. Fill in the mandatory **API Key**
3. Fill in the mandatory **API Secret**
4. Fill in the mandatory **Extra Data: webhookID**
5. Fill in the mandatory **Extra Data: webhookSecret**
6. Select in the mandatory **Extra Data: dynamicDescriptor:** True, False
7. Select in the mandatory **Extra Data: paypalAddressSelection:** True, False

![Connector Config - Ingenico iDeal](https://documentation.ixopay.com/manual/assets/ideal-img/connector-config-ingenico-ideal.d2b7a18.1280.png)Connector Config - Ingenico iDeal

Additional parameters to be configured (see Connector Detail Overview - Ingenico Creditcard - Vault Configuration):

1. Select the mandatory **Platform** Global Collect, Ogone
2. Select the mandatory **Environment** Live, Pre-Production, Sandbox
3. Check the optional Option **Use final authorization for pre-authorization (if the MID doesn't support normal authorization)**
4. Check the optional Option **Use final authorization for debit (if the MID doesn't support normal debit)**
5. Check the optional Option **Enable dynamic Descriptor**

![Connector Detail Overview - Ingenico Creditcard - Vault Configuration](https://documentation.ixopay.com/manual/assets/ideal-img/connector-detail-overview-ingenico-creditcard-vault-configuration.7cbaeea.1280.png)Connector Detail Overview - Ingenico Creditcard - Vault Configuration

Configure the following parameters (see Connector Config - Ingenico SEPA, Connector Config - Ingenico iDeal XML):

1. Fill in the mandatory **Username**
2. Fill in the mandatory **Password**
3. Fill in the mandatory **API Secret**
4. Fill in the mandatory **Extra Data: apiKeyId**
5. Fill in the mandatory **Extra Data: merchantId**
6. Fill in the optional **Extra Data: resellerId**
7. Fill in the optional **Extra Data: defaultMandatePlace**
8. Fill in the optional **Extra Data: IpWhiteList**
9. Fill in the optional **Extra Data: sftpUsername**
10. Fill in the optional **Extra Data: sftpPassword**
11. Select the optional **Extra Data: handleRejectsAsErrorsAndNotAsChargebacks:** True, False
12. Select the optional **Extra Data: mandateSigned:** True, False
13. Fill in the optional **Extra Data: iDealIssuerRetrieveAllowedOrigins**
14. Select the optional **Extra Data: SDDTreatPendingAsSuccess:** True, False

![Connector Config - Ingenico SEPA](https://documentation.ixopay.com/manual/assets/ideal-img/connector-config-ingenico-sepa.8e7694c.1280.png)Connector Config - Ingenico SEPA![Connector Config - Ingenico iDeal XML](https://documentation.ixopay.com/manual/assets/ideal-img/connector-config-ingenico-ideal-xml.63e9c14.1280.png)Connector Config - Ingenico iDeal XML

Additional configuration specifics can be found in the Adapter-specific API Documentation

Configure the following parameters for the Connector, depending on the selected Payment Method and Ingenico Endpoint (see Connector Config - Ingenico Sofort):

1. Fill in the mandatory **Extra Data: apiKeyID**
2. Fill in the mandatory **Extra Data: merchantID**
3. Fill in the mandatory **Extra Data: webhookID**
4. Fill in the mandatory **Extra Data: webhookSecret**
5. Fill in the mandatory **Extra Data: webhookSecret**
6. Select in the mandatory **Extra Data: endpoint**

![Connector Config - Ingenico Sofort](https://documentation.ixopay.com/manual/assets/ideal-img/connector-config-ingenico-sofort.e6779cb.1060.png)Connector Config - Ingenico Sofort

> **Note**
>
> Depending on which Ogone endpoint you are using, you either need to configure the Igenico or the WorldlineOgone Adapter. Contact your Customer Success Manager or contact our support in the [IXOPAY Customer Experience Portal](https://ixopay.my.site.com/support) if you have any questions.

## WorldlineOgone Connector Configuration

Configure the following parameters for the Connector (see Connector Config - WorldlineOgone):

1. Fill in the mandatory **API Secret**
2. Fill in the mandatory **Extra Data: SHAOUT** — Ogone Backoffice Parameter (see Ogone Backoffice - …; Configuration -> Technical Information -> Transaction feedback Under "Security for request parameters" -> "SHA-OUT pass phrase")
3. Fill in the mandatory **Extra Data: SHAIN** — Ogone Backoffice Parameter (see Ogone Backoffice - SHAIN)
4. Fill in the mandatory **Extra Data: SHAIN2** — Ogone Backoffice Parameter (see Ogone Backoffice - SHAIN)
5. Fill in the mandatory **Extra Data: Hashalgorithm** (lowercase and without dash, example: sha512) — Ogone Backoffice Parameter (see Ogone Backoffice - Hash)
6. Fill in the mandatory **Extra Data: PSPID** — Your PSP ID
7. Fill in the mandatory **Extra Data: PSWD** — API user password
8. Fill in the mandatory **Extra Data: USERID** — API user username
9. Fill in the mandatory **Extra Data: APIKey** — Ogone Backoffice Parameter (see Ogone Backoffice - API & Webhook)
10. Fill in the mandatory **Extra Data: WebhookKey** — Ogone Backoffice Parameter (see Ogone Backoffice - API & Webhook)
11. Fill in the mandatory **Extra Data: WebhookSecret** — Ogone Backoffice Parameter (see Ogone Backoffice - API & Webhook)

![Connector Config - WorldlineOgone](https://documentation.ixopay.com/manual/assets/ideal-img/connector-config-worldlineogone.28ee11b.1280.png)Connector Config - WorldlineOgone![Ogone Backoffice - SHAIN](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-shain.d6d1159.1080.png)Ogone Backoffice - SHAIN![Ogone Backoffice - Hash](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-hash.b345e70.908.png)Ogone Backoffice - Hash![Ogone Backoffice - API & Webhook](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-api-webhook.d632e08.1088.png)Ogone Backoffice - API & Webhook

### Ogone Backoffice Configurations

Configure the following settings in your Ogone Backoffice for the Connector to work properly:

#### Setup Postback URL

Configuration -> Technical Information -> Transaction feedback, configure:

1. HTTP request for status change select option **For each offline status change (payment, cancellation, etc.)** (see Ogone Backoffice - HTTP request for status change) and fill in the requested Postback URL
2. Direct HTTP server-to-server request select option **Always deferred (not immediately after the payment)** (see Ogone Backoffice - Direct HTTP server-to-server) and fill in the requested Postback URLs

#### Activate "Alias Manager" and "Refunds"

Configuration -> Account -> Your options, activate:

1. RECX - Alias Manager (see Ogone Backoffice - Alias Manager and Refunds)
2. RFD - Refunds (see Ogone Backoffice - Alias Manager and Refunds)

#### PAYIDSUB for Recurring Payments

Configuration -> Technical Information -> Transaction feedback, configure "PAYIDSUB" in Dynamic e-Commerce parameters for referenced Transactions:

1. Dynamic e-Commerce parameters add the parameter **PAYIDSUB** (see Ogone Backoffice - Dynamic e-Commerce parameters)

![Ogone Backoffice - HTTP request for status change](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-http-request-for-status-change.59ad0fb.1080.png)Ogone Backoffice - HTTP request for status change![Ogone Backoffice - Direct HTTP server-to-server](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-direct-http-server-to-server.22ff7db.1082.png)Ogone Backoffice - Direct HTTP server-to-server![Ogone Backoffice - Alias Manager and Refunds](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-alias-manager-and-refunds.83e1705.994.png)Ogone Backoffice - Alias Manager and Refunds![Ogone Backoffice - Dynamic e-Commerce parameters](https://documentation.ixopay.com/manual/assets/ideal-img/ogone-backoffice-dynamic-e-commerce-parameters.d52cc50.1084.png)Ogone Backoffice - Dynamic e-Commerce parameters

## Data Fetcher Configuration

You have the option to configure Data Fetchers (see section Enable and Set Up Reconciliation on the [Provider Level](https://documentation.ixopay.com/manual/docs/post-processing/provider)) either on Provider or on Connector Level, depending on which setup works better for your provider.

### Reconciliation

Configure the following Parameters for the Reconciliation Data Fetcher to fetch Reconciliation (xml format) via an SFTP (see Reconciliation Data Fetcher Provider Level):

1. Fill in the expected **Interval** in which the Reconciliation File should be fetched - days, hours
2. Select the Adapter **IngenicoPci, IngenicoConnectPci, IngenicoConnect or IngenicoXml**
3. Enable **Testmode** to fetch Reconciliation staging files (files starting with `wxt.` - only available if enabled from Igenico) from the SFTP Server, disabled production files (files starting with `wx1.`) are fetched from the SFTP Server
4. Fill in the mandatory **Extra Data: merchantId** (string) — Merchant ID provided by Ingenico required to retrieve the WX Report Files.
5. Fill in the mandatory **Extra Data: sftpUsername** (string) — SFTP Username required for the Authorization.
6. Fill in the mandatory **Extra Data: sftpPassword** (string) — SFTP Password required for the Authorization
7. Fill in the optional **Extra Data: sftpRootDirectory** (string) — Root folder on the SFTP Server where the WX report files are available
8. Select the optional **Extra Data: handleRejectsAsErrorsAndNotAsChargbacks** (boolean): true, false — to determine if a rejected transaction should be handled as chargeback or not

![Reconciliation Data Fetcher Provider Level](https://documentation.ixopay.com/manual/assets/ideal-img/reconciliation-data-fetcher-provider-level.ce060f1.806.png)Reconciliation Data Fetcher Provider Level

### Provider Settlement

Configure the following Parameters for the Settlements Provider Data Fetcher to fetch Settlement (xml format) via SFTP (see Edit Provider Settlement Data Fetcher Provider Level):

1. Fill in an optional **Name**
2. Fill in the expected **Interval** in which the Provider Settlement File should be fetched - days, hours
3. Select the Adapter **IngenicoConnectPci or IngenicoConnect**
4. Enable **Testmode** to fetch Provider Settlement staging files (files starting with `wxt.` - only available if enabled from Igenico) from the SFTP Server, disabled production files (files starting with `wx1.`) are fetched from the SFTP Server
5. Fill in the mandatory **Extra Data: sftpHost** (string) — SFTP Host name required for the Authorization
6. Fill in the mandatory **Extra Data: merchantId** (string) — Merchant ID provided by Ingenico required to retrieve the WX Report Files.
7. Fill in the mandatory **Extra Data: sftpUsername** (string) — SFTP Username required for the Authorization.
8. Fill in the mandatory **Extra Data: sftpPassword** (string) — SFTP Password required for the Authorization
9. Fill in the optional **Extra Data: sftpRootDirectory** (string) — Root folder on the SFTP Server where the WX report files are available
10. Fill in the optional **Extra Data: sftpPrivateKey** : (string) — SFTP private Key required for Authorization
11. Fill in the optional **Extra Data: sftpPassphrase** (string) — SFTP Passphrase required for Authorization

![Edit Provider Settlement Data Fetcher Provider Level](https://documentation.ixopay.com/manual/assets/ideal-img/edit-provider-settlement-data-fetcher-provider-level-ingenico.85e4a9e.992.png)Edit Provider Settlement Data Fetcher Provider Level

## WorldlineOgone Data Fetcher Configuration

### Provider Settlement

Configure the following Parameters for the Settlements Provider Data Fetcher to fetch Settlement (csv & xml format) via SFTP (see Edit Provider Settlement Data Fetcher Provider Level):

1. Fill in the optional **Name**
2. Fill in the expected **Interval** in which the Provider Settlement File should be fetched - days, hours
3. Select the Adapter **WorldlineOgone**
4. The Setting **Testmode** is irrelevant for this adapter
5. Fill in the mandatory **Extra Data: sftpHost** (string) - SFTP Server Host
6. Fill in the optional **Extra Data: sftpPort** (string)
7. Fill in the mandatory **Extra Data: sftpUsername** (string): SFTP Username required for the Authorization
8. Fill in the mandatory **Extra Data: sftpPassword** (string): SFTP Password required for the Authorization
9. Select the optional **Extra Data: rootDirectory** — The root directory to fetch from; required if not (`/`).
10. Fill in the optional **regexPattern:** To specify which files should be fetched

![Edit Provider Settlement Data Fetcher Provider Level](https://documentation.ixopay.com/manual/assets/ideal-img/edit-provider-settlement-data-fetcher-provider-level-ogone.7b132ed.986.png)Edit Provider Settlement Data Fetcher Provider Level

> **Info**
>
> In case Postfinance files and Twint files are not in the same directory/path you should set up two data fetchers.