Thought Machine: Vault Core, Vault Payments and core-bank modernization

Vault Core separates programmable product rules, foundational ledger capabilities and cloud infrastructure. Its published product families include current accounts, savings and term deposits, multi-currency wallets, loans and mortgages, credit cards and buy-now-pay-later arrangements. Product teams can change banking rules independently of the ledger engine. That makes product-code versioning, interest calculations, reversals and migration reconciliation central to implementation.[1]

Vault Payments consolidates processing across transaction rails. Its published rail examples establish platform capabilities, not a promise that an unlicensed fintech gains direct membership of those schemes. The purchasing institution still needs to establish sponsorship, settlement accounts, scheme messages, sanctions screening, cut-offs and exception handling in its applicable market.[2]

The software is designed for API-driven integration into surrounding customer channels, bank middleware and risk-control systems. That does not automatically mean every historic core interface, AML tool or settlement system already has a verified connector. An integration inventory should identify the party maintaining each interface, its data model, error queues and release-upgrade timetable.[1][3]

Multi-region and multi-cloud support are architectural options. The deployment agreement establishes the actual failover topology, recovery objectives, hosting regions, encryption-key ownership and resilience tests.[1][3]

A comparable quotation separates the platform commitment, development and testing environments, infrastructure, migration work, payment-volume tiers and termination assistance. A bank replacing its full account book has a different delivery scope from one adding a single product alongside its existing core.[1][2]

Running cost also depends on which party hosts the system and on the internal technology team required to maintain banking-product code. Vendor support, cloud consumption, consulting and payment-scheme charges can be material but are not established as bundled into one published subscription.[3]

The three deployment routes in Vault Core provide a useful planning distinction. Coexistence leaves part of the old system running, greenfield starts with a clean book, and full replatforming has to replicate contractual account terms and historic ledger balances. In each route, a bank should test interest accrual, reversal behaviour, account status, end-of-day extracts and financial reconciliations, not merely the user interface.[1]

For Vault Payments, settlement and exception management are separate workstreams. Technical acceptance should include scheme acknowledgements, message rejects, late reversals, intraday liquidity, sanctions and fraud holds, contingency channels and on-call ownership. The cutover timetable is agreed for the deployment.[2]

Thought Machine describes engineering and support coverage across its regional hubs and implementation partners. Contractual service hours, incident priorities, escalation, maintenance windows, version support and ownership of partner code determine how that coverage applies to an individual bank.[4][3]

The public commercial enquiry is handled through a form, while the privacy page names a separate data-protection route. These should not be confused with the authenticated technical support channel available to a contracted banking customer.[6][5]

Thought Machine Group Limited is named in the public privacy notice. The customer relationship may use a group company or other delivery entity stated in the contract. That contracting entity must not be inferred from a regional sales office alone. No bank or broker permission is implied by the vendor name.[5][4]

A banking client must retain control over customer onboarding, prudential and conduct obligations, complaint handling and any client-money or deposit protection scheme. Vault Payments is a processing system; a successful payment API integration is not the same thing as central bank settlement access or banking authorisation.[1][2]

Thought Machine was founded in London in 2014 and launched Vault Payments in 2022, according to its corporate timeline. It identifies London, New York and Singapore as regional hubs, with offices in Lisbon, Miami and Sydney. The privacy notice names Thought Machine Group Limited and group companies; the customer agreement determines the actual delivery and contracting entity.[4][5]

Operator

Thought Machine Group Limited and contracting group entities

Service scope

Cloud-native banking ledger and payment-processing software sold to financial institutions. Vault Core handles product and ledger logic; Vault Payments is a distinct transaction-processing system. Thought Machine is a software supplier rather than a bank or customer-deposit custodian.

Customer types

Banks; Digital banks; Deposit and lending institutions; Payments providers; Bank technology integrators

Delivery

Hosted; Hybrid; API

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

Vault Core; Vault Payments

Pricing scope

Enterprise licence, hosting, migration, payment-rail integration and professional-service prices require a scoped commercial quotation; no universal public per-account or per-transaction tariff was verified.

Implementation

The supplier describes coexistence, replatforming and greenfield implementation paths. Bank product migration, cloud architecture, product smart contracts, payment rail access, ledger reconciliation and regulatory certification must be scoped by programme. No universal delivery lead time or public service-level schedule was found.

Support

Commercial contact form, implementation partner network and customer support teams across regional offices. The group describes global engineering coverage; published marketing does not establish a universal 24/7 ticket response SLA for every contract.

Permissions and regulatory scope

The reviewed pages identify a banking technology vendor, not a deposit-taking institution. A bank deploying Vault Core or Vault Payments remains responsible for its own permissions, safeguarding, payment-scheme access and regulatory reporting; those responsibilities are not conferred by installing the software.

Provider metadata checked 22 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6

The decisive due-diligence documents are an architecture design, product-rule catalogue, data-conversion control plan, resilience test evidence and explicit commercial allocation of interface ownership. Compare the system’s accounting controls and operational exit routes with the buyer’s own compliance and reconciliation requirements before committing to a cutover date.[1][2][3]