Request a Demo
FAQ

Frequently Asked Questions About Sanson Group

Answers to common questions about composable banking, fintech services, AI, integration, security, modernization and working with Sanson.

02Composable Banking

Composable Banking

What is composable banking?

Composable banking is an architectural approach where independent, interchangeable fintech modules — for payments, lending, RegTech, AI and more — connect to a bank's existing core through standardized APIs. This lets financial institutions modernize individual capabilities progressively, rather than replacing their entire technology stack at once.

Composable Banking Platform →
Why use modular banking services?

Modular services let institutions adopt new capabilities on their own timeline, without a coordinated system-wide release. Each module can be updated, replaced or expanded independently, reducing the risk and cost associated with large, all-at-once technology projects.

Can banks modernize without replacing everything?

Yes. A composable approach connects new modular capabilities to your existing core through APIs, so institutions can modernize specific areas — like payments or lending — without replacing the underlying core system.

Why Sanson →
Can services be adopted independently?

Yes. Each of Sanson's six capabilities — digital banking, payments, RegTech, Open Banking, lending and AI-driven automation — can be adopted on its own, in whatever sequence matches an institution's priorities.

03Platform & Architecture

Platform & Architecture

How does Sanson integrate with existing banking systems?

Sanson connects to an institution's existing core banking system through standardized APIs and an integration layer, rather than requiring a full replacement. This allows new capabilities to work alongside what's already running.

Composable Banking Platform →
How are APIs used?

APIs connect modular capabilities, orchestration and the core to one another in a standardized way, replacing the need for custom point-to-point integrations between systems.

What does the integration layer do?

The integration layer manages API connectivity, orchestration, middleware and data connectivity — coordinating how modules, existing infrastructure and the core work together.

Can banks adopt individual capabilities?

Yes. Institutions can start with a single capability — such as payments or RegTech — and expand the architecture over time as priorities and readiness allow.

Payment Infrastructure →
04AI & Intelligence

AI & Intelligence

How is AI used in banking?

AI is used across banking to detect fraud, personalize customer experiences, automate credit scoring and underwriting, power conversational service and streamline compliance and operations.

AI & Intelligence →
What banking workflows can AI support?

AI can support onboarding, fraud detection, compliance monitoring, credit decisioning, lending, customer service and back-office operations, functioning as an embedded capability across the platform.

How is AI governed?

AI governance includes clear ownership over how models are developed and deployed, explainability appropriate to a decision's risk level, data governance and ongoing monitoring for model performance.

How is human oversight maintained?

Higher-risk or higher-impact decisions are designed to route through human review rather than acting fully autonomously, with clear escalation and approval checkpoints built into the workflow.

05Security & Compliance

Security & Compliance

How is customer data protected?

Data protection is addressed through access controls, data governance policies and monitoring built into the platform's connectivity and data layers. Specific technical safeguards for a given engagement are confirmed during architecture review.

Specific certifications and technical controls: [REQUIRES VERIFIED INFORMATION]
What security standards are supported?

Applicable security standards depend on an institution's environment and regulatory requirements, and are confirmed during the architecture assessment for each engagement.

[REQUIRES VERIFIED INFORMATION]
What regulatory environments are supported?

Regulatory scope varies by institution and jurisdiction. Specific regulatory environments and controls supported for a given engagement are confirmed as part of the engagement process.

[REQUIRES VERIFIED INFORMATION]
06Engagement & Pricing

Engagement & Pricing

What does a typical engagement look like?

Sanson engagements typically follow three phases: Discover & Design, Deploy & Integrate, and Optimize & Evolve — starting with the institution's existing environment and priorities.

How is implementation structured?

Implementation follows a phased path: understanding the current architecture, designing the target state, deploying and integrating the first capability, then optimizing and expanding from there.

How is pricing determined?

Pricing depends on the scope, capabilities and integration requirements of each engagement, and is discussed directly with Sanson's team during a consultation.

[REQUIRES VERIFIED INFORMATION]
Can Sanson support architecture assessment?

Yes. An architecture assessment is typically the starting point for understanding an institution's existing environment and identifying where modernization will have the clearest impact.

Request a Demo →

Modernize Your Banking Architecture

Talk with Sanson's team about the capabilities, integration requirements and modernization priorities that matter most to your institution.

Request a Demo