Skip to main content
Configuration covers everything that shapes how ReconLayer interprets your data and who can act on it. In the dashboard this spans two areas: the Configuration page (file mappings, canonical fields, data sources) and the Settings page (organization details, workspace access, and user preferences). Both are thin layers over API resources that you can also manage directly.
The dashboard is one consumer of the API. Reconciliation rules, organization settings, member access, and user preferences are all available via dedicated endpoints, so you can manage configuration as code if you prefer.

​
Configuration page

The page header reads “Configuration” with the description “Business setup for imports, canonical data, and source connectivity.” A warning banner explains the current scope:
Launch scope is limited to import mappings, canonical fields, and source connectivity. Advanced reconciliation rule controls stay hidden until the backend rule engine is fully enabled.
Three tabs are available:

​
File mappings

This tab lists your organization’s import profiles — the field mappings that turn uploaded files into canonical PaymentIntent or FlowLeg records, loaded via List import profiles (GET /v1/import-profiles). Each profile shows:
  • Its name and sourceType
  • The number of fields mapped
  • An active/inactive badge
  • Its field mappings as sourceColumn -> targetField pairs
Selecting a profile (if you have config_edit) opens an editor where you can change its field mappings, source type, and active status. Saving calls Update an import profile (PATCH /v1/import-profiles/{importProfileId}), and a profile can be removed via Delete an import profile. The New import profile action (also requires config_edit) creates a profile via Create an import profile (POST /v1/import-profiles).
Prefer deterministic keys for mappings — external reference, provider transfer ID, beneficiary account, and transaction hash — whenever your source files include them. These are the fields the matching engine relies on most.

​
Canonical fields

A reference view of the canonical fields that import profiles map into, loaded via List canonical fields (GET /v1/canonical-fields). Examples include:
Canonical fieldBelongs to
externalReferencePaymentIntent
sourceAmountPaymentIntent
destinationAmountPaymentIntent
providerTransferIdFlowLeg
txHashFlowLeg
beneficiaryAccountPaymentIntent
This tab is read-only — it exists so operators building or reviewing an import profile know which target fields are available.

​
Data sources

Lists the integrations connected to your organization (for example a PSP like Bridge, an on-chain provider, or a bank statement source), loaded via the integrations API. Selecting Add a data source (requires config_edit) opens a picker backed by Get integration catalog, followed by a connection form. Depending on the provider, connecting a source calls either the generic integration creation endpoint or, for Bridge specifically, the dedicated Bridge integration endpoint (Create a Bridge integration).

​
Reconciliation rules

A Reconciliation Rule controls how the matching engine evaluates a PaymentIntent against incoming evidence — amount tolerances, time windows, and SLA thresholds. Rules are managed entirely through the API: A rule can target a specific combination of paymentType and sourceType, just paymentType, just sourceType, or serve as the organization default — resolved in that priority order (most specific first). Each rule defines:
  • amountTolerance — allowed amount difference for a match
  • timeWindowMinutes — maximum time gap between expected and observed activity
  • expectedCompletionMinutes — expected end-to-end duration for the route
  • delayedSettlementThresholdMinutes
  • sourceSlaMinutes
  • intermediaryInSlaMinutes
  • transferSlaMinutes
  • intermediaryOutSlaMinutes
  • destinationSlaMinutes
  • allowProviderIdMatch
  • allowTxHashMatch
  • allowReferenceExactMatch
  • allowAmountAndTimeWindowMatch
  • requireAllRequiredLegs
A dedicated rule-editing screen exists in the dashboard’s codebase but is currently hidden behind a launch-scope flag while the backend rule engine is finished. Until it is enabled, manage reconciliation rules through the API endpoints above. Changing a rule re-evaluates matching for affected open cases.

​
Settings page

The Settings page (“Account, login, organization, and workspace preferences for signed-in users”) covers identity-and-org-level configuration. It has five tabs: General, Access, Notifications, Members, and Preferences.

​
General — organization settings

Backed by Get organization settings and Update organization settings: 
GET /v1/organization-settings
PATCH /v1/organization-settings
The form covers:
FieldDescription
nameOrganization display name
descriptionFree-text description
regionOperating region
currencyDefault currency (USD, EUR, GBP, MXN, BRL)
slaProfileDefault SLA profile applied where a rule does not override it
retentionData retention period (1, 3, 5, 7, or 10 years)
Changes require the settings_general permission.

​
Access — identity and login

When Clerk-based identity is enabled, this tab shows your login details: primary email, organization, account creation date, and last successful login. MFA and passkey status are displayed, though enabling them currently requires a Clerk plan upgrade and the controls are disabled with an explanatory note.

​
Members — workspace access and roles

Backed by the member access API: There are three roles:
RoleWho it’s for
adminFull access (locked — permissions cannot be edited)
operationsOperators who triage cases, run imports, and manage configuration
read_onlyAuditors, support, or leadership who need visibility without write access
Each role maps to a set of permissions grouped as follows:
Permission groupPermissions
Overview and casesoverview_view, cases_view, cases_action, cases_export
Importsimports_view, imports_upload, imports_review
Configurationconfig_view, config_edit
Developerdeveloper_view, webhooks_manage, api_keys_manage, logs_view
Audit and settingsaudit_view, settings_general, settings_notifications
Members and rolesmembers_invite, members_manage
Admins have every permission. Operations and read-only roles have an explicit true/false for each permission, editable (for non-locked roles) through the Manage roles modal, which calls Update workspace role permissions.
Several actions on this tab — inviting members, syncing members from Clerk, and changing roles — require a signed-in user with members_invite or members_manage, not an API key.

​
Preferences — per-user settings

Backed by Get user preferences and Update user preferences: 
GET /v1/user-preferences/{userId}
PATCH /v1/user-preferences/{userId}
Currently this controls UI-level preferences such as font size, persisted per signed-in user.

​
Notifications

Configures queue alerts, security alerts, product updates, and a weekly digest. This tab is currently marked as coming soon in the dashboard.

​
From here

List import profiles

Manage import mappings programmatically.

List reconciliation rules

Read and adjust matching tolerances and SLA thresholds.

Get organization settings

Read or update organization-level configuration.

List workspace roles and member access assignments

Manage who can access the workspace and what they can do.