API version log
Features and changes in the Wallets API
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:
emailloyaltyIdphoneNumber
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
userInfomay not be the same as the
New query parameters for Get Wallet details
includeSDKInfo= When set totruethis will populate the listsdkIdswith the id of all the SDKs associated with this wallet.includeUserInfo= When set totruethis will populate theuserInfofield.-
For
userInfoto 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
identityTrustAnchoron 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
datafield within the WSP events for payment instrument onboarding to include:maskedPannickname
- 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
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
Updated request/response examples in API Reference for each endpoint

WSP Events example
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
sessionIdwithin thesessionobject was always equal to the fieldtransactionId. To be consistent, we have removed the fieldtransactionId, meaning you should rely onsessionIdwithin thesessionobject.- Removed
statusfield.
- Change field Process WLW transaction result request.
transactionId➡️sessionId
- Change field in Process WLW events:
- In the
datafield you have been able to expect atransactionIdwhen receiving transaction events, this field has now changed tosessionId. See example event in WSP Events table.
- In the
ECR ➡️ PSP integration changes
- New endpoints that will replace old endpoints:
2025.09.00
Released: 30.09.2025
DYNAMIC_SDKID
DYNAMIC_SDKIDNow 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.
Updated about 1 month ago
