a year ago
REPAY Payables: Version 296.1
Release Date: January 25, 2024
This release corrects an issue where some customers couldn't see the payments associated with their payment groups. It also includes custom reconciliation file work for a client and internal fixes for issues with paused payments, virtual card generation, and RAPs.
Release Notes
| Ticket | Type | Description |
|---|---|---|
| CPAY-6418 | Feature | Payables API. Added mapping for the paused payment status code. The paymentStatus field now returns the status Pending when the payment pmt_stat_cd = 'S' (paused). Previously, it returned null. |
| CPAY-6027 | Feature | Custom work. Updated a client's daily reconciliation file. For virtual cards, the DOCNUMBR field includes the card token instead of the last 4 digits of the card. |
| CPAY-6060 | Fix | Internal. Payments > Manage RAPs. You couldn't view the list of RAPs without filtering (by customer, vendor, assignee, or status); the screen displayed the following error:DataTables warning: table id=rapPaymentsDatatable - Ajax error.This issue was caused by the large number of RAPs returned; we reduced the default search range to six weeks from 12 and service performance improved. |
| CPAY-6188 | Fix | Paused payments. When a vendor was enrolled, payments for that vendor weren't automatically unpaused and sent. |
| CPAY-6393 | Fix | Internal. Virtual card transactions with certain dates (for example, 01/08/2024) were rejected. With this fix, the transaction processor resolves the date parsing issue from the previous release. |
| CPAY-6426 | Fix | Internal. The “Funded Payment Processor” has greater control over the loaded configuration and validates the pool ID and organization ID to ensure requests are routed to the correct virtual card provider. |
| CPAY-6746 | Fix | Some customers reported that when they expanded a payment group, the payments weren't displayed. This fix rolls back a change in the previous release, where when customer information was updated, REPAY Payables attempted to re-index all of the customer's payments to improve search performance. If the customer had a large number of payments, this increased the database load and disrupted other payment update processes. |