---
title: "Integrations &amp; transports"
url: "https://dev.ionova.ai/integrations"
image: "https://dev.ionova.ai/_og/d/c_Ocean.takumi,title_~SW50ZWdyYXRpb25zICYgdHJhbnNwb3J0cw,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMyRTUwOTAifX19,p_Ii9pbnRlZ3JhdGlvbnMi,s_1mtLaahw73jGDxFP.png"
---

Integrations

# Reach ARS _however you run_.

Call ARS over REST or wire it into the rails you already operate — message queues, streams, file drops, the database, or an MCP client. It deploys as a sidecar, so nothing rips and replaces.

Seven _transports_Same engine, whichever way you connect.

| Transport   | Use it when                                                                      |
| :---------- | :------------------------------------------------------------------------------- |
| REST        | Synchronous request/response — the default for at-entry and pre-submission checks. |
| MCP         | An AI agent or assistant calls ARS as a tool. See SDKs & tools.                  |
| IBM MQ      | Enterprise message-queue integration into existing payment middleware.           |
| Kafka       | High-throughput streaming of messages through the engine.                        |
| SFTP        | Scheduled bulk file drops — host-to-host and batch remediation.                  |
| JDBC        | Direct master-data cleansing against a database.                                 |
| File Upload | One-off or ad-hoc batch correction without a standing integration.               |

Pre-built _connectors_Drop-in adapters for the platforms you already run.

| Connector             | Platform                            |
| :-------------------- | :---------------------------------- |
| MuleSoft Anypoint     | Integration / iPaaS flows           |
| Volante VolPay        | Payment processing & transformation |
| Finastra FusionFabric | Core banking & payments             |
| SWIFT Alliance        | Network access & messaging          |

**Sidecar by design —** ARS deploys _beside_ your ERP, TMS, payment engine or hub — no core replacement. Your PII never leaves your infrastructure, and you adopt it one channel at a time.

Where next

[SDKs & MCP](https://dev.ionova.ai/tools)[Channels](https://dev.ionova.ai/channels)[Find your path](https://dev.ionova.ai/solutions)[API reference](https://dev.ionova.ai/apis)