Fix Readme
Abstract
This document contains fix list information for Financial Transaction Manager for Interac e-Transfers for Red Hat OpenShift 4.0.3.
Content
Fix List for Financial Transaction Manager for Interac e-Transfers for Red Hat OpenShift 4.0.3.
The following table shows a list of available packages for FTM for Interac e-Transfers for Red Hat OpenShift 4.0.3.
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
| V.R.M.F fix list | Build date | Pre-requisite |
| 4.0.3.1 (Fixpack1) | 20220517-0634 | Supports both a full installation and an update from 4.0.3.0 interim fix 6 (iFix6) |
| 4.0.3.0 interim fix 6 (iFix6) | 20220106-1111 | Supports both a full installation and an update from 4.0.3.0 interim fix 3.1 (iFix3.1) |
| 4.0.3.0 interim fix 3.1 (iFix3.1) | 20211217-0642 | Supports both a full installation and an update from 4.0.3.0 interim fix 3 (iFix3) |
| 4.0.3.0 interim fix 3 (iFix3) | 20210716-2353 | Supports both a full installation and an update from 4.0.3.0 interim fix 2 (iFix2) |
| 4.0.3.0 interim fix 2 (iFix2) | 20210521-0721 | Supports both a full installation and an update from 4.0.3.0 interim fix 1 (iFix1) |
| 4.0.3.0 interim fix 1 (iFix1) | 20210427-2044 | Supports both a full installation and an update from 4.0.3.0 |
| 4.0.3.0 | 20210317-1901 | None |
Note: APAR links for security fixes aren’t active.
Refer to Financial Transaction Manager for Interac e-Transfers for Red Hat OpenShift 4.0.3 Release Information for more information about issues and changes.
| Back to top |
4.0.3.1 (Fixpack1)
|
| Number | Type | Description |
| 136340 | Defect | Description: After upgrading to OCP 4.8 the Digital Payment (DP) Operator kept shutting down and restarting
Solution: Updated the following DP Operator resources:
1. initialDelaySeconds: default: 120, increased to 150
2. timeoutSeconds: default: 10, increased to 15 |
| 133996 | Enhancement | Description: Add LDAPS support for the MQ Web console. |
| Back to top |
4.0.3 interim fix 6 (iFix6) release
|
| Fix number | Type | Description |
| 127308 | Enhancement | Description: The Interac Notification YAML is updated to a newer Interac specification. As a result, in the YAML (or Swagger UI) API for /notifications/push (Inbound Notifications), the "previous_fraud_type" and "current_fraud_type" Enum fields now include "BUS_EML_COMPR", "VNDR_EML_COMPR", "MALWARE", "APP_FRAUD", and "FRAUD_BUS". |
| 128460 | Enhancement | Description: The Interac Payments YAML is updated to a newer Interac specification. As a result, in the YAML (or Swagger UI) for /payment/origination/credit-transfer (Interac Outbound API), the "customer_authentication_method" Enum field now includes "TOKEN" and "MAKER_CHECKER". |
| 118436 | Enhancement |
Description: All Accounting Responses use the same SubType. All accounting requests now support a distinct accounting response type.
|
| 131129 | Defect | Description: Emoji included in SendMoney requests are being converted to an escape sequence causing transaction rejection |
| 130996 | Defect | Description: '\r' characters in a SendMoney request are being converted to '\n' in the outbound message to Interac |
| 127228 | Defect |
Problem: When creditor.name is missing in an Interac /payment/origination/credit-transfer request, a validation error occurs. The path mentioned in the validation error was incorrect.
Solution: The validation error path when missing creditor.name was corrected.
|
| 129024 | Defect |
Problem: When creditor_account.identification.other.scheme_name.proprietary is missing in an Interac /payment/origination/credit-transfer request, a validation error occurs. The path mentioned in the validation error was incorrect.
Solution: The validation error path when missing creditor_account.identification.other.scheme_name.proprietary was corrected.
|
| 129093 | Defect |
Problem: The Interac Notifications API does not use the Interac schema validation 5000 error.
Solution: The API was updated to use the 5000 error when there is a validation issue to better describe what was wrong with the request.
|
| 120369 | Defect |
Problem: The \r, \b, and \f control characters were not being processed correctly by Interac /payment/origination/credit-transfer API.
Solution: The Interac /payment/origination/credit-transfer API was updated to always reject requests that include \b or \f characters. \r characters are still allowed and are now handled correctly.
|
| 128996 | Defect |
Problem: The Header parameters in the "FTM for Interac Inbound Notifications" APIs did not have their length constraints listed in the YAML.
Solution: The YAML is updated to now include these. Due to an issue with the Swagger UI, the UI will not show the length constraints. You must go to the YAML directly to see them.
|
| 129665 | Defect |
Problem: The YAML fields for invoicer ID, Invoicee ID, Ultimate Debtor ID, Ultimate Creditor ID, Initiating Party, and Debtor ID have a limit of 20 characters but the Interac specification allows up to 35.
Solution: The YAML fields for invoicer ID, Invoicee ID, Ultimate Debtor ID, Ultimate Creditor ID have been updated to accept up to 35 characters. However, the characters for Ultimate Debtor ID, Ultimate Creditor ID, Initiating Party, and Debtor ID can be no more than 80 bytes in total (when encoded as UTF-8).
To support this, three Business Rules Data descriptors were updated. The changes are all in the "Data XML Descriptor" tab of SampleBusinessRulesBaseConfiguration.xls:
The ibmValDepositorId field in the AcknowledgmentEndpointsTable row had its length changed from 20 to 35.
The ibmValDepositorId field in the SttlSubCreateBalOriginatorTable row had its length changed from 20 to 35.
The ibmValDepositorId field in the SttlSubWhenRequestedTable row had its length changed from 20 to 35.
The field lengths of Ultimate Debtor Id, Ultimate Creditor ID, Invoicer ID, and Invoicee ID are increased from 20 to 35 characters. The Initiating Party ID and Debtor ID fields retain their field length of 20 characters.
API Updates: With this change, the YAML introduces new objects used by the Initiating Party ID and Debtor ID to restrict their field lengths to 20 characters. These objects are:
Existing objects for the other ID fields are updated to support the new 35 character limits
|
| 128759 | Defect |
Problem: Race condition for Error handling between Digital Payments and Immediate Payments when a timeout triggers failure at prechecks and so on.
Solution: Persist the error data earlier that removes the race condition. This ensures the API sees the error code when it reports the reject.
|
| 127229 | Defect |
Problem: Incorrect handling of Ultimate Creditor/Debtor in the Score / Send payment requests.
Solution: Modify the mapping function to map Ultimate Creditor/Debtor for these requests.
|
| 129844 | Defect |
Problem: Customer requesting 400 code be able to ignore previous indeterminate responses.
Solution: HTTP error codes can now be marked as absolute reject. This allows the reject code to overrule a previous indeterminate response. Broadly the codes can be defined as:
Codes categorized as Reject can cause a reject, but only if no previous Indeterminate response was received. However, codes categorized as Absolute Reject will cause the payment to be rejected.
|
| 127039 | Defect |
Problem: Outflow publication failure was incorrectly marking the events as published.
Solution: This is now corrected and the unit of work is rolled back and an Unexpected Error is recorded in the Event logs (visible in the OAC).
|
| 128097 | Defect |
Problem: Incorrect handling of soft timeouts when a timeout is ignored because of a later soft timeout.
Solution: The code was changed to remove the one that is being skipped so it is not considered again.
|
| 127042 | Defect |
Problem: Some payment notification events can fail to correlate if FTM did not receive the send payment response.
Solution: Payment notifications that fail to correlate on clearing system reference (network ID) will then attempt to correlate on the request identification that was provided in the call to Interac.
|
| 127156 | Defect |
Problem: Some network notifications are not properly processed if 2 duplicates arrive at the same time.
Solution: The standard Immediate Payments duplicate check pattern was applied. Also, minor enhancements were made to avoid rejecting all duplicate requests, which allows at least one to proceed correctly.
|
| 128201 | Defect |
Problem: Audit log sometimes shows "DP Request Passed"; logged 3 times.
Solution: Resolved issue in PreCheck result evaluation code that erroneously missed updating an ObjValue causing the evaluation code to run twice for the same event causing a double report of "DP Request Passed" logged. This resulted in 3 rather than 2 reports of that message. This was only happening if the Sanction check was skipped based on supplementary data value.
|
| 127231 | Defect |
Problem: Cancellation from OAC sends 'unknown reason' in the reason_memo.
Solution: reason_memo when canceled via the OAC will now always be absent since the runtime does not have information to explain the reason.
|
| 126975 | Defect |
Problem: Can't search by PMC in the OAC.
Solution: The 5 payment types are now classified and so appear in the dropdown. Other types may still appear in the dropdown.
|
| 129591 | Defect |
Problem: Bad product experience if the Interac Cancel call is not successful.
Solution: Payment cancellation flow is enhanced to support retries in the same way as the send payment. An extra state is provided so that it can be customized as an alert.
Cancellation is also enhanced to differentiate between customer and operator cancel. This allows auto reversal to be enabled for a customer-initiated cancellation but suppressed for Interac or Operator cancellations.
|
| 126206 | Defect |
Problem: FTM can update the payment status to an incorrect value if two notifications arrive or are processed out of order.
Solution: The status is updated only if the status change. Invalid updates are suppressed. All updates are recorded against the payment object with timestamps to allow clear diagnosis of any operational discrepancy.
|
| Back to top | 4.0.3 interim fix 3.1 (iFix3.1) release |
4.0.3.0 interim fix 3.1 (iFix3.1) fixes the following log4j vulnerabilities:
| Back to top | 4.0.3 interim fix 3 (iFix3) release |
| Fix number | Type | Description |
| 124389 | Defect |
Problem: Exception event caused by thread safety issue from UOW (Unit of Work) Event diagnostic code
Resolution: FTM was updated to correct the thread safety issue.
|
| 122028 | Defect |
Problem: Race condition in the Throttler FSM on 2 events/transitions between S_Idle and S_Throttling.
Resolution: Refactored Throttler FSM to use a single S_Throttling state.
|
| 123234 | Defect |
Problem: Deadlock while processing Transactions_Rejected() or Presentment_Rejected()
Resolution: Code changed to alter Db2 locking to avoid deadlocks.
|
| 120850 | Defect |
Problem: Incorrect handling of timeout conditions when PreCheck services are evaluated.
Resolution: A number of fixes were made to close gaps in the serial service execution logic regarding the timeout.
|
| 124507 | Defect |
Problem: Deadlock while processing Transactions_Rejected() or Presentment_Rejected()
Resolution: Code changed to alter Db2 locking to avoid deadlocks.
|
| 124597 | Defect |
Problem: Payment processing latency increased over a long test duration.
Resolution: Simplified a number of Error Check SQL statements to avoid unnecessary joins on database tables.
|
| 125429 | Defect |
Problem: Interac API allows some Unicode characters into fields in ISF that do not comply with the ISF XSD. This problem prevents the process from processing the payment, rejecting the payment, or both.
Resolution: Key actions were updated to catch XSD validation exceptions to allow rejections to occur.
|
| 124864 | Defect |
Problem: Events inserted into the database contain timestamps provided by application code. Therefore, at insert time the timestamps can be slightly older than expected, causing them to be missed by the code that polls the database.
Resolution: Timestamps are now updated by using a database trigger, which means they are much closer to the select availability time. Also, the polling process applies a small offset to allow a small margin of error regarding the timestamps.
|
| 124682 | Defect |
Problem: The ISF field for the electronic address was not large enough to hold the largest possible size (2048 characters).
Resolution: The ISF field was switched to one designed to hold electronic addresses up to 2048 characters in length.
|
| 125207 | Defect |
Problem: The MapTimeout reject path did not include XSD validation exception logic to allow the reject to occur when the ISF is invalid.
Resolution: Add the XSD validation exception logic to allow the reject to occur.
|
| 125205 | Defect | Problem: ClearingSystemReference not recorded as an ID_REFERENCE against the master transaction. Resolution: Code corrected to address this problem. |
| 125388 | Defect | Problem: Race condition around the IP Correlation record for DP Release. Resolution: Have the API create the Correlation record instead of IP on the Loaded message. |
| 125122 | Defect |
Problem: Add participant web service was experiencing a delay due to the participant detail creation process.
Resolution: The add participant web service was optimized to improve performance by reducing the scope of updating the participant roles to only those roles that are available to the participant instead of all role types.
|
| 124733 | Defect | Problem: Unnecessary SQL executed before the initial load of UI pages Inbound Transmissions, Inbound Batches, and Inbound Transactions Resolution: Execute SQL when the filter is applied |
| 124092 | Defect | Problem: Multi-byte characters not properly handled by emulators produced unexpected results such as false-positive validation errors. Resolution: Modified Java virtual machine (JVM) options to specify UTF-8 encoding. |
| 124737 | Defect | Problem: Real-time payments were observed to have significant delays during business rule server activation. Resolution: Released write locks before caches were updated in the Business Rules Server activation process. This fix enables real-time payments to be processed without any delays. |
| 125276 | Defect | Problem: Business Rules Server container wasn't able to find the over-the-wall fix JAR folder. Resolution: Corrected the location for the Business Rules Server over-the-wall fix JAR folder. |
| 123934 | Defect | Problem: The IP_ISO_MessageSet_US message library is not in the Interac artifacts container. Resolution: The IP_ISO_MessageSet_US message library was added to the Interac artifacts container. |
| Back to top | 4.0.3 interim fix 2 (iFix2) release |
| Fix number | Type | Description |
| 123988 | Defect |
Problem: Interac Response mapping for Reason can't handle the full 2000 characters that can be sent back in the reject messages
Resolution: Interac Response Mappers are updated to split the 2000 characters based on the length restrictions in the ISF XSD. The reason data can be spread over multiple (repeating) ISF elements. The data in the first element is used to populate the detailed IP error record.
|
| 123868 | Defect |
Problem: Timeout mid Serial Pre Checks does not correctly flag Failure so the default timeout error is not logged.
Resolution: Code corrected to correctly log the error in this circumstance.
|
| 123630 | Defect |
Problem: Socket Exception needs to be treated as an Indeterminate outcome
Resolution: Response Mappers updated to treat exceptions as Indeterminate.
|
| 123415 | Defect |
Problem: It's possible to create "Invalid E_EventAbortEvent" by adding more than 1024 chars to the EVENT_DATA context
Resolution: Code changed to not include EVENT_DATA context.
|
| 123294 | Defect |
Problem: Some Outflow events might get missed regarding publication
Resolution: FTM was improved to reduce the possibility of delayed or missing events.
|
| 123201 | Defect |
Problem: Digital Payment (DP) Integration flow can send ALL errors to Digital Payments regarding ReleaseTransaction but the transaction was already rejected
Resolution: Code path for this specific scenario was corrected to return only the error codes expected.
|
| Back to top | 4.0.3 interim fix 1 (iFix1) release |
| Fix number | Type | Description |
| 122923 | Defect |
Problem: Update Interac Customer “active” flag is reversed in-network call to Interac
Resolution: When the Update Customer API was updating a customer on the Interac Network, the API incorrectly set the "active" field of Customer Notifications to "false" even when the API caller specified the value as "true". |
| 122926 | Defect | Problem: Register Interac Customer API updates Participant incorrectly Resolution: If it isn't already assigned, the Register Customer API adds the "Interac Customer" role to the affected participant. The role was incorrectly being added to the current version of the participant instead of the draft version created specifically for the role. |
| 122994 | Defect |
Problem: 4.0.3.0 GA to 4.0.3.0 iFix1 Migration: Executing InteracImport.properties generates errors during DSU process
Work-around: DSU worksheet FeatureXREF.xls provided with 4.0.3.0 ifix1 must be replaced with the one provided here before the migration as documented in DSUMigration_v4.0.3.0_ifix1.pdf is done.
|
| 122123 | Defect | Problem: Interac – Notify IP Engine - Transmission Loaded event doesn't support "responseRequired" parameter Resolution: Enhanced PresentmentGroupEventHandler to now support parameter "responseRequired". The default value is TRUE. The reference implementation for the Transaction Server scheduler was updated for the event "Interac – Notify IP Engine - Transmission Loaded" to specify FALSE for the new parameter. This setting prevents the resending of messages when the pod that is running Transaction Server is restarted. <PARAMETER name="responseRequired">FALSE</PARAMETER> See migration document TransactionServerSchedulerChanges_v4.0.3.0_ifix1.pdf, which is included with the Interac e-Transfers Entitled documentation on Fix Central see 4.0.3-FTM-Interac-MP-Documents for Interac e-Transfers Data migration is required for existing WIP_RECORD entries. Follow the Database migration instructions as specified in the Release Notes. |
| Back to top | 4.0.3 release |
| Fix number | Type |
Description
|
| 119467 | Defect |
Problem: Web Service API: ID Reference search needs to remove hardcoded 'Channel'
Resolution: Added an optional queryparam so that the customer can supply a channel value to use to search for ID reference data.
|
| 119414 | Defect |
Problem: Interac customer page is displayed for a participant even if the permissions are not provided from Permission Assignments - Administrator
Resolution: Corrected Interac customer page from displaying for a participant even if the permissions are not provided from Permission Assignments - Administrator
|
| 121277 | Defect | Problem: System Error is displayed when search bar input is used in the Recipients subpage of the Participant Details page Resolution: The recipient data mapping for payment schema and message standard type and notification are missing. The missing mapping was added and the filter is now working as expected. |
| 120847 | Defect |
Problem: OCP - System Error is displayed when search bar is used in participant's recipient information page
Resolution: Missing bank name and account name mapping were added.
|
| 118486 | Defect |
Problem: Score Payment Call Failing because Calling localhost
Resolution: The outbound URL for payment, score, and fraud is now provided in the pod by using environment variables.
|
| 107523 | Defect | Problem: FTMDB and FTM Application Properties Not Promoted in IBM MQ REST and Response Flows Resolution: The BusinessDay bean interface was missing one of the exception signatures in local. The additional issue in the remote and access objects was also corrected. |
| 108531 | Defect | Problem: Interac Related Transactions tab missing from transmission hierarchy page in the Digital Payments user interface Resolution: The Related Transactions tab appears only if a related transaction exists. |
| Back to top |
4.0.3 interim fix 4 (iFix4) release
Canceled
|
| Fix number | Type | Description |
| 127308 | Enhancement | Description: The Interac Notification YAML is updated to a newer Interac specification. As a result, in the YAML (or Swagger UI) API for /notifications/push (Inbound Notifications), the "previous_fraud_type" and "current_fraud_type" Enum fields now include "BUS_EML_COMPR", "VNDR_EML_COMPR", "MALWARE", "APP_FRAUD", and "FRAUD_BUS". |
| 128460 | Enhancement | Description: The Interac Payments YAML is updated to a newer Interac specification. As a result, in the YAML (or Swagger UI) for /payment/origination/credit-transfer (Interac Outbound API), the "customer_authentication_method" Enum field now includes "TOKEN" and "MAKER_CHECKER". |
| 118436 | Enhancement |
Description: All Accounting Responses use the same SubType. All accounting requests now support a distinct accounting response type.
|
| 127228 | Defect |
Problem: When creditor.name is missing in an Interac /payment/origination/credit-transfer request, a validation error occurs. The path mentioned in the validation error was incorrect.
Solution: The validation error path when missing creditor.name was corrected.
|
| 129024 | Defect |
Problem: When creditor_account.identification.other.scheme_name.proprietary is missing in an Interac /payment/origination/credit-transfer request, a validation error occurs. The path mentioned in the validation error was incorrect.
Solution: The validation error path when missing creditor_account.identification.other.scheme_name.proprietary was corrected.
|
| 129093 | Defect |
Problem: The Interac Notifications API does not use the Interac schema validation 5000 error.
Solution: The API was updated to use the 5000 error when there is a validation issue to better describe what was wrong with the request.
|
| 120369 | Defect |
Problem: The \r, \b, and \f control characters were not being processed correctly by Interac /payment/origination/credit-transfer API.
Solution: The Interac /payment/origination/credit-transfer API was updated to always reject requests that include \b or \f characters. \r characters are still allowed and are now handled correctly.
|
| 128996 | Defect |
Problem: The Header parameters in the "FTM for Interac Inbound Notifications" APIs did not have their length constraints listed in the YAML.
Solution: The YAML is updated to now include these. Due to an issue with the Swagger UI, the UI will not show the length constraints. You must go to the YAML directly to see them.
|
| 129665 | Defect |
Problem: The YAML fields for invoicer ID, Invoicee ID, Ultimate Debtor ID, Ultimate Creditor ID, Initiating Party, and Debtor ID have a limit of 20 characters but the Interac specification allows up to 35.
Solution: The YAML fields for invoicer ID, Invoicee ID, Ultimate Debtor ID, Ultimate Creditor ID have been updated to accept up to 35 characters. However, the characters for Ultimate Debtor ID, Ultimate Creditor ID, Initiating Party, and Debtor ID can be no more than 80 bytes in total (when encoded as UTF-8).
To support this, three Business Rules Data descriptors were updated. The changes are all in the "Data XML Descriptor" tab of SampleBusinessRulesBaseConfiguration.xls:
The ibmValDepositorId field in the AcknowledgmentEndpointsTable row had its length changed from 20 to 35.
The ibmValDepositorId field in the SttlSubCreateBalOriginatorTable row had its length changed from 20 to 35.
The ibmValDepositorId field in the SttlSubWhenRequestedTable row had its length changed from 20 to 35.
The field lengths of Ultimate Debtor Id, Ultimate Creditor ID, Invoicer ID, and Invoicee ID are increased from 20 to 35 characters. The Initiating Party ID and Debtor ID fields retain their field length of 20 characters.
API Updates: With this change, the YAML introduces new objects used by the Initiating Party ID and Debtor ID to restrict their field lengths to 20 characters. These objects are:
Existing objects for the other ID fields are updated to support the new 35 character limits
|
| 128759 | Defect |
Problem: Race condition for Error handling between Digital Payments and Immediate Payments when a timeout triggers failure at prechecks and so on.
Solution: Persist the error data earlier that removes the race condition. This ensures the API sees the error code when it reports the reject.
|
| 127229 | Defect |
Problem: Incorrect handling of Ultimate Creditor/Debtor in the Score / Send payment requests.
Solution: Modify the mapping function to map Ultimate Creditor/Debtor for these requests.
|
| 129844 | Defect |
Problem: Customer requesting 400 code be able to ignore previous indeterminate responses.
Solution: HTTP error codes can now be marked as absolute reject. This allows the reject code to overrule a previous indeterminate response. Broadly the codes can be defined as:
Codes categorized as Reject can cause a reject, but only if no previous Indeterminate response was received. However, codes categorized as Absolute Reject will cause the payment to be rejected.
|
| 127039 | Defect |
Problem: Outflow publication failure was incorrectly marking the events as published.
Solution: This is now corrected and the unit of work is rolled back and an Unexpected Error is recorded in the Event logs (visible in the OAC).
|
| 128097 | Defect |
Problem: Incorrect handling of soft timeouts when a timeout is ignored because of a later soft timeout.
Solution: The code was changed to remove the one that is being skipped so it is not considered again.
|
| 127042 | Defect |
Problem: Some payment notification events can fail to correlate if FTM did not receive the send payment response.
Solution: Payment notifications that fail to correlate on clearing system reference (network ID) will then attempt to correlate on the request identification that was provided in the call to Interac.
|
| 127156 | Defect |
Problem: Some network notifications are not properly processed if 2 duplicates arrive at the same time.
Solution: The standard Immediate Payments duplicate check pattern was applied. Also, minor enhancements were made to avoid rejecting all duplicate requests, which allows at least one to proceed correctly.
|
| 128201 | Defect |
Problem: Audit log sometimes shows "DP Request Passed"; logged 3 times.
Solution: Resolved issue in PreCheck result evaluation code that erroneously missed updating an ObjValue causing the evaluation code to run twice for the same event causing a double report of "DP Request Passed" logged. This resulted in 3 rather than 2 reports of that message. This was only happening if the Sanction check was skipped based on supplementary data value.
|
| 127231 | Defect |
Problem: Cancellation from OAC sends 'unknown reason' in the reason_memo.
Solution: reason_memo when canceled via the OAC will now always be absent since the runtime does not have information to explain the reason.
|
| 126975 | Defect |
Problem: Can't search by PMC in the OAC.
Solution: The 5 payment types are now classified and so appear in the dropdown. Other types may still appear in the dropdown.
|
| 129591 | Defect |
Problem: Bad product experience if the Interac Cancel call is not successful.
Solution: Payment cancellation flow is enhanced to support retries in the same way as the send payment. An extra state is provided so that it can be customized as an alert.
Cancellation is also enhanced to differentiate between customer and operator cancel. This allows auto reversal to be enabled for a customer-initiated cancellation but suppressed for Interac or Operator cancellations.
|
| 126206 | Defect |
Problem: FTM can update the payment status to an incorrect value if two notifications arrive or are processed out of order.
Solution: The status is updated only if the status change. Invalid updates are suppressed. All updates are recorded against the payment object with timestamps to allow clear diagnosis of any operational discrepancy.
|
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"4.0.3"}]
Was this topic helpful?
Document Information
Modified date:
09 June 2022
UID
ibm16434117