Launch products on a licensed core
We integrate and extend the core, a provider's or your own, and build the ledger and reconciliation around it. A core's mistakes compound into every balance, statement and report. We have integrated Mambu and helped build a skinny core.
DT One and Beforepay, integrated for Shaype end clients
Onto Shaype Core in 2021, three months in parallel
Discrepancies surface in minutes, not at month end
Capabilities in core integration
Core integration and migration
Accounts and cards sit on the core, rewards and lending come through supplier integrations, and your team inherits none of the core's complexity. Your customers get a balance that can be explained and a statement where every line is something that happened. Mambu is among the cores we have integrated, and where a full core is more than the product needs, we have helped build a skinny core. The team our managing director led at Shaype moved its platform onto Shaype Core in 2021 with no downtime.
Event sourced ledgers
Immutable, append only entries with balances derived from them, so every number can be explained and a correction is a compensating entry rather than an edit.
Reconciliation
Matching against scheme, sponsor bank, processor and settlement files, built alongside the ledger and alerting on business invariants rather than stack traces.
Partner sandboxes
Sandbox environments and developer experience for the partners who build on your platform: their product teams build and demo against the sandbox before they certify, and it is close enough to production that certification holds no surprises.
Integration surfaces we know from the inside
- Mambucore banking · Shaype, 2018 to 2023
- Shaype Corea skinny core · Shaype, 2018 to 2023
- Threddcard processor, for card issuing on the core · Shaype, 2018 to 2023
- Shaype platform APIsintegrating end clients with the platform · Shaype, since 2023, Sofitect
- Shaype platform webhooksan integration layer for mobile phone notifications · Shaype, 2023, Sofitect, under contract to Mobiquity
- DT Oneperks supplier, for mobile top ups, gift cards and rewards · Shaype, 2026, Sofitect
- Beforepaymicro lending platform · Shaype, 2026, Sofitect
- Sardinetransaction monitoring and fraud decisioning · Shaype, 2018 to 2023
Entries marked Shaype, 2018 to 2023 were built while Marius Telespan was Shaype's Head of Engineering. They are his track record, not Sofitect engagements. Entries marked Shaype, a year and Sofitect are Sofitect's own engagements on the platform, for Shaype and its end clients, since 2023.
Moving a live platform to its own core
In 2021 Shaype moved its platform off the SaaS core it ran on and onto Shaype Core. The work was done by the team our managing director, Marius Telespan, led as its Head of Engineering. It was an internal Shaype project with no third parties, and not a Sofitect engagement. Shaype needed features that were easier to build on a core shaped to its own model, such as paying someone on the platform by their phone number, and wanted the call to an external core out of the latency path. It is told here so you can judge the method and not the claim.
- 01
Build the new core
Shaype Core, built as an event sourced ledger. Twelve months, with the platform still running on the SaaS core throughout.
- 02
Migrate and validate
Several full test migrations, each validated and reconciled against the live core. When validation found anything, the run was discarded and a fresh one started from a clean state, the live core untouched. Three months.
- 03
Run in production in parallel
Shaype Core as a shadow core for three months. A proxy service with a validation layer answered every read from both cores and compared the results live, as customers used the system, on production data. No discrepancies.
- 04
Then the switch
Everything moved: customers, accounts, cards, transactions, authorisation holds and ledgers. No downtime. The old core decommissioned.
In the UK and EU
A core migration, done once on Shaype's platform, onto Shaype Core in 2021, by the team our managing director led as its Head of Engineering. Or a new product on a banking as a service provider. A ledger and reconciliation layer for an EMI or payment institution, where the FCA's safeguarding rules expect safeguarded funds to be reconciled daily. Partner sandboxes for an embedded finance platform certifying its own clients. We have not built on every core. We have built the ledger and reconciliation around Mambu, and the reconciliation around a skinny core that is itself the ledger. The pattern transfers.
The delivery path
Map the core
Its data model, its events and its failure modes, written down before anything is built to depend on them.
Model the money
Ledger and state machine first. If the accounting model is wrong, no amount of application code recovers it.
Reconcile from day one
Matching runs from the first posting, so a mismatch is a failing check in week two rather than a finding in month fourteen.
Operate with evidence
Structured logs, alerting on business invariants and reconciliation dashboards that a compliance officer can read.
Ledger and core engineering at Shaype, the Australian banking as a service platform operating under its own AFSL, built from 2018 to 2023 by the team our managing director, Marius Telespan, led as its Head of Engineering. That team helped build Shaype Core, its skinny core, built as an event sourced ledger. In 2021 the same team moved the platform from the SaaS core to Shaype Core: twelve months to build the new core, three months to validate and reconcile it against the old core, three months in production in parallel, then the switch, with no downtime.
- Shaype Core, a skinny core built as an event sourced ledger, which that team helped build
- The 2021 move onto Shaype Core: customers, accounts, cards, transactions, authorisation holds and ledgers, with no downtime
- Three months in production in parallel with no discrepancies, after full test migrations rerun from a clean state whenever validation found anything
- Reconciliation and partner sandboxes around it
Bring us your core integration problem
Ninety minutes with the engineers who would do the work, on one problem you name: a product to launch on a core, a ledger that will not reconcile, a sandbox your partners cannot build against.