---
title: "Retrieval of transaction details (AISP)"
method: GET
path: "/accounts/{accountResourceId}/transactions/{transactionResourceId}/details"
tags: ["AISP"]
---

# Retrieval of transaction details (AISP)

`GET /accounts/{accountResourceId}/transactions/{transactionResourceId}/details`

## Request

- Base URL: `https://www.10207.oba-bad-me-live-api.banquepopulaire.fr/stet/psd2/v1.6.2`
- URL: `https://www.10207.oba-bad-me-live-api.banquepopulaire.fr/stet/psd2/v1.6.2/accounts/{accountResourceId}/transactions/{transactionResourceId}/details`
- Auth: OAuth 2
  - Authorization code: `/stet/psd2/oauth/authorize`
  - Token URL: `/stet/psd2/oauth/token` scopes: `aisp`

### Description
This call returns the details of a transaction from a given PSU account.
The AISP has to specified
- the account through an account resource identification
- the transaction through a transaction resource identifcation
### Prerequisites
- The TPP was registered by the Registration Authority for the AISP role
- The TPP and the PSU have a contract that was enrolled by the ASPSP
  - At this step, the ASPSP has delivered an OAUTH2 "Authorization Code" or "Resource Owner Password" access token to the TPP (cf. § 3.4.2).
- The TPP and the ASPSP have successfully processed a mutual check and authentication
- The TPP has presented its OAUTH2 "Authorization Code" or "Resource Owner Password" access token which allows the ASPSP to identify the relevant PSU and retrieve the linked PSU context (cf. § 3.4.2) is any.
- The ASPSP takes into account the access token that establishes the link between the PSU and the AISP.
- The TPP has previously retrieved the list of available accounts for the PSU and the transactions from one given account
- A transaction includes a "details" hyperlink which indicates that detailed information is available for this transaction.
### Business flow
The AISP requests the ASPSP on one of the transactions.
The ASPSP answers by the details on this transaction.

## Path parameters

- `accountResourceId` string, required
- `transactionResourceId` string, required

## Query parameters

- `dateFrom` string, date-time
- `dateTo` string, date-time
- `dateType` 'transactionDate' | 'bookingDate'
- `entryReferenceFrom` string
- `entryReferenceto` string
- `workspace` string

## Headers

- `Authorization` string, required
- `PSU-IP-Address` string
- `PSU-IP-Port` string
- `PSU-HTTP-Method` string
- `PSU-Date` string
- `PSU-GEO-Location` string
- `PSU-User-Agent` string
- `PSU-Referer` string
- `PSU-Accept` string
- `PSU-Accept-Charset` string
- `PSU-Accept-Encoding` string
- `PSU-Accept-Language` string
- `PSU-Device-ID` string
- `Digest` string
- `Signature` string, required
- `X-Request-ID` string, required

## Response `200`

Complete transactions response

- HalTransactionDetails: HYPERMEDIA structure used for returning the details of a given transaction
  - `details` string[], required: Details of the transactions
  - `_links` TransactionDetailsLinks, required: links that can be used after retrieving details on a given transaction | Link | Description | | ---- | ----------- | | transactions | link to the transaction list | | accounts | link to the list of all available accounts |
    - `transactions` GenericLink: hypertext reference
      - `href` string, required: URI to be used. HREF stands for Hypertext REFerence.
      - `templated` boolean: This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570. Otherwise, this property must be absent or set to false default value: false
    - `accounts` GenericLink: hypertext reference
      - `href` string, required: URI to be used. HREF stands for Hypertext REFerence.
      - `templated` boolean: This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570. Otherwise, this property must be absent or set to false default value: false

## Other responses

- `204`: No content.
- `400`: Invalid status value
- `401`: Unauthorized, authentication failure.
- `403`: Forbidden, authentication successful but access to resource is not allowed.
- `404`: Not found, no request available.
- `405`: Method Not Allowed.
- `406`: Not Acceptable.
- `408`: Request Timeout.
- `429`: Too many requests.
- `500`: Internal server error.
- `503`: Service unavailable.

---

[API](https://skmtc.dev/groupebpce/apis/accounts-information.md) - [All operations](https://skmtc.dev/groupebpce/apis/accounts-information/llms.txt) - [OpenAPI document](https://skmtc.dev/groupebpce/apis/accounts-information/revisions/1e8366574497?raw)