Skip to main content

6 January 2022

ยท 2 min read

New featuresโ€‹

โ†ช๏ธ We fully support all kinds of Received Sepa Direct Debit: Core and B2B.

๐Ÿ”š You can now close an account by API using the closeAccount mutation.

Improvementsโ€‹

โ™ป๏ธ It's now possible to release a card authorization using the Event Simulator.

๐Ÿ” You can now filter cards by statuses for a given Account Membership using the accountMembership.cards query.

๐Ÿ“ƒ Default pagination has been increased to 50 items per page in the payments query in order to align with other queries.

๐Ÿ“ For each card transaction on the Account Statement, the description field now shows the cardholder name and the last four digits of the card.

โœ‰๏ธ Webhooks offer 2 new onboarding events: Onboarding.Created and Onboarding.Updated

๐Ÿ”„ Exponential backoff when retrying failed webhook events, with up to a maximum of 7 retries.

Bug fixโ€‹

โœ… The list of accepted characters in the reference field of the initiateCreditTransfer mutation has been updated to match current SEPA guidelines.

๐Ÿ’ณ The image returned in the cardUrl (card query) is now updated when the Account Member name is updated

๐Ÿ’ฅ When issuing cards, Cardholder names and delivery addresses can include special characters and accents like "Amรฉlie" or "HauptstraรŸe".

Breaking changesโ€‹

๐Ÿ†” It's been 3 months now (that's 3 releases ago), that partners integrating by API must make sure their UX entices users to prove their identity. To give you time to develop this user flow, we've been texting all users about identity verification as soon as they are created. Starting today, we no longer send new users this sms.