News

BPE becomes Louvre Banque Privée - Technical update needed

13th September, 2023

BPE becomes Louvre Banque Privée, consequently the domain name evolves as well as the associated API's.

These changes will be effective from September 13th, 2023. If you use the BPE APIs, please make the following updates :

Current URLs :

  • BPE : https://api-openbanking.bpe.fr
  • BPE sandbox : https://api-sandbox.bpe.fr

Target URLs :

  • Louvre Banque Privée : https://api-openbanking.louvrebanqueprivee.fr
  • Louvre Banque Privée sandbox : https://api-sandbox.louvrebanqueprivee.fr

The BPE URLs will remain functional for 3 months from today until the BPE domain is closed.

News about this developer portal

11th September, 2023

From today, it is no longer possible to create devapps from this developer portal. 

You will have to use our new developer portal GetArkea.

As a reminder, this devportal will be definitely closed on November 22th, 2023.

Technical update on 17th and 24th September, 2023

28th August 5th September, 2023

For reasons of upgrading our databases, authentication will be unavailable on 17th and 24th september, 2023 from 8 am to 9 am.

This concerns both our websites and mobile apps.

This database upgrade will also make our PSD2 payment API unavailable.

Thanks in advance for your understanding. Feel free to contact us if you have any question.

Our new developer portal has arrived

22nd August, 2023

We hope you enjoy using our developer portal. We are pleased to announce the launch of a brand new distribution site for our APIs, offering you an even more pleasant and intuitive user experience. 

Find out more about our new API portal GetArkea.

We sent you an email today to explain how to proceed to use this new portal.

 

From September 11th, 2023, it will no longer be allowed to create devapps from this devportal. You will have to use our new portal GetArkea.

Within 3 months, this devportal will no longer be accessible.

PSD2 authentication unavailable August 13th, 2023

08th August, 2023

For reasons of maintenance on one of our services, DSP2 authentication will be unavailable on 13/08/2023 from 6am to 7am.

Thanks in advance for your understanding.

Technical update on September 10th, 2023

13th July, 2023

An important technical update improving our infrastructures is scheduled for September 10th, 2023.

It will involve the unavailability of some of our services from 6:10 a.m. to 7:30 a.m. :

Unavailability of Instant Payment,
Unavailability of the Fortuneo web site and mobile application,
Unavailability of PRO and PART sites and mobile applications (CMB, CMSO, ABEI, ABS, ABP, LBP, AZB, AXA).

CMB and CMSO authentication unavailable during a few minutes on July 9th, 2023

15th June, 2023

For reasons of maintenance of our databases servers, authentication will be unavailable on both mobile and web sites for CMB and CMSO on July 9th, 2023 for a maximum period of 15 minutes between 8 a.m. and 9 a.m...

Thanks in advance for your understanding.

Payment API and authentication unavailable during a few minutes on June 18th, 2023

15th June, 2023

For reasons of maintenance of our databases servers, our payment API will be unavailable on June 18, 2023 for a maximum period of 15 minutes between 8 a.m. and 9 a.m..

For the same reason, authentication will be unavailable on both mobile and web sites for CMB and CMSO on June 18th, 2023 for a maximum period of 15 minutes between 8 a.m. and 9 a.m...

 

Thanks in advance for your understanding.

Information on the SCA deadline

25th April, 2023

For your information :

Currently a strong authentication is required every 90 days for the customer to agree to the continuity of service. On July 25, 2023, this period will be 180 days. I can confirm that there will be no impact on your level and no break in service.

Technical incident online banking service

29th March, 2023

An incident is currently in progress on the online banking service of Arkéa entities. You will be kept informed of its resolution.

The incident is resolved and the Remote Banking service is restored.

Modification of the Sandbox URL

7th March, 2023

We made some url modifications for our sandbox part in the "Step1 - Retrieve the authorization code" section.

https://api.arkea.com/psd2-psu-sandbox/authorize...

becomes

https://api-public.arkea.com/psd2-psu-sandbox/authorize...

AIS / PIS course not possible at Axa Bank

15th February, 2023

We are facing an unavailability on Axa Bank on the AIS / PIS routes. We are doing our best to restore the service.

Incidents references : TCK3693428/TCK3719156

Affected client : Axa Banque

Incident start date/time : 15/02/2022 - 15h30
Incident end date/time : -

Description / Impact(s):
AIS / PIS course not possible at Axa Bank

=> issue solved on 17-02-2023 17:52

Aumax Pour Moi : All good things come to an end

20th December, 2022 16th January, 2023

Services of "Aumax Pour Moi" will shut down on January 22nd  at midnight 25th at 08:30.

Be aware that APIs will not be available anymore at the same time.

Aumax Pour Moi PSD2 Certificate

20th December, 2022

Due to a technical anomaly, we are forced to switch eiDAS certificates to non-eiDAS X509 certificates.

If you control the type of certificate during your MTLS calls, you may be impacted. We therefore recommend you to apply a standard X509 check and to disable the eiDAS checks.

We are aware of the inconvenience this may cause you given the short notice, and we apologize for it.

Technical incident online banking service

07th Decembre, 2022

An incident is currently in progress on the online banking service of Arkéa entities except Fortunéo. You will be kept informed of its resolution.

The incident is resolved and the Remote Banking service is restored.

Technical delivery on 12th of December 2022

06th Decembre, 2022

On 12th of December 2022, a technical delivery concerning our QTSP's repository will take place at noon. A very brief unavailability of our services (APIs and Fallback interface) might be observed for our banks.

The 1.4.1 version decommissioning

05th Septembre, 2022
 

The 1.4.1 version is decommissioned, the 1.4.2 is the default one means that you do not have to specify it in your request.

New version - July 2022

13th July, 2022

We are pleased to inform you that in 13 July 2022, this new release does not involve any non-backward-compatible change.

PISP - You can now  initiate currency transfers in the SEPA zone and outside the SEPA zone (any currency) for a TPP on the 1.4.2.18 version

  • International (Domestic payments in non-euro currency
  • International payments
  • International Scheduled (with requestedExecutionDate) are also allowed

International Payments are allowed  on the following entities :

 

Crédit Mutuel de Bretagne,
CMSO, ABP, ABEI, BPE, ABS, AXA Banque

The default version : 1.4.2

16th February, 2022
We are pleased to inform you that in 06 June 2022, the default version becomes the 1.4.2. Means that if you do not specify that you want to use the 1.4.1 version, your requests will be treated with 1.4.2 format.
In 05 September 2022, the 1.4.1 version will be decommissionned .

Arkea PSD2 certificates

09th September, 2021

Due to a technical anomaly, we are forced to temporarily switch eiDAS certificates to non-eiDAS X509 certificates.

Depending on the services concerned, the deadlines requiring a change are as follows:

https://api-openbanking.arkea-banque-ei.com: 2021-09-10 13:00

https://api-openbanking.arkeabanqueprivee.fr: 2021-09-10 13:00

https://api-openbanking.arkea-banking-services.com: 2021-09-10 13:00

https://api-openbanking.bpe.fr 2021-09-10: 13:00

https://api-openbanking.fortuneo.com 2021-09-16: 13:00

https://api-openbanking.cmb.fr 2021-09-16: 13:00

https://api-openbanking.cmso.com 2021-09-16: 13:00

If you control the type of certificate during your MTLS calls, you may be impacted. We therefore recommend that you apply a standard X509 check and deactivate the eiDAS checks.

The time to return to a normal situation allowing the use of eiDAS certificates is at least 3 weeks.

We are aware of the inconvenience this may cause you given the short notice, and we apologize for it.

Version 07 july 2021 New version 1.4.2

07th July, 2021

 

For our latest version, we do now respect the 1.4.2.18 STET model. The following list give you the details of the changes for this new version.

 

This new release 1.4.2.18 involve the following backwards-compatibles changes with our latest 1.4.1.3 version :

  • PISP : Adding of a new object, equivalent amount for international payments
  • PISP : Adding an optional InstructionForCreditorAgent structure for international payments
  • PISP : Adding an optional UltimateDebtor structure for international payments
  • PISP : Allow the specification of an intermediary agent for international payments
  • PISP/Fix : The field paymentTypeInformation.serviceLevel is not mandatory anymore
  • PISP/Fix : We have fixed a wrong behavior on the schemeName field

This new release 1.4.2 involve the following nonbackwards-compatibles changes with our latest 1.4.1 version :

  • AISP : You can now specify wich version you want to use (1.4.1 or 1.4.2)
  • AISP : We set amount type to number
  • AISP : The Field transactionDate is now a datetime
  • AISP : There is new values for PsuStatus and "Co-account Holder" is replaced by "Account Co-holder"
  • PISP : You can now specify wich version you want to use (1.4.1 or 1.4.2)
  • PISP : For version 1.4.2, you should now respect the OAUTH2 Simple REDIRECT Approach
  • PISP : The date-time formats is now restricted to date-time information (we do not accept anymore date-time information without time)
  • PISP : The remittance structured object has evolved
  • PISP : We have modified the Address structure
  • PISP : Purpose object is now at instruction level
  • PISP : UltimateCreditor object is not dusplicated anymore
  • PISP : The amount type are now number

  • PISP : We have added an ACTC value for transaction status
  • PISP : We have added a new payment/transaction status for cancellation
  • PISP : We have added a precision on the PUT Payment-request when unauthorized modifications are posted
     

We will continue to support 1.4.1 version

New version - 08 April 2021

08th April, 2021

This new release does not involve any non-backwards-compatibles changes.

  • AISP - You can now get the information about the card used for a transaction on the deferred debit operations (except for Fortuneo).
    • This information is displayed on a new field "additionalTransactionInformation", this is an add-on from STET 1.4.2 into the version STET 1.4.1
    • Please refer to the documentation for more information and details about the format.
    • This new information will be available on Fortuneo transactions from mid-April 2021

Maintenance of developer.arkea.com website

22nd September, 2020

The website developer.arkea.com will be unavailaible the 28th of September from 2pm Paris time for few minutes due to a maintenance operation.

New version - 08 july 2020

08th July, 2020

This new release does not involve any non-backwards-compatibles changes.

  • PISP - You can now interact with the professional bank accounts (except for ABEI)
  • CBPII - You can now interact with the professional bank accounts (except for ABEI)
  • AISP - You can now interact with the professional bank accounts (except for ABEI)
  • AISP - We've added in the sandbox cases for our professional bank accounts
  • AISP - You can now get the name of the owner of a beneficiaries in a details field (usefull when a psu manage several spaces of accounts)
  • AISP - We've adjusted the behavior of the querry parameters dateFrom and dateTo on a search of transactions

Use cases with professional accounts available in Sandbox

24th June, 2020

You were waiting for them : personae with professional accounts are now available in Sandbox !

Payment tip : How to easily recover debtor's IBAN

23rd June, 2020

During a payment request, you can now recover debtor's IBAN : once the PSU has selected the debit account in the validation process, execute a GET /payment-requests/{paymentRequestResourceId}. You will retrieve it into debtorAccount field.

New web site for Allianz Banque

10th June, 2020

We will sooon open a new website for Allianz Banque’s customers.

You will be able to integrate this new website from July, 2020. The migration between current website and new website for all customers will be performed on September, 2020. From this date, the current website will be no more available.

Feel free to ask us for the new documentation by using the  contact form from the beginning of July.

SCA deployment

10th June, 2020

To allow you to adapt your environments, here are the next dates for SCA deployment :

  • AZB : june, 2020,
  • ABS : july, 2020,
  • CMB : little by little from september to october, 2020.

The other banks hosted by Arkéa have already been deployed.

Continuity of our services

27th March, 2020

Hello,

please be aware that, in this unprecedented period, linked to the spreading of COVID-19, we are making every effort to ensure the best possible continuity of our services and to respond to your requests as quickly as possible.

We count on your understanding.

We hope that in this particular period, you and your loved ones are keeping safe and healthy.

Yours sincerely.

Fortuneo : SCA in the Fallback mechanism

10th March, 2020

From march 11, 2020, it will be mandatory to use SCA in the Fallback mechanism of Fortuneo.

Feel free to ask for help by using the contact form.

New authentication on fallback from 17 February 2020

31st January, 2020

We are currently modifying the authentication mode for the fallback interface of CMB, CMSO, ABEI, ABP and BPE. The estimated date of moving to production for this modification is 17 February 2020. From this date, the old way of authenticating will stay available during one month to let you take into account this evolution. So, we ask you to migrate to the new authentication mode before 17 of March 2020.

Ask for the new fallback's documentation !

Do not hesitate to contact us in case of trouble.

Thanks in advance.

Ability to test Strong Customer Authentication (SCA) in Fallback mechanism

20th December, 2019

It is now possible to activate SCA on demand in the Fallback mechanism of the following entities :

  • Crédit Mutuel de Bretagne,
  • CMSO, ABP, ABEI, BPE, 
  • ABS/AZB : available on 21st of january.

Feel free to ask for the documentation by using the contact form.

Devapps for CMMC

19th December, 2019

From the 1st of january 2020, Crédit Mutuel du Massif Central will no longer be managed by Credit Mutuel Arkea teams but by  Crédit Mutuel Alliance Fédérale (https://www.creditmutuel.fr/oauth2/en/devportal/index.html).

The consequence is that the application's contexts that you have created on our developer portal will be removed. The URLs api-openbanking.cmmc.fr and api-sandbox.cmmc.fr will no longer be accessible.

The entry into force of the PSD2

14th September, 2019

Access to the production environment is now open to TPPs (PSD2 licensed players) for the personal bank accounts using our APIs.

For business accounts, access is possible using our fallback mechanism described here.

The fallback mechanism is open to TPPs for personal and business bank accounts. To use the fallback mechanism, a creation of a developer application for each bank is required.

Below you will find a summary table of available bank via APIs or fallback mechanism :

Bank Personal account Business account
Crédit Mutuel de Bretagne API + Fallback Fallback
Crédit Mutuel du Massif Central API + Fallback Fallback
Crédit Mutuel du Sud Ouest API + Fallback Fallback
Arkéa Banque Privée API + Fallback Fallback
Arkéa Banque Entreprises & Institutionnels Not applicable Fallback
Arkéa Banking Services Not applicable Fallback
Fortuneo API + Fallback Not applicable
MAX API + Fallback Not applicable
BPE API + Fallback Fallback
Allianz Banque API + Fallback Fallback

Access to the production environment

11th September, 2019

Access to the production environment will be open from the 11th of September for the personal bank accounts using our APIs. Please consult the check list of prerequisites to use the APIs to be sure you are ready.

For business accounts, access is possible using our fallback mechanism described here

The fallback mechanism is part of the production environment and will also be open from the 11th of September for personal and business bank accounts. In accordance with the ACPR decisions, Strong Customer Authentication (SCA) will not be implemented on this contingency mode. To use the fallback mechanism, a creation of a developer application for each bank is required (a complete check list of the prerequisites to use fallback is available in FAQ).

Strong Customer Authentication (SCA) will be deployed gradually on our banks websites. This will not impact PSD2 access for nominal and contingency modes until further implementation.