Pilih negara atau wilayah Anda

A customer banking app for Thought Machine Vault Core.

Vault runs your products as smart contracts. We give your customers and staff the screens on top.

We build the Thought Machine Vault Core connector during your implementation programme, with the same connector kit as our existing connectors.

Core banking

How we connect to Thought Machine Vault Core

Vault Core is a cloud-native core banking platform from Thought Machine, where products are defined as smart contracts and data leaves as event streams. It runs across cloud providers and is used by large banks, regional banks and digital banks.

Through the Core API

We read customers, accounts and balances and submit postings through Vault's REST Core API, with credentials your team issues.

Through the event streams

Vault publishes balance, accounting and customer events on Kafka. We consume the topics the app needs, so screens stay current.

Tested on your sandbox

We run our connector checks against your Vault test environment before anything reaches production.
Data

What moves between Thought Machine Vault Core and your app

  • Customers and their accounts, mirrored by reference
  • Live balances read from Vault
  • Transactions and postings
  • Payments submitted to Vault and tracked
  • Balance and customer events from Vault's streams

Smart contracts, product logic and the ledger stay in Vault. We keep no ledger and run no product logic.

Contoh penggunaan

What your bank can do with it

Ship the app with the core

Your engineers build products in Vault while the customer app is already finished in your brand.

Open accounts with checks

Applicants verify their identity and your staff approve with an explained risk score before Vault opens the account.

Serve businesses on the same app

Business customers set payment rules where the maker never approves their own payment.
Why it matters

What it changes for your bank

Your team stays on products

Smart contracts stay your engineers' work. The app and staff portal come from us.

Events, not polling

Screens update from Vault's streams, so customers see changes as they happen.

Reviewed changes only

Every connector change is published with two people's approval and can be rolled back.
Rollout

From first call to live

  1. Step 1: PenjajakanWe map your Vault products, smart contract parameters and stream topics.
  2. Step 2: Build the connectorWe build the Vault connector with our connector kit on the Core API and streams you run.
  3. Step 3: Design your appWe set your brand, products and wording for web, iPhone and Android.
  4. Step 4: Test and launchWe test on your Vault environment, then launch with your sign-off.
Pertanyaan

Thought Machine Vault Core: what IT teams ask

Do you write or change our smart contracts?
No. Smart contracts stay with your engineers. We call the Core API and read the results.
Do you need access to our Kafka cluster?
Read access to the topics the app needs, scoped by your team. We never write to Vault's streams.
Where does Everbranch run relative to our Vault deployment?
In its own environment, with one database per bank. Connections to Vault go only to the hosts on your bank's allowlist.
Can we move off our current digital channel gradually?
Yes. Both can run against Vault at the same time while you move customers over.
Related

Mambu

Mambu gives you a cloud core. We give your customers the app on top and your staff the portal to run it.
Read more

Temenos Transact

Keep Transact as your core and give customers an app they enjoy. We connect through the Transact APIs your bank licenses, or the files it already exchanges.
Read more

Apache Fineract

Your customers open accounts, check balances and pay from one app in your brand. Fineract stays your book of record, and our connector talks to it through its REST API.
Read more
Program percontohan

Running Thought Machine Vault Core? Let's map it.

Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.

  • Nama dan warna Anda di demo
  • Jawaban lugas untuk tim risiko, kepatuhan, dan TI
  • Tanpa komitmen