Software licence
The bank operates the platform under an enterprise licence with source code escrow. Fortiva provides annual licensing and L3 support; the bank handles L1/L2.
DEPLOYED WHERE YOU OPERATE
Your data centre. Your operating model.
Production-ready infrastructure without a foreign SaaS dependency. Your engineers verify the deployment; your teams control the service.
| Where control sits | Fortiva in your bank | Foreign SaaS model |
|---|---|---|
| Source code escrow | Contractual escrow and engineer sandbox access | Depends on vendor terms |
| Data residency | Deployment in the bank's data centre | Depends on hosting region and provider |
| Regulatory roadmap | Institution-specific control matrix | Shared provider roadmap |
| Brand & contracts | Owned by the bank | Depends on the service arrangement |
| Key location | Customer device and the bank's infrastructure | Depends on provider architecture |
| Verifiable build | Signed images, SBOM and reproducible inputs | Depends on vendor disclosure |
| Access-cut risk | No foreign SaaS service switch | Exposure to provider access restrictions |
| Commercial model | Deployment project, annual licence and L3 support; no per-wallet or per-transaction fees | Provider-specific subscription and usage terms |
Comparison of operating models; individual provider contracts and architectures vary.
Fits the bank's operating environment.
Fortiva runs on Kubernetes with PostgreSQL in the bank's data centre or private cloud. Signing participants operate in separate network segments. The project integrates the bank's HSM/KMS, SIEM, core banking and client ledger. Capacity, high availability, backup and recovery objectives are agreed during design; production HSM/KMS adapters and cryptography validation are included in the deployment scope.
Agree who owns each decision.
The bank operates its environment. Fortiva supplies the software, deployment project and L3 support. Confirm responsibilities during design and acceptance.
| Area | Bank | Fortiva |
|---|---|---|
| Infrastructure | Provide and operate the data centre and selected HSM/KMS. | Deploy the platform within the agreed architecture. |
| Policies | Set risk policies, signers, roles and approval requirements. | Provide the policy engine and configuration within the deployment scope. |
| Recovery | Control recovery authority and the two escrow-holder arrangement. | Provide the recovery design and support deployment acceptance exercises. |
| Release acceptance | Verify release evidence and accept the software into the environment. | Supply signed images, an SBOM and reproducible build inputs. |
| Support | Provide first- and second-line operations support. | Provide L3 software support under the annual agreement. |
Escrow and an engineering sandbox.
Source code escrow supports contractual continuity arrangements. Sandbox access for the bank’s engineers is provided under NDA to evaluate workflows and integration boundaries. These arrangements are scoped with the deployment project.
Three ways to work together.
Co-development
The bank's engineers and Fortiva develop institution-specific adapters, reporting and payment integrations against an agreed roadmap.
Group operator
The bank runs a platform for subsidiaries and institutional clients, with separate vaults, policies and evidence trails per tenant.
FROM DISCOVERY TO PRODUCTION
A clear path into your infrastructure.
A phased engagement with agreed acceptance criteria. The schedule is scoped with your bank.
- 01
DISCOVERY
Discovery workshop
Align the business line, architecture and operating responsibilities.
- 02
WEEKS 1–2
NDA, demo & evidence
Review the architecture and audit evidence; give engineers sandbox access.
- 03
WEEKS 2–4
Design & acceptance
Agree policies, roles, integrations and acceptance criteria.
- 04
WEEKS 5–12
Deployment & pilot
Install in the bank. Validate on testnet before a controlled mainnet pilot.
- 05
MONTH 4+
Independent audit & production
Complete deployment audits and production acceptance, then expand to the next business line.