Tailwind
Integration

Plugs into what your bank already runs.

Tailwind runs on your own servers, so client data never leaves your bank, and your tech team controls every release.

A typical integration takes weeks, not months.

Your bank’s infrastructure
Your business banking app
Tailwind Cash flow planning and forecasting
Your core banking systems
APIs, events or open banking
4 Your code repository
Built and run by you
Tailwind Sends code and updates
1 Shown in your app
2 Signed in with your login
3 Balances and transactions
Only the code comes from Tailwind.
Everything else stays inside your bank.
01

Inside your app, separate from its code

Clients open Tailwind as one more section of your app, with no hand-off to someone else’s site.

Under the surface it stays fully separate from your app’s code. That means it can’t break what’s already there, and new versions reach your clients without waiting for your next app release.

For your tech team
  • Works with any front-end stack
  • No code shared with your app
  • Updated without a release of your app
See how it takes on your brand
Your menu and header around it.
  1. Your client signs in to your app With the login they use today
  2. Your app hands over a one-time pass Signed with your own key
  3. Tailwind opens the planning section The pass can’t be used again
02

Signed in with your login

Tailwind keeps no user accounts or passwords of its own. It relies on the sign-in your bank already runs: your app vouches for each client with a signed, one-time pass, and the planning section opens straight away.

That means one less identity system to secure, audit and support, and your app stays in charge of who gets in.

For your tech team
  • Works with your existing sign-in
  • Key rotation without downtime
03

Fed by data you already have

Tailwind speaks the Berlin Group PSD2 format your open-banking interface already produces. Your team passes accounts, balances and transactions on as they are, with no new data model to learn and no mapping layer to maintain.

How and when it flows is up to you.

transaction.json Berlin Group PSD2
{
  "transactionId": "txn-2026-11-05-001",
  "valueDate": "2026-11-05",
  "transactionAmount": {
    "amount": "-1250.00",
    "currency": "EUR"
  },
  "creditorName": "Office Supplies Ltd"
}
One payment, exactly as your open-banking interface describes it.
REST APIs

Send it when it suits you

Your systems decide the timing: as payments happen, overnight or on demand. Retries are always safe, so a dropped connection never leaves duplicates behind.

RabbitMQ events

Stream every change

If your core banking already publishes events, Tailwind can listen in. Clients see changes within moments.

Open banking (PSD2)

Let Tailwind fetch it

Tailwind reads the data through the open-banking interface you already run for third-party providers. Often the quickest route to launch, with nothing new to build.

Any mix

Or combine them

Load the history in one go, then keep it fresh day to day. Every route uses the same format, so there’s still only one data model to work with.

Optional

Accounts at other banks, too

Most businesses bank in more than one place. Switch this on and your clients can add the accounts they hold elsewhere, so the forecast shows their whole cash position.

Your app becomes where they plan the whole business, not just the part that banks with you.

Clients confirm access on the other bank’s own pages, so Tailwind never sees their credentials, and the connected accounts stay up to date on their own.

Runs through a PSD2 account-information provider that you contract with.

04

Running on your servers

You get Tailwind as source code and run it on your own infrastructure, on Kubernetes or any other container platform. Nothing at runtime depends on us: no calls home, no outside service that can fail, and no client data passing through anyone else.

That means your security team can review every line, and your platform team runs it with the tools and processes it already uses, even in restricted build environments.

For your tech team
  • Full source code, yours to review
  • Stateless, so it scales out as usage grows
  • Built for rolling updates
  • Builds in restricted environments

Updates on your terms

Nothing changes in production until your team decides it should. Each update arrives as ordinary commits you can read, scan and test, so it goes through the same change process as your own software, and rolls back the same way.

By the time it reaches you, it has already passed our own automated tests, code checks and vulnerability scans.

  1. Tailwind’s repository
    Tested on every change
  2. Your mirror
    Every change visible as a diff
  3. Your review
    Scans, Tests, Approvals
  4. Your registry
    Images your team built
  5. Your servers
    Live when you decide

Covered by the controls you already have

Client data never leaves your environment, so Tailwind adds no new place for it to live. The GDPR and data-residency controls you already have cover it as they are.

Erased on request

Erasure requests are simple to handle: delete a company or an account, and everything that belongs to it goes too.

Retention you choose

Old records are removed automatically once the period your policy sets has passed, so data never piles up beyond what you need.

A trail for every request

Every request is logged and traceable through your own logs, so audits and incident reviews start with the full picture. Sensitive fields are masked.

Locked to your domains

No one can place Tailwind inside a look-alike site: it opens only within the domains you allow, and only over HTTPS.

Easy to keep an eye on

Your operations team watches it like any other service: health checks plug into your existing monitors, and errors can go to your own Sentry.

Who does what

Your team does what only it can do. We handle the rest.

Your tech team

  • Mirrors the repository and builds the images
  • Runs them alongside PostgreSQL and Redis
  • Adds the planning section to your app and issues the one-time passes
  • Connects the account data: by API, events or open banking

Tailwind

  • Styles the interface to your brand
  • Provides a ready-made image build, including for restricted environments
  • Deploys the standard package with your team, free of charge
  • Gives you a guide for every touchpoint and assists your team throughout the integration
  • Ships updates, support and maintenance, all covered by the quarterly fee

So your planning section can be live within 30 days.

Bring your tech team

In 30 minutes we’ll show how Tailwind would sit in your setup and answer your team’s questions. Prefer to read first? Ask us for the technical specification.