# Agent UI
Source: https://docs.finpace.tech/ai/agent-ui

White-label AI interaction layer for customers and staff.

# Agent UI

## Role

Agent UI is the conversational and adaptive interaction layer that can sit in:

* mobile banking
* online banking
* RM workbench
* assisted-service flows

## Customer-facing patterns

* explain balances and transactions
* help navigate account features
* collect structured onboarding data
* guide users through lending applications
* surface relevant actions and reminders
* show experiment-aware messaging and offers

## Staff-facing patterns

* summarize customer context
* draft servicing responses
* highlight pending approvals
* retrieve policy-relevant facts
* prepare case notes and handoff summaries
* assemble workbench context for assisted service

## Protected action boundary

Protected actions such as payment release, signatory change, limit increase, pricing override, or credit approval route through:

* entitlement checks
* policy evaluation
* approval profile
* authoritative core execution

## UX rule

Every AI-generated recommendation shown in Agent UI indicates:

* whether it is informational
* whether it is a draft
* whether it requires approval
* which action will happen next if confirmed


# AI runtime overview
Source: https://docs.finpace.tech/ai/ai-runtime-overview

How Finpace embeds AI into banking safely.

# AI runtime overview

Finpace public positioning presents AI as part of the operating core, not as a chatbot bolted onto the edge.

This documentation therefore models the AI runtime as a **governed execution layer** with five parts:

1. **Agent UI** for customer and staff interaction
2. **MCP gateway** for safe tool exposure
3. **AI Shield** for perimeter and policy enforcement
4. **Policy engine** for action evaluation
5. **AI audit store** for evidence and traceability

## AI design principles

### Assist before acting

AI can summarize, propose, draft, explain, and route before it executes a protected action.

### Tools, not raw system access

AI agents receive task-scoped tools such as:

* retrieve arrangement summary
* draft customer message
* prepare payment instruction
* request covenant waiver review
* summarize application documents

### Policies precede execution

Every state-changing AI call is evaluated for:

* entitlement
* consent
* approval requirement
* product and jurisdiction rule
* risk score
* tool safety profile

### Evidence is mandatory

Each AI-assisted action writes:

* prompt or request context hash
* tool selection
* policy evaluation result
* approvals obtained
* final business outcome


# AI Shield
Source: https://docs.finpace.tech/ai/ai-shield

Policy, risk, and perimeter controls for partner and agent interactions.

# AI Shield

## Core role

AI Shield is the control and protection layer around AI and partner interactions.

It evaluates:

* who is acting
* what tool they want to use
* which customer or arrangement is affected
* whether consent exists
* whether the action is allowed in the current jurisdiction
* whether the action is allowed, challenged, approval-gated, or blocked

## Typical AI Shield outcomes

* `allow`
* `allow_with_redaction`
* `allow_with_approval`
* `challenge`
* `block`

## Example controls

### Data minimization

A customer service assistant can retrieve an account summary but not full document archives.

### Action restriction

An AI assistant can prepare a payment but cannot release it without approval.

### Jurisdiction gate

A tool can be available in one geography and blocked in another due to local rules.

### Risk-based challenge

High-risk requests can require step-up authentication or human review.

## Evidence model

AI Shield decisions are queryable by:

* tool
* actor
* policy pack
* outcome
* affected business object
* time window


# Governed actions and approval controls
Source: https://docs.finpace.tech/ai/governed-actions-and-approval-controls

How AI-assisted actions are evaluated, staged, and executed.

# Governed actions and approval controls

## Action classes

### Informational

No state change.
Examples:

* explain a fee
* summarize a statement
* list missing documents

### Preparatory

Creates a draft or proposal.
Examples:

* draft customer message
* prepare payment instruction
* draft credit memo

### Protected

May change customer, arrangement, or facility state.
Examples:

* update signatory
* release payment
* approve offer
* waive covenant breach
* grant forbearance

## Protected action sequence

```text theme={null}
User or agent request
  -> tool selection
  -> policy evaluation
  -> entitlement check
  -> approval rule lookup
  -> draft command created
  -> approver action if required
  -> core execution
  -> event emitted
  -> evidence recorded
```

## Approval design requirements

Protected action docs state:

* approval trigger
* number of approvers
* approval level source
* maximum authority
* escalation path
* expiry rule
* cancellation rule

## Why this matters

Banks can tolerate AI-assisted work.
They do not tolerate undocumented control leakage.


# MCP gateway
Source: https://docs.finpace.tech/ai/mcp-gateway

Perimeter abstraction for AI and partner access.

# MCP gateway

## Purpose

Finpace MCP is the **controlled boundary** between:

* internal banking services
* external partners
* AI agents
* white-label AI interfaces

Its job is to expose the right tools and data **without exposing core APIs directly**.

## Responsibilities

* tool publication and cataloging
* credential isolation
* tenant and partner segmentation
* request normalization
* rate limiting
* policy hooks
* audit correlation

## Tool design pattern

A tool represents a business-safe action.

Good examples:

* `get_customer_overview`
* `list_open_tasks`
* `prepare_payment_for_approval`
* `summarize_credit_application`
* `request_missing_document`

Bad examples:

* `run_any_sql`
* `patch_any_customer_record`
* `override_limit_without_control`

## Isolation model

The documentation assumes:

* separate partner contexts
* separate service principals
* explicit capability grants
* logging by tool, partner, and tenant
* policy packs attached per integration


# Model governance and audit
Source: https://docs.finpace.tech/ai/model-governance-and-audit

AI evidence, explainability, retention, and operational governance.

# Model governance and audit

## Governance domains

* model registry
* prompt and policy versioning
* tool publication approval
* retrieval source control
* output monitoring
* red-team and abuse testing
* operational incident review

## Minimum evidence for AI-assisted state change

* request id
* actor and channel
* tool called
* model or workflow version
* retrieval sources used
* policy decision
* approvers
* final system command
* resulting business object changes

## Retention expectations

Institutions can configure:

* retention by event type
* masking of sensitive prompt fragments
* export for audit
* legal hold
* purge behavior after expiry

## Explainability posture

For regulated actions, the documentation uses:

* rule and policy explainability
* explicit business reasons
* source-attributed summaries
* structured decision evidence

The documentation avoids implying that raw model confidence is an acceptable regulatory explanation.


# Create account application
Source: https://docs.finpace.tech/api-reference/accounts/create-account-application

/reference/openapi.yaml post /account-applications



# Create account arrangement
Source: https://docs.finpace.tech/api-reference/accounts/create-account-arrangement

/reference/openapi.yaml post /accounts
Open arrangement from product and customer context.



# Create direct debit mandate
Source: https://docs.finpace.tech/api-reference/accounts/create-direct-debit-mandate

/reference/openapi.yaml post /accounts/{arrangementId}/direct-debit-mandates



# Create signatory
Source: https://docs.finpace.tech/api-reference/accounts/create-signatory

/reference/openapi.yaml post /accounts/{arrangementId}/signatories



# Create standing order
Source: https://docs.finpace.tech/api-reference/accounts/create-standing-order

/reference/openapi.yaml post /accounts/{arrangementId}/standing-orders



# Get account application
Source: https://docs.finpace.tech/api-reference/accounts/get-account-application

/reference/openapi.yaml get /account-applications/{applicationId}



# Get account arrangement
Source: https://docs.finpace.tech/api-reference/accounts/get-account-arrangement

/reference/openapi.yaml get /accounts/{arrangementId}



# List account applications
Source: https://docs.finpace.tech/api-reference/accounts/list-account-applications

/reference/openapi.yaml get /account-applications



# List accounts
Source: https://docs.finpace.tech/api-reference/accounts/list-accounts

/reference/openapi.yaml get /accounts



# List direct debit mandates
Source: https://docs.finpace.tech/api-reference/accounts/list-direct-debit-mandates

/reference/openapi.yaml get /accounts/{arrangementId}/direct-debit-mandates



# List signatories
Source: https://docs.finpace.tech/api-reference/accounts/list-signatories

/reference/openapi.yaml get /accounts/{arrangementId}/signatories



# List standing orders
Source: https://docs.finpace.tech/api-reference/accounts/list-standing-orders

/reference/openapi.yaml get /accounts/{arrangementId}/standing-orders



# Create customer agreement
Source: https://docs.finpace.tech/api-reference/agreements/create-customer-agreement

/reference/openapi.yaml post /customer-agreements
Create agreement across account, loan, overdraft, or service.



# Get customer agreement
Source: https://docs.finpace.tech/api-reference/agreements/get-customer-agreement

/reference/openapi.yaml get /customer-agreements/{agreementId}



# List customer agreements
Source: https://docs.finpace.tech/api-reference/agreements/list-customer-agreements

/reference/openapi.yaml get /customer-agreements



# Create AI assist session
Source: https://docs.finpace.tech/api-reference/ai-runtime/create-ai-assist-session

/reference/openapi.yaml post /ai/assist/sessions
Create governed AI session.



# Evaluate AI policy
Source: https://docs.finpace.tech/api-reference/ai-runtime/evaluate-ai-policy

/reference/openapi.yaml post /ai/policies/evaluate
Evaluate policy for requested tool or action.



# Execute governed AI tool
Source: https://docs.finpace.tech/api-reference/ai-runtime/execute-governed-ai-tool

/reference/openapi.yaml post /ai/tools/execute
Execute policy-approved AI tool.



# List AI assist sessions
Source: https://docs.finpace.tech/api-reference/ai-runtime/list-ai-assist-sessions

/reference/openapi.yaml get /ai/assist/sessions



# List AI audit events
Source: https://docs.finpace.tech/api-reference/ai-runtime/list-ai-audit-events

/reference/openapi.yaml get /ai/audit/events



# List AI session messages
Source: https://docs.finpace.tech/api-reference/ai-runtime/list-ai-session-messages

/reference/openapi.yaml get /ai/assist/sessions/{sessionId}/messages



# Send AI session message
Source: https://docs.finpace.tech/api-reference/ai-runtime/send-ai-session-message

/reference/openapi.yaml post /ai/assist/sessions/{sessionId}/messages



# Create posting instruction
Source: https://docs.finpace.tech/api-reference/balances/create-posting-instruction

/reference/openapi.yaml post /posting-instructions



# Get balances
Source: https://docs.finpace.tech/api-reference/balances/get-balances

/reference/openapi.yaml get /accounts/{arrangementId}/balances



# Get posting instruction
Source: https://docs.finpace.tech/api-reference/balances/get-posting-instruction

/reference/openapi.yaml get /posting-instructions/{instructionId}



# List fee runs
Source: https://docs.finpace.tech/api-reference/balances/list-fee-runs

/reference/openapi.yaml get /fee-runs



# List interest runs
Source: https://docs.finpace.tech/api-reference/balances/list-interest-runs

/reference/openapi.yaml get /interest-runs



# List posting instructions
Source: https://docs.finpace.tech/api-reference/balances/list-posting-instructions

/reference/openapi.yaml get /posting-instructions



# List transactions
Source: https://docs.finpace.tech/api-reference/balances/list-transactions

/reference/openapi.yaml get /accounts/{arrangementId}/transactions



# Create campaign
Source: https://docs.finpace.tech/api-reference/campaigns/create-campaign

/reference/openapi.yaml post /campaigns
Create campaign with targeting and approval metadata.



# Create experiment
Source: https://docs.finpace.tech/api-reference/campaigns/create-experiment

/reference/openapi.yaml post /experiments
Create controlled A/B experiment for product, pricing, or messaging.



# Get campaign
Source: https://docs.finpace.tech/api-reference/campaigns/get-campaign

/reference/openapi.yaml get /campaigns/{campaignId}



# Get experiment
Source: https://docs.finpace.tech/api-reference/campaigns/get-experiment

/reference/openapi.yaml get /experiments/{experimentId}



# List campaigns
Source: https://docs.finpace.tech/api-reference/campaigns/list-campaigns

/reference/openapi.yaml get /campaigns



# List experiment assignments
Source: https://docs.finpace.tech/api-reference/campaigns/list-experiment-assignments

/reference/openapi.yaml get /experiments/{experimentId}/assignments



# List experiment variants
Source: https://docs.finpace.tech/api-reference/campaigns/list-experiment-variants

/reference/openapi.yaml get /experiments/{experimentId}/variants



# List experiments
Source: https://docs.finpace.tech/api-reference/campaigns/list-experiments

/reference/openapi.yaml get /experiments



# Create case
Source: https://docs.finpace.tech/api-reference/cases/create-case

/reference/openapi.yaml post /cases
Create service, dispute, or operational case.



# Create task for case
Source: https://docs.finpace.tech/api-reference/cases/create-task-for-case

/reference/openapi.yaml post /cases/{caseId}/tasks



# Get case
Source: https://docs.finpace.tech/api-reference/cases/get-case

/reference/openapi.yaml get /cases/{caseId}



# List cases
Source: https://docs.finpace.tech/api-reference/cases/list-cases

/reference/openapi.yaml get /cases



# List tasks for case
Source: https://docs.finpace.tech/api-reference/cases/list-tasks-for-case

/reference/openapi.yaml get /cases/{caseId}/tasks



# Create availability window
Source: https://docs.finpace.tech/api-reference/channels/create-availability-window

/reference/openapi.yaml post /channels/availability-windows



# Create channel feature flag
Source: https://docs.finpace.tech/api-reference/channels/create-channel-feature-flag

/reference/openapi.yaml post /channels/feature-flags



# Create channel session
Source: https://docs.finpace.tech/api-reference/channels/create-channel-session

/reference/openapi.yaml post /channels/sessions
Create omnichannel session context.



# Get channel session
Source: https://docs.finpace.tech/api-reference/channels/get-channel-session

/reference/openapi.yaml get /channels/sessions/{sessionId}



# List channel availability windows
Source: https://docs.finpace.tech/api-reference/channels/list-channel-availability-windows

/reference/openapi.yaml get /channels/availability-windows



# List channel feature flags
Source: https://docs.finpace.tech/api-reference/channels/list-channel-feature-flags

/reference/openapi.yaml get /channels/feature-flags



# List channel sessions
Source: https://docs.finpace.tech/api-reference/channels/list-channel-sessions

/reference/openapi.yaml get /channels/sessions



# Create collateral
Source: https://docs.finpace.tech/api-reference/collateral/create-collateral

/reference/openapi.yaml post /collateral
Create collateral record with owner and valuation context.



# Create collateral link
Source: https://docs.finpace.tech/api-reference/collateral/create-collateral-link

/reference/openapi.yaml post /facilities/{facilityId}/collateral-links



# Create condition precedent
Source: https://docs.finpace.tech/api-reference/collateral/create-condition-precedent

/reference/openapi.yaml post /facilities/{facilityId}/conditions



# Create covenant
Source: https://docs.finpace.tech/api-reference/collateral/create-covenant

/reference/openapi.yaml post /facilities/{facilityId}/covenants
Create covenant with thresholds and monitoring rules.



# Create covenant breach
Source: https://docs.finpace.tech/api-reference/collateral/create-covenant-breach

/reference/openapi.yaml post /covenant-breaches



# Get collateral
Source: https://docs.finpace.tech/api-reference/collateral/get-collateral

/reference/openapi.yaml get /collateral/{collateralId}



# List collateral links
Source: https://docs.finpace.tech/api-reference/collateral/list-collateral-links

/reference/openapi.yaml get /facilities/{facilityId}/collateral-links



# List collateral records
Source: https://docs.finpace.tech/api-reference/collateral/list-collateral-records

/reference/openapi.yaml get /collateral



# List conditions precedent
Source: https://docs.finpace.tech/api-reference/collateral/list-conditions-precedent

/reference/openapi.yaml get /facilities/{facilityId}/conditions



# List covenant breaches
Source: https://docs.finpace.tech/api-reference/collateral/list-covenant-breaches

/reference/openapi.yaml get /covenant-breaches



# List covenants
Source: https://docs.finpace.tech/api-reference/collateral/list-covenants

/reference/openapi.yaml get /facilities/{facilityId}/covenants



# Waive covenant breach
Source: https://docs.finpace.tech/api-reference/collateral/waive-covenant-breach

/reference/openapi.yaml post /covenant-breaches/{breachId}/waive



# Create customer
Source: https://docs.finpace.tech/api-reference/customers/create-customer

/reference/openapi.yaml post /customers
Create customer from party and segment attributes.



# Get customer
Source: https://docs.finpace.tech/api-reference/customers/get-customer

/reference/openapi.yaml get /customers/{customerId}



# List customer consents
Source: https://docs.finpace.tech/api-reference/customers/list-customer-consents

/reference/openapi.yaml get /customers/{customerId}/consents



# List customers
Source: https://docs.finpace.tech/api-reference/customers/list-customers

/reference/openapi.yaml get /customers



# Create document
Source: https://docs.finpace.tech/api-reference/documents/create-document

/reference/openapi.yaml post /documents
Register uploaded or generated document.



# Get document
Source: https://docs.finpace.tech/api-reference/documents/get-document

/reference/openapi.yaml get /documents/{documentId}



# List documents
Source: https://docs.finpace.tech/api-reference/documents/list-documents

/reference/openapi.yaml get /documents



# Create entitlement
Source: https://docs.finpace.tech/api-reference/entitlements/create-entitlement

/reference/openapi.yaml post /entitlements
Create action-level entitlement.



# Get entitlement
Source: https://docs.finpace.tech/api-reference/entitlements/get-entitlement

/reference/openapi.yaml get /entitlements/{entitlementId}



# List entitlements
Source: https://docs.finpace.tech/api-reference/entitlements/list-entitlements

/reference/openapi.yaml get /entitlements



# Create event subscription
Source: https://docs.finpace.tech/api-reference/events/create-event-subscription

/reference/openapi.yaml post /events/subscriptions
Subscribe to business events.



# List event subscriptions
Source: https://docs.finpace.tech/api-reference/events/list-event-subscriptions

/reference/openapi.yaml get /events/subscriptions



# Create interaction event
Source: https://docs.finpace.tech/api-reference/interactions/create-interaction-event

/reference/openapi.yaml post /interaction-events
Write inbound or outbound interaction evidence.



# Create routing profile
Source: https://docs.finpace.tech/api-reference/interactions/create-routing-profile

/reference/openapi.yaml post /routing-profiles
Create contact-center or RM routing profile.



# Get customer workbench context
Source: https://docs.finpace.tech/api-reference/interactions/get-customer-workbench-context

/reference/openapi.yaml get /workbench/customer-context/{customerId}



# Get interaction event
Source: https://docs.finpace.tech/api-reference/interactions/get-interaction-event

/reference/openapi.yaml get /interaction-events/{eventId}



# Get routing profile
Source: https://docs.finpace.tech/api-reference/interactions/get-routing-profile

/reference/openapi.yaml get /routing-profiles/{routingProfileId}



# List interaction events
Source: https://docs.finpace.tech/api-reference/interactions/list-interaction-events

/reference/openapi.yaml get /interaction-events



# List routing profiles
Source: https://docs.finpace.tech/api-reference/interactions/list-routing-profiles

/reference/openapi.yaml get /routing-profiles



# Create affordability assessment
Source: https://docs.finpace.tech/api-reference/lending/create-affordability-assessment

/reference/openapi.yaml post /affordability-assessments
Run or persist affordability assessment.



# Create credit application
Source: https://docs.finpace.tech/api-reference/lending/create-credit-application

/reference/openapi.yaml post /credit-applications
Create SME or consumer lending application.



# Create decision package
Source: https://docs.finpace.tech/api-reference/lending/create-decision-package

/reference/openapi.yaml post /decision-packages
Create decision package from scoring, bureau, and policy results.



# Create drawdown
Source: https://docs.finpace.tech/api-reference/lending/create-drawdown

/reference/openapi.yaml post /facilities/{facilityId}/drawdowns



# Create extra payment request
Source: https://docs.finpace.tech/api-reference/lending/create-extra-payment-request

/reference/openapi.yaml post /facilities/{facilityId}/extra-payments



# Create facility
Source: https://docs.finpace.tech/api-reference/lending/create-facility

/reference/openapi.yaml post /facilities
Create facility after accepted offer.



# Create forbearance action
Source: https://docs.finpace.tech/api-reference/lending/create-forbearance-action

/reference/openapi.yaml post /facilities/{facilityId}/forbearance



# Create payment holiday
Source: https://docs.finpace.tech/api-reference/lending/create-payment-holiday

/reference/openapi.yaml post /facilities/{facilityId}/payment-holidays



# Create reschedule
Source: https://docs.finpace.tech/api-reference/lending/create-reschedule

/reference/openapi.yaml post /facilities/{facilityId}/reschedules



# Generate credit offer
Source: https://docs.finpace.tech/api-reference/lending/generate-credit-offer

/reference/openapi.yaml post /credit-applications/{applicationId}/offer



# Get affordability assessment
Source: https://docs.finpace.tech/api-reference/lending/get-affordability-assessment

/reference/openapi.yaml get /affordability-assessments/{assessmentId}



# Get credit application
Source: https://docs.finpace.tech/api-reference/lending/get-credit-application

/reference/openapi.yaml get /credit-applications/{applicationId}



# Get decision package
Source: https://docs.finpace.tech/api-reference/lending/get-decision-package

/reference/openapi.yaml get /decision-packages/{decisionPackageId}



# Get facility
Source: https://docs.finpace.tech/api-reference/lending/get-facility

/reference/openapi.yaml get /facilities/{facilityId}



# List affordability assessments
Source: https://docs.finpace.tech/api-reference/lending/list-affordability-assessments

/reference/openapi.yaml get /affordability-assessments



# List credit applications
Source: https://docs.finpace.tech/api-reference/lending/list-credit-applications

/reference/openapi.yaml get /credit-applications



# List decision packages
Source: https://docs.finpace.tech/api-reference/lending/list-decision-packages

/reference/openapi.yaml get /decision-packages



# List drawdowns
Source: https://docs.finpace.tech/api-reference/lending/list-drawdowns

/reference/openapi.yaml get /facilities/{facilityId}/drawdowns



# List facilities
Source: https://docs.finpace.tech/api-reference/lending/list-facilities

/reference/openapi.yaml get /facilities



# List forbearance actions
Source: https://docs.finpace.tech/api-reference/lending/list-forbearance-actions

/reference/openapi.yaml get /facilities/{facilityId}/forbearance



# List payment holidays
Source: https://docs.finpace.tech/api-reference/lending/list-payment-holidays

/reference/openapi.yaml get /facilities/{facilityId}/payment-holidays



# List reschedules
Source: https://docs.finpace.tech/api-reference/lending/list-reschedules

/reference/openapi.yaml get /facilities/{facilityId}/reschedules



# Receive decision callback
Source: https://docs.finpace.tech/api-reference/lending/receive-decision-callback

/reference/openapi.yaml post /decision-packages/{decisionPackageId}/callback



# Record decision for credit application
Source: https://docs.finpace.tech/api-reference/lending/record-decision-for-credit-application

/reference/openapi.yaml post /credit-applications/{applicationId}/decision



# Submit credit application
Source: https://docs.finpace.tech/api-reference/lending/submit-credit-application

/reference/openapi.yaml post /credit-applications/{applicationId}/submit



# Add liquidity pool member
Source: https://docs.finpace.tech/api-reference/liquidity/add-liquidity-pool-member

/reference/openapi.yaml post /liquidity-pools/{poolId}/members



# Create liquidity pool
Source: https://docs.finpace.tech/api-reference/liquidity/create-liquidity-pool

/reference/openapi.yaml post /liquidity-pools
Create notional or physical liquidity pool.



# Create sweep instruction
Source: https://docs.finpace.tech/api-reference/liquidity/create-sweep-instruction

/reference/openapi.yaml post /liquidity-sweeps
Create target-balancing or sweep instruction.



# Get liquidity pool
Source: https://docs.finpace.tech/api-reference/liquidity/get-liquidity-pool

/reference/openapi.yaml get /liquidity-pools/{poolId}



# Get sweep instruction
Source: https://docs.finpace.tech/api-reference/liquidity/get-sweep-instruction

/reference/openapi.yaml get /liquidity-sweeps/{sweepId}



# List liquidity pool members
Source: https://docs.finpace.tech/api-reference/liquidity/list-liquidity-pool-members

/reference/openapi.yaml get /liquidity-pools/{poolId}/members



# List liquidity pools
Source: https://docs.finpace.tech/api-reference/liquidity/list-liquidity-pools

/reference/openapi.yaml get /liquidity-pools



# List sweep instructions
Source: https://docs.finpace.tech/api-reference/liquidity/list-sweep-instructions

/reference/openapi.yaml get /liquidity-sweeps



# Create notification delivery
Source: https://docs.finpace.tech/api-reference/notifications/create-notification-delivery

/reference/openapi.yaml post /notification-deliveries



# Create notification template
Source: https://docs.finpace.tech/api-reference/notifications/create-notification-template

/reference/openapi.yaml post /notification-templates
Create template with channel, language, and approval workflow.



# Create statement request
Source: https://docs.finpace.tech/api-reference/notifications/create-statement-request

/reference/openapi.yaml post /statements



# Get notification template
Source: https://docs.finpace.tech/api-reference/notifications/get-notification-template

/reference/openapi.yaml get /notification-templates/{templateId}



# List notification deliveries
Source: https://docs.finpace.tech/api-reference/notifications/list-notification-deliveries

/reference/openapi.yaml get /notification-deliveries



# List notification templates
Source: https://docs.finpace.tech/api-reference/notifications/list-notification-templates

/reference/openapi.yaml get /notification-templates



# List statements
Source: https://docs.finpace.tech/api-reference/notifications/list-statements

/reference/openapi.yaml get /statements



# Health check
Source: https://docs.finpace.tech/api-reference/operations/health-check

/reference/openapi.yaml get /health



# Create party
Source: https://docs.finpace.tech/api-reference/parties/create-party

/reference/openapi.yaml post /parties
Create a natural person or legal entity record.



# Create party group
Source: https://docs.finpace.tech/api-reference/parties/create-party-group

/reference/openapi.yaml post /party-groups



# Get party
Source: https://docs.finpace.tech/api-reference/parties/get-party

/reference/openapi.yaml get /parties/{partyId}



# List parties
Source: https://docs.finpace.tech/api-reference/parties/list-parties

/reference/openapi.yaml get /parties



# List party groups
Source: https://docs.finpace.tech/api-reference/parties/list-party-groups

/reference/openapi.yaml get /party-groups



# Approve payment
Source: https://docs.finpace.tech/api-reference/payments/approve-payment

/reference/openapi.yaml post /payments/{paymentId}/approve



# Create payment
Source: https://docs.finpace.tech/api-reference/payments/create-payment

/reference/openapi.yaml post /payments
Initiate payment with mandate and limit checks.



# Get payment
Source: https://docs.finpace.tech/api-reference/payments/get-payment

/reference/openapi.yaml get /payments/{paymentId}



# List payments
Source: https://docs.finpace.tech/api-reference/payments/list-payments

/reference/openapi.yaml get /payments



# Reject payment
Source: https://docs.finpace.tech/api-reference/payments/reject-payment

/reference/openapi.yaml post /payments/{paymentId}/reject



# Create pricing quotation
Source: https://docs.finpace.tech/api-reference/pricing/create-pricing-quotation

/reference/openapi.yaml post /pricing-quotations



# Create rate card
Source: https://docs.finpace.tech/api-reference/pricing/create-rate-card

/reference/openapi.yaml post /pricing-rate-cards
Create risk-, channel-, and campaign-aware rate card.



# Get rate card
Source: https://docs.finpace.tech/api-reference/pricing/get-rate-card

/reference/openapi.yaml get /pricing-rate-cards/{rateCardId}



# List pricing quotations
Source: https://docs.finpace.tech/api-reference/pricing/list-pricing-quotations

/reference/openapi.yaml get /pricing-quotations



# List rate cards
Source: https://docs.finpace.tech/api-reference/pricing/list-rate-cards

/reference/openapi.yaml get /pricing-rate-cards



# Create product
Source: https://docs.finpace.tech/api-reference/products/create-product

/reference/openapi.yaml post /product-catalog/products
Create versioned product template.



# Create product bundle
Source: https://docs.finpace.tech/api-reference/products/create-product-bundle

/reference/openapi.yaml post /product-bundles



# Create product offer
Source: https://docs.finpace.tech/api-reference/products/create-product-offer

/reference/openapi.yaml post /product-offers
Create commercial offer tied to pricing and eligibility.



# Get product
Source: https://docs.finpace.tech/api-reference/products/get-product

/reference/openapi.yaml get /product-catalog/products/{productId}



# List product bundles
Source: https://docs.finpace.tech/api-reference/products/list-product-bundles

/reference/openapi.yaml get /product-bundles



# List product offers
Source: https://docs.finpace.tech/api-reference/products/list-product-offers

/reference/openapi.yaml get /product-offers



# List product versions
Source: https://docs.finpace.tech/api-reference/products/list-product-versions

/reference/openapi.yaml get /product-catalog/products/{productId}/versions



# List products
Source: https://docs.finpace.tech/api-reference/products/list-products

/reference/openapi.yaml get /product-catalog/products



# Accounts, arrangements, and mandates
Source: https://docs.finpace.tech/domains/accounts-arrangements-and-mandates

Arrangements, balances, signatories, mandates, and lifecycle controls.

# Accounts, arrangements, and mandates

## Arrangement model

An arrangement is the contractual banking object held by the customer.

Examples:

* demand deposit account
* savings account
* overdraft-linked current account
* loan facility
* term loan
* revolving credit line

An account is the operational representation used for:

* balances
* postings
* statements
* servicing actions
* payment routing

## Lifecycle states

Typical arrangement states:

* `draft`
* `pending_review`
* `approved`
* `active`
* `restricted`
* `dormant`
* `closed`

State transitions are controlled by:

* product rules
* compliance status
* approval policies
* funding conditions
* document completion

## Signatories and mandates

For business banking, the arrangement model must support:

* single signatory
* joint signatory
* amount-tier authority
* channel-specific authority
* transaction-type restrictions
* validity periods
* revocation history

## Standing orders and direct debit mandates

These are separate controlled objects with:

* creation source
* customer authorization evidence
* schedule or mandate attributes
* status history
* cancellation reason
* amendment audit

## Why this matters to documentation

Tier-1 institutions do not want a generic “account” page.
They need to see:

* the difference between party, customer, arrangement, account, and mandate
* the lifecycle states
* who can change what
* which changes require approval


# Affordability, scoring, and decisioning
Source: https://docs.finpace.tech/domains/affordability-scoring-and-decisioning

Responsible-lending checks, score orchestration, pricing inputs, and asynchronous decisions.

# Affordability, scoring, and decisioning

## Affordability assessment

Finpace supports affordability assessment records that capture:

* declared and verified income
* recurring commitments
* debt-to-income ratio
* overcommitment indicators
* disposable-income result
* jurisdiction-specific responsible-lending checks
* supporting evidence references

## External scoring and bureau orchestration

The decisioning layer supports:

* internal scorecards
* third-party decision engines
* bureau calls
* open-banking data pulls
* fraud checks
* callback-driven delayed decisions
* manual referral queues

## Decision results

A decision result can be:

* approved
* conditionally approved
* referred
* declined
* expired

Each result records:

* decision package id
* score inputs and outputs
* pricing factors
* exception reason
* approver identity where relevant
* final offer reference

## Personalized offers

Offer generation supports:

* product comparison
* rate and fee personalization
* channel-specific terms
* expiry windows
* acceptance controls
* downstream contract creation


# Cases, documents, and tasks
Source: https://docs.finpace.tech/domains/cases-documents-and-tasks

Operational work management and document lifecycle.

# Cases, documents, and tasks

## Case model

A case is the operational wrapper for work that spans multiple steps and participants.

Examples:

* onboarding review
* payment repair
* lending exception
* covenant breach remediation
* customer complaint
* fraud escalation

## Task model

Tasks carry:

* assignee
* queue
* due date
* SLA clock
* related business object
* status
* completion evidence

## Document model

Documents must support:

* category and type
* source system
* version
* upload actor
* linked parties or facilities
* hash or integrity marker
* retention rule
* deletion restriction if subject to hold

## Typical task triggers

* missing document
* expired KYC
* approval pending
* payment exception
* rate reset requiring review
* covenant breach follow-up
* AI tool execution blocked by policy

## AI usage

AI may:

* classify incoming documents
* summarize a case
* draft a follow-up request
* propose routing priority

AI may not:

* delete evidence
* override retention rules
* close regulated cases without policy-approved automation


# Collateral, covenants, and conditions
Source: https://docs.finpace.tech/domains/collateral-covenants-and-conditions

Collateral records, covenant monitoring, conditions precedent, and waiver control.

# Collateral, covenants, and conditions

## Collateral model

Collateral is represented separately from the facility and supports:

* linkage to one or more facilities
* valuation history
* owner and guarantor linkage
* legal perfection tracking
* insurance evidence
* impairment, substitution, and release status
* document evidence

## Covenant model

A covenant record defines:

* covenant type
* measurement frequency
* threshold
* data source
* test logic
* grace period
* breach action
* waiver authority

## Conditions precedent and drawdown checks

The platform supports controlled checklists before initial or subsequent drawdown:

* legal documents complete
* collateral perfected
* insurance evidence present
* approvals complete
* customer representations confirmed
* covenant setup complete

## Monitoring patterns

* scheduled review
* event-driven review
* manual breach logging
* remediation plan tracking
* waiver approvals
* collateral revaluation triggers


# Customer interaction and channels
Source: https://docs.finpace.tech/domains/customer-interaction-and-channels

Omnichannel access, sessions, channel control, and assisted service.

# Customer interaction and channels

## Supported channels

* mobile banking
* web banking
* RM desktop
* contact-center desktop
* secure messaging
* email-assisted service
* partner-operated assisted channels

## Session model

A channel session consolidates:

* actor identity
* customer context
* delegated authority
* current journey
* recent account and loan events
* open service requests
* risk or challenge state
* channel capability set

## Channel controls

Operations can manage:

* channel availability windows
* maintenance windows
* feature flags
* high-risk action restrictions
* jurisdiction-specific channel policies
* device and authentication policies

## Assisted-service continuity

The same business context can move across:

* self-service
* RM-assisted flow
* contact-center flow
* AI-assisted flow

The session and interaction history preserve continuity across all of them.

## Strong authentication

The channel layer supports:

* MFA
* device binding
* step-up challenges
* delegated approval journeys
* risk-based challenge flows


# Lending origination
Source: https://docs.finpace.tech/domains/lending-origination

Applications, data collection, offers, approvals, and contract creation.

# Lending origination

## Main objects

### Credit application

The application record stores:

* borrower and related parties
* requested facility
* source channel
* product reference
* required documents
* underwriting stage
* submission status

### Underwriting package

A derived working set used for assessment:

* financial inputs
* bureau or open banking data
* fraud and KYB results
* collateral proposals
* covenant proposals
* analyst commentary
* approval conditions

### Offer

The commercial or conditional outcome of a decisioning flow.

## Supported origination patterns

* digital self-service
* RM-assisted origination
* branch-assisted capture
* partner-originated application
* pre-approved or pre-qualified flow

## Decisioning pattern

1. Capture application
2. Validate minimum data
3. Pull external signals
4. Run eligibility
5. Run credit and fraud checks
6. Produce referral or decision
7. Generate conditional or final offer
8. Route to approval if needed
9. Bind offer and create facility

## Evidence and explainability

Every decision preserves:

* input source
* rule set version
* external data provider response id
* analyst override reason
* approval chain
* resulting offer or decline rationale

## AI usage in origination

Allowed AI uses:

* summarizing application packs
* extracting information from uploaded documents
* proposing missing-information requests
* drafting credit memos for analyst review
* highlighting inconsistencies across data sources

Protected actions remain approval-aware:

* final credit approval
* collateral waiver
* covenant relaxation
* pricing override


# Lending servicing
Source: https://docs.finpace.tech/domains/lending-servicing

Drawdowns, repayments, restructures, forbearance, and servicing events.

# Lending servicing

## Servicing actions

The servicing domain supports:

* drawdown booking
* rollover
* rate reset
* repayment allocation
* fee assessment
* prepayment
* restructuring
* deferment
* forbearance
* write-off recommendation
* closure

## State model

Typical facility states:

* `approved`
* `available`
* `drawn`
* `in_repayment`
* `past_due`
* `restructured`
* `forborne`
* `written_off`
* `closed`

## Payment allocation

The allocation order is explicit.
Example:

1. past due fees
2. past due interest
3. past due principal
4. current fees
5. current interest
6. current principal

## Servicing control points

Certain actions require approval:

* restructure
* payment holiday
* rate concession
* covenant waiver
* early settlement with exception pricing
* write-off

## Customer interaction events

* payment due reminder
* missing information notice
* covenant breach notice
* maturity reminder
* rate reset notice
* forbearance acceptance


# Notifications, statements, and correspondence
Source: https://docs.finpace.tech/domains/notifications-statements-and-correspondence

Outbound communication, templates, delivery events, and statement generation.

# Notifications, statements, and correspondence

## Communication types

* transactional alert
* servicing notice
* approval request
* document request
* statement
* facility letter
* overdue reminder
* regulatory notice
* campaign or offer communication

## Delivery channels

* in-app inbox
* email
* SMS
* push notification
* webhook to enterprise middleware
* printable correspondence package

## Template design rules

Templates support:

* role-specific content
* jurisdiction-specific clauses
* language selection
* product and event variables
* approval requirements for high-impact correspondence

## Statement expectations

Statements are definable by:

* product
* frequency
* cut-off
* delivery channel
* legal disclosure pack
* correction and regeneration rules

## Delivery evidence

Every delivery event preserves:

* template version
* delivery channel
* dispatch timestamp
* success or failure outcome
* destination reference
* operator or automated trigger source


# Party and customer model
Source: https://docs.finpace.tech/domains/party-and-customer-model

Party, customer, legal entity, relationship, and consent design.

# Party and customer model

## Core objects

### Party

A party is any person or organization the platform needs to identify, evaluate, or relate to a banking arrangement.

Examples:

* natural person
* sole trader
* corporate entity
* beneficial owner
* authorized signatory
* director
* guarantor

### Customer

A customer is the banking relationship representation used by Finpace for servicing, entitlements, product ownership, risk assessment, and communications.

### Relationship

Relationships connect parties to parties and parties to arrangements.

Examples:

* `director_of`
* `beneficial_owner_of`
* `authorized_signatory_for`
* `guarantor_for`
* `parent_of_group_member`
* `relationship_manager_for`

## Design rules

* a legal entity can exist before it becomes an active customer
* one party can participate in multiple customer contexts
* relationship validity is date-effective
* every high-risk relationship can carry enhanced due diligence attributes
* consent records are separate from party master data and are versioned

## Required data clusters

### Identity and profile

* names
* registration numbers
* tax identifiers
* incorporation details
* residency and jurisdiction markers

### Risk and compliance

* PEP indicators
* sanctions screening outcomes
* customer risk rating
* KYB and KYC status
* periodic review dates

### Contact and communication

* addresses
* phones
* emails
* preferred language
* channel preferences

### Consent and preference

* marketing consent
* analytics consent
* open banking consent
* document and e-sign consent
* AI interaction consent where required by policy

## Why this matters for AI

The AI runtime never infers authority from a conversation alone.
Authority must come from:

* authenticated actor identity
* represented customer context
* relationship rights
* arrangement-level entitlements
* policy evaluation


# Payments, limits, and liquidity
Source: https://docs.finpace.tech/domains/payments-limits-and-liquidity

Payments, approvals, limits, liquidity pools, sweeps, and balance events.

# Payments, limits, and liquidity

## Payment initiation

The platform supports:

* internal transfers
* domestic credit transfers
* cross-border payments
* bulk payments
* standing order execution
* direct debit processing

## Approval controls

Payments can be:

* straight-through processed
* routed through maker-checker
* escalated for excess amount
* blocked for sanctions or risk
* released after manual review

## Limit domains

Relevant limit types include:

* arrangement limit
* signatory limit
* customer daily limit
* channel limit
* obligor and group exposure limit
* pool and sweep limit

## Liquidity structures

Liquidity management is a core capability and supports:

* intraday and end-of-day balance monitoring
* physical and notional pool definitions
* target balancing rules
* parent-child sweep structures
* pool participation rules
* sweep execution calendars
* breach alerts
* treasury integration events
* pool-level approvals and limit checks

## Events

* `payment.initiated`
* `payment.awaitingApproval`
* `payment.released`
* `payment.rejected`
* `balance.changed`
* `limit.breached`
* `liquidity.pool.updated`
* `liquidity.sweep.executed`


# Postings, balances, and ledger
Source: https://docs.finpace.tech/domains/postings-balances-and-ledger

Posting instructions, holds, balances, accounting, and reconciliation model.

# Postings, balances, and ledger

## Posting model

Finpace exposes a posting-instruction model rather than a vague transaction primitive.

A posting instruction:

* identifies source intent
* resolves value date and booking date
* checks limits and restrictions
* produces one or more customer-visible entries
* produces accounting effects
* preserves reversal lineage

## Balance model

Key balance concepts:

* current balance
* available balance
* uncleared balance
* hold amount
* overdraft headroom
* accrued interest
* pending fees

## Holds and reservations

Holds are first-class objects with:

* reason
* channel
* amount
* effective window
* release rule
* linked payment or case reference

## Ledger expectations

The documentation assumes:

* customer-facing balances are derived from authoritative postings
* accounting rules are configurable by product and event type
* reversal and correction actions preserve lineage
* operational reconciliation can trace from payment or servicing event to ledger impact

## Accounting controls

Relevant accounting objects:

* chart of accounts mapping
* product accounting rules
* accrual jobs
* fee and interest runs
* suspense and exception postings
* closing and correction journals

## Documentation rule

Never describe “transactions” in the abstract.
Always clarify:

* initiation object
* posting instruction
* customer entry
* accounting effect
* event emitted


# Pricing, campaigns, and experimentation
Source: https://docs.finpace.tech/domains/pricing-campaigns-and-experimentation

Rate cards, offer pricing, campaign orchestration, and controlled experimentation.

# Pricing, campaigns, and experimentation

## Rate-card model

Finpace supports rate cards that vary by:

* risk score band
* customer segment
* channel
* campaign
* relationship tenure
* product version
* collateral profile
* exception authority

A rate card can govern:

* nominal rate
* APR
* origination fee
* maintenance fee
* penalty fee
* early-settlement fee
* discount or waiver rules

## Pricing quotation lifecycle

A pricing quotation records:

* the source product
* the applicable rate card version
* customer and relationship factors
* derived commercial terms
* validity window
* override reason and approver when applicable

## Campaign management

Campaigns are core capabilities for:

* offer segmentation
* temporary pricing changes
* channel-specific messaging
* expiry rules
* target population definitions
* approval and publication control

## Experimentation

Controlled experimentation supports:

* product-variant testing
* pricing tests
* messaging tests
* channel-journey tests
* control-group assignment
* conversion measurement
* outcome attribution

Experiments are versioned, approved, time-bounded, and auditable.


# Product factory and offers
Source: https://docs.finpace.tech/domains/product-factory-and-offers

How products, versions, bundles, pricing, and offers are modeled.

# Product factory and offers

## Product layers

### Product definition

Defines the reusable product template.

Examples:

* current account
* notice deposit
* revolving overdraft
* SME term loan
* consumer personal loan

### Product version

A time-effective release of the product definition with frozen commercial and regulatory attributes.

### Offer

A product instance presented to a specific customer or segment, potentially with:

* personalized pricing
* promotional conditions
* channel-specific eligibility
* expiry date
* approval requirement

## Parameter domains

A Finpace product definition can carry parameters across:

* eligibility
* pricing
* fees
* interest rules
* limit rules
* repayment behavior
* statement and notice rules
* jurisdiction-specific compliance attributes
* document requirements
* servicing permissions

## Bundles

Bundles package multiple products and entitlements into a controlled commercial offer.

Example:

* SME current account
* overdraft line
* digital banking access
* pricing package
* approval matrix
* statement pack

## Governance

### Product change workflow

1. Draft
2. Review
3. Approve
4. Activate
5. Sunset

### Rules for production use

* no direct editing of active versions
* version comparison must be auditable
* downstream channels consume explicit product version references
* the API reference distinguishes draft, approved, and active product data


# Relationship workbench and interaction history
Source: https://docs.finpace.tech/domains/relationship-workbench-and-interaction-history

RM workbench, contact-center context, routing, and interaction evidence.

# Relationship workbench and interaction history

## Customer 360 workbench

The workbench surfaces:

* customer master profile
* relationship hierarchy
* accounts and balances
* loan positions and schedules
* pending approvals
* cases and tasks
* recent communications
* open pipeline items
* contextual offers and warnings

## Routing and queueing

Finpace supports routing based on:

* customer value
* assigned RM
* language
* skill profile
* service type
* urgency
* complaint or payment-risk indicators

## Interaction event history

Every interaction can be written as an event with:

* channel
* interaction type
* purpose
* outcome
* agent
* timestamp
* linked customer
* linked product or arrangement
* linked case or task
* recording or transcript reference where applicable

## CTI and screen-pop

Telephony and chat platforms can:

* perform customer lookup
* preload customer context
* open the workbench on inbound events
* attach interaction outcomes back to the customer event history


# API conventions
Source: https://docs.finpace.tech/getting-started/api-conventions

Authentication, idempotency, approvals, events, and error patterns.

# API conventions

## Authentication and authorization

All external API calls are expected to use:

* OAuth 2.0 or OIDC for delegated access
* mTLS for high-trust server integrations
* scoped bearer tokens for application access
* explicit service principals for machine-to-machine integrations

## Idempotency

The following operations must require an `Idempotency-Key` header:

* payment initiation
* account opening
* posting instruction submission
* credit application submission
* drawdown booking
* document upload registration
* AI governed tool execution for state-changing commands

A repeated request with the same semantic payload and key returns the original accepted result.

## Maker-checker and approval pattern

For protected actions, Finpace uses a staged command model.

1. Client submits a command
2. Platform validates syntax and entitlement
3. Command enters `pending_approval` if approval is required
4. Approval actors can approve, reject, or return for amendment
5. The command is executed only after the control profile is satisfied
6. Execution evidence is attached to the originating command record

## Eventing

Events are emitted for:

* arrangement state changes
* posted transactions
* payment status changes
* document lifecycle actions
* task status changes
* credit decision events
* covenant breach detection
* AI tool evaluation and execution outcomes

### Event design rules

* immutable payload
* event id
* causation id
* correlation id
* occurred timestamp
* tenant id
* actor context
* business object reference

## Error model

The API error model uses a machine-readable structure:

```json theme={null}
{
  "errorCode": "LIMIT_BREACH",
  "message": "Payment exceeds available arrangement limit.",
  "category": "business_rule",
  "correlationId": "01J123ABCXYZ",
  "details": [
    {
      "field": "amount",
      "issue": "exceeds_limit"
    }
  ]
}
```

## Versioning

This package uses path-stable resources and additive evolution principles:

* avoid breaking field renames
* add optional fields first
* deprecate with notice
* isolate behavioral changes behind policy or capability flags where possible


# Platform architecture
Source: https://docs.finpace.tech/getting-started/platform-architecture

Reference architecture for Finpace core banking, channels, integrations, and governed AI runtime.

# Platform architecture

## Logical layers

```text theme={null}
Channels and workbenches
  ├─ Retail and business digital channels
  ├─ RM and operations workbench
  ├─ Contact-center and assisted-service interfaces
  ├─ Partner channels
  └─ Agent UI

AI runtime and control plane
  ├─ MCP gateway
  ├─ Policy engine
  ├─ Tool registry
  ├─ AI Shield
  └─ AI audit and evidence store

Core banking domain services
  ├─ Party and customer
  ├─ Agreements and entitlements
  ├─ Product factory, pricing, campaigns, experiments
  ├─ Arrangements and accounts
  ├─ Posting, balances, holds, and liquidity
  ├─ Lending origination, affordability, scoring, servicing
  ├─ Collateral, covenants, and conditions
  ├─ Cases, documents, tasks, notifications
  └─ Interaction history and workbench context

Shared control services
  ├─ Identity and access
  ├─ Approval orchestration
  ├─ Audit and immutable event log
  ├─ Reporting and reconciliation
  └─ Event streaming

External integrations
  ├─ KYC and KYB
  ├─ Sanctions and AML
  ├─ Payment rails
  ├─ Document signing
  ├─ Credit bureaus and open banking
  └─ CRM, DWH, and analytics
```

## Architectural rules

### 1. Core APIs remain authoritative

Posting authority, arrangement state transitions, credit decisions, limit enforcement, and servicing outcomes are executed by core services.

### 2. Agents use governed tools

Finpace MCP exposes business-safe tools rather than unrestricted CRUD access to core services.

### 3. Protected actions are policy-evaluated

Before execution, the runtime evaluates:

* actor identity
* delegated authority
* channel
* customer consent
* product and jurisdiction rules
* approval profile
* policy outcome
* risk score

### 4. Evidence objects are reusable

The same evidence objects support:

* internal audit
* regulator review
* customer dispute handling
* operational traceability
* AI explainability

## Deployment model

The reference architecture supports:

* private cloud
* client cloud
* hybrid deployment
* controlled on-premises deployment for high-sensitivity institutions

Regional isolation is available for:

* prompts
* retrieval stores
* tool execution logs
* document caches
* policy packs
* audit evidence


# Platform capabilities
Source: https://docs.finpace.tech/getting-started/platform-capabilities

Capability scope for the Finpace platform.

# Platform capabilities

Finpace supports a unified operating model across retail, business, and lending domains.

## Customer and relationship capabilities

* natural person and legal entity profiles
* multi-entity groups and related-party hierarchies
* signatories, contact roles, guarantors, directors, and beneficial owners
* agreements across accounts, overdrafts, loans, and cash-management services
* entitlements by actor, object, action, and channel

## Product and pricing capabilities

* deposit, current-account, savings, overdraft, term-loan, revolving-credit, and fee-service products
* versioned product templates
* fee, interest, penalty, and commission definitions
* risk-based rate cards
* campaign rules and eligibility filters
* controlled A/B experiments for terms, pricing, and messaging

## Arrangement and money-movement capabilities

* application intake and assisted onboarding
* arrangement lifecycle management
* balance views, holds, reservations, and posting instruction processing
* internal, domestic, cross-border, recurring, and bulk payments
* multi-level approvals and mandate control
* liquidity pools, target balancing, and sweeps

## Lending capabilities

* digital and assisted origination
* affordability assessment and responsible-lending checks
* scoring and bureau orchestration
* offer generation and e-signature
* disbursement, schedules, restructuring, holidays, and forbearance
* collateral, valuations, covenants, conditions precedent, and waivers

## Operational capabilities

* omnichannel sessions
* RM and contact-center workbench
* interaction history and queue routing
* cases, tasks, SLA control, and document workflows
* statement production and event-driven notifications

## AI capabilities

* governed conversational assistance
* controlled tool execution through MCP
* policy enforcement through AI Shield
* evidence-backed explanations and audit views
* approval-aware action execution for protected banking activities


# Security and governance
Source: https://docs.finpace.tech/getting-started/security-and-governance

Security, role controls, approvals, encryption, and audit expectations.

# Security and governance

## Core control domains

The platform supports:

* role-based access control
* fine-grained entitlements by action and object
* maker-checker approval rules
* segregation of duties validation
* full audit history for configuration and servicing changes
* encryption in transit and at rest
* credential isolation for partner integrations
* document and consent evidence retention

## Role domains

### Front-office roles

* relationship manager
* branch operator
* contact-center operator
* assisted-onboarding operator

### Middle-office roles

* underwriting analyst
* risk officer
* compliance reviewer
* operations controller

### Back-office roles

* payments operator
* finance and reconciliation analyst
* product administrator
* data maintenance administrator
* system administrator

### AI runtime roles

* policy administrator
* tool publisher
* audit reviewer
* runtime operator

## Protected actions

The following actions default to protected status:

* arrangement closure
* signatory or mandate changes
* entitlement changes
* limit increases
* payment override approvals
* liquidity sweep policy changes
* credit decisions
* drawdown approval
* covenant breach waivers
* collateral release
* product parameter changes
* experiment publication
* AI tool publication and policy changes

## Audit model

Every protected action preserves:

* who requested it
* on whose behalf it was requested
* which policy pack was evaluated
* whether approval was required
* who approved it
* what state changed
* which objects were affected
* the final outcome


# Consumer lending
Source: https://docs.finpace.tech/guides/consumer-lending

Reference guide for personal loan origination and servicing.

# Consumer lending

## Product types

* unsecured personal loan
* salary-linked loan
* top-up loan
* refinance
* card-linked installment facility

## Documentation focus

Consumer lending docs should clearly cover:

* affordability and responsible lending checks
* disclosures and acceptance
* decision explainability
* repayment schedule generation
* payment holiday and forbearance handling
* complaint and dispute support

## API focus

The most important API families are:

* credit applications
* offers
* facilities
* repayment schedules
* servicing actions
* notifications


# Retail and business account launch
Source: https://docs.finpace.tech/guides/retail-and-business-account-launch

Reference guide for deposit and overdraft launch patterns.

# Retail and business account launch

## Typical launch sequence

1. Define product and product version
2. Configure fees, interest, and eligibility
3. Configure documents and disclosures
4. Configure mandates and signatory model
5. Configure approval profile
6. Expose offer to channel set
7. Test onboarding, opening, funding, and servicing events
8. Activate statements and notification templates
9. Reconcile accounting outputs before production

## SME variant

For business accounts, add:

* legal entity and UBO capture
* mandate structures
* limit rules
* linked overdraft settings
* RM-assisted flows

## Key test packs

* same-day account opening
* failed KYC path
* signatory update
* payment awaiting approval
* overdraft utilization
* fee correction
* statement regeneration


# SME lending
Source: https://docs.finpace.tech/guides/sme-lending

Reference guide for SME term loans and credit lines.

# SME lending

## Covered lifecycle

* pre-screen
* application capture
* financial and KYB enrichment
* analyst review
* decisioning
* conditional offer
* approval
* documentation
* drawdown
* monitoring
* covenant and collateral follow-up
* restructure or workout

## Key data sets

* borrower structure
* requested amount and tenor
* pricing proposal
* collateral proposal
* financial statements
* bureau and open banking signals
* approval conditions
* document evidence

## AI support

Recommended AI use:

* summarize borrower pack
* compare uploaded financial documents
* propose analyst checklist completion
* draft credit note from structured inputs

Do not publish unsupported claims that AI performs final lending judgment autonomously.


# SME onboarding and account opening
Source: https://docs.finpace.tech/guides/sme-onboarding-and-account-opening

End-to-end guide for assisted and digital SME onboarding.

# SME onboarding and account opening

## Reference journey

1. Start application
2. Capture legal entity and representative data
3. Collect KYB and UBO information
4. Collect documents
5. Run sanctions, fraud, and compliance checks
6. Evaluate eligibility
7. Open account or route to review
8. Activate channels and linked services
9. Deliver confirmations and document pack

## Control points

* missing document queue
* UBO mismatch review
* sanctions escalation
* signatory validation
* product eligibility failure
* account opening approval if threshold or exception requires it

## AI support

Useful AI steps:

* summarize legal structure from documents
* identify missing onboarding data
* draft follow-up requests
* explain onboarding status to RM or customer


# Overview
Source: https://docs.finpace.tech/index

Finpace core banking, lending, servicing, workflow, and governed AI runtime documentation.

# Finpace Developer Portal

Finpace documents the banking system of record, operational workflow, and governed AI runtime used to support retail banking, business banking, SME lending, consumer lending, service operations, and controlled partner access.

The portal is written for:

* tier-1 banks
* digital banks and regulated financial institutions
* solution architects and integration teams
* operations, risk, compliance, and servicing functions
* channel, CRM, and AI runtime teams

## What this portal documents

1. **Core banking domain model**\
   Parties, customers, agreements, products, arrangements, balances, limits, mandates, postings, statements, and servicing controls.

2. **Lending domain model**\
   Applications, underwriting packages, affordability, scoring, offers, facilities, schedules, collateral, covenants, restructures, and write-off controls.

3. **Interaction and workflow model**\
   Omnichannel sessions, RM workbench, contact-center routing, interaction history, tasks, cases, documents, and notifications.

4. **Governed AI runtime**\
   MCP, Agent UI, AI Shield, policy evaluation, controlled tool execution, explainability evidence, and audit.

## Documentation principles

* **Everything described here is treated as product capability.**
* **Each public capability has a matching API surface.**
* **Control boundaries are explicit.**
* **AI operates inside banking controls, not around them.**
* **Operational evidence is preserved for servicing, compliance, and audit.**

## Main capability areas

* customer and party management
* agreements, entitlements, and organizational hierarchies
* product factory, pricing, campaigns, and experimentation
* account opening, mandates, and signatory control
* balances, holds, posting instructions, and ledger outputs
* payments, approvals, liquidity pools, and sweeps
* SME and consumer lending
* affordability, scoring, and decisioning
* collateral, covenants, and condition management
* cases, tasks, documents, and correspondence
* omnichannel access, RM workbench, and contact-center orchestration
* governed AI assistance and controlled action execution


# Reference overview
Source: https://docs.finpace.tech/reference/overview

What the Finpace API covers and how to read it.

# Reference overview

The API reference models the business objects and control surfaces a bank expects to see documented.

## API domains

* parties, groups, customers, agreements, and entitlements
* products, bundles, offers, rate cards, campaigns, and experiments
* account applications, arrangements, balances, mandates, and transactions
* payments, approvals, liquidity pools, and sweeps
* credit applications, affordability assessments, decision packages, offers, and facilities
* collateral, covenants, and condition checklists
* channel sessions, interaction events, workbench context, and routing profiles
* cases, tasks, documents, statements, notification templates, and deliveries
* AI assist sessions, policy evaluation, and governed tool execution

## Conventions

* OAuth or bearer-token protected
* idempotency for state-changing calls
* event-friendly resource design
* explicit approval endpoints where control is required
* object-centric responses rather than UI-shaped payloads