Provider tender, not provider lock-in.
Multiple providers can compete for the same intent. The Router evaluates capability, route economics, gas requirements and execution maturity instead of hard-coding one provider into the product.
Universal Router is an outcome-first execution layer for wallets, payment apps and other products that need to move value across providers and networks without exposing provider, gas or recovery mechanics to the application.
Universal Router separates the user-facing contract from network- and provider-specific mechanics. It discovers eligible sources, compares execution supply and locks a plan against the requested recipient outcome.
Multiple providers can compete for the same intent. The Router evaluates capability, route economics, gas requirements and execution maturity instead of hard-coding one provider into the product.
Provider fees, bridge costs, gas policy, sponsorship recovery and platform fees are normalized around the final recipient outcome and maximum user debit.
A provider being integrated is not the same as a route being proven. Routes remain gated until the relevant quote, prepare, execution, status and recovery behavior has evidence for that profile.
Unknown post-submit states are not treated as permission to send again. Idempotency, status resolution and fund-location logic are part of the Router lifecycle.
Provider status is intentionally not binary. A provider can be verified for one route profile and remain in certification for another. Capability labels explain why each supply source exists behind the tender.
A paymaster, fee payer or TRON resource gateway is not treated as another bridge. Router composes the execution provider with an eligible gas/resource policy for the locked route.
Applications describe the target outcome and constraints. Provider- and network-specific execution remains behind the Router boundary.
Wallets and payment applications do not need separate product logic for every bridge, gas sponsor or network-specific execution adapter.
The lifecycle makes execution maturity explicit. Supply can change, but the application-facing operation remains coherent from intent to receipt.
Find balances, supported assets, candidate networks and route-specific eligibility.
Ask eligible providers for executable supply instead of binding the product to one provider.
Compare recipient outcome, total payer debit, gas path, expiry and execution evidence.
Run the locked plan only after user authorization and the required pre-submit checks.
Resolve unknown or partial states against the same operation instead of blindly submitting again.
Universal Router normalizes network-specific signing, gas, provider and settlement mechanics behind one outcome-oriented execution model.
Verified source and destination profiles, including the settled Base + Arbitrum USDC multi-input route.
Verified source participation in the settled multi-input profile, with additional provider routes under certification.
Live BSC sponsorship and settlement profiles exist alongside EIP-7702 / ERC-4337 smart-account integration.
Same-chain USDT resource execution is REAL_VERIFIED. TRON-origin cross-chain execution is PARTIAL_VERIFIED.
Same-token terminal payments with Router fee payer are mainnet verified.
Direct, bridge, intent and smart-account capable supply is integrated behind route-specific gates.
Eligible across multiple provider families with exact-output and gas-aware tender support.
Integrated across direct, cross-chain and intent supply with runtime capability gates.
Integrated into provider discovery and common origin execution models.
Native P2WPKH / PSBT execution is implemented behind an operator gate.
Universal Router treats BNB Chain as an execution rail that can participate as a source or destination inside the same intent lifecycle used across the rest of the Router. Scoped mainnet sponsorship and settlement profiles are already proven; broader smart-account submission and recovery remain certification-gated.
BNB integration combines smart-account / EIP-7702-compatible execution, ERC-4337 bundler and paymaster paths, provider capability checks, exact-output constraints and user authorization. Separately, a scoped MegaFuel + LI.FI BSC→Base profile already has mainnet sponsored execution and settlement evidence. Smart-account submit and recovery are still fail-closed until certified.
The Router selects an eligible gas policy at route level. The application should not require a user to manually choose a bundler, paymaster or sponsor just to execute the intended payment.
Applications receive one operation that progresses through explicit states. Unknown post-submit conditions move into recovery rather than being interpreted as permission to retry blindly.
Candidate economics and capability evidence are available.
The locked signing / transaction payload matches the intended route constraints.
User authorization is bound to the locked plan.
Execution has crossed the broadcast / provider submission boundary.
Destination outcome and required receipts are verified.
Unknown, partial or failed states are resolved against the same operation.
The Router is designed to own routing and state transitions, not private keys or a server-side omnibus customer balance.
The Router does not receive private keys. The intent fixes the recipient, output asset, destination network, output amount and debit constraints before execution proceeds.
Once submit may have happened, the safe action is to resolve state. The Router records the operation identity, checks provider / chain status and recovers the existing execution path.
This is a concrete runtime-verified composition, not a statement that Universal Router only exists for Base. The profile demonstrates two compatible source balances participating in one intent and one final recipient payout.
The Router is a standalone infrastructure product. Universal Card is one client of the same intent and execution model.
Let a user choose what should arrive while routing across eligible balances, networks and providers underneath.
Keep recipient settlement fixed while the Router evaluates execution supply and total payer debit.
Integrate one intent lifecycle instead of reproducing provider-specific quote, gas, submit and recovery logic in every product.
Universal Card demonstrates how the same Router can be presented to a consumer: choose the outcome, review the debit, authorize once and track one operation through settlement or recovery.