improved

Sync ID Returned on Auth Request Complete

When completing an AIS connection using our auth requests feature, you will now get the syncId returned in the payload. This will allow you to track the status of the sync that completes the connection in the case of using enableAsync

fixed

Asset Account Provider Names Returned

Previously, if an asset account was created and a provider name was given, that provider name wouldn't be returned when retrieving accounts. Provider names are now returned when getting accounts for asset types.

added

New endpoint GET /accounts-list

Update on GET /accounts-list endpoint.

improved

Session Not Found Checks

There had been more instances of Session Not Found pages showing up when returning from bank consents. The reasons this was happening were:

added

Code Samples

We have released a repository that will demonstrate how to communicate with out APIs in various programming languages. Documentation can be found here

added

Variable Recurring Payments (VRP)

Variable Recurring Payments can now be created for banks that support them. VRPs allow a single consent to be created for multiple payments, with the ability to set limits on the time and amount

added

New Connection: Wise (formerly Transferwise)

improved

Payments without a payeeId

We have added a new feature to our payment auth requests, including standing orders and recurring payments.

improved

Default Initial Consent From Periods

We now make use of the initial transactions month history information we get for our banking providers (made available in our connection list) to allow our clients to retrieve more than the usual 12 months of transactions on initial connection.
If the banking provider gives us information on how far back they can go for transactions, we will either go the full length they provide, or 36 months by default (which ever is shortest). So for example:

fixed

Payee Schema Validation

Inputs for payee details like sort code and account number are validated correctly, returning a HTTP 400 Bad Request response with the correct body describing what format is expected for the given fields.