Skip to main content
Pix Direct, via JD connects your ledger straight to the Pix arrangement through JD’s DICT and SPI gateway. DevOps sets its behavior through environment variables at deploy time. To change a variable, restart the service. This page covers the variables distinctive to this rail. For the datastore, multi-tenancy, streaming, telemetry, and authentication knobs that every Lerian Go service shares, see BYOC configuration essentials.
In the tables below, the Default / Required column shows the default value. A bold qualifier (for example Required) marks variables you must set. means no default. 🔒 marks a secret — inject it at deploy time from your secret store, and never commit it. This page lists variable names and behavior only. It prints no secret values.

Server and port

The service listens on the address in SERVER_ADDRESS (default :8080). The liveness, readiness, and version probes bind this same port. See Server for the shared server knobs and Default network ports.

JD integration

Credentials and endpoints for JD’s OAuth-secured API and its Pix (JDPI) surface.

Dynamic QR code hosting

The rail hosts signed (JWS) dynamic-QR payloads and the JWK set used to verify them. The plugin serves those documents under the host in QRCODE_PUBLIC_BASE_URL. Set a bare host (FQDN) with no URL scheme, because JDPI rejects a scheme.

Midaz ledger binding

Which Midaz organization, ledger, asset, and external account this rail books Pix movements against, plus the ledger service endpoints and machine-to-machine credentials.

Transaction and operation routes

The plugin maps Pix cash-in, cash-out, reversal, and intra-PSP flows onto named Midaz transaction and operation routes. Set one value per flow so the plugin books each Pix event onto the correct route.
OPERATION_ROUTE_CASHIN_* and OPERATION_ROUTE_CASHOUT_* stand for exactly twelve concrete per-leg route-mapping variables (eight cash-in, four cash-out). Each maps one pipeline leg to a Midaz operation-route ID — set each one explicitly:Cash-in (8): OPERATION_ROUTE_CASHIN_CREDIT, OPERATION_ROUTE_CASHIN_CREDIT_QRCODE, OPERATION_ROUTE_CASHIN_CREDIT_REVERSAL, OPERATION_ROUTE_CASHIN_DEBIT, OPERATION_ROUTE_CASHIN_DEBIT_QRCODE_EXTERNAL, OPERATION_ROUTE_CASHIN_DEBIT_REVERSAL_EXTERNAL, OPERATION_ROUTE_CASHIN_REVERSAL_CREDIT, OPERATION_ROUTE_CASHIN_REVERSAL_DEBITCash-out (4): OPERATION_ROUTE_CASHOUT_CREDIT_EXTERNAL, OPERATION_ROUTE_CASHOUT_CREDIT_REVERSAL, OPERATION_ROUTE_CASHOUT_DEBIT, OPERATION_ROUTE_CASHOUT_DEBIT_REVERSAL_EXTERNAL

Jobs and limits

Notifications

Optional end-customer notifications for Pix events. Leave the provider blocks unset to disable that channel.

CRM

Runtime configuration (systemplane)

This rail mounts the systemplane admin API on its main port, gated by SYSTEMPLANE_ENABLED. When enabled, the service exposes an authenticated plane for reading and writing runtime configuration. See Systemplane for the API, namespaces, and required permissions.

Health and readiness

The rail exposes GET /health (liveness) and GET /readyz (readiness) on the main port, plus /metrics and /version. When you enable multi-tenancy (MULTI_TENANT_ENABLED=true), the rail adds an auth-gated per-tenant probe at GET /readyz/tenant/{id}. See Health and readiness for the response shape and startup/drain behavior.