Frequently asked questions

Does Strovia sit between us and our counterparty?

No. The standard has you exchange messages directly through its REST API, and that doesn’t change. Strovia is your SIVI system: it sends with your credentials and receives on endpoints registered in your name.

Why not connect directly with our counterparty ourselves?

You do connect directly. The question is who builds and runs the system on your side. That system needs:

the API client and server, certificates and the feedback scenarios;
strict validation, chunking and conversion to your formats;
annual release changes, monitoring and audit evidence.

Strovia provides all of that, so you don’t have to build and maintain it.

What does our counterparty need to do?

Register your endpoints, certificates and IP addresses, as for any new connection. Strovia prepares a registration pack with all the details.

How does Strovia reach our internal systems?

Through downloads, the API, or a small connector agent in your network that only connects outwards: no inbound firewall ports. You can also run Strovia in your own environment [FOUNDER TO CONFIRM TIMING].

Do we have to use Strovia for every message?