Read transaction details

Use the Apaleo Payment API to look up details about any payment transaction. This is useful for debugging payment issues, reconciling charges, or checking the status of a specific transaction.

Required scope: payment:transactions.read must be enabled in your app to use these endpoints.

Look up by PSP reference

Use this when you have the pspReference returned from the Adyen /payments call. This is the most common lookup — the pspReference is returned on every successful authorisation and should be stored by your application.

GET /payment/v1/transactions/{pspReference}

The response includes a full event journal showing every action taken on the transaction — authorisations, captures, refunds, and refusals — in chronological order.

{
  "pspReference": "8815360785594505",
  "amount": {
    "currency": "EUR",
    "value": 190
  },
  "merchantReference": "YOUR_ORDER_REFERENCE",
  "merchantAccountCode": "MyHotelCOM",
  "terminalId": "T400-1234567",
  "originalFolioId": "XKCDER-1-1",
  "propertyId": "BER",
  "journal": [
    {
      "pspReference": "8815360785594505",
      "amount": {
        "currency": "EUR",
        "value": 190
      },
      "eventCode": "AUTHORISATION",
      "dateTime": "2021-09-08T04:42:19.1650234Z",
      "isSuccess": false,
      "reason": "Refused",
      "refusalReason": "05 : Do not honor"
    },
    {
      "pspReference": "862623095673169A",
      "amount": {
        "currency": "EUR",
        "value": 100
      },
      "eventCode": "CAPTURE",
      "dateTime": "2021-09-08T04:43:19.1650286Z",
      "isSuccess": true
    },
    {
      "pspReference": "862623087842791E",
      "amount": {
        "currency": "EUR",
        "value": 90
      },
      "eventCode": "CAPTURE",
      "dateTime": "2021-09-08T04:44:19.1650295Z",
      "isSuccess": true
    },
    {
      "pspReference": "862623094473133B",
      "amount": {
        "currency": "EUR",
        "value": 10
      },
      "eventCode": "REFUND",
      "dateTime": "2021-09-08T05:14:19.1650308Z",
      "isSuccess": false
    }
  ]
}

Understanding the journal

Each entry in the journal array represents one event on the transaction:

Field	Description
`pspReference`	The unique Adyen reference for this specific event. Captures and refunds each get their own reference.
`eventCode`	The type of event: `AUTHORISATION`, `CAPTURE`, `REFUND`, `CANCELLATION`.
`isSuccess`	Whether the event succeeded.
`reason`	A human-readable reason, present on failures.
`refusalReason`	The raw acquirer response code on refused transactions. See the Adyen raw acquirer responses documentation for a full list.

A transaction can have multiple captures if a pre-authorization was split across folios. Each capture appears as a separate journal entry with its own pspReference and amount.

Look up by merchant reference

Use this when you do not have the pspReference — for example, when a guest did not complete a 3D Secure redirect and the final pspReference was never returned to your application.

GET /payment/v1/transactions?merchantReference={merchantReference}

The merchantReference is the reference value your application sent in the original Adyen /payments request. Always store this alongside the pspReference so you have a fallback for lookups.

The response has the same structure as the PSP reference lookup above.