GET
/
v3
/
SUSPENDED
[
  {
    "id": "<string>",
    "linkId": "<string>",
    "transactionDate": "2019-01-28T00:00:00",
    "postingDate": "2019-01-28T00:00:00",
    "postingStatus": "POSTED",
    "responseCode": "1A",
    "transactionType": {
      "authorizationType": "AUTH",
      "code": "<string>",
      "name": "<string>"
    },
    "acquiringInstitutionIdentificationCode": "<string>",
    "settlementAmount": {
      "amount": 3.14,
      "currency": "EUR"
    },
    "transactionAmount": {
      "amount": 3.14,
      "currency": "EUR"
    },
    "paymentReference": "<string>",
    "payerName": "<string>",
    "fromAddress": "<string>",
    "fromZip": "<string>",
    "fromCity": "<string>",
    "fromBankAccountNumber": "<string>",
    "fromCustomerAccountNumber": "<string>",
    "fromOrganizationalNumber": "<string>",
    "fromBankAccountType": "BBAN",
    "fromBankName": "<string>",
    "toBic": "<string>",
    "discLinkTransactionId": "<string>",
    "fileName": "<string>",
    "toBankAccountNumber": "<string>",
    "toBankAccountType": "BBAN",
    "reason": "<string>"
  }
]

Query Parameters

​
auditUser
string
required

The audit user to log the request

​
fromDate
string<date-time>

From which date you want to list the transactions in ISO-8601 date-time format.

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.

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

​
linkId
string

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"

​
transactionType
object
​
acquiringInstitutionIdentificationCode
string

Acquiring Institution Identification Code

​
settlementAmount
object

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

​
transactionAmount
object

Amount including currency

​
paymentReference
string

Reference number used for the transaction

​
payerName
string

Name of the payer for the transaction

​
fromAddress
string

Address of payer

​
fromZip
string

Zip code of payer

​
fromCity
string

City of payer

​
fromBankAccountNumber
string

Source account number

​
fromCustomerAccountNumber
string

from the Enfuce system, where the payment was posted

​
fromOrganizationalNumber
string

Send organization number

​
fromBankAccountType
enum<string>

The type of bank account

Available options:
BBAN,
IBAN,
PLUSGIRO,
BANKGIRO
​
fromBankName
string

Source bank name

​
toBic
string

Target BIC code, used for pain file generation

​
discLinkTransactionId
string

The transactionId of the original financial transaction of this discount

​
fileName
string

Name of processed file, typically for managing incoming payments.

​
toBankAccountNumber
string

Target account number

​
toBankAccountType
enum<string>

The type of bank account

Available options:
BBAN,
IBAN,
PLUSGIRO,
BANKGIRO
​
reason
string

Reason for the suspension of the transaction