Collection on schedule
Due dates watched off-chain, authorized pulls executed on time, every attempt recorded.
Mesub handles scheduled collections, failed-payment retries, and access control in one subscription layer.
Built on the open-source-audited Solana Subscriptions program.

The protocol settles the money. Mesub runs the subscription around it - so a payment result becomes something your product can act on.
See how it worksDue dates watched off-chain, authorized pulls executed on time, every attempt recorded.
Charge in USDC or another compatible SPL Token or Token-2022 mint through the same subscription flow.
Multiple subscriptions can share the same token account without competing for its single delegate slot.
Wire the subscribe flow once and watch the rest from one place: what is due, what settled, what failed, and who came back after a retry. The same data your app reads through the API, in a view your team can act on.

Install the SDK, read the subscription state, decide. Accounts, delegations and pull execution stay on our side of the line - your route handler only ever sees an answer.
Questions
Mesub is a billing layer for Solana subscriptions: it collects authorized recurring payments on schedule, retries the ones that fail, and turns the result into the access state your product reads.
A billing layer for Solana subscriptions. It collects the recurring payments a subscriber has authorized on-chain, retries the ones that fail, and turns each result into an access state your app can read.
A merchant publishes a plan on-chain: amount, token, billing period. The subscriber approves it once from their own wallet, authorizing a transfer capped at that amount per period, and can revoke it at any time.
The subscription turns unpaid, and if no later try settles it is stopped and nothing more is charged. On the paid tiers Mesub retries on the schedule you set and access stays on while it does; on Free you retry by hand and access is off until a payment settles.
Yes. Subscribers sign a delegation from their own wallet and keep custody of their funds. Mesub never holds keys - it only submits pulls that were already authorized, within the signed cap.
The status says where a subscription stands (active, unpaid, cancelled, stopped or ended), and access is the yes or no the API answers for your app: a cancelled subscription keeps access until the period already paid ends, an unpaid one only on the paid tiers. Gate on access, not on the status; Mesub also reads the wallet ahead of each renewal and tells you whether the next charge can pay.
Install the SDK, drop the subscribe component into your checkout, and put one guard in front of the routes you sell. The guard asks Mesub whether the customer has access and answers HTTP 402 when they do not.
Still have a question? [email protected]Copy
Wire the subscribe flow, add the guard, and let the processor take the calendar from there.
Every line is checkable in the open-source repository.