Introduction
One API over PISPs, aggregators, meta-providers and bank APIs. What Unirail does and how the pieces fit together.
Unirail is the routing layer between platforms that move money and the providers that can move it. Your backend integrates once with the Unirail API; Unirail turns that into calls to whichever providers you've connected, finds and prices the routes between accounts, initiates payments along those routes, and normalises everything the providers send back into one event stream.
Four surfaces, one product
- The API and SDK (
api.unirail.dev,@unirail/sdk) is what your backend calls: institutions, customers, bank links, accounts aspayto://addresses, route quotes, payment intents with legs, and events. - The dashboard (
app.unirail.dev) is where you manage environments, API keys, provider connections, routing policy, webhook endpoints and the event log. - Secret federation keeps your provider credentials in your own vault. Unirail reads them from Infisical through OIDC federation and never stores them.
- The marketplace (unirail.dev/providers) lists every provider Unirail has integrated or researched, with coverage, custody, who is regulated and how onboarding works.
The objects
| Object | Id | What it is |
|---|---|---|
| Customer | cus_… | Your user, by reference. Unirail never does your KYC. |
| Institution | ins_… | A bank, merged across every provider that reaches it. |
| Link session | lnk_… | One attempt to link a customer's bank account through a provider. |
| Account | acct_… | Somewhere money can come from or go to, with masked payto:// addresses. |
| Route quote | qt_… | A priced route between two accounts, with a digest to bind approval to. |
| Payment intent | pi_… | A payment along an approved quote, made of legs. |
| Leg | leg_… | One hop of a payment on one rail, recording who holds the money after it. |
| Event | evt_… | Something that happened, delivered by webhook and replayable from /v1/events. |
Everything belongs to exactly one environment, and the API key you call with decides which.
What's integrated today
Plaid, Yapily and Enable Banking ship with adapters verified against each provider's sandbox. Every other provider in the marketplace is listed: researched from public documentation, with no adapter yet. Routes today run bank to bank with no one holding the money in between.