Get Payment Status

Use this endpoint to retrieve the full status of a payment.

The status response includes all operations performed on the payment.

If the payment consists of multiple operations, the response returns the complete operation history.


Endpoint

GET /v1/{pspReference}/status
  • {pspReference} — the unique payment identifier you received when you created the payment session.
  • You do not need to include the idempotency-key (a header that prevents duplicate requests) for status requests.

Example Request

GET /v1/{pspReference}/status

Example Response

{
  "responseInfo": {
    "responseCode": 0,
    "responseText": "Success"
  },
  "operationList": [
    {
      "id": "01J9X5Z9K8W4F8H3ZQ6D1M2N3P",
      "type": "CREATE_SESSION",
      "status": "COMPLETED",
      "details": {}
    },
    {
      "id": "01J9X60ABCDEF123456789GHJKL",
      "type": "AUTHENTICATION",
      "status": "COMPLETED",
      "details": {
        "eci": "05"
      }
    },
    {
      "id": "01J9X61MNOPQR123456789STUVW",
      "type": "AUTHORIZATION",
      "status": "COMPLETED",
      "details": {
        "amount": 15000,
        "currency": "NOK",
        "acquirer": "ExampleAcquirer",
        "scheme": "VISA",
        "authCode": "123456",
        "pspShopperId": "Example pspShopperId if applicable",
        "merchantShopperId": "Example merchantShopperId if applicable",
        "paymentInstrumentReference": "Example reference if applicable",
        "recurringReference": "Example reference if recurring payment"
      }
    }
  ]
}

Field Reference

Path Parameter

FieldTypeRequiredDescription
pspReferencestring (UUID v7, a time-sortable universally unique identifier)YesThe unique payment identifier you received when you created the session.

Response

responseInfo

FieldTypeRequiredDescription
responseCodeintegerYesA code indicating the request result.
responseTextstringYesA human-readable description of the result.

operationList

Array containing all operations performed on the payment.

Each entry represents one lifecycle event.

FieldTypeRequiredDescription
idstring (ULID, a time-sortable unique identifier)YesThe unique identifier Aera assigns to this operation.
typestringYesThe operation type (e.g., CREATE_SESSION, AUTHENTICATION, AUTHORIZATION, CAPTURE, CANCEL, REFUND, UPDATE).
statusstringYesThe operation status (e.g., COMPLETED, PENDING, FAILED).
detailsobjectNoOperation-specific details. The structure varies by operation type.

Operation Types

The type field may include:

  • CREATE_SESSION
  • AUTHENTICATION
  • AUTHORIZATION
  • CAPTURE
  • CANCEL
  • REFUND
  • UPDATE

Important Notes

  • The status endpoint returns the complete lifecycle of the payment.
  • The response lists operations in chronological order.
  • Some operations (such as refunds) can appear multiple times.
  • The details object varies depending on the operation type. For example, the AUTHENTICATION operation includes an eci field (Electronic Commerce Indicator, a value indicating the authentication level).
  • You can call this endpoint multiple times — it does not modify payment state.

Did this page help you?