Your future banking experience

Your bank, in their hands.

Bring your brand to ready-made iOS and Android apps, with account, payment and card journeys connected to the capabilities you configure in Crassula.

Explore your app experienceExplore the connected experience ↓
iOSAndroidWeb
Your new bank

Your accounts

JL
Euro account€12,480.00Available balance · EUR
GBP1,240.50USD3,200.00

Recent activity

Aster StudioIncome+2,500.00EUR
UberTransport−18.60EUR
SpotifyEntertainment−11.99EUR
IKEAHome & living−149.00EUR
Illustrative customer appExample tariff. No payment is sent.

Connect the services behind your app.

A selection of our connectorsExplore all connectors
Built around their day

A balance check. A payment. Back to their day.

Give customers a familiar way to check a balance, find account details and review a transfer. Your brand carries through the small moments that make up everyday banking.

A man checking his phone at home.
Case Studies

See what teams build with Crassula.

One identity across every channel

The same banking relationship. A layout for each screen.

Let customers find their accounts, balances and activity through web and mobile experiences shaped around the same product configuration.

n.Your new bank
Personal bankingJL
Jamie’s accounts

Your money, at a glance.

€EUR12,480.00Euro account · •••• 4201
£GBP1,240.50Pound sterling
$USD3,200.00US dollar

Recent activity

Aster StudioIncome+2,500.00 EURCompleted
UberTransport−18.60 EURCompleted
SpotifyEntertainment−11.99 EURCompleted
IKEAHome & living−149.00 EURCompleted
An illustrative shared account view. Branding changes appearance; product modules define available services.
01

Recognisable on the phone

Offer branded iOS and Android apps with the account and payment capabilities enabled for your fintech.

02

Useful in the browser

Present multiple accounts, activity and statements in a workspace designed for the web.

From appearance to a working product

Agree what your app needs to do.

Start with the customer journey, then confirm the banking modules, provider connections and release work behind it.

Explore white-label apps →
01

Shape the identity

Agree the application name, colours, appearance and languages for your product. Keep those choices separate from account eligibility, payment rules and pricing.

Application identityiOS · Android · Web
02

Connect the customer journeys

Confirm which account, payment, card and verification services the app will present. Review authentication and integration scope against your existing systems.

Explore selected connector ↗

Illustrative product connection. Provider scope and availability are agreed for your programme.

03

Validate the release

Review the configured journeys, supported devices, operating processes and publishing responsibilities before agreeing the release plan.

Discuss your implementation →
Built for developers

Your interface. Connected to real account data.

Build your own balance screen on top of the Banking API, or extend your branded Crassula apps. Retrieve account balances by currency to power the experience you design.

  • Read balances for each account and currency
  • Filter the response to one account
  • Use current, reserved and available balances
Explore the API docs
GET/api/clients/{clientId}/balances
Node.js · native fetch
// Retrieve account balances
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)}/balances`;
const query = new URLSearchParams({
  "filter[account]": "YOUR_ACCOUNT_NUMBER"
});
const response = await fetch(`${baseUrl}${path}?${query}`, {
  method: 'GET',
  headers: {
    Authorization: apiKey,
  },
});

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.

Mobile Banking App

FAQ

The questions teams ask us before a first call.

Not covered here?Bring your question to a demo with our team.
How can we adapt the apps to our brand?

Configure the application identity, colours, appearance and language defaults. Agree any changes to layouts and customer journeys during product scoping. Branding settings are separate from banking rules and provider connections.

Which customer channels are supported?

Offer branded iOS and Android apps alongside a web interface. Each channel can present the banking capabilities configured for your product, with navigation and layouts suited to its platform.

What is connected behind the app?

The app presents account, payment, card and verification capabilities configured in Crassula. Agree the required modules, supported providers and customer journeys for your programme.

Can we connect our existing systems?

Review your current architecture, authentication and account/payment workflows with our team. Integration scope depends on those systems and the capabilities your app needs; compatibility is assessed rather than assumed.

What determines the release plan?

Branding, enabled capabilities, provider integrations, validation and publishing responsibilities determine the delivery scope. Agree these dependencies with the team before setting the release plan.

Top