Configuration Items

Tenant configuration items are key-value pairs that control how the Eclipse platform behaves for a specific tenant — payment thresholds, feature flags, integration credentials, KYC settings, and more. They can be managed directly from the Admin Portal.

Accessing Configuration Items

Navigate to the tenant sidebar → Configuration.

The configuration screen lists all config items currently defined for this tenant. Items are displayed as a searchable, paginated table.

Configuration Table Columns

Column	Description
Key	The configuration key name (e.g., `payment.enabled`, `kyc.provider`)
Value	The current value — sensitive values are masked
Description	Human-readable description of what this key controls

Searching Configuration Items

Use the search bar at the top of the table to filter by key name. Type any part of the key to narrow results.

Creating a Configuration Item

Click + Add Config Item.
Enter the key name — must match a key recognised by Eclipse (refer to the Tenant Config Reference for all supported keys).
Enter the value.
Click Save.

For keys that hold credentials, API keys, or other secrets, prefix the value with Encrypt: to instruct Eclipse to store the value encrypted at rest. For example: Encrypt:my-secret-api-key.

Editing a Configuration Item

Click the Edit icon on the config item row.
Update the value in the dialog.
Click Save.

Changes take effect immediately — no restart or re-deployment is required.

Deleting a Configuration Item

Click the Delete icon on the row.
Confirm deletion.

Deleted config items revert to the global or institution-level default for that key. If no default exists, the feature or integration controlled by that key will be disabled.

Encrypted Values

Config items prefixed with Encrypt: are stored encrypted in the uk_arch.property table using platform-managed encryption. When displayed in the portal, encrypted values are masked. You can re-set an encrypted value but cannot read the current plaintext from the portal UI — use the API if programmatic access is needed.

Common Configuration Keys

The following keys are frequently used. See the full Tenant Config Reference for the complete list.

Key	Description
`payment.enabled`	Enable or disable all payment processing for the tenant (`true`/`false`)
`kyc.provider`	KYC provider identifier
`callbackUrl`	Webhook URL for transaction notifications
`HMACOutboundSignatureKey`	Secret key for signing outbound webhook payloads
`cardIssuer`	Card issuer identifier for card operations
`sms.gateway`	SMS provider for customer notifications
`email.gateway`	Email provider for customer notifications
`maxTransactionAmount`	Maximum single transaction amount in minor units
`dailyWithdrawalLimit`	Daily withdrawal limit per wallet in minor units

Config Inheritance

Eclipse uses a three-tier configuration hierarchy:

Global — Platform-wide defaults set by EFT Corporation
Institution — Institution-level overrides (if applicable)
Tenant — Tenant-specific values (set here)

Tenant-level values always take precedence over institution and global defaults for that tenant. If a key is not set at the tenant level, the institution or global value is used.

Notes

Some keys require a specific format (e.g., comma-separated lists, JSON objects, or numeric values). Refer to the Tenant Config Reference for validation rules.
Incorrect values for certain keys (e.g., setting payment.enabled to a non-boolean) will cause the platform to use the default value, not the incorrectly-typed value. Always verify key formats before saving.
Use the Debug Agent for diagnosing issues caused by misconfigured keys.