Back to Blog

Programmable Payment Routing for the Onchain Agent Economy

OOBE Protocol is partnering with MultiHopper to bring programmable payment routing into its agent infrastructure, giving autonomous agents more control over how value moves across path, timing, privacy, policy, and compliance.

S
Solking
August 25, 2026
·
4 min read
Programmable Payment Routing for the Onchain Agent Economy

OOBE Protocol x MultiHopper: Programmable Payment Routing for the Onchain Agent Economy

Autonomous AI agents are moving quickly from research concepts to systems that interact with real infrastructure, applications, and financial rails. But for an agentic economy to actually function, agents need more than intelligence. They need infrastructure that lets them identify themselves, coordinate with other agents, execute onchain actions, and move capital on their own.

That is where OOBE Protocol is building.

OOBE provides the infrastructure for autonomous agents on Solana, bringing identity, coordination, tooling, execution, payments, and runtime into one stack. Through SAP and SAP MCP, agents can register, discover and coordinate with each other, access ecosystem tools, and transact through x402 and escrow-based payments.

That already gives agents the ability to move value. The next layer is giving them more control over how that value moves.

This is where MultiHopper comes in. The partnership expands OOBE’s existing payment infrastructure with programmable routing around path, timing, privacy, policy, and compliance.

Bringing programmable routing to autonomous agents

Financial transactions are a fundamental part of any autonomous economy. Agents need to pay for APIs, services, data, compute, and interactions with other agents, and they need to route those payments according to specific requirements around privacy, timing, policy, and compliance.

MultiHopper is programmable routing infrastructure for digital assets, essentially SWIFT rebuilt natively onchain. It routes assets across any wallet or contract with full control over path and timing, with no custody, no signatures required from hop wallets, and no pooled funds.

Privacy is handled at the public transaction layer while keeping compliance built into the routing process, with every hop screened through MultiHopper's TRM Labs integration at the smart contract level for OFAC and illicit-fund exposure.

Through the integration, MultiHopper's routing capabilities will become accessible to SAP agents through OOBE's SAP MCP tooling and runtime, extending programmable routing across agent workflows, developer integrations, and user-facing OOBE products.

OOBE Protocol & Multihopper Integration Logic
OOBE Protocol & Multihopper Integration Logic

Why payment routing matters for the agent economy

Agent-to-agent commerce introduces requirements that traditional payment infrastructure was never built around. An autonomous agent may need to route payments according to predefined policies, execute transactions autonomously within defined permissions and risk controls, preserve privacy between counterparties, handle different settlement requirements, apply compliance rules to transactions, and coordinate payments as part of a larger onchain workflow.

MultiHopper's routing infrastructure is built around exactly these requirements, programmable and fully onchain rather than relying on mixers, tumblers, or commingled funds.

Bringing it into OOBE Protocol's stack gives agents and applications more control over how payments are routed without requiring a separate routing layer. It extends OOBE's existing payment and execution infrastructure with MultiHopper's programmable routing capabilities.

Built on Solana

The partnership is launching within the Solana ecosystem, where transaction speed and low cost suit autonomous, high-frequency interactions well. For agents operating in real time, payment infrastructure has to keep pace with execution.

Solana provides the settlement layer, OOBE provides the agent infrastructure, and MultiHopper adds programmable payment routing, creating a direct path from agent intent to financial execution.

A shared opportunity

The partnership also creates a shared commercial opportunity for both teams. Transactions routed through OOBE agents and products using MultiHopper will contribute to a shared revenue model, aligning both sides around growing usage and transaction volume.

For OOBE Protocol, it adds a stronger financial layer not only for developers building on SAP, but also for the broader user-facing products and experiences OOBE plans to bring onchain.

For MultiHopper, it opens access to both a growing agent ecosystem and new transaction flow coming through OOBE’s wider stack.

From Build Station Berlin, organized by @SuperteamDE
From Build Station Berlin, organized by @SuperteamDE

From Build Station Berlin to partnership

What started at Build Station in Berlin, Germany as a connection between two teams building different parts of the same vision has grown into a deeper technical and commercial partnership, bringing OOBE’s agent infrastructure together with MultiHopper’s programmable payment routing.

What's next

The teams are now working through the integration itself, including SAP MCP tooling, routing and execution flows, security and policy controls, and the developer experience around bringing MultiHopper into agent workflows.

The shared long-term vision is straightforward: give autonomous agents the infrastructure to operate independently and the programmable financial rails to transact within defined rules.

OOBE Protocol is building the infrastructure for autonomous onchain agents.

MultiHopper is building programmable, private, and compliant routing for onchain value movement.

Together, the two are building the financial infrastructure for the next generation of autonomous onchain agents.