3. Monitor Transaction

When the Payment Order is created, transaction monitoring will be kicked off automatically.

Based on the compliance score, a Payment Order will be automatically approved, automatically denied, or have a Case opened for manual review.

Using your sandbox account, you can test these scenarios using select counterparties. If you are unfamiliar with making payments, check out the Payments Quickstart Guide, as well as the Internal Accounts and Counterparties Sandbox details pages. The sandbox will return dummy data and not run live checks on the data submitted, as those require calls to downstream data providers.

Compliance Score	Sandbox Simulation	Result
`low` or `medium`	Create a debit payment to the default `Harry Potter` counterparty.	The `Payment Order` will be automatically `approved`.
`high`	Create a debit payment to the default `Snape (ACH/Wire Return) - R03 No Account/Unable to Locate Account` counterparty.	A `Case` will be opened for manual review, and the `Payment Order` will be in `needs_approval` state.
`very_high`	Create a debit payment to the default `Lucius (General Failure)` counterparty.	The `Payment Order` will be automatically `denied`.

Additional information about the Payment Order can be found in the related Decision object.

Webhooks are used to provide status updates on Payment Orders. The following are relevant states for transaction monitoring.

Event	Description
`payment_order.needs_approval`	A `Payment Order` needs approval when a transaction monitoring `Case` has been opened or when payment operations approval rules are triggered.
`payment_order.approved`	A `Payment Order` has been `approved`, either automatically or manually.
`payment_order.denied`	A `Payment Order` has been `denied`, either automatically or manually.

If a Payment Order is approved and will be sent to the bank. If a Payment Order is denied, it will not be sent (it is a terminal state).