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

17 July 2025

ยท 2 min read

New featuresโ€‹

๐Ÿ”— Send a SEPA Direct Debit B2B mandate registration link to users with the canInitiatePayments permission. Get the link from your Dashboard > Data > Accounts page.

Improvementsโ€‹

๐Ÿ’ณ One-off single use virtual cards now default to expiring 30 days after creation. This applies when SpendingLimitPeriod is set to Always in the addSingleUseVirtualCard and addSingleUseVirtualCards mutations. You can change this by setting a custom cardContractExpiryDate.

๐Ÿงญ Transaction confirmation documents now follow a new, more readable naming convention that includes the document language. The new format is: TransactionConfirmation_[transactionId]_[documentLanguage].

Updatesโ€‹

๐Ÿชช Starting August 7th, we'll recommend QES as the identification method for German accounts, replacing the current Expert level. If you use Auto, no action is needed. This change will apply automatically.

API updatesโ€‹

Upcoming breaking changesโ€‹

๐Ÿ›‘ Starting August 18th, the initiateCheckMerchantPayment mutation will return a new rejection: MerchantPaymentAlreadyExistsRejection. This occurs when you try to create a merchant payment, but the CMC7 value is already used by an existing payment that hasn't been Rejected or Canceled. If the existing payment with the same CMC7 was Rejected or Canceled, your mutation will still succeed.

๐Ÿ’ณ Starting August 21st, refund transactions will be linked to the paymentId of their original debit authorization when referenced by merchants. This change affects you only if you expect debit clearing transactions on a debit authorization.