Skip to content
Bitween AI is on the way

Financial services

Payments, statements and partner APIs, with the controls your auditors expect.

Banks, fintechs and insurers integrate with corporate clients, payment hubs, KYC providers and core systems that can't go down. Bitween keeps that traffic in your own infrastructure, retries only what is safe to retry, and records who changed every rule.

Talk to an architectRead the docs

The challenge

What makes financial services integration hard.

01

Retries can cost money

A blind retry of a payment can duplicate it. Retry decisions must be explicit, capped and explainable.

02

Core systems are sacred

Integrations must reach core databases and services without broad credentials or ad-hoc SQL.

03

Change control is mandatory

Every change to an integration needs an owner, a timestamp and a before-and-after.

Flows you can run today

How Bitween handles it.

Each flow below uses capabilities that exist in Bitween now, with links into the documentation that describes them.

Flow 1

Payment instructions from corporate clients

Clients post JSON payment instructions to a sync API gateway with their partner key. A validator checks them before anything is stored, and the rules-based mapper produces namespaced XML, such as ISO 20022-style messages, for the payment hub.

  1. 1Sync API gateway
  2. 2Validator
  3. 3JSON → namespaced XML
  4. 4Deliver
  5. 5Response to client

Flow 2

Safe retries by design

A retry policy blocks retries for validation and business errors and allows capped, exponential retries only for transient network failures. Each exchange can be retried once, so attempts form a single chain you can audit.

  1. 1Match the error
  2. 2Block business errors
  3. 3Allow transient · capped
  4. 4One chain of attempts
  5. 5Alert when spent

Flow 3

Core banking events without ad-hoc SQL

Named, database-checked statements poll transaction tables with bound parameters only. People who write statements never get the right to change credentials, and new transactions are published as events to RabbitMQ.

  1. 1Named statement
  2. 2Bound parameters
  3. 3Incrementing cursor
  4. 4Map
  5. 5Publish to RabbitMQ

Controls that matter here

Capabilities behind the flows.

Change history with before and after

The audit trail records who changed which subscription, policy, partner or role, with the old and new value of every property.

Docs

Evidence for every message

Each exchange keeps its input, mapped output and response, its result, and the reason any retry was or was not scheduled.

Docs

Inside your perimeter

Self-hosted on your Kubernetes or VMs, with Azure managed identity for SQL and PostgreSQL connections.

Docs

Separation of duties

Custom roles combine permissions like exchanges.operate or retry-policies.edit, and the last administrator can never be removed.

Docs

Good to know about formats and scope

Bitween maps JSON and XML natively, including XML namespaces. Payment scheme connectivity such as SWIFT or card networks is not built in; it connects through HTTP, file or custom adapters.

Related use cases

Go deeper on the patterns.

API gateway for partners

One HTTPS endpoint per business process: sync when partners need an answer, async when they need speed.

ERP & database sync

Poll named SQL statements into exchanges and write deliveries back to tables and procedures.

Event-driven integration

Consume from RabbitMQ and Amazon SQS, route by content and chain flows by message type.

Plan your financial services integrations with us.

Share your partners, systems and volumes. We'll show you how the flows would run on Bitween in your own environment.

Talk to an integration architectRead the docs