ACH settlement in minutes, not days.
The Pegasus routing engine moves ACH over regulated stablecoin rails without holding the float. One noncustodial integration also powers RWA distribution and onchain yield.
Batch windows. Overnight float. Clearing that waits on banking hours.
Stablecoin path. Continuous settlement. No float held in the middle.
One routing engine. Execution end to end.
The engine behind minute-level ACH settlement is in production across 66 chains. Institutions connect once. Native settlement, multiple liquidity providers.
Scoped, revocable permissions. No claim on balances.
Client assets remain within the client’s own perimeter. Pegasus holds only scoped, revocable permissions with no claim on underlying balances.
Institutions connect once. The routing engine handles ACH, RWA distribution, and onchain strategies across venues, chains, and liquidity providers.
Settlement happens onchain, natively, across multiple liquidity providers. No synthetic intermediaries.
Banking windows become continuous settlement.
ACH was built for batch clearing. The routing engine moves those payments onto regulated stablecoin rails so treasury teams go from multi day float to settlement in minutes, without changing who holds the assets.
- OriginatedPayment instruction filed
- BatchedWaiting on clearing windows
- T+3 to T+5Float sits with the PSP
- FinalFunds available days later
- InstructedSame ACH intent, scoped permissions
- RoutedEngine selects the stablecoin rail
- MinutesOnchain confirmation, no overnight float
- SettledFunds final. No intermediary float.
Float leaves the path
PSPs today sit on unsettled ACH exposure for days. The routing engine uses stablecoin rails so settlement does not depend on holding that float.
Atomic multi leg commit
Routing, conversion, and payout commit together. If any leg fails, the transaction does not settle. Treasury sees a deterministic outcome.
Assets stay in perimeter
Noncustodial by architecture. Client balances remain under client control with scoped, revocable permissions and no claim on underlying funds.
That same routing engine also powers RWA distribution and onchain yield. Compress ACH into minutes, and extend into the layers below. One integration. Multiple institutional rails.
Three layers on the routing engine.
Besides ACH settlement, the same engine opens RWA distribution, onchain strategies, and stablecoin payout rails. The client sets the parameters. Capital controls sit onchain.
RWA Distribution Rails
The routing engine moves institutional capital into regulated settlement environments, with atomic multi leg execution. A transaction commits only when every leg succeeds.
Custody integration is handled through scoped permissions, compatible with existing custodial workflows.
Onchain Strategies
Lending, looping and structured products on institutional grade collateral, executed atomically by the routing engine on top of the distribution layer.
Parameters and risk limits are set by the client and enforced onchain.
Stablecoin Settlement
The routing engine's fiat facing path for ACH and payouts: stablecoin settlement with onchain confirmation in seconds, exposure moved to providers priced to carry it.
Compresses 3 to 5 day ACH clearing into minutes. Runs alongside existing banking rails without holding the float.
The routing engine, built like the systems it connects to.
The routing engine runs on privately owned bare metal infrastructure. No shared cloud tenancy in the execution path.
Sanctions and compliance screening is integrated directly into the flow, not bolted on after settlement.
SOC 2 Type I complete; Type II in progress.
Connect once. Let the routing engine settle ACH, distribute RWA assets, and produce onchain yield.
Talk to our team about a controlled integration into your product or workflow.
Speak with us.
Tell us about your product or workflow and we'll get back to you within one business day.
Or email [email protected]