Core Banking Platform

Build your next banking product on a core that can change.

Bring account products, pricing and payment operations together. Connect the providers you need, give your team clear controls and choose a rollout that fits your existing stack.

Account productsPrice listsBack-Office DashboardAPI
Your new bankBanking operationsProduct preview
Daily operations

Customer accounts

Example data
Available across EUR accounts49,520.50EUR
Available across GBP accounts8,320.00GBP

Connect the services behind your bank.

A selection of our connectorsExplore all connectors
The people behind your platform

Build the team behind a better banking experience.

Give operations, payments and compliance teams a shared place to work, with access and approval responsibilities shaped around your business.

  • Clear roles and responsibilities
  • One connected operating environment
A financial product team working together in a studio.
Case Studies

See what teams build with Crassula.

Built around the decisions your team makes

The product should evolve. The operating model should stay clear.

01

Shape the account product

Define personal and business account structures, currencies and provider defaults before you bring the product to customers.

Explore accounts →
02

Make pricing part of the product

Set reusable price lists with fixed, percentage and recurring fees. Keep the commercial model connected to the service you deliver.

Product pricing →
03

Give operations a defined role

Configure permissions and payment approvals so your team can work within a clear policy as the product grows.

Back-Office Dashboard →
Your starting point matters

Launching something new or changing what already runs?

These are different projects. Start with the path that matches your institution, your data and your operating responsibilities.

A new product

Start with the banking model you want.

Configure the initial account products, tariffs and approval policies. Connect the providers and customer channels required for your first release.

  1. Define products and responsibilities
  2. Connect providers and interfaces
  3. Validate the end-to-end journey
An existing institution

Plan the transition around what must keep working.

Review the current system, data scope and integrations with our team. Crassula can run alongside an existing core; the migration approach depends on your requirements.

  1. Map the current operating model
  2. Agree the scope and data requirements
  3. Validate the transition plan

Moving off a legacy or first-generation core? Crassula can even migrate you for free depending on the amount of data, and can run alongside your existing system, so you modernize in stages instead of betting the bank on a single cut-over.

A connected foundation

Keep your product, providers and interfaces in the same conversation.

Use documented APIs to connect your own experience. Select integrations for the capabilities your programme needs. Product configuration and provider availability determine what your customers can use.

Customer channelsYour web and mobile experience
iOSAndroidWebAPI
Crassula
Crassula
AccountsPricingPermissionsApprovals
Connected servicesBanking providers and payment rails
OpenPaydCurrencycloudRailsr
Built for developers

Build accounts into your own experience.

Open a named account from your own product. Connect the account journey to the banking capabilities available in your Crassula environment.

  • Create an account for an existing client
  • Pass the account name, currency and country
  • Use the returned account in your next journey
Explore the API docs
POST/api/clients/{clientId}/accounts
Node.js · native fetch
// Create an account
const baseUrl = process.env.CRASSULA_BASE_URL;
const apiKey = process.env.CRASSULA_API_KEY;
const clientId = process.env.CRASSULA_CLIENT_ID;

const path = `/api/clients/${encodeURIComponent(clientId)}/accounts`;
const response = await fetch(`${baseUrl}${path}`, {
  method: 'POST',
  headers: {
    Authorization: apiKey,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "name": "Everyday account",
    "currency": "EUR",
    "countryCode": "DE"
  }),
});

if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
Crassula Connectors

Connect the services your product needs.

Choose integrations that fit your programme, market and required capabilities.

Core Banking

FAQ

The questions teams ask us before a first call.

Not covered here?Bring your question to a demo with our team.
Is Crassula a full core banking system?

For a new or challenger bank, yes - Crassula provides a modern real-time ledger, accounts, payments, cards and products you can run as your core. For a large established bank, Crassula is best used as the orchestration and product layer on top of your existing system of record, not a replacement for a tier-one core like Temenos or Thought Machine.

How long does a core implementation take?

A greenfield launch on Crassula takes weeks, versus the 18-36 months typical of a traditional core program. Modernization projects that run Crassula alongside an existing core are staged, so you avoid a single high-risk cut-over.

Can we migrate from our current core?

Yes. Crassula can run in parallel with your current core during the transition, so operations keep running while you move. Depending on how much data comes across, the migration can even be free.

Is it API-first?

Yes. Every core function - accounts, transfers, cards, limits, reporting - is available over a documented API, so your apps, channels and third parties integrate cleanly.

Core Banking

Bring your next product. We’ll map the foundation.

Talk through your account model, connected services and rollout requirements with our team.

Discuss your architecture
Top