SaFi Bank Space : Transactions - communication with Fraud & Risk Service (Slacker)

Created by Slavomír Kocka, last modified by Michal Glaus on Nov 29, 2022

Domain “Transactions” uses both types of communication:

REST for integration with UI or Application
Async Kafka for communication with Thought Machine (TM) or communication between modules

For communication between the domain and Fraud Services is currently as well expected async communication using Kafka platform.

Expected communication

There are two areas of expected communication. First would be information flow about transactions to build knowledge-base by fraud. Second would be querying of the fraud system whether certain transaction is permitted or not.

“Bank events” will be produced into Kafka Topic by TransactionProcessorManager (TPM) at the end of processing of each transaction, whether successful or not. These will be consumed by various services and among them would be also Slacker. By this it will receive all information about transactions, even rejected by Slacker itself.
TPM would send request using respective Kafka topic for “advice” if to process certain transaction. This step would happen before any other processing, especially before TM. Only alternative when Slacker is omitted is when there is payment between own accounts (owner of both accounts is the same) or when source or target account is internal bank account (eg. fees, interest rate). After receiving async response TPM would continue transaction processing. There is few outcomes possible:
- Approve - transaction will be processed in standard way and final result would be streamed into respective topic.
- Reject - transaction will not be processed any further and final result in form or reject would be streamed into respective topic.
- Step-up - this would indicate to TPM to request additional authorisation from the App. When received, process would continue.
- Manual approval - this would be triggered by Slacker itself, thus TPM would expect for Approve or Reject from this manual process. Due to nature of this step it would be not specially treated in Transaction domain.

Note: There is uncertainty whether card transactions would be processed by TPM. If that would be the case, TPM would expect sync communication here. On top of that “manual-approval” and “step-up” would be omitted as non applicable.

Attachments:

~drawio~61d41633e67ea2006bc72586~Untitled Diagram.drawio.tmp (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio.png (image/png)

~Untitled Diagram.drawio.tmp (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio.png (image/png)

~Untitled Diagram.drawio.tmp (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio (application/vnd.jgraph.mxfile)

Untitled Diagram.drawio.png (image/png)