Worldpay

WorldPay

Depending on the chosen method the a subset of the following parameters for the Connector need to be configured (see Connector Config - WorldPay I & II):

1. Fill in the mandatory WorldPay Merchant Code
2. Fill in the mandatory Password
3. Fill in the mandatory API Username
4. Fill in the mandatory API Password

Additional Extra Data is available to be configured:

1. Fill in the optional Extra Data: currencyForRegister
2. Fill in the mandatory Extra Data: recurringMerchantCode
3. Fill in the mandatory Extra Data: forwardBillingDetails: True, False
4. Fill in the optional Extra Data: forwardShippingDetails: True, False
5. Fill in the optional Extra Data: useStoredCredentials: True, False
6. Fill in the optional Extra Data: useTokenization: True, False
7. Fill in the optional Extra Data: receiverCurrency
8. Fill in the optional Extra Data: chargeback911Secret - optional; Secret key is related to the Authentication to accept webhook notifications from Chargeback911 with header CB911_SIG, value to be hash_hmac with sha256 of the timestamp and the secret key (for mapping see Chargeback911 Webhooks)-

Connector Config - WorldPay IConnector Config - WorldPay II

Keep in mind that for PCI compliant Adapters you need to connect with the PCI environment and the PCI Vault Configuration is shown.

WorldPay Creditcard

Depending on the chosen Interface Type a subset of the following parameters for the Connector need to be configured (see PCI Vault Configuration - Creditcard WorldPay I, II & III):

1. Select the mandatory Environment : Live, Test, Production
2. Fill in the mandatory Username
3. Fill in the mandatory Password
4. Fill in the mandatory Merchant Entity
5. Fill in the optional Merchant Category Code
6. Fill in the optional Shared Secret for Notifications
7. Fill in the mandatory AccountID
8. Fill in the mandatory AccountToken
9. Fill in the mandatory AcceptorID
10. Fill in the mandatory TerminalID
11. Fill in the mandatory ApplicationName
12. Select the mandatory Currency
13. Select the mandatory Market Code
14. Check the option Enable Incremental Authorizations
15. Fill in the mandatory Merchant Code
16. Fill in the mandatory XML Username
17. Fill in the mandatory XML Password
18. Select an optional Amount for card verification
19. Select the optional Debit waits for webhook
20. Check the Option Do not send 3DS 2.x dsTransactionId for Visa

PCI Vault Configuration - Creditcard WorldPay IPCI Vault Configuration - Creditcard WorldPay IIPCI Vault Configuration - Creditcard WorldPay III

Data Fetcher Configuration

You have the option to configure Data Fetchers (see section Enable and Set Up Reconciliation on the Provider Level) either on Provider or on Connector Level, depending on which setup works better for your provider (see Edit Provider).

Edit Provider

Provider Settlement

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

1. Fill in the expected Interval in which the Provider Settlement File should be fetched - days, hours
2. Select the Adapter WorldPay
3. Enable Testmode - irrelevant for this adapter
4. Fill in the mandatory Extra Data: sftpUser used for authentication
5. Fill in the mandatory Extra Data: private Key used for authentication
6. Fill in the mandatory Extra Data: regex used to specify file pattern

Edit Provider Settlement Data Fetcher Provider Level

Settlement fields

Batch Number

The batch number is taken from the value of the column “Batch ID”.

Mapped Fields

We are mapping the following fields from the Worldpay settlement reports (Provider → IXOPAY platform):

Mapped status values

Chargeback911 Webhooks

A chargeback is only created when the IXOPAY platform receives a webhook with status New , a chargeback reversal is only created when the verdict = Win is received (see https://apidoc.chargebacks911.com/documentation#tag/Webhooks/paths/~1webhooks/post)

Chargeback

Chargeback Reversal