Tributary Review 2026: Rule-Based Payments on Solana

Tributary is a payments protocol on Solana built around one idea: money should move according to rules the owner sets once, rather than needing a signature each time. Users delegate token spending authority and install a policy, and payments then execute within those limits.

The homepage frames this as a primitive with three parts: a trigger condition (WHEN), a value transfer (PULL) and a destination (ROUTE). The simplest setup, a scheduled pull to a wallet, works as recurring payments. The project reports more than 4,000 pulls executed on mainnet by six teams, and lists 10+ integrations.

Use cases named include SaaS subscriptions, freelance milestone payments, usage-based billing for AI and API providers, invoices, and budgets for AI agents. Developers can integrate through a TypeScript SDK, React components and a hosted USDC checkout.

The project is early. Adoption numbers are modest, and the homepage does not publish audits, a team or fee rates.

Most crypto payments are push-based: you hold a balance and sign each transfer. Tributary uses a pull model instead. A user signs once to delegate spending authority over a token and to install a policy that defines what can be taken and when.

The Solana program enforces the policy. A gateway signer can trigger a payment only when the agreed conditions are met, and the program pulls the delegated amount from the user's token account, pays the recipient and splits the fee on-chain in one step. The project says it holds no funds and uses no escrow for this basic config.

A fuller configuration adds a validation gate and a routing step. For example, a Lighthouse assertion can check that a hot wallet's USDC balance is below a threshold. If so, the pull goes through a Meteora DLMM swap before reaching the recipient. If the balance is fine, nothing moves.

Tributary's homepage describes the fee structure but not the numbers. Each payment carries one gateway-set fee, calculated in basis points of the amount. That fee is split on-chain between the protocol, which receives a 20% share, a scheduler and the gateway.

The actual gateway fee rates are not published on the homepage. Users would also pay normal Solana network fees, and swap routes would add the costs of the venue used. Check the documentation or the gateway you use for current rates.

Tributary says it is non-custodial and never holds user funds, with payment rules enforced by the Solana blockchain. That reduces counterparty risk compared with a custodial bot, but it does not remove smart-contract risk or the risk of approving overly broad delegation.

The homepage does not mention an audit, bug bounty, team identities or past incidents. Treat it as unaudited until a report is found in the documentation. Users should set tight amounts and intervals, review each policy before signing, and revoke delegations they no longer need.

Tributary is aimed at Solana developers, SaaS and API businesses, DAOs and teams building AI agents that need to pay or get paid on a schedule or by usage. It also suits users of those services who prefer to set spending limits once instead of signing every charge. People who want a simple consumer wallet feature or a protocol with a long audited track record may find it too early.