Payments

​

Bug fixes

• Incoming cancellation requests are now linked to the original payment when the requesting bank uses the 8-character BIC, or a settlement date that differs from the payment’s while all other details match. Previously such requests could appear without a linked payment.
• Liquidity webhooks are no longer marked as failed when your endpoint replies with a response body.
• Fixed Verification of Payee requests with national characters in the account holder name returning CANNOT_VERIFY. Names are now converted to the EPC Basic Latin character set before being forwarded to the responding PSP, in line with EPC VoP API Specifications v1.1.1, §3.1, p. 15.
• Transfers between CENTROlink settlement accounts now accept only your SCT and SCT Inst accounts of the same BIC. Other combinations are refused with 400 TRANSFER_BETWEEN_DIFFERENT_SCHEMES instead of being accepted and left pending.

​

New features

• You can now choose a light, dark or system appearance under Settings > Appearance. Your choice is remembered in your browser.
• Filter the payments list by transaction type, including several types at once. The CSV export uses the same filter.
• Payment and cancellation status history now shows how much time passed between statuses.
• EKS participants can see their current maximum holding amount and the date it applies from on the Liquidity page.
• EKS participants can move liquidity from a registered operational account to their EKS SCT or SCT Inst settlement account. See Transfers between settlement accounts.

​

Improvements

• The menu is now a single level: Liquidity, Payments, Returns, Cancellations and Investigations. Payments and Returns open the payments list filtered by type, and Cancellations and Investigations have a Needs attention tab counting inbound requests that wait for your answer.
• Transfers between settlement accounts are now transferType: INTERNAL in POST /v1/nostro-accounts/transfers and GET /v1/nostro-accounts/transfers. transferType is optional and defaults to INTERNAL. Responses return INTERNAL where they returned INTRA_NOSTRO; requests with INTRA_NOSTRO are still accepted.
• Withdrawals to a safeguarding account take an optional purpose of up to 140 characters, which defaults to “Transfer to safeguarding account”. The transfer list now returns debtorBankName and creditorBankName, and the transfer form shows the BIC of each account.
• Verification of Payee now returns a match when names differ only in punctuation or quotation marks, and recognises Slovak, Czech and Polish legal forms such as s.r.o., a.s. and sp. z o.o..

​

Bug fixes

• Multi-page SWIFT statements are now imported in full; intermediate pages carrying an interim balance were previously rejected.
• SWIFT cancellation reason text is no longer split across lines, and UETR values are passed intact.
• Payment list filters now reject invalid or incomplete IBANs, show a clear empty state, and no longer add entries to your browser history.

​

New features

• Account creation is now governed by your subscription plan; plans with unlimited accounts are unaffected. Contact us if you reach your plan’s limit.
• The Liquidity dashboard now shows a notice when your CENTROlink account at Lietuvos bankas exceeds its maximum holding amount, with the excess amount and the deadline to withdraw it. You can start a withdrawal to your safeguarding account from the notice, and the notice clears once the withdrawal completes.
• Added the MAX_HOLDING_AMOUNT_BREACHED webhook, sent when your CENTROlink account exceeds its maximum holding amount. Set its URL in the webhook settings.

​

Improvements

• Liquidity accounts can now be filtered by bank, in addition to rail and BIC.
• When creating a safeguarding transfer you can add operational and safeguarding accounts on the spot; they are saved to your Liquidity settings, allowing to create one-click transfers between them.
• Liquidity transfers show clearer IBAN validation messages, and transfer statuses use the same colours as payment statuses.

​

Bug fixes

• Fixed copied payments with address details being blocked by validation of hidden fields; the address section now opens with the original values.
• Fixed automatic liquidity stopping when the optional Warning Balance is not configured.
• Fixed overdrawn SWIFT nostro balances being stored and displayed as positive amounts.
• Excluded SWIFT nostro balances from SEPA automatic-liquidity totals and alerts.

​

New features

• Added a dedicated Liquidity transfers view with filtering, transfer details, lifecycle history, and related operations.
• Added a flow for moving excess liquidity from operational accounts to configured safeguarding accounts.
• Added configurable columns, pinning, ordering, and row density for Payments, Investigations, and Cancellations tables.
• Added support for SWIFT currencies with three fractional digits: BHD, IQD, JOD, KWD, LYD, OMR, and TND.
• Added processing of inbound SWIFT MT950 account statements, including statement publication and nostro balance updates.
• Added CSV exports for cancellations and investigations that preserve the selected filters and sort order.

​

Improvements

• Extended payment-message XML downloads to SWIFT, TARGET2, and EKS payments.
• Added rail and BIC filters to the Liquidity accounts view.
• Improved VoP result feedback, including clearer match states and keyboard-accessible suggested names.

​

New features

• Balances of SEPA Instant liquidity accounts at CENTROlink are now updated from the new end-of-day balance notification (IAPNOT).

​

Improvements

• Reject, return, and refund requests for SDD collections are now checked against the scheme deadlines. Requests past the deadline are refused with a 4xx error before a return is created, instead of being sent to the clearing system and rejected there.
• Return and Refund for SDD collections are now one Return action with the applicable reasons listed in the UI. Expired reasons cannot be selected, and payment details show the settlement age and the submit-by date for the chosen reason.
• Outgoing SWIFT payments and returns now move to Accepted as soon as the correspondent bank’s statement confirms the debit, regardless of the statement format. Before, payments through some correspondent banks stayed in their previous status.
• The next settlement date shown when creating a payment now uses the calendar of the selected account’s payment scheme.
• The old version of the web interface has been retired.

​

Bug fixes

• Preserved original debtor and creditor data in payment API responses while keeping corrected liquidity-transfer parties in the dashboard.
• Removed aggregated balance totals from SWIFT correspondent rows in the Liquidity accounts view.

​

New features

• Added UETR filtering and the uetr response field to GET /v3/payments.

​

Bug fixes

• Fixed SWIFT nostro balances to show amounts exactly as reported by correspondent banks, including non-EUR accounts, without mixing movements across accounts.
• Fixed an unavailable connector configuration for one nostro account preventing the remaining liquidity accounts from loading.
• Fixed inbound SWIFT messages being assigned to the wrong tenant when multiple tenants share one application channel.
• Corrected SWIFT cancellation rejection handling by removing the unsupported NARR reason, allowing AC04 and AM04, and including the returned payment’s UETR for ARDT responses.

​

New features

• Added a Liquidity accounts view that groups balances by payment rail and institution, including correspondent banks for SWIFT accounts.
• Added a slide-over flow for moving funds between eligible nostro accounts.
• Added reject, return, and refund actions for eligible SDD Core transactions in payment details.
• Added downloads of available original SEPA messages from payment status history and the payment download menu.
• SWIFT payment validation now accepts institutions reachable through a published correspondent relationship.

​

Bug fixes

• Fixed cancellation actions allowing mixed SCT and SCT Inst batches or a new request while another cancellation is in progress.
• Fixed VoP routing selecting a participant registered for a different verification scheme.

​

New features

• Added automatic payment status requests for outbound SEPA Instant payments that remain in Sent to clear, with a tenant-level setting to enable or disable the automation.
• Added payment status request reminders for pending outbound claim non-receipt investigations, including reminder eligibility and history in the API and dashboard UI.
• Added settlement account currency to SWIFT payments created through the dashboard UI.

​

Improvements

• SDD reversals are now validated against the five-interbank-business-day submission window; expired reversals and reversals whose deadline cannot be verified are rejected before submission.
• Swapped the debtor and creditor columns in the SEPA payments table.
• Updated outgoing SWIFT payment and return messages to include instructed amounts in the required schema order.

​

Bug fixes

• Fixed liquidity-transfer adjustment legs displaying incorrect directions, amount signs, party names, and accounts in the dashboard UI and exported PDFs.

​

New features

• Added the signer role to user administration for organization administrators.
• Added POST /v3/payments/sepa for creating SEPA CT and SEPA Instant payments with the v3 payment schema and idempotency protection.
• Added GET /v3/payments for retrieving payment summaries with cursor-based pagination and filtering.
• Added filtering by UETR for SWIFT and T2 payments in the dashboard UI.
• Added VoP beneficiary verification when creating SEPA payments in the dashboard UI for clients using both services.

​

Bug fixes

• Fixed investigation searches failing when the case ID is missing.
• Fixed inbound payment returns dead-lettering when OrgnlTxRef omits debtor or creditor details, which left cancellations stuck in CANCELLATION_IN_PROGRESS.
• Fixed inbound payment cancellation requests failing to correlate when OrgnlEndToEndId is NOTPROVIDED but the stored transaction has an end-to-end ID.

​

New features

• Added cancellation reasons and cancellation reason filtering to the dashboard UI.
• Added Mark as Completed and Return actions for accepted payments in the dashboard UI. Completed payments now show the Return action.
• Added an API endpoint for looking up VoP directory accounts by IBAN.

​

Improvements

• Added SWIFT participation validation to bank information lookups.
• Added SWIFT participation validation when initiating SWIFT payments.
• Added the settlement BIC column to payment exports in the dashboard UI.
• Documented that the Nostro account balance and statement APIs accept non-IBAN account identifiers.

​

New features

• Added the bank name and a structured bank address (street, building, postal code, town, country subdivision, and country) to the Get bank information for IBAN response. Both come from SWIFT reference data and are returned only when the bank is reachable via SWIFT (sepaSchemas.SWIFTCORE: true). Use them to prefill creditor agent details on SWIFT payment forms.

​

New features

• Added client-defined metadata values to SCT, INST, and SDD payment creation, transaction details, and exact-match transaction searches.
• Added an option to download SWIFT balance statements.

​

New features

• Added optional debtor account currency and name fields to the SWIFT payment form in the dashboard UI.

​

New features

• Added Accepted, Completed, and Rejected status updates for outgoing SWIFT payment returns.
• Added display of the VoP client secret in the UI.

​

Bug fixes

• Fixed payment table content being cut off on laptop-width screens in the dashboard UI.

​

New features

• Added optional debtor account currency and name fields to the Create SWIFT Payment API.

​

Bug fixes

• Added transliteration of unsupported characters in debtor and creditor names and postal addresses for outgoing SWIFT payments.

​

New features

• Added support for creating T2 payments from the UI.
• Added processing of inbound T2 credit transfers, including webhook notifications.
• Added processing of inbound T2 status update messages.

​

Bug fixes

• Fixed QWAC certificate validation rejecting valid chains when an intermediate CA’s OCSP responder returns UNKNOWN; validation now falls back to the CRL before failing.
• Fixed bank name not being populated on payments created through the UI.

​

Bug fixes

• Fixed inbound pacs.002 messages dead-lettering on transient optimistic-lock conflicts; they are now retried in-process.

​

New features

• Added support for matching inbound pacs.002 and pacs.028 messages by originalMsgId.
• Added tenant-scoped webhook configuration with per-tenant limits, role-based access, audit logging, and rule-based filtering.

​

Bug fixes

• Fixed inbound SWIFT pacs.004 returns failing when the original creditor (OrgnlTxRef/Cdtr) has no account block.

​

Bug fixes

• Fixed participant validation resolving an incorrect BIC.
• Fixed intermittent failures when persisting transaction status history changes.

​

New features

• Added role assignment in the new user dashboard UI.
• Added display of the settlement BIC and account (IBAN or other) for SWIFT payments in the UI.
• Added the currency column to the payments statement CSV export.

​

Improvements

• Added the ability to include additional fields in webhook payloads that map a cancellation to its original payment when the original payment is not in the system.

​

Bug fixes

• Fixed payments being rejected due to idempotency record collisions.
• Fixed inbound camt.027 messages failing to process when the optional InstrForAssgne element is missing.
• Fixed payment amount limit not being enforced.
• Fixed SWIFT payment copying not working in the UI.

​

Improvements

• Replaced the SEPA message ID with the SWIFT message ID in the SWIFT payment profile, and added the UETR field.
• Hid the cancel action for outgoing SWIFT payments until cancellation is supported.

​

New features

• Added the investigations role for viewing and managing inquiries.

​

Improvements

• Made the settlement BIC parameter optional in the SWIFT payment form when other account is selected.

​

Bug fixes

• Removed scheme.proprietary from debtor identification in the SWIFT API, as CBPR+ does not allow it.
• Fixed SWIFT Payment API response not returning request parameters and mapping fields incorrectly.
• Fixed SWIFT payment PDF download failing for return transactions when account information is missing.

​

New features

• Added claim non-receipt initiation and processing via API.
• Inbound SEPA CT payments with a future settlement date now transition to Accepted status first and move to Completed only when the settlement date arrives.
• Added inquiry processing and management in the UI.

​

Bug fixes

• Fixed SEPA INST payment reject and accept responses failing to be delivered.

​

Bug fixes

• Fixed SWIFT outbound payment failing due to incorrect service code.
• Fixed SWIFT outbound payment error when remittance information is not provided.

​

New features

• Added purpose field to the SWIFT payment initiation form in the UI.
• Added field validations and mandatory parameter enforcement for SWIFT payment creation in the UI.
• Added routing code support for US market SWIFT payments in USD.
• Added party identification (orgId, prvtId) support across all payment methods (SEPA CT, INST, SDD, SWIFT) for payments, returns, and cancellation requests.

​

Bug fixes

• Fixed bank name not rendering for SWIFT inbound payment returns.

​

New features

• Exposed account statement dates endpoint in the API documentation.
• Added liquidity-viewer role to manageable roles in the user administration UI.

​

Bug fixes

• Fixed CSV download failing when a payment has no BIC.
• Fixed outbound pacs.002 response to pacs.028 inquiry requests not setting AccptncDtTm.
• Corrected trxId in the payment-cancellation-status-change webhook documentation to be marked as not required.

​

New features

• Finalized the investigations API with unified statuses, transitions, paths, and response structure.

​

Bug fixes

• Fixed an empty SvcLvl XML element being generated in outgoing SWIFT pacs.008 messages when serviceLevel is not provided, which caused schema validation failures.
• Fixed Additional Information validation for SEPA Instant cancellation requests to allow the field only for reason codes CUST, AM09, AC03, and FRAD, and removed the incorrect TECH value.
• Fixed pacs.002 consumption failing for SDD payments sent within the same tenant scope.

​

New features

• Added settlement.priority parameter to the Create SWIFT Payment API, supporting URGT, HIGH, and NORM values for controlling payment settlement priority.
• Added debtor.agentAccount parameters (iban, otherAccountId, currency) to the Create SWIFT Payment API for specifying the debtor agent nostro account.
• Webhook notifications with status Sent to clear are now sent for SWIFT payments.
• Added incoming SWIFT pacs.004 (Payment Return) message processing, updating original transaction status and creating return transactions.
• Introduced delayed accept mode for incoming SEPA INST payments, which automatically accepts payments if no API response is received within a configurable time window.
• Added camt.054_LB_O liquidity transfer statement downloads via API and UI.
• Inbound SCT/INST cancellation requests can now be processed even when the original transaction is not in the system, enabling accept and reject workflows without manual intervention.

​

Improvements

• Moved messageRouting.receiverBic to settlement.bic in the Create SWIFT Payment API and removed the messageRouting object.
• Added settlement date column and payment purpose to the new UI payments table and payment profile.
• Fixed inconsistencies between inbound SWIFT pacs.008 message data and stored transaction data.
• Updated the SEPA unauthorized character conversion list per the EPC217-08 conversion table.

​

Bug fixes

• Fixed an issue where rescheduled payments reused the same idempotency key, causing outgoing messages to not be sent.
• Fixed messageRouting.receiverBic not being forwarded to the XML AppHdr/To and InstdAgt fields, which incorrectly fell back to creditor.agentBic.
• Fixed user role assignment in the new UI dashboard to allow adding roles to users, not just removing them.

​

New features

• purposeCode is now mandatory for UAE outbound SWIFT payments and optional for all others.
• Extended the list of allowed values for the trx_purpose_information parameter in SEPA payment creation.
• Added a DECLINE action in the UI for transactions in to_sign status.
• Added SWIFT MT940 account statement processing, transforming settlement confirmations into payment status updates.
• Added SWIFT MT199 free format message processing for payment rejection handling.
• SWIFT transactions can now be created without requiring BIC codes.

​

Improvements

• Payment currency is now displayed alongside amounts in all UI tables.
• categoryPurposeCode and categoryPurposeProprietary are now both optional but mutually exclusive in SWIFT payment creation.
• Removed hybrid and unstructured address support for outgoing SWIFT payments; only structured addresses are now accepted with country and townName as required fields.
• creditor.agentBic is no longer mandatory in the Create SWIFT Payment API; the system resolves it automatically from the creditor IBAN when possible.
• Removed instructionId from the Create SWIFT Payment API request; it is now generated internally.
• Removed COVE from allowed values for settlement.method in SWIFT payment creation; only INDA and INGA are supported.
• Removed debtor.agentBic from the SWIFT payment API request; the system now resolves and validates it from the debtor IBAN.

​

Bug fixes

• Fixed incorrect payment method when switching from SEPA CT to SEPA INST during payment creation in the UI.
• Fixed creditor and debtor IBANs not being nullable when exporting CSV.
• Fixed SCT payment return in the new UI redirecting to the old UI payment form instead of staying in the new UI.

​

Improvements

• Added pacs.002 attachment for pacs.004 SDD to the reprocessing workflow.

​

Bug fixes

• Fixed the API response when settlement.iban is not provided to return a descriptive validation error instead of a generic error message.
• Fixed an issue where the group status reject reason code from pacs.002 messages was not saved for rejected transactions.

​

Improvements

• Removed unused address parameters from the API.

​

Bug fixes

• Resolved a bug for a scheduled payment.
• Fixed status synchronization issues for inter-account transfers.

​

New features

• The bank-info/iban API endpoint now returns the bank name alongside BIC and SEPA schema information, providing more comprehensive bank details for payment validation. This is an optional feature — contact support to enable it.
• Users with the liquidity-viewer role can now download Nostro account statements directly from the UI, improving self-service capabilities for liquidity management.

​

Improvements

• Updated company properties (name, address, code) in payment PDF printouts to reflect current registration details.

​

Bug fixes

• Fixed an issue preventing users from downloading CAMT054D SDD statements through the UI.

​

Bug fixes

• The debtor name field is now mandatory in SEPA Direct Debit payment initiation, preventing syntax validation errors and ensuring SEPA compliance.
• Resolved JSON format errors when retrieving Nostro account statements via API.
• Fixed an issue where debtor city was omitted from outgoing pacs.008 messages.
• Fixed race conditions in message processing event consumption under high load.

​

New features

• Introduced automated liquidity management for CENTROlink, allowing clients to configure automatic fund transfers between SCT and INST accounts to maintain operational liquidity.
• Added validation for category purpose codes (FCOL, FCIN, INTE) requiring proper party identification.
• Updated allowed values for payment purpose information to align with current SEPA specifications.

​

Improvements

• Removed transaction limit for UI exports. Clients can now export their complete transaction history without restrictions.
• Made the enhanced cancellation request processing flow more configurable.

​

Performance

• Significantly improved database performance when processing batched Credit Transfer messages through bulk operations.
• Improved cursor-based search performance through optimized sort operations.