Multisafepay

Configuration specifics

Configure the following parameters for the Connector (see Connector Configuration):

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: migrationUuidPrefix
5. Select the mandatory Extra Data: useDirectType: True, False (select True in case you do not want to use SEPA Direct Debit with redirect)

Connector Configuration

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

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.

Reconciliation

Configure the following Parameters for the Reconciliation Data Fetcher to fetch reconciliations (json format) by calling the transactions endpoint /transactions (see Reconciliation Data Fetcher Provider Level):

1. Fill in the optional Name
2. Fill in the expected Interval in which the Reconciliation File should be fetched - days, hours
3. Select the Adapter MultiSafepay, MultiSafepayPci
4. Enable Testmode — to fetch reconciliations from the test endpoint (https://api.multisafepay.com/v1/json) instead of the production endpoint (https://testapi.multisafepay.com/v1/json)
5. Fill in the mandatory Extra Data: apiKey — required for the settlement and reconciliation calls

Reconciliation Data Fetcher Provider Level

Provider Settlement

Configure the following Parameters for the Settlements Provider Data Fetcher to fetch settlements (json format) by calling the transactions endpoint /transactions (see Edit Provider Settlement Data Fetcher Provider Level):

1. Fill in the optional Name
2. Fill in the expected Interval in which the Reconciliation File should be fetched - days, hours
3. Select the Adapter MultiSafepay, MultiSafepayPci
4. Enable Testmode - to fetch settlements from the test endpoint (https://api.multisafepay.com/v1/json) instead of the production endpoint (https://testapi.multisafepay.com/v1/json)
5. Fill in the mandatory Extra Data: apiKey — required for the settlement and reconciliation calls

Edit Provider Settlement Data Fetcher Provider Level