SaFi Bank Space : GCP Command Pub/Sub subscribe logic for POC purpose

Created by Kobe Wang, last modified by User e8658 on Feb 13, 2023

The command messages are initiated from external systems like risk, accounting, loan, transaction, etc. They will send the command messages to our GCP project “Data Test”, Pub/Sub topic <slacker-manager-commands>. The command messages like below:

Command Type	Example	Description
`DEBUG_MESSAGE`	{ "commandType":"DEBUG_MESSAGE", "customerId":"2a237743-4ea0-3d9e-bc35-b89b78d39011", "params":{ "message":"This is a debug message" } }	Writes the message with a log. debug method
`CREATE_JIRA_TICKET`	{ "commandType":"CREATE_JIRA_TICKET", "customerId":"6049ca0e-9e4b-4e69-9dbf-9086c7510150", "params":{ "messageType":"CREATE_JIRA_TICKET", "accountId":"a94be305-a08f-4bd2-9d08-e9a796c87a26", "transactionId":"99ceba0d-0ef9-4f15-bec6-54e1fe46c057", "transactionAmount":"445000.0", "transactionType":"INTRABANK_TRANSACTION", "transactionPosted":"2023-02-10T10:22:32.822Z", "transactionDirection":"DEBIT", "manualApproveReason":"slacker demo test manualApproveReason" }, "fraud report":{ "transactionId":"99ceba0d-0ef9-4f15-bec6-54e1fe46c057", "customerId":"6049ca0e-9e4b-4e69-9dbf-9086c7510150", "amount":445000.0, "tranasction_direction":"DEBIT", "report_type":"Fraud Check" }, "aml report":{ "transactionId":"99ceba0d-0ef9-4f15-bec6-54e1fe46c057", "customerId":"6049ca0e-9e4b-4e69-9dbf-9086c7510150", "amount":445000.0, "tranasction_direction":"DEBIT", "report_type":"AML Check", "AML0001A":"Completed", "AML0002A":"Triggered", "AML0003A":"Completed", "AML0009A":"Completed", "AML0015A":"Completed" }, "approvalStatus": "APPROVED", "commands": ["SEND_NOTIFICATION", "CREATE_JIRA_TICKET"] }	Calls ticket-manager and create a new JIRA ticket like https://safibank.atlassian.net/jira/servicedesk/projects/BOSD/issues/BOSD-131 (need authorization by Back Office team).
`LOG_MESSAGE`	Sample Message { "commandType":"LOG_MESSAGE", "customerId":"2a237743-4ea0-3d9e-bc35-b89b78d39011", "params": { "transactionId":"XXXXX", "amount":"XXXXX", "ruleHit":"XXXXXX", "approvalStatus":"", "commands":"" }, "logId": "", "logTimestamp":"" } `params` will not have fixed key-value pairs, and can accept any number of keys. The idea is to dump `params` as a JSON string for later processing.	Aim: To send log messages to Slacker for suspicious activities, which were picked up on Anti-Fraud side Outcome: Slacker upon receiving LOG_MESSAGE, push the message to another endpoint that ingests and writes the log into a table. Before pushing the message, Slacker will add a `logId` and a `logTimestamp`
`SEND_NOTIFICATION` (PUSH)	{ "commandType":"SEND_NOTIFICATION", "customerId":"2ae37743-4ea0-3d9e-bc35-b89b78d39011", "params":{ "messageType":"OVERDRAFT_OPENED" } }	Calls output-manager and send the message to our internal Kafka topic “message.internal“
`REVOKE_CUSTOMER_KEY`	{ "commandType":"REVOKE_CUSTOMER_KEY", "customerId":"2ae37743-4ea0-3d9e-bc35-b89b78d39011" }	SM-4805 - Add revoke customer private key command Done
`FREEZE_ACCOUNT`	{ "commandType":"FREEZE_ACCOUNT", "customerId":"2ae37743-4ea0-3d9e-bc35-b89b78d39011" }	SM-4804 - Add account status change command Done
`UNFREEZE_ACCOUNT`	{ "commandType":"UNFREEZE_ACCOUNT", "customerId":"2ae37743-4ea0-3d9e-bc35-b89b78d39011" }	SM-4804 - Add account status change command Done

2. Subscribers will be listening to the GCP Pub/Sub and try to parse it, if the coming command message can’t be parsed, will remove it from the current topic and send it to its related DLQ topic.

If the command type is “DEBUG_MESSAGE“, just write the message with a log. debug method.
If the command type is “SEND_NOTIFICATION“, it will call output-manager and send the message to our internal Kafka topic “message.internal“
If the command type is “CREATE_JIRA_TICKET”, will call ticket-manager and create a new JIRA ticket like https://safibank.atlassian.net/jira/servicedesk/projects/BOSD/issues/BOSD-131 (need authorization by Back Office team).

Attachments: