My Oracle Support Banner

Parametrize JMS Response messages for blocked and released payment in TF (Doc ID 2742379.1)

Last updated on JANUARY 12, 2021

Applies to:

Oracle Financial Services Transaction Filtering - Version 8.0.6 and later
Information in this document applies to any platform.

Symptoms

User need to decide whether to display of hide the data within the below three fields at any given time for JSON feedback message for BLOCKED and RELEASED payments in JMS queue.

MATCH REASON, USER COMMENTS and RISK REASON fields within this JSON response should be parametrizable

parametrization should be possible for any type of incoming real-time payment (either Swift or Fed wire payment) and at a jurisdiction level

Steps to reproduce :

Step 1 : Post the swift message

Step 2 : Open web logic JMS queue

Step 3 : Check for response messages

Expected result :

The MATCH REASON, USER COMMENTS and RISK REASON fields within this JSON response should be parametrizable,

Actual result :

The MATCH REASON, USER COMMENTS and RISK REASON fields are displayed by default and it cannot be parametrized.

JMS Response :

{"RISK SCORE":95,"REFERENCES":[{"TYPE":"TRANSACTION","RISK REASON":"[Risk-Watchlist Screening Evaluation]",

"REFERENCE ID":"ABC1234","STATUS":"SUSPICIOUS",

"MATCH REASON":"[B0011]Exact bank identification code (BIC) match - ,[B0021]Bank identification code (BIC) contains -"}],

"EXTERNAL DATA":null,"MESSAGE REFERENCE":"091117-DSNY0001","STATUS":"BLOCKED","MATCH SCORE":95,"USER COMMENTS":"Test block."}

Changes

JMS Response customized 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.