Case Management: Changing a Transaction or Account Status

Once a transaction is evaluated through the Workflow, you can assign an agent for case review within the Case Management tool. The agent can then submit a change of status for the transaction or account within the dashboard.

❗NOTE: Since the status update takes place on the dashboard, this can only be done if the entity triggered a case-generating rule.

To facilitate changes to the status of an account or a transaction from the dashboard, there are a few implementation steps that need to be completed to support this functionality.

This article will cover the following sections:

• Accessing Change Status Modal in the Dashboard
• Implementing Change Status for Accounts
• Implementing Change Status for Transactions

Accessing Change Status Modal in the Dashboard

The Change Status option is accessed from a Case detail view.

For Accounts, it can be reached from the Overview section under the More Actions menu.

For Transactions, it can be reached from the Recent Transactions section under the More Actions menu.

Implementing Change Status for Accounts

The Change Status form provides several options to update the status of the account. These options include "Active," "Deactivated," and Frozen.

Changing the status in the modal does not do anything on its own. The UI form DOES NOT update the record in Alloy In order to save the new status for Accounts, Alloy must receive the final status via an API call. If Alloy does not receive the PATCH request, the status in the modal will revert to the original status.

The steps to implement support for changing the status:

1. The new status is selected from the Change Status form.
2. A webhook is fired by Alloy containing the new status.
3. A PATCH API call must fire to Alloy to change the new status.

If Step 3 doesn’t happen, the status will revert to the original status; Alloy does not change any status automatically.

When a new account status is selected under the Change Status form, a webhook will fire to let you know immediately when the status has changed from the dashboard. A listener should be setup for the webhook event Notify on attempted bank account status update.

The webhook event will return a response that looks like:

{
  "request_token": "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
  "timestamp": 1659717998440,
  "type": "create:bankaccountsnapshots:status_description",
  "description": "",
  "data": {
    "bank_accounts": [
      {
        "bank_account_id": "txn-account-status-update-test-02-acc01"
      }
    ],
    "new_status": "Frozen",
    "sent_by": "agent@sample.com",
    "sent_at": 1659717998363
  }
}

Parse the response for data.new_status for the account update. With the parsed updated status, submit a PATCH/accounts API call to save the new status in the dashboard.

Implementing Change Status for Transactions

The Change Status form provides the options "Accepted" and "Rejected" to update the status of the transaction.

However, changing the status in the modal does not do anything on its own. In order for changing the status to work for Transactions, Alloy must receive the final status via an API call.

The steps to implement support for changing the status:

1. The new status is selected from the Change Status form.
2. A webhook is fired by Alloy containing the new status.
3. A PATCH API call must fire to Alloy to change the new status.

If Step 3 doesn’t happen, the status will revert to the original status; Alloy does not change any status automatically.

When a new transaction status is selected under the Change Status form, a webhook will fire to let you know immediately when the status has changed from the dashboard. A listener should be setup for the Webhook event Notify on attempted transaction status update.

The webhook event will return a response that looks like:

{
  "request_token": "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
  "timestamp": 1659717400214,
  "type": "update:transactions:status",
  "description": "",
  "data": {
    "transactions": [
      {
        "transaction_id": "3458309489520AAAA",
        "current_status": "Paused"
      }
    ],
    "new_status": "Accepted",
    "sent_by": "agent@sample.com",
    "sent_at": 1659717400133
  }
}

Parse the response for data.new_status for transaction update. With the parsed updated status, submit a PATCH/transactions API call to save the new status in the dashboard.

❗ NOTE: The update to the status in the UI form DOES NOT update the record in Alloy. You must submit a PATCH request with the updated status from the webhook in order to be reflected in Alloy’s dashboard. If the PATCH request is not fired, the status in the modal will revert to the original status.