In this release, we’ve introduced some new features and enhancements to the PayConex platform, including updated processor integrations, and improved system performance. We’ve also resolved a number of issues to ensure a smoother, more reliable user experience. Below is a summary of the key updates and fixes included in this release.

What’s New

Automatic Inclusion of Mastercard MPG ID

Transactions processed through PayConex's connections with RapidConnect, RapidConnect-North, and TSYS now automatically include the Mastercard Merchant Payment Gateway ID (MPG ID). This update ensures compliance with Mastercard’s requirements by embedding the assigned MPG ID in all Mastercard authorization requests helping to prevent declines related to missing IDs. Other PayConex processor connections will implement the same solution as they add support.

Refactored File-Based Settlement Processes

The file-based settlement processes for RapidConnect, RapidConnect-North, TSYS, and Chase Paymentech have been refactored. These backend improvements boost performance and will allow the system to be further expanded upon for features that are planned to be added in the future.

Additionally, our team has also updated each settlement job to better meet cutoff times, ensuring that transactions are batched and settled within the intended daily cutoff windows for greater accuracy and consistency.

Bug Fixes

Incorrect `Invoice_Number` on Elavon Refunds

Fixed an issue where refunds on the Elavon platform were sent with an incorrect Invoice_Number value (showing the original transaction’s ID instead of the refund’s ID). Refund transactions now include the correct unique identifier in the Invoice_Number field at Elavon, ensuring accurate reporting and reconciliation.

Undefined Authentication Value for 3-D Secure Transactions

Addressed a bug in the 3-D Secure system where an undefined authentication value was returned in certain error scenarios. The system will now handle unexpected outcomes more gracefully, ensuring that an appropriate authentication status or error message is provided instead of an “undefined” value.

Protocol Inconsistencies in 3-D Secure Challenges

Resolved inconsistencies in protocol version and status reporting for 3-D Secure transactions that required a challenge. Previously, when a 3-D Secure challenge was needed, the system’s status callback could return a status of "U" (undefined/unavailable) along with an incorrect protocol version. The challenge flow now consistently reports the correct protocol version and status, providing accurate results for challenge-required authentication cases.

Elavon Settlement Auth Pattern Mismatch

Updated the Elavon settlement logic to correctly match authorization patterns. This fix resolves an issue that caused certain Elavon transactions — which had been authorized successfully — to fail during settlement due to a regex pattern mismatch. Now, the settlement process properly recognizes the auth records, and those transactions settle without errors.

Account Updater API “Brand Not Found” Error

Fixed a problem where ACH tokens were being sent to the account updater service and the error returned was “brand not found” error. The API will now provide back an error message stating that the transaction is not a card transaction.

Second Partial Refund on Sales with Additional Fee Parameter

Resolved an issue with our Elavon integration that prevented a second partial refund from processing on sales that included an additional fee. Previously, attempting a second partial refund on a transaction with an added fee could fail with an “Invalid Amount” error. Now, multiple partial refunds (up to the total of the original sale amount) can be completed successfully even if the sale had extra fees applied.

Browser-Authenticate Null-to-Array Error

Fixed a backend error that was triggered by a null-to-array conversion during browser-based authentication. This issue caused a “browser-authenticate” error in certain scenarios. With this release, the conversion is handled properly, and the authentication flow proceeds without throwing this error.

Duplicate Accounts in Search Results

Fixed an issue where the same account could appear twice in certain account search results. The search functionality has been corrected to eliminate duplicate entries, so each account is now listed only once in the results as expected.

Authorization Codes on MyChart Staging Payment Page

Ensured that the MyChart integration properly displays authorization codes on the payment processed page. Previously, the auth code might not appear for a processed payment in the MyChart staging environment, causing confusion during testing. With this fix, the authorization code is shown correctly on the confirmation page after a payment is processed in MyChart’s staging site.

Two-Factor Login Tab Title Fix

Corrected the browser tab title for the two-factor authentication login page. It was previously mislabelled as “Forgot Password,” which was misleading. The tab title now correctly reflects the two-factor login page, providing a consistent and accurate title when users are entering their authentication code.

We appreciate your feedback and continued support. If you encounter any issues or have questions regarding this release, please contact our customer service team at service@bluefin.com. We look forward to bringing you even more improvements in future releases!

Guides

Release Notes

Discussions