Payments

​

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.

​

Improvements

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

​

Bug fixes

• Fixed SCT payment return in the new UI redirecting to the old UI payment form instead of staying in the new UI.

​

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.