Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

16 December 2021

ยท 2 min read

New featuresโ€‹

๐Ÿคณ Users can now consent using biometry. To try it out for yourself, just clear your browser data. During your next consent, we'll ask you to register your FaceId, TouchId, or Fingerprint. Passcode will only be requested if a user has changed their mobile device.

๐Ÿ“ฒ Some of you wish to send notifications via your own app, to offer a great UX just like the best neobanks. This is now possible. Just define your preferred consent notification channel, SMS or App, by using the new updateUserConsentSettings mutation.

โœ… Thanks to the new updateOnboarding and finalizeOnboarding mutations you are not obligated to use our #nocode interfaces. You can onboard customers directly from your product, if you prefer.

Improvementsโ€‹

๐Ÿ” We added new account filters : canManageAccountMembership, canManageBeneficiaries, canInitiatePayments and new accountMemberships filters: status, canInitiatePayments, canManageAccountMembership, canManageBeneficiaries.

๐Ÿ“œ The list of transactions associated to a received direct debit mandate can now be retrieved using the API.

๐Ÿƒ The dashboard lets you sort webhook event logs using 2 new filters: eventId and resourceId. View each webhook's KPIs for the last 7 days: hits, counter, and error rate. We also added 2 new events: Onboarding.created and Onboarding.updated.

๐Ÿšฎ Transactions where paymentProduct is SEPACreditTransfer and status is Upcoming can now be canceled using the cancelTransaction mutation.

Bug fixesโ€‹

๐Ÿ’ณ When requesting physical cards, the Company Name and the Name/Last Name are now truncated to 38 characters. This is a mail delivery requirement.

๐ŸŒ The card language (used for 3DS, ATM screens and delivery envelopes) is dynamically assigned. Available languages: DE, FR, IT, NL, EN, ES. When a language is not available, the default language is EN.

Breaking changesโ€‹

๐Ÿ”ข Pagination on the accountHolders, accountMemberships, and accounts queries has been fixed. It might break if you implement the filter on the front-end. These queries now only return the requested number of items, rather than all items at once.