Agentic Aı for banking.
Squids run operations across the bank, from the loan application to the missing payment. Marrinn builds onboarding, review and case systems for banks and building societies, and connects them to the core banking platform, the CRM and the payment systems you already run. An underwriter, a compliance officer or an operations lead approves. Ledger records who did what.
Keep your core banking system. See every customer on one live map.
Core banking, the CRM and the KYC files stay where they are. TagFlow keeps a current copy of each, matches their records, and Squids work from the result.
Banking operations, built around how you run it.
Each module a bank runs, and where it comes from: built for you by Marrinn, in TagFlow today, or the system you already run, connected.
Select a module
In TagFlow, extended for you
KYC and customer onboarding
Identity, ownership and source of funds checks, with a risk rating.
A Squid reads registry, ownership and adverse media, pre-fills the file and asks the client only for missing documents. The compliance officer approves.
The FCA fined Starling Bank £28,959,426 for failures in sanctions screening and high-risk onboarding.
Built for you by Marrinn
Lending and credit memo
Application intake, policy checks, credit memo and offer.
A Squid reads accounts and bureau data and drafts the credit memo with its reasoning. The underwriter approves.
The application, the policy checks, the credit memo and the underwriter's decision sit on one record.
Your system, connected
Financial crime alert review
One case view for each AML alert, sanctions hit and report draft.
A Squid gathers the customer file and history for an alert and drafts the case note. The MLRO approves.
The NCA received 872,048 suspicious activity reports from April 2023 to March 2024.
Built for you by Marrinn
Complaints and redress
Complaint log, eight-week clock, redress calculation and final response.
A Squid pulls account history, suggests a root cause and drafts the final response. The senior complaints handler approves.
The Financial Ombudsman received 214,600 new complaints in 2025/26, and 18,900 were current account fraud and scams.
Built for you by Marrinn
APP fraud claims
Triage, evidence and reimbursement decision for scam claims.
A Squid gathers payment and customer records and recommends a decision with the rule cited. The senior fraud analyst approves.
By the end of 2025, £243m had been paid back to APP scam victims under the PSR reimbursement rule.
Built for you by Marrinn
Arrears and vulnerable customers
Early contact, forbearance options and the vulnerability record.
A Squid drafts a contact plan from the customer record and vulnerability flags. The collections team leader approves.
Each contact, forbearance option and vulnerability note is kept on the customer's record with its date.
In TagFlow, extended for you
Regulatory reporting
Return builds, ledger reconciliation and sign-off tracking.
A Squid reconciles return lines to the ledger and flags breaks before sign-off. The finance director approves.
Each return line is reconciled to the ledger, breaks are flagged, and sign-off is recorded by name.
- Built for you by Marrinn
- In TagFlow today
- Your system, connected
KYC and customer onboardingIn TagFlow, extended for you
In TagFlow, extended for you
KYC and customer onboarding
Identity, ownership and source of funds checks, with a risk rating.
A Squid reads registry, ownership and adverse media, pre-fills the file and asks the client only for missing documents. The compliance officer approves.
The FCA fined Starling Bank £28,959,426 for failures in sanctions screening and high-risk onboarding.
Lending and credit memoBuilt for you by Marrinn
Built for you by Marrinn
Lending and credit memo
Application intake, policy checks, credit memo and offer.
A Squid reads accounts and bureau data and drafts the credit memo with its reasoning. The underwriter approves.
The application, the policy checks, the credit memo and the underwriter's decision sit on one record.
Financial crime alert reviewYour system, connected
Your system, connected
Financial crime alert review
One case view for each AML alert, sanctions hit and report draft.
A Squid gathers the customer file and history for an alert and drafts the case note. The MLRO approves.
The NCA received 872,048 suspicious activity reports from April 2023 to March 2024.
Complaints and redressBuilt for you by Marrinn
Built for you by Marrinn
Complaints and redress
Complaint log, eight-week clock, redress calculation and final response.
A Squid pulls account history, suggests a root cause and drafts the final response. The senior complaints handler approves.
The Financial Ombudsman received 214,600 new complaints in 2025/26, and 18,900 were current account fraud and scams.
APP fraud claimsBuilt for you by Marrinn
Built for you by Marrinn
APP fraud claims
Triage, evidence and reimbursement decision for scam claims.
A Squid gathers payment and customer records and recommends a decision with the rule cited. The senior fraud analyst approves.
By the end of 2025, £243m had been paid back to APP scam victims under the PSR reimbursement rule.
Arrears and vulnerable customersBuilt for you by Marrinn
Built for you by Marrinn
Arrears and vulnerable customers
Early contact, forbearance options and the vulnerability record.
A Squid drafts a contact plan from the customer record and vulnerability flags. The collections team leader approves.
Each contact, forbearance option and vulnerability note is kept on the customer's record with its date.
Regulatory reportingIn TagFlow, extended for you
In TagFlow, extended for you
Regulatory reporting
Return builds, ledger reconciliation and sign-off tracking.
A Squid reconciles return lines to the ledger and flags breaks before sign-off. The finance director approves.
Each return line is reconciled to the ledger, breaks are flagged, and sign-off is recorded by name.
Already on Temenos, nCino, Fenergo or Salesforce? Keep it, or run it on Marrinn.
Squids read from the system you run today. Where TagFlow has the module, you move that work across; where it does not, Marrinn builds it from your requirements.
- Temenosor built by Marrinn
- Thought Machineor built by Marrinn
- Mambuor built by Marrinn
- Finastraor built by Marrinn
- nCinoor built by Marrinn
- Fenergoor TagFlow KYC
- Salesforceor TagFlow CRM
- Microsoft Dynamicsor TagFlow CRM
- Fiservor built by Marrinn
- TCS BaNCSor built by Marrinn
Where banking work slows down, and what it costs.
Published figures on what slow onboarding, outages and failed controls cost a bank.
- 803 hoursof cumulative outage across nine major UK banks and building societies, January 2023 to February 2025Treasury Committee, from the firms’ own written responses, 2025.
- 56%of online payments failed during the Barclays outage of 31 January to 2 February 2025Treasury Committee, Barclays letter of 26 February 2025; Computer Weekly, February 2025.
- £48.65mfine for TSB over its April 2018 platform migrationFCA and PRA final notice press release, December 2022.
- £3.3bnforecast UK bank spend on legacy systems in 2026The Banker, citing a SaaScada survey of 150 banks.
Each system acts on half the picture.
- 1Two systems
- 2One acts alone
- 3What goes wrong
- 4The Digital Twin
- 5A person decides
Aisha Rahman is in Temenos and Fenergo. Each holds a different fact.
The payment system raises an alert and waits. It cannot see what Fenergo knows.
The alert sits in a queue. The bank either freezes her account without asking, or misses a check it must make.
The Digital Twin puts both on one record for Aisha Rahman and flags the clash.
The financial crime analyst approves a request to Aisha for proof of funds. Nothing goes out before that.
TemenosCore bankingActing now
£48,000 credit. Her usual is £3,200.
FenergoKYC file
Proof of funds needed over £25,000.
Nobody sees itLarge credit, no proof of funds on file
FlaggedLarge credit, no proof of funds on file
The cost of not having a Digital Twin.
Each system acts on what it can see. These mistakes happen in the gaps between them.
- Required checks missedA sanctions alert in one system never reaches the payment in another.ScreeningPayments
- Good customers frozenAccounts are blocked before anyone reads the customer's file.ScreeningCRM
- Fraud paid outThe payment leaves before the fraud flag reaches the payments team.FraudPayments
- Loans approved on half the factsAn underwriter approves a loan without the arrears held elsewhere.LendingCollections
- Two answers to one complaintTwo teams reply to the same customer and say different things.ComplaintsCRM
- Days to answer the regulatorEach answer is rebuilt by hand from four systems.Every system
Keep the systems you run. TagFlow joins each customer’s records into one page, and Squids work from it.
Aisha Rahman is CIF 004417 in Temenos, KYC-90213 in Fenergo and A. Rahman, contact 55812, in Salesforce. TagFlow matches the first two exactly; the Salesforce record scores 84 percent on birth date and postcode and a person confirms it, so TagFlow keeps one page for her, linked to alert FC-2026-0912, the £48,000 credit, her usual monthly credit of £3,200 and the source of funds rule for credits over £25,000. At 09:12 Temenos reports a £48,000 credit to her current account. KYC Squid checks her ID and address in Fenergo and finds both current. Financial Crime Squid drafts the case note from the Temenos history and cites the rule. Contact Squid drafts a source of funds request to the contact details in Salesforce, found under A. Rahman. The financial crime analyst approves the request for Aisha and 11 others at 09:26. At 09:27 the request for Aisha is sent, the 11 others the same, and Temenos is unchanged.
- Match her records
- Credit reported
- Squids work
- Analyst approves
- Aisha reviewed
Temenos stays where it is. TagFlow keeps a current copy. How we connect what you keep →
Squids that know how your organisation runs.
Before a Squid acts, it reads the record, its history, your procedures and the duty that applies. Then it hands the work to the next module, and a named role decides.
A customer reports a scam at 10:42. The evidence, the rule and the refund are ready for a fraud analyst by lunchtime.
Mobile app and core bankingFraud case APP-2026-3318Customer reports a £6,800 Faster Payment to a new payee as a scam
AWhat the Intake Squid reads first
- RecordCore banking£6,800 Faster Payment, new payee, 09:58 today
- HistoryCRMNine years a customer, no earlier fraud claim
- PolicyFraud claims procedure v4Refund above £5,000 needs senior analyst sign-off
- PeopleShift rosterFraud analyst on shift, senior analyst as delegate
BSquids across your modules
Service DeskIntake SquidOpens the case and starts the decision clockHands to Evidence Squid
Fraud case management, built to orderEvidence SquidGathers payment records and drafts the recommendationHands to Finance Squid
TagFlow FinanceFinance SquidDrafts the refund journal and the customer letter
CWho decides
LedgerEvery step, with the time and the role
A complaint arrives by email. The history, the redress and a draft final response reach a senior handler with weeks to spare.
Shared complaints inboxComplaint 2026/0317Customer complains about repeated overdraft charges after a payment was returned
AWhat the Complaints Squid reads first
- RecordCRMComplaint 2026/0317, received 20 Oct, via email
- HistoryCore bankingThree overdraft charges, £24 each, in 60 days
- HistoryService DeskCustomer contacted us twice on this in October
- PolicyRedress policy v6Handlers refund charges plus interest up to £500
BSquids across your modules
Service DeskComplaints SquidLogs the complaint, starts the clock, links the historyHands to Redress Squid
TagFlow FinanceRedress SquidCalculates the refund and interest, drafts the journalHands to Response Squid
Document StudioResponse SquidDrafts the final response with the right to refer
CWho decides
LedgerEvery step, with the time and the role
A loan payment is missed. The Squid sees the bereavement note first, and the plan that reaches the customer is a kind one.
Core banking, collections feedArrears A-2026/2207£284 loan instalment missed on 14 Oct, balance £9,500
AWhat the Arrears Squid reads first
- RecordCore bankingPersonal loan, £284 instalment returned unpaid
- HistoryCRM call notesCustomer mentioned a bereavement three weeks ago
- HistoryCore bankingFirst missed payment in 31 months
- PolicyArrears policy v5Vulnerability flag means specialist team, no collections call
BSquids across your modules
Collections, built to orderArrears SquidReads the missed payment and checks the flagsHands to Support Squid
TagFlow CRMSupport SquidRoutes to the specialist team and drafts a kind messageHands to Finance Squid
TagFlow FinanceFinance SquidModels a reduced payment plan and its schedule
CWho decides
LedgerEvery step, with the time and the role
What Marrinn runs for a bank.
Every part runs under one permission model, with one record of every action.
Onboarding, KYC and review workflows
Case systems for client onboarding and periodic reviews, with checklists, approval gates and deadlines.
Workflow and approvals
Approval gates, reminders, escalation and service level targets by priority, with business-hours calendars.
Squids for the front and back office
Agents that read, draft and chase inside the permissions you set and a budget you control.
Records and audit trail
Every action is recorded with who approved it. Exports and a configurable retention period are supported.
Legacy migration
Move records out of a legacy system in dry runs before anything is switched over.
Voice agents for the contact centre
Agents that answer the call, having already read the number and pulled the caller’s record. 31 languages per agent, about 90 percent of the world’s population.
Reports and board packs
Cases by stage, deadlines met and backlog by team, with plain-English queries.
Secrets for connected systems
Encrypted credentials, rotation and an access log for every system a Squid connects to.
Systems built to your requirements
Custom software built in short rounds, with a first working, secure version in about 10 days.
The rules your systems have to show they follow.
Marrinn builds the records and controls that show a bank follows the rules it is held to.
- FCA Consumer DutyFirms must show good outcomes on products, price and value, understanding and support, and report on it to the board each year.
- Senior Managers and Certification RegimeNamed senior managers are accountable for each function.
- Operational resilience, PS21/3 and SS1/21Firms identify important business services and set impact tolerances, in force since March 2025.
- Critical Third Parties regimeRegulators oversee the technology suppliers that many firms depend on.
- DORAEU digital operational resilience rules for EU entities and groups.
- Money Laundering Regulations 2017, POCA and JMLSG guidanceUK anti-money laundering law and sector guidance, with suspicious activity reports sent to the NCA.
- PSR APP fraud reimbursementMost victims of authorised push payment scams are reimbursed within five business days, under the rules in force since October 2024.
- DISP complaint rulesEight weeks to a final response, then the Financial Ombudsman.
- UK GDPRA lawful basis for each use of data, retention rules and subject access requests answered in one month.
- Consumer Credit Act and CONCRules on credit agreements, affordability and arrears handling.
rules answered from one record: who, what, when and why. You show it. You do not rebuild it.
Built for regulated work, and ready in about 10 days.
Marrinn built KYC and CRM for Arzan. The same platform and build method apply to a bank: your requirements, short rounds of change and your sign-off.
Arzan
Arzan is an investment company, not a bank. Marrinn built its KYC checks and CRM, with one client record from first contact to an approved account. Bank onboarding and review is the same kind of work.
See what was built →- 01
The same method for a bank
Onboarding, review and case work run on the platform and the short rounds of change used for Arzan, built to your requirements and your sign-off.
- 02
A first version in about 10 days
A first working, secure version in about 10 days, then rounds of change until you sign it off.
- 03
Your core stays in place
Squids work through connections to the core banking platform, CRM, payment and document systems you already run.
- 04
Legacy retired on your timetable
Marrinn Migrate moves records in dry runs, so a legacy system is switched off when you are ready.
- 05
Hosting you choose
On our cloud, in your own cloud account or on your own servers.
- 06
A record for every action
Each action carries the time, the role and the approval, so the evidence is ready when a regulator asks.
- £48.65mfine for one platform migration that failedFCA and PRA final notice, December 2022.
- 6+ weekstypical onboarding for a UK corporate bankFenergo, 2025 Financial Crime Industry Trends Report (vendor-commissioned).
- 5 business daysin which most authorised push payment scam victims are reimbursedPayment Systems Regulator, rules in force from October 2024.
Hosted where your security policy requires.
Licensing and hosting are agreed before the first round of work begins.
- Our cloudHosted and run by Marrinn
- Your cloud accountIn your own tenancy, under your keys
- Your own serversOn your premises, with your records on your hardware
Licensed per user. You own your data and can export it at any time.
Questions a bank asks first.
Questions buyers ask before a demo.
Can Marrinn connect to our core banking platform and CRM?
Yes. Squids work through connections to the systems you already run. Which systems to connect first is decided in the discovery session.
Does a Squid make credit or compliance decisions?
Decisions stay with people. A Squid reads, drafts and chases, a named role that you set, such as an underwriter or a compliance officer, approves each action, and the Ledger records who approved it and when.
Can Marrinn build for a bank?
Yes. Marrinn has delivered KYC checks and a CRM for Arzan, a risk management system for National Investment Company and a correspondence and business process system for Kuwait Municipality. Banking work is the same kind of work: cases, approvals, connected systems and one record of every action, on the same platform and the same build method. The first working, secure version arrives in about 10 days, so you can judge it on your own onboarding or lending process before you commit.
How soon do we see a working system?
A first working, secure version in about 10 days, then rounds of change until you sign it off.
Do we have to replace our core in one move?
Marrinn connects to what you run first. A legacy system is retired when its records have been moved and checked in a dry run.
Where is our data held?
On our cloud, in your own cloud account or on your own servers. You choose, and you can export your records at any time.
See a banking workflow run on your own cases.
Thirty minutes with the Marrinn team. Bring the process that takes your team longest. We reply within one UK business day.
