WHAT IT IS
FlowCore handles the origination and authorisation of domestic and international payments, with compliance checks and approval flows configured by the bank. It connects the core banking system to the payment networks through adapters, with live integrations with Essence, Banka, EMIS, SWIFT and BNA. It can run as SaaS or on the bank's own infrastructure, and supports SWIFT MT and ISO 20022.
THE PLATFORM
Every order in progress with direction, purpose, originator, beneficiary and an explicit status - pending signature, in progress, completed, rejected or returned.
Every step of the approval chain with timestamp, owner and comment - submission, holds, manual approvals and automatic execution.
A single dynamic form for domestic and international payments - customer and entity, purpose, processing mode, source account and beneficiary - before the review step.
Configuration by region, country and currency, with the order of use per bank and a side panel to manage countries and default currencies.
Upload a PSX or PS2 file and follow the four steps - file, validation, authorisation and review - in one operation.
WHY IT MATTERS
One platform to originate, validate and authorise domestic and international payment orders - document checklists, automatic compliance flagging and approval workflows the bank configures itself. Beyond the bank itself, the last-mile connectivity engine takes over. The same FlowCore sits on top of the core already in place and settles into whichever clearing house the market happens to use - EMIS in Angola, SWIFT, the central bank, another domestic switch.
ADVANTAGES
Origination, validation and authorisation of payments in a single flow - no switching between multiple screens or parallel systems.
AML, risk lists and due diligence applied directly at origination - not as a separate check after the fact.
Forms, document checklists, notifications and approval matrices designed and maintained by the bank itself, via BPM/DMN - with no dependency on the vendor.
SWIFT MT and ISO 20022 side by side - the global SWIFT migration stops being a disruptive project.
FEATURES
Origination by operation type: a single dynamic form that adapts to the nature of the payment, reducing input errors.
Configurable document checklist: the bank defines, per operation type, which documents are required, optional or confirmation-only.
Automatic customer flagging: list checks at the start of the operation to surface cases that need review.
Configurable approval workflow: authorisation matrices per operation type, designed in BPM/DMN by the bank itself.
Automatic risk validation: currency, high-risk country, purpose and due diligence checked before proceeding or routing to manual review.
Direct debits (SDD): enrolment, account debit authorisation and debit instruction - live over EMIS today, and portable to another domestic switch through the same adapter.
Architecture built for mission-critical payment operations - from origination to execution, with compliance built into every step.
BUILT FOR
Transfers, debits and credits processed at scale, with a need for structured origination and authorisation.
Corporate operations (capital, payroll) and retail operations managed in the same flow, with segment-specific rules.
Multiple customers and entities managed at once - branch, agency banking and digital channels on the same engine.
AML, risk lists and regulatory reporting handled inside the approval flow itself, not as a separate system.
HOW IT WORKS
Customer or operator starts the payment order, with a document checklist and automatic compliance flagging.
Rules engine checks currency, high-risk country, purpose and due diligence, deciding to proceed or route to manual review.
Configurable workflow moves the operation through the authorisation levels defined by the bank.
Hand-off to the bank's core and to the destination rail - EMIS, SWIFT, the central bank, another local switch - with automatic confirmation and reconciliation.
INM's payment processing engine: origination, authorisation (compliance plus configurable approval workflows) and last-mile connectivity for domestic and international payments. It runs on the core the bank already has instead of replacing it, and hands off to each market's clearing house through an adapter.
Yes. The core connection is adapter-based - Banka, Finastra Essence, an in-house legacy system, whatever is already there - over API/ISO, with no change to the central system. The domestic side works the same way: each market's clearing house, EMIS in Angola included, plugs in through an adapter.
Both. Banks in markets with data-residency requirements usually choose on-premise; SaaS where regulation allows it.
Yes - the engine is natively multi-protocol (SWIFT MT and ISO 20022 / PS2-PSX), which lets you migrate message formats without disrupting the origination and approval workflows you already have configured.
INM's own teams - we don't subcontract implementation. The same team runs, evolves and supports the product 24/7 after go-live.
Talk to our team to see how this product fits your ecosystem.