Fix Readme
Abstract
Fix list for Financial Transaction Manager for Digital Payments for Multiplatforms 3.2.11.
Content
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
- To avoid a loss of functionality when you migrate from one release to another, check the Compatibility Matrix for the release being migrated to. The Compatibility Matrix is located in the release information for Financial Transaction Manager for Digital Payments 3.2.11 Multiplatforms.
| Back to contents | 3.2.11.2 (Fix pack 2) release |
| Fix number | Type | Component | Description |
| TS015785260 | APAR | Zelle | FTM does not handle return scenario when recipient's account is NSF. |
| TS019026533 | APAR | Zelle | Incoming payments that are held by Fraud should not be allowed to be Released. |
| TS018955958 | APAR | Address NPE's while running expired payment task. | |
| TS017486451 | APAR | Services Framework | Concurrency locking in Services Framework not working properly with multiple JVMs. |
| TS017966195 | APAR | Transaction Server | Pre-Allocation Task Failure due to Daylight Savings Time |
| TS018790939 TS018780680 | APAR | Risk Monitor API | Credit limit deducted from single day after being rejected from 30-day global limit. |
| TS018783388 | APAR | TCH RTP | Return pacs.008 Missing Originating FI and Originating Fi ID's field values |
| TS019103704 | APAR | Zelle | FTM is unable to handle cancel_by_sender for AWOP payments. |
| TS018159708 | APAR | "Database Accessor Exception; Accessor - Database Accessor Exception" OR "Database failure while processing notification. TIMEOUT" errors being seen in DB Linux server. |
| Back to contents | 3.2.11.1 interim fix 9 |
| Fix number | Type | Component | Description |
| 23632 | Defect | Risk | When deleting a Risk Monitor, added check for Risk Velocity payment info to determine whether monitor should be soft deleted or not. |
| 23626 | Defect | Database - Other | Remove extra comma from comment on the CXC Token table for fraud column. |
| Back to contents | 3.2.11.1 interim fix 8 |
| Fix number | Type | Component | Description |
| DT442940 | APAR | Real Time Payments Tasks | Added null checks on payment object and stats in debug logging and task messaging. |
| DT442943 | APAR | Real Time Payments Console | Cancel_per_sender messages are now supported for incoming payments that are held by Fraud. |
| DT442945 | APAR | Real Time Payments Console | When an incoming payment is held for Fraud, and the receiving token becomes inactive, the payment will now be failed. |
| DT439525 | APAR | Gateway Other | Set the Originating FI and Originating FI Id on a TCH pacs.008 return. |
| DT442947 | APAR | Gateway Other, Presentment Engine, Transaction Server | Corrected Distribution Perf issues and Gateway crashes caused by previous ifix6 defect 15935 |
| 19816 | Defect | Gateway Engine, Transaction Server Console, Real Time Payments Console, Settlement Engine, Presentment Engine | Close accessor to prevent resource leaks. |
| 19886 | Defect | Real Time Payments Console | Add null check on payment status during cancel payment. |
| 19462 | Defect | Partner Console | Backport Defect 152522 to add missing getter for retrieving the list of return reason codes. |
| Back to contents | 3.2.11.1 interim fix 7 |
| Fix number | Type | Component | Description |
| DT435483 | APAR | Core | During the creation of CXCPayment Requests, if the responder token was a Zelletag with a length of 10, a '1' was incorrectly being appended to the front of the tag. A check was corrected during the validation process to no longer append the '1' to Zelletag tokens. |
| 16184 | Defect | Real Time Payments | Validate the new Row Limit parameter of the CXCExpirePaymentTask even when it is the only configured parameter of the task. |
| DT435484 | APAR | Transaction Server | Addressed an issue with the query that populates the Related Transaction tab for non payment transactions and pacs.008's |
| 15861 | Defect | Gateway | Support for Debit Network Transaction Detail (DNTD) v3 Record Specification which provide Participants with additional detail about Supported Debit Card Payments. Added support for 8 new v3 fields which can be verified in inbound transmission hierarchy (Transaction details under Debit Card Information tab). |
| 15030 | Defect | Risk Console | Validate Payment ID before creating Risk Monitor Definition. |
| 15029 | Defect | Risk Console | Validate Payment ID before creating Risk Monitor Definition. |
| 16328 | Defect | Risk Console | Close resources to prevent DB2 statement leaks. |
| DT435488 | APAR | Risk Engine | Now uses the current monitor date when undoing non-business day monitor types |
| Back to contents | 3.2.11.1 interim fix 6 |
| Fix number | Type | Component | Description |
| DT418823 | APAR | txs_console, txs_other Transaction Server - Other | Problem: Initiate Credit Transfer payments are not being linking to corresponding Request for Payment transactions on the Inbound Transactions Related Transactions tab. Solution: Fixed query to properly link Request for Payment transactions to the associated Initiate Credit Transfer payments on the Related Transactions tab. |
| DT394591 | APAR | Real Time Payments | Problem: Incoming standard payments that fail do not trigger the correct notification alert. Solution: Incoming standard payments now trigger the correct notification type during the payment cancellation process. |
| 14524 | Defect | Transaction Server - Console | Fixed issue with query that was incorrectly populating the Related Transactions tab for Non Payment transactions. |
| 14188 | Defect | Real Time Payments | Problem: Current version of EWS wsdl does not support necessary messages for Zelle Risk Insights for Received Payments. Solution: Updated the EWS wsdl file to version 4.8. |
| 14190 | Defect | Real Time Payments | Problem: Requested functionality by customer to comply with EWS mandates. Solution:FTM has been updated to use the OnNewPaymentStatusNotification4.8. And, when RIZ scores are provided by EWS, FTM will pull those values from the notification and provide them to the customer's Fraud User Exit for proper evaluations. |
| 14615 | Defect | Real Time Payments | A new error code was added to for a Transfer Funds error while processing an incoming Zelle Dispute. The new code is ZEL0014. This error code was added to give the customer an option to differentiate between a return and a dispute for the purpose of configuring automatic returns. Out of the box, this error code does will not create automatic returns. That can be added, if desired, using the Digital Payments User Interface. Specifically, by finding the ZEL0014 error code on the Error Codes screen and adding an Associated Reason Code. The code will need to be added manually using the following sql insert statement. INSERT INTO ERROR_CODES (ERROR_CODE, CATEGORY, REJECT, OVERRIDE, NOTIFICATION_INCL, DESCRIPTION) VALUES ('ZEL0014', 15, 1, 'N', 'N', 'Payment Failed During Funds Transfer Of Dispute'); |
| 15414 | Defect | Real Time Payments | When attempting to resync a payment either via the UI or when using the Resync Task, a null pointer is possible if the reason code value is null. Resolution: Add a null check for the reason code during the resync process. |
| 14651 | Defect | Core - Console Real Time Payments | Problem: When using the Liberty Web Service available profiles API call, FTM is always validating the participant which is not necessary. Solution: When using the Liberty Web Service Api calls: availableProfiles or getEWSTokenStatus. A participant will go through validation when provided to the API. If the value, FTM_PASSTHROUGH, is provided. Validation will be skipped and processing will continue as expected. |
| 14186 | Defect | Real Time Payments | Problem: Incoming payments held for possible fraud, when released or canceled, are not processing correctly Resolution: Incoming payments that are released or canceled will continue processing successfully. |
| DT393746 | APAR | Distribution Engine | Problem: In distribution engine cancel payment process, when a payment is canceled and it is the only payment mapped to an outbound batch, the currency on the related Outbound Presentment Group is incorrectly calculated such that it ends up being null. The currency calculation in this case must check for this case and produce the correct result Solution: A fix was made to an edge case when cancelling a payment. For this case, if the transaction being canceled is the only payment on the outbound batch, it would result in the outbound file currency being set to null. |
| 14657 | Defect | Gateway Engine | Refactor Gateway Engine return item post processing to issue a query to determine if there is actually returns to be processed. |
| 15935 | Defect | Presentment Engine | Problem: Database deadlock occurs when one thread is cancelling a payment at the same time another thread is setting the outbound ready flag on the same associated presentment record. Resolution: When performing updates to an Transmission/Batch/Segment, the currency is now updated at the same time as the control total values are updated for the hierarchy. This eliminates the database deadlock which was occurring in the update code path. |
| 14654 | Defect | Real Time Payments | Problem: If a Zelle-tag token is restricted (and subsequently marked inactive) via the FTM UI, it can no longer be assigned as a recipient. This is different from both mobile and email tokens, which can be added as recipients, even if they are inactive. Resolution: Zelle-tag tokens that are inactive, can now be added as recipients. |
| 14655 | Defect | Real Time Payments | Problem: A couple of error messages returned from actions related to restricted tokens are not tailored to the situation, and causing confusion for the customer: • Registering an existing token that is restricted returns an error saying it's inactive, and suggests reactivating it via the update api, which is not possible • Attempting to activate a restricted token fails without mentioning the token's restricted status Resolution: Updated the error messages to eliminate any confusion for the customer. |
| 15934 | Defect | Services Engine | Problem: Zelle Settled payment statuses L and O are not recognized as final states during Expire payments query. Task runs slow when there are many bdays of payments or payment requests to look thru and move or expire. Resolution: Add Settled Status L and O as a final states for lookup during expiration task query. Also, added the ability to run the expire payments task on a particular Bday Id as well as a configuration parameter to limit the number of payment requests searched for a single run of the task. |
| 14186 | Defect | Real Time Payment | Problem: Incoming payments held for possible fraud, when released or canceled, are not processing correctly Resolution: Incoming payments that are released or canceled will continue processing successfully. |
| 16229 | Defect | Transaction Server | Problem: Zelle Payment requests should not go to distribution. Resolution: Update the ITS scheduler to remove possibility of Payment Requests being sent to distribution. |
| 14648 | Defect | Real Time Payment, Zelle Console | Problem With the addition of Zelle tag tokens, more token information is needed by the customer's User Exits. Resolution FTM added the participantZelleToken and recipientZelleToken objects as part of the CXCPayment object for customer use in their custom User Exits. |
| DT397257 | APAR | Real Time Payment | Problem: Some failure reasons and descriptions are not getting set during payment failures. Resolution: FTM is now correctly setting failure reason codes and descriptions when payment failures occur during EWS call to validate the Recipient. |
| DT393653 | APAR | Real Time Payment | Problem: Zelletag were not yet supported on origination for our owned tokens. Resolution: There was a condition preventing execution of expected code. This check has been removed, and the CXCMultitoken API works with Zelletag tokens now. |
| DT387284 | APAR | Transaction Server Console, Core | Problem: When the Force Filter option is enabled for the Inbound Transactions screen, it is still rendering the Inbound Transactions screen without requiring an additional filter to be added. The root cause is due to the Transmission Received past 5 minutes filter having been added to the default filter of the screen, but the backing code was not modified to add this column to the minimum required columns for the Force Filter along with the Business Date. Resolution: Force Filter option for transactions now checks for both BDay AND Received default filters. |
| 14344 | Defect | Services Engine | Problem: Two instances of a non-concurrent task executing at the same time, potentially resulting in duplicate work. When two separate users started the same non-current task or if the task was started by another Services Framework instance, this issue could arise. Resolution: Services Framework is now looking for any record associated with the task classname running on any JVM/Server, including its own. The user who starts the task instance is no longer a factor in whether another instance can be executed. |
| DT395672 | Defect | Real Time Payment, Real Time Payment Console, Digital Payments Shared | Problem: Customer reported issues with FTM created QR codes at other Financial Institutions Resolution: When creating a QR code, only the first name or business name is needed. FTM no longer includes the last name. |
| Back to contents | 3.2.11.1 interim fix 5 |
| Fix number | Type | Component | Description |
| DT378828 | Defect | Real Time Payments Transaction Server - Other | Problem: Internal returns that fail due to a funds transfer issue are incorrectly going to Distribution. Solution: The Zelle_Complete state is now set after returns are successfully processed. Because of this change, you must also change the Transaction Server scheduler to replace one stanza and add two stanzas. The following existing stanza needs to be replaced: <EVENT> <NAME>Distribution - Batch</NAME> <TYPE>PresentmentStateChange</TYPE> <TYPE>PresentmentColumnChange</TYPE> <TYPE>PresentmentGroupColumnChange</TYPE> <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentReadyEventHandler</EXEC> <PARAMETER name="workType">Present</PARAMETER> <PARAMETER name="msgType">presStatesReached</PARAMETER> <!-- presStates1 for ACH and CPS --> <PARAMETER name="presStates1">LOADED,AUTH_CHECKED</PARAMETER> <!-- presStates2 for Check --> <PARAMETER name="presStates2">BALANCED</PARAMETER> <PARAMETER name="outboundReady">!2</PARAMETER> <PARAMETER name="group.condition">ACCEPTED</PARAMETER> <PARAMETER name="inbound.condition">ACCEPTED</PARAMETER> <PARAMETER name="condition">ACCEPTED</PARAMETER> <PARAMETER name="pending">N</PARAMETER> <PARAMETER name="group.pending">N</PARAMETER> <PARAMETER name="presLevel">PROC</PARAMETER> <PARAMETER name="paymentStandard">Check,NACHA,INTERNAL,CPA 005,EDI X12,Fedwire,ISO 20022,Posting File,SWIFT</PARAMETER> <!-- Purposefully not including Zelle --> <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF> <PARAMETERREF>sendToDistribution</PARAMETERREF> </EVENT> The following stanza replaces the existing stanza: <EVENT> <NAME>Distribution - Batch</NAME> <TYPE>PresentmentStateChange</TYPE> <TYPE>PresentmentColumnChange</TYPE> <TYPE>PresentmentGroupColumnChange</TYPE> <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentReadyEventHandler</EXEC> <PARAMETER name="workType">Present</PARAMETER> <PARAMETER name="msgType">presStatesReached</PARAMETER> <!-- presStates1 for ACH and CPS --> <PARAMETER name="presStates1">LOADED,AUTH_CHECKED</PARAMETER> <!-- presStates2 for Check --> <PARAMETER name="presStates2">BALANCED</PARAMETER> <PARAMETER name="outboundReady">!2</PARAMETER> <PARAMETER name="group.condition">ACCEPTED</PARAMETER> <PARAMETER name="inbound.condition">ACCEPTED</PARAMETER> <PARAMETER name="condition">ACCEPTED</PARAMETER> <PARAMETER name="pending">N</PARAMETER> <PARAMETER name="group.pending">N</PARAMETER> <PARAMETER name="presLevel">PROC</PARAMETER> <PARAMETER name="paymentStandard">Check,NACHA,CPA 005,EDI X12,Fedwire,ISO 20022,Posting File,SWIFT</PARAMETER> <!-- Purposefully not including Zelle or INTERNAL --> <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF> <PARAMETERREF>sendToDistribution</PARAMETERREF> </EVENT> The following two stanzas need to be added: <EVENT> <NAME>Distribution - Batch (Internal Zelle Settlement)</NAME> <TYPE>PresentmentStateChange</TYPE> <TYPE>PresentmentColumnChange</TYPE> <TYPE>PresentmentGroupColumnChange</TYPE> <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentReadyEventHandler</EXEC> <PARAMETER name="workType">Present</PARAMETER> <PARAMETER name="msgType">presStatesReached</PARAMETER> <!-- presStates1 for ACH and CPS --> <PARAMETER name="presStates1">LOADED,AUTH_CHECKED, ZELLE_COMPLETE</PARAMETER> <!-- presStates2 for Check --> <PARAMETER name="presStates2">BALANCED</PARAMETER> <PARAMETER name="outboundReady">!2</PARAMETER> <PARAMETER name="group.condition">ACCEPTED</PARAMETER> <PARAMETER name="inbound.condition">ACCEPTED</PARAMETER> <PARAMETER name="condition">ACCEPTED</PARAMETER> <PARAMETER name="pending">N</PARAMETER> <PARAMETER name="group.pending">N</PARAMETER> <PARAMETER name="presLevel">PROC</PARAMETER> <PARAMETER name="productCode">ZELS</PARAMETER> <PARAMETER name="paymentStandard">INTERNAL</PARAMETER> <!-- Purposefully not including Zelle --> <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF> <PARAMETERREF>sendToDistribution</PARAMETERREF> </EVENT> <EVENT> <NAME>Distribution - Batch (Internal NOT Zelle Settlement)</NAME> <TYPE>PresentmentStateChange</TYPE> <TYPE>PresentmentColumnChange</TYPE> <TYPE>PresentmentGroupColumnChange</TYPE> <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentReadyEventHandler</EXEC> <PARAMETER name="workType">Present</PARAMETER> <PARAMETER name="msgType">presStatesReached</PARAMETER> <!-- presStates1 for ACH and CPS --> <PARAMETER name="presStates1">LOADED,AUTH_CHECKED</PARAMETER> <!-- presStates2 for Check --> <PARAMETER name="presStates2">BALANCED</PARAMETER> <PARAMETER name="outboundReady">!2</PARAMETER> <PARAMETER name="group.condition">ACCEPTED</PARAMETER> <PARAMETER name="inbound.condition">ACCEPTED</PARAMETER> <PARAMETER name="condition">ACCEPTED</PARAMETER> <PARAMETER name="pending">N</PARAMETER> <PARAMETER name="group.pending">N</PARAMETER> <PARAMETER name="presLevel">PROC</PARAMETER> <PARAMETER name="productCode">!ZELS</PARAMETER> <PARAMETER name="paymentStandard">INTERNAL</PARAMETER> <!-- Purposefully not including Zelle --> <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF> <PARAMETERREF>sendToDistribution</PARAMETERREF> </EVENT> |
| DT381642 | Defect | Real Time Payments | Problem: Incoming standard payments that fail do not trigger the correct notification alert. Solution: Incoming standard payments now trigger the correct notification type during the payment cancellation process. |
| DT382355 | Defect | Real Time Payments Transaction Server - Console | Zelle processing no longer adds extra trackable records to the table in the database. |
| DT385988 | Defect | Real Time Payments | Problem: The CXC Payment object does not have a value for the recipient business name during processing. Solution: The recipient business name is now properly set during payment processing. |
| DT386031 | Defect | Problem: QR codes are not scanning properly all the time. Solution: A QR code might potentially contain white space. Removed the white space before the QR code is processed. | |
| DT386420 | Defect | Problem: A warning pop-up window should appear when a customer attempts to return a payment that is outside the configured window. Solution: Fixed the validation to check against the correct date so that a warning pop-up window appears when a payment window is configured. | |
| DT387192 | Defect | Real Time Payments | Fixed a problem where a Zelle tag that was assigned to a participant as a recipient was not removed from the recipient list for the participant when its Zelle tag token was deleted. |
| DT387568 | Defect | Core - Console Real Time Payments | Problem: Unenrolling and reenrolling Zelle participants can cause some inactive participant-level Risk monitors to reactivate. Solution: Participant-level Risk monitors are no longer affected when Zelle participants are enrolled or unenrolled. |
| 122128 | Defect | Transaction Server - Other | RTP transactions in the RTP payment table are now being purged as part of the Transaction Server purge processing. |
| 151612 | Defect | Real Time Payments | Problem: The WebSphere Liberty GET EWS_STATUS API does not include a field for the contact method in the request to EWS. Solution: Added the contact_method optional field to the WebSphere Liberty GET EWS_STATUS API. |
| 152100 | Defect | Real Time Payments | Problem: FTM is not setting the status when it creates a changePaymentStatus request for Accept Without Posting (AWP) payments. Solution: FTM now properly sets the Accept Without Posting (AWP) status when it creates the changePaymentStatus request to EWS. |
| 152154 | Defect | Transaction Server - Other | Addressed a database performance issue by setting the date during business day preallocation to a date in the distant past. The date is now set to the beginning of the epoch: (1970-01-01-00.00.00.000000). |
| Back to contents | 3.2.11.1 interim fix 4 |
| Fix number | Type | Component | Description |
| DT260214 | APAR | Real Time Payments | Remove isIsZelletagAvailable check when creating a recipient. |
| DT261569 | Defect | Real Time Payments | Returns are incorrectly failing with IMA0029 error code. |
| DT269446 | Defect | Real Time Payments | Non ZELLE QR Code Error Message. |
| DT269908 | Defect | Real Time Payments | Payment getting failed during validate recipient is not triggering notification. |
| 150867 | Defect | Real Time Payments | Problem: EODProcessor makes calls to archive server(s) when it shouldn't. Solution: Offending functions removed. |
| 151032 | Defect | Real Time Payments | Problem: EWS now allows multiple Zelle tags to be associated with a Participant account. Solution: Removed previous fix that would only allow one Zelle tag token to be associated with a Participant account. |
| 151075 | Defect | Real Time Payments | Problem: FTM does not mark the funds transfer flag if a return result from the Funds Transfer user exit is "Failure to transfer funds for... (Unknown Reason)". In this situation, the funds could have actually been transferred without FTM being made aware. Solution: A new Severe Alert will be shown if the payment is failed during Funds Transfer for an unknown reason. The new alert is: "ZELFT100S". With a description of: "Transfer of funds failed for an unknown reason. System unsure if funds were transfered or not. Manual intervention may be required." |
| Back to contents | 3.2.11.1 interim fix 3 |
| Fix number | Type | Component | Description |
| DT257303 | Defect | Real Time Payments | Active Zelle Tag Token is not accepted as a recipient. |
| DT257833 | Defect | Core - Console | FTM Individual Risk Limit updated in previous version when edited |
| DT257933 | Defect | Gateway - Other | Unable to pass validation for Nacha File Ingestion |
| DT258072 | Defect | Transaction Server - Console Web Services | ICT-v2 WS API is not setting TECH_PRIORITY at batch level. |
| DT258078 | Defect | Core - Console | TCH 3.0: New field miss match in pain001ToISF mapper |
| DT258454 | Defect | Framework Console | Login User Exit integration setup |
| DT258900 | Defect | Distribution Engine | Outbound transmission file cannot be built due to Null Pointer Exception |
| Back to contents | 3.2.11.1 interim fix 2 |
| Fix number | Type | Component | Description |
| DT238780 | Defect | Distribution Engine | ZELLE ACH file has an Incorrect Trailer Record |
| DT245005 | Defect | Core - Console Transaction Server - Console | TCH admi.004 (960) system notification messages are not processed properly. |
| DT245938 | Defect | Real Time Payments | Trying to stop potential incorrect status during resync and loss of EWS network connection |
| DT246916 | Defect | Transaction Server - Console Web Services | Add check for IP configuration for IP_OBJ_STATUS_TIMEOUT if distribution timeout is null |
| DT248008 | Defect | Real Time Payments | Wrong Org ID used in GetPaymentRequest 4.3 |
| DT248085 | Defect | Real Time Payments | Active Zelle Tag Token is not accepted as a recipient |
| DT248088 | Defect | Core | Need to add inbound product as a Monitor type when creating a new Global Limit using the Limit Span of Velocity |
| DT255371 | Defect | Real Time Payments | Wrong Org Id in Get Payment Request Details Request 4.2 |
| DT256709 | Defect | Real Time Payments | AIT - ibmValClDestinationRT is assigned incorrectly |
| DT256715 | Defect | Core | Error while editing the Credit Limit for Individual Single / Multi Day limit. |
| DT256723 | Defect | Distribution Engine | Distribution Engine: file built during payment cancel has incorrect control total |
| DT256726 | Defect | Risk | Risk monitors are always being applied to business days even if configured to calendar days |
| Back to contents | 3.2.11.1 interim fix 1 |
| Fix number | Type | Component | Description |
| DT180541 | Defect | Real Time Payments | Liberty Initiate Credit Transfer can not be run in asynchronous mode when using ref_transaction_id. |
| DT198711 | Defect | Real Time Payments | Actor Organization Id is incorrect on the details from a result on the Transfer Token screen. |
| DT198790 | Defect | Real Time Payments | DB2 Table Alter partition was executing with incorrect date range |
| DT208791 | Defect | Real Time Payments | Financial Transaction Manager is updating the Fraud column incorrectly when multiple messages are being sent from Fraud for the same payment. |
| DT208938 | Defect | Real Time Payments | Recipient Names are not being trimmed when they enter the database. |
| DT211291 | Defect | Real Time Payments | Financial Transaction Manager is not able to handle Return scenario when recipient account is NSF. |
| DT213971 | Defect | Real Time Payments | Add recipient call flow needs to change depending on the status of token. |
| DT224886 | Defect | Real Time Payments | Able to link multiple Zelle tags to the same DDA. |
| DT223035 | Defect | Real Time Payments | Financial Transaction Manager incoming Payments don't go through fraud check before transferring funds. |
| DT237071 | Defect | Real Time Payments | Initiate credit transfers are incorrectly mapping to outbound request for payments. |
| DT237074 | Defect | Real Time Payments | ZelleTag token is not being deleted via User Interface. |
| DT237075 | Defect | Real Time Payments | Zelle - Configuration issue : Cannot activate Business Rules release. |
| 143718 | Defect | Real Time Payments | Problem: Outgoing Request for Payment status does not get update to 'expired' after expiry date has passed. Solution: Request for Payments will now use the correct timezone time format to expire at the correct time. |
| 146404 | Defect | Real Time Payments | Problem: Having Settled status be assigned to Standard Payments once settlement is received from the other Financial institution. Solution: Code change to use Settled payment status. |
| Back to contents | 3.2.11.1 (Fix pack 1) release |
| Fix number | Type | Component | Description |
| 143445 | Defect | Business Rules | Problem: Issue when CPA transactions are processed such that a lookup in Business Rules intermittently fails to return the correct row. Solution: Fixed an intermittent problem when table lookups are done in the XmlMappingTask and ModulusCheckTask (CPA workflow). Problems occurred while a high number of concurrent Business Rules threads were used. The problem caused payments to fail processing because data fields were not set. |
| 144050 | Defect | Web Services | Problem. The latest TCH 3.0 spec from Jan 2023 enables RFRF (request for return of funds) to use UPAY reason code. Solution. Added reason code UPAY for RFRF (request for return of funds) when it is used from Control Center user interface. |
| 144899 | Defect | Business Rules | Problem: During an activation, tactical or otherwise, Business Rules is stopping all new connections. Solution: Fixed an issue where a Business Rules activation was taking long time and new connections from the Gateway were not allowed while the Business Rules Servers were processing the activation request. |
| 144092 | Defect | Web Services | Problem. The latest TCH 3.0 spec from Jan 2023 enables RFRF (request for return of funds) to use UPAY reason code. Solution. Added reason code UPAY for reqretfunds_v2 Liberty API for RFRF (request for return of funds). |
| 144282 | Defect | Control Center UI | Problem: Incorrect description of recall reason codes in Control Center for the RFRF (request for return of funds) reason codes. Solution: 1. Change "Initiate Recall" to "Request Recall" in descriptions for all the RFRF codesx 2. The UPAY reason codes has the description "UPAY – Request Recall – RFP Warranty Breach Claim" |
| 142938 | Defect | Risk | Problem: Risk velocity monitors are not correctly storing information in the Risk lifetime totals tables. This problem affects Risk Velocity Limit change conditions if they are configured to use either of the following change conditions: Aggregate amount of successful transactions OR Number of successful transactions. Solution: Fixed the storing of information in the applicable tables. |
| 144190 | Defect | Control Center UI | Problem: Service request count is inconsistent on the processing batches and ICLs page and on the service manager page Solution: Updated the hyperlink on the Inbound/Processing and CPCS Entries pages for the Service Requests column to pull back all services that are associated with that particular batch or entry. |
| 143513 | Defect | Zelle | Problem: The initial company ID for originated Zelle payments was being set to the bank code of the participant. Solution: This value needs to reflect the Zelle standard/realtime company ID properties. Depending on timing, this problem caused some payments to be incorrectly mapped into outbound batches based on the company ID. |
| 144188 | Defect | Business Rules | Problem: Business Rules performance improvement needed Solution: Performance issue fixed when Business Rules is processing work through the XmlMappingTask that uses XPath notations to process fields in XML. The following string must be specified in the VMArgs when the Business Rules Server is started - -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault |
| 143052 | Defect | Zelle | Problem: Creating a token that has an organization ID that is different than the ID of the participant was inadvertently allowed. Resolution: A new error was added to prevent this case. |
| 144600 | Defect | Zelle | Problem: The Sample Business Rules configuration had a gap for received payments, DB table RULES.DEPOSIT_PRODUCT_LOOKUP_TC_FTM. That table has two rows for ZELLE_Recv payments (for U2B and U2C transaction categories). That was correct initially because EWS never included information about the sender. However, FTM implemented "Zelle: MANDATE SenderType support for 4.0 APIs (106420)", which started to use the sender information. Now that lookup could be "B2B" or "C2B" (or "C2C"). For the B2B/C2B scenarios, FTM should be assigning the ZSBR (not ZELR) product code. Solution: DSU spreadsheet SampleBusinessRulesAchConfiguration.xls was updated. The following rows were added to the "FTM Product Lookup TC" sheet: MSG_TYPE_NAME_IN TXN_CATEGORY PRODUCT_CODE ZELLE_Recv C2C ZELR ZELLE_Recv C2B ZSBR ZELLE_Recv B2B ZSBR |
| 143840 | Defect | Zelle | Problem: Error code 122400 refers to the previous name of the Zelle service (CXC - clearXchange). Now Zelle is part of EWS (Early Warning Services). Solution: Renamed error code 122400 from "Default CXC Organization not set" to "Supported EWS Organization IDs not set". |
| Back to contents | 3.2.11.0 interim fix 2 |
| Fix number | Type | Component | Description |
| 147669 | Defect | Business Rules - Other | Problem: Potential race condition exists when unlocking Business Rules workflow. Solution: Reordered the unlocking of Business Rules managers to prevent potential race condition. |
| 152011 | Defect | Gateway Engine Distribution Engine Transaction Server - Console | Problem: TS015439187 - Batch wire - Failed Batches while revalidating transmission. Solution: Use Short instead of int for SMALLINT database values. Additional commits added around batch revalidation. |
| 151684 | Defect | Gateway - Other | Problem: Backport defect 142918 to v3.2.11.0 ifix - The inbound currency code Gateway file stat property was inserted twice during ACH fragmentation, which caused the inbound physical transmission page to be inaccessible. Solution: Synchronize updates when doing file fragmentation to prevent duplicate Gateway property records. |
| Back to contents | 3.2.11.0 interim fix 1 |
| Fix number | Type | Component | Description |
| 143350 | Defect | Gateway | Problem: The izxfix.jar was not empty in the 3.2.11.0 GA build. Solution: The izxfix.jar was reset to empty to facilitate IBM Support. |
| Back to contents | 3.2.11.0 release |
| Fix number | Type | Component | Description |
| 134376 | Defect | Real Time Payments | Problem: TCH RTP credit transfers are not rejected when the destination Creditor FI is offline, disconnected, or suspended. Solution: Fixed an issue with the TCH workflow in the Samples DSU for Business Rules (SampleBusinessRulesBaseConfiguration.xls). |
| 136828 | Defect | Real Time Payments | Problem: After an ONUS Initiate Credit Transfer API is made, the Request for Return of Funds API shows status 'Wait for Resolution of Investigation'. Solution: This problem was fixed in Samples DSU (SampleAchConfiguration.xlsx). The INTERNAL_TCH message type for the transmission definition was added. |
| 140491 | Defect | Real Time Payments | Problem: Saturdays and Sundays were incorrectly configured as working days in the FTM Product configuration (DSU spreadsheet). Solution: The configuration was updated to ensure that Saturdays and Sundays are marked as nonworking days for HVP payment schemes TARGET2, EURO1, and CBPR+. |
| 140507 | Defect | Database | Problem: Database deadlock prevented the transaction delete operation from completing. Solution: Added database commits to prevent the deadlock scenario from occurring. |
| 140804 | Defect | Real Time Payments | Problem: Data on the Parties tab in the Control Center user interface is missing or inaccurate. Solution: Changes on the Parties tab were made to accurately reflect where transactions originated from and to whom they are destined. Certain transactional messages do not always contain all the data necessary for the Parties tab and the enrichment process must pull in data from related messages. There are fixes regarding the data, which is pulled from related messages, to accurately reflect the transaction data. |
| 142548 | Defect | Scheduler | The default scheduler XML is configured for a complete Risk functionality for incoming and outgoing payments. A complete Risk configuration might not be needed based on requirements. To help processing perform better, a reduced Risk configuration might need to be considered. |
| 142880 | Defect | Scheduler | Problem: Potential missing Settlement Posting files after a Db2 or IBM MQ outage. Solution: SELECT PRESENTMENT_ID FROM PRESENTMENT WHERE STATUS='Complete' AND SETTLEMENT_PRIME IS NULL AND PRES_LEVEL='P' WITH UR Then, go to the Service Manager user interface and filter on UOW of Presentment, specifying each presentment_id returned from this query. Find the task with the work type of "Settlement" and restart it. This process results in the state being set and the SettlementPosting file being generated and processed. |
| 143042 | Defect | Real Time Payments | Problem: The reqretfunds_v2 API is documented as having the input field 'additional_information'. This field is ignored during processing. Solution: All the APIs including reqretfunds_v2 use 'additional_info' and not 'additional_information'. This problem is a documentation defect that will be fixed in next release. |
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9JGN","label":"IBM Financial Transaction Manager for Digital Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.2.11"}]
Was this topic helpful?
Document Information
Modified date:
29 October 2025
UID
ibm16839189