Reads user's consent's cards

get

https://example.com/tpp/v1/users/{userId}/consents/{consentId}/cards

Reads a list of user's specific consent's cards with additional information, e.g. balance information.

BOI-REMARK - BOI is differentiating ASPSPs in the role of banks and of credit card processors:

For banks, this endpoint is returning all accounts used for reconciliation of the related credit cards. The account identifier in this case is masked PAN of one of the related cards. This might be only one account with several cards.
For credit card processors, the Read Card Account List will deliver a dedicated card-account for every card related to a PSU. The account identifier in this case will be a masked PAN.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

userId

string

required

ID of the addressed user. Consists of the sub + @ + tpp_id.

consentId

string

required

length ≤ 523

Resource ID of the addressed consent.

Query Params

preventUpdate

boolean

If contained, we won't update user's financial data (i.e. no account data requests will be made to the ASPSP).

withBalances

boolean

If contained, this function reads the list of accessible payment accounts including the booking balance,
if granted by the PSU in the related consent and available by the ASPSP.

transactionId

string

In case the request processing took longer than X-Request-Wait milliseconds,
this value will be used for resuming the past request.

Headers

X-Trace-Id

string

X-Request-Wait

integer

≥ 0

Defaults to 10

In case the request processing requires calls to external resources (as ASPSPs),
this value will define the maximum number of milliseconds
in which the API server will wait for all external resources' responses to complete.
If not present, the default configured duration will be used.

X-Psu-IP-Address

string

length ≤ 15

In case if end user is online, this header should be present and contain an IP address of the user.

X-Tpp-Id

string

Contains TPP name

Origin

string

Responses

200OK

401Consent insufficient meaning the consent doesn't include at least one of requested data baskets [ACCOUNTS, BALANCES, TRANSACTIONS] in order to access the addressed service.

404User not found

410Consent not found. When returned from accounts endpoints, it can also mean the related consent isn't valid nor suspended.

429Too many requests for the same resource

451The related consent is suspended, access for the data is temporarily blocked.

500Failed to fetch consent accounts list

502Failed to refresh related consent(s) status