Skip to main content

[V2.1] Reviewing Flagged Transactions

Find the transactions your policies flagged, read why, and approve or reject them.

Written by Emanuel

When your policies can't decide on a transaction, they flag it, and it waits for a person on your team. Your status stays Pending, and on an outgoing transaction nothing is sent to the counterparty institution until someone approves or rejects the flags.

Requirements

Your role needs permission to authorize and reject transactions: Group Admin, Entity MLRO, Entity Admin or Analyst, as listed in Member Roles and Permissions.

Find flagged transactions

  • Inbox: the row "Transactions are waiting for your action" shows how many are flagged. Click it to open them.

  • Transactions: the Flagged tab, under All, Incoming or Outgoing, lists them with a count.

Click Review Flags on a row to open the transaction at its Review panel.

Read the flags

The Review panel says how many items hold your authorization. Under Policy flags, each line gives one reason your policies flagged the transaction. A reason can be an address, a counterparty institution, a blockchain or a token that your policies flag or that you haven't reviewed yet.

Participants marks the flagged customer or address, and PII data opens the customers' Travel Rule data. The Timeline shows when your policies flagged the transaction, and Comments holds your team's notes.

A flagged transaction's Review panel, the Approve and Reject buttons boxed

Approve or reject

Approve and Reject in Policy flags decide all the flags on the transaction at once.

  • Approve: the flags are resolved. Once nothing else holds your authorization, your status becomes Authorized by itself.

  • Reject: your status becomes Rejected, and the counterparty institution is told.

The original flag stays in the audit log after you resolve it, with who resolved it.

Requirements still waiting

Waiting on lists the requirements you set that the counterparty institution hasn't met yet, such as Receive Travel Rule data. You can wait for it, or click Skip on one requirement or Skip all. Each requirement is also skipped by itself once its time-out runs out.

Every skip is recorded in the audit log. A skip only stops the requirement from holding your authorization, so your customer's personal data is still held until the counterparty confirms the destination address.

Authorize with items still open

You can click Authorize at the top of the transaction while a flag or a requirement is still open. The dashboard then lists what will be overridden and asks for a reason, which is recorded. Your status becomes Authorized straight away, and your open requirements become Skipped.

Requirements the counterparty institution set for you stay open until you meet them. To stop the transaction instead, click Reject.

After your decision

Once every institution has authorized an outgoing transaction, it is Ready to settle. Your organization sends the funds and records the transaction hash, through your integration or with Add tx hash. Statuses explains what each status means from there.

Did this answer your question?