Transaction Approval Configuration

  • This chapter describes the features of the Airlock IAM Transaction Approval module and how to configure and use them:
  • The module exposes a REST API that allows 3rd party systems, such as e-banking systems, to verify transactions by sending transaction details to the end-user using second-factor authentication tokens. Banking payment approval is a typical use case.
  • The module is meant to be used as an internal infrastructure, e.g. invoked from an e-banking system acting as a delegating entity on behalf of a user and not to be exposed directly to the internet.

Summary of technical facts

The following is a brief list of technical facts of the Airlock IAM Transaction Approval.



Description and links

Module name


The Transaction Approval module can be enabled or disabled using the application parameters property iam.modules.

Configuration root

Transaction Approval

The Transaction Approval module is a top-level element in the configuration.



The URL of the Transaction approval interface is defined by the application parameter iam.transaction-approval.url.path and defaults to /<instance-name>-transaction-approval/.