core v.26.10.13-26.10.22
client v.26.10.9-26.10.10
New Features
Integrations
Convera outgoing payment webhooks. Convera webhooks for outgoing payments are now fully operational and provide real-time transaction status updates. Returned payments, whether full or partial, are processed automatically: a refund is created and the returned funds are credited back to the account balance.
Improvements
Compliance
Sumsub own-account transfer flag. Transactions sent to Sumsub for monitoring now include a flag that identifies transfers between a user's own accounts, such as between an IBAN and a debit card. This lets you configure rules in the Sumsub dashboard so these internal transfers are not flagged as suspicious. Clients using Sumsub TMS should update their monitoring rules to use the new property.
Reports
Accounting report columns and date filter. The Accounting and Historical Transactions Accounting reports, including their API exports, now have dedicated columns for Client ID, Client type, Internal Account Number, IBAN and Provider Number. A new Date basis filter in the interface and API generates reports by either the creation or the update date of transactions.
Fixes
Transfers
NIUM purpose codes. Initiating payments through NIUM with certain purpose codes no longer causes a system error. Seven-character purpose codes required by the provider are now supported, so these transfers are processed successfully.
LITAS SEPA Instant late rejections. Incoming LITAS SEPA Instant transfers no longer stall in an intermediate state when a late clearing rejection arrives during verification. Late rejections now move the payment to a declined status without manual intervention. Improved transaction locking and optimized Salv verification timeouts prevent deadlocks.
ClearBank payment references. Incoming payment references from ClearBank webhooks for SEPA Credit Transfers and TARGET2 payments are now captured in transaction descriptions. They are therefore included in exported CSV account statements and forwarded to compliance screening.
Payment template method. Applying a payment template no longer defaults the payment method to standard SEPA. Payments created from templates now use the intended payment method.
Integrations
IFX fee and balance requests. Errors when fetching fee and balance information for payments from IFX accounts are resolved, as account validation and balance checks keep working with the optimized handling of encrypted provider credentials. If an account's integration settings need an update, administrators can re-enter the credentials on the provider configuration page to restore full payment functionality.
Reports
iFast and iFX settlement dates. Completed iFast and iFX transactions in the Accounting report previously appeared on dates that differed from provider statements, because the settlement date was recorded at creation rather than completion. The settlement date now matches the completion date or the confirmed value date reported by iFast and iFX, so daily closing balances in the report match provider statements.