1/29/2026 Release
Key Updates: GIACT risk verification for Payrix ACH transactions now provides detailed decision data in error webhooks. Plus: improved transaction debugging with Payrix processor IDs on failed transactions, enhanced data management with 1-year transaction archival, and cleaner dashboard UI with alphabetized filters, updated sidebar icons, and various UX improvements.
Jump to: New Features | Improvements | Important Changes
New Features
GIACT Risk Verification for Payrix ACH
When Payrix ACH verify transactions fail GIACT risk verification, detailed decision results are now fetched and included in your webhooks, giving you clearer insight into why a verification failed.
- Enriched Error Data - GIACT decision results (BLOCK/PASS/SKIP) are automatically fetched and included in transaction error data
- Webhook Flow - Receive a
transaction.pendingwebhook initially, followed by atransaction.erroredwebhook with the complete GIACT verification results - Platform Configuration - Enable by setting
giactEnabled: trueon your Payrix processor configuration
Improvements
Failed Transaction Debugging (Payrix)
The processorTransactionId is now persisted and returned for failed Payrix transactions, enabling better debugging and support workflows.
- Error Response Enhancement - Failed transactions now include the Payrix transaction ID in
authorization.processorTransactionId - Database Persistence - Transaction IDs are stored for correlation with Payrix records
- Support Improvement - Easier reconciliation and debugging for failed payment scenarios
Dashboard UX Improvements
- Alphabetized Connections Filter - The Connections dropdown in the Transaction Log is now sorted A-Z for easier navigation
- Sidebar Toggle Icons - Distinct menu-fold and menu-unfold icons provide clear visual feedback for sidebar state
- Webhooks Table Cleanup - Removed unnecessary pagination from the Webhooks configuration page
- Merchant Details Fix - Fixed pagination bar alignment on the Updates/Activity Log tab
- AI Tooltip Update - Boarding form tooltip now reads: "Pre-filled using publicly available data gathered by AI. Please verify and update if needed."
Important Changes
The following changes may affect existing integrations:
Transaction Date Archival
Transactions older than 1 year are now archived and not available for querying. This affects both the API and Dashboard.
- API Validation - The List Transactions endpoint now rejects
startDatevalues more than 1 year in the past with a 400 Bad Request error - Dashboard Validation - Date pickers disable dates older than 1 year with tooltips explaining the restriction
- URL Parameter Handling - Bookmarked URLs with old dates are automatically adjusted with a notification
ACH Drawdown Restriction
ACH transactions now reject Drawdown transaction type with a clear error message.
- Validation - Submitting ACH with transaction type DRAWDOWN returns: "Drawdown is not supported for ACH transactions. Drawdown is only applicable for lending payment methods."
- Error Code - Returns
processorCode: 'ACH_UNSUPPORTED_TRANSACTION_TYPE'
