Changelog

Enhanced Transaction Handling

After extensive development, our platform now supports seamless and secure transaction processing. This upgrade ensures zero-downtime during payment operations, the ability to revert transactions, and safeguards against unauthorized modifications.

New & Improved:

• Payment Filters: AI Filters now enhance existing payment filters, providing more accurate transaction categorizations.
• Notifications: Upon receiving a notification about a payment issue, the resolution input field will now automatically appear.
• Transaction History: Users can now browse through multiple transaction records without needing to refresh the page.
• Templates: When creating a payment template from an existing transaction, users can now choose which account to associate it with.

Fixes:

• Dashboard: Improved the handling of transaction summaries in list or board layout, with automatic date updates.
• Dashboard: Ensured the order of columns on transaction dashboards matches the order of payment milestones displayed in the sidebar.
• Desktop Application: Fixed a glitch that prevented PDF export of transaction reports in the absence of connected printers.
• Help Center: Enhanced the capability to access payment-related documentation links directly from the in-app help center.
• Transaction Editor: The user mention feature now respects the 'Display full names' setting in transaction comments.
• Filters: Resolved an inconsistency where filter queries with 'includes any' settings sometimes returned incorrect results.

For more information, refer to our documentation.

New Payment Regions and Replicas

Our platform now supports setting up same-region payment replicas. These replicas are dedicated, read-only units designed to handle payment read operations on the same dataset as their corresponding read-write instances.

Use Regions to Advance:

• Enhanced Throughput: Distribute read operations across multiple replicas to improve throughput for all types of payment workloads.
• Dedicated Read-only Workloads: Assign analytical and reporting tasks to a read replica to maintain the performance of your main payment processing workload.
• Controlled Data Access: Grant read-only access to specific applications or users who do not require write permissions.
• Resource Customization: Customize CPU and memory resources for each read replica according to the specific requirements of different applications or users.
• Customization Features: Instantly create and customize resources of one or more read replicas for any payment branch, adjusting the allocated vCPU and memory as needed.

For more information, refer to our documentation post on payment replicas or the read replicas section in the documentation.