Frequently Asked Questions

NetiRails is a payment orchestration platform for fintechs, payment institutions and banks that run cross-border payments. It connects payment execution, FX, compliance, ledgering and reconciliation into one operational system that runs on your own infrastructure.

Payment orchestration is the layer that coordinates everything sitting between the payment rail and live operations: routing each payment through the right providers, holding the state of every transaction, normalising statuses across systems, retrying what fails, and producing data that reconciles.

The rail moves the money. Orchestration is what makes that movement operable, auditable and repeatable across corridors, currencies and providers.

None of those on their own. NetiRails is a productized service: a reusable software foundation plus the implementation work to put it into production inside your institution. It is not a regulated payment processor and not a payout network, so it does not move money in its own name.

The distinction that matters most: networks like SWIFT coordinate messages between institutions, while NetiRails coordinates the payment flow inside one institution, across the providers that institution has chosen.

NetiRails is designed primarily for fintechs, payment institutions, neobanks, and other financial players building cross-border payment or settlement products.

It is the strongest fit for teams that need to launch a real service, reduce operational complexity, and avoid building the whole stack from scratch.

NetiRails is built by Neti, a software engineering and blockchain delivery company founded in 2010, with more than 40 engineers and over 120 delivered projects, rated 5.0 on Clutch.

Neti has worked on blockchain and DLT systems since 2019, across fintech, payments, tokenization and trade finance. NetiRails is where that delivery experience is packaged into one product for cross-border payments.

NetiRails is deployed on-premise, on your own infrastructure, and plugs into the providers, ledgers and payment systems you already run. There is no migration and no re-platforming project, because NetiRails adds the orchestration layer above your stack rather than replacing it. Your payment logic, your data and your architecture stay yours.

NetiRails is a set of modules that deploy and scale independently: workflow orchestration, provider abstraction, FX and liquidity logic, stablecoin settlement rails, a reconciliation engine, an operations and compliance layer, and a privacy layer.

You start with the modules the first flow needs and add the rest when the business requires them, not when a vendor decides to upsell. You do not pay for modules you do not use.

Yes. Providers across ledger, wallet, custody, FX, KYC and on/off-ramp are integrated through a pluggable mediator pattern rather than hardcoded into the payment core, so changing one is a configuration and adapter change measured in days, not a re-architecture project measured in months.

This is deliberate: vendor lock-in is one of the most expensive structural risks in payment infrastructure, and the architecture removes it by design. You are never locked into a single vendor.

No. NetiRails is infrastructure, not a regulated payment processor and not a custodian, so it does not take possession of funds. Funds sit with the custody provider you contract with, and key management stays with you or with that provider, through integrations such as Fireblocks and Turnkey.

NetiRails orchestrates the flow and records what happened; it does not hold what moves through it.

Failure handling is part of the system, not an operational afterthought. Every transaction carries a durable state, provider statuses are normalised into one model, retries are idempotent so a repeat never double-sends, and anything that needs a human lands in exception case management with hold, release and reject gates and a named owner.

The full audit trail is written as the payment moves, so you can answer where the money is and why something stopped without reconstructing it from provider statements.

Usually, it is not the rail itself. Problems show up first in statuses, exceptions, retries, reconciliation, compliance checks, and the operational work needed to understand where money is, why something failed, and what needs human action.

That is why NetiRails is built as an operational backbone, not just a payment integration.

From a few seconds up to a maximum of 30 minutes. The exact time depends on the currency and the settlement corridor used. Settlement runs outside the standard correspondent banking windows, so funds reach the beneficiary even when traditional systems are closed.

USDC and USDT are supported as native settlement assets, with on-chain and off-chain bridging and custody integration behind them. The FIAT currencies and corridors available to you depend on the on/off-ramp and custody providers you contract with, which is why the provider layer is pluggable rather than fixed.

FX runs through the provider you choose, coordinated by the FX and liquidity module: routing rules across providers, spread control, reserve optimisation and stablecoin-based hedging. NetiRails integrates 1inch for on-chain FX routing and can sit alongside your existing FX partners.

You keep the commercial relationship and the rate; NetiRails makes the routing and the resulting positions visible and reconcilable.

The ledger is the single source of truth. Every payment, across providers, currencies, stablecoin and FIAT, is recorded against one transactional record, and reconciliation runs against that ledger rather than against provider statements. Settlement files, CRM bookings, on-chain events and provider responses all match back to the same record, which is what makes month-end close hold together as you add corridors.

Both. The orchestration layer handles real-time payments and batch runs through the same system, with the same status normalisation, retries and exception handling in either mode.

Minimal ones. NetiRails runs a workflow that matches the process already in place on your side, so you do not have to rebuild your existing flows. Provider integrations sit behind a mediator layer, so adding or changing a partner is an adapter, not a change to your payment core.

Integration follows the messaging your systems already use, and the architecture is built toward ISO 20022 alignment for institutions that require it. Provider integrations sit behind the pluggable mediator layer, which means a new custody, FX, KYC or ramp partner is an adapter, not a change to your payment core.

A realistic first milestone is one meaningful end-to-end payment scenario in production, not everything at once. The delivery model targets a first live corridor in around 90 days, including the operational backbone around the flow rather than just the transfer itself. Neti has shipped a comparable production B2B payment MVP in 14 weeks under a fixed-price commitment.

A real business owner on your side, a decision to go to production rather than to explore, and availability from the people who own the payment process and the provider relationships. NetiRails is delivered with implementation ownership on our side, including discovery, configuration, integrations, documentation and knowledge transfer, so what we need from you is direction and access, not engineering capacity.

It is both. NetiRails is best described as a productized service: a repeatable infrastructure foundation combined with discovery, configuration, integrations, documentation, knowledge transfer, and implementation ownership.

Clients are not buying a black-box tool or extra developers. They are buying a working payment capability delivered in a defined model.

Yes. The modular architecture of NetiRails lets the platform integrate with the systems already running in your institution, so the workload on your side stays as small as possible.

If you would rather use external providers, we have ready integrations with leading vendors in this area, which shortens the time from project start to go-live.

NetiRails is compliance-ready, which means it is designed to support controls, auditability, and compliance workflows from the start. At the same time, NetiRails does not take legal responsibility for the client's regulatory compliance or licensing obligations, it supports the process, but it is not a substitute for legal or regulated ownership on the client side.

NetiRails is infrastructure, not a regulated payment processor, so legal responsibility for your regulatory posture stays with your team. The workflow is designed to support it: hold, release and reject gates, KYC, AML and screening integration points, and a full audit trail are part of the system from the first milestone.

KYC, KYT, AML, sanctions screening, Travel Rule support and MiCA-ready controls are designed into the payment flow from day one rather than added before launch. NetiRails gives your compliance function the checkpoints, evidence and audit trail it needs to demonstrate control. It does not certify your institution, and the regulatory obligation stays with the licence holder.

Public rails create transparency by default, and financial institutions need controlled visibility instead. NetiRails is built for settlement flows where sensitive transaction data stays confidential, while compliance teams, auditors and regulators keep verifiable access when required. Private by default, auditable by design.

Every state change in a payment is recorded against a canonical transaction record: which provider was called, what came back, which compliance checkpoint passed or held, what was retried, and who released an exception. Because reconciliation runs against the same ledger, the audit trail and the books tell the same story, which is what shortens audit preparation from weeks to hours.

Yes. Regulatory requirements mean you must hold direct agreements with your custody, AML, KYC and KYT providers. The selection path is much simpler with us: thanks to our existing integrations and partnerships we recommend a specific option and point you to named contacts on the provider side who will run the conversation through to signature.

NetiRails has working integrations across the layers a cross-border flow needs: Fireblocks and Turnkey for custody and key management, Sumsub for KYC and AML, Yellow Card for on and off-ramp, 1inch for FX routing, and Formance for ledgering. These are starting points, not requirements. Each one sits behind the same pluggable mediator layer as any provider you bring yourself.

Yes. You can bring your own custodian, liquidity provider, issuer or compliance partner, use the integrated partner ecosystem, or run a mix and change it over time. The architecture is modular across ledger, custody, compliance, FX, liquidity and on/off-ramp layers precisely so that provider choice stays a commercial decision rather than an architectural one.

The partnership program connects custody, compliance, on/off-ramp, FX and ecosystem partners into one orchestrated infrastructure, so a payment team does not have to stitch fragmented providers together from scratch. For an institution buying NetiRails it means the integration work with those partners is already done and the commercial introduction is faster.