Fraud screening deployment

The simulator reads requests from the Immediate Payments application output queue, <prefixes>.REQUEST.TO.FRAUD. It responds to the application by placing responses on the <prefixes>.RESPONSE.FROM.FRAUD queue.

Fraud screening request

The fraud screening request uses the following information:

Transaction type (business concept) - IP_FRAUD_REQUEST.
Request ID.
ISF structure of the received request.

Fraud screening response

Status code	Transaction type (business concept)
ACTC (TCH) or ACCP (SCTInst)	IP_FRAUD_RESPONSE
PDNG	IP_FRAUD_RESPONSE_PENDING
RJCT	IP_FRAUD_RESPONSE_REJECT

The simulator responds to a fraud screening request with a fraud screening response.
ISF transaction structure - isf:Acknowledgment.
In the response, the request ID and TransactionIdentification are populated from the request ID of the fraud screening request.
The response contains an accept, pending, or reject status code.

For responses with a pending and reject status code, a reason and reason code are provided in the acknowledgment message. For more information, see Reject codes and reasons.

To control the status codes of the response acknowledgments, the following user-defined properties are provided:

SOF_Name_RJCT - the default value is SOF.RJCT.
SOF_Name_PEND - the default value is SOF.PEND.
SOF_Name_PEND_RJCT - the default value is SOF.ACK.RJCT.

The debtor name of the fraud screening request message is compared to these properties.

The following example shows the debtor name within the fraud screening request message ISF:

<PartyRole xsi:type="isf:DebtorRole">
   <Player xsi:type="isf:Person">
      <PartyName>
         <Name>Mr Debtor 1 SOF.RJCT</Name>

The ISF field for the debtor name is populated from the debtor of the original message.

If the name field contains the string that is defined in SOF_Name_RJCT property, as shown in bold text in the previous example, the simulator replies with a reject status code. And, the business concept is set to IP_FRAUD_RESPONSE_REJECT.

If the name field contains the string that is defined in the SOF_Name_PEND property, the simulator replies with a pending status code. And, the business concept is set to IP_FRAUD_RESPONSE_PENDING.

If the name field contains the strings that are defined in the SOF_Name_PEND and the SOF_Name_PEND_RJCT properties, a response with a reject status code is stored in the store acknowledgment queue. Otherwise, a response with an accept status code is prepared.

When any message is placed on the trigger acknowledgment queue, the stored acknowledgment message is sent to Immediate Payments.

SOF_CrdtAgtRCLRspRjct - the default value is BBBBUS91(SCTInst).

The simulator rejects a credit return request when the creditor agent BIC is equal to SOF_CrdtAgtRCLRspRjct.

SOF_CretrAgtRspRjct - the default value is 021200282(TCH):

The simulator rejects a credit return request when the case creator agent ID is equal to SOF_CretrAgtRspRjct.

SOF_CrdtAcctROIRjct - the default value is DE29A12000194212188885(SCTInst):

The simulator rejects a credit return request when the creditor account is equal to SOF_CrdtAcctROIRjct.

If the described conditions do not apply, the simulator responds with an accept status code.

Status code quick reference example

The simulator behavior that can be expected when the defaults defined for the user-defined property (UDP) values are used is shown in the following table.

Table 1. Example fraud screening simulator responses for default property values
ISF type	Condition	Value	Status
All ISF types	Contents of the debtor name field contains	SOF.PEND	Pending
		SOF.ACK.RJCT	The triggered acknowledgment contains a reject status code. If this value is not in the name field, the triggered acknowledgment response contains an accept status code.
		SOF.RJCT	Reject
CreditReturn	Creditor agent BIC is equal to	SCTInst:SOF_CrdtAgtRCLRspRjct (default: BBBBUS91)	Reject
CreditInvestigation	Case creator agent ID is equal to	TCH:SOF_CretrAgtRspRjct (default: 021200282)	Reject
All ISF types		None of these values	Accept