Skip to main content

Six / PAYONE

Configure the following parameters for the Connector (see Connector Detail Overview - Six Elink Creditcard - Vault Configuration):

  1. Select the mandatory Target Environment: Staging, Production
  2. Fill in the mandatory Acquiring Institution Code: SIX Payment Services Europe, SIX Payment Services Switzerland, SIX Payment Services Austria
  3. Fill in the mandatory Merchant ID
  4. Fill in the mandatory Terminal IDs
  5. Enable the option Allow dynamic descriptor
  6. Enable the option Process all DINERs recurring transactions as MOTO Transactions
  7. Enable the option Process all DINERs cof transactions as ECommerce Transactions
  8. Enable the option Ignore Exemptions on Diners Cards
  9. Enable the option Marketplace MID
  10. Fill in the parameters for the Card Acceptor Name and Location
  11. Fill in the mandatory Name — 1-25 characters
  12. Fill in the mandatory City — 1-13 characters
  13. Fill in the mandatory Country Code — two-character, uppercase, alphabetic string (ISO 3166-1 alpha-2 code)
  14. Fill in the mandatory Street — 1-48 characters
  15. Fill in the mandatory Postal Code — 1-10 characters
  16. Add CCTI-IDs (Override defaults) to
  17. Fill in the Default Capture Reference

Six Push

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

  1. Fill in the mandatory Username
  2. Fill in the mandatory Password
  3. Fill in the mandatory API Secret

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.

Provider Settlement

Configure the following Parameters for the Settlements Provider Data Fetcher to fetch Settlement (xml file with default filename regex is: /\.EVP\.MRXD/) via SFTP (ftservice.six-group.com) (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 Six
  4. The Setting Testmode is irrelevant for this adapter
  5. Fill in the mandatory Extra Data: sftpUsername: used for authentication
  6. Fill in the mandatory Extra Data: sftpHost: specify the Host used for fetching documents
  7. Fill in the mandatory Extra Data: rootDirectory: specify the root directory for the files to be fetched
  8. Fill in the optional Extra Data: fileNameRegex: specify the naming convention of the files to be fetched
  9. Fill in the optional Extra Data: sftpPrivateKey: used for authentication
  10. Fill in the Extra Data: privateKeyPassword: used for authentication
  11. Select the optional Extra Data: returnAddMercDataInTransactionId — True, False
  12. Select the optional Extra Data: sumTransactionsWithoutId — True, False

Settlement fields

The extSettlingRefNo and the paymentNo are set as settlement number depending on the availability of this field. Some countries like Austria provide only paymentNo. The priority is extSettlingRefNo -> paymentNo -> now as Ymd.

Batch Number

The batch number is populated with the filename. It is expected to include a timestamp.

Payment Reference

The payment reference is taken from the parameter paymentNo.

Mapped Fields

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

ProviderIXOPAY platformdefault (if not set by Provider)
arnSettlement arnNone
aTrxOCTransaction settlement currencyNone - required
aTrxNetSCNet settlement amountNone
aTrxOC ‘c’Settlement currencyNone
xRateExchange RateNone
panLast 4 digits - Return dataNone
aComEffExclVatSCTransaction fee amountNone
aComEffExclVatSC ‘c’Transaction fee currencyNone
condCode = 1Fee type MarkupNone
condCode = 15Fee type interchangeNone
condCode = 35Fee type SchemeNone
condCode = 38Fee type SchemeNone
condCode = 103Fee type interchangeNone
condCode = 200, 221, 600Fee type markupNone
Payment DateSettlement dateNow
paymentNoSettlement numberNone
extSettlingRefNoSettlement numberNow as Ymd
addlMercDataSettlement transaction idNone

PAYONE Creditcard

Configure the following parameters for the Connector (see Connector Detail Overview - PAYONE Creditcard - Vault Configuration):

  1. Select the mandatory Target Environment: Dev, Quality, Production
  2. Select the mandatory option Route via ISONAC
  3. Fill in the mandatory Merchant ID provided by PAYONE
  4. Fill in the mandatory Terminal IDs (see also Terminal Setup)
  5. Fill in the mandatory Card Acceptor Name and Location
    1. Name
    2. City
    3. Country Code (2-character)
  6. Fill in the optional CCTI-IDs (Override defaults)
  7. Fill in the optional Default Capture Reference