Changelog

🇩🇪 Sparda München: Update to Open Banking Flow
Sparda München has changed its Open Banking technology provider, resulting in a shift from the redirect flow to an embedded flow. Please update the integration accordingly.

Fineco institution in Italy
The 'UNKNOWN' account type for AIS/Data requests from Fineco (Italy) will be replaced with specific account types per Yapily API specifications, Please see Get Account.
Please review your current usage of the 'UNKNOWN' account type and prepare to use the new, specific account types per your business needs.

🇳🇱 New Bank Integration: Knab Netherlands
We're excited to announce a new integration in Netherlands — Knab is now available!
You can now connect to and initiate payments with Knab. This connection supports both AIS (Account Information Services) and PIS (Payment Initiation Services).

Deprecation Notice: Legacy Endpoints Now Deprecated
As previously communicated, the following legacy endpoints have now been officially deprecated and are scheduled for removal from Production:

/features – This endpoint, which listed all features supported by Yapily, is deprecated. Please use Get Institutions instead, which provides institution-specific features and geographic coverage.

/me – This endpoint, used to retrieve application metadata and institution details, is no longer supported. For metadata, use Get application details. For institution information, refer to Get Institutions.

Please update your integrations as soon as possible to avoid any disruption. For guidance on transitioning to the updated endpoints, feel free to contact our support team.

DataPlus Enrichment Only
DataPlus Enrichment Only API - this API enhancement allows customers to submit their own transaction data and categorise them useful links:

Yapily Data Plus

Tutorial: Getting Enrichment Only

Enrichment

⚡️ SEPA Instant Enabled for Deutsche Bank Group
We're pleased to announce that SEPA Instant payments are now supported for the Deutsche Bank Group.
You can now initiate real-time payments with the following institutions:

Deutsche Bank

Norisbank

Postbank

Payments are processed instantly, ensuring faster and more efficient transactions

🇦🇹 New Bank Connection: Volksbank Austria
We're excited to announce a new integration in Austria — Volksbank Austria is now available!
You can now connect to and initiate payments with Volksbank Austria. This connection supports both AIS (Account Information Services) and PIS (Payment Initiation Services).
For the full list of supported institutions within this group, please visit our Institution configuration page.

Hosted Payments: We’ve introduced a key enhancement to our hosted payment journey, streamlining the process for banks that require Payer IBAN and Name. Previously, the PSU (Payment Service User) was always prompted to provide this information. With our latest update, when the Payer IBAN and Name are included in the payload, they will no longer be requested from the PSU.

Intesa Sanpaolo introduced a change on their open banking API: retail and corporate accounts were split out to two separate API endpoints.
As a result, Yapily API now has two separate Intesa Sanpaolo institutions:
The existing institution Intesa Sanpaolo from now on will provide access only to retail accounts.
New institution Intesa Sanpaolo (Corporate) will provide access to corporate accounts. For new consents, Yapily customers will need to redirect their corporate account PSUs to the new institution.
Valid consents can be still be used against the existing institution until their expiry.

Hosted Pages Expanded - New countries: Hosted Pages now available in these additional countries:
Hosted Payments & Data: Netherlands, Belgium, Spain, Lithuania, Austria, France, Portugal
Hosted Data: Netherlands, Belgium, Spain, Lithuania, Austria, France, Portugal, Norway, Sweden

Data Plus - New Error Code for Transaction Retrieval Process (16002): This error occurs when there are no available transactions for the selected time period.
Action Required when receiving this error:
Adjust the from and before date parameters in your request and try again.

Hosted Pages - Bank Pre-selected Page and Yapily Connect regulatory wording:

Change 1: An updated consent wording is now on the Hosted Pages for those using the Yapily Connect Ltd or Yapily Connect UAB AISP or PISP license, which was a regulatory requirement change.

Change 2: The layout of the bank selection page when an institution is pre-selected. The user will only see the pre-selected bank, and no longer see the search bar.

Data Plus: 'categorisationType' Field Now Mandatory: the `categorisationType` field in the API endpoint `POST /accounts/{accountId}/transactions/categorisation` will become mandatory. Previously, this field was optional and allowed customers to choose between business and consumer categorization hierarchies

Hosted Pages - Change to use bank "Short Name": The bank selection page in the Hosted Payments and Consent product has been updated to utilise the "Short Name" of the banks within an application. This change aims to present a given PSU with the more recognised name of a given bank when choosing to complete a given payment of granting consent to bank account information.
Ex: UK bank "National Westminster Bank" will now be presented as "Natwest".

Hosted Pages - Consent Initiation Page: We have updated the design for the Authorisation Pages in the Hosted Payments and Hosted Data UI. This release aims to provide the PSU with clearer instructions on what is required to initiate the provisioning of their consent.

Natwest Transaction Status Change: From March 2024 NatWest will introduce the transaction status of “booked” for intra-day transactions that have not yet been posted, in order to align with Mobile Banking.

The change will be implemented across NatWest, Royal Bank of Scotland, Ulster Bank NI and NatWest/RBS International for personal and business banking customers who use Mobile or Online Banking.

Transaction types affected:

BAC	Automated Credit
BSP	Branch Single Payment
CDM	Cash & Deposit Machine