Christophe François authored Apr 08, 2021 and hydrargyrum committed Apr 26, 2021

All values are in the account's currency except for unitvalue which can
be in its original currency.

Damien authored Apr 06, 2021 and hydrargyrum committed Apr 26, 2021

Setup right column for balance for loan revolving, we want to display
the used amount, which is the amount that need to be refund.
Total amount for loan revolving match the max amount authorized by the
bank.
For this kind of loans, LCL doesn't display any rate, handle this case.

nvergnac authored Mar 17, 2021 and hydrargyrum committed Apr 08, 2021

-Change klass in LoanPage : Account > Loan

-Add the following Loan obj_ when available :
  - name
  - total_amount
  - account_label
  - rate
  - maturity_date
  - next_payment_amount
  - next_payment_date

Damien Mat Jedrzejewski authored Mar 16, 2021 and hydrargyrum committed Mar 24, 2021

iter_market_orders were implemented on parent,
but they don't exist on LCLParcCardsBrowser
and LCLEnterpriseBrowser sub-browsers.

Damien Mat Jedrzejewski authored Jan 04, 2021 and hydrargyrum committed Jan 09, 2021

Error 500 when searching detail of a 'Compte à terme',
as on the website.
Now raises a BrowserUnavailable.

Florent Viard authored Dec 18, 2020 and hydrargyrum committed Jan 09, 2021

When requesting to send the otp code to the user, the server can
sometimes reply with a "authentsimple", that means that an otp is not
needed anymore and will can just continue directly.

Florent Viard authored Dec 18, 2020 and hydrargyrum committed Jan 09, 2021

Example of raised message:
"Nous ne pouvons pas réaliser cette opération en ligne. Merci de
contacter votre conseiller."

Florent Viard authored Dec 01, 2020 and hydrargyrum committed Dec 07, 2020

Some recipients ibans cannot be found anymore on the website.
But since we kept the iban stored on our side, the 'old'
transfer.recipient_iban is not empty when making a transfer.

For example, this could be the case for internal accounts like "Livret
A".
In such a case, there encountered exception was like:

AssertionError: recipient_iban changed during transfer processing (from
"FR01234XXXXXXXXXXXXXXX42" to "NotAvailable")

Closes: 168427@sibi

Julien Montagnat authored Oct 26, 2020 and hydrargyrum committed Nov 17, 2020

The LCLBrowser is now a TwoFactorBrowser, the initialization
is different from other LCL browsers ("ent")

Guillaume Risbourg authored Oct 02, 2020 and hydrargyrum committed Oct 07, 2020

Some accounts' ibans cannot be found anymore on the website. But since we
kept the iban stored on our side, the 'old' transfer.account_iban is not
empty when making a transfer. When we do not find the account based on its iban,
we search it based on its id. So the account is valid, the iban is just different.
This check allows to not have an assertion error when making a transfer from
an account in this situation.

Damien Mat Jedrzejewski authored Sep 02, 2020 and hydrargyrum committed Sep 23, 2020

When amount is not found by the first parsing,
it must be done by a second one.
I changed the condition on which this is triggered,
since it not needed anymore,
and would throw an AttributeError when page is parsed a second time.

Christophe François authored Aug 31, 2020 and hydrargyrum committed Sep 09, 2020

Quantity and validity date are not always available.

Yoann Guillard authored Jul 15, 2020 and hydrargyrum committed Aug 07, 2020

Some users are unauthorized to access life insurance.
This was raising an error cause the redirection to
the main website was not handled.

ntome authored Jul 20, 2020 and hydrargyrum committed Aug 07, 2020

open_transaction_page returns None for those transactions, we don't open the
"related page".

Yoann Guillard authored Jul 09, 2020 and hydrargyrum committed Aug 07, 2020

Sometimes, for professional accounts, the balance was the sum of
transactions of last x (47) days. I added a new method get_balance.
Maybe the previous should be removed. I put a backtrace to check it.

ntome authored Jul 13, 2020 and hydrargyrum committed Aug 07, 2020

For each checking account transaction, we tried to open the transaction
dedicated page to fetch details.
Unfortunately, on some accounts, none of the transaction details page work,
we get a page telling the user is not allowed to see that info. For example,
this can happen on a professional account while the user is a private one.
They can see the list of transaction but not the full details.

We now keep the behavior but if we encountered too many failures (5) on those
details, we stop trying to go to the details.

Obnoxious validate() code is moved to a more appropriate place.

jnifenecker authored Jun 22, 2020 and ntome committed Jul 02, 2020

The ELCLBrowser's subdomain is no longuer used and is now equivalent of LCLBrowser.
Only the login page still function (to not mess with end-user habits I guess)
but is not needed anymore.

Guillaume Risbourg authored Jun 04, 2020 and hydrargyrum committed Jun 17, 2020

The new error is : Un numéro de téléphone enregistré est nécessaire afin
de vous envoyer un code de validation.
This wasn't handled by the previous `get_error` because it searched for
`code de connexion`.

Guillaume Risbourg authored May 19, 2020 and hydrargyrum committed Jun 03, 2020

After validating the sms to confirm the new recipient,
the website can display an error.

Closes: 64209@sibi

Guillaume Risbourg authored Apr 10, 2020 and hydrargyrum committed Apr 22, 2020

The new error requires the user to have a phone number to validate the
recipient:
Aucun Téléphone
Un numéro de téléphone enregistré est nécessaire afin de vous envoyer un code de connexion.
Nous vous invitons à vous rendre à votre agence ou appeler le 09 69 36 30 30.