Connexis Cash

Connexis Cash PSD2 Account Information API (STET)

A PSD2-compliant Account Information Service (AISP) API exposed by BNP Paribas Corporate and Institutional Banking. Third-party providers consume this REST/JSON API, which follows the STET PSD2 standard, to retrieve account information for Connexis Cash users. Production uses OAuth2 Authorization Code Grant with QWAC certificates; the sandbox uses Client Credentials. Onboarded TPPs must supply QWAC certificates, callback URLs, and EBA reference codes.

GitHub OpenAPI

Operations 4

GET /v2/accounts Retrieval of the PSU accounts (AISP) #
GET /v2/accounts/{accountResourceId}/balances Retrieval of an account balances report (AISP) #
GET /v2/accounts/{accountResourceId}/transactions Retrieval of an account transaction set (AISP) #
GET /v2/trusted-beneficiaries Retrieval of the trusted beneficiaries list (AISP) #

Documentation

📖
Documentation
https://developers.cib.bnpparibas.com/index.php/api-docs/account-information-psd2-stet-mock
📖
APIReference
https://developers.cib.bnpparibas.com/index.php/api-docs/account-information-psd2-stet-mock

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/connexis-cash/refs/heads/main/openapi/connexis-cash-account-information-psd2-stet-mock-openapi.yml

Other Resources

🔗
DeveloperPortal
https://developers.cib.bnpparibas.com/
🔗
Production
https://psd2.api.cib.bnpparibas.com/gb-account-information-psd2-stet
🔗
Sandbox
https://api.sandbox.cib.bnpparibas.com/gb-account-information-psd2-stet-mock
🔗
Fallback
https://connexis.bnpparibas.com/
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/connexis-cash/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/psd2-account-information"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

connexis-cash-account-information-psd2-stet-mock-openapi.yml Raw ↑ 
openapi: 3.0.0
info:
   version: 2.0.0
   x-stet-version: 1.4.0.47
   title: Account Information (PSD2 STET Mock)
   x-generate-global-scope: true
   description: "## Overview\nThird Party Providers can consume the PSD2 AISP API\
      \ to retrieve account information from Connexis Cash.\n\nOur API allows TPPs\
      \ to access Account information on behalf of CONNEXIS CASH users. This API intends\
      \ to provide an interface between:\n\n+ Account Servicing Payment Service Providers\
      \ (**ASPSP**)\n\n+ Third Party (Payment Service) Providers (**TPP**)\n\n\nTPP\
      \ act with Account Information Service Providers role (**AISP**)\n\n\nThe Payment\
      \ Service User (**PSU**) is the owner of the accounts held by the ASPSP and\
      \ gives accreditations to the TPP in order to access his accounts information\
      \ or initiates payment from these accounts.\n\n\nTPPs can now offer accounts\
      \ information services to customers using CONNEXIS CASH eBanking solution.\n\
      \n\n\n## User Consent\n\n\nCONNEXIS CASH chose the Full-AISP model (A1 from\
      \ the STET documentation) : CONNEXIS CASH does not require to be informed of\
      \ the details of the PSU consent. Whatever the AISP request, the CONNEXIS CASH\
      \ will respond, being unable to check the compliance of the request against\
      \ the user choices.\n*The PUT/Consent request is only applicable in the Mixed\
      \ model (A2 of the STET documentation), CONNEXIS Cash will not implement such\
      \ request in the sandbox environment and in the production environment. In accordance\
      \ with the PSD2, a TPP and a PSU must have a contractual relationship.*\n\n\n\
      \n\n## API Architecture\n\n\nThe API is designed on a REST FULL model using\
      \ JSON structures. Our API is based on STET (1.4.0.47) format.\n## Sandbox\n\
      A sandbox environment is available to facilitate the onboarding and learning\
      \ process of the TPP.\n\nThose APIs return fake data. No sensitive information\
      \ shall be shared through the sandbox environment.\n\nOn the sandbox environment,\
      \ Client_credential is the only OAuth 2.0 flow available.\n\n## Production\n\
      The URL of the production environment is **https://psd2.api.cib.bnpparibas.com/gb-account-information-psd2-stet**.\
      \ \n\nThe Authorization code url is : **https://api.cib.bnpparibas.com/oauth2/v1/authorize?client_id={cliend_id}&response_type=code&scope={scopes}&redirect_uri={redirect_uri}&state={state}**.\n\
      \nThe TPP must use the OAuth2 Authorization Code Grant flow for AISP, PISP or\
      \ PIISP scope.\nThe production environment can only be accessed according to\
      \ the full STET standard and requires a qwac certificate delivered by a QTSP.\n\
      For a manual onboarding, the TPP should provide its QWAC certificate, callback\
      \ URL, and EBA reference code to **dl.cib.api.psd2.support@bnpparibas.com**\n\
      ## Support\nNeed support? We are here to help you\n\nIn case of technical issue\
      \ between you as TPP and the bank, please contact us at the following email\
      \ address : **dl.cib.api.psd2.support@bnpparibas.com**\nPlease be aware that\
      \ the client can always contact us via his usual BNPP representative as the\
      \ issue might come from a wrong set up in the client contract. \n## Fallback\
      \ Process\nAs part of its legal obligations under PSD2, BNPP CIB implements\
      \ a fallback mechanism. \nThis fallback solution is not available in sandbox\
      \ environment with fake data.\n\n**Prerequisite**\n\nThis process allows developers\
      \ to use fallback mechanism only in case the dedicated API is not available\
      \ and in compliance with the regulation (EU) 2018/389.\n\n**URL Fallback**\n\
      \nThe Fallback URL for TPP is the same URL as Connexis Cash customers : https://connexis.bnpparibas.com/\n\
      \n**TPP identification** \n\nThe same requirements regarding identification\
      \ of TPPs with QWACs apply irrespective of whether the TPPs are accessing the\
      \ users’ payment accounts via the dedicated interface or via Connexis Cash.\
      \ The identification of TPPs towards Connexis Cash should be based on the use\
      \ of qualified certificates for website authentication (QWACs).\n\n**Strong\
      \ customer authentication through Connexis Cash**\n\nTo access Connexis Cash,\
      \ the user have to enter his customer credentials. TPP developers can connect\
      \ to our online banking with this customer credentials in order to retrieve\
      \ PSD2 data.  \n"
servers:
-  url: https://api.sandbox.cib.bnpparibas.com/gb-account-information-psd2-stet-mock
   description: PROD_INTERNET
paths:
   /v2/accounts:
      get:
         operationId: accountsGet
         tags:
         - AISP
         summary: Retrieval of the PSU accounts (AISP)
         description: "### Description\n\nThis call returns all payment accounts that\
            \ are relevant to the PSU on behalf of whom the AISP is connected.\n\n\
            \n*This requests makes available all the accounts which are available\
            \ today in the Reporting module of Connexis Cash. The returned accounts\
            \ might differ from the ones used for payment, and should therefore not\
            \ be used for Payment Initiation.*\n\n\nThanks to HYPERMEDIA, each account\
            \ is returned with the links aiming to ease access to the relevant transactions\
            \ and balances.\n\n\nThe result may be subject to pagination (i.e. retrieving\
            \ a partial result in case of having too many results) through a set of\
            \ pages by the ASPSP. Thereafter, the AISP may ask for the first, next,\
            \ previous or last page of results.\n\n\n*Attention : the « name » account\
            \ field is not necessarily an IBAN, this name is customizable by the client.\
            \ Furthermore, some optional fields present in the STET documentation\
            \ are not communicated through the API because they are currently not\
            \ transmitted to our clients  or they are specific to the retail segment\
            \ (psuStatus, linkedAccount, product)*\n\n\n### Prerequisites\n\n- The\
            \ TPP has been registered by the Registration Authority for the AISP role.\
            \ (not mandatory for Sandbox)\n- The TPP and the PSU have a contract that\
            \ has been enrolled by the ASPSP (not mandatory for Sandbox)         \
            \  \n    - At this step, Connexis Cash has delivered an OAUTH2 access\
            \ token to the TPP via OAuth2 flow : Authorization Code Grant (for production)\
            \ or Client Credential (for sandbox).\n\n        For more details about\
            \ OAuth2 flow, please click on the links below : \n\n        - Authorization\
            \ Code Grant flow : https://developers.cib.bnpparibas.com/docs/auth2-ac-psd2\n\
            \n        - Client Credential flow : https://developers.cib.bnpparibas.com/docs/auth2-cc\n\
            \n- The TPP and the ASPSP have successfully processed a mutual check and\
            \ authentication\n- The TPP has presented its OAUTH2 access token\n- Connexis\
            \ Cash takes into account the access token that establishes the link between\
            \ the PSU and the AISP.\n\n### Business Flow\n\n- The TPP sends a request\
            \ to the ASPSP for retrieving the list of the PSU payment accounts. The\
            \ ASPSP computes the relevant PSU accounts and builds the answer as an\
            \ accounts list.\n\n- The result may be subject to pagination in order\
            \ to avoid an excessive result set. Each payment account will be provided\
            \ with its characteristics.\n\n\n### Specific for the Sandbox\n\n- For\
            \ this sandbox, **the data is fictive**, we put the account lists of a\
            \ fictive user “ User 1” at TPP’s disposal.\n\n- The « User 1 » owns 5\
            \ accounts : one Dutch account in EUR, one Polish account in EUR, one\
            \ Greek account in EUR and 2 Danish accounts in DKK.\n\n- The “Signature”\
            \ and “X Request ID” parameters will not be verified by our sandbox for\
            \ the test. They must be not null.\n"
         security:
         -  OAuth2:
            - aisp
         parameters:
         -  $ref: '#/components/parameters/PsuIpAddressHeader'
         -  $ref: '#/components/parameters/PsuIpPortHeader'
         -  $ref: '#/components/parameters/PsuHttpMethodHeader'
         -  $ref: '#/components/parameters/PsuDateHeader'
         -  $ref: '#/components/parameters/PsuGeoLocation'
         -  $ref: '#/components/parameters/PsuUserAgentHeader'
         -  $ref: '#/components/parameters/PsuRefererHeader'
         -  $ref: '#/components/parameters/PsuAcceptHeader'
         -  $ref: '#/components/parameters/PsuAcceptCharsetHeader'
         -  $ref: '#/components/parameters/PsuAcceptEncodingHeader'
         -  $ref: '#/components/parameters/PsuAcceptLanguageHeader'
         -  $ref: '#/components/parameters/PsuDeviceId'
         -  $ref: '#/components/parameters/DigestHeader'
         -  $ref: '#/components/parameters/SignatureHeader'
         -  $ref: '#/components/parameters/Correlation'
         responses:
            '200':
               description: |
                  The ASPSP return a PSU context
                  - listing the accounts that have been made available to the AISP by the PSU and,
                  - for each of these accounts, the further transactions that have been enabled by the PSU through HYPERMEDIA links.
               headers:
                  X-Request-ID:
                     description: |
                        Correlation header to be set in a request and retrieved in the relevant response
                     schema:
                        type: string
               content:
                  application/json:
                     schema:
                        $ref: '#/components/schemas/HalAccounts'
            '204':
               $ref: '#/components/responses/204'
            '401':
               $ref: '#/components/responses/401'
            '403':
               $ref: '#/components/responses/403'
            '404':
               $ref: '#/components/responses/404'
            '405':
               $ref: '#/components/responses/405'
            '406':
               $ref: '#/components/responses/406'
            '408':
               $ref: '#/components/responses/408'
            '429':
               $ref: '#/components/responses/429'
            '500':
               $ref: '#/components/responses/500'
            '503':
               $ref: '#/components/responses/503'
   /v2/accounts/{accountResourceId}/balances:
      get:
         operationId: accountsBalancesGet
         description: "### Description\n\nThis call returns a set of balances for\
            \ a given PSU account that is specified by the AISP through an account\
            \ resource Identification.\n\nThe answer to this request will provide\
            \ the account balance but also other balances which are currently made\
            \ available for clients through the Connexis Cash platform.\n\nOn the\
            \ Connexis Cash platform the client can access Ledger (booked or available)\
            \ and Value (booked, without intraday or available, with intraday) balances.\
            \ Those balances will be provided in the answer to the request while complying\
            \ with STET standards. For more information, please find below the corresponding\
            \ table:\n\n<table>\n  <tr>\n    <th>STET</th>\n    <th>Balances code</th>\n\
            \    <th>Connexis Balances</th>\n  </tr>\n  <tr>\n    <td><strong>CLBD</strong></td>\n\
            \    <td>Accounting Balance</td>\n    <td><strong>Ledger Booked</strong></td>\n\
            \  </tr>\n  <tr>\n    <td><strong>XPCD</strong></td>\n    <td>Instant\
            \ Balance</td>\n    <td><strong>Ledger available</strong></td>\n  </tr>\n\
            \  <tr>\n    <td><strong>VALU</strong></td>\n    <td>Value-date balance</td>\n\
            \    <td><strong>Value Booked (without intraday)</strong></td>\n  </tr>\n\
            \  <tr>\n    <td><strong>OTHR</strong></td>\n    <td>Other Balance</td>\n\
            \    <td><strong>Value available (with intraday)</strong></td>\n  </tr>\n\
            </table>\n\n*Furthermore, some optional fields present in the STET documentation\
            \ are not communicated through the API because they are currently not\
            \ transmitted to our clients  or they are specific to the retail segment\
            \ (lastChangeDateTime and lastCommittedTransaction).*\n\n### Prerequisites\n\
            - The TPP has been registered by the Registration Authority for the AISP\
            \ role. (not mandatory for Sandbox)\n- The TPP and the PSU have a contract\
            \ that has been enrolled by the ASPSP (not mandatory for Sandbox)    \
            \       \n    - At this step, Connexis Cash has delivered an OAUTH2 access\
            \ token to the TPP via OAuth2 flow : Authorization Code Grant (for production)\
            \ or Client Credential (for sandbox).\n\n        For more details about\
            \ OAuth2 flow, please click on the links below : \n\n        - Authorization\
            \ Code Grant flow : https://developers.cib.bnpparibas.com/docs/auth2-ac-psd2\n\
            \n        - Client Credential flow : https://developers.cib.bnpparibas.com/docs/auth2-cc\n\
            \n- The TPP and the ASPSP have successfully processed a mutual check and\
            \ authentication\n- The TPP has presented its OAUTH2 access token\n- Connexis\
            \ Cash takes into account the access token that establishes the link between\
            \ the PSU and the AISP.\n- The TPP has previously retrieved the list of\
            \ available accounts for the PSU\n\n### Business Flow\n\n- The AISP requests\
            \ the ASPSP on one of the PSU’s accounts. The ASPSP answers by providing\
            \ a list of balances on this account.\n\n### Specific for the Sandbox\n\
            \n- To get positive results (200 response), i.e. accessing the fake data\
            \ provided by Connexis Cash, it is necessary to indicate a valid accountResourceId.\
            \ In case an invalid \"accountResourceId\" is present, an error message\
            \ will be displayed.\n\n- The list of valid accountResourceId can be obtained\
            \ via the get/accounts request in the resourceId field or below:\n\n \
            \ - 1306171745\n\n  - 1306171845\n\n  - 1987376645\n\n  - 19737006845\n\
            \n  - 19737007345\n\n - The “Signature” and “X Request ID” parameters\
            \ will not be verified by our sandbox for\nthe test. They must be not\
            \ null.\n"
         summary: Retrieval of an account balances report (AISP)
         tags:
         - AISP
         security:
         -  OAuth2:
            - aisp
         parameters:
         -  $ref: '#/components/parameters/AccountResourceIdentification'
         -  $ref: '#/components/parameters/PsuIpAddressHeader'
         -  $ref: '#/components/parameters/PsuIpPortHeader'
         -  $ref: '#/components/parameters/PsuHttpMethodHeader'
         -  $ref: '#/components/parameters/PsuDateHeader'
         -  $ref: '#/components/parameters/PsuGeoLocation'
         -  $ref: '#/components/parameters/PsuUserAgentHeader'
         -  $ref: '#/components/parameters/PsuRefererHeader'
         -  $ref: '#/components/parameters/PsuAcceptHeader'
         -  $ref: '#/components/parameters/PsuAcceptCharsetHeader'
         -  $ref: '#/components/parameters/PsuAcceptEncodingHeader'
         -  $ref: '#/components/parameters/PsuAcceptLanguageHeader'
         -  $ref: '#/components/parameters/PsuDeviceId'
         -  $ref: '#/components/parameters/DigestHeader'
         -  $ref: '#/components/parameters/SignatureHeader'
         -  $ref: '#/components/parameters/Correlation'
         responses:
            '200':
               description: The ASPSP answers with a list of account balances
               headers:
                  X-Request-ID:
                     description: |
                        Correlation header to be set in a request and retrieved in the relevant response
                     schema:
                        type: string
               content:
                  application/json:
                     schema:
                        $ref: '#/components/schemas/HalBalances'
            '204':
               $ref: '#/components/responses/204'
            '400':
               $ref: '#/components/responses/400'
            '401':
               $ref: '#/components/responses/401'
            '403':
               $ref: '#/components/responses/403'
            '404':
               $ref: '#/components/responses/404'
            '405':
               $ref: '#/components/responses/405'
            '406':
               $ref: '#/components/responses/406'
            '408':
               $ref: '#/components/responses/408'
            '429':
               $ref: '#/components/responses/429'
            '500':
               $ref: '#/components/responses/500'
            '503':
               $ref: '#/components/responses/503'
   /v2/accounts/{accountResourceId}/transactions:
      get:
         operationId: accountsTransactionsGet
         description: "### Description\n\n\nThis call returns transactions for an\
            \ account for a given PSU account that is specified by the AISP through\
            \ an account resource identification.\n\n\nThe request may use some filter\
            \ parameter in order to restrict the query, on a given imputation date\
            \ range\n\n\n*As Connexis Cash does not permit its clients to filter on\
            \ a given technical incremental identifier (optional filter AfterEntryReference\
            \ proposed by STET), our API does not support this type of filter.*\n\n\
            The maximum transaction history range returned is 13 months. (Note : there\
            \ are no error messages if the query parameter “entryDateTo” of the request\
            \ contains a date older than 13 months) .In the absence of query Parameters\
            \ (entryDateFrom and entryDateTo), the period returned by default is 8\
            \ days : (fromdate is -2 days and To date is + 5days).\n\n\nThe result\
            \ may be subject to pagination (i.e. retrieving a partial result in case\
            \ of having too many results) through a set of pages by the ASPSP.\n\n\
            \nOptional parameters can be added by the TPP: PageSize and Page Number\
            \ (by default, in the absence of value, the parameters are PageSize =\
            \ 10 and Page Number = 0)\n\n\n*All fields specified by STET will be made\
            \ available for a TPP, except the optional fields « RessourceID » and\
            \ « entryReference ».*\n\n\n*Moreover, there is currently a technical\
            \ identification attribute of the transaction but this one is for internal\
            \ use only and cannot be passed to the clients.*\n*The “status” field\
            \ is converted in order to comply with STET standards. You will find below\
            \ the information:*\n\n- BOOK: (ISO20022 ClosingBooked) Accounted transaction\
            \ : “B”\n\n- PDNG: (ISO20022 Expected) Instant Balance Transaction : “\
            I”\n\n\n### Prerequisites\n\n- The TPP has been registered by the Registration\
            \ Authority for the AISP role. (not mandatory for Sandbox)\n- The TPP\
            \ and the PSU have a contract that has been enrolled by the ASPSP (not\
            \ mandatory for Sandbox)           \n    - At this step, Connexis Cash\
            \ has delivered an OAUTH2 access token to the TPP via OAuth2 flow : Authorization\
            \ Code Grant (for production) or Client Credential (for sandbox).\n\n\
            \        For more details about OAuth2 flow, please click on the links\
            \ below : \n\n        - Authorization Code Grant flow : https://developers.cib.bnpparibas.com/docs/auth2-ac-psd2\n\
            \n        - Client Credential flow : https://developers.cib.bnpparibas.com/docs/auth2-cc\n\
            \n- The TPP and the ASPSP have successfully processed a mutual check and\
            \ authentication\n- The TPP has presented its OAUTH2 access token\n- Connexis\
            \ Cash takes into account the access token that establishes the link between\
            \ the PSU and the AISP.\n- The TPP has previously retrieved the list of\
            \ available accounts for the PSU\n\n### Business Flow\n\n\nThe AISP requests\
            \ the ASPSP on one of the PSU’s accounts. It may specify some selection\
            \ criteria (Date From / Date To).\n\n\nThe ASPSP answers by a set of transactions\
            \ that matches the query.\n\n\nThe result may be subject to pagination\
            \ in order to avoid an excessive result set.\n\n\n### Specific for the\
            \ Sandbox\n\n- To get positive results (200 response) i.e. accessing the\
            \ fake data provided by Connexis Cash, it is necessary to indicate a valid\
            \ accountResourceId. In case of invalid accountResourceId, un error message\
            \ is displayed.\n\n- The list of valid accountResourceId can be retrieved\
            \ via the get/accounts request in the resourceId field or below :\n\n\
            <table>\n  <tr>\n    <th>Account Ressource ID</th>\n    <th>Transactions</th>\n\
            \  </tr>\n  <tr>\n    <td>1306171745</td>\n    <td>00</td>\n  </tr>\n\
            \  <tr>\n    <td>1306171845</td>\n    <td>10</td>\n  </tr>\n  <tr>\n \
            \   <td>1987376645</td>\n    <td>02</td>\n  </tr>\n  <tr>\n    <td>19737006845</td>\n\
            \    <td>00</td>\n  </tr>\n  <tr>\n    <td>19737007345</td>\n    <td>09</td>\n\
            \  </tr>\n</table>\n- Among the proposed accounts, 19737007345 and 1987376645\
            \ have an associated transactions list (10 transactions for 1306171845\
            \ and 2 transactions for 1987376645).\n- For the sandbox, there will be\
            \ no pagination in the result.\n- The “Signature” and “X Request ID” parameters\
            \ will not be verified by our sandbox for the test. They must be not null.\n\
            - The date format is yyyy-mm-dd\n"
         summary: Retrieval of an account transaction set (AISP)
         security:
         -  OAuth2:
            - aisp
         tags:
         - AISP
         parameters:
         -  $ref: '#/components/parameters/AccountResourceIdentification'
         -  $ref: '#/components/parameters/FromImputationDate'
         -  $ref: '#/components/parameters/ToImputationDate'
         -  $ref: '#/components/parameters/pageNumber'
         -  $ref: '#/components/parameters/pageSize'
         -  $ref: '#/components/parameters/PsuIpAddressHeader'
         -  $ref: '#/components/parameters/PsuIpPortHeader'
         -  $ref: '#/components/parameters/PsuHttpMethodHeader'
         -  $ref: '#/components/parameters/PsuDateHeader'
         -  $ref: '#/components/parameters/PsuGeoLocation'
         -  $ref: '#/components/parameters/PsuUserAgentHeader'
         -  $ref: '#/components/parameters/PsuRefererHeader'
         -  $ref: '#/components/parameters/PsuAcceptHeader'
         -  $ref: '#/components/parameters/PsuAcceptCharsetHeader'
         -  $ref: '#/components/parameters/PsuAcceptEncodingHeader'
         -  $ref: '#/components/parameters/PsuAcceptLanguageHeader'
         -  $ref: '#/components/parameters/PsuDeviceId'
         -  $ref: '#/components/parameters/DigestHeader'
         -  $ref: '#/components/parameters/SignatureHeader'
         -  $ref: '#/components/parameters/Correlation'
         responses:
            '200':
               description: Complete transactions response
               headers:
                  X-Request-ID:
                     description: |
                        Correlation header to be set in a request and retrieved in the relevant response
                     schema:
                        type: string
               content:
                  application/json:
                     schema:
                        $ref: '#/components/schemas/HalTransactions'
            '204':
               $ref: '#/components/responses/204'
            '400':
               $ref: '#/components/responses/400'
            '401':
               $ref: '#/components/responses/401'
            '403':
               $ref: '#/components/responses/403'
            '404':
               $ref: '#/components/responses/404'
            '405':
               $ref: '#/components/responses/405'
            '406':
               $ref: '#/components/responses/406'
            '408':
               $ref: '#/components/responses/408'
            '429':
               $ref: '#/components/responses/429'
            '500':
               $ref: '#/components/responses/500'
            '503':
               $ref: '#/components/responses/503'
   /v2/trusted-beneficiaries:
      get:
         operationId: trustedBeneficiariesGet
         tags:
         - AISP
         summary: Retrieval of the trusted beneficiaries list (AISP)
         description: "### Description\n\nThe trusted counterparties list is considered\
            \ as the authorized counterparties list so that a payment could be initiated\
            \ without SCA. The list, if provided by an ASPSP, should be put at the\
            \ AISP’s disposal as he is currently able to visualize it via the ASPSP\
            \ online interface.\n\nIn Connexis Cash, an entity can register a counterparty\
            \ in a list of usual counterparties. However for payment authorization,\
            \ strong authentication (SCA) is systematically requested. **The list\
            \ of counterparties is not a trusted list of counterparties as described\
            \ in the RTS, this is why this request will not return any result, (200\
            \ empty Response []).**\n\n\n - The “Signature” and “X Request ID” parameters\
            \ will not be verified by our sandbox for\nthe test. They must be not\
            \ null.\n\n### Prerequisites\n\n- The TPP has been registered by the Registration\
            \ Authority for the AISP role. (not mandatory for Sandbox)\n- The TPP\
            \ and the PSU have a contract that has been enrolled by the ASPSP (not\
            \ mandatory for Sandbox)           \n    - At this step, Connexis Cash\
            \ has delivered an OAUTH2 access token to the TPP via OAuth2 flow : Authorization\
            \ Code Grant (for production) or Client Credential (for sandbox).\n\n\
            \        For more details about OAuth2 flow, please click on the links\
            \ below : \n\n        - Authorization Code Grant flow : https://developers.cib.bnpparibas.com/docs/auth2-ac-psd2\n\
            \n        - Client Credential flow : https://developers.cib.bnpparibas.com/docs/auth2-cc\n\
            \n- The TPP and the ASPSP have successfully processed a mutual check and\
            \ authentication\n- The TPP has presented its OAUTH2 access token\n"
         security:
         -  OAuth2:
            - aisp
         parameters:
         -  $ref: '#/components/parameters/PsuIpAddressHeader'
         -  $ref: '#/components/parameters/PsuIpPortHeader'
         -  $ref: '#/components/parameters/PsuHttpMethodHeader'
         -  $ref: '#/components/parameters/PsuDateHeader'
         -  $ref: '#/components/parameters/PsuGeoLocation'
         -  $ref: '#/components/parameters/PsuUserAgentHeader'
         -  $ref: '#/components/parameters/PsuRefererHeader'
         -  $ref: '#/components/parameters/PsuAcceptHeader'
         -  $ref: '#/components/parameters/PsuAcceptCharsetHeader'
         -  $ref: '#/components/parameters/PsuAcceptEncodingHeader'
         -  $ref: '#/components/parameters/PsuAcceptLanguageHeader'
         -  $ref: '#/components/parameters/PsuDeviceId'
         -  $ref: '#/components/parameters/DigestHeader'
         -  $ref: '#/components/parameters/SignatureHeader'
         -  $ref: '#/components/parameters/Correlation'
         responses:
            '200':
               description: |
                  The ASPSP returns the list of whitelisted beneficiaries
               headers:
                  X-Request-ID:
                     description: |
                        Correlation header to be set in a request and retrieved in the relevant response
                     schema:
                        type: string
               content:
                  application/json:
                     schema:
                        $ref: '#/components/schemas/HalBeneficiaries'
            '204':
               $ref: '#/components/responses/204'
            '401':
               $ref: '#/components/responses/401'
            '403':
               $ref: '#/components/responses/403'
            '404':
               $ref: '#/components/responses/404'
            '405':
               $ref: '#/components/responses/405'
            '406':
               $ref: '#/components/responses/406'
            '429':
               $ref: '#/components/responses/429'
            '500':
               $ref: '#/components/responses/500'
components:
   parameters:
      AccountResourceIdentification:
         name: accountResourceId
         in: path
         description: Identification of account resource to fetch
         required: true
         schema:
            type: string
            pattern: ^([a-zA-Z0-9 \/\-?:\()\.,']{1,35})$
      PaymentRequestResourceIdentification:
         name: paymentRequestResourceId
         in: path
         description: Identification of the Payment Request Resource
         required: true
         schema:
            type: string
            pattern: ^([a-zA-Z0-9 \/\-?:\()\.,']{1,35})$
      AfterEntryReference:
         name: afterEntryReference
         in: query
         description: |
            Specifies the value on which the result has to be computed.
            Only the transaction having a technical identification greater than this value must be included within the result
         required: false
         schema:
            type: string
            maxLength: 40
      ToImputationDate:
         name: entryDateTo
         in: query
         description: |
            Exclusive maximal imputation date of the transactions.
            Transactions having an imputation date equal to this parameter are not included within the result.
         required: false
         schema:
            type: string
            format: date-time
      FromImputationDate:
         name: entryDateFrom
         in: query
         description: |
            Inclusive minimal imputation date of the transactions.
            Transactions having an imputation date equal to this parameter are included within the result.
         required: false
         schema:
            type: string
            format: date-time
      pageNumber:
         name: pageNumber
         in: query
         description: |
            Specifies a page number in case of a pagination
         required: false
         schema:
            type: integer
            format: int32
      pageSize:
         name: pageSize
         in: query
         description: |
            Specifies the number of transactions to be displayed in the page in case of pagination
         required: false
         schema:
            type: integer
            format: int32
      PsuIpAddressHeader:
         name: PSU-IP-Address
         in: header
         description: IP address used by the PSU's terminal when connecting to the
            TPP
         schema:
            type: string
      PsuIpPortHeader:
         name: PSU-IP-Port
         in: header
         description: IP port used by the PSU's terminal when connecting to the TPP
         schema:
            type: string
      PsuHttpMethodHeader:
         name: PSU-HTTP-Method
         in: header
         description: Http method for the most relevant PSU’s terminal request to
            the TTP
         schema:
            type: string
      PsuDateHeader:
         name: PSU-Date
         in: header
         description: Timestamp of the most relevant PSU’s terminal request to the
            TTP
         schema:
            type: string
      PsuGeoLocation:
         name: PSU-GEO-Location
         in: header
     

# --- truncated at 32 KB (98 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/connexis-cash/refs/heads/main/openapi/connexis-cash-account-information-psd2-stet-mock-openapi.yml