Path Parameters
The account id to fetch list of transactions for
Query Parameters
The audit user to log the request
List only transactions. This will exclude authorisations that have not yet been cleared.
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.
"2019-01-28T00:00:00"
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.
"2019-01-28T00:00:00"
Current page
How many transactions should be returned per page, default is 15. Cannot be more than 30.
1 < x < 30
Response
Successful lookup of transactions
Unique transaction id
Unique Root id for the transaction or Authorization
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.
"2019-01-28T00:00:00"
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.
"2019-01-28T00:00:00"
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.
POSTED
, POSTED_DISPUTE
, CLOSED
, PENDING
, REJECTED
"POSTED"
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
"1A"
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.
"061-Usage Limit \"24H_RETAIL\" Amount Exceeded"
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.
"ATM"
Retrieval reference number
Authorization code
Acquiring Institution Identification Code
Card Acceptor Identification Code
Related to cardAcceptorIdentificationCode, represents sub card acceptor
Settlement amount summed up with markup fee (if markup fee is persent)
Amount including currency
Summed up other fees
Represents value of text
field provided during transaction posting
255
Reference number used for the transaction
First and last name of payer
Payment receiver name
Address of payer
Zip code of payer
City of payer
Source account number
Target account number
from the Enfuce system, where the payment was posted
Send organization number
Source bank name
The type of bank account
BBAN
, IBAN
, PLUSGIRO
, BANKGIRO
The type of bank account
BBAN
, IBAN
, PLUSGIRO
, BANKGIRO
Target BIC code, used for pain file generation
The transactionId of the original financial transaction of this discount
The date and time in YYYY-MM-DDThh:mm:ss format when transaction was created. Timezone is Enfuce system timezone, i.e. UTC.
"2019-01-28T00:00:00"
Name of processed file, typically for managing incoming payments.
For authorizations, indicates whether authorization was processed by Enfuce STIP or not.
Whether a collection payment transaction (CPT) is received from a collection agency or not. Only applies to payment transactions for invoices in collection.
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.).
If transaction is posted to a card then this cardId will be set