Service Provider Offering
The following tables illustrate the range of services offered by the Service Providers in the productive environment of bLink. While all foundational functionalities are supported, disparities arise in the breadth of data coverage and the support for certain endpoints. These differences require careful consideration by Service Users when integrating the APIs into their specific Use Cases. Understanding these variations is crucial for smooth integration and good performance in the bLink system.
Consent flow
Initially service providers primarily developed the consent flow for desktop and e-banking. However for many service users, especially modern fintech apps it is essential that the consent flow can be initiated directly on a smartphone. The first row of the table below shows which service providers support initiating the consent flow on mobile devices.
The Swiss market research firm Trenda has recorded the various consent flows of service providers on both desktop and smartphone. Trenda is kindly making these videos available to bLink service users as well as interested participants.
In the second column (Device: Smartphone) and third column (Device: Desktop) of the following table, you will find the corresponding video links. Access is password-protected.
Would you like to see how individual banks design the consent flow in their role as service providers?
Please contact us via the contact form and include “Trenda” in the text field. You will then receive the password.
About Trenda: Trenda is a Swiss company that helps retail banks, consulting firms, and providers in Switzerland and Liechtenstein make better, data-driven decisions through precise market analyses, current trends, and sound competitive insights. The digital Trenda platform provides curated market trends, relevant news, competitive analyses, and extensive data collections, enabling targeted evaluations and efficient collaboration within the organization. Learn more about Trenda.
| Participant | SP supports Consent Flow initiated on smartphone | Video of Consent Flow on smartphone | Video of Consent Flow on desktop |
|---|---|---|---|
| Acrevis | ✅ | - | - |
| AKB | ✅ | Demo | - |
| Avera | ✅ | - | - |
| BCJ | ✅ | - | - |
| BCV | ✅ | - | - |
| BEKB | ✅ | Demo | - |
| CIC | ✅ | - | - |
| Clientis | ✅ | Demo | - |
| Esprit | ✅ | - | - |
| HBL | ✅ | Demo | - |
| LUKB | ✅ | Demo | - |
| NKB | ✅ | Demo | - |
| PostFinance | ✅ | Demo | - |
| SGKB | ✅ | - | - |
| SZKB | ✅ | Demo | - |
| TKB | ✅ | Demo | - |
| UBS | ✅ | Demo | - |
| Valiant | ✅ | Demo | - |
| ZGKB | ✅ | Demo | - |
| ZKB | ❌ | - | - |
Account Information Service
The table below highlights AIS-specific differences between Service Providers. The information is structured into general characteristics of the data offering and into API features, where each feature may include one or multiple endpoints and define the format in which the data is retrieved. The provided details may influence how account data and account information, such as balances and transactions, can be retrieved, interpreted, and processed by Service Users.
| Participant | Supported Customer Segment | accounts | iso20022 | |||||
|---|---|---|---|---|---|---|---|---|
| Support JSON Endpoints | Max Limit for paginated transactions | Available Data Range | Support camt.053 XML files | Available Data Range (at initial consent) | Available Data Range | Support camt.052 XML files | ||
| Acrevis | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 2 Years | 2 Years | TBD |
| AKB | Retail & Corporate | ✅ | TBD | 14 Months | ✅ | 60 Days | As of initial consent | TBD |
| Avera | Retail & Corporate | ✅ | TBD | > 2 Years | ✅ | Last business day only | Last business day only | ✅ |
| BCJ | Retail & Corporate | ✅ | TBD | 3 Years | ✅ | 0 | Last business day only | ✅ |
| BCV | Retail & Corporate | ✅ | TBD | 1 Year | ✅ | 1 Year | 1 Year | TBD |
| BEKB | Retail & Corporate | ✅ | TBD | > 2 Years | ✅ | > 2 Years | > 2 Years | TBD |
| CIC | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 2 Years | 2 Years | TBD |
| Clientis | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 0 | Last business day only | TBD |
| Esprit | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 2 Years | 2 Years | TBD |
| HBL | Retail & Corporate | ✅ | 100 | 2 Years | ✅ | 30 Days | 30 Days | ❌ |
| LUKB | Retail & Corporate | ✅ | 1000 | > 2 Years | ✅ | > 2 Years | > 2 Years | ✅ |
| NKB | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 2 Years | 2 Years | TBD |
| PostFinance | Retail | ❗* | 100 | 2 Years | ❌ | ❌ | ❌ | TBD |
| SGKB | Retail & Corporate | ✅ | TBD | 2 Years | ✅ | 5 Days | 5 Days | ✅ |
| SZKB | Retail & Corporate | ✅ | TBD | 5 Years | ✅ | 0 | Last business day only | ✅ |
| TKB | Corporate | ✅ | TBD | Balance=5 Days; Transactions =2 Years | ✅ | Last business day only | Last business day only | ✅ |
| UBS | Retail & Corporate | ✅ | TBD | > 2 Years | ✅ | Since 02/2025, max. 2Y | Since 02/2025, max. 2Y | ✅ |
| Valiant | Corporate | ✅ | TBD | 2 Years | ✅ | 0 | Last business day only | ✅ |
| ZGKB | Corporate | ✅ | TBD | 5 Years | ✅ | 0 | Last business day only | ✅ |
| ZKB | Retail & Corporate | ✅ | TBD | 3 Years | ✅ | 0 | 7 Days | ✅ |
❗*: The transactions endpoint exposes C-level (entry-level) transaction data only.
Payment Submission Service
The table below highlights PSS-specific differences between Service Providers. The information is grouped by API features, where each feature may comprise one or multiple endpoints and define the format in which payment-related data is exchanged. The provided details may influence how payments are submitted, monitored, and processed within the integration.
| Participant | payments | iso20022 | consents | diagnostics |
|---|---|---|---|---|
| Acrevis | ✅ | ✅ | ✅ | ✅ |
| AKB | ✅ | ✅ | ✅ | ✅ |
| Avera | ✅ | ✅ | ✅ | ✅ |
| BCJ | ✅ | ✅ | ✅ | ✅ |
| BCV | ✅ | ✅ | ✅ | ✅ |
| BEKB | ✅ | ✅ | ✅ | ✅ |
| CIC | ✅ | ✅ | ✅ | ✅ |
| Clientis | ✅ | ✅ | ✅ | ✅ |
| Esprit | ✅ | ✅ | ✅ | ✅ |
| HBL | ✅ | ✅ | ✅ | GET only |
| LUKB | ✅ | ✅ | ✅ | ✅ |
| NKB | ✅ | ✅ | ✅ | ✅ |
| SGKB | ✅ | ✅ | ✅ | ✅ |
| SZKB | ✅ | ✅ | ✅ | ✅ |
| TKB | ✅ | ✅ | ✅ | ✅ |
| UBS | ✅ | ✅ | ✅ | ❌ |
| Valiant | ✅ | ✅ | ✅ | ✅ |
| ZGKB | ✅ | ✅ | ✅ | ✅ |
| ZKB | ✅ | ✅ | ✅ | ✅ |