Skip to main content

Configure Orchestrate Transaction Sender

Follow these steps to configure and connect to Orchestrate Transaction Sender dependencies:

  1. Configure Apache Kafka (mandatory)
  2. Configure Redis (optional). Use a persistent cache (recommended).
  3. Configure monitoring (optional). Improve the development experience and debugging.
  4. Configure Multi-tenancy (optional). Use Orchestrate with multiple tenants.

In addition to the dependencies, Orchestrate Transaction Sender needs to be configured to connect to the other microservices and to define how the service should be exposed.


Configure each microservice using microservice-specific environment variables. Command line options are also available and take precedence over environment variables.


Environment VariableCommand line optionDescriptionDefault
API_URLapi-urlURL of the Gateway API HTTP endpoint.localhost:8081
API_METRICS_URL(only ENV var)URL of the Gateway API HTTP metrics endpoint.localhost:8082
KEY_MANAGER_URLkey-manager-urlURL of the Key Manager HTTP endpoint.
NONCE_MAX_RECOVERYnonce-max-recoveryMaximum number of tries to recover a transaction with invalid nonce before returning an error.5
NONCE_MANAGER_TYPEnonce-manager-typeType of the nonce manager cache. Can be in-memory or redisredis

CLI options

See the complete list of command line options for the Orchestrate Transaction Sender: