Marketplace preview · 13 providers, 3 integrated

One API for every payment rail.

For example: I need payment initiation in the UK.

Unirail sits between your app and the providers that move money, check accounts and verify people, in every country they cover. Connect the ones you want with your own credentials, and let your users pick the route.

Open the dashboard Read the docs

4providers for payment initiation in the UK

  1. Enable BankingOpen banking
    Integrated
    No custodyAIS · PIS
  2. PlaidOpen banking
    Integrated
    No custodyAIS · PIS · VRP · KYC
  3. YapilyOpen banking
    Integrated
    No custodyAIS · PIS
  4. TrueLayerOpen banking
    Listed
    No custodyAIS · PIS
Open the full marketplace
The marketplace

Who provides what, and where.

Unirail starts at banking and grows outwards: verification, identity, compliance. Pick what you are building and the country you serve, and see every provider that can do it, what is live today, and who holds the money on the way.

Today Unirail routes account-to-account payments that nobody holds in between. Meta-providers that hold funds in transit only appear where your routing policy admits them.

Capabilities pick one or more
BankingLive now
VerificationListed
IdentityNext
ComplianceLater
Money movementListed
See the results

Loading the marketplace…

Providers
0
Integrated
0
Listed
0
Open slots
0

  • Plaid

    Open banking
    Integrated
    • AIS
    • PIS
    • VRP
    • KYC
    • AML (illustrative, not in the catalogue)
    No custody1 country
    Details

    Bank linking, UK payment initiation, VRP consents and identity verification through Plaid Link.

    Regulated
    Plaid is the PISP and AISP; the platform contracts with Plaid directly.
    Onboarding
    Self-serve sandbox · Production by contractProduction Payment Initiation needs Plaid's approval of the use case; VRP is enabled separately.
    Pays to
    payto://scan
    Credentials
    CLIENT_ID, SECRET, read from your own Infisical vault
    Illustrative
    Plaid Monitor is Plaid's own screening product; it is not part of Unirail's catalogue.

  • Yapily

    Open banking
    Integrated
    • AIS
    • PIS
    No custody1 country
    Details

    UK open banking: account linking and single immediate payments across UK banks, with Unirail's own bank picker.

    Regulated
    Yapily (Yapily Connect) or the platform's own licence.
    Onboarding
    Self-serve sandbox · Production by contractUnder Yapily Connect, Yapily is the regulated party and the platform shows Yapily's disclosure; payments are capped at £15,000.
    Pays to
    payto://scan payto://iban
    Credentials
    APPLICATION_ID, APPLICATION_SECRET, read from your own Infisical vault

  • Enable Banking

    Open banking
    Integrated
    • AIS
    • PIS
    No custody15 countries
    Details

    EEA account information and payment initiation: SEPA, SEPA Instant and domestic schemes, straight from payer to payee.

    Regulated
    Enable Banking by default; a licensed TPP can bring its own eIDAS certificates.
    Onboarding
    Self-serve sandbox · Production by contractWithout a contract, production runs in restricted mode (own accounts only).
    Pays to
    payto://iban
    Credentials
    APPLICATION_ID, PRIVATE_KEY_PEM, read from your own Infisical vault

  • TrueLayer

    Open banking
    Listed
    • AIS
    • PIS
    No custody1 country
    Details

    UK and European payment initiation; a second UK PISP for substitution when one provider degrades.

    Regulated
    TrueLayer as PISP.
    Onboarding
    Self-serve sandbox · Production by contract
    Pays to
    payto://scan payto://iban

  • Neonomics

    Open banking
    Listed
    • AIS
    • PIS
    • Verify
    No custody4 countries
    Details

    Nordic and EEA account information and payment initiation.

    Regulated
    Neonomics (Finanstilsynet).
    Onboarding
    Sandbox on request · Production by contractPoll-only statuses and multi-step SCA; account verification is limited to four calls a day.
    Pays to
    payto://iban payto://bban

  • Airwallex

    Meta-provider
    Listed
    • Payout
    • Pay-in
    • CoP/VoP
    • FX
    • X-border
    Held in transit19 countries
    Details

    One contract for collections into Airwallex accounts, payouts over local rails in many countries, FX, and UK CoP / EU VoP name checks. Routes through it hold money in transit.

    Regulated
    Airwallex holds funds in transit under its own licences.
    Onboarding
    Self-serve sandbox · Production by contract
    Pays to
    payto://scan payto://iban payto://ach payto://sgacct payto://bsb

  • Nium

    Meta-provider
    Listed
    • Payout
    • Pay-in
    • Verify
    • FX
    • X-border
    Held in transit2 countries
    Details

    Wallet-based global payouts, collections and FX, plus Nium Verify for account checks.

    Regulated
    Nium under its own licences.
    Onboarding
    Sandbox on request · Production by contractRequires an IP allowlist (static egress).
    Pays to
    payto://iban payto://scan payto://sgacct

  • Wise Platform

    Meta-provider
    Listed
    • AIS
    • Payout
    • FX
    • X-border
    Held in transitPayer's own account16 countries
    Details

    Cross-border transfers through Wise, or from a user's existing Wise account.

    Regulated
    Wise under its own licences.
    Onboarding
    Self-serve sandbox · Partner programmeLinking a user's own Wise account uses OAuth with mTLS and SCA step-up.
    Pays to
    payto://iban payto://scan payto://ach

  • Bridge

    On-chain
    Listed
    • Payout
    • Pay-in
    • Ramps
    Held in transitHeld for the user1 country
    Details

    Stablecoin orchestration: on and off ramps, virtual accounts and custodial wallets, including USDC and USDT.

    Regulated
    Bridge (a Stripe company); no UK FCA authorisation listed.
    Onboarding
    Self-serve sandbox · Production by contractEvery end user becomes a Bridge customer; whether third-party P2P payouts are permitted is unverified.
    Pays to
    payto://caip10 payto://ach payto://iban

  • Moneytree

    Account data
    Listed
    • AIS
    • Verify
    No custody1 country
    Details

    Japanese account aggregation for linking and ownership checks.

    Regulated
    Moneytree is a registered 電子決済等代行業者.
    Onboarding
    Sandbox on request · Production by contractData only; Japanese payment initiation needs the platform's own 電子決済等代行業 registration.
    Pays to
    payto://zengin

  • PayNow QR

    Direct scheme
    Listed
    • PIS
    No custody1 country
    Details

    Singapore person-to-person payments by QR code to a PayNow proxy, attested rather than confirmed.

    Regulated
    No intermediary; the payer's bank executes over FAST.
    Onboarding
    No sandbox · Self-serve productionNo provider: Unirail generates the SGQR payload and the payer pays in their own banking app. There is no completion signal.
    Pays to
    payto://paynow

  • OpenPayd

    Meta-provider
    Listed
    • Payout
    • Pay-in
    • CoP/VoP
    • Ramps
    Held in transit15 countries
    Details

    Banking-as-a-service: accounts and virtual IBANs, payouts, pay-by-bank, stablecoin ramps, UK CoP and EU VoP.

    Regulated
    OpenPayd under its own licences.
    Onboarding
    Sandbox on request · Production by contract
    Pays to
    payto://iban payto://scan

  • Modern Treasury

    Meta-provider
    Listed
    • Payout
    • Pay-in
    • Verify
    Your entity holdsHeld in transit1 country
    Details

    US payment operations over the platform's own bank accounts: ACH, wires, RTP, counterparties and reconciliation.

    Regulated
    The platform's own banks, or Modern Treasury's PSP.
    Onboarding
    Self-serve sandbox · Production by contract
    Pays to
    payto://ach payto://iban

  • Name check (CoP / VoP)

    1 open slot · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

  • Account verification

    1 open slot · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

  • KYC & ID verification

    3 open slots · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

  • KYB

    2 open slots · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

  • AML & sanctions screening

    2 open slots · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

  • Transaction monitoring

    2 open slots · placeholder
    Listing soon

    There is room for more than one provider per capability and country. Nobody is listed here yet, so these are placeholders, not partners.

    Browse providers

Data: a snapshot of Unirail’s provider catalogue. “Listed” providers come from desk research of public documentation and are not yet integrated. Open slots are placeholders for vendors nobody has listed.

How a payment travels

Five stops, one line of track.

The same five steps whichever provider carries the money. Your app never branches on a provider again.

  1. Ask for routes between two payto:// accounts. Up to three come back: cheapest, fastest and recommended, each with its legs, cost, ETA and who holds the money.

    routeQuotes.create

  2. Your user picks the route, in your UI. Today every route is account to account with no custody; meta-providers appear only where your policy admits them.

    quotes[i]

  3. Bind your user's approval, a passkey for example, to the quote's id and digest. If what they approved no longer holds, the intent fails with quote_changed.

    id + digest

  4. Create the payment intent with an idempotency key. Unirail hands back the next action, usually a redirect to the payer's bank.

    paymentIntents.create

  5. Every provider's statuses arrive as one event stream, signed with Standard Webhooks, whichever rail carried the payment.

    payment_intent.succeeded
Times and IDs are example values.
The platform

Everything around the rails, done once.

The parts every payments team rebuilds per provider, built once and shared by all of them.

One API

Institutions, customers, bank links, payto:// accounts, route quotes, payment intents and events. One SDK, the same calls whichever provider sits underneath.

Your user picks the route

Every quote spells out its legs, cost, ETA and custody, so the choice is real.

From
payto://scan •••• 0008
To
payto://iban GB•• •••• 3000
Legs
1 leg via Plaid
ETA
~40 s
Fee
£0.10
Custody
No custody

Example values, not real pricing.

Credentials stay in your vault

Provider keys live in your own Infisical. Unirail reads them at request time through OIDC federation and never stores them.

One event stream

Statuses from every provider, normalised and signed with Standard Webhooks.

  1. link_session.completedacct_…
  2. payment_intent.processingpi_…
  3. leg.updatedleg_…
  4. payment_intent.succeededpi_…

webhook-id webhook-timestamp webhook-signature

A control plane for all of it

Test and live environments, API keys, connections and routing policy, in one dashboard.

Open the dashboard
For developers

Quote, approve, pay. That is the integration.

Two calls move money through whichever provider your user chose. Everything else, from bank pickers to provider statuses, arrives in the same shapes.

  • payto://Every account is a payto:// address, and Unirail only ever returns it masked.
  • minor unitsAmounts are integer minor units in a string, so “5000” in GBP is £50.00 and no float ever carries money.
  • idempotentWrites take an idempotency key, so a retried request never pays twice.
  • test / liveSeparate test and live environments with their own API keys and connections.
Read the docs Get a test key
checkout.ts
import { createUnirail } from "@unirail/sdk";

const unirail = createUnirail({ apiKey: process.env.UNIRAIL_SECRET_KEY });

const { quotes } = await unirail.routeQuotes.create({
  from: payer,
  to: payee,
  amount: { value: "5000", asset: "iso4217:GBP" },
});

const intent = await unirail.paymentIntents.create(
  { quote: quotes[0].id, digest: quotes[0].digest, returnUri },
  { context: { idempotencyKey: `pay:${id}` } },
);

Banking first. Identity and compliance next.

3 integrated, 10 listed, and open slots for the KYC, KYB and screening vendors still to come.

Integrated: Plaid, Yapily, Enable Banking. Listed: TrueLayer, Neonomics, Airwallex, Nium, Wise Platform, Bridge, Moneytree, PayNow QR, OpenPayd, Modern Treasury.

Browse providers

Bring your providers. Keep your keys.

Connect the providers you already have, or add new ones from the marketplace. Your users choose the route, and your credentials never leave your vault.

Open the dashboard Read the docs