Skip to main content

[V2.1] Statuses

What My Status, the transaction status and each requirement status mean, and what moves them.

Written by Emanuel

Every transaction shows two statuses side by side, because each institution keeps its own decision. My Status is where your organization stands, and Transaction status is where the transaction stands across every institution and the blockchain. It's normal for the two to differ while a transaction is in progress.

My Status

My Status follows from your policies' verdict and your requirements, so nobody sets it by hand. Every institution on the transaction sees it, but not the reason behind it.

  • Pending: your policies are still running, they flagged the transaction and it waits for a person on your team, or a requirement isn't met yet.

  • Authorized: your policies approved the transaction, and every requirement is satisfied, skipped or doesn't apply. It's also Authorized when a person on your team authorized it over an open flag or requirement.

  • Rejected: your policies or your team rejected the transaction, or one of your requirements was rejected, such as a beneficiary name that doesn't match.

  • Canceled: the originator's institution, which created the transaction, withdrew it before settlement. No other institution can cancel.

My Status can still change after Authorized. When something on the transaction changes and your policies run again, a new flag or a reopened requirement puts it back to Pending, and a rejection makes it Rejected.

Your policies' verdict

Your policies give each transaction a verdict: approve, flag or reject. When several apply, the strictest wins. The verdict is private to your organization, and other institutions see only its effect on My Status.

A flag keeps My Status at Pending until a person on your team approves or rejects it, as described in Reviewing Flagged Transactions. The timeline shows the verdict, and the audit log keeps the original flag after it is resolved.

Transaction status before settlement

  • Active: at least one institution is still Pending.

  • Ready to settle: every institution has authorized the transaction, so the originator's institution can send the funds and record the transaction hash.

  • Rejected: at least one institution rejected the transaction, so the funds aren't sent.

  • Canceled: the originator's institution canceled the transaction, so the funds aren't sent. A cancellation wins over a rejection.

Transaction status after settlement

Once the funds move on the blockchain, the transaction never goes back to a status from before settlement.

  • Settled: the funds moved and every institution has authorized the transaction.

  • Settled Incomplete: the funds moved while at least one institution hadn't authorized yet. It becomes Settled once every institution has.

A transaction recorded for a deposit that already arrived starts as Settled Incomplete. A Settled transaction can also go back to Settled Incomplete, for example when an institution rejects it after settlement over a compliance issue. Returning the funds then takes a revert.

Reverts

A revert returns the funds of a settled transaction. It is a new transaction linked to the original, and the original's status follows it.

  • Revert Requested: an institution asked for a revert.

  • Revert Authorized: the revert was authorized.

  • Reverted: the revert settled on the blockchain.

  • Reverted-IncompleteAuthorization: the revert settled before it was authorized.

  • Revert Rejected: the revert was refused.

  • Revert Canceled: the institution that asked for the revert withdrew it. Only that institution can.

Requirement statuses

A requirement is one obligation that must be met before an institution can authorize, such as receiving the Travel Rule data. One institution sets it, and the same institution or the counterparty must meet it.

  • Pending: not met yet.

  • Satisfied: met.

  • Partially satisfied: part of the Travel Rule data was sent or received. It applies only to sending and receiving Travel Rule data, and to a partial name match reported by your developers.

  • Skipped: its time-out ran out, the institution that set it skipped it, or a person authorized the transaction while it was open. Every skip is recorded in the audit log.

  • Rejected: the institution that set it refused it, or the institution asked to meet it answered with a rejection. A rejected requirement makes My Status Rejected.

  • N/A: it doesn't apply to this transaction, for example below your Travel Rule threshold.

A skipped Receive Travel Rule data can still change. When the counterparty's data arrives after the time-out, it becomes Satisfied, or Partially satisfied when only part of it arrives.

Your developers read the same statuses through the API, as described in Statuses in the developer docs.

Did this answer your question?