Skip to main content

​
Security, privacy and controls

Control areaDesign approach
Identity and accessOAuth 2.0 for external clients, OIDC for interactive users, mTLS for trusted server-to-server channels, role and entitlement checks on every business action.
Segregation of dutiesFour-eyes approval for sensitive operations such as pricing changes, mandate updates, limit overrides and product activation.
Data protectionEncryption in transit and at rest, field-level masking for sensitive attributes, managed key rotation and access logging.
AuditabilityImmutable business and technical audit trails with trace identifiers, actor identity, reason codes and before/after states.
Resilience controlsIdempotent write APIs, retry-safe asynchronous workflows, circuit breakers, queue-based decoupling and replayable events.
Jurisdiction supportConfigurable regulatory attributes, retention policies and reporting extracts for EU and local market obligations without hardcoding a single country-specific rule pack.
Finpace assumes a zero-trust posture between channels, services and external integrations. External clients authenticate through the gateway. Internal service-to-service traffic is authenticated and authorized through workload identity or mTLS policies depending on the deployment standard. Sensitive actions such as mandate amendment, limit override, pricing changes and data corrections are routed through approval workflows and recorded as compliance events.

​
Event model and operational evidence

Every material state change may emit a business event. Events are used for notification triggers, integration propagation, analytics and operational monitoring. Typical event families include:
  • customer-profile-updated
  • agreement-created
  • account-opened
  • mandate-changed
  • overdraft-limit-amended
  • loan-application-status-changed
  • credit-decision-completed
  • facility-drawdown-booked
  • hardship-request-submitted
  • service-request-status-changed
  • notification-delivery-updated
Events are immutable. Replays are supported through retained event streams and versioned schemas. Downstream consumers must treat events as integration facts rather than as commands.