SaFi Bank Space : Testing of Transaction Use Cases and Flows

Created by User 87682, last modified on Sep 15, 2022

Collaborators:

For testing of integrating Transactions Topics with Functions

During testing, we assume that Slacker will be used primarily for 2 processes:

SYNC

This will consist of REST API requests sent from Slacker
Transactions that will trigger the synchronous process will depend on business functionality, whereby particular transactions may be flagged for screening via Slacker
E.g. Anti-Money Laundering flags based on transaction parameters
In this case, Slacker will send a request to a Cloud Function, and the Cloud Function will return a decision for TransactionStatus as well as a Command (e.g. SEND_NOTIFCATION)
- ```
enum class TransactionStatus {
    APPROVED,
    REJECTED,
    STEP_UP_NEEDED_LEVEL1,
    MANUAL_APPROVAL_NEEDED,
}
```

ASYNC

This refers to screening transaction streams that are outside of business logic used in the synchronous workflow
E.g. Freezing of suspicious account due to suspicious transactions using some fraud detection model, Blocking anomalous transactions and creating a ticket for manual review
In this case, the Cloud Function that is listening to the Pub/Sub topic will send a Command to Slacker to act upon the detected anomaly or event

API REFERENCE

TO DO

Define the type of commands for ASYNC workflow
- Reference Page - GCP Command Pub/Sub subscribe logic for POC purpose