Thomas Toumeyragues authored Jan 19, 2023 and Maxime Gasselin committed Jan 27, 2023

Some connections on creditdunord and its childs have this
systematic error of 'mauvais_contrat'. There is not much
information given by the bank about this error.

Thomas Toumeyragues authored Oct 06, 2022 and Maxime Gasselin committed Jan 27, 2023

CustomId should be used to access history pages.
Accessing history pages with Id instead of customId
worked so far with most accounts as their customId is
equal to their Id.
But for Loan accounts and Loan-like accounts (as
Mortgage for example) Id is different from
their customId. For those accounts using Id causes
an error, while customId works.

This change has also been applied to access
investment page, for consistency. It has no
effect as for wealth accounts Id equals
customId

jlouvel authored Jun 24, 2022 and ntome committed Jul 04, 2022

Reason 'acces_bloq' given in the JSON after posting the credentials
wasn't handled. For pro accounts, the website asks the user to contact
his bank advisor or the website hotline. For par accounts, the user can
reset his password directly from the website.
It seems to happen especially on accounts where the users were asked to
change their password some time ago but never actually did it because their
connections are in wrongpass or bug since then.

Damien Ramelet authored Apr 14, 2022 and ntome committed Apr 29, 2022

Raising BrowserIncorrectPassword was to permissive, ensure
it's now raised in the rights cases and handle possible
unknown cases

Damien Ramelet authored Jan 24, 2022 and ntome committed Jan 26, 2022

creditdunord api sometimes return truncated JSON which will make
the module crash. Retrying the request at that point is doing the job

David Horozian authored Dec 28, 2021 and ntome committed Jan 26, 2022

An alert asking the user to fill-in their e-mail can sometimes
appear on the website, preventing the user from accessing their
accounts. This bypasses the alert.

Differentiate pri and pro accounts and get more info when available:
email, first and last name.

"statut" codes we get from the server are sometimes in uppercase.
So, always compare with case insensitivity to be safe.

Sometimes on login we can be redirected on a technical error page

Damien Ramelet authored Sep 10, 2021 and hydrargyrum committed Sep 23, 2021

While consulting history of an account, the API can
encounter some temporary technical issue

Damien Mat Jedrzejewski authored Jul 30, 2021 and hydrargyrum committed Aug 13, 2021

Some connections have two accounts with the
exact same attributes in the json.

Damien Ramelet authored Jul 23, 2021 and hydrargyrum committed Aug 13, 2021

When the 2FA come close to expiring, creditdunord allow user to redo the
2FA earlier, skipping it.

Damien Mat Jedrzejewski authored Mar 03, 2021 and hydrargyrum committed Mar 12, 2021

Some accounts don't have a 'libelleBanque',
those are to be avoided.

Damien Mat Jedrzejewski authored Mar 03, 2021 and hydrargyrum committed Mar 12, 2021

IbanPage is not available if transfers are not authorized.
We now control its status before trying
to parse IBAN on it.

Damien Mat Jedrzejewski authored Feb 10, 2021 and hydrargyrum committed Mar 12, 2021

First use of this capability in a module.
It allows to match accounts fetched in a new version
of the module, with their previous incarnation a the database,
thanks to the match_account method.

In this case, all ids, labels,
and a few types and numbers have changed.

Christophe François authored Feb 04, 2021 and hydrargyrum committed Mar 12, 2021

There was an issue in the iter_accounts of kolb, a child of this
connector, due to some pages now loading with javascript which broke the
navigation.

Instead of adding messy ways of working around the issue in an already
messy connector I remade it using the much cleaner new JSON pages of the
"Synthèse Multibanque" space.

However, there is no way to get the same IDs as the old version and
accounts fetched with this new version don't match the old ones.