API version log

2026.04.01

🚀
Released: 30.04.2025

📔 DOCUMENTATION: New Response code and added some missing descriptions/examples added.
- 68513 = Invalid CVD signature.
⚙️ FEATURE: New full hybrid payment flow, where full amount no longer has to be covered in full by a firm funding source.
⚙️ FEATURE: Added support for multiple firm funding sources in the same transaction (in preparations for Bancontact).
🐛 BUGFIX: Onboarding the same payment instrument multiple times to the same wallet (which should only result in override of existing information about that payment instrument) caused a broken state for the payment instrument priority. This could be seen as a "Duplicate key error" and cause errors during opening the wallet dashboard, as well as during transactions.
🐛 BUGFIX: Now sending currency on all sub-transactions/payment instruments listed in transactionDetails in Merchant callback.
🐛 BUGFIX: Not sending payment instruments with status AUTHORIZATION_PENDING In merchant callback. Neither when transactions fail, nor when success. All payment instruments should have reached a "final state" before sending callback to merchant/ECR.
🐛 BUGFIX: For full hybrid payment, now showing correct amount on firm funding source in transactionDetails when amount is reallocated from voucher to firm funding source.
🔒SECURITY: Internal security patches.

2026.04.00

🚀
Released: 22.04.2025

New Response codes
Extend PSP -> WLW apis to support new/updated fields (amountDetails and transactionDetails) for the following functionality:
- Get transaction status (ECR -> PSP)
- Merchant callback (PSP -> ECR)
❗️
Temporary reduced wait time before WSP events are sent (60s -> 10s). Will be adjusted back later this year.
Bugfix:
- Empty string for redirect_uri from DPA will cause a bad request exception (HTTP status 400) and in turn a controlled error from the Wallets SDK.
- Sending Merchant callback even in error scenarios.

Internal changes (not effecting WSP)

Internal security patches.
Implemented stability for API calls to internal Aera services and balance checks.

2026.03.01

🚀
Released: 31.03.2025

New features

New Wallet Management API endpoint for creating session that can be used for initiating onboarding of a payment instrument: Create payment instrument session.
- This endpoint introduces a new "concept": paymentInstrumentType. Read more about "Participating Payment System VS Payment Instrument Type" here.
- This endpoint also introduces a new WLW Response code 68708.
DPA can now configure a set of allowed redirect URLs.
- 📘
  Note: This list of URLs has to be communicated to Aera, and Aera will then add them to the DPA configuration in our systems.
Add support for XTRA acquiring using the Aera PSP.

2026.03.00

🚀
Released: 20.03.2025

WSP API changes

Added new field (proprietaryData) will be received by the WLW, from the ECR/PSP and passed on the WSP in the Process WLW transaction init request and Process WLW transaction result request requests.

Functional changes to the WLW

WLW is now integrated to the real Aera PSP.
If a consumer tries to add the same payment instrument twice to the same wallet, WLW will no longer return an error. It will accept the new information and overwrite the existing payment instrument.

❗️
A re-onbarding for all wallets is needed.

2026.02.00

🚀
Released: 23.02.2025

📘
This release contains no changes to the WLW API specifications.

Aera PSP API docs

We have updated the Aera PSP API documentation.

Other Updates

General security patches
Now sending dateOfBirth to XTRA issuing API during onboarding of XTRA payment instruments.

2026.01.00

Bugfixes

Made sure to always populate the field sessionExpirationTime when WLW is calling the WSP endpoint: Process WLW transaction init request

2025.12.00

🚀
Released: 19.12.2025

New WSP wallet management endpoints

Updated response body for Get Wallet details

The following fields (in the root object) is now controlled by the WSP:

email
loyaltyId
phoneNumber

❗️
This means that Aera will not populate these fields, unless provided by the WSP using the Update Wallet details endpoint.

In the response body we have added a new field called userInfo, this field contains personal information, which Aera acquires during a wallet onboarding. The content of this field can't be updated by the WSP, only by the consumer when performing an onboarding.

❗️
This means that, for example the email field within userInfo may not be the same as the email field on the root level.

New query parameters for Get Wallet details

includeSDKInfo = When set to true this will populate the list sdkIds with the id of all the SDKs associated with this wallet.
includeUserInfo = When set to true this will populate the userInfo field.
- 📘
  For userInfo to be available, consumers have to perform a new onboarding (you do not need to delete the whole wallet).

Other small improvements

No longer require the field identityTrustAnchor on Create Xtra Payment Instrument.
- 🚧
  A default value is hard coded until we receive information from Xtra regarding what can be a valid value.
Sending WSP events when onboarding an XTRA payment instrument.
Expanded the data field within the WSP events for payment instrument onboarding to include:
- maskedPan
- nickname
Now sending WSP events both when a consumer or WSP delete a single payment instrument from a wallet.

2025.11.00

🚀
Released: 5.12.2025

New page for response codes

Response codes

Updated demo PSP headers

Added the following headers, to make the demo PSP even more similar to the actual PSP:

idempotency-key

❗️
The DemoPSP must be treated as what it is; a demo application. Changes in the API specification may still be needed to successfully integrate towards the real Aera PSP.

New request body examples for transactions

Request examples

Updated request/response examples in API Reference for each endpoint

Duplicate validation

Consumers will no longer be able to onboard the same MONIZZE account (duplicates) multiple times to the same wallet. The same MONIZZE account can still be onboard to multiple wallets.
- Note: duplicate validation does only work for MONIZZE accounts added to a wallet after this release. It is suggested to re-onboard any existing MONIZZE accounts.
Duplicate XTRA accounts, with the same IBAN can't be onboard to the same wallet. The same XTRA account can still be onboard to multiple wallets.

New Session details endpoint

See Wallet Session Management for more details. You can find the API specifications here.

2025.10.01

🚀
Released: 31.10.2025

WSP Management API

New endpoint for onboarding XTRA payment instruments

New transaction status

SIGNED = Consumer has signed transaction and it is no longer possible to cancel the transaction.

Explicitly clarifying expectations related to normal handling of Aera Wallet API.

2025.10.00

🚀
Released: 31.10.2025

WLW ➡️ WSP integration changes

Changed field(s) in Process WLW transaction init request
- sessionId within the session object was always equal to the field transactionId. To be consistent, we have removed the field transactionId, meaning you should rely on sessionId within the session object.
- Removed status field.
Change field Process WLW transaction result request.
- transactionId ➡️ sessionId
Change field in Process WLW events:
- In the data field you have been able to expect a transactionId when receiving transaction events, this field has now changed to sessionId. See example event in WSP Events table.

ECR ➡️ PSP integration changes

New endpoints that will replace old endpoints:

2025.09.00

🚀
Released: 30.09.2025

`DYNAMIC_SDKID`

Now support use of DYNAMIC_SDKID when initiating transactions towards Aera demo PSP.

2025.08.00

🚀
Released: 29.08.2025

WSP Events have been implemented. See page WSP Events for examples, as well as what type of events you can expect at this time.
New endpoint for deleting single wallet sdk.
New endpoint in demo PSP for canceling a transaction.
New field sent to transaction-init and transaction-result requests:
- status = transactions status. See page "Transactions" for details about each possible status.