Information on a BRD-GROUPE SOCIETE GENERALE customer payment account, which is accessible online.

The accounts API allow third party applications to interact with the accounts of a BRD-GROUPE SOCIETE GENERALE user on his behalf, allowing the following operations:

List of accounts (Sandbox)
Account details (Sandbox)
Account balances (Sandbox)
Account transactions (Sandbox)

Fallback

In case the APIs do not work, we have developed a fallback solution that requires accessing the URL https://tppbck-retail.devbrd.ro. This solution allows web scraping with certificate as in the case of a classic request.

Account Information Consent

The consent specifies the accounts and the type of information (accounts / balances / transactions) which the client wants and agrees to be exposed through the AISP (Account Information Service Provider) application.

Creation of the consent

The consent is defined by the user within the TPP, with AISP role, application, which further sends the information to the bank (ASPSP) for further processing. The ASPSP returns as a response, to the account information consent request, a unique reference number (Consent-ID) and a message for the client informing/requesting the PSU for approval of the consent in his MyBRD application.

SCA authorization in a decoupled method

The user follows the instructions and starts the MyBRD application, using his/her credentials for authentication in the online banking. Based on the reference and information about the TPP, the user is able to identify the consent and approve it. Note: currently in Sandbox there is no SCA authorization implementation, all authorization actions being considered as already executed, implicitly.

Status of the consent

The TPP is able to retrieve the content / status of the consent (accepted / denied) and after approval by the client, the TPP is able to retrieve list of accounts, account details, balances or transactions.

A consent can be deleted by the client in the TPP application ( terminatedByTPP) or in his/her MyBRD application (revokedByPSU) The consent API allows the following request methods: GET, POST and DELETE and the following operations:

Create consent (Sandbox)
Consent details (Sandbox)
Consent status (Sandbox)
Delete consent (Sandbox)

Worth mentioning that the endpoints related to posting and deleting of the consent are provided for the sandbox only for the developers to try them out.

SANDBOX This API is included in a Sandbox environment to test your applications before accessing live data. A non-real user was created by default for testing your applications (see the table below).
User: 13333330
Account identifier: RO47BRDE410SV04747474100
Currency: RON
Balance: 2020.55
Transactions: 3

Account identifier: RO46BRDE410SV04646464100
Currency: EUR
Balance: -
Transactions: -

Consent ID
800000022 - Created for a "received" consent 700000011 - Created for an "expired" consent 600000033 - Created for a "valid" consent with empty arrays 500000044 - Created for a "valid" consent with all psd2
Payment ID
1122334455000 - Created for a payment initiation request
Note!
The certificate does not have to be provided on the Sandbox environment. The certification usage is mandatory in Production environment. When accessing the Portal in order to get a successful response from the system, the request should match the specific header, path, body and query parameters as per the documentation or else you will receive a HTTP error status code.