PayConex - 08.13.2024

This month's PayConex release brings a series of important updates and bug fixes aimed at enhancing the platform's reliability and usability. Key improvements include resolving issues with duplicated reportable fields in custom reports, fixing recurring transaction setup errors for RapidConnect merchants, and correcting transaction metadata for merchants using Elavon. Additionally, we've improved error handling during connectivity issues with Accertify, ensuring smoother transaction processing. These updates are part of our ongoing commitment to providing a seamless and efficient user experience.

Improvements and Bug Fixes

Fix for Duplicated Reportable Fields in Custom Reports

Some users experienced an issue where reportable fields in custom reports were duplicated under specific conditions, causing confusion and blocking System Innovators from using custom reports effectively. This bug has been resolved, and reportable fields now appear only once in the report headers, regardless of the date range or whether the report is newly created or an existing report being edited. This fix ensures consistent and clear report headers, streamlining the creation and editing of custom reports.

Recurring Transaction Setup Error for RapidConnect Merchants

RapidConnect merchants in the PayConex certification environment encountered errors when setting up recurring transactions from existing transactions. The error message "INVALID TRANSACTION..." was displayed, preventing the transaction setup. The PayConex portal now correctly sets up recurring transactions for RapidConnect merchants without displaying error messages, supporting their go-live process and improving overall integration.

Correction of Incorrect Invoice_Number on Reissue Transactions for Elavon

A bug was identified where the Invoice_Number field on reissue transactions for certain accounts was incorrectly populated. Instead of using the format "account_id-transaction_id," it was sometimes using "account_id-token_id." This issue has been fixed, and the Invoice_Number now consistently follows the correct format. This correction ensures accuracy in transaction records and reports, enhancing reliability and trust in the system for affected accounts.

Handling Accertify Declined Transactions During Connectivity Issues

When there were connectivity issues with Accertify, transactions were being declined unnecessarily. This issue has been addressed to improve error handling and prevent false declines. Transactions will now handle timeouts and connectivity issues more gracefully, ensuring that connectivity issues do not unnecessarily disrupt transaction processing.

We appreciate your feedback and continued support. If you encounter any issues, please reach out to our customer service team at [email protected].