Read transaction list of an account.

GET 
/api/v1/accounts/:account-id/transactions

Read transaction reports or transaction lists of a given account addressed by "account-id", depending on the steering parameter "bookingStatus" together with balances.

For a given account, additional parameters are e.g. the attributes "dateFrom" and "dateTo". The ASPSP might add balance information, if transaction lists without balances are not supported.

Request

Path Parameters

account-id stringrequired

This identification is denoting the addressed account. The account-id is retrieved by using a "Read Account List" call.

Query Parameters

WithBalance 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. This parameter might be ignored by the ASPSP.
Example: false
dateFrom date
Conditional: Starting date (inclusive the date dateFrom) of the transaction list, mandated if no delta access is required and if bookingStatus does not equal "information".
For booked transactions, the relevant date is the booking date.
For pending transactions, the relevant date is the entry date, which may not be transparent neither in this API nor other channels of the ASPSP.
Example: 2024-03-20
dateTo date
End date (inclusive the data dateTo) of the transaction list, default is "now" if not given.
Might be ignored if a delta function is used.
For booked transactions, the relevant date is the booking date.
For pending transactions, the relevant date is the entry date, which may not be transparent neither in this API nor other channels of the ASPSP.
Example: 2024-03-25
entryReferenceFrom string

This data attribute is indicating that the AISP is in favour to get all transactions after the transaction with identification entryReferenceFrom alternatively to the above defined period. This is a implementation of a delta access. If this data element is contained, the entries "dateFrom" and "dateTo" might be ignored by the ASPSP if a delta report is supported.

Optional if supported by API provider

bookingStatus BookingStatusrequired

Possible values: [booked, pending, both, information, all]

Permitted codes are

• booked
• pending
• both
• information
• all

"booked" shall be supported by the ASPSP. To support the "pending" and "both" feature is optional for the ASPSP, Error code if not supported in the online banking frontend. If supported, "both" means to request transaction reports of transaction of bookingStatus either "pending" or "booked". To support the "information" feature is optional for the ASPSP. Currently the booking status “information” only covers standing orders. Error code if not supported. To support the "all" feature is optional for the ASPSP, Error code if not supported. If supported, "all" means to request transaction reports of transaction of any bookingStatus ("pending", "booked" or "information").

deltaList boolean

This data attribute is indicating that the AISP is in favour to get all transactions after the last report access for this PSU on the addressed account. This is another implementation of a delta access-report. This delta indicator might be rejected by the ASPSP if this function is not supported. Optional if supported by API provider

Header Parameters

X-Request-ID uuidrequired
ID of the request, unique to the call, as determined by the initiating party.
Example: c66d0ad3-4089-4996-bd48-523ae3e484f7
Consent-ID stringrequired
This then contains the consentId of the related AIS consent, which was performed prior to this payment initiation.
Example: 354c3126-be8c-4bcb-8cc6-0c317b8efb30
Digest string
Is contained if and only if the OpenBankingGateway.Models.Accounts.AISRequestHeaders.Signature element is contained in the header of the request.
Example: SHA-256=hl1/Eps8BEQW58FJhDApwJXjGY4nr1ArGDHIT25vq6A=
Signature string

A signature of the request by the TPP on application level. This might be mandated by ASPSP.

TPP-Signature-Certificate int32

A signature of the request by the TPP on application level. This might be mandated by ASPSP.

PSU-IP-Address string
Possible values: Value must match regular expression \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}
The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP. It shall be contained if and only if this request was actively initiated by the PSU.
Example: 192.168.8.78
PSU-IP-Port string
Possible values: Value must match regular expression [\d]
TThe forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.
Example: 1234
PSU-Accept string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Charset string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Encoding string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Language string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-User-Agent string

The forwarded Agent header field of the HTTP request between PSU and TPP, if available.

PSU-Http-Method PSUHttpMethod
Possible values: [GET, POST, PUT, PATCH, DELETE]
HTTP method used at the PSU ? TPP interface, if available. Valid values are:
• GET
• POST
• PUT
• PATCH
• DELETE
PSU-Device-ID string
UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID needs to be unaltered until removal from device.
Example: 99435c7e-ad88-49ec-a2ad-99ddcb1f5555
PSU-Geo-Location string
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
Example: GEO:52.506931;13.144558

Responses

200

Success

Response Headers

• X-Request-ID string

  ID of the request, unique to the call, as determined by the initiating party.

application/json

Schema

Schema

account object

Reference to an account by either

• IBAN, of a payment accounts, or
• BBAN, for payment accounts if there is no IBAN, or
• Not used by SDC the Primary Account Number(PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
• Not used by SDC the Primary Account Number(PAN) of a card in a masked form, or
• Not used by SDC an alias to access a payment account via a registered mobile phone number(MSISDN).
• A payment account AccountReferenceOther when using a national payment Form.

iban stringnullablerequired

Possible values: Value must match regular expression [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}

IBAN of the account.

bban stringnullablerequired

Basic Bank Account Number (BBAN) Identifier.

This data element can be used in the body of the consent request. Message for retrieving account access consent from this account. This data elements is used for payment accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN).

Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer

currency stringrequired

Possible values: non-empty, Value must match regular expression [A-Z]{3}

Account Currency Code.

transactions object
booked object[]nullable
Array of transaction details.
Array [
bookingDate stringnullablerequired
The date when an entry is posted to an account on the ASPSPs books
transactionId stringnullablerequired
This identification is given by the attribute transactionId of the corresponding entry of a transaction list.
creditorName stringnullablerequired
Creditor name.
creditorAccount object
Reference to an account by either
• IBAN, of a payment accounts, or
• BBAN, for payment accounts if there is no IBAN, or
• Not used by SDC the Primary Account Number(PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
• Not used by SDC the Primary Account Number(PAN) of a card in a masked form, or
• Not used by SDC an alias to access a payment account via a registered mobile phone number(MSISDN).
• A payment account AccountReferenceOther when using a national payment Form.
iban stringnullablerequired
Possible values: Value must match regular expression [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
IBAN of the account.
bban stringnullablerequired
Basic Bank Account Number (BBAN) Identifier.
This data element can be used in the body of the consent request. Message for retrieving account access consent from this account. This data elements is used for payment accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN).
Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Account Currency Code.
debtorName stringnullablerequired
debtorAccount object
Reference to an account by either
• IBAN, of a payment accounts, or
• BBAN, for payment accounts if there is no IBAN, or
• Not used by SDC the Primary Account Number(PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
• Not used by SDC the Primary Account Number(PAN) of a card in a masked form, or
• Not used by SDC an alias to access a payment account via a registered mobile phone number(MSISDN).
• A payment account AccountReferenceOther when using a national payment Form.
iban stringnullablerequired
Possible values: Value must match regular expression [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
IBAN of the account.
bban stringnullablerequired
Basic Bank Account Number (BBAN) Identifier.
This data element can be used in the body of the consent request. Message for retrieving account access consent from this account. This data elements is used for payment accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN).
Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Account Currency Code.
transactionAmount object
Base Model for amount.
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
amount stringrequired
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
• 1056
• 5768.2
• -1.50
• 5877.78
valueDate stringnullablerequired
The Date at which assets become available to the account owner in case of a credit.
]
pending object[]nullable
Array of transaction details.
Array [
transactionId stringnullablerequired
This identification is given by the attribute transactionId of the corresponding entry of a transaction list.
creditorName stringnullablerequired
Creditor name.
creditorAccount object
Reference to an account by either
• IBAN, of a payment accounts, or
• BBAN, for payment accounts if there is no IBAN, or
• Not used by SDC the Primary Account Number(PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
• Not used by SDC the Primary Account Number(PAN) of a card in a masked form, or
• Not used by SDC an alias to access a payment account via a registered mobile phone number(MSISDN).
• A payment account AccountReferenceOther when using a national payment Form.
iban stringnullablerequired
Possible values: Value must match regular expression [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
IBAN of the account.
bban stringnullablerequired
Basic Bank Account Number (BBAN) Identifier.
This data element can be used in the body of the consent request. Message for retrieving account access consent from this account. This data elements is used for payment accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN).
Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Account Currency Code.
debtorName stringnullablerequired
debtorAccount object
Reference to an account by either
• IBAN, of a payment accounts, or
• BBAN, for payment accounts if there is no IBAN, or
• Not used by SDC the Primary Account Number(PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
• Not used by SDC the Primary Account Number(PAN) of a card in a masked form, or
• Not used by SDC an alias to access a payment account via a registered mobile phone number(MSISDN).
• A payment account AccountReferenceOther when using a national payment Form.
iban stringnullablerequired
Possible values: Value must match regular expression [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
IBAN of the account.
bban stringnullablerequired
Basic Bank Account Number (BBAN) Identifier.
This data element can be used in the body of the consent request. Message for retrieving account access consent from this account. This data elements is used for payment accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN).
Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Account Currency Code.
transactionAmount object
Base Model for amount.
currency stringrequired
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
amount stringrequired
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
• 1056
• 5768.2
• -1.50
• 5877.78
valueDate stringnullablerequired
The Date at which assets become available to the account owner in case of a credit.
]

Example (from schema)

{
  "account": {
    "iban": "string",
    "bban": "string",
    "currency": "EUR"
  },
  "transactions": {
    "booked": [
      {
        "bookingDate": "string",
        "transactionId": "string",
        "creditorName": "string",
        "creditorAccount": {
          "iban": "string",
          "bban": "string",
          "currency": "EUR"
        },
        "debtorName": "string",
        "debtorAccount": {
          "iban": "string",
          "bban": "string",
          "currency": "EUR"
        },
        "transactionAmount": {
          "currency": "EUR",
          "amount": "5877.78"
        },
        "valueDate": "string"
      }
    ],
    "pending": [
      {
        "transactionId": "string",
        "creditorName": "string",
        "creditorAccount": {
          "iban": "string",
          "bban": "string",
          "currency": "EUR"
        },
        "debtorName": "string",
        "debtorAccount": {
          "iban": "string",
          "bban": "string",
          "currency": "EUR"
        },
        "transactionAmount": {
          "currency": "EUR",
          "amount": "5877.78"
        },
        "valueDate": "string"
      }
    ]
  }
}

Example 1.

{
  "account": {
    "iban": "AL4820511014241481CLPECFEUR0",
    "bban": "401241481CLPECFEUR06",
    "currency": "EUR"
  },
  "transactions": {
    "booked": [
      {
        "bookingDate": "2017-10-25",
        "transactionId": "5ed28002-df27-4665-ba3d-2ae3676785f9",
        "creditorName": "John Smith",
        "creditorAccount": {
          "iban": "AL5920511014241481CLPECLALLA",
          "bban": "401241481CLPECLALLAZ",
          "currency": "ALL"
        },
        "transactionAmount": {
          "currency": "EUR",
          "amount": "250"
        },
        "valueDate": "2017-10-26"
      },
      {
        "bookingDate": "2017-10-25",
        "transactionId": "3fd51675-bb06-46c0-8a81-3e5a44cbbfb3",
        "creditorAccount": {
          "iban": "AL1020511014241481CLPECFUSDN",
          "bban": "401241481CLPECFUSDNT",
          "currency": "USD"
        },
        "debtorName": "Sebastian Moore",
        "transactionAmount": {
          "currency": "EUR",
          "amount": "25"
        },
        "valueDate": "2017-10-26"
      }
    ],
    "pending": null
  }
}

401

Unauthorized

403

Forbidden

Loading...