1. Locate the Interac artifacts pod named: ftm-artifact-interac-*
2. Copy the file /home/ftmuser/ftm/artifacts/ftm-db2-check-4.0.3-iFix6-latest.zip from the Interac artifacts pod
3. Extract the contents of this downloaded file.
4. Locate the ../ibm/ftm/shared/v403/pfs/Database/db2/{os}/util folder in the extracted directory structure.
5. Locate the PAY_AND_NON_PAY_TXN_V.PayOnly.ddl file.

Improved security of communication between FTM components
FTM communication between components is now more secure with TLS encryption.
IBM MQ and Db2 communications are running over TLS.
The Java Platform, Enterprise Edition, J2SE, and IBM App Connect Enterprise client applications connect over a TLS protocol.
The procedure to generate (if self-signed certificates) and configure TLS certificates used by all the FTM components is documented by FTM. The default CipherSuite/CipherSpec used by IBM MQ and all the clients is SSL_RSA_WITH_AES_128_CBC_SHA256/TLS_RSA_WITH_AES_128_CBC_SHA256. This default can be customized during deployment with the Operator Instance YAML.

LTPA keys by default
No customization is required. LTPA keys are managed by the individual Java Platform, Enterprise Edition Liberty server instances. The default configuration is used and LTPA keys are created when the application pod starts.

Readiness and liveness health check probes and prestop pod lifecycle event
FTM now comes with health check probes (readiness and liveness) and with prestop pod lifecycle events implemented.
Readiness and liveness probes: During the rolling upgrades, the new version pod is created and when it becomes ready, Red Hat OpenShift deletes the old pod. Red Hat OpenShift runs the readiness probe to decide whether the pod is ready or not. Unless the probe returns success, it does not mark the new pod in ready state.
Liveness probes are run periodically, like a readiness probe. If a liveness probe fails, Red Hat OpenShift restarts the container.
Prestop pod lifecycle event: Red Hat OpenShift allows adding the PreStop hook to be run inside the container before Red Hat OpenShift deletes the container. This script is called by Red Hat OpenShift before it deletes the container.

Customize FTM by using ConfigMaps
FTM operator now supports configmap-based approach to let user provide custom server.xml or other configuration files in addition to the persistent volume-based approach. Separate ConfigMaps are created for each FTM component, and the customer can place all the customized files in those ConfigMaps. This method is useful for customers who do not use persistent volumes or do not have easy access to the persistent volumes from outside the container. This method is supported for JSE and Java EE components.

Usage count metering differentiates between production and non-production environments
The FTM metering application, which is in the OAC pod, now differentiates between production and non-production usage counts. The differentiation is made based on the "Environment type" variable under "License" category of IBM FTM Base Operator.
- Customers should set this variable to "Production" or "NonProduction" based on the type of environment they are building during the operator installation.
- Regardless of "Environment type" value, all usage counts are calculated and stored in the database.
- Only production mode usage counts are reported to the IBM License Server, which is in the "ibm-common-services" namespace and is shared across all projects.

Enhance Interac Fraud Flow to propagate Interac participantFraudInstruction

Update Initiating Party handling to incorporate usage of Interac Registration ID when Participant ID is provided

Interac Events - Request for Payment Schedule Notifications

Interac Notifications API:  FTM accepts Interac pushed Request for Payment Scheduled notifications.  FTM logs the notification and can be customized to publish the notification to external systems.

Reject Interac Payment When Assigned to Open (Not Active) Business Day

Interac Send Money
FTM rejects an Interac Send Money transaction when the transaction gets assigned to a business day that is not active.  The feature ensures a payment does not accidentally get stalled due to system misconfiguration.

Implement Interac Inbound Heartbeat

Interac Notifications API:  FTM implemented the /heartbeat operation of the Interac Notifications API.  FTM responds positively to the Interac Network's heartbeat requests when FTM is healthy and can receive and process Interac Push Notifications and responds negatively when FTM is unable to receive and process Interac Push Notifications.

Enhance eTransfers Workflow to Assign Error Code to Items Whose ISF Data field is Not Current

Interac Send Money:  FTM rejects an Interac Send Money transaction if the transaction with a specific error code when the FTM Gateway is misconfigured.  The feature ensures a payment does not accidentally get stalled due to system misconfiguration.

Reject payment when debtor not enrolled into Interac

FTM now supports canceling Interac transactions by using the Digital Payments Control Center user interface, on the Inbound Transaction page at Origination & Receipt > Transactions.
This action can be run by using More > Actions > Cancel, and requires transactions to have the 'Interac e-Transfers' Payment Scheme and have an FTM base Status of 'Outgoing Payment Pending Creditor Action' (S_OutgoingCTPendingCreditorAction).
When the user clicks Cancel, a dialog box opens. The dialog box has three cancel actions available, Cancel, Force Cancel, and Force complete, each with different workflows and user input fields.
After the cancel is initiated, a message is sent to the Immediate Payments command queue and is then processed by an Immediate Payments workflow.

PFS Participant Directory UI: Interac Customer Support (Toggle, Create, Update)

 Interac Customer Screen

A new participant directory page was added to 4.0.3, which allows viewing, creating, editing, and toggling of an Interac customer with the Interac Network.

Permissions

New view and edit permissions for access control were added. Note: Edit permission is required for using the toggle button.

Interac Customer page

A new Interac customer page is visible if the user has view permission and the selected participant has the Interac Customer role. This page is an operational data page that is editable only when the latest, active version of the participant is viewed.

If a participant is not registered with the Interac network, the page is in create mode. In create mode, the Interac participant user ID is editable. By default, this value is set to the participant ID, but can be changed.   

After it is saved, the Interac participant user ID cannot be changed. If the user has edit permission, a toggle button appears to activate or deactivate the Interac customer.

Note: If the participant has no addresses, you cannot select address information

When the toggle button is clicked, a dialog box that asks for a reason for toggling this Interac customer is opened.

Retry Requirements from (send Money only)

Automatically Reject Interac Payment When Stalled in Transaction Mapped

Enrich/Fetch Interac Participant ID information from participant directory and pass it to Interac