AI for banking, from credit decisioning to KYC, AML and treasury automation.

Annex III §5(b) classifies AI used to evaluate the creditworthiness of natural persons or to establish their credit score as high-risk. That triggers obligations on risk management, data governance, technical documentation, record-keeping, transparency, human oversight, accuracy, robustness and cybersecurity. We build conformity-assessment scaffolding into the system from week one: an ISO 42001-aligned governance memo, the technical documentation pack the regulation requires, an append-only audit log, and a documented human-in-the-loop step for any decision that affects a customer. If your specific use case is limited-risk rather than high-risk, we ship the proportionate controls, but we never default to less than the regulation requires.

Federal Reserve SR 11-7 is the most-cited model-risk-management standard globally and most internal validation teams already work to it (or its OCC counterpart, Bulletin 2011-12). We anchor every banking-AI engagement to its three pillars: sound development, implementation and use; effective validation; and sound governance, policies and controls. The technical-documentation pack we deliver mirrors the SR 11-7 line items so validation teams do not have to invent a new control set. Where the bank operates under PRA SS1/23 or another local equivalent, we align to that instead.

Yes. The delivery layer is built around your core, not the other way around. We ship integrations with Temenos Transact and Infinity, Mambu, FIS Profile, Finastra Fusion, and the major card and AML platforms (Actimize, SAS AML, ComplyAdvantage). For systems without a modern API we build a queue-based bridge with idempotent writes and a manual reconciliation interface. The audit log writes regardless of where the data lands.

Article 22 prohibits decisions producing legal or similarly significant effects from being made solely on automated processing without explicit safeguards. For credit decisioning that means the human reviewer has to retain a substantive, not rubber-stamp, role. We design the workflow so the AI structures the decision packet (features, policy hits, comparable cases, draft rationale) and the human underwriter signs the actual decision with the ability to override. Every override is logged with reason codes and a free-text rationale, and the customer-facing reasons-for-decline letter is generated against the same audit log.

DORA applies to banks as in-scope financial entities under Article 2(1)(a). AI systems used in critical or important functions therefore inherit DORA obligations on ICT risk management, third-party risk, incident reporting and resilience testing. We deliver the third-party-risk register entry, the ICT-incident playbook for AI-specific failure modes (drift, prompt-injection, model unavailability), and a resilience-testing protocol that fits inside DORA's threat-led penetration-testing regime where applicable.

By default, all processing and storage runs in EU regions on infrastructure under EU jurisdiction. We support regional pinning when a regulator or contract requires it (Germany-only, Lithuania-only, US-only). Customer data lands in immutable EU object storage with hashes recorded in the audit log. We do not train any model on your data, full stop. If your contract requires US-resident processing for a US-only line of business, we expose that as an explicit configuration toggle, never a default.

A first engagement targets one workflow with a measurable baseline, runs 4 to 12 weeks to production, and lands as a single signed-off system inside one core or supporting platform. Common first scopes are: KYC document automation, AML alert triage on one alert family, credit decisioning on one product (unsecured consumer lending or SME lending), or fraud-pattern detection on one product line. Submit a project with the workflow you have in mind and the rough volume, and we scope and price the discovery phase before any code is written.

Pricing is set after the discovery sprint, against your specific workflow, integration surface and conformity scope. We do not publish a flat rate because the variation across banking AI is wide: KYC document extraction on a stable form set is a different build from a multi-product credit-decisioning stack with full SR 11-7 documentation. Submit a project with the workflow and rough volume, and we come back with a discovery proposal within one business day.