<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Ibanity - Medium]]></title>
        <description><![CDATA[Ibanity is a financial API marketplace. Our technology helps you connect to a wide range of financial services from different providers, without the hassle and complexity of integrating separate APIs. One API to rule them all. - Medium]]></description>
        <link>https://medium.com/ibanity?source=rss----ddc1cea2a0f4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Ibanity - Medium</title>
            <link>https://medium.com/ibanity?source=rss----ddc1cea2a0f4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:52:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ibanity" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Une app bancaire basique en no-code sur votre compte actuel grâce à la DSP2 et Glide ]]></title>
            <link>https://medium.com/ibanity/une-app-bancaire-basique-en-no-code-sur-votre-compte-actuel-gr%C3%A2ce-%C3%A0-la-dsp2-et-glide-e11c86f396d2?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/e11c86f396d2</guid>
            <category><![CDATA[glide]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[dsp2]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Mon, 17 May 2021 18:26:53 GMT</pubDate>
            <atom:updated>2021-05-18T07:35:33.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7R_NyFNbukTzVZ2iSkFOsQ.png" /><figcaption>Une app bancaire connectée à votre compte grâce à la DSP2</figcaption></figure><p>Cela fait maintenant plus de 2 ans que le cadre légal est installé. Il est désormais possible, pour des sociétés ayant obtenu une license d’institution de paiement dans un des pays d’Europe, d’obtenir l’accès à l’historique des transactions bancaires de leurs clients et d’initier des paiements sur ces comptes, via des interfaces dédiée (aussi appelées APIs).</p><p>L’objectif de cette nouvelle législation, <a href="https://www.banque-france.fr/stabilite-financiere/securite-des-moyens-de-paiement-scripturaux/2eme-directive-sur-les-services-de-paiement">la DSP2</a>, est de permettre l’emergence de nouveaux services à destination des consommateurs et des entreprises. Ces nouveaux services peuvent voir le jour sous certaines conditions et permettre une harmonisation de l’échange de données bancaires dans plusieurs industries, comme le secteur comptable, le conseil financier ou encore les institutions de crédit.</p><h3>Quand votre compte bancaire rencontre le no-code</h3><p>Chez <a href="https://www.isabelgroup.eu/en/">Isabel Group</a>, on s’est demandé assez rapidement ce que le no-code pouvait apporter à cette nouvelle ouverture du secteur bancaire. La particularité de l’économie des APIs et du no-code, c’est qu’on ne peut pas vraiment prévoir comment ces APIs vont être utilisées, comment elles vont être connectées avec d’autres services et pour générer quelle valeur ajoutée.</p><p>Au lieu d’essayer de tout prévoir, pourquoi est-ce qu’on ne mettrait tout simplement pas ces capacités d’accès à la balance et à la liste des transactions de comptes de toutes les banques en Europe auxquelles on se connecte actuellement dans les plateformes d’intégration no-code ? Après quelques tests, on a décidé de pousser ces connections dans Zapier via notre produit à destination des TPE, Ponto.</p><p><a href="https://zapier.com/apps/ponto/integrations">Ponto Integrations | Connect Your Apps with Zapier</a></p><p>Ce que cette intégration permet de faire, c’est d’utiliser les “triggers” pour lancer un de vos “Zap”, une sorte de recette qui défini des actions à faire en fonction d’évènements précis, pour ceux qui ne connaissent pas Zapier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*2OjlwLmyyxT6nMXqE6Rfkw.png" /><figcaption>Les triggers disponibles au moment de la rédaction de ce post</figcaption></figure><p>Aujourd’hui, Ponto supporte plusieurs centaines de banques en Europe, dont une bonne centaine en France.</p><h3>Préparer les données pour qu’elles soient disponibles dans Glide</h3><p>Glide utilise une feuille de calcul Google comme source de données. On doit donc commencer par lier notre compte bancaire avec une feuille de calcul dédiée que l’on pourra utiliser plus tard dans glide.</p><p>Ponto n’ayant pas (encore 😉) d’intégration directe avec Google docs, nous utiliseront Zapier pour “pousser” les données dans cette feuille de calcul.</p><p>Créons une nouvelle feuille ‘’transactions” et créons une colonne pour chaque attribut renvoyé par l’API de Ponto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kH0T2F3aLcccVgRzyvKYA.png" /><figcaption>Nouvelle feuille de calcul reprenant les attributs renvoyés par Ponto pour une transaction bancaire</figcaption></figure><p>La liste complète des attributs d’une transaction peut être consultée (en anglais uniquement) sur <a href="https://documentation.myponto.com/api/curl#transaction-attributes">la documentation de l’API de Ponto</a>.</p><p>Créons maintenant un nouveau Zap dans Zapier, nous le nommerons “Mon app bancaire — Transactions”. Dans l’étape “trigger”, on commence par choisir Ponto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6NVfcZdkq_w5xHJuaRFhQ.png" /><figcaption>Choisir Ponto dans l’étape “trigger” sur Zapier</figcaption></figure><p>Il faut maintenant connecter notre compte Ponto ou en créer un dans la foulée.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYFIvlPbmwNA8k8PUeD2nw.png" /><figcaption>Connecter un compte Ponto existant ou en créer un nouveau</figcaption></figure><p>Il est possible de créer un compte Ponto directement sans sortir de Zapier et de connecter notre compte bancaire en même temps, nous pouvons donc directement profiter de la période d’essai du service. Nous recevrons les instructions pour compléter notre compte par email plus tard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFjRNIA-9XhLAR4xlB_jkg.png" /><figcaption>Créer son compte Ponto</figcaption></figure><p>Nous pouvons alors sélectionner un compte bancaire déjà lié à notre compte Ponto ou en ajouter un autre. Nous sommes alors dirigé vers le site de notre banque pour autoriser l’accès.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zDWRaDspN3Vq9GtvfHqyA.png" /><figcaption>Liste des comptes</figcaption></figure><p>Une fois les comptes souhaités activés, nous pouvons maintenant sélectionner le compte qui nous servira de source de données pour notre app bancaire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iniOwUZedR8HSYTTD-qcJg.png" /><figcaption>Selection du compte qui servira de source de donnée</figcaption></figure><p>Nous devrions normalement pouvoir tester notre “trigger” et voir apparaître notre dernière transaction dans l’interface de Zapier 😎</p><p>L’étape suivante est de configurer l’accès à Google docs de la même manière. Pour ce faire, on sélectionne donc “Google Sheets” dans l’étape “Action” sur Zapier, et on choisi ensuite “create spreadsheet row” comme action. Après avoir lié notre compte google, nous devrions pouvoir choisir la feuille de calcul que nous avons créée plus haut.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q06o7t2IeSeB7YJnKbIGng.png" /><figcaption>Configurer Google sheets dans Zapier et connecter la feuille créée précédement</figcaption></figure><p>Nous voyons alors apparaître toutes les colonnes disponibles et il suffit maintenant de faire le mapping entre les colonnes dans google sheets et les attributs renvoyés par Ponto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jra9PoTLmwEoJ5IZQUoDhA.png" /><figcaption>Mapping des données entre Ponto et Google sheets</figcaption></figure><p>Une fois le mapping terminé, nous pouvons maintenant tester notre zap et une transaction doit apparaître dans notre feuille de calcul 🤩</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJzGTfvfnj7fr61f1_SUZA.png" /><figcaption>Les transactions de mon compte bancaire sont maintenant poussées dans la feuille de calcul</figcaption></figure><p>Il ne nous reste plus qu’a activer notre nouveau Zap ! Afin de stocker également les changements de balances sur ce même compte, nous devons créer un autre Zap, qui utilisera cette fois le trigger “New Balance” et poussera les informations dans une seconde feuille de calcul. Nous pouvons suivre le même tutoriel que pour les transactions en appliquant le même concept aux attributs retournés par l’API de Ponto mais cette fois pour la balance du compte.</p><h3>Utiliser les données bancaires dans glide</h3><p>Les données de notre compte bancaire devraient désormais commencer à arriver dans notre feuille de calcul Google. Le Zap ne se déclenche que lorsqu’il y a de nouvelles transactions et que la balance du compte change, il est donc possible qu’il faille plusieurs jours avant d’avoir une liste plus fournie. Néanmoins, nous pouvons déjà préparer notre app basique dans Glide et commencer à expérimenter avec nos données.</p><p>Une fois enregistré sur Glide, il faut créer une nouvelle app et sélectionner Google Sheets comme source de données.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56k_k1xnaS2SFlmHkUnqRw.png" /><figcaption>Sélectionner notre feuille de calcul comme source de donnée</figcaption></figure><p>Glide nous crée par défaut deux tabs, une par feuille dans notre Google Sheet. Nous avons donc la possibilité d’afficher la liste des transactions disponibles dans notre source de données et de jouer avec l’évolution de la balance du compte.</p><p>En changeant les attributs utilisés dans la liste, on affiche le montant, le nom de la contrepartie et la date valeur de la transaction. On peut également voir le détail de chaque transaction en suivant les liens dans la liste. Toutes ces fonctionnalités sont fournies par défaut par Glide !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dFIh3xFDSP5pjj6WumW4zg.png" /><figcaption>Ecran liste des transactions</figcaption></figure><p>Pour que la liste des transactions soit triée par date valeur, on peut utiliser la fonction “sort” en cliquant sur “Options” en haut à droite et configurer l’ordre en fonction de la date valeur comme ceci:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*ppnP-7OjGXIToNX9zURttg.png" /><figcaption>Configuration de l’ordre des transactions</figcaption></figure><p>Vous pouvez jouer avec la visualisation des données en changeant l’ordre, la taille du texte, ou en enlevant les informations que vous jugez inutiles.</p><p>Pour l’écran représentant la balance de notre compte, nous souhaitons afficher la plus récente. On doit donc changer de modèle et prendre le style “Details” plutôt que “List”. On peut alors modifier les champs affichés à l’écran, jouer avec la taille du texte, ajouter le même filtre de triage que pour la liste des transactions et le tour est joué. Avec un peu plus de boulot, il y a surement moyen que ça aie plus de gueule que ça 😜</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9uiiO7nrVfXxTgmfU1pCSQ.png" /><figcaption>Ecran balance</figcaption></figure><p>Maintenant qu’on a les choses de base, essayons de donner plus fonctionnalités à notre application. Ce serait intéressant de pouvoir consulter nos rentrées et nos sorties par contrepartie, afin d’avoir une meilleure idée de nos plus grands postes de coûts ainsi que de nos meilleurs clients. On va créer une tab “Cash in” et une autre “Cash out”, le style de ces tabs sera “Details” et on y ajoute un titre et un élément de type “Charts”.</p><p>On doit maintenant filtrer les informations en fonction du montant, pour ce faire, on sélectionne l’élément “Charts” et dans l’onglet “Options”, nous pouvons décider de filtrer uniquement les transactions dont le montant est positif ou négatif. Ce qui nous donne le résultat suivant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlExVRQlhyQ-HBxB6H-OyA.png" /><figcaption>Ecrans Cash out / Cash In</figcaption></figure><p>Plutôt pas mal pour quelques minutes passées dans Glide 😇</p><p>Il est temps de publier l’app pour l’utiliser sur notre smartphone ! En cliquant sur Publish en haut à droite, l’app est désormais accessible, il vous suffit juste de scanner le code QR et de l’ajouter votre home screen.</p><h3>Et maintenant ?</h3><p>L’app est certes très simple pour le moment, mais elle fait déjà peut-être mieux certaines choses que celle de votre banque actuelle. Il y a encore beaucoup de fonctionnalités à ajouter pour en faire une app bancaire aboutie comme par exemple:</p><ul><li>L’initiation de paiement (pas encore supportée par Ponto sur Zapier)</li><li>L’ajout d’informations sur les contreparties</li><li>La catégorisation des transactions</li><li>Une recherche plus aboutie dans les transactions</li><li>Une gestion de budgets</li><li>…</li></ul><p>Pour certaines de ces fonctionnalités, il est plus que probable que d’autres outils que Glide soient nécessaires, mais la perspective de refaire entièrement une app bancaire sans écrire une ligne de code est plutôt excitante 🤯</p><p>Depuis quelques semaines maintenant, j’utilise une app similaire, faite sur Glide, pour consulter de manière quotidienne les informations bancaires de ma société perso. Je n’ouvre plus l’app de ma banque qui est souvent plus compliquée à utiliser et demande plus d’actions de ma part avant d’accéder aux données qui m’intéressent. Qui plus est, elle n’offre qu’une possibilité très réduite de chercher dans mes transactions, et l’app Glide telle que présentée dans ce tuto est à ce niveau là plus adaptée à mes besoins que l’app de ma banque.</p><p>Il y a encore beaucoup de choses avec lesquelles nous expérimentons ces derniers temps dans l’univers no-code, notamment la création d’alertes qui se déclenchent lorsque la balance atteint un certain seuil ou lorsqu’une transaction avec des attributs particuliers ou un montant important sont détectés.</p><p>Ce qui est sûr, c’est qu’on a à peine effleuré les possibilités données pas le fait de pousser nos informations bancaires dans des outils no-code comme Glide, n’hésitez pas à nous donner votre feedback par rapport à ce MVP ou à nous partager vos idées, on se fera un plaisir d’essayer de les mettre en pratique avec nos outils no-code préférés 😍</p><p>Si ce qu’on fait vous intéresse, ça se passe ici: <a href="https://myponto.com/en">https://myponto.com/en</a></p><p>Marc</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e11c86f396d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/une-app-bancaire-basique-en-no-code-sur-votre-compte-actuel-gr%C3%A2ce-%C3%A0-la-dsp2-et-glide-e11c86f396d2">Une app bancaire basique en no-code sur votre compte actuel grâce à la DSP2 et Glide 🚀</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finance automation with PSD2]]></title>
            <link>https://medium.com/ibanity/finance-automation-with-psd2-a448a66232ba?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/a448a66232ba</guid>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[business-process]]></category>
            <category><![CDATA[banking]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 07:05:14 GMT</pubDate>
            <atom:updated>2020-06-23T07:11:17.304Z</atom:updated>
            <content:encoded><![CDATA[<p>Since September 2019, more banks have been releasing their mandatory API to allow regulated third parties to connect to the payment accounts of their customers.</p><figure><img alt="Picture of the mechanical turk, the first chess playing automaton, showing how it was operated with a human inside." src="https://cdn-images-1.medium.com/max/1024/1*yfur6fEDemmKiGCJTzCY4g.jpeg" /><figcaption>The Mechanical Turk, the first chess player “automaton” (<a href="https://en.wikipedia.org/wiki/The_Turk">https://en.wikipedia.org/wiki/The_Turk</a>)</figcaption></figure><p>At <a href="https://ibanity.com/home">Ibanity</a>, we have been integrating hundreds of these APIs and it turns out <a href="https://medium.com/ibanity/api-aggregators-key-to-psd2-success-3c823eeef224">our predictions</a> were verified: Without API aggregators, PSD2 is most probably doomed. The technical barriers to entry for fintechs are still way too high. Add to this the fact that there are only a couple of hundred companies that applied for an AISP or PISP license in Europe so far, it does not look very encouraging right now.</p><p><em>Read our article: “</em><a href="https://medium.com/ibanity/api-aggregators-key-to-psd2-success-3c823eeef224"><em>API aggregators key to PSD2 success</em></a><em>” for more information.</em></p><p><strong>The future of account information is in automation</strong></p><p><a href="https://en.wikipedia.org/wiki/Business_process_automation">Business Process Automation</a> or workflow automation, has been a prominent topic for a while in the B2B industry. It’s now becoming an area of investment for several banks and Fintechs. The workflow automation market itself is estimated to reach more than USD 10 Billion by the end of 2023. Combining workflow automation with open banking capabilities brought by PSD2, brings opportunities to automate repetitive tasks and moreover paves the way for companies to truly go beyond banking by integrating their banking experience, and data, into their business processes and tools.</p><p><strong>Your money, your rules</strong></p><p>In order to be everywhere at any time, banks and fintechs keep creating new channels and user interfaces for their customers, which they will usually transform into commercial cross-selling gateways later on. The customer however is meanwhile drowning into an ocean of financial applications that increasingly look and feel the same and sometimes even offer the same added value.</p><p>It also means that, as a customer, you get yet another interface you are expected to use every day, even if you already have another product in your current toolchain that provides you the same value. Another annoying point is that integration between that bank provided software with your other tools is always rather limited and based on manual file exports.</p><p>It’s your money, your bank account, your data, so you should be able to define your own personal experience around it and include it in your current processes. Yet, for years, banks have limited your capabilities to keep you in their very own channels and products.</p><p><strong>Open up with Ponto</strong></p><p>We built <a href="https://myponto.com/">Ponto</a> with business process automation in mind. We wanted to create a way for businesses to decide which software can access which bank account and more. That is exactly what Ponto does: it allows you to connect your bank account to the software you are already comfortable with.</p><p>At any given time, <a href="https://myponto.com/">Ponto</a> customers can manage those consents, revoke them and trigger a <a href="https://en.wikipedia.org/wiki/Strong_customer_authentication">Strong Customer Authentication</a> flow whenever needed.</p><p>Next to using partner integrations, <a href="https://myponto.com/">Ponto</a> also provides an API for companies willing to integrate with their custom software. This opens up the possibilities even more for companies to literally include their banking experience in anything.</p><p><strong>Ponto + Zapier = 🚀</strong></p><p>Ever took a moment to think about all the thing you could build on top of your banking data? With <a href="https://zapier.com/apps/ponto/integrations">our Zapier integration</a>, you can now connect your bank account from 150+ banks in Europe to all the saas services available in <a href="https://zapier.com/apps/ponto/integrations">Zapier</a>. These integrations will unleash the true potential of PSD2 account information and finally offer organizations the flexibility they have longed for during the past decade.</p><p>Some of our customers have already been using <a href="https://zapier.com/apps/ponto/integrations">Zapier</a> to build customized financial dashboards, action lists in Airtable, alerts by email or SMS, and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QYvHbZIlA7HMql7LrMMEFg.png" /><figcaption>Ponto integration page on Zapier</figcaption></figure><p>We can’t wait to see what our customers will build with <a href="https://zapier.com/apps/ponto/integrations">Zapier</a> and are very excited to work on the future of finance automation in a PSD2 world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a448a66232ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/finance-automation-with-psd2-a448a66232ba">Finance automation with PSD2</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API aggregators key to PSD2 success]]></title>
            <link>https://medium.com/ibanity/api-aggregators-key-to-psd2-success-3c823eeef224?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c823eeef224</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[belgium]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[psd2]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Fri, 26 Jan 2018 10:26:12 GMT</pubDate>
            <atom:updated>2020-06-23T10:14:30.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQNtkHT9SiSzemXbE3KM9w.jpeg" /></figure><p><em>An API aggregator (also referred to as “API Hub”) is an API on top of several different APIs. It provides a single point of implementation and delivers a unique and standardized API regardless of what APIs or services it integrates with.</em></p><p>It’s been a few days since January 13. A few countries have transposed the European directive into local legislation and a few more banks have released their developer portal, sandbox and documentation. Looking at the few currently available APIs, we can already draw a few conclusions.</p><p><em>Update 23/06/2020: We have recently published </em><a href="https://medium.com/ibanity/finance-automation-with-psd2-a448a66232ba?source=friends_link&amp;sk=2626f641b6bdb5ce0bd7769c38544b26"><em>an article showing how Ponto, our new product, helps companies automate their business processes thanks to PSD2.</em></a></p><h4>No two APIs are built the same</h4><p>Over the past few months, we have received several questions about our message format, its compliance with market standards such as ISO20022 and currently available open specifications (Berlin Group, Paris Group, PolishAPI, Open Banking UK,…). In our opinion the message in itself is probably the easiest thing to integrate in an API, regardless of its format. Every decent programming language will let you parse text quite easily and efficiently. Whether it is in a JSON or XML structure (or even something else) does not matter.</p><p>On the other hand, several other traits of an API can either make the lives of developers easy or a living hell.</p><ul><li>Authentication model of the API</li><li>Pagination model (in list of account transactions for instance)</li><li>Proper use of HTTP verbs and status codes</li><li>Error handling (clear and straightforward)</li><li>Developer onboarding process</li></ul><p>What you can see today, looking at all APIs already available, is that for all or some of those specific characteristics, no two banks are similar.</p><p>Some banks provide a sandbox and allow you to access real data with the flip of a switch while some others require that you connect to a specific and separate environment, etc…</p><p>This makes integration to many banks more difficult for developers. API aggregators abstract that complexity by proposing only one clean API. Implement it once and support all currently (and future) supported banks.</p><h4>Third party providers want to focus on their added value</h4><p>Most companies reaching out to us on PSD2 today are from many different fields: insurance brokers, credit institutions, accounting packages, software agencies, … All of them want to process account information or initiate payments to deliver more value to their own customers.</p><p>Most TPPs that reached out to us do not want to bear the costs of integrating with dozens or hundreds of APIs. Even banks themselves are releasing requests for proposals on API aggregation projects as this article is being written, in order to become TPPs themselves. Some of those TPPs will carry out this implementation effort themselves of course, possibly some of the largest ones, but there are lots of TPPs out there, looking for easy access to many banks with one single integration.</p><p>Without API aggregators, PSD2 may very well end up favoring the largest TPPs that are already present on the market today and still making it too difficult for new players to get in the game. To be ambitious and international from the start, these new players would need to invest massively in bank integrations. API aggregators can help them quickly get started and reach a European market from day one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*Kou1XRBGfXDDPRBPsFBWlA.png" /><figcaption>Ibanity is a bank API aggregator that facilitates interaction between third party providers and banks.</figcaption></figure><h4>Smaller banks may be the big losers of that fragmentation</h4><p>Let’s put ourselves in the shoes of a TPP. I have limited funds that I want to spend on integration and I want to maximize my market reach. My strategy is going to be very simple: focus on the large banks.</p><p>In Belgium, integrating the four largest banks will give you access to the large majority of the market, estimated at around 80%. Add four more integrations with mid-tier banks and the best you can reach is 10% more. As a result, smaller banks risk being shadowed by large ones and ignored by TPPs.</p><p>The main risk is that if great products come out on the market that does not support smaller banks, customers of those smaller banks may move their assets to another bank to benefit from these new services. Of course, it is all speculation and nobody can truly predict the future. It is clear that PSD2 adoption will not happen overnight.</p><p>In the end, what was supposed to bring more competition on the market may very well simplify the banking ecosystem in favor of large banking groups and large TPPs.</p><p>In order to stay relevant in a post-PSD2 world, smaller banks should be proactive by being integrated in an API aggregator in order to benefit from a larger TPP reach. That way, they can avoid increasing churn in their customer base and develop new innovative products and services by acting as a TPP on the API aggregator themselves.</p><h4>API Aggregators are matchmakers in the PSD2 landscape</h4><p>An API is roughly a communication protocol and series of messages used by two information systems to interact with each other. As such, it is easy to consider the consumer of an API as another piece of software. That is of course if you don’t take into consideration the person that will need to make that interaction possible, the software developer. They are the ones building new products and services for the bank’s customers.</p><p>If you look at the software developers as the true consumers of an API, which they are, then you need to cater for their needs and make sure your API is following the best quality standards that software developers like. It means that as a bank, you now have a new distribution channel, with a new kind of partner, the software developer. Are banks equipped to reach and capture their attention? Some are, but a large majority are still trying to figure it out.</p><p>API aggregators usually have a strong developer-centric mindset and know what needs to be done to attract them. Banks, by partnering up with API aggregators, can start building their community and reach out to potential future partners without making the initial investment themselves.</p><h4>API Aggregators are PSD2 enablers</h4><p>PSD2 bears great promises. To reach its objectives, we must prevent that the complexity of integration kills it.</p><p>API aggregators help PSD2 succeed by:</p><ul><li>Providing a single secure interface to several banks, lowering the workload of onboarding and supporting TPPs for them.</li><li>Providing international bank reach to TPPs in one single integration so they can compete on a larger market from the start.</li><li>Acting as a matchmaker between banks and the TPP ecosystem to accelerate partnerships.</li><li>Providing visibility and TPP reach to smaller banks with a future-proof digital strategy.</li></ul><p><strong>Want to know more about our API aggregation services?</strong> Reach out to us at info@ibanity.com or through our website https://ibanity.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c823eeef224" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/api-aggregators-key-to-psd2-success-3c823eeef224">API aggregators key to PSD2 success</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ibanity is looking for software engineers]]></title>
            <link>https://medium.com/ibanity/ibanity-is-looking-for-software-engineers-3cade451e1f9?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/3cade451e1f9</guid>
            <category><![CDATA[belgium]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Mon, 20 Nov 2017 12:44:39 GMT</pubDate>
            <atom:updated>2017-11-20T12:45:50.980Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYllJJrTVIcuC6dqD2_DrQ.png" /></figure><p>Within the new landscape that directives such as the European payment directive (PSD2) are creating, Ibanity aspires to become the best financial services integration platform and API on the market. Making connectivity with financial services easy and friction-less for software developers will be key in the creation of amazing new products. Those new changes also mean financial institutions will also need our support to adapt and become compliant.</p><p>We are looking for software developers and software engineers who believe they can contribute to our vision and bring their own ideas to help us with financial institution integrations, API specification, software architecture, micro-service architecture, security and also artificial intelligence.</p><p>You will be working within our engineering team and work on critical parts of our system. You will be part of an experienced team with a devops mindset. We need our team members to be enthusiastic about solving new problems and be detail-oriented in their work.</p><p>Part of Isabel Group, Ibanity is a product meant for software developers, which means that we put a lot of focus in building high quality software for the financial industry. Software that could one day be used behind the scenes by millions of users and process payments at large scale. Technological challenges are part of the journey and we are looking for team members who want to take part in revolutionizing the financial sector through APIs.</p><p><strong>Responsibilities</strong></p><ul><li>Work closely with product owners to design solutions</li><li>Develop, test, deploy and maintain software</li><li>Participate in design and architecture decisions, as well as team planning</li><li>Manage priorities and be creative in proposing scope adaptations to meet deadlines</li></ul><p><strong>Qualifications</strong></p><ul><li>5 years of combined experience coding in any of the following languages: Erlang, Java, Ruby, Python, Javascript, Elixir</li><li>At least 2 years of experience working in web-based projects</li><li>Previous experience building APIs is a plus</li><li>English proficiency in both verbal and written communication</li><li>Interest in learning new coding languages as needed</li></ul><p><strong>Position</strong></p><ul><li>Based in Brussels, 2 minutes walk from Central Station</li><li>Possibility to work part-time from our offices in Louvain-la-Neuve</li><li>Remote not possible</li><li>Part-time not possible</li><li>Freelance or employee contracts available</li></ul><p>Interested? Send your application to jobs@ibanity.com and we’ll be in touch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cade451e1f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/ibanity-is-looking-for-software-engineers-3cade451e1f9">Ibanity is looking for software engineers</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ibanity joins Isabel Group]]></title>
            <link>https://medium.com/ibanity/ibanity-joins-isabel-group-e6457dbfa140?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/e6457dbfa140</guid>
            <category><![CDATA[belgium]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 09:11:11 GMT</pubDate>
            <atom:updated>2017-09-12T09:11:10.659Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we are happy to announce that ibanity has been acquired by Isabel Group.</p><p>We found in Isabel Group the perfect partner to support us and help us take part in the future of open banking in Europe.</p><p><a href="https://www.isabel.eu/en/about-us.html">Isabel Group</a> is a market leader in multi-banking applications in Belgium and was co-founded by the largest Belgian banks in 1995. They process more than 433 million payment transactions every year.</p><p>By combining our visions, we believe we can come up with a unique offering, on the Belgian market and in Europe.</p><p>Our objectives haven’t changed, they’ve just been given a serious shot of steroids…</p><h3>It’s still us</h3><p>We believe the financial industry is changing. EU regulations such as PSD2 pave the way for an open banking world.</p><p>Banking is too important nowadays to be left to bankers alone. As a team, we want to provide a developer-centric product that would aggregate all existing and future bank APIs, provide SDKs for easy integration and deliver a stellar experience to developers, banks and their respective customers.</p><p>We believe that integrating your software platform with banks to process your customers account data or initiate payments should not take more time than to make yourself a cup of coffee. It’s a strong statement but one we’ve been working towards since ibanity was known as <a href="https://medium.com/ibanity/we-built-an-api-on-top-of-belgian-banks-2331c6988689">omnibank.io</a>, <a href="https://medium.com/ibanity/we-built-an-api-on-top-of-belgian-banks-2331c6988689">a simple side project we presented a year ago</a>, that we created next to our consulting business at <a href="http://spin42.com/">Spin42</a>.</p><p><a href="https://www.linkedin.com/in/loicvigneron/">Loïc</a>, <a href="https://www.linkedin.com/in/thibaultponcelet/">Thibault</a>, <a href="https://www.linkedin.com/in/olivier-delens-a701555a/">Olivier</a> and I have shaped what ibanity is today over the past months and we are excited about the challenges to come next.</p><h3>What now?</h3><p>Integrating Isabel Group will give us an opportunity to deliver our value proposition on the market faster than we could have done it alone and extend it to serve the needs of banks as well.</p><p>Trust, security and compliance are going to be key in the future development of open banking. Having the support of a renowned group will help us tackle those challenges.</p><p>The opportunities that a product such as ibanity offers are not only limited to PSD2 or open banking, it goes much further. With the support of Isabel Group, we will be given the flexibility to explore its full potential and develop new products and services around it.</p><h4>We’re hiring</h4><p>All of this will only be possible with the right team. One of our first objectives is to grow this team with like-minded people. If you are interested in open banking, PSD2 and new ways of banking, we always have room for the right people, junior or not. We are more interested in attitude than skills.</p><p>Interested? Simply send us your application and explain how you think you could contribute to ibanity at jobs@ibanity.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6457dbfa140" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/ibanity-joins-isabel-group-e6457dbfa140">Ibanity joins Isabel Group</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Omnibank is dead… Say hi to ibanity!]]></title>
            <link>https://medium.com/ibanity/omnibank-is-dead-say-hi-to-ibanity-c10993f8b765?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/c10993f8b765</guid>
            <category><![CDATA[fintech-sandbox]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Mon, 06 Mar 2017 09:53:22 GMT</pubDate>
            <atom:updated>2017-03-03T18:00:22.450Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WSWwolIFQr9D-rsVnpS6cw.png" /><figcaption>Omnibank.io becomes ibanity</figcaption></figure><p><em>This is the third article on the progress of ibanity (pka Omnibank.io), you can read more about </em><a href="https://medium.com/@mlainez/we-built-an-api-on-top-of-belgian-banks-2331c6988689#.hf800nkam"><em>the genesis of the project</em></a><em> and our first introduction of </em><a href="https://medium.com/@mlainez/omnibank-is-still-alive-and-kicking-eaa05052d59c#.affuss9ku"><em>the developer sandbox</em></a><em>.</em></p><p>Quite a lot has happened since our last <a href="https://medium.com/@mlainez/omnibank-is-still-alive-and-kicking-eaa05052d59c#.affuss9ku">medium post</a>. We’d like to share some of it with you starting with one major update: Omnibank is dead…</p><p>Long live ibanity!</p><h3>Why the name change?</h3><p>Last november 2016, we gathered to decide what we wanted from this project. We had a working technical solution, support for 6 banks and were already using it to solve our own problems. We asked ourselves if transforming a side project into a real product company was something we truly wanted. We took some time to think about it and we made a decision. In 2017, we plan on working full time on it. Currently, we can only afford to spend at best a couple of days a week which is clearly not enough but we’ll come back to that.</p><p>We changed name mostly because of <a href="http://www.fsma.be/~/media/Files/fsmafiles/wetgeving/wet_loi/2014-04-25_Wet-loi.ashx">Article 5 in the law of April 25 2014</a> that states a list of which organisations are allowed to use the word “bank” in their name. Hint: we’re not in that list.</p><h3>Introducing ibanity</h3><p>Our mission is to deliver developers a SDK and a bank aggregation API that will let them build awesome products. We want to remove the friction of accessing banking data and provide the best experience possible.</p><p>Confirming our involvement in the project and changing name meant for us we needed to step it up a bit. So we decided it was time to make what we had a bit more appealing and more “<em>production-ready”</em>. We have reworked our portal entirely and we have worked on the end-user flow that will allow your customers to link an account to your platform.</p><h4>The embeddable widget</h4><p>In order to allow your customers to give you access to their accounts, we needed to have an easy to embed widget.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c744b0d116ff354678968be5a1bc2879/href">https://medium.com/media/c744b0d116ff354678968be5a1bc2879/href</a></iframe><h4>The developer portal</h4><p>We have completely revamped our existing portal and included more security features. Authentication is done with login/password + Google Authenticator at the moment. We will add SMS security code as an alternative to Google Authenticator in the future. It is important to us that 2FA is the default authentication model on our developer portal.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F206579293&amp;url=https%3A%2F%2Fvimeo.com%2F206579293&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F621640354_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/a631be2276b5d75a753815ee6b8a0c83/href">https://medium.com/media/a631be2276b5d75a753815ee6b8a0c83/href</a></iframe><p>As you can see, per application you create on our portal, you get two sets of credentials. A publishable token and a certificate. We go into more details in the next section.</p><h4>What does it look like for the end-user, your customers?</h4><p>Ibanity acts as a trusted intermediate that allows developers to access their customers bank data. That way, the developers can rely on us to protect their customers sensible data while we provide them connection to as many banks as possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F206588030&amp;url=https%3A%2F%2Fvimeo.com%2F206588030&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F621651916_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/465dccdfaca1368c8af10d58b0664ce5/href">https://medium.com/media/465dccdfaca1368c8af10d58b0664ce5/href</a></iframe><p>Onboarding takes only a minute per bank linked. They just need their usual bank credentials (digipass or password or pincode) and a phone number to receive an SMS.</p><h4>Our API security model</h4><p>In the previous sections we introduced two different sets of credentials.</p><ul><li>Publishable tokens</li><li>Certificates</li></ul><h4><strong>Publishable tokens</strong></h4><p>They are used only to inject the html widget. It is a safe to publish token that makes it possible for us to identify an application on our portal. All connections from the widget go straight to ibanity, they do not go through your services.</p><h4><strong>Certificates</strong></h4><p>Those are of course quite sensible. These certificates are what you need to use in order to call our API from your servers. It’s a way to securely identify which application is calling. Those certificates are generated and signed by our very own root certificate authority.</p><p>A valid API call from your servers to ibanity will need the certificate. Either you or we can revoke any of those credentials as soon as we identify any unexpected behaviour, rendering all your requests unauthorized.</p><p>All the sensible data we need to save in order for the API to function properly is encrypted and decrypted with <a href="https://www.vaultproject.io/">vault by hashicorp</a>. The whole thing is deployed on several distinct instances of AWS in Frankfurt. Those data centers are PCI, SOC &amp; ISO27001 compliant.</p><p><a href="https://aws.amazon.com/compliance/">Cloud Compliance - Amazon Web Services (AWS)</a></p><h3>Our Roadmap</h3><p>We know a lot of you are eager to get your hands on ibanity, especially those who have seen a live demo on real banks. However, we’ve only started 6 month ago and there is still quite a lot for us to do to get there. As we are only working at most a couple of days a week on this, we had to decide if we wanted to keep bootstrapping or get funded. We decided to open a seed investment round to move faster and be able to work on ibanity full-time.</p><p>Anyone interested can contact us at hey@ibanity.com and ask for our investors pitch deck.</p><p>Our current plan is the following:</p><ul><li>Q1 2017: Get funded to work full-time on ibanity. Finish the last developments to make it fully production-ready.</li><li>Q2 2017: Open up the multi-bank sandbox for anyone to try. Get first live banks in production. Launch of our beta program.</li><li>Q3 2017: Focus on customer base growth and improving ibanity based on the feedback received. Add more banks live.</li><li>Q4 2017: End of beta, official launch.</li></ul><h3>Wanna help?</h3><p>There are many ways you can help:</p><ul><li>Talk about us to your developer/entrepreneur colleagues.</li><li>Share this blogpost to any person that might be interested.</li><li>Introduce us to investors or funds if you know any that would like what we’re trying to do.</li><li>Send an email to your banks support center asking them to speed up discussions with ibanity.</li></ul><p>We are more than ever convinced that this is the perfect timing to change the status-quo around access to banking data here in Belgium. We’re doing the best we can to make it happen and with your help, we will.</p><p><em>Feel free to contact us with feedback and questions at our new email address hey@ibanity.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10993f8b765" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/omnibank-is-dead-say-hi-to-ibanity-c10993f8b765">Omnibank is dead… Say hi to ibanity!</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Omnibank is still alive and kicking!]]></title>
            <link>https://medium.com/ibanity/omnibank-is-still-alive-and-kicking-eaa05052d59c?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/eaa05052d59c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[betech]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Mon, 06 Mar 2017 09:53:07 GMT</pubDate>
            <atom:updated>2017-03-04T06:35:34.584Z</atom:updated>
            <content:encoded><![CDATA[<p><em>UPDATE 03/17: Omnibank is now renamed ibanity for compliance reasons, you can read why in </em><a href="https://medium.com/@mlainez/omnibank-is-dead-say-hi-to-ibanity-c10993f8b765#.d0etgem0b"><em>our latest story</em></a><em>.</em></p><p><em>Omnibank aims at providing software developers an API to access bank information. Getting hooked up to your data shouldn’t take more than the time your coffee needs to pour. Want to meet us? We will be at the </em><a href="http://fintechbelgium.be/2016/07/03/fintech-belgium-summit-2016/"><em>Fintech Summit on October 13</em></a><em> and pitching at the </em><a href="http://startups.be/content/fintech-conference"><em>ING Fintech Conference</em></a><em>.</em></p><p>It’s now been almost two months since <a href="https://medium.com/@mlainez/we-built-an-api-on-top-of-belgian-banks-2331c6988689#.qvozb04vx">our first announcement</a> where we came out of the woods with Omnibank. After all this time, things have been moving at a rapid pace. We are now supporting more banks and got in touch with several financial institutions to pitch the project.</p><p><a href="http://omnibank.io/">Omnibank - An API on top of banks</a></p><h3>We already met most of the Belgian banks</h3><p>Thanks to the traction we had with our first post, banks and financial institutions were curious to meet us. We met with a dozen of them, we got a chance to demo our product as it is at the moment, explain the underlying magic and expose them how we wanted to position ourselves on the market with Omnibank. PSD2 will bring a lot of new opportunities by itself but we would also like to tap into all that is out of PSD2&#39;s scope. We want to become the prefered platform for developers to interact with banks by providing added value in terms of data quality, monitoring, support, documentation and added value features on our API.</p><h3>We have added more banks to our list</h3><p>We’re happy to tell you that we added, through the same techniques as before, 3 more banks to our list of supported establishments. We now have a mix of large and small banks. We are currently in discussion with them to make this support more official. As soon as we make progress on this point, we’ll let you know. Right now, we still haven’t planned on disclosing the names of the banks we support.</p><h3>What does it look like?</h3><p>We got lots of feedback from the #betech community and met with quite a lot of software developers, startups, Fintechs, software providers and we tried to show them the complete value stream as much as possible. Since about a month ago, we have finished a very rough version of our developer portal that we use during current demos. It gives an idea of the complete flow and shows that it wouldn’t take more than a couple of minutes to access your banking data with our current technical solution. All relevant data has been anonymised.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F185956665&amp;url=https%3A%2F%2Fvimeo.com%2F185956665&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F595862280_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/f1b3f46192357d561fb722d19ea66b77/href">https://medium.com/media/f1b3f46192357d561fb722d19ea66b77/href</a></iframe><p>We currently focus on what we call the “single user” use-case, meaning a single person accessing his own or his company’s banking data. We do not support third parties such as PFMs and customer facing apps on Omnibank yet. Of course, we plan to support it in the near future.</p><h3>What’s next for us?</h3><p>Discussions, discussions, discussions… Now that we have the proper means to show the value it could bring, the next step is to get the banks onboard. We are actively discussing with 2 of them and will hopefully have an agreement to move forward by the end of 2016. Yup, not as fast as we would all like, but it’s already a big step for those banks.</p><h3>Marc Lainez on Twitter</h3><p>Multi banking in Belgium today... We want to fix that with https://t.co/DQoELsWk9l #fintech #betech</p><h3>How can you help?</h3><p>A lot of you asked how you could help. Several suggested they could develop and maintain libraries in different programming languages and that’s awesome!</p><p>However, the simplest and best way you can help us is to bug your bank! Contact your relationship manager, send a helpdesk message, tweet, post on facebook, tell your bank you want to access your data through Omnibank.</p><p>The more software developers, agencies, companies ask their bank to be supported by Omnibank, the easiest it will be for us to convince their Marketing and Innovation departments. Use #omnibankio so we can keep track of your actions.</p><h3>Our message to the banks</h3><p>You should not fear what’s ahead. Disruption of the financial sector and digitalisation will happen. We believe it is a chance for banks to reinforce the relationship they have with their existing customers.</p><p>The best move is to be ahead of the curve, to consider this a chance to build a new distribution channel with its own user experience, a distribution channel focused on software developers. Because they are also customers of yours and they are and will be the ones building software for your competitors, Fintechs, startups or for the SME next door. Don’t ignore their call and let us help you figure out how to deal with them.</p><p>We are exactly like those software developers and we know what they would like to use in their day to day work. We are ready to help you, but will you let us?</p><p><em>Drop us an email at contact@omnibank.io or follow us on twitter </em><a href="http://twitter.com/omnibank_io"><em>@omnibank_io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaa05052d59c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/omnibank-is-still-alive-and-kicking-eaa05052d59c">Omnibank is still alive and kicking!</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We built an API on top of Belgian banks]]></title>
            <link>https://medium.com/ibanity/we-built-an-api-on-top-of-belgian-banks-2331c6988689?source=rss----ddc1cea2a0f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/2331c6988689</guid>
            <category><![CDATA[banks]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[belgium]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Marc Lainez]]></dc:creator>
            <pubDate>Mon, 06 Mar 2017 09:52:41 GMT</pubDate>
            <atom:updated>2018-02-15T15:15:46.706Z</atom:updated>
            <content:encoded><![CDATA[<p><em>UPDATE 01/18: Omnibank/Ibanity has been acquired by Isabel Group in September 09/17, </em><a href="https://medium.com/ibanity/ibanity-joins-isabel-group-e6457dbfa140"><em>read the story.</em></a></p><p><em>UPDATE 03/17: Omnibank is now renamed ibanity for compliance reasons, you can read why in </em><a href="https://medium.com/@mlainez/omnibank-is-dead-say-hi-to-ibanity-c10993f8b765#.d0etgem0b"><em>our latest story</em></a><em>.</em></p><p>For a while now, in Belgium, we’ve been quite forgotten in the tech revolution that is happening in the banking sector. Whether you’re talking about PFMs (Personal Financial Manager) such as Mint.com, Linxo.com or other services in the likes of Plaid.com or Mondo to name a few, all these innovations have been happening everywhere but in Belgium.</p><p>To enable this, and make it possible for such an ecosystem to rise, you need a shift in the banks mindset, a shift to “let go”, and see what can be built on top of some of the data they possess.</p><p>For example, PFMs use bank transaction data, enrich them with external data sources, let you set personal goals, automated notifications etc…</p><p>Should you want to build something like this in Belgium, you’re stuck with last century’s technologies and barriers to entry, several have tried but as soon as they had to talk to Belgian banks, they failed. Hopefully, <a href="http://ec.europa.eu/finance/payments/framework/index_en.htm">PSD2, the new version of the European directive</a> on payment services, is going to lower those barriers, but it will likely still be expensive for startups and SMEs to build the proper tech to access their banking data.</p><p>We’re happy to announce that we have found a way to access bank accounts’ transactions data and are now able to allow developers to connect to their customers’ bank accounts or to their own. We are officially launching this project named Omnibank.</p><p><a href="http://www.omnibank.io/">Omnibank - An API on top of banks</a></p><h4>We are building an API that will be an aggregator of banking data on top of all popular Belgian and European banks</h4><p>We are currently working on an API layer on top of most banks in Belgium that will make it possible, in one place, to get information about your customers’ accounts at all those supported banks and let them authorise which accounts from which banks can be accessed by your products using our API.</p><h4><strong>Supporting 2 banks already</strong></h4><p>Agreed, it’s not much, but it’s a start. Although the goal is to support most of them, we can already say that after a few days working on it, we managed to hook up to 2 banks in Belgium. We wanted to have more than one to make sure our technical solution could be repeatable and it seems it is. We are fairly confident that we will be able to add more banks in the following weeks but right now, we want to focus on making it as easy to use as possible before doing that. We are then focusing on our API and documentation to onboard projects asap before opening to the public.</p><h4>Why would you want that?</h4><ol><li>You are a Fintech startup that has been waiting for a while to get access to your customers’ banking transactions data through an API instead of CODA files and/or CSV imports to build new products around banks’ transactions data (PFMs, savings advisors, etc…).</li><li>You are a startup or an SME that needs accounting automation because your business model requires it or simply to save time and alleviate human errors.</li><li>You are a developper or a maker that simply wants to play around with your bank transaction data. Your money, your rules!</li><li>You are a financial or insurance institution that would like to visualise the complete financial overview of your customers to help them make better decisions. Or you are a bank with internal innovation programs that want to quickly build POCs of new product ideas without going through the regular slow internal IT channels.</li></ol><h3>No, we are not faking it</h3><p>At the moment, we wrote a set of tools to build bots that help us manage our incoming and outgoing transactions. We’ve linked this to our invoicing system and have simply built a small slack bot to have full transparency about money movements in our company. We’ve made a gif of our slack bot, most of the information is not shown as it is quite sensible data but if you don’t trust us, come visit us, we’ll be happy to show you a real life “uncensored” demo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*AzM4HjGepaN4M3BLjWAS6g.gif" /><figcaption>Slack bot giving us the balance of our professional account and a list of the last 5 transactions</figcaption></figure><h3>We are looking for alpha testers</h3><p>We are looking for Fintechs or any developer with a project that would like to give it a try and help us shape our API. We want this to be as developer-friendly as possible and would therefore drive this part of our development with real projects. If you have something that would benefit from bank transaction data, subscribe to our waiting list on our website and we’ll get in touch with you.</p><h3>Where do we go from here?</h3><p>Our hope is that if we get enough support from the community and are able to show strong interest to banks, we will find ways to better collaborate with them and make this project durable over time. Currently, our plan is the following:</p><ul><li>First we finish what we started, ie. finalising and fine tuning the API by partnering with real projects.</li><li>Then, we make sure we add at least 5 more Belgian banks on Omnibank (we currently only support two of them, but are working on others).</li><li>After this, we will build libraries for all popular languages and work on a developer portal.</li><li>Once the portal is done, we’ll open for public beta.</li><li>Then, we’ll see, we have plenty of ideas on where to go once all the above is done, and you’ll have plenty of ideas too…</li></ul><h3>What’s the vision?</h3><p>We believe that people should be empowered to manage their bank transactional data the way they want and that they should be given the right to share that information with whichever services they deem fit to get better quality of service and transparency than what their bank is currently offering them. The current state of the Belgian banking industry doesn’t allow this to be done easily for developers. Omnibank will change that.</p><p>So tell us, does it make any sense to you guys or is it just us?</p><p>We are open for feedback and suggestions, let us know how we could help you and what you’d build with an API on top of your bank accounts’ transactions data.</p><p>Contact us at contact@omnibank.io</p><p>Omnibank is a product made by Spin42.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2331c6988689" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibanity/we-built-an-api-on-top-of-belgian-banks-2331c6988689">We built an API on top of Belgian banks</a> was originally published in <a href="https://medium.com/ibanity">Ibanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>