📘
Want to access a more technical changelog?
For past versions, you can have more detailed information here
| Modification | Description |
|---|
| Simplify your integration with webhooks | You can now use webhooks to simplify your integration. 4 events are avaiable for now: item created, account created, account created, item refreshed. You can check the documentation here and create webhooks from your dashboard. |
| New data for banks | In List banks endpoint, we added new fields: capabilities (the features available for this bank: ais, single or bulk transfers, single or bulk payments) and linked information (max number of transactions for bulk transfers, max number of characters for the label) |
| New endpoint to list and filter banks | You can use the new Search banks endpoint to filter the banks you want to display to your users depending on the countries (fr, uk, de, es) and the capabilities data (ais, single_transfer, bulk_transfer, single_payment, bulk_payment) |
| Double SCA management | The double SCA sometimes needed for professional banks is nows handled in the Bridge Connect. Your users will see 2 successive pages asking them to enter a code |
| Modification | Description |
|---|
| New data available in your dashboard | Login to your dashboard and access your page and find new data available: your items status and the top banks by items status |
| New flag for transactions from differed debit card accounts | It might happen that your users see duplicated transactions from their differed debit card accounts and their checkin accounts. From now on duplicated transactions have a flag show_client_side at false so you can hide them. See documentation |
| Retrieve a transfer from a transfer request | You can now check if a transfer has been created from a transfer request (therefore know what your users did in the Bridge Pay). Modification is applied for single and bulk transfer requests |
| Link a reference to transfers and bulks | When calling single and bulk transfers endpoint to generate a Bridge Pay link, you can now add a new input client_reference, to help you keeping track of your users single and bulk transfers |
| Modification | Description |
|---|
| New feature: merchant payments | Your users can proceed to payments thanks to our new endpoint Create a payment request. They will go through their bank interface and process a transfer as a payment to your bank account |
| New feature: bulk transfers with Bridge Pay | You can now execute multiple transfers in one user journey, with only one SCA. One bank is available for now: Qonto. Contact us if you want to test it and check the guide |
| New feature: check our connectors statuses by API | If you have an application in production, you can now use a new endpoint to check our connectors statuses. You can use it to automate some actions or communications to your users. Documentation |
| Bridge Pay: pre-fill the beneficiary via receiver account id | You could already pre-fill a transfer's beneficiary so that your user doesn't have to select it in the Bridge Pay, thanks to its IBAN. You can now use the receiver account id instead. Documentation |
| Bridge Connect: pre-fill the bank | When calling the Bridge Connect endpoint, you can define a bank id as an input. With this, your user will directly access to the corresponding bank form, without going through the banks list. Documentation |
| Modification | Description |
|---|
| Bridge Pay: pre-fill the beneficiary via IBAN | You can now pre-fill a transfer's beneficiary so that your user doesn't have to select it in the Bridge Pay. To do it, define an IBAN when calling Send transfer endpoint |
| Dashboard: members invitation | New feature in the dashboard: you can invite members to access your applications. They can see your applications information and edit sandbox apps, but cannot edit production apps. More information |
| KYC | We developed a new endpoint to list KYC data of you user. Please ask us to get the documentation and try the endpoint |
| New connector: Paypal | You users can now synchronize their Paypal account with the Bridge Connect |
| Modification | Description |
|---|
| New dashboard | We deployed a new dashboard where you can manage your applications and customize them. Access the dashboard |
| New category: payment incidents | We improved our categorization engine thanks to a new category for the payment incidents. The id of this new category is 756587. This category will gather the banking commissions and the other payment incidents |
| More details on the items' status | You can now access the status_code_info and the status_code_description to manage the banking connections of your clients. These new fields are detailed on our Items status page |
| Caisse d'Epargne Particuliers | We have migrated to the PSD2 API of the bank Caisse d'Epargne Particuliers. Therefore we are now displaying in Bridge the details of its 15 regional branches |
| Modification | Description |
|---|
| New Bridge Connect | We revamped the Bridge Connect: simplified user journey and new design. You can also select the banks you want to highlight when the user arrives on the banks list. |
| Initiate transfers with Bridge Pay | Your users can now initiare transfers to their trusted beneficiary thanks to our new interface "Bridge Pay". Documentation |
| Future transactions | Transactions have a new field is_future so you know the transaction impacts or not the account balance. False: false : it means the transaction is a debited transaction. True: it means the transaction will be debited in the future and doesn’t affect the account’s balance |
| Accounts' IBAN (AIS) | The Account ressource has a new field for the IBAN. Support for this information varies depending on the account's bank |
| API authentication | The Client-Id and the Client-Secret of your application should be send through Headers and not Params anymore |
| User authentication | The email and the password of your users should be send through Body and not Params anymore |
| Modification | Description |
|---|
| New Bridge Connect | We revamped the Bridge Connect: simplified user journey and new design. You can also select the banks you want to highlight when the user arrives on the banks list. |
| Initiate transfers with Bridge Pay | Your users can now initiare transfers to their trusted beneficiary thanks to our new interface "Bridge Pay". Documentation |
| Future transactions | Transactions have a new field is_future so you know the transaction impacts or not the account balance. False: false : it means the transaction is a debited transaction. True: it means the transaction will be debited in the future and doesn’t affect the account’s balance |
| Accounts' IBAN (AIS) | The Account ressource has a new field for the IBAN. Support for this information varies depending on the account's bank |
| API authentication | The Client-Id and the Client-Secret of your application should be send through Headers and not Params anymore |
| User authentication | The email and the password of your users should be send through Body and not Params anymore |
| Manage Strong Customer Authentication with Bridge Connect | You can manage all the PSD2 authentication complexities with our web application by using the endpoint Manage SCA and Sync |
| Bridge Connect: country selection | You now have the ability to set up the default country for the banks displayed in the Bridge Connect. Use the country parameter in your "Connect an item" call. Available country codes : fr, uk, de, es, nl |
| Bridge Connect: email pre-filling | You now have the ability to pre-fill the email of your user on the email validation page of the Bridge Connect. Use the prefill_email parameter in your "Connect an item" call |
| Bridge Connect steps | You can follow the path of your user in the Bridge Connect funnels in details. How? By interpreting the redirect URL, at the end of the funnel, enriched with parameters. You will be able to know at which step the user has left the funnel |