02
Architecture
From the account to the rail.
Many institutions still stitch a domestic core, a payments hub, and a card processor. Cush Core is the book, the agents, and the rails, licensable under your name.
Four layers
Layer 01
Products under your licence.
Accounts, cards, lending, payments, and payroll are configured as governed blueprints and issued in your name. Customers see your brand. Supervisors see your books.
- Current accounts, savings, cards, credit, and SME lending
- Cross-border payments and payroll as first-class products
- Product blueprints issued in hours, not a change programme
- White-label under the institution’s licence
Catalogue
What the institution can issue.
Each product is a governed blueprint on the same ledger. Customers see the institution. The examination sees one book.
01
Accounts and savings
Issue current and savings accounts in the institution’s brand, on books you can examine.
02
Cards
Debit and credit programmes with the same ledger, the same policy, and the same replay.
03
Lending
Retail and SME credit without a second origination stack sitting beside the core.
04
Payments and remittance
Clearing, RTGS, instant schemes, correspondent books, and remittance as products you offer, on the same ledger as the account.
05
Onboarding and KYC
Identity, screening, and a guided application journey, ready on day one.
Onboarding
From application to account, every decision kept.
Apply, verify, assess, approve, activate. Identity is checked through integrated KYC providers, then risk grading, PEP and sanctions screening and eligibility rules are evaluated. The workflow routes each case to the right approver and stores every decision for audit and dispute resolution.
06
Embedded APIs
Interfaces so partners can embed accounts and payouts inside their own products.
Catalogue
Define once. Issue many times.
Products are versioned blueprints, with pricing, eligibility and features set at blueprint level and tailored by segment, selling entity or channel. A pricing or eligibility change needs no code and never breaks a contract already issued. Families include current accounts, savings, loans, mortgages, cards, fixed rate bonds, car and secured loans, retail bonds, ETFs and OTC derivatives.
Operator control centre
One portal for the whole operation.
Cush Core gives operations a single secure portal: Customer 360, product management, onboarding workflows, a ledger explorer, an agent studio for AI agents, management information, a network graph and access management. Every action in it is traceable. No spreadsheets and no separate tools.
QCan operations staff inspect the ledger themselves?+
Yes. The ledger explorer shows every transaction, every event and every chain, without a database query.
Scale
Scale out, not up.
Stateless services scale independently by adding instances. Each business object owns its own chain, so many objects are processed in parallel, with automatic failover to spare nodes and specialist workloads routed to the right node. PostgreSQL gives ACID guarantees at the data layer, and rolling deploys avoid customer facing downtime.
Product blueprints · hours, not programmes
Configure a licence.
Select the products an institution will issue. The JSON is the contract the control plane executes. It is not a slide.
Booking entity
Catalogue
2 products on this blueprint.
blueprint.json
{
"issuer": "Your Bank",
"entity": "UK Ltd",
"products": [
"Current accounts",
"Debit cards"
],
"ledger": "BLAKE3",
"policy": {
"owner": "institution",
"aml": "in-flight",
"replay": true
},
"rails": {
"in": [
"FPS",
"SEPA",
"Fedwire",
"SWIFT"
],
"out": [
"CHAPS",
"TARGET2",
"FAST",
"PIX"
]
}
}Contract
The contract is the product.
In the Cush Core design, every product is a versioned blueprint, and every payment, fee and interest accrual runs as a smart contract bound to it. Each sale creates a customer instance of the contract, not a copy of the code. A new version never breaks a contract already issued.
QIs a product a configuration or a contract?+
A contract. The blueprint states the terms and the smart contract engine executes them. Legal agreements, interpretation and discretion stay with the institution and its counsel.
Brands and entities
Several brands. One book.
Cush Core separates three roles: the provider that operates the platform, the selling entity whose brand the customer sees, and the manufacturing entity that holds the product licence and originates the product. Strict data separation holds between every entity on the platform. A new brand or partner channel reuses the same core instead of a new stack.
QCan we run more than one brand on Cush Core?+
Yes. Each brand sells through its own selling entity, products are held by the manufacturing entity, and data is kept strictly separate between them. Customers see the brand they chose. Supervisors see the books of each entity.
Smart contract execution
Every transaction, replayed exactly as it ran.
In the Cush Core design, every financial operation, whether a payment, a fee or an interest accrual, is a smart contract bound to the product catalogue. Contracts are built from reusable pipelines, every version is immutable, and any execution can be replayed exactly as it ran on day one. The institution can show a transaction was correct without asking a developer.
QCan we prove how a past transaction was calculated?+
Yes. The contract version that ran is immutable and the execution is recorded on the ledger with actor, time and outcome. Replay it and the same inputs give the same result.
Adoption
Sidecar, replatform, or greenfield.
The same licensable core. Three ways in, so the board does not have to bet the house on a weekend.
01Sidecar (coexist)
Sit beside the incumbent core.
For digital brands and banks that will not rip and replace. Stand up a digital book, a correspondent product, or a new geography first. Evidence first. Leave the back book untouched until the institution decides otherwise.
02Replatform
Migrate a line of business without a franchise freeze.
Move one book onto Cush Core while the rest of the house continues. Dual-run, then cut. No weekend cutover of the entire estate.
03Greenfield
Licence a new entity from the first posting.
A subsidiary, digital bank, or payments entity. Accounts, cards, lending, and rails under your name from day one.
Connectivity
On-ramp in. Off-ramp out.
Faster Payments, SEPA, Fedwire, cards, and SWIFT inbound. CHAPS, TARGET2, FAST, PIX, and SWIFT outbound. Routing follows rules you set. The ledger is the book.
On-ramp
Credits post to the customer account on the same ledger as the rest of the book.
FPS
Faster Payments
Instant inbound · United Kingdom
On-ramp. Sterling credits post to the customer’s account on the same ledger that holds the rest of the book.
SEPA
SEPA
Euro inbound · Europe
On-ramp. SEPA credit transfer on the euro book. Same policy, same replay, same entity isolation.
ACH
Fedwire / ACH
Dollar inbound · United States
On-ramp. Dollar clearing on the US entity. Dual-control and velocity rules stay in the mandate you write.
CARD
Card acquiring
Scheme inbound · Global
On-ramp. Card present and not-present credits land on the ledger as first-class postings, not a sidecar processor.
SWIN
SWIFT inbound
Correspondent in · International
On-ramp. MT and ISO 20022 credits scored and posted before the nostro is touched.
Off-ramp
Instructions leave only after the ledger post and the agent trace.
CHAPS
CHAPS
Sterling RTGS · United Kingdom
Off-ramp. Same-day high-value settlement under standing mandate, not a second payments hub.
TGT
TARGET2
Euro RTGS · Euro area
Off-ramp. High-value euro beside SEPA. One control plane for wholesale and retail.
SWOUT
SWIFT outbound
Correspondent out · International
Off-ramp. Correspondent instructions leave only after the ledger post and the agent trace.
FAST
FAST
Instant outbound · Singapore
Off-ramp. Instant Singapore dollar with name enquiry before confirmation. The customer sees your brand.
PIX
PIX
Instant outbound · Brazil
Off-ramp. Instant Brazilian real, routed on cost, success rate, and policy with the rest of the book.
Payments processing
From instruction to settlement, in one place.
In the Cush Core design, each payment is a ledger command, recorded from instruction to confirmation. Smart contracts validate scheme confirmations and post settlement events automatically, and a dedicated payments service applies scheme rules, cut offs and retries. Shadow ledger sync keeps an existing core or accounting system in step.
Rails
Faster Payments, Bacs Direct Debit and Direct Credit, SEPA Credit Transfer, SEPA Instant, SWIFT gpi, Mastercard and Visa card rails, and internal book transfers.
QMust we retire our existing core to use Cush Core payments?+
No. Shadow ledger sync keeps an external core banking or accounting system in step automatically.
Commercial terms, including the per-customer model, are set in the briefing and recorded under Governance.
Discuss a licenceOpen banking
Open banking, with consent on the record.
Cush Core includes account information and payment initiation APIs, a consumer API for mobile and web, and a provider API for third party providers. The consent lifecycle is managed and audited, and every consent grant carries its own scoped access token.
QHow is customer consent tracked?+
Each consent is managed through its full lifecycle and audited, and access is scoped to the consent that granted it.
