GET
/
v3
/
account
/
{accountId}
[
  {
    "id": "<string>",
    "linkId": "<string>",
    "transactionDate": "2019-01-28T00:00:00",
    "postingDate": "2019-01-28T00:00:00",
    "postingStatus": "POSTED",
    "responseCode": "1A",
    "responseDescription": "061-Usage Limit \"24H_RETAIL\" Amount Exceeded",
    "transactionType": {
      "authorizationType": "AUTH",
      "code": "<string>",
      "name": "<string>"
    },
    "transactionConditionCode": "ATM",
    "retrievalReferenceNumber": "<string>",
    "authorizationCode": "<string>",
    "acquiringInstitutionIdentificationCode": "<string>",
    "cardAcceptorIdentificationCode": "<string>",
    "submerchantId": "<string>",
    "settlementAmount": {
      "amount": 3.14,
      "currency": "EUR"
    },
    "transactionAmount": {
      "amount": 3.14,
      "currency": "EUR"
    },
    "feeAmount": {
      "amount": 3.14,
      "currency": "EUR"
    },
    "merchant": {
      "country": "FIN",
      "city": "Helsinki",
      "name": "Airline of the world",
      "mcc": 3016
    },
    "text": "<string>",
    "paymentReference": "<string>",
    "payerName": "<string>",
    "paymentReceiver": "<string>",
    "fromAddress": "<string>",
    "fromZip": "<string>",
    "fromCity": "<string>",
    "fromBankAccountNumber": "<string>",
    "toBankAccountNumber": "<string>",
    "fromCustomerAccountNumber": "<string>",
    "fromOrganizationalNumber": "<string>",
    "fromBankName": "<string>",
    "fromBankAccountType": "BBAN",
    "toBankAccountType": "BBAN",
    "toBic": "<string>",
    "discLinkTransactionId": "<string>",
    "createdAt": "2019-01-28T00:00:00",
    "fileName": "<string>",
    "processedByEnfuceStip": true,
    "receivedFromCollectionAgency": true,
    "acqRefNumber": "<string>",
    "cardId": "<string>"
  }
]

Path Parameters

accountId
string<biginteger>
required

The account id to fetch list of transactions for

Query Parameters

auditUser
string
required

The audit user to log the request

transactionsOnly
boolean
default:false

List only transactions. This will exclude authorisations that have not yet been cleared.

fromDate
string<date-time>

From which date you want to list the transactions in ISO-8601 date-time format. If null, then toDate must also be null. This is the date of the transaction's authorisation.

Example:

"2019-01-28T00:00:00"

toDate
string<date-time>

To which date you want to list the transactions in ISO-8601 date-time format. If null, then fromDate must also be null. This is the date of the transaction's authorisation.

Example:

"2019-01-28T00:00:00"

page
integer
default:0

Current page

size
integer
default:15

How many transactions should be returned per page, default is 15. Cannot be more than 30.

Required range: 1 < x < 30

Response

Successful lookup of transactions

id
string

Unique transaction id

Unique Root id for the transaction or Authorization

transactionDate
string<date-time>

The local date (and time) when the transaction was made. I.e. the date/time in the time zone in which the payment terminal/merchant is. In date-time format YYYY-MM-DDThh:mm:ss. Please note that the authorisation and clearing formats used by card schemes for do not support conveying the time zone in which the transaction has been done. The card scheme may also just include the date and no specific time. Enfuce relays the date and time as received from the card scheme.

Example:

"2019-01-28T00:00:00"

postingDate
string<date-time>

The date and time when transaction was posted at Enfuce. In date-time format YYYY-MM-DDThh:mm:ss. Timezone is Enfuce system timezone, i.e. UTC.

Example:

"2019-01-28T00:00:00"

postingStatus
enum<string>

Posting status values:

  • POSTED - Transaction/authorization has been successfully posted.
  • POSTED_DISPUTE - Transaction has been posted with the dispute contract.
  • CLOSED - Authorization status after its matching transaction was successfully processed, or if the authorization is expired.
  • PENDING - Transaction/authorization is waiting for processing or being processed.
  • REJECTED - Transaction/authorization was rejected.
Available options:
POSTED,
POSTED_DISPUTE,
CLOSED,
PENDING,
REJECTED
Example:

"POSTED"

responseCode
string

After authorization, Enfuce generates a response code that guides the merchant how to proceed with the purchase. If approved (Response code 0 or 10), the purchase is finalized. If declined (Response code is not 0 or 10), the merchant must cancel the purchase or request an alternative payment method. Refer to our service description for a complete list of response codes and their usage details. Response code values according to ISO-8583:1987:

  • Approved: 0 or 10
  • Declined: 3-96 and 1A, N0, N7
Example:

"1A"

responseDescription
string

When a payment is declined, a response description is returned, if available, providing more context on why the transaction failed. This includes a return code and a brief explanation. If multiple issues cause the decline, only one response description is sent, prioritized as the most relevant for the decline. Refer to our service description for the list of most relevant response descriptions and their usage details.

Example:

"061-Usage Limit \"24H_RETAIL\" Amount Exceeded"

transactionType
object
transactionConditionCode
string

Transaction conditions define the specific circumstances under which a card transaction occurred. For example, they describe whether the chip was read or if the transaction was contactless, how the cardholder was authenticated, and whether the transaction was e-commerce or card-present. For more information, see our Transaction Conditions Service Description.

Example:

"ATM"

retrievalReferenceNumber
string

Retrieval reference number

authorizationCode
string

Authorization code

acquiringInstitutionIdentificationCode
string

Acquiring Institution Identification Code

cardAcceptorIdentificationCode
string

Card Acceptor Identification Code

submerchantId
string

Related to cardAcceptorIdentificationCode, represents sub card acceptor

settlementAmount
object

Settlement amount summed up with markup fee (if markup fee is persent)

transactionAmount
object

Amount including currency

feeAmount
object

Summed up other fees

merchant
object
text
string

Represents value of text field provided during transaction posting

Maximum length: 255
paymentReference
string

Reference number used for the transaction

payerName
string

First and last name of payer

paymentReceiver
string

Payment receiver name

fromAddress
string

Address of payer

fromZip
string

Zip code of payer

fromCity
string

City of payer

fromBankAccountNumber
string

Source account number

toBankAccountNumber
string

Target account number

fromCustomerAccountNumber
string

from the Enfuce system, where the payment was posted

fromOrganizationalNumber
string

Send organization number

fromBankName
string

Source bank name

fromBankAccountType
enum<string>

The type of bank account

Available options:
BBAN,
IBAN,
PLUSGIRO,
BANKGIRO
toBankAccountType
enum<string>

The type of bank account

Available options:
BBAN,
IBAN,
PLUSGIRO,
BANKGIRO
toBic
string

Target BIC code, used for pain file generation

The transactionId of the original financial transaction of this discount

createdAt
string<date-time>

The date and time in YYYY-MM-DDThh:mm:ss format when transaction was created. Timezone is Enfuce system timezone, i.e. UTC.

Example:

"2019-01-28T00:00:00"

fileName
string

Name of processed file, typically for managing incoming payments.

processedByEnfuceStip
boolean

For authorizations, indicates whether authorization was processed by Enfuce STIP or not.

receivedFromCollectionAgency
boolean

Whether a collection payment transaction (CPT) is received from a collection agency or not. Only applies to payment transactions for invoices in collection.

acqRefNumber
string

Acquirer Reference Number (ARN) is a unique number assigned to a card transaction by the acquirer (merchant's bank). It is used to track a specific transaction across banks (merchant bank, cardholder bank, etc.).

cardId
string

If transaction is posted to a card then this cardId will be set