Get a List of Payment Accounts

 Using this service, you can get access various data from a payment account authorized by the customer : 

• list all eligible online accessible payment accounts ;

• retrieve accounting balance ;

• get payment account holder identity.

• get URI for GET /accounts/balances and  GET /accounts/transactions methods.

Access to this method is limited to a maximum of 4 batch per day for one given TPP and PSU (except if the PSU is connected and has requested this operation).

Prerequisites

In order to proceed, TPP needs to fulfill all eligibility criteria and to present a valid OAUTH2 Authorization token (see use case "Get your token").

Request

"get/accounts"

See also STET V1.4.0.47 / Part II / section 4.1 page 5 

Mandatory parameter

No parameters required.

Result

IF YOU USE THIS REQUEST FOR THE FIRST TIME

(therefore if you didn't send previously any information using PUT /consents, OR if all granted accounts have not been revoked using PUT /consents - see use case "Forward customer's consent") :

• this call allows you to list all eligible online accessible authorized payment accounts

• It doesn't allow you to retrieve any additional data (no balance, no URI, no payment account holder identity)

IF YOU USE HAVE ALREADY FORWARDED AT LEAST ONE CONSENT FROM THE CUSTOMER

(therefore if you have used previously PUT /consents request, OR if all granted accounts have not been revoked using PUT /consents - see use case "Forward customer's consent") : this call allows you to retrieve all eligible online accessible authorized payment account with the following additional data :

• Accounting balance if this account is flagged in the "balances" parameter in PUT /consents method

• l'URL for the GET /accounts/balance method if this account is flagged in the "balance" parameter in PUT /consent

• l'URL for the GET /accounts/transactions method if this account is flagged in the "transactions" parameter in PUT /consent

• Get payment account holder identity if the field "psuIdentity" have been setup at TRUE value in the PUT /consents.

Example 

Acceptance tests

The purpose of these tests is to ensure that the API complies with the STET standard. They should be validated before any application deployment.