Handle the payment result

🚧
Early release
Online payments is in early development (MVP). This section may change.

When the shopper is done, three things tell you what happened. Use each for its own job.

Signal	Comes from	Use it to
Return URL	The shopper's browser goes to your success, cancel or error URL	Show the shopper the right page
Notification	Aera calls your server	Know the session is completed, then check the status
Get payment status	You call Aera	Get the confirmed result and every operation on the payment

Never ship an order based on the return URL alone. The shopper can close the browser before it loads, or open it themselves. Always confirm on your server.

Return URLs

You set the three URLs in merchantData when you create the session:

Field	Aera sends the shopper here when
`successRedirectUrl`	The payment succeeded
`cancelRedirectUrl`	The shopper cancelled
`errorRedirectUrl`	The payment failed

Get the payment status

GET /v1/{pspReference}/status

You don't need an idempotency-key. The call doesn't change the payment, so you can make it as often as you need.

Example Get payment status response

{
  "responseInfo": { "responseCode": "0", "timeStamp": "2026-10-20T10:23:19.279Z" },
  "status": "AUTHORIZED",
  "merchantReference": "order-1234",
  "amountDetails": { "amount": 15000, "currency": "NOK" },
  "operationList": [
    { "id": "01J9X5Z9K8W4F8H3ZQ6D1M2N3P", "type": "CREATE_SESSION", "status": "COMPLETED", "details": {} },
    { "id": "01J9X60ABCDEF123456789GHJK", "type": "AUTHENTICATION", "status": "COMPLETED", "details": { "eci": "05" } },
    {
      "id": "01J9X61MNOPQR123456789STUV",
      "type": "AUTHORIZATION",
      "status": "COMPLETED",
      "details": {
        "amount": 15000,
        "currency": "NOK",
        "acquirer": "123456",
        "scheme": "VISA",
        "authCode": "123456"
      }
    }
  ]
}

How to read it

status is the payment's current state. See Payment lifecycle.
operationList lists every operation on the payment, oldest first. Some operations, such as captures and refunds, can appear several times.
Each operation has a type, a status and details. Which details fields are filled depends on the type. For example, AUTHENTICATION has eci (the Electronic Commerce Indicator, which shows how the shopper was authenticated).

Operation `type`	Meaning
`CREATE_SESSION`	The payment session was created
`AUTHENTICATION`	The shopper authenticated, for example with 3-D Secure
`AUTHORIZATION`	The payment was authorised
`CAPTURE`	An amount was captured
`CANCEL`	An amount was cancelled
`REFUND`	An amount was refunded
`UPDATE`	The authorisation was changed

Operation `status`	Meaning
`COMPLETED`	It succeeded
`PENDING`	It is still in progress
`FAILED`	It failed

With immediateCapture set to true, a successful payment has both AUTHORIZATION and CAPTURE.

References you may need later

The details of the authorisation can also contain:

Field	Use it for
`pspShopperId`	Aera's ID for the shopper. Send it in later sessions to show their saved cards.
`paymentInstrumentReference`	The saved card, if the shopper saved it. Use it to pre-select or delete the card.
`recurringReference`	The recurring agreement, if one was created. Use it in Authorize recurring payment.

What to do next

Result	Next step
Authorised, not captured	Capture when you ship, or cancel
Captured	Ship. Refund if needed
Failed or cancelled	Let the shopper try again with a new payment session