- Mar 31, 2019
-
-
To use 'digital key' to add new recipient
-
choose digital key to add new recipient if it's activated t
-
- Mar 16, 2019
-
-
-
Romain Bignon authored
All copyright holders have given their consent.
-
- Feb 27, 2019
-
-
Romain Bignon authored
-
check only iban part of recipient id
-
-
recipient id can change, avoid to retrieve duplicate recipient to not search recipient by id in transfer and search by iban
-
- Feb 24, 2019
-
-
Romain Bignon authored
-
- Jan 23, 2019
-
-
- Jan 06, 2019
-
-
Romain Bignon authored
-
- Dec 21, 2018
-
-
- Dec 06, 2018
-
-
code 1001 "Une erreur est survenue, veuillez rafraîchir votre page" is more website unavailable than incorrect password
-
remove all 'webid' from budgea
-
-
-
- Dec 02, 2018
-
-
if it's empty, avoid check recipient_iban
-
set default value Decimal(0) for transfer fees
-
- Nov 30, 2018
-
-
- Nov 10, 2018
-
-
The account table is present when no account is present, we need to add condition to avoid research account in this case. Closes: 27858@sibi
-
Sometimes the request to the old website returns a Server Error (500) that crashes all BNP connections. With this try/except , the connection to the old website will fail but it will not prevent all the accounts from the new API to be scraped correctly. Closes: 7735@zendesk, 7863@zendesk, 27832@Sibi, 16333@Sibi, 27833@Sibi
-
The market accounts were not scraped yet, the BNP website seems to have changed recently. This patch enables scraping of the market accounts. The iter_investments method already worked as such, however the pagination is not yet handled. When there is only one account on the "invests" page, the checking and the market account are fused into one account, the market balance is not scraped, nor are the investments. This patch enables both accounts to be visible with their respective balances and the investments related to the market account. Closes: 6827@zendesk
-
wrongpass code 7 is "Vous ne pouvez pas encore vous connecter car votre code secret est en cours d'envoi" action needed code 50 is "Votre mot de passe temporaire a expiré. Veuillez effectuer une nouvelle demande." error code 207 is "Ce service est momentanément indisponible. Veuillez renouveler votre demande ultérieurement." Closes: 27655@sibi 27257@sibi 27481@sibi 27483@sibi 27478@sibi
-
-
-
-
- Oct 22, 2018
-
-
Romain Bignon authored
-
Romain Bignon authored
For an incorrect authentication, the returned message is: "Erreur lors de l'authentification Code retour : 201" The related message in localized file is: "Votre saisie est incorrecte.<br>Veuillez renouveler votre identification."
-
-
- Oct 11, 2018
-
-
When we face an error at login, bnp gives us a code. This code's signification is explained on at documentation page. This commit gets the message directly from the website.
-
bnp now ask the new password to be different from the past 2.
-
- Oct 09, 2018
-
-
Do not use AddRecipientError for user error anymore Use AddRecipientBankError instead and use 'assert' for program error case
-
- Sep 17, 2018
-
-
Romain Bignon authored
This reverts commit f65830ba.
-
- Introduce more swear words to represent the diversity of the English language - Upgrade outdated insults - Only wish harm on objects (though webdevs barely qualify as human)
-
- Sep 16, 2018
-
-
- Aug 22, 2018
-
-
For some reason the pages.py file contained tabs instead of spaces, I replaced all the concerned lines and re-tested with BNP connections to verify that everything works and that the file passes the pyflakes3 test.
-
- Aug 18, 2018
-
-
The BNP module did not scrape the "Assurance Vie" space yet, which may contain additional accounts that are not included in their API. Among those we can find Life Insurance, Capitalisation contracts and PERP accounts, and maybe more. I also implemented the iter_investments() method for this space, however the domain does not seem to display any kind of transaction history for these accounts. Closes: 5016@zendesk
-
- import unicode_literals in each Python module - import weboob's basestring compat - xrange -> range - tested on 90 connections, 1 for each API
-
- Jul 29, 2018
-
-
Closes: 9334@sibi
-
A recurring problem with bnporc is that sometimes you may not have the good transactions list. It may be truncated a lot. For example, from 50 transactions, you had only 5. Because of that, in the backend some transactions become deleted because of one update with the bad transactions. I tried to fix it by copying the website, since you never had bad transactions on it. First, I changed the 'typeReleve' from 'Comptable' to 'Previsionnel' because it is the only type the website is using. And I added some parameters to the history request. The same ones are used to go on the transaction page and to get the json data. I tested a lot on connections, knowing the right and the wrong history state. Since I applied the patch, I had not once the wrong state. Closes: 5663@zendesk Closes: 6219@zendesk Closes: 6225@zendesk Closes: 6229@zendesk Closes: 6115@zendesk
-