Overview

Configuration in Payment Reconciler falls into two categories:

Category	Where	Purpose
Tenant settings	`PATCH /tenants/:id/settings`	Per-environment behavior: matching, locale, jobs, LedgerMatch, cache
Resource config	`POST /webhooks`, `POST /data-sources`	Webhook endpoints and data source connections

All tenant settings are scoped to tenant and environment. Include X-Tenant-Id and X-Environment when updating settings.

Tenant settings

Tenant settings control how the system behaves for a given tenant and environment. They are stored as JSON and updated via PATCH /tenants/:id/settings. Nested structures:

Nested config	Purpose
Tenant Settings	Top-level attributes and nested structure
Locale Preferences	Locale, timezone, currency, date/number format—used by field mappings
Job Scheduling	Cron schedules (matching, Stripe sync), retention
LedgerMatch Preferences	REST vs gRPC, timeout, retries
Cache Preferences	Enable/disable match and expected caches

Resource config

Resource	Purpose
Webhook Config	URL, events, retry policy, signature verification
Data Source Config	Stripe, CSV, EBICS connection parameters

Webhooks and data sources are created via their respective APIs. They are scoped to tenant and environment.

Next steps

Tenant Settings — Full attribute reference
Tenants — How to configure settings in practice