- May 22, 2020
-
-
It would be more flexible (ex for "Personne Morale (hors SP)". Moreover "Personne Protégé" is added to the list.
-
If the login starts with a lowercase character, banquepopulaire returns value for private user (part) by default.
-
-
-
Works as well on connections where almost no information on parent account is available.
-
Deferred debit card are now exported as separate accounts, and the deferred debit transactions are on those accounts, not on the checking account anymore.
-
New subwebistes don't need phase 1 param anymore. We think more subwebistes would have this behaviour so we decide to try the login twice without and with phase param.
-
Sometimes the _bic of the emitter account in the iter_accounts. This can be fixed by getting the bic of the emitter accounts at the same time we get the ciphered contract number and ciphered iban.
-
"Phase" bpcesta params in authorize url is not necessary anymore for "part" bpaca user. But for the other cases the param is still required. The phase information seems to be in js file and the value is not hardcoded. That's why we must be vigilant if other subwebsites migrate to this version. Moreover in bpaca the good user status is required. We can get the information in as-ex-ano-groupe.banquepopulaire.fr API.
-
-
-
Sometimes we have the unitvalue as a ratio of the unitprice instead of an absolute value, we don't want to fetch it. The unit value of invests is given in the original currency. All other values are in euro.
-
-
-
This URL wasn't handled so the action needed was not always raised.
-
-
CloudCard (aka Secur'Pass) is a method that asks for an AppValidation when adding new recipients or making transfer when not on the Caisse d'Epargne application.
-
I don't know why this param was passed everytime, it absolutely does not change anything to the responses. Also corrected the use of sorted_transactions: it is enough to sort them per JSON instead of sorting them altogether. The JSONs are correctly dates between each other.
-
-
-
-
The iter_history was only returning the last month of history whereas 3 months are available in the JSON. Besides, there was no 'dayfirst=True' so all the dates were completely wrong.
-
-
Less granularity but job overhead is paid less times.
-
-
On some websites we observe 3 dates: validity_date, creation date and execution date. The 'date' attribute is set to the creation_date since all market orders have one, whereas some market orders (that are still ongoing, or that have been refused or cancelled) have no execution_date, and the date is often used to sort the orders chronologically.
-
- May 10, 2020
-
-
- May 08, 2020
-
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
- May 07, 2020
-
-
-
-
This was rejected: [ (a), ] because last token of last element is "a", not ")". So we have to skip closing parentheses before reaching the trailing comma. Also, simply use "generic_visit" instead of calling "visit" on sub nodes ourselves.
-
-
-
-
-
-