Version 4.0.36

Changes related to version 4.0.35.

Connectors improvements

• IT
  • Cedacri: payment status returned by PUT payments or GET status is including the debtor name.
  • Banco Posta Corporate (Affari) (1198), Banco Posta private (Online) (1199), BPER Business (1200), BPER (1201), Credit Agricole Cariparma business (1202), Credit Agricole Cariparma (1203), Credit Agricole FriulAdria business (1204), Credit Agricole FriulAdria (1205), Credito Emiliano Business (1206), Credito Emiliano (1207), Credito Valtellinese Spa (1208), Banca Nacional del Lavoro (1236), Hello Bank (1237), BNL Corporate (1238), Banco di Sardegna S.p.A. (1601), Banco BPM (2032), Webank (2033), Isybank S.P.A. (2034), Banca WIDIBA Spa (2035), Intesa Sanpaolo S.P.A. (2047), Banca Fideuram S.P.A. (2048), Intesa Sanpaolo Private Banking S.P.A. (2049), Banco Posta Business (Link) (2089), Banca Popolare Di Sondrio Conto Corrente (2225), Banca Popolare Di Sondrio Carta Iban (2226):
    Send creditor/recipient's bank BIC to debtor bank if supplied.
• BE, GB, NL Triodos: sending the remittance information unstructured to the bank.
• BE
  • Belfius: fix the balance amount taken as the ITBD. Targeting account with multiple currency.
  • KBC: improvement for internal token refresh
• GB Revolut: fix for bank API upgrade.
• AT Erste bank:
  • AIS access option moved from Customizable (0) to Detailed (3).
  • The bank is raising an error during payment creation when the PSU doesn't have a default account set. We catch this error and return a PropertyError with the message "When the PSU has multiple accounts, the debtor.Iban should be supplied." In this case, you must ask for the IBAN, add it to your payment model and init a new payment with this model. We will reuse the token if the PSU if it is still valid.
• ES
  • Selfbank: enabling instant SEPA payments.
  • Caixabank: fix for get transactions pagination.
• FR
  • Banque Populaire Grand Ouest / CMM Grand Ouest (1115), Banque Populaire Bourgogne Franche Comté (1116), Banque Populaire Auvergne et Rhône-Alpes (1117), Banque Populaire Rives de Paris + BICS (1118), Banque Populaire Val de France (1119), Banque Populaire du Nord (1120), Banque Populaire Sud (1121), Banque Populaire Aquitaine Centre Atlantique / CMM Littoral du Sud Ouest (1122), Banque Populaire Alsace Lorraine Champagne (1123), Banque Populaire Occitane (1124), Banque Populaire Méditerranée (1125), Banque de Savoie (1126), Banque BCP (1128), BTP Banque (1129), Banque Palatine (1130), Caisse d'Epargne Ile De France (1131), Caisse d'Epargne Provence Alpes Corse (1132), Caisse d'Epargne Normandie (1133), Caisse d'Epargne Bourgogne Franche-Comté (1134), Caisse d'Epargne Bretagne-Pays De Loire (1135), Caisse d'Epargne Midi-Pyrénées (1136), Caisse d'Epargne Aquitaine Poitou-Charentes (1137), Caisse d'Epargne Languedoc-Roussillon (1138), Caisse d'Epargne Rhône Alpes (1139), Caisse d'Epargne Loire Drôme Ardèche (1140), Caisse d'Epargne Loire-Centre (1141), Caisse d'Epargne Côte d'Azur (1142), Caisse d'Epargne Auvergne et Limousin (1143), Caisse d'Epargne Grand Est Europe (1144), Caisse d'Epargne Hauts de France (1145), Crédit Coopératif (1146), Natixis Global Trade (1147), Natixis Wealth Management (1148)
    Connecting a new account was dropping the consent of th previously connected ones. AIS linking option moved from separate (1) to linked (0), you have to provide the list of accounts you already have consent for with the list of new accounts you want to connect. Handled automatically by SkyBridge/Gateway.
  • Crédit Mutuel and CIC: update of authorization URL (internal).
• NL ABN Amro: added bulk payment.
• DE Voksbank banks: added instant SEPA payment.
• SE ICA: fixed payment scope.

Using key vault in Docker (TPP only)

Find this in the doc Docker configuration .

To enforce privacy and security, we have added the possibility to get data from an Azure key vault instead of having to store them in the Docker's configuration.

To use it, the TPP has to add new "settingsConnectionStrings" section at the root of the config.json file. Inside there may be placed multiple connections string with the following format: "<vaultType>;<vaultURL>". Example:

{
	"settingsConnectionStrings": {
  	"connection1": "<vaultType>;<vaultURL>",
  	"connection2": "<vaultType>;<vaultURL>"
	}
}

Currently the only supported vaultType is "AzureKeyVault".

To use an object from your vault, use following format "$<connectionName>;<keyVaultPropertyName>".

Example:

{
  "defaultBankSettings": {  
  	"ncaId": "$connection1;ncaId",
  	"appClientId": "$connection1;appClientId",
  	"appClientSecret": "$connection1;appClientSecret",
  	"tlsCertificateName": "$connection2;tlsCertificateName",
  	"tlsCertificatePassword": "$connection2;tlsCertificatePassword",
  	"signingCertificateName": "$connection2;signingCertificateName",
  	"signingCertificatePassword": "$connection2;signingCertificatePassword"
	}
}

You can also use it the same way to fetch full setting object, by sending the same format in "bankSettingsCode" in the request model. That will try to get JSON object with all the necessary objects from your key vault.

E.g., in the model you sent in the request, model.bankSettingsCode is equal to "$connection2;settings-BE-BNP" and in your "$connection2" vault, you have define an object "settings-BE-BNP" with the JSON string value '{ "ncaid": "XYZ", "appClientId": "123"... }'

"bankSettingsCode" with simple value can also be used to get pre-set setting values from the config.jon file.

E.g., in the model you sent in the request, model.bankSettingsCode is equal to "settings-BE-BNP" and in your config.json, you define:

{
  ...
  "settings-BE-BNP": {
    "ncaId": "$connection1;ncaId",
  	"appClientId": "$connection1;appClientId",
  	"appClientSecret": "$connection1;appClientSecret",
  	"tlsCertificateName": "$connection2;tlsCertificateName",
  	"tlsCertificatePassword": "$connection2;tlsCertificatePassword",
  	"signingCertificateName": "$connection2;signingCertificateName",
  	"signingCertificatePassword": "$connection2;signingCertificatePassword"
  }
  ...
}