Unirail decides which provider and rail each payment, bank link or identity check should use, what it will cost under your own contracts and why. It also connects to your providers, reads their credentials from your vault and tracks your contracts with them.
Provider credentials are read from your Infisical, the secrets manager Unirail supports today. Adding a provider doesn't mean adding environment variables to every service.
Unirail keeps a versioned record of each provider contract, with its fees, volume tiers and renewal dates. You can see what each provider costs you and what switching would save.
For each payment, bank link or identity check, Unirail returns the provider and rail to use, its cost under your contracts, the ETA, the success likelihood, ranked alternatives and the options it ruled out with reasons.
What stays with you
Unirail never holds or moves funds and isn't the regulated party.
The money, moved between banks under your providers' licences
Your own licences
Your contracts with each provider and their fees
Your provider credentials, kept in your own vault
Your compliance duties: KYC, AML, sanctions and record keeping
Provider credentials live in your own Infisical. In Decide mode they never leave your platform. In Execute mode
Unirail authenticates to Infisical with OIDC, reads a credential and keeps it in memory for up to five minutes. It
never writes it to disk. If you revoke the grant, new reads will stop.
Every routing decision gives its reasons for the provider it chose, such as the price under your contract, how similar
payments have gone and your preference. It also lists every provider it ruled out with the reason.
Each claim in the catalogue that a provider offers a capability in a country links to its source, usually the
provider's own documentation. Most claims also carry the date they were checked. Corrections are recorded in the
changelog, including one to Enable Banking's UK coverage.