Every system you run.
Connected by i-Con.

i-Con connectors are pre-built components that know how to talk to a specific system, protocol or file format. Combine them into flows, and i-Con moves, transforms and delivers information between core banking, payments, MultiValue databases, messaging, documents and the cloud, without custom point-to-point code.

104components available today

16functional areas

19connectors coming soon

Browse all connectors Request a Demo

What i-Con does

One integration layer between all of your systems.

Most organisations connect their systems one pair at a time. Every new link is custom code that has to be built, tested and maintained, and every system change breaks something downstream.

i-Con takes a different approach. Each system connects once, to i-Con, through a connector. Integration flows are then assembled from those connectors in the visual interface builder, so routing, transformation, scheduling and delivery are configured rather than hand-coded.

Replace or upgrade a system and only its connector changes. Every flow that depends on it keeps running.

Core banking

Payments

MultiValue

i-Con connectors and flows

APIs & channels

Files & documents

Cloud & queues

How connectors work together

Trigger. Connect. Transform. Deliver.

Trigger

A flow starts on a schedule, when an API or HTTP call arrives, when a message lands on a queue, when a file is dropped or when a cloud event fires.

Schedule · API Host · IBM MQ · Azure Event Grid

Connect

Connectors read from and write to the systems involved, using each system’s own interface, whether that is a web service, a database, a file or a host session.

Temenos T24 OFS · SQL Query · SFTP · jBASE Read File

Transform

Data is mapped, validated, translated and enriched along the way, so each system receives information in exactly the format it expects.

XML Translator · JSON Converter · Validator · Text Mapping

Deliver

Results are posted to the target system, published as an event or API response, or turned into documents, emails and SMS messages.

RESTful Service · PDF · SMTP · Send SMS

What you can do with i-Con

Capabilities built from real, production-ready connectors.

Connect core banking and payments

Talk to Temenos T24 through OFS and the Temenos Application Gateway, call Oracle FLEXCUBE web services, and exchange SWIFT, ISO 20022 and AS2805 messages. Drive HPS PowerCARD and Glory teller cash recyclers from the same flows.

Unlock MultiValue and host systems

Read and write records, run commands and call subroutines on jBASE, UniVerse and MVsharp, and reach older hosts over Telnet, SSH and remote commands, without rewriting the applications that depend on them.

Publish and consume APIs

Expose your own REST, SOAP and HTTP services from i-Con, and call any external REST or SOAP API. Systems behind i-Con stay protected while partners and channels get a clean interface.

Move files and data securely

Transfer files over SFTP, SCP and FTP, read and write delimited and fixed-width files and Excel workbooks, bulk-load SQL Server, and compress or encrypt data in transit.

Transform and validate data

Convert between XML, JSON, XSD-driven formats, flat files and character sets. Map values, translate fields and validate data before it reaches the next system.

Work with queues, events and messaging

Send and receive through IBM MQ and MSMQ, publish and subscribe to Azure Event Grid and Event Hub, and reach customers through SMPP, SMS, email and fax.

Generate and deliver documents

Produce PDFs and Word documents, merge and password-protect them, archive output to IBM Content Manager OnDemand, and deliver secure digital statements through Infoslips.

Check credit, compliance and external data

Query CASA, Experian and KreditInform credit bureaus, look up vehicle registrations on eNaTIS, track fleets through Webfleet and pull Reuters market data, all inside your business flows.

Extend with your own logic

When a step needs something unique to your business, drop in C# or Python code, or run an operating-system command, alongside the standard connectors in the same flow.

A flow in practice

Month-end statements, start to finish.

An example of how a bank could combine five connectors into one automated flow, replacing a process that would otherwise need extracts, scripts and manual sending.

Step 1

Schedule

Runs at month-end

Step 2

T24 Extractor

Pulls account activity

Step 3

XML Translator

Shapes the statement data

Step 4

PDF + PDF Encryptor

Builds a protected statement

Step 5

Infoslips / SMTP

Delivers it to the customer

Connect in days, not months

Reuse the same components across flows

Change one system without rewriting the others

Add new connectors as your landscape grows

Connector directory

Find the connector you need.

Search by system, vendor or task, or jump straight to a category. Select any connector to see what it does and what you can configure.

Platform & orchestration

Core banking

Payments, cards & devices

Credit, compliance & customer data

Web services & APIs

Connectivity & protocols

Messaging & queuing

Cloud & eventing

Email, SMS & fax

Database

These connectors aren't limited to SQL Server. The same components connect to jBase, Oracle, MySQL, UniVerse and other ODBC or ADO.NET accessible databases.